Conference information processing method and device

Abstract

The invention discloses a conference information processing method and device, and the method comprises the steps: displaying a field for configuring a conference after detecting that a conference creation operation is triggered in a visual configuration page of a terminal; detecting corresponding field information for the field configuration for the conference in a visual configuration page; the corresponding field information is sent to a server side, so that the server side verifies the compliance verification field in the corresponding field information, and a verification result is fed back to the terminal; wherein a pre-configured verification rule is called during verification, and the to-be-verified field information in the corresponding field information is verified based on the verification rule indication constraint content. The personalized conference is created in a visual configuration mode, and personalized verification is performed on the personalized conference in the configuration mode, so that the purpose of automatically creating the compliant personalized conference is achieved.

Description

Technical Field

[0001] The present invention relates to the technical field of information processing, and in particular to a conference information processing method and device. Background Art

[0002] In the medical field, meetings are held frequently. In related technologies, the creation and holding of meetings largely rely on manual creation, which cannot make meeting creation efficient, transparent, and intelligent. Summary of the invention

[0003] The main purpose of the present invention is to provide a conference information processing method and device to solve the defects existing in the related technology.

[0004] In order to achieve the above-mentioned purpose, according to the first aspect of the present invention, a conference information processing method is provided, including presenting the fields for configuring the conference when it is detected in the terminal visualization configuration page that the conference creation operation is triggered; detecting the corresponding field information configured for the conference field in the visualization configuration page; sending the corresponding field information to the server for the server to verify the compliance verification fields therein, and feeding back the verification results to the terminal; wherein, when performing the verification, the pre-configured verification rules are called, and the field information to be verified in the corresponding field information is verified based on the constraint content indicated by the verification rules.

[0005] Optionally, when configuring the verification rule, the method includes: detecting whether a condition configuration template is triggered, and if any condition configuration template is triggered, configuring different condition configuration templates based on the content of the user configuration operation instruction; wherein the condition configuration template includes a conference basic information condition configuration template, and the conference basic information condition configuration template includes multiple sub-condition configuration templates, each of which includes a conference type to be configured, verification information to be configured corresponding to the conference of the type to be configured, and logical relationships to be configured between the verification information to be configured.

[0006] Optionally, verifying the corresponding field information based on the verification rule indication constraint content includes: parsing the corresponding field to determine the meeting type field therein; calling all configured conditional configuration templates associated with the meeting type based on the meeting type field; verifying the field information to be verified in the corresponding field information based on the verification information configured in the configured meeting basic information conditional configuration template and the configured logical relationship.

[0007] Optionally, the condition configuration template includes a speaker condition configuration template, the speaker condition configuration template includes at least one speaker sub-condition configuration template, each speaker sub-condition configuration template includes the speaker type to be configured, the conference type to be configured corresponding to different types of speakers, the verification information to be configured corresponding to the speaker type to be configured, and the logical relationship to be configured between the verification information to be configured; the condition configuration template also includes a fee standard condition configuration template, the fee standard configuration rule template includes at least one sub-fee standard condition configuration template, each sub-fee standard condition configuration template includes the conference type to be configured, the catering standard verification information to be configured corresponding to different conference types and the accommodation standard verification information to be configured, and the logical relationship to be configured between the verification information to be configured; and / or, the condition configuration template also includes a conference procurement condition configuration template, the conference procurement condition configuration template includes at least one sub-conference procurement condition configuration template, each sub-conference procurement condition configuration template includes the vehicle procurement verification information to be configured, the transportation procurement verification information to be configured, and the logical relationship to be configured between the verification information to be configured.

[0008] Optionally, verifying the corresponding field information based on the verification rule indication constraint content includes: parsing the corresponding fields to determine the speaker type field therein; calling all configured participant speaker condition configuration templates associated with the conference type field and the speaker type field based on the two; verifying the field information to be verified in the corresponding field information based on the verification information configured in the configured participant speaker condition configuration template and the configured logical relationship.

[0009] Optionally, the method also includes: the terminal receives verification pass feedback information sent by the server and detects whether the approval operation is triggered; if triggered, an approval request is sent to the server so that the server obtains the approval rules corresponding to the created meeting and approves the created meeting based on the approval rules.

[0010] Optionally, the approval rules are obtained in advance through visual configuration. When configuring the approval rules, the method includes: detecting whether the approval condition configuration component is triggered in the approval rule visual configuration interface; if triggered, presenting the preset approval conditions in the approval rule visual configuration interface for the user to select and obtain the target approval conditions; if triggered, presenting the preset approver information in the approval rule visual configuration interface for the user to select the approver information and obtain the target approver information; and forming the approval rules based on the target approval conditions and the target approver information.

[0011] Optionally, the method further includes: the terminal obtains the speaker information configured by the user in the visual configuration, sends the speaker information to the server, and the server stores it in the database; when configuring the corresponding field information for the conference field, requesting the server to call the speaker data in the database for configuration

[0012] According to a second aspect of the present invention, a conference information processing device is provided, comprising: a configuration unit, for presenting fields for configuring a conference when it is detected in a terminal visualization configuration page that a conference creation operation is triggered; detecting corresponding field information configured for the conference fields in the visualization configuration page; and creating a request unit, for sending the corresponding field information to a server, so that the server can verify the compliance verification fields therein, and feed back the verification results to the terminal; wherein, when performing the verification, a preconfigured verification rule is called, and the field information to be verified in the corresponding field information is verified based on the constraint content indicated by the verification rule.

[0013] According to a third aspect of the present invention, there is provided a computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to execute the method described in any one of the implementations of the first aspect.

[0014] According to a fourth aspect of the present invention, there is provided an electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor executes the method described in any one implementation of the first aspect.

[0015] The conference information processing method and device of this embodiment include presenting the fields for configuring the conference after detecting that the conference creation operation is triggered in the terminal visualization configuration page; detecting the corresponding field information configured for the conference fields in the visualization configuration page; sending the corresponding field information to the server for the server to verify the compliance verification fields therein, and feeding back the verification results to the terminal; wherein, when performing the verification, the pre-configured verification rules are called, and the field information to be verified in the corresponding field information is verified based on the constraint content indicated by the verification rules. Personalized conferences are created through visual configuration, and personalized verification of personalized conferences is performed through configuration, so as to achieve the purpose of automatically creating compliant personalized conferences. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0017] Figure 1 is a flow chart of a conference information processing method according to an embodiment of the present invention;

[0018] Figure 2a , Figure 2b is a schematic diagram of an application of a conference information processing method according to an embodiment of the present invention;

[0019] Figure 3 is a schematic diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0020] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings 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 should fall within the scope of protection of the present invention.

[0021] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so as to describe the embodiments of the present invention described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0022] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0023] According to an embodiment of the present invention, a method for exchanging enterprise data based on email is provided. Figure 1 As shown, it includes the following steps 101 to 103:

[0024] Step 101: When it is detected in the terminal visualization configuration page that a conference creation operation is triggered, fields for configuring the conference are presented.

[0025] Step 102: Detect corresponding field information for the conference field configuration in the visualization configuration page.

[0026] In this step, a conference creation component that can be triggered by the user is presented in the visualization configuration page. When this component is triggered, specific conference configuration content can be presented. The conference configuration content includes multiple fields for the conference. For example, fields related to the basic information of the conference such as the conference applicant field, fields related to the conference person in charge (the corresponding field information can be user-defined information), the nature of the conference field (the corresponding field information includes promotion or non-promotion, etc.), the type of conference field (the corresponding field information includes department meetings, in-hospital meetings, city meetings, regional meetings, national meetings, researchers meetings, expert consultation meetings, satellite meetings / special meetings, etc.), the conference name field (the corresponding field information can be a user-defined name), the main / sub-venue field, the meeting start time field (the corresponding field information can be a user-defined start time), the meeting end time field (the corresponding field information can be a user-defined end time), the number of external participants field (the corresponding field information can be a user-defined number field), the number of internal participants field (the corresponding field information can be a user-defined number field), and the like.

[0027] The conference fields also include the conference speaker fields. Users can trigger the speaker selection operation on the page, and based on the selected speaker, the conference speaker-related fields are presented. These fields have corresponding field information by default. The conference speaker information can also be configured. The conference speaker information is stored in the speaker library. After the speaker selection operation is triggered, the server is requested to call the relevant speaker from the speaker library.

[0028] The conference fields also include attendee fields. Users can trigger the operation of selecting attendees on the page. Based on the selected attendees, attendee-related fields such as external attendee fields, internal attendee fields, and temporary attendee fields are displayed. These fields correspond to field information such as name, department title, etc. by default. The configuration of attendee information can also be completed through configuration.

[0029] The fields for meetings also include other budget and allocation fields. Users can trigger the page to select the field to add the budget, and then present the budget-related fields, including the expense type field, number of people field, frequency field, budget field, and per capita field; users can select the cost allocation field on the page to select the field to allocate the cost, and then present the fields related to the cost allocation, including the expense-bearing department field, product field, allocation ratio field, allocation amount field, etc. These fields have corresponding field information by default.

[0030] By making the field information configurable, it is possible to further diversify the creation of meetings.

[0031] Step 103: Send the corresponding field information to the server so that the server can verify the compliance check fields therein, and feed back the verification results to the terminal, wherein the preconfigured verification rules are called during the verification, and the field information to be verified in the corresponding field information is verified based on the constraint content indicated by the verification rules.

[0032] In this step, after the configuration is completed, the user can request the server to create a meeting, so that the server can complete the verification of the field information. If the verification is successful, the approval process can be entered for approval, and the creation can be completed after approval. If the verification is unsuccessful, the approval process will not be entered and the meeting cannot be created. The server verifies according to a verification rule, and the verification rule is based on the personalized verification rule obtained by the configuration method. During the verification, the corresponding data can be searched one by one according to the semantic logic to see if it meets the configuration, such as whether the data exists, customized statistics within a certain range, and obtaining master data, etc.

[0033] As an optional implementation of this embodiment, when configuring the verification rules, the method includes: detecting whether the condition configuration template is triggered, and if any condition configuration template is triggered, configuring different condition configuration templates based on the content of the user configuration operation indication; wherein the condition configuration template includes a conference basic information condition configuration template, and the conference basic information condition configuration template includes multiple sub-condition configuration templates, and each sub-condition configuration template includes the type of meeting to be configured and the verification information to be configured corresponding to the meeting of the type to be configured.

[0034] In this optional implementation, the user can visually configure the verification rules through the visual configuration page in the management business system. Multiple condition configuration templates are pre-set and can be presented in the configuration interface of the terminal. Exemplarily, the condition configuration templates include but are not limited to the basic information of the meeting condition configuration template, the speaker condition configuration template, the cost standard condition configuration template, and the meeting procurement condition configuration template, etc. After the user personalizes the template, multiple different verifications for the self-created meetings can be generated, and the meetings created by the user can be personalized and controlled at a fine-grained level, meeting the creation needs of personalized meetings.

[0035] Furthermore, the conference basic information condition configuration template includes multiple sub-templates, such as conference application sub-condition configuration template, conference material sub-condition configuration template, conference budget sub-condition configuration template, conference time sub-condition configuration template, speaker service type sub-condition configuration template, participant ratio sub-condition configuration template, and lecture fee payment sub-condition configuration template. These sub-condition configuration templates include the conference type field to be configured, different verification information to be configured under different types of conferences, and the logical relationship between the verification information.

[0036] refer to Figure 2a Taking the conference application sub-condition configuration template as an example, users can configure the conference type in the template, such as internal conference, academy-level academic exchange meeting, intra-academy MDT meeting, large-scale academic exchange meeting, etc., and can select one or more conference types. After configuring the conference type, configure the verification information under the one or more types, such as the number of days before and after the meeting start date, the verification information is less than 5 days, the total number of participants, the verification information is greater than 50, the conference format, the verification information is online, etc. When there are multiple verification information, you can configure the logical relationship between the verification information, such as "and", "or", etc.

[0037] This configuration can make one type of meeting have corresponding target verification information, or make multiple different types of meetings have the same verification information. For example, "academy-level academic exchange meeting, in-academy MDT meeting, large-scale academic exchange meeting" can all correspond to a verification information of "the number of days before and after the meeting start date is less than 5 days, and the meeting format is online".

[0038] Furthermore, since different meetings may require different verification information, after configuring one target verification information, you can continue to configure target verification information for other types of meetings, such as "the total number of participants in internal meetings and academy-level academic exchanges is greater than 50", and then obtain verification information for other types of meetings. Logical relationships can be configured between different target verification information. For example, "and", "or", etc. Based on this, a meeting application sub-condition configuration template can be obtained. Through this sub-condition configuration template, the field information when creating a meeting can be verified for compliance with the meeting application according to the target verification information.

[0039] refer to Figure 2bTaking the speaker service type condition configuration template as an example, users can configure the conference type in the template, such as academy-level academic exchange conference, intra-academy MDT conference, and / or large-scale academic exchange conference, etc., and can select one or more conference types. After completing the configuration of the conference type, configure the verification information under the one or more types, such as the number of speakers among the participating speakers, the verification information is greater than 1, the conference contains the speaker service type verification information including the host, the number of times the speaker attends the conference on the same day, the verification information is less than 2, the number of annual invitations of the speaker, the verification information is less than 10 times, etc. When there are multiple verification information, the logical relationship between the verification information can be configured, such as "and", "or", etc. For example, the conference type verification information, the number of participating speakers verification information, and the conference contains the speaker service type verification information are connected with "and".

[0040] By providing conditional templates and supporting users to personalize the configuration of verification information, users can automatically perform verification as expected at multiple compliance verification points in a personalized manner.

[0041] As an optional implementation method of this embodiment, verifying the corresponding field information based on the verification rule indication constraint content includes: parsing the corresponding field to determine the conference type field therein; calling all configured conditional configuration templates associated with the conference type based on the conference type field; verifying the field information to be verified in the corresponding field information based on the verification information configured in the configured conference basic information conditional configuration template and the configured logical relationship.

[0042] In this optional implementation, when configuring template verification based on sub-conditions, target verification information related to the meeting type can be called based on the meeting type configured when creating the meeting, and the field information to be verified in the field information, such as meeting duration, number of participants, meeting format, etc., can be verified based on the target verification information.

[0043] As an optional implementation method of this embodiment, the condition configuration template includes a participant speaker condition configuration template, and the participant speaker condition configuration template includes at least one participant speaker sub-condition configuration template, each speaker sub-condition configuration template includes a speaker type to be configured, a conference type to be configured corresponding to different types of speakers, verification information to be configured corresponding to the speaker type to be configured, a logical relationship to be configured between the verification information to be configured, and when multiple speaker types are configured, a logical relationship to be configured between different types of speakers.

[0044] In this optional implementation, the condition configuration template may also include a condition configuration template for participating speakers, which may include multiple sub-condition configuration templates such as a single lecture fee limit sub-condition configuration template and a speaker service time condition configuration template. Through these configuration templates, compliance checks can be performed on speakers involved in creating a meeting.

[0045] Taking the sub-condition configuration template of the single lecture fee limit as an example, the user can configure the speaker label in the template, verify information such as university professor, scientific researcher, etc., configure the speaker service fee, and verify information such as greater than 4,000, etc.; the user can also configure the speaker level, such as verifying that the information level is A; the user can also configure the meeting type in the template, etc.

[0046] As mentioned above, conditions such as speaker tag verification information, conference type, speaker level, etc. can be freely combined through logical relationships to form a target verification information; different target verification information can be combined through logical relationships. The above configuration can realize the configuration of single limit verification information.

[0047] As an optional implementation of this embodiment, the condition configuration template also includes a cost standard condition configuration template, and the cost standard configuration rule template includes at least one sub-cost standard condition configuration template, each sub-cost standard condition configuration template includes the conference type to be configured, the catering standard verification information to be configured corresponding to different conference types, and the accommodation standard verification information to be configured, the logical relationship to be configured between the verification information to be configured, and when multiple conference types are configured, the logical relationship to be configured between different types of conferences. The condition configuration template also includes a conference procurement condition configuration template, and the conference procurement condition configuration template includes at least one sub-conference procurement condition configuration template, each sub-conference procurement condition configuration template includes the vehicle procurement verification information to be configured, the transportation procurement verification information to be configured, the logical relationship to be configured between the verification information to be configured, and when multiple conference types are configured, the logical relationship to be configured between different types of conferences.

[0048] In this optional implementation, target verification information can also be obtained by combining different verification information. The target verification information can be combined through logical relationships to achieve the construction of fee standard compliance inspection rules and conference procurement inspection rules.

[0049] As an optional implementation method of this embodiment, verifying the corresponding field information based on the verification rule indication constraint content includes: parsing the corresponding fields to determine the speaker type field therein; calling all configured participant speaker condition configuration templates associated with the conference type field and the speaker type field based on the two; verifying the field information to be verified in the corresponding field information based on the verification information configured in the configured participant speaker condition configuration template and the configured logical relationship.

[0050] In this optional implementation, when verifying the speaker, all verification rules related to the speaker can be called out based on the speaker tag, and verification is performed using the verification rules.

[0051] As an optional implementation method of this embodiment, the method also includes: the terminal receives the verification pass feedback information sent by the server, and detects whether the approval operation is triggered; if triggered, sends an approval request to the server, so that the server obtains the approval rules corresponding to the created meeting, and approves the created meeting based on the approval rules.

[0052] As an optional implementation of this embodiment, the approval rule is obtained in advance through visual configuration. When configuring the approval rule, the method includes: detecting whether the approval condition configuration component is triggered in the approval rule visual configuration interface; if triggered, presenting the preset approval condition in the approval rule visual configuration interface for the user to select and obtain the target approval condition; if triggered, presenting the preset approver information in the approval rule visual configuration interface for the user to select the approver information and obtain the target approver information; and forming the approval rule based on the target approval condition and the target approver information.

[0053] In this optional implementation, in this optional implementation, after the verification is passed, the approval stage can be entered, and the created meeting is approved in the approval stage according to the approval conditions and approval users configured by the user.

[0054] Furthermore, when configuring the approval process, users can trigger the approval condition configuration operation and then select preset approval conditions and preset approvers. The preset approval conditions include but are not limited to the scope of application of the meeting, whether the meeting applicant is the meeting leader, the total budget of the meeting, the meeting application department, etc. Approval conditions can be added by the administrator as needed, including configuring approvers and the transfer conditions of approvers, such as which approver to transfer to if the approver cannot be found, etc.

[0055] As an optional implementation method of this embodiment, the method also includes the terminal obtaining the speaker information configured by the user in the visual configuration, sending the speaker information to the server, and storing it in the database by the server; when configuring the corresponding field information for the conference field, requesting the server to call the speaker data in the database for configuration.

[0056] In this optional implementation, a user library can be constructed by adding user information based on user configuration operations, and speakers can be created based on the user information in the user library, thereby constructing a speaker library. The speaker library stores speaker information, including basic speaker information and lecture fee limit information. The lecture limit information can be configured with different limit values, custom upper limits, etc. in a visual manner, and also includes speaker information modification records; further, when creating a meeting, since the speaker is associated, the speaker's attendance record is formed after the meeting is held, so each speaker information also has an attendance record.

[0057] Furthermore, when configuring speaker-related fields in the conference fields when creating a conference, a call request may be sent to associate the call speaker information with the created conference.

[0058] This embodiment realizes the creation of personalized conferences in a visual configuration manner, as well as the effects of automated verification and personalized approval.

[0059] It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that here. According to an embodiment of the present invention, a conference information output device is also provided, including a configuration unit for presenting a configuration conference field when a conference creation operation is detected to be triggered in a terminal visualization configuration page; detecting corresponding field information configured for the conference field in the visualization configuration page; creating a request unit for sending the corresponding field information to a server, so that the server can verify the compliance check field therein, and feed back the verification result to the terminal; wherein, when performing the verification, a preconfigured verification rule is called, and the field information to be verified in the corresponding field information is verified based on the constraint content indicated by the verification rule.

[0060] As an optional implementation method of this embodiment, when configuring the verification rules, it is detected whether the condition configuration template is triggered. If any condition configuration template is triggered, different condition configuration templates are configured based on the content of the user configuration operation instruction; wherein, the condition configuration template includes a conference basic information condition configuration template, and the conference basic information condition configuration template includes multiple sub-condition configuration templates, each sub-condition configuration template includes the type of conference to be configured, the verification information to be configured corresponding to the conference of the type to be configured, and the logical relationship to be configured between the verification information to be configured.

[0061] As an optional implementation method of this embodiment, verifying the corresponding field information based on the verification rule indication constraint content includes: parsing the corresponding field to determine the conference type field therein; calling all configured conditional configuration templates associated with the conference type based on the conference type field; verifying the field information to be verified in the corresponding field information based on the verification information configured in the configured conference basic information conditional configuration template and the configured logical relationship.

[0062] As an optional implementation method of this embodiment, the condition configuration template includes a speaker condition configuration template, the speaker condition configuration template includes at least one speaker sub-condition configuration template, each speaker sub-condition configuration template includes the speaker type to be configured, the conference type to be configured corresponding to different types of speakers, the verification information to be configured corresponding to the speaker type to be configured, and the logical relationship to be configured between the verification information to be configured; the condition configuration template also includes a fee standard condition configuration template, the fee standard configuration rule template includes at least one sub-fee standard condition configuration template, each sub-fee standard condition configuration template includes the conference type to be configured, the catering standard verification information to be configured corresponding to different conference types and the accommodation standard verification information to be configured, and the logical relationship to be configured between the verification information to be configured; and / or, the condition configuration template also includes a conference procurement condition configuration template, the conference procurement condition configuration template includes at least one sub-conference procurement condition configuration template, each sub-conference procurement condition configuration template includes vehicle procurement verification information to be configured, transportation procurement verification information to be configured, and the logical relationship to be configured between the verification information to be configured.

[0063] As an optional implementation method of this embodiment, verifying the corresponding field information based on the verification rule indication constraint content includes: parsing the corresponding fields to determine the speaker type field therein; calling all configured participant speaker condition configuration templates associated with the conference type field and the speaker type field based on the two; verifying the field information to be verified in the corresponding field information based on the verification information configured in the configured participant speaker condition configuration template and the configured logical relationship.

[0064] As an optional implementation method of this embodiment, the device also includes: an approval operation detection unit, the terminal receives the verification pass feedback information sent by the server, and detects whether the approval operation is triggered; if the approval request unit is triggered, it sends an approval request to the server, so that the server can obtain the approval rules corresponding to the created meeting, and approve the created meeting based on the approval rules.

[0065] As an optional implementation method of this embodiment, the approval rule is obtained in advance through visual configuration. When configuring the approval rule: whether the approval condition configuration component is triggered is detected in the approval rule visual configuration interface; if triggered, the preset approval condition is presented in the approval rule visual configuration interface for the user to select and obtain the target approval condition; if triggered, the preset approver information is presented in the approval rule visual configuration interface for the user to select the approver information and obtain the target approver information; the approval rule is composed based on the target approval condition and the target approver information.

[0066] The device also includes: a speaker information configuration unit terminal obtains the speaker information configured by the user in the visual configuration, sends the speaker information to the server, and the server stores it in the database; when the speaker information calling unit configures the corresponding field information for the conference field, it requests the server to call the speaker data in the database for configuration.

[0067] According to an embodiment of the present invention, the present invention also provides an electronic device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can implement the method described in any of the above embodiments when executing.

[0068] According to an embodiment of the present invention, the present invention further provides a readable storage medium, which stores computer instructions, and the computer instructions are used to enable a computer to implement the method described in any of the above embodiments when executed.

[0069] According to an embodiment of the present invention, the present invention further provides a computer program product, which can implement the method described in any of the above embodiments when executed by a processor.

[0070] FIG2 shows a schematic block diagram of an example electronic device 300 that can be used to implement an embodiment of the present invention. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices.

[0071] As shown in FIG2 , the electronic device 300 includes a computing unit 301, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 302 or a computer program loaded from a storage unit 308 into a random access memory (RAM) 303. In the RAM 303, various programs and data required for the operation of the electronic device 300 can also be stored. The computing unit 301, the ROM 302, and the RAM 303 are connected to each other via a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0072] A number of components in the electronic device 300 are connected to the I / O interface 305, including: an input unit 306, such as a keyboard, a mouse, etc.; an output unit 307, such as various types of displays, speakers, etc.; a storage unit 308, such as a disk, an optical disk, etc.; and a communication unit 309, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 309 allows the electronic device 300 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0073] The computing unit 301 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 301 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 301 performs the various methods and processes described above, such as the object matching method. For example, in some embodiments, the object matching method may be implemented as a computer software program, which is tangibly included in a machine-readable medium, such as a storage unit 308. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 300 via the ROM 302 and / or the communication unit 309. When the computer program is loaded into the RAM 303 and executed by the computing unit 301, one or more steps of the method described above may be performed.

[0074] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include: being implemented in one or more computer programs, which may be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general programmable processor, which may receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0075] The program code for implementing the method of the present invention can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, partially on the machine as a stand-alone software package and partially on a remote machine, or entirely on a remote machine or server.

[0076] In the context of the present invention, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Claims

1. A conference information processing method, characterized in that: include: When the conference creation operation is detected to be triggered in the terminal visualization configuration page, the fields for configuring the conference are presented; Detecting corresponding field information configured for the conference field in the visualization configuration page; The corresponding field information is sent to the server so that the server can verify the compliance verification field therein and feed back the verification result to the terminal; Wherein, when performing the verification, the preconfigured verification rule is called, and the field information to be verified in the corresponding field information is verified based on the constraint content indicated by the verification rule.

2. The conference information processing method according to claim 1, characterized in that: When configuring the verification rules, the method includes: Detect whether the condition configuration template is triggered, and if any condition configuration template is triggered, configure different condition configuration templates based on the content of the user configuration operation instruction; Among them, the condition configuration template includes a conference basic information condition configuration template, and the conference basic information condition configuration template includes multiple sub-condition configuration templates. Each sub-condition configuration template includes the type of conference to be configured, the verification information to be configured corresponding to the conference of the type to be configured, and the logical relationship to be configured between the verification information to be configured.

3. The conference information processing method according to claim 2, characterized in that: Verifying the corresponding field information based on the verification rule indication constraint content includes: Parsing the corresponding fields to determine the conference type field therein; calling all configured conditional configuration templates associated with the conference type based on the conference type field; The field information to be verified in the corresponding field information is verified based on the verification information configured in the completed conference basic information condition configuration template and the configured logical relationship.

4. The conference information processing method according to claim 3, characterized in that: The condition configuration template includes a conference speaker condition configuration template, the conference speaker condition configuration template includes at least one conference speaker sub-condition configuration template, each speaker sub-condition configuration template includes a speaker type to be configured, a conference type to be configured corresponding to different types of speakers, verification information to be configured corresponding to the speaker type to be configured, and a logical relationship to be configured between the verification information to be configured; The condition configuration template also includes a cost standard condition configuration template, and the cost standard configuration rule template includes at least one sub-cost standard condition configuration template, each sub-cost standard condition configuration template includes a conference type to be configured, catering standard verification information to be configured corresponding to different conference types, accommodation standard verification information to be configured, and logical relationships to be configured between the verification information to be configured; And / or, the condition configuration template also includes a conference procurement condition configuration template, the conference procurement condition configuration template includes at least one sub-conference procurement condition configuration template, each sub-conference procurement condition configuration template includes vehicle procurement verification information to be configured, transportation procurement verification information to be configured, and logical relationships to be configured between the verification information to be configured.

5. The conference information processing method according to claim 4, characterized in that: Verifying the corresponding field information based on the verification rule indication constraint content includes: Parsing the corresponding fields to determine the speaker type field therein; based on the conference type field and the speaker type field, calling all configured conference speaker condition configuration templates associated with the conference type field and the speaker type field; Based on the verification information configured in the completed participant condition configuration template and the configured logical relationship, the to-be-verified field information in the corresponding field information is verified.

6. The conference information processing method according to claim 1, characterized in that: The method further comprises: The terminal receives the verification feedback information sent by the server and detects whether the approval operation is triggered; If triggered, an approval request is sent to the server, so that the server can obtain the approval rules corresponding to the created meeting and approve the created meeting based on the approval rules.

7. The conference information processing method according to claim 6, characterized in that: The approval rules are pre-configured visually, and the method for configuring the approval rules includes: Check whether the approval condition configuration component is triggered in the approval rule visual configuration interface; If triggered, the preset approval conditions are presented in the approval rule visual configuration interface for users to select and obtain the target approval conditions; If triggered, the preset approver information is presented in the approval rule visual configuration interface, so that the user can select the approver information and obtain the target approver information; Approval rules are formed based on target approval conditions and target approver information.

8. The conference processing method according to claim 1, characterized in that: The method also includes: The terminal obtains the speaker information configured by the user in the visual configuration, and sends the speaker information to the server, which stores it in the database; When configuring the corresponding field information for the conference field, the server is requested to call the speaker data in the database for configuration.

9. A conference information processing device, characterized in that: include: A configuration unit, configured to present fields for configuring a conference when a conference creation operation is detected to be triggered in a terminal visualization configuration page; Detecting corresponding field information configured for the conference field in the visualization configuration page; Create a request unit, which is used to send the corresponding field information to the server, so that the server can verify the compliance verification field therein, and feed back the verification result to the terminal; Wherein, when performing the verification, the preconfigured verification rule is called, and the field information to be verified in the corresponding field information is verified based on the constraint content indicated by the verification rule.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the method according to any one of claims 1 to 8.

Images