WO2024067161A1 - 一种通过5g消息实现无app化移动办公的方法 - Google Patents

一种通过5g消息实现无app化移动办公的方法 Download PDF

Info

Publication number
WO2024067161A1
WO2024067161A1 PCT/CN2023/119043 CN2023119043W WO2024067161A1 WO 2024067161 A1 WO2024067161 A1 WO 2024067161A1 CN 2023119043 W CN2023119043 W CN 2023119043W WO 2024067161 A1 WO2024067161 A1 WO 2024067161A1
Authority
WO
WIPO (PCT)
Prior art keywords
business
message
office
downlink
execution engine
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/119043
Other languages
English (en)
French (fr)
Inventor
王斌
杨戉
盛振明
夏建明
颜凤辉
赵磊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Digital Intelligence Technology Co Ltd
Original Assignee
China Telecom Digital Intelligence Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Telecom Digital Intelligence Technology Co Ltd filed Critical China Telecom Digital Intelligence Technology Co Ltd
Publication of WO2024067161A1 publication Critical patent/WO2024067161A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/903—Querying
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/34—Graphical or visual programming
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/1091—Recording time for administrative or management purposes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present invention belongs to the technical field of mobile office, and specifically relates to a method for realizing APP-free mobile office through 5G messages.
  • the technical problem to be solved by the present invention is to provide a method for realizing APP-free mobile office through 5G messages in view of the shortcomings of the above-mentioned prior art.
  • the 5G message system realizes the expansion of information such as pictures, videos, voices, and geographic locations, which can facilitate the uplink and downlink of data.
  • the MAAP message in the 5G message supports floating menus and multi-card functions, which is convenient for users to directly select. Therefore, it can conveniently support most mobile office needs, such as clocking in and out of get off work, employees uploading such as leave, reimbursement, various to-do reminders, approval functions, group chats, and company information release.
  • the mobile phone accesses the operator's 5G message system, and the operator's 5G message system is in storage and forwarding mode.
  • the 5G message finally received by the enterprise has a source IP of the operator's 5G message system. Therefore, the enterprise only needs to use a simple IP whitelist at the Internet entrance to prevent most attacks, which is safer.
  • the user's mobile phone number cannot be easily counterfeited, which is equivalent to pre-authentication, preventing the possibility of password theft such as dragging the database.
  • a large number of new functions only require low-code orchestration on the enterprise side, without any front-end upgrades.
  • the post-payment function ensures that employees do not need to pay when using 5G messages, but the enterprise will make a unified settlement. It can be seen that the migration of mobile office systems to 5G messages takes into account security, economy, and convenience.
  • the technical solution adopted by the present invention is:
  • a method to achieve APP-free mobile office through 5G messaging requires internal deployment within the company:
  • the chatbot server serves as a bridge between 5G messages and the company's office server;
  • a low-code front-end editor that provides a visual interface to simplify editing business rules
  • the business database is used to store business rules and describe how to conduct office business through various sub-modules of 5G messages.
  • the administrator first needs to build and edit the business logic and downlink 5G message template in the low-code front end according to the office business logic.
  • the front end generates business rules and downlink 5G message templates based on user input and stores them in the business database.
  • the chatbot reads data from the business database when it starts. For emergency business, the chatbot also supports hot updates to update incremental data from the business database.
  • the chatbot server includes:
  • MAAP gateway is used to communicate with the operator's internal MAAP system. For uplink messages, it is necessary to extract the mobile phone number and user information (including text, coordinates, or uploaded file addresses); for downlink notifications, it is necessary to transmit them to the operator's 5G message system;
  • LDAP gateway used to access the corporate address book and authenticate employee identities based on the mobile phone numbers carried in uplink 5G messages;
  • the NLP analysis module is used to identify user input to the corresponding office business function and locate key information as business parameters;
  • the multi-message packaging module is used to aggregate and package multiple consecutive messages
  • API Gateway used to establish HTTP connections to the backend office server for uplink messages and HTTP connections to the receiving office server for downlink notifications
  • Downlink template used to render service data into MAAP messages in standard format
  • the rule execution engine is the core of the entire system. When it starts, it calls all rules and message templates from the business database, then receives uplink messages from the MAAP interface, receives downlink notifications from the API gateway, and calls the modules in the chatbot to complete the mobile office process.
  • the attributes of the rule including whether it is upstream or downstream, rule keywords, and rule parameters;
  • NLP analysis module which is the original text information sent by the user
  • Multi-message packaging module including the results of NLP analysis, uplink images, videos and geographic location coordinates sent by users, etc.
  • API Gateway which is the URL of the office server (different services have different URLs) and input parameters;
  • the following template contains the template index and the actual value of the template variable.
  • MAAP gateway for user mobile phone numbers and 5G messages generated through downlink templates
  • the process usually includes the following steps:
  • Step 1 The employee uses the 5G messaging function on the mobile phone to send one or more uplink 5G messages to the company chatbot number;
  • Step 2 This 5G message reaches the MAAP gateway of the company's chatbot module through the operator's 5G message system;
  • Step 3 The MAAP gateway extracts the employee's mobile phone number from the MAAP message, queries the company address book through the LDAP gateway, and performs user authentication;
  • Step 4 After authentication, the MAAP gateway hands the 5G text message to the rule execution engine;
  • Step 5 The rule execution engine sends the 5G text message to the NLP module, obtains the business keywords and business parameters, and then searches for business rules based on the business keywords;
  • Step 6 The rule execution engine packages multiple messages sent by the user according to the business rules
  • Step 7 The rule execution engine may need to combine the business data with the downlink template according to the business rules to generate a 5G card message with a floating menu;
  • Step 8 The rule execution engine sends this card message to the user's mobile phone through the operator's 5G message system according to the business rules. After the user confirms, a new 5G message is generated and sent up to the rule execution engine;
  • Step 9 The rule execution engine confirms the end of the business process based on the business rules and sends all data to the service interface of the company's office server through the API gateway.
  • the method generally includes the following steps:
  • Step 1 The office server calls the API gateway and passes in the business type and business parameters;
  • Step 2 The API gateway notifies the rule execution engine and passes in the business type and business parameters;
  • Step 3 The rule execution engine searches for the required downlink template according to the business rules, and then combines the business parameters with the downlink template to generate a 5G card message with a floating menu;
  • Step 4 The rule execution engine sends the card message to the user's mobile phone through the MAAP gateway and the operator's 5G message system according to the business rules;
  • a separate uplink 5G text message is actually sent.
  • the content of the message is a special text message customized by the chatbot, which can directly encapsulate business keywords and business parameters. It can be directly recognized by the rule execution engine without NLP recognition and sent directly to the office server through the API gateway.
  • This method requires the deployment of a chatbot server, a business database, and a low-code front-end editor within the company: the chatbot is a bridge between the 5G message and the company's office server; the business database is used to store business rules, describing how to use each sub-module of the 5G message. Conduct office business, and downlink 5G message templates are used to describe the format of downlink 5G messages and the required variables; the low-code front-end editor is used to provide a visual interface to simplify the editing of business rules and downlink templates.
  • chatbot server When the chatbot server starts, all rules and message templates are transferred from the business database, and then uplink messages are received from the operator's 5G message system, downlink notifications are received from the office server, and then various internal functions are called according to business rules to complete the process of mobile office through 5G messages.
  • FIG. 1 is a schematic diagram of the method of the present invention.
  • FIG2 is a schematic diagram of an uplink message.
  • FIG3 is a schematic diagram of a downlink notification.
  • the present invention provides a method for realizing APP-free mobile office through 5G messaging, which needs to be deployed within the company:
  • the chatbot server serves as a bridge between 5G messages and the company's office server;
  • a low-code front-end editor that provides a visual interface to simplify editing business rules
  • the business database is used to store business rules and describe how to conduct office business through various sub-modules of 5G messages.
  • the administrator first needs to build and edit business logic and downlink 5G message templates in the low-code front end according to the office business logic.
  • the front end generates business rules and downlink 5G message templates based on user input and stores them in the business database.
  • the chatbot reads data from the business database when it starts. For emergency business, the chatbot also supports hot updates to update incremental data from the business database.
  • the chatbot server includes:
  • MAAP gateway is used to communicate with the operator's internal MAAP system. For uplink messages, it is necessary to extract the mobile phone number and user information (including text, coordinates, or uploaded file addresses); for downlink notifications, it is necessary to transmit them to the operator's 5G message system;
  • LDAP gateway used to access the corporate address book and authenticate employee identities based on the mobile phone numbers carried in uplink 5G messages;
  • the NLP analysis module is used to identify user input to the corresponding office business function and locate key information as business parameters;
  • the multi-message packaging module is used to aggregate and package multiple consecutive messages
  • API Gateway used to establish HTTP connections to the backend office server for uplink messages and HTTP connections to the receiving office server for downlink notifications
  • Downlink template used to render service data into MAAP messages in standard format
  • the rule execution engine is the core of the entire system. When it starts, it calls all rules and message templates from the business database, then receives uplink messages from the MAAP interface, receives downlink notifications from the API gateway, and calls the modules in the chatbot to complete the mobile office process.
  • the attributes of the rule including whether it is upstream or downstream, rule keywords, and rule parameters;
  • NLP analysis module which is the original text information sent by the user
  • Multi-message packaging module including the results of NLP analysis, uplink images, videos and geographic location coordinates sent by users, etc.
  • API Gateway which is the URL of the office server (different services have different URLs) and input parameters;
  • the following template contains the template index and the actual value of the template variable.
  • MAAP gateway for user mobile phone numbers and 5G messages generated through downlink templates
  • the process generally includes the following steps:
  • Step 1 The employee uses the 5G messaging function on the mobile phone to send one or more uplink 5G messages to the company chatbot number;
  • Step 2 This 5G message reaches the MAAP gateway of the company's chatbot module through the operator's 5G message system;
  • Step 3 The MAAP gateway extracts the employee's mobile phone number from the MAAP message, queries the company address book through the LDAP gateway, and performs user authentication;
  • Step 4 After authentication, the MAAP gateway hands the 5G text message to the rule execution engine;
  • Step 5 The rule execution engine sends the 5G text message to the NLP module, obtains the business keywords and business parameters, and then searches for business rules based on the business keywords;
  • Step 6 The rule execution engine packages multiple messages sent by the user according to the business rules
  • Step 7 The rule execution engine may need to combine the business data with the downlink template according to the business rules to generate a 5G card message with a floating menu;
  • Step 8 The rule execution engine sends this card message to the user's mobile phone through the operator's 5G message system according to the business rules. After the user confirms, a new 5G message is generated and sent up to the rule execution engine;
  • Step 9 The rule execution engine confirms the end of the business process based on the business rules and sends all data to the service interface of the company's office server through the API gateway.
  • the method generally includes the following steps:
  • Step 1 The office server calls the API gateway and passes in the business type and business parameters;
  • Step 2 The API gateway notifies the rule execution engine and passes in the business type and business parameters;
  • Step 3 The rule execution engine searches for the required downlink template according to the business rules, and then combines the business parameters with the downlink template to generate a 5G card message with a floating menu;
  • Step 4 The rule execution engine sends the card message to the user's mobile phone through the MAAP gateway and the operator's 5G message system according to the business rules;
  • a separate uplink 5G text message is actually sent.
  • the content of the message is a special text message customized by the chatbot, which can directly encapsulate business keywords and business parameters. It can be directly recognized by the rule execution engine without NLP recognition and sent directly to the office server through the API gateway.
  • the administrator generates through the low-code front end:
  • attributes include uplink, keyword is leave, business parameters are time, reason, picture; the calling order is NLP analysis, multi-message packaging, downlink template, MAAP interface, button selection, API gateway.
  • ⁇ Downline template used to let users confirm whether the business is correct.
  • the template contains the company logo, fixed text, template variables such as user name, reason, time, picture, and contains two buttons to confirm and cancel.
  • This business rule and the downstream template will be stored in the business database.
  • Chatbot When Chatbot starts, it loads the data in the business database.
  • the MAAP gateway extracts the employee’s mobile phone number from the MAAP message, queries the company address book through the LDAP gateway, and performs user authentication.
  • the MAAP gateway passes the data to the rule execution engine.
  • the rule execution engine sends the employee's 5G text message to the NLP module.
  • NLP recognizes that the business keyword is leave, the time in the business parameter is tomorrow, and the reason is fighting illness.
  • the result is returned to the rule execution engine, and the rule execution engine finds the business rules based on the business keywords.
  • the rule execution engine recognizes that the picture belongs to the business parameters required by the rules after receiving it according to the business rules. Therefore, it packages the picture information into multiple messages and uses it as the picture parameter of the leave business.
  • the rule execution engine queries the required downstream template according to the business rules, combines the business parameters with the downstream template, and generates a 5G card message with a floating menu for the user to confirm the information.
  • the text in the message is "Dear A, you have applied for leave. The leave time is tomorrow. The reason is to see a doctor.
  • the attached picture is the certificate you uploaded"; the picture in the message is the picture uploaded by the user; the buttons in the message are confirmation and cancel.
  • the uplink message corresponding to the first confirmation button is "!@# ⁇ Leave--Confirm---MD5"
  • the uplink message corresponding to the second rejection button is "!@# ⁇ Leave--Cancel-MD5".
  • the rule execution engine sends the card message to the operator's 5G message system through the MAAP interface according to the business rules, and finally sends it to the user's mobile phone. After the user clicks the confirmation button, a new 5G message will be automatically generated and sent to the rule execution engine in a similar way to step 3.
  • the rule execution engine recognizes that this is an uplink message formed by clicking the button based on "!@# ⁇ ", directly extracts the business keywords, business parameters and MD5, and calculates MD5 again to prevent attacks.
  • Rule execution follows business rules, confirms the end of the business process, and sends all data to the leave interface of the office server through the API gateway.
  • the administrator generates through the low-code front end:
  • the business rule attributes include downlink, the keyword is leave approval, and the business parameters are transaction id, leader name, leader mobile phone number, employee name, time, reason, and picture.
  • the calling order is downlink template, MAAP interface, button confirmation, API gateway;
  • Downward template used for leaders to review and approve.
  • the template contains the company logo, fixed text, and template variables for all business parameters, including two buttons: Agree and Reject.
  • Chatbot When Chatbot starts, it loads data from the business database
  • the office server calls the leave approval interface in the API gateway and passes in business parameters;
  • the API gateway passes the business keyword "leave approval" and all input parameters to the rule execution engine
  • the rule execution engine searches for business rules based on business keywords, searches for downlink templates based on business rules, and generates a downlink 5G message.
  • the message text is "Dear XX, your subordinate A has applied for leave business. The leave time is tomorrow. The reason is to see a doctor.
  • the attached picture is the uploaded certificate.”
  • the message picture is the picture uploaded by the employee.
  • the message contains two buttons.
  • the uplink message corresponding to the first approval button is "!@# ⁇ Leave approval--transaction id, agree--MD5"
  • the uplink message corresponding to the second rejection button is "!@# ⁇ Leave approval--transaction id, reject--MD5".
  • "!@# ⁇ ” is the button click behavior recognition keyword, which can be customized.
  • "Leave approval” is the business keyword
  • "transaction id, reject” is the business parameter
  • MD5 is the MD5 calculation of the business keyword, business parameter and an internal key to prevent malicious attacks.
  • the rule execution engine sends the message to the leader’s mobile phone according to the business rules
  • the rule execution engine recognizes that this is an uplink message generated by clicking a button based on “!@# ⁇ ”, directly extracts the business keywords, business parameters and MD5, and calculates MD5 again to prevent attacks;
  • the approval record results will be sent to the office server through the API gateway according to business rules.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • General Business, Economics & Management (AREA)
  • Databases & Information Systems (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computational Linguistics (AREA)
  • Educational Administration (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种通过5G消息实现无APP化移动办公的方法，在公司内部部署：chatbot服务器，作为5G消息系统和公司办公服务器的桥梁；低代码前端编辑器，用于提供一个可视化界面，简化业务规则和下行模板的编辑；业务数据库，用于存放业务规则以及下行5G消息模板，业务规则用于描述如何通过5G消息系统的各个子模块进行办公业务，下行5G消息模板用于描述下行5G消息的格式和所需要的变量。

Description

一种通过5G消息实现无APP化移动办公的方法 技术领域
本发明属于移动办公技术领域，具体涉及一种通过5G消息实现无APP化移动办公的方法。
背景技术
当前在手机上进行移动办公通常需要使用APP，且不使用VPN，这样就相当于将公司办公服务器直接暴露在互联网上，很容易受到各种攻击。由于苹果和安卓系统的差异，前端APP需要开发两套代码，或者通过套用第三方框架实现兼容，但是执行效率有所降低。同时移动办公大部分需要处理的事务相对比较固定，可以考虑用5G消息替代。
发明内容
本发明所要解决的技术问题是针对上述现有技术的不足，提供一种通过5G消息实现无APP化移动办公的方法。5G消息系统在传统短信发送文字的基础上，实现了图片，视频，语音，地理位置等信息的扩展，可以方便实现资料的上下行。5G消息中的MAAP消息支持悬浮菜单和多卡片功能，方便用户直接进行选择。因此可以方便的支持大部分移动办公的需求，如上下班手机打卡、员工上传类如请假，报销、各类待办提醒、审批功能、群聊、公司信息发布。同时不同手机遵循同样的5G消息协议和格式，企业不用考虑平台的差异性，从而节约了前端的开发费用。手机接入运营商5G消息系统，运营商5G消息系统为存储转发模式，企业最终收到的5G消息，其源IP为运营商5G消息系统，因此企业在互联网入口处只需要使用简单的IP白名单，就能防止大部分攻击，更加安全。用户的手机号无法简单仿冒，相当于进行了预认证，防止了拖库等密码失窃的可能。大量新功能只需要在企业端进行低代码方式的编排，不需要前端进行任何升级。后向付费功能保证了员工在使用5G消息时无需付费，而是由企业进行统一结算。可见移动办公系统迁移到5G消息，兼顾了安全性，经济型，便利性。
为实现上述技术目的，本发明采取的技术方案：
一种通过5G消息实现无APP化移动办公的方法，需要为在于公司内部部署：
chatbot服务器，作为5G消息和公司办公服务器的桥梁；
低代码前端编辑器，用于提供一个可视化界面，简化业务规则的编辑；
业务数据库，用于存放业务规则，描述如何通过5G消息各个子模块进行办公业务。
进一步优选地，管理员首先需要根据办公业务逻辑在低代码前端构建和编辑业务逻辑和下行5G消息模板，前端根据用户输入生成业务规则和下行5G消息模板，存入业务数据库，chatbot在启动时从业务数据库读取数据，对于紧急业务chatbot也支持热更新，从业务数据库更新增量数据。
所述chatbot服务器包括：
MAAP网关，用于与运营商内部MAAP系统通信，对于上行消息，需要提取出手机号码，用户信息(包含文本，或者坐标，或者上传文件地址)；对于下行通知，需要将其传输给运营商的5G消息系统；
LDAP网关，用于访问企业通讯录，根据上行5G消息携带的手机号码认证员工身份；
NLP分析模块，用于将用户输入识别到对应办公业务功能，并定位出关键信息，作为业务参数；
多消息打包模块，用于将多个前后相连的消息进行汇总打包；
API网关，用于对于上行消息建立到后台办公服务器的HTTP连接，对于下行通知接收办公服务器的HTTP连接；
下行模板，用于将业务数据渲染为标准格式的MAAP消息；
规则执行引擎是整个系统的核心，启动时从业务数据库调入所有规则和消息模板，之后从MAAP接口接收上行消息，从API网关接收下行通知，并调用chatbot内的模块完成移动办公流程。
业务规则需要描述：
规则的属性，包含上行还是下行，规则关键字，规则参数；
内部模块调用顺序，注意在一个流程中，一个模块可能需要被调用多次；
内部模块调用时的入参：
NLP分析模块，为用户发送的原始文本信息；
多消息打包模块，为NLP分析的结果，用户发送的上行图像，视频和地理位置坐标等；
API网关，为办公服务器的URL(不同业务，URL不同)和入参；
下行模板，为模板索引和模板变量的实际值
MAAP网关，为用户手机号和通过下行模板生成的5G消息；
对于用户上行业务，流程通常包括以下步骤：
步骤1.员工通过手机的5G消息功能，向公司chatbot号码发送一条或者多条上行5G消息；
步骤2.此5G消息，通过运营商5G消息系统，到达公司chatbot模块的MAAP网关；
步骤3.MAAP网关从MAAP报文中提取出员工手机号，通过LDAP网关，查询公司通讯录，进行用户认证；
步骤4.认证通过后，MAAP网关将5G文本消息交给规则执行引擎；
步骤5.规则执行引擎，将5G文本消息发送到NLP模块，获取业务关键字和业务参数，再根据业务关键字查找业务规则；
步骤6.规则执行引擎根据业务规则，对用户发送的多条消息进行多消息打包；
步骤7.规则执行引擎根据业务规则，可能需要将业务数据结合下行模板，生成一条带悬浮菜单5G卡片消息；
步骤8.规则执行引擎根据业务规则，将此卡片消息通过运营商5G消息系统下发到用户手机，用户进行确认后生成一条新的5G消息并上行到规则执行引擎；
步骤9.规则执行引擎根据业务规则，确认业务流程结束，将所有数据通过API网关发送到公司办公服务器的服务接口。
对于办公系统下行通知，参考图3，所述方法通常包括以下步骤：
步骤1.办公服务器调用API网关，传入业务类型和业务参数；
步骤2.API网关通知规则执行引擎，传入业务类型和业务参数；
步骤3.规则执行引擎根据业务规则，查找需要的下行模板，再将业务参数结合下行模板，生成一条带悬浮菜单5G卡片消息；
步骤4.规则执行引擎根据业务规则，将此卡片消息通过MAAP网关，经过运营商5G消息系统下发到用户手机；
用户在5G消息中点击按钮后，实际是发送了一条单独的上行5G文本消息，其内容是在chatbot自定义的一个特殊文本消息，可以直接封装业务关键字和业务参数，不需要进行NLP识别就可以直接被规则执行引擎识别，并且直接通过API网关送到办公服务器。
本发明具有以下有益效果：
大大提高了安全性，经济型，便利性。用户不需要使用办公APP，而是通过5G消息中的MAAP系统，使用5G消息进行各项办公业务；同时公司办公系统置于chatbot后，不需要在互联网暴露接口，公司在互联网入口处对运营商5G消息系统设置IP白名单，检测通过后允许运营商5G消息系统中的MAAP平台向部署于公司的chatbot系统发送5G消息。此方法需要在公司内部部署chatbot服务器，业务数据库和低代码前端编辑器：chatbot是5G消息和公司办公服务器的桥梁；业务数据库用于存放业务规则，描述如何通过5G消息各个子模块 进行办公业务，以及下行5G消息模板，用于描述下行5G消息的格式和所需要的变量；低代码前端编辑器用于提供一个可视化界面，简化业务规则和下行模板的编辑。chatbot服务器启动时从业务数据库调入所有规则和消息模板，之后从运营商5G消息系统接收上行消息，从办公服务器接收下行通知，再根据业务规则调用内部各个功能，完成通过5G消息进行移动办公的流程。
附图说明
图1为本发明方法原理图。
图2为上行消息示意图。
图3为下行通知示意图。
具体实施方式
如图1所示，本发明一种通过5G消息实现无APP化移动办公的方法，需要为在于公司内部部署：
chatbot服务器，作为5G消息和公司办公服务器的桥梁；
低代码前端编辑器，用于提供一个可视化界面，简化业务规则的编辑；
业务数据库，用于存放业务规则，描述如何通过5G消息各个子模块进行办公业务。
管理员首先需要根据办公业务逻辑在低代码前端构建和编辑业务逻辑和下行5G消息模板，前端根据用户输入生成业务规则和下行5G消息模板，存入业务数据库，chatbot在启动时从业务数据库读取数据，对于紧急业务chatbot也支持热更新，从业务数据库更新增量数据。
所述chatbot服务器包括：
MAAP网关，用于与运营商内部MAAP系统通信，对于上行消息，需要提取出手机号码，用户信息(包含文本，或者坐标，或者上传文件地址)；对于下行通知，需要将其传输给运营商的5G消息系统；
LDAP网关，用于访问企业通讯录，根据上行5G消息携带的手机号码认证员工身份；
NLP分析模块，用于将用户输入识别到对应办公业务功能，并定位出关键信息，作为业务参数；
多消息打包模块，用于将多个前后相连的消息进行汇总打包；
API网关，用于对于上行消息建立到后台办公服务器的HTTP连接，对于下行通知接收办公服务器的HTTP连接；
下行模板，用于将业务数据渲染为标准格式的MAAP消息；
规则执行引擎是整个系统的核心，启动时从业务数据库调入所有规则和消息模板，之后从MAAP接口接收上行消息，从API网关接收下行通知，并调用chatbot内的模块完成移动办公流程。
业务规则需要描述：
规则的属性，包含上行还是下行，规则关键字，规则参数；
内部模块调用顺序，注意在一个流程中，一个模块可能需要被调用多次；
内部模块调用时的入参：
NLP分析模块，为用户发送的原始文本信息；
多消息打包模块，为NLP分析的结果，用户发送的上行图像，视频和地理位置坐标等；
API网关，为办公服务器的URL(不同业务，URL不同)和入参；
下行模板，为模板索引和模板变量的实际值
MAAP网关，为用户手机号和通过下行模板生成的5G消息；
如图2所示，对于用户上行业务，流程通常包括以下步骤：
步骤1.员工通过手机的5G消息功能，向公司chatbot号码发送一条或者多条上行5G消息；
步骤2.此5G消息，通过运营商5G消息系统，到达公司chatbot模块的MAAP网关；
步骤3.MAAP网关从MAAP报文中提取出员工手机号，通过LDAP网关，查询公司通讯录，进行用户认证；
步骤4.认证通过后，MAAP网关将5G文本消息交给规则执行引擎；
步骤5.规则执行引擎，将5G文本消息发送到NLP模块，获取业务关键字和业务参数，再根据业务关键字查找业务规则；
步骤6.规则执行引擎根据业务规则，对用户发送的多条消息进行多消息打包；
步骤7.规则执行引擎根据业务规则，可能需要将业务数据结合下行模板，生成一条带悬浮菜单5G卡片消息；
步骤8.规则执行引擎根据业务规则，将此卡片消息通过运营商5G消息系统下发到用户手机，用户进行确认后生成一条新的5G消息并上行到规则执行引擎；
步骤9.规则执行引擎根据业务规则，确认业务流程结束，将所有数据通过API网关发送到公司办公服务器的服务接口。
如图3所示，对于办公系统下行通知，参考图3，所述方法通常包括以下步骤：
步骤1.办公服务器调用API网关，传入业务类型和业务参数；
步骤2.API网关通知规则执行引擎，传入业务类型和业务参数；
步骤3.规则执行引擎根据业务规则，查找需要的下行模板，再将业务参数结合下行模板，生成一条带悬浮菜单5G卡片消息；
步骤4.规则执行引擎根据业务规则，将此卡片消息通过MAAP网关，经过运营商5G消息系统下发到用户手机；
用户在5G消息中点击按钮后，实际是发送了一条单独的上行5G文本消息，其内容是在chatbot自定义的一个特殊文本消息，可以直接封装业务关键字和业务参数，不需要进行NLP识别就可以直接被规则执行引擎识别，并且直接通过API网关送到办公服务器。
实施例
以下结合两个具体办公流程对实施例作进一步详细描述。
员工请假流程，包括：
1.管理员通过低代码前端生成：
●业务规则，属性包括上行，关键字为请假，业务参数为时间，原因，图片；调用顺序为NLP分析，多消息打包，下行模板，MAAP接口，按钮选择，API网关。
●下行模板，用于让用户确认业务是否正确，模板中包含公司标识，固定文字，模板变量为用户名字，原因，时间，图片，包含两个按钮确认和取消。
这条业务规则和下行模板都会存储至业务数据库中。
2.Chatbot在启动时，将业务数据库中的数据载入。
3.员工甲在手机上向公司chatbot号码发送一条5G文本消息“我明天因为去看病请假一天”，又截屏了一个医院预约单作为图片发送给chatbot号码。这条消息通过运营商5G消息系统，到达公司的chatbot功能中的MAAP网关。
4.MAAP网关从MAAP报文中提取出员工手机号，通过LDAP网关，查询公司通讯录，进行用户认证。
5.认证成功后，MAAP网关将数据交给规则执行引擎。
6.规则执行引擎将员工5G文本消息发送到NLP模块，NLP识别到业务关键字为请假，业务参数中的时间为明天，原因为抗病，将结果返回至规则执行引擎，规则执行引擎根据业务关键字查找到业务规则。
7.因为文字和图片是分为两条5G消息到达的，规则执行引擎按照业务规则，在收到图片后，识别到其属于规则中需要的业务参数，因此通过多消息打包，将图片信息作为请假业务的图片参数。
8.规则执行引擎按照业务规则，查询到所需的下行模板，将业务参数结合下行模板，生成一条带悬浮菜单5G卡片消息，让用户进行信息确认。消息中的文字为“亲爱的甲，您已申请请假业务，请假时间为明天，原因为看病，附图为您上传的证明”；消息中的图片为用户上传图片；消息中的按钮为确认和取消。第一个确认按钮对应的上行消息为“！@#￥请假--确认--MD5”，第二个拒绝按钮对应的上行消息为“！@#￥请假--取消-MD5”。“！@#￥”为按钮点击行为识别关键字，可以自定义，“请假”为业务关键字，“确认”/“取消”为业务参数，MD5为将业务关键字，业务参数和一个内部key进行MD5计算，防止恶意攻击。
9.规则执行引擎按照业务规则，将卡片消息通过MAAP接口，送达运营商5G消息系统，最后下发到用户手机，用户点击确认按钮后，会自动生成一条新的5G消息，类似步骤3上行到规则执行引擎。规则执行引擎根据“！@#￥”识别到此是通过点击按钮形成的上行消息，直接提取业务关键字，业务参数和MD5，再次计算MD5防止攻击。
10.规则执行按照业务规则，确认业务流程结束，将所有数据通过API网关发送到办公服务器的请假接口。
对于审批流程，
1.管理员通过低代码前端生成：
业务规则属性包含下行，关键字为请假审批，业务参数为事务id，领导姓名，领导手机号，员工姓名，时间，原因，图片。调用顺序为下行模板，MAAP接口，按钮确认，API网关；
下行模板，用于让领导进行审批，模板中包含公司标识，固定文字，模板变量为所有的业务参数，包含两个按钮同意和拒绝；
2.Chatbot在启动时，将业务数据库中的数据载入；
3.办公服务器调用API网关中的请假审批接口，传入业务参数；
4.API网关向规则执行引擎传递业务关键字为请假审批，和全部入参；
5.规则执行引擎根据业务关键字，查找业务规则，根据业务规则，查找下行模板，生成一条下行5G消息。消息文字为“亲爱的XX，您的下属甲已申请请假业务，请假时间为明天，原因为看病，附图为上传的证明”。消息图片为员工上传图片。消息包含两个按钮，第一个同意按钮对应的上行消息为“！@#￥请假审批--事务id，同意--MD5”，第二个拒绝按钮对应的上行消息为“！@#￥请假审批--事务id，拒绝--MD5”。“！@#￥”为按钮点击行为识别关键字，可以自定义，“请假审批”为业务关键字，“事务id，拒绝”为业务参数，MD5为将业务关键字，业务参数和一个内部key进行MD5计算，防止恶意攻击。
6.规则执行引擎根据业务规则，则将此消息送到领导手机；
7.领导点击同意按钮，自动上行一条5G消息“！@#￥请假审批--事务id，同意--MD5”，经过运营商5G消息系统，chatbot的MAAP接口到达规则执行引擎；
8.规则执行引擎根据“！@#￥”识别到此是通过点击按钮形成的上行消息，直接提取业务关键字，业务参数和MD5，再次计算MD5防止攻击；
9.检验合格后，再通过业务规则，经API网关，将审批记结果发送至办公服务器。
以上仅是本发明的优选实施方式，本发明的保护范围并不仅局限于上述实施例，凡属于本发明思路下的技术方案均属于本发明的保护范围。应当指出，对于本技术领域的普通技术人员来说，在不脱离本发明原理前提下的若干改进和润饰，应视为本发明的保护范围。

Claims (9)

  1. 一种通过5G消息实现无APP化移动办公的方法，其特征在于，在公司内部部署：
    chatbot服务器，作为5G消息系统和公司办公服务器的桥梁；
    低代码前端编辑器，用于提供一个可视化界面，简化业务规则和下行模板的编辑；
    业务数据库，用于存放业务规则以及下行5G消息模板，其中，业务规则用于描述如何通过5G消息系统各个子模块进行办公业务，下行5G消息模板用于描述下行5G消息的格式和所需要的变量。
  2. 根据权利要求1所述的一种通过5G消息实现无APP化移动办公的方法，其特征在于，管理员首先根据公司办公系统业务逻辑在低代码前端编辑器构建和编辑业务逻辑和下行5G消息模板，低代码前端编辑器根据用户输入生成业务规则和下行5G消息模板，存入业务数据库，chatbot服务器在启动时从业务数据库读取数据，对于紧急业务chatbot服务器也支持热更新，从业务数据库更新增量数据。
  3. 根据权利要求1所述的一种通过5G消息实现无APP化移动办公的方法，其特征在于，所述chatbot服务器包括：
    MAAP网关，用于与运营商5G消息系统内部的MAAP系统通信；
    LDAP网关，用于访问企业通讯录，使用LDAP协议通过5G消息携带的手机号码进行员工身份的认证；
    NLP分析模块，分析用户上行消息，识别业务类型和业务参数；
    多消息打包模块，用于将多个前后相连的消息进行汇总打包；
    API网关，与办公服务器进行通信，处理上行请求和下行通知；
    下行模板，用于将业务数据根据模板渲染为标准格式的5G消息；
    规则执行引擎，启动时从业务数据库调入所有规则和消息模板，之后从MAAP接口接收上行消息，从API网关接收下行通知，并调用chatbot服务器内各个模块完成移动办公流程。
  4. 根据权利要求1-3任一所述的一种通过5G消息实现无APP化移动办公的方法，其特征在于，业务规则包括：
    规则的属性，包含上行还是下行，规则关键字，规则参数；
    内部模块调用顺序，一个流程中，一个模块可能需要被调用多次；
    内部模块调用时的入参，具体的；
    对于NLP分析模块，为用户发送的原始文本信息；
    对于多消息打包模块，为NLP分析的结果或者用户发送的上行图像、视频和地理位置坐标；
    对于API网关，为办公服务器的URL和入参；
    对于下行模板，为模板索引和模板变量的实际值；
    对于MAAP网关，为用户手机号和通过下行模板生成的5G消息。
  5. 根据权利要求1所述的一种通过5G消息实现无APP化移动办公的方法，其特征在于，员工手机和公司chatbot服务器都连接到运营商5G消息系统；
    员工手机不下载APP，只使用内置的5G消息功能，通过运营商5G消息系统，使用公司办公功能；
    公司办公系统置于chatbot服务器后，不在互联网暴露接口，在互联网入口处对运营商5G消息系统设置IP白名单，检测通过后允许运营商5G消息系统中的MAAP平台向chatbot服务器发送5G消息。
  6. 根据权利要求1-4任一所述的一种通过5G消息实现无APP化移动办公的方法，其特征在于，对于用户上行业务，所述方法包括以下步骤：
    步骤1.员工通过手机的5G消息功能，向公司chatbot号码发送一条或者多条上行5G消息；
    步骤2.对于步骤1发送的5G消息，通过运营商5G消息系统，到达公司chatbot服务器的MAAP网关；
    步骤3.MAAP网关从5G消息报文中提取出员工手机号，通过LDAP网关，查询公司通讯录，进行用户认证；
    步骤4.认证通过后，MAAP网关将5G文本消息交给规则执行引擎；
    步骤5.规则执行引擎，将5G文本消息发送到NLP模块，获取业务关键字和业务参数，再根据业务关键字查找业务规则；
    步骤6.规则执行引擎根据业务规则，对用户发送的多条消息进行多消息打包；
    步骤7.规则执行引擎根据业务规则，将业务数据结合下行模板，生成一条带悬浮菜单5G卡片消息；
    步骤8.规则执行引擎根据业务规则，将所述卡片消息通过运营商5G消息系统下发到用户手机，用户进行确认后生成一条新的5G消息并上行到规则执行引擎；
    步骤9.规则执行引擎根据业务规则，确认业务流程结束，将所有数据通过API网关发送到公司办公服务器的服务接口。
  7. 根据权利要求1-4任一所述的一种通过5G消息实现无APP化移动办公的方法，其特征在于，对于办公系统下行通知业务，所述方法包括以下步骤：
    步骤1.办公服务器调用API网关，传入业务类型和业务参数；
    步骤2.API网关通知规则执行引擎，传入业务类型和业务参数；
    步骤3.规则执行引擎根据业务类型查找业务规则，再根据业务规则查找需要的下行模板，将业务参数结合下行模板，生成一条带悬浮菜单5G卡片消息；
    步骤4.规则执行引擎根据业务规则，将所述卡片消息通过MAAP网关，经过运营商5G消息系统下发到用户手机。
  8. 根据权利要求1-4任一所述的一种通过5G消息实现无APP化移动办公的方法，其特征在于，用户在5G消息系统中点击按钮后，实际是发送了一条单独的上行5G文本消息，其内容是在chatbot自定义的一个特殊文本消息，可以直接封装业务关键字和业务参数，不需要进行NLP识别就可以直接被规则执行引擎识别，并且直接通过API网关送到办公服务器。
  9. 根据权利要求6所述的一种通过5G消息实现无APP化移动办公的方法，其特征在于，用户发送的消息可请求的服务包括：上下班手机打卡、员工上传类如请假，报销、各类待办提醒、审批、群聊和公司信息发布。
PCT/CN2023/119043 2022-09-27 2023-09-15 一种通过5g消息实现无app化移动办公的方法 Ceased WO2024067161A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211178662.9A CN115700685A (zh) 2022-09-27 2022-09-27 一种通过5g消息实现无app化移动办公的方法
CN202211178662.9 2022-09-27

Publications (1)

Publication Number Publication Date
WO2024067161A1 true WO2024067161A1 (zh) 2024-04-04

Family

ID=85120614

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/119043 Ceased WO2024067161A1 (zh) 2022-09-27 2023-09-15 一种通过5g消息实现无app化移动办公的方法

Country Status (2)

Country Link
CN (1) CN115700685A (zh)
WO (1) WO2024067161A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115700685A (zh) * 2022-09-27 2023-02-07 中电信数智科技有限公司 一种通过5g消息实现无app化移动办公的方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200114171A (ko) * 2019-03-27 2020-10-07 주식회사 팩앤롤 문서서식 기반 정보화 플랫폼 제공 장치
CN112527373A (zh) * 2020-12-11 2021-03-19 浪潮云信息技术股份公司 一种基于运行综合管理中心业务的可视化平台拓展方法
CN114115852A (zh) * 2021-11-30 2022-03-01 深圳壹账通智能科技有限公司 可视化服务编排方法、装置、设备及介质
CN114386938A (zh) * 2021-12-21 2022-04-22 南京欣网互联网络科技有限公司 一种5g消息平台的运营管理系统
CN114449458A (zh) * 2020-10-16 2022-05-06 中国移动通信集团浙江有限公司 一种5g消息回落方法、系统、计算设备和存储介质
CN115700685A (zh) * 2022-09-27 2023-02-07 中电信数智科技有限公司 一种通过5g消息实现无app化移动办公的方法

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20200114171A (ko) * 2019-03-27 2020-10-07 주식회사 팩앤롤 문서서식 기반 정보화 플랫폼 제공 장치
CN114449458A (zh) * 2020-10-16 2022-05-06 中国移动通信集团浙江有限公司 一种5g消息回落方法、系统、计算设备和存储介质
CN112527373A (zh) * 2020-12-11 2021-03-19 浪潮云信息技术股份公司 一种基于运行综合管理中心业务的可视化平台拓展方法
CN114115852A (zh) * 2021-11-30 2022-03-01 深圳壹账通智能科技有限公司 可视化服务编排方法、装置、设备及介质
CN114386938A (zh) * 2021-12-21 2022-04-22 南京欣网互联网络科技有限公司 一种5g消息平台的运营管理系统
CN115700685A (zh) * 2022-09-27 2023-02-07 中电信数智科技有限公司 一种通过5g消息实现无app化移动办公的方法

Also Published As

Publication number Publication date
CN115700685A (zh) 2023-02-07

Similar Documents

Publication Publication Date Title
US11768951B2 (en) Systems and methods of gesture triggered automatic erasure on a private network
US11102010B2 (en) System and apparatus for providing authenticable electronic communication
US10193844B1 (en) Secure cloud-based messaging and storage
US9641575B2 (en) Method for sharing multimedia content between two users
US20110321131A1 (en) Security model for workflows aggregating third party secure services
KR20160092021A (ko) 제 3 자 애플리케이션 활동 데이터 수집을 위한 시스템 및 방법
CN108123933B (zh) 基于互联网大数据的信息泄露自动监测方法和系统
US20220405740A1 (en) Making Payments Through Electronic Channels
US20250168169A1 (en) Communication platform server integration
CN107438054B (zh) 基于公众平台实现菜单信息控制的方法及系统
CN1398375A (zh) 用于认证用户的方法和设备
US20240121230A1 (en) Systems and methods for generating and using secure sharded onboarding user interfaces
WO2024067161A1 (zh) 一种通过5g消息实现无app化移动办公的方法
CN110458518A (zh) 一种集中式多账号微信自媒体管理平台及运行方法
CN108305073A (zh) 使用通信信道执行交易请求的方法和系统
US11323270B2 (en) System and apparatus for providing authenticable electronic communication
WO2021081705A1 (zh) 支付平台管理方法、设备、支付平台以及计算机存储介质
TW201907389A (zh) 管理一或多個運算裝置的通訊之系統、裝置和方法
CN113946739B (zh) 敏感数据查询方法、装置、设备及存储介质
CN120320959A (zh) 一种融合大模型的智能化dapp装置
US12505243B2 (en) Image and message management and archiving for events
KR100946410B1 (ko) 타인의 동의에 의한 휴대폰 결제 방법 및 시스템
JP2007036562A (ja) 電話番号の登録・認証システム，方法，認証サーバおよびプログラム
CN115776548A (zh) 双录系统
TW201907688A (zh) 驗證自一或多個運算裝置所接收的通訊之系統、裝置和方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23870395

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 16/07/2025)

122 Ep: pct application non-entry in european phase

Ref document number: 23870395

Country of ref document: EP

Kind code of ref document: A1