Intelligent office system middle table

Abstract

The invention relates to the technical field of internet and intelligent office, and discloses an intelligent office system middle desk, which comprises a built-in super administrator account, the super administrator account creates a tenant account and distributes a tenant system function authority, a data viewing range authority and a data operation authority, and the tenants create user accounts and distribute corresponding permissions. According to the intelligent office system middle platform, through data interaction and function linkage of the intelligent office system middle platform and other sub-service systems, the problem that after the system is interrupted due to abnormal tasks, the batch of interacted data is not interrupted synchronously but is brought into an interface message retransmission queue by the intelligent office system middle platform in a bookkeeping manner, and the interaction efficiency is improved is solved. And after the subsequent system exception is recovered, the batch of interacted exceptional data is continuously transmitted, so that the integrity and the stability of interface data transmission between the intelligent office system middle platform and the accessed sub-service system are ensured.

Description

Technical Field

[0001] The present invention relates to the technical field of Internet and intelligent office, and specifically to a platform for an intelligent office system. Background Art

[0002] The main function of the existing smart office system middle platform is to integrate multiple other third-party business subsystems, so that the middle platform of this system can be used as a unified login entrance to log in to other third-party business subsystems that have been connected to this middle platform system without logging in.

[0003] The smart office system middle platform is mainly used in the intelligent application fields within corporate offices under the Internet + Internet of Things technology, such as conference room reservation, unmanned front desk smart reception, smart workstation reservation and other business scenarios, as well as automatic control of IoT devices in these business scenarios and other functional applications.

[0004] The existing smart office system platform lacks the function of dividing tenants and users of the system, and cannot provide users with more convenient system services through SAAS architecture, such as monthly leasing and purchasing package packages based on demand to use the system services; The existing smart office system middle platform lacks the function of unified configuration and management of connected sub-business systems, and cannot well realize the unified setting of public data information of other sub-business systems through the smart office system middle platform, such as organizational departments, user accounts, regional permissions, system notifications, material templates and other unified management functions; The existing smart office system middle platform lacks the function of unified interface call task management for the connected sub-business systems, and cannot well realize data interaction and functional linkage with other sub-business systems through unified task scheduling of the smart office system middle platform. If the task is abnormally interrupted, the batch of data being interacted will be synchronously interrupted, and the integrity and stability of the interface data transmission between the smart office system middle platform and the connected sub-business systems cannot be well guaranteed.

[0005] In view of this, we propose a smart office system middle platform. Summary of the invention

[0006] The purpose of the present invention is to provide a smart office system platform to solve the problems raised in the above background technology.

[0007] To achieve the above object, the present invention provides the following technical solutions: A smart office system middle platform includes a built-in super administrator account, which creates tenant accounts and assigns tenant system function permissions, data viewing range permissions, and data operation permissions; Tenants create user accounts and assign corresponding permissions; The management user creates ordinary user accounts and assigns ordinary user permissions. Different roles manage the next level of accounts and system data according to different data viewing scopes and functional permissions, and implement unified configuration and management of data information that the role account has permission to view. When the system has new scheduling tasks, it interacts with other sub-business systems through three steps: task preprocessing, batch task execution, batch task status confirmation, and task table status update, to ensure the integrity and stability of interface data transmission.

[0008] Preferably, system function permissions serve as the main carrier of data permissions and system permissions, and exclusive system function packages are formulated according to different user needs. System function permissions serve as the main carrier of data permissions and system permissions, and according to user procurement needs, tenants formulate exclusive system function packages for each user to meet users' diverse and flexible service supply needs.

[0009] Preferably, the data viewing scope permission is set to only view the data created by oneself, view the data within the same department or designated departments, view the data within the same company and designated branches and subsidiaries of the company. The data viewing scope permission refers to the allocation and setting of viewing scope permissions for the data of the functional modules of each business subsystem in the system. For example: only being able to view the data created by oneself, being able to view the data within the same department or designated departments, being able to view the data within the same company and designated branches and subsidiaries of the company.

[0010] Preferably, data operation permissions are controlled to the allocation settings of specific page function permissions such as adding, deleting, modifying and querying each specific sub-business system function module and menu, and data operation permissions are the permission allocation dimensions for each functional sub-module and menu within this product, and the permission granularity can control the allocation settings of specific page function permissions such as adding, deleting, modifying and querying each specific sub-business system function module and menu.

[0011] Preferably, different roles use this middle platform to uniformly set up and manage organizational departments, user accounts, regional permissions, system notifications, material templates and other functional applications.

[0012] Preferably, in the data interaction of the new scheduling task, the middle platform sends a new task message to the message queue processing service, and the message queue processing service forwards it to the relevant sub-business system.

[0013] Preferably, the sub-business system performs internal preprocessing operations after receiving the new task message, and sends a message to the message queue processing service that it is ready to receive the new task after the preprocessing is completed.

[0014] Preferably, after the middle station receives the message prepared by the sub-business system, it sends the new task-related data to the message queue processing service in batches in the form of data packets, and the message queue processing service synchronously forwards it to the sub-business system.

[0015] Preferably, after processing the task data, the sub-business system sends the processing result to the message queue processing service, and the message queue processing service forwards it to the middle station. After receiving it, the middle station automatically updates the task execution status and resends the task if there is a failure.

[0016] Preferably, when creating a new task, the task status and related information are recorded in the Tasks and TaskLogs tables. The default status of Tasks is status = pending, retry_count = 0, batch_no records the entire life cycle of the task, and the TaskLogs table is the actual single data packet to be pushed; start the scheduled task query task, if there is a task being processed in the in_progress status, the task is interrupted and waits for the next task; after starting the task, publish a specific topic and content, the sub-business system subscribes to the task rules to execute the corresponding rules, and receives a receipt for the published message, and the middle station starts to execute content push after subscribing to the receipt message; content push publishes a specific topic and message confirmation receipt, and returns a successful status when the App processes the number of messages that meet the task requirements. If there is a failure record, enter the retry task.

[0017] Compared with the prior art, the present invention provides a smart office system platform, which has the following beneficial effects: 1. The smart office system middle platform, through the unified task scheduling of the smart office system middle platform and the data interaction and functional linkage with other sub-business systems, solves the problem that after the system is interrupted due to task exception, the batch of data being interacted will not be synchronously interrupted, but will be accounted by the smart office system middle platform and included in the interface message retransmission queue. After the subsequent system exception is recovered, the batch of data that was interacted with abnormally will continue to be transmitted, thereby ensuring the integrity and stability of the interface data transmission between the smart office system middle platform and the connected sub-business system.

[0018] 2. The middle platform of the smart office system provides a SAAS architecture, which can provide users with more convenient system services, such as monthly leasing, purchasing a package on demand to use the system services, and also supports private procurement and deployment of the system. Compared with the existing technology, it can only be sold as a single software system as a whole software package, which cannot meet the functional services of purchasing and using system software on demand.

[0019] 3. The smart office system middle platform realizes the unified setting of public data information of other sub-business systems through the smart office system middle platform, such as organizational departments, user accounts, regional permissions, system notifications, material templates and other unified management functions. Compared with the existing technology, you can only log in to the middle platform system of the existing technology and perform the operation settings of specific business functions in multiple software systems. It is impossible to uniformly operate and set it in the middle platform, and other related sub-business systems can synchronously update settings and functional services. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 A brief schematic diagram of the SAAS architecture of the smart office system of the present invention; Figure 2 A detailed schematic diagram of the SAAS architecture of the smart office system of the present invention; Figure 3 This is a flow chart of middle-end task scheduling in the smart office system of the present invention. DETAILED DESCRIPTION

[0021] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0022] See also Figure 1 - Figure 3 , the present invention provides a technical solution: A smart office system middle platform includes a built-in super administrator account. The super administrator account creates tenant accounts and allocates tenant system function permissions, data viewing range permissions and data operation permissions. Tenants create user accounts and allocate corresponding permissions. Management users create ordinary user accounts and allocate ordinary user permissions. Different roles manage the next layer of accounts and system data according to different data viewing ranges and functional permissions, so as to achieve unified configuration and management of data information that the role account has permission to view. When the system has a new scheduling task, it interacts with other sub-business systems through three links: task preprocessing, batch task execution, batch task status confirmation and task table status update, so as to ensure the integrity and stability of interface data transmission. Compared with the existing technology, the middle platform of the existing technology lacks the function of unified interface call task management for the connected sub-business system, and cannot realize data interaction and functional linkage with other sub-business systems through unified task scheduling of the smart office system middle platform. If the task is abnormally interrupted, the batch of data being interacted will be synchronously interrupted, so as to ensure the integrity and stability of interface data transmission between the smart office system middle platform and the connected sub-business system.

[0023] In one embodiment of the present invention, the super administrator creates tenant accounts and allocates tenant permissions using the following scenarios: This middle platform has the function of creating tenant accounts and assigning tenant system function permissions, data viewing scope permissions and data operation permissions. At the beginning of the system installation and deployment, a super administrator account (SuperAdmin) will be built in. This account is used to create new tenant account information and assign system function permissions, data viewing scope permissions and data operation permissions to the new tenant; System function permissions are the main carriers of data permissions and system permissions. Based on the purchasing needs of tenants, the super administrator will formulate a dedicated system function package for each tenant to meet the diverse and flexible service supply needs of tenants. Data viewing scope authority refers to the allocation and setting of the viewing scope authority of the data of each business subsystem function module in the system, for example: only the data created by oneself can be viewed, the data within the same department or several designated departments can be viewed, and the data within the same company and several branches and subsidiaries of the company can be viewed; Data operation permissions are the permission allocation dimension for each functional sub-module and menu within this product. The permission granularity can control the allocation and setting of specific page function permissions such as adding, deleting, modifying and querying each sub-business system functional module and menu.

[0024] In one embodiment of the present invention, tenants create user accounts and assign user rights using the following scenarios: This platform has the function of creating user accounts and assigning user system function permissions, data viewing range permissions, and data operation permissions. The tenant created by the super administrator creates new user organizations and account information, and assigns system function permissions, data viewing range permissions, and data operation permissions to the newly created user; System function permissions are the main carriers of data permissions and system permissions. Based on the user's purchasing needs, the tenant will formulate a dedicated system function package for each user to meet the user's diverse and flexible service supply. Data viewing scope authority refers to the allocation and setting of the viewing scope authority of the data of each business subsystem function module in the system, for example: only the data created by oneself can be viewed, the data within the same department or several designated departments can be viewed, and the data within the same company and several branches and subsidiaries of the company can be viewed; Data operation permissions are the permission allocation dimension for each functional sub-module and menu within this product. The permission granularity can control the allocation and setting of specific page function permissions such as adding, deleting, modifying and querying each sub-business system functional module and menu.

[0025] In one embodiment of the present invention, the management user creates a common user account and allocates common user rights using the following scenarios: This platform has the function of creating common user accounts and assigning user system function permissions, data viewing range permissions, and data operation permissions. The management user account created by the tenant creates a new common user organization and account information, and assigns system function permissions, data viewing range permissions, and data operation permissions to the newly created user; System function permissions are the main carriers of data permissions and system permissions. According to the application needs of ordinary users, management users formulate exclusive system function permissions for each ordinary user to meet the diverse and flexible service supply of ordinary users. Data viewing scope authority refers to the allocation and setting of the viewing scope authority of the data of each business subsystem function module in the system, for example: only the data created by oneself can be viewed, the data within the same department or several designated departments can be viewed, and the data within the same company and several branches and subsidiaries of the company can be viewed; Data operation permissions are the permission allocation dimension for each functional sub-module and menu within this product. The permission granularity can control the allocation and setting of specific page function permissions such as adding, deleting, modifying and querying each sub-business system functional module and menu.

[0026] like Figure 2 As shown, these three roles can manage the next level of accounts and system data according to different data viewing scopes and functional permissions, so that user accounts of different roles can be uniformly configured and managed through this middle platform. The data information that the role account has permission to view, such as the unified setting of management organization departments, user accounts, regional permissions, system notifications, material templates and other functional applications.

[0027] like Figure 3 As shown in the figure, the data interaction and functional linkage process between the platform and other sub-business systems in this smart office system is described as follows: When the middle office system has a new scheduling task, the data interaction with other sub-business systems can usually be divided into three links: 1. Task preprocessing; 2. After preprocessing is completed, batch tasks begin to be executed; 3. Confirm the batch task status and update the task table status.

[0028] That is, between the middle platform and other sub-business systems ( Figure 3 Before the task starts, the middle station sends a message to the message queue processing service ( Figure 3The APP sends a message that a new task is about to be released (marked as EMQX on the top). EMQX forwards this message to the relevant APP. When the APP receives the message that the new task is about to be released, the APP performs internal preprocessing operations. After the preprocessing is ready, the APP sends a message to EMQX that I am ready to receive new tasks. EMQX forwards this message to the middle station. After receiving the message, the middle station starts to send new task-related data in batches to EMQX in the form of data packets. EMQX also receives the data packets sent by the middle station in batches and forwards them to the APP synchronously. The APP receives the task data sent by the middle station in batches and processes it until it is completely received and processed. Then, it sends the processing result to EMQX. EMQX forwards this result to the middle station. After receiving it, the middle station automatically updates the execution status of the task here. If the task processing result received fails, the middle station will resend the task. The resending process is as follows Figure 3 The business flow is consistent with the above three links; The method described in this process can solve the problem that when data is interacting between this middle platform and other sub-business systems, the batch of data being interacted will be synchronously interrupted after the task is interrupted due to an abnormality. By using this method, the abnormally interrupted task will be recorded by the middle platform of this smart office system and included in the interface message retransmission queue, and the batch of abnormally interacted data will continue to be transmitted after the subsequent system abnormality is recovered, thereby ensuring the integrity and stability of the interface data transmission between the middle platform of the smart office system and the connected sub-business system.

[0029] Furthermore, the code logic and field definitions related to this method are as follows: When creating a new task, go to the Tasks and TaskLogs tables. The default status of Tasks is status = pending, retry_count = 0, batch_no: the task includes the complete life cycle of retries, and the TaskLogs table is the actual single data packet to be pushed.

[0030] Start the scheduled task (scheduled once for each group), query the task, if there is a task in progress, interrupt the task and wait for the next task.

[0031] After starting the task, publish the topic: topic / before / {device ID} content:{"taskRule":"full / update / add","taskCount":100}, (TaskRule task rule, full full coverage, update update coverage, taskCount: batch task processing quantity).

[0032] APP subscribes to task rules, executes corresponding rules (delete, add, overwrite), and after processing, publishes the message with receipt, and subscribes to the middle office topic / app / before / {device ID},content:{"ok":true} After receiving the task rule pre-processing message ok=true, start content push, otherwise it will fail directly.

[0033] Content push publishing topic: topic / process / {device ID} / {task_type} / batch_no / task_id Message confirmation receipt: topic / process / app / {device ID} / {task_type} / batch_no / task_id Content:{"ok": true, "taskCount": 100, "failTask": "1,2,3"} When the number of messages processed by the App and tasksCount are both equal to 100, the message processing is completed and a success status is returned. If there is a failure record in failTask, enter the retry task.

[0034] The above generally describes the present invention in detail, but it is obvious to a person skilled in the art that some modifications or improvements can be made based on the present invention. Therefore, modifications or improvements that do not depart from the spirit of the present invention are within the scope of protection of the present invention.

Claims

1. Smart office system platform, characterized by: Includes a built-in super administrator account, which creates tenant accounts and assigns tenants system function permissions, data viewing scope permissions, and data operation permissions; Tenants create user accounts and assign corresponding permissions; The management user creates ordinary user accounts and assigns ordinary user permissions. Different roles manage the next level of accounts and system data according to different data viewing scopes and functional permissions, and implement unified configuration and management of data information that the role account has permission to view. When the system has new scheduling tasks, it interacts with other sub-business systems through three steps: task preprocessing, batch task execution, batch task status confirmation, and task table status update, to ensure the integrity and stability of interface data transmission.

2. The smart office system platform according to claim 1, characterized in that: System function permissions are the main carrier of data permissions and system permissions, and exclusive system function packages are formulated according to different user needs.

3. The smart office system platform according to claim 1, characterized in that: The data viewing scope permission is set to view only the data created by oneself, view the data within the same department or several designated departments, view the data within the same company and several branches and subsidiaries under the designated company.

4. The smart office system platform according to claim 1, characterized in that: Data operation permissions are controlled to the allocation and setting of specific page function permissions such as the addition, deletion, modification and query of each sub-business system function module and menu.

5. The smart office system platform according to claim 1, characterized in that: Different roles can use this middle platform to uniformly set up and manage organizational departments, user accounts, regional permissions, system notifications, material templates and other functional applications.

6. The smart office system platform according to claim 1, characterized in that: In the data interaction of the new scheduling task, the middle platform sends a new task message to the message queue processing service, and the message queue processing service forwards it to the relevant sub-business system.

7. The smart office system platform according to claim 6, characterized in that: After receiving the new task message, the sub-business system performs internal preprocessing operations. After the preprocessing is completed, it sends a message to the message queue processing service that it is ready to receive the new task.

8. The smart office system platform according to claim 6, characterized in that: After the middle station receives the message prepared by the sub-business system, it sends the new task-related data to the message queue processing service in batches in the form of data packets, and the message queue processing service synchronously forwards it to the sub-business system.

9. The smart office system platform according to claim 6, characterized in that: After processing the task data, the sub-business system sends the processing results to the message queue processing service, which forwards them to the middle station. After receiving the results, the middle station automatically updates the task execution status and resends the task if there is a failure.

10. The smart office system platform according to claim 9, characterized in that: When creating a new task, the task status and related information are recorded in the Tasks and TaskLogs tables. The default status of Tasks is status = pending, retry_count = 0, batch_no records the complete life cycle of the task, and the TaskLogs table is the actual single data packet to be pushed; start the scheduled task query task. If there is a task being processed in the in_progress status, the task is interrupted and waits for the next task; after starting the task, publish a specific topic and content, the sub-business system subscribes to the task rules to execute the corresponding rules, and receives a receipt for the published message. After the middle station subscribes to the receipt message, it starts to execute content push; content push publishes a specific topic and message confirmation receipt. When the App processes the number of messages that meet the task requirements, it returns a successful status. If there is a failure record, it enters the retry task.

Images