Conference creation method, electronic device, and computer-readable storage device
By acquiring and binding quick meeting IDs and normal meeting IDs, the problem of low efficiency in the meeting creation process is solved, enabling quick entry into the meeting and unbinding after completion, saving server resources and improving user experience and efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-04
- Publication Date
- 2026-03-27
AI Technical Summary
In existing technologies, the process of creating a meeting ID affects the efficiency of users joining a meeting, especially when the number of users increases and the frequency of use increases, resulting in excessive time consumption.
A first meeting is created by obtaining the first meeting ID (quick meeting ID), and a second meeting ID is generated and bound. This allows the same meeting to be queried using both meeting IDs until the normal meeting ID application is completed, at which point the binding is released to save server resources.
This allows users to join a meeting in advance using a quick meeting ID before the normal meeting ID application is completed, improving user experience, saving server resources, and increasing meeting entry efficiency.
Smart Images

Figure CN116743518B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the field of communication, in particular to a conference creation method, an electronic device and a computer readable storage device. BACKGROUND
[0002] With the progress of science and technology, online mode provides more possibilities for work communication. Online conference has become the only choice for most companies to carry out business and internal communication. The current creation method of online conference usually requires the user to apply for a conference to the server, and the server creates a conference number for the conference, which is used to identify the conference. The user enters the conference through the conference number to realize the common meeting. However, due to the expansion of the user scale and the increase of the use frequency of online conference, it takes more time to create a specific conference number, which affects the efficiency of the user entering the conference. SUMMARY
[0003] The main purpose of the present application is to provide a conference creation method, an electronic device and a computer readable storage device, which can solve the technical problem that the process of creating a conference number affects the efficiency of the user entering the conference.
[0004] To solve the above technical problems, the first technical solution adopted by the present application is to provide a conference creation method. The method comprises: obtaining an input first conference number; creating a corresponding first conference based on the first conference number, and generating a corresponding second conference number based on the first conference; and binding the first conference number and the second conference number, so that the first conference can be queried through the first conference number and the second conference number.
[0005] To solve the above technical problems, the first technical solution adopted by the present application is to provide an electronic device. The electronic device comprises a processor and a memory connected to the processor, the memory is used to store program data, and the processor is used to execute the program data to realize the method described in the first technical solution.
[0006] To solve the above technical problems, the third technical solution adopted by the present application is to provide a computer readable storage device. The computer readable storage device stores program data, which can be executed by a processor to realize the method described in the first technical solution.
[0007] The beneficial effects of the present application are: different from the prior art, the conference is created according to the obtained first conference number, i.e. the fast conference number, and the normal conference number is applied according to the created conference, i.e. the application of the second conference number, so that the user can enter and share the conference in advance through the fast conference number when the normal conference number is not yet applied, and the fast conference number is released after the normal conference number is applied, so as to save the server resources. BRIEF DESCRIPTION OF DRAWINGS
[0008] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and all other drawings obtained by those of ordinary skill in the art without creative effort based on these drawings are within the scope of the present application.
[0009] Figure 1 is a flowchart of the first embodiment of the conference creation method of the present application;
[0010] Figure 2 is a flowchart of the second embodiment of the conference creation method of the present application;
[0011] Figure 3 is a flowchart of the third embodiment of the conference creation method of the present application;
[0012] Figure 4 is a flowchart of the fourth embodiment of the conference creation method of the present application;
[0013] Figure 5 is a flowchart of the fifth embodiment of the conference creation method of the present application;
[0014] Figure 6 is a flowchart of the sixth embodiment of the conference creation method of the present application;
[0015] Figure 7 is a flowchart of the seventh embodiment of the conference creation method of the present application;
[0016] Figure 8 is a flowchart of the eighth embodiment of the conference creation method of the present application;
[0017] Figure 9 is a flowchart of the ninth embodiment of the conference creation method of the present application;
[0018] Figure 10 is a structural schematic diagram of an embodiment of the electronic device of the present application;
[0019] Figure 11 is a structural schematic diagram of an embodiment of the computer readable storage device of the present application. DETAILED DESCRIPTION
[0020] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of the present application.
[0021] The terms "first", "second", and the like in the specification are used to distinguish between similar objects, not to describe a particular sequential order. Moreover, the terms "include", and "have", and any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or device that comprises a list of steps or units is not limited to the listed steps or units, but can optionally further include additional steps or units not listed, or can optionally further include steps or units inherent to such process, method, system, product, or device.
[0022] Reference herein to "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment can be included in at least one embodiment of the application. The appearance of the phrase in various places in the specification does not necessarily all refer to the same embodiment, nor does it necessarily refer to a separate or alternative embodiment, in isolation or in combination with other embodiments. It is explicitly and implicitly understood by those skilled in the art that embodiments described herein can be combined with other embodiments.
[0023] As shown in Figure 1 Figure 1 The flowchart of the first embodiment of the method for creating a conference in the application is shown. It includes the following steps:
[0024] S11: Obtain the input first conference number.
[0025] The input first conference number is obtained, which is a quick conference number created for early entry into a conference. The conference number is input by the user to create a conference. Since it is convenient for the user to create and enter a conference, the conference number is more concise than a normal conference number, and the user usually does not want to be too complex in order to facilitate memory. For example, if the normal conference number is eight digits, the first conference number can be four, five, six, etc.
[0026] S12: Create a corresponding first conference based on the first conference number, and generate a corresponding second conference number based on the first conference.
[0027] After obtaining the input first conference number, the server creates a conference according to the first conference number for the user to use the conference for the conference. At the same time, after completing the creation of the conference, the second conference number, i.e., the normal conference number, is applied for the conference. At this time, the first conference can be entered by the first conference number.
[0028] S13: Bind the first conference number and the second conference number, so that the first conference can be queried by both the first conference number and the second conference number.
[0029] After the conference creation is completed and the second conference number application is completed, the first conference number and the second conference number are bound, so that the first conference number and the second conference number are both bound to the created conference, so that subsequent entering the created conference through inputting the first conference number and the second conference number is enabled. Subsequently, the first conference number can be unbound from the second conference number to save relevant resources of the server, and the specific implementation method can be realized through the description of the following embodiments.
[0030] Through the method described in this embodiment, the conference is created according to the obtained first conference number, that is, the fast conference number, and the normal conference number application, that is, the second conference number application, is performed according to the created conference. Further, when the normal conference number has not been applied, the entering and sharing of the conference through the fast conference number in advance is enabled, and after the normal conference number application is completed, the fast conference number is unbound to save the server resources, and the entering and sharing of the conference through the second conference number is enabled.
[0031] As shown in Figure 2 , the flowchart of the third embodiment of the conference creation method of the present application is shown. Figure 2 The method is a further extension of step S11. It includes the following steps:
[0032] S21: Query whether a second conference corresponding to the first conference number exists.
[0033] When the conference is created according to the input first conference number, the server is traversed to query whether a conference corresponding to the first conference number exists. The existing conference is identified as a second conference. If it exists, step S22 is performed.
[0034] S22: Display the identification information of the second conference.
[0035] When it is queried that the second conference corresponding to the first conference number exists, the identification information of the second conference is displayed. For example, the conference name, conference code, etc. of the second conference are displayed. The identification information of the second conference can be joined in response to a click operation. If it does not exist, step S23 is performed.
[0036] S23: Create a corresponding first conference based on the first conference number.
[0037] If the existing second conference corresponding to the first conference number is not queried, the creation of the first conference is directly performed.
[0038] As shown in Figure 3 , the flowchart of the third embodiment of the conference creation method of the present application is shown. Figure 3 The method is a further extension of step S22. It includes the following steps:
[0039] S31: Display a conference creation button.
[0040] If a second meeting corresponding to the first meeting ID is found to already exist, the identification information of the second meeting will be displayed. Furthermore, a "Create Meeting" button will be displayed, allowing the user to choose whether to continue creating the first meeting based on the first meeting ID.
[0041] S32: In response to a click on the meeting creation button, retrieve the entered meeting name.
[0042] If the user chooses to continue creating the first meeting, the meeting name input interface will be displayed in response to the user clicking the meeting creation button. This meeting name input interface allows the user to enter a meeting name, and the meeting names for the first and second meetings will be different to distinguish them from the existing second meeting.
[0043] S33: Create the corresponding first meeting based on the first meeting number and meeting name.
[0044] After obtaining the first meeting ID and the name of the meeting to be created, the first meeting is created based on the meeting ID and the meeting name.
[0045] In one embodiment, after the user chooses to continue creating the meeting, the server directly generates a meeting name for the first meeting. This meeting name is based on the user's account name, thus distinguishing it from the second meeting. For example, in response to the creation operation of the first meeting with meeting number 1122, and given that the identification information of an existing second meeting number shows its meeting name as 1122, the server directly names the first meeting using the user's account name, such as AB, naming it 1122-AB. The first meeting is then created based on the named first meeting name and the first meeting number.
[0046] like Figure 4 As shown, Figure 4 This is a flowchart illustrating a fourth embodiment of the method for creating a meeting for this application. This method is a further extension of the third embodiment. It includes the following steps:
[0047] S41: Determine whether the number of existing meetings corresponding to the first meeting number is less than the set number threshold.
[0048] If a second meeting corresponding to the first meeting number is found to already exist, the identification information of the second meeting will be displayed. Further, it is determined whether the displayed number of second meetings is less than a predetermined threshold. If not, the user is prompted to re-enter the first meeting number. If yes, step S42 is executed.
[0049] S42: Display the meeting creation button.
[0050] In addition to displaying the identification information for the second meeting, a meeting creation button is further displayed, allowing users to choose whether to continue creating the first meeting based on the first meeting number.
[0051] S43: In response to a click on the meeting creation button, retrieve the entered meeting name.
[0052] If the user chooses to continue creating the first meeting, the meeting name input interface will be displayed in response to the user clicking the meeting creation button. This meeting name input interface allows the user to enter a meeting name, and the meeting names for the first and second meetings will be different to distinguish them from the existing second meeting.
[0053] S44: Create the corresponding first meeting based on the first meeting number and meeting name.
[0054] After obtaining the first meeting ID and the name of the meeting to be created, the first meeting is created based on the meeting ID and the meeting name.
[0055] The method described in this embodiment limits the addition of new meetings under a first meeting number when too many meetings are detected, thus preventing excessive system data complexity and impacting system computational efficiency. It also improves the user experience by reducing the time users spend searching for their target meeting among numerous others.
[0056] like Figure 5 As shown, Figure 5 This is a flowchart illustrating a fifth embodiment of the method for creating a meeting in this application. This method is a further extension of step S22. It includes the following steps:
[0057] S51: Generate the corresponding third meeting number based on the first meeting number.
[0058] If a second meeting corresponding to the first meeting number is found to already exist, its identifier information is displayed. Furthermore, a third meeting number is generated directly from the first meeting number. The third meeting number has a longer character length than the first meeting number and contains all the characters of the first meeting number. For example, if the first meeting number is 1122, while displaying the identifier information of the existing second meeting corresponding to 1122, a third meeting number 11221 is generated based on 1122.
[0059] S52: Displays a meeting creation prompt button based on the third meeting number.
[0060] After a new third meeting ID is generated, the third meeting ID and a button for creating a meeting based on the third meeting ID are displayed, allowing users to choose whether to create a meeting based on the third meeting ID.
[0061] S53: In response to the click of the meeting creation inquiry button, create the corresponding first meeting based on the third meeting number.
[0062] After the user selects to continue meeting creation, the first meeting is created based on the third meeting number.
[0063] In one embodiment, during the process of creating a meeting based on a third meeting number, it is also necessary to perform a query operation for the meeting corresponding to the meeting number to determine whether a corresponding second meeting exists. The relevant steps can be referred to the description in the above embodiments, and will not be repeated here.
[0064] like Figure 6 As shown, Figure 6 This is a flowchart illustrating the sixth embodiment of the meeting creation method of this application. This method is a further extension of the meeting creation process already completed in the above embodiments. It includes the following steps:
[0065] S61: Determine whether the meeting number when entering the corresponding meeting is the first meeting number or the third meeting number.
[0066] After the first meeting is created, you can join the meeting using the quick meeting number. The quick meeting number includes the entered first meeting number and a third meeting number that is a variation of the first meeting number. The system checks whether the corresponding meeting number used when joining the meeting is either the first or third meeting number. If so, proceed to step S62.
[0067] S62: Send a confirmation message to the relevant meeting members.
[0068] When a user enters the corresponding meeting using the first or third meeting ID, the server sends a confirmation message to the members in the meeting to determine whether the user is allowed to enter.
[0069] In one embodiment, the server may send messages to at least one of the following: the meeting creator, a temporarily appointed meeting administrator, or other participants.
[0070] In another embodiment, the confirmation message sent by the server may further include the user's account name, job information, company department information, etc., to help meeting members select the person to join the meeting, and also to prevent the user from using the wrong quick meeting ID to join other meetings.
[0071] After the conference is created, the second conference number corresponding to the conference has been generated, and the conference does not need multiple conference numbers, which causes waste of related resources. Therefore, it is necessary to release the binding relationship between the first conference number and the second conference number, to release the binding relationship between the first conference number and the conference, so that the conference can be queried only through the second conference number. The specific unbinding process can be realized by the method described in the following embodiments.
[0072] As Figure 7 shown, Figure 7 a flowchart of a seventh embodiment of the conference creation method of the present application. The method is a further extension after the conference creation of the above-mentioned embodiments has been completed. It includes the following steps:
[0073] S71: obtaining the unbinding operation.
[0074] The user selects the unbinding operation.
[0075] In an embodiment, a button for unbinding the first conference number and the second conference number can be displayed, and in response to the clicking operation of the button, the unbinding operation of the first conference number and the second conference number can be performed.
[0076] S72: in response to the unbinding operation, unbinding the first conference number and the second conference number.
[0077] In an embodiment, in response to the clicking operation of the button, the server unbinds the first conference number and the second conference number, so that the conference can be entered only through the second conference number.
[0078] As Figure 8 shown, Figure 8 a flowchart of an eighth embodiment of the conference creation method of the present application. The method is a further extension after the conference creation of the above-mentioned embodiments has been completed. It includes the following steps:
[0079] S81: obtaining the binding duration of the first conference number and the second conference number.
[0080] After the application of the second conference number is completed, the first conference number and the second conference number are bound, and the binding time of the first conference number and the second conference number is started to be recorded.
[0081] S82: judging whether the binding duration is greater than a set duration threshold.
[0082] In the process of the conference, it is judged whether the binding time is greater than a pre-set duration threshold. If yes, step S83 is executed.
[0083] S83: in response to the binding duration of the first conference number and the second conference number being greater than the set duration threshold, unbinding the first conference number and the second conference number.
[0084] If the binding duration exceeds the set duration threshold, the binding between the first and second meeting numbers is directly released without manual intervention from meeting members. Otherwise, proceed to step S84.
[0085] S84: Maintain the binding between the first conference number and the second conference number.
[0086] If the binding duration is determined to be less than the set duration threshold, the binding relationship between the first conference number and the second conference number will continue to be maintained.
[0087] like Figure 9 As shown, Figure 9 This is a flowchart illustrating the ninth embodiment of the meeting creation method of this application. This method is a further extension of the meeting creation already completed in the above embodiments. It includes the following steps:
[0088] S91: Get the binding duration between the first and second meeting numbers.
[0089] After completing the application for the second meeting number, bind the first meeting number to the second meeting number and start recording the binding time of the first meeting number and the second meeting number.
[0090] S92: Determine whether the binding duration is greater than the set duration threshold.
[0091] During the meeting, determine whether the binding time exceeds a preset duration threshold. If yes, proceed to step S93. Otherwise, proceed to step S96.
[0092] S93: In response to the binding duration of the first conference number and the second conference number exceeding the set duration threshold, send a confirmation message to the members in the meeting to unbind them.
[0093] When the binding duration exceeds the set duration threshold, a confirmation message is sent to the meeting members regarding the termination of the binding between the first and second meeting numbers.
[0094] In one embodiment, when the binding duration exceeds a duration threshold, a confirmation message to disconnect the meeting number binding is sent to the meeting creator.
[0095] S94: In response to the confirmation message for member selection, unbind the first meeting number from the second meeting number.
[0096] When a meeting member chooses to unbind, in response to a confirmation message, the binding between the first meeting ID and the second meeting ID is directly unbound.
[0097] S95: In response to a denial message from the member selection, maintain the binding relationship between the first meeting number and the second meeting number, and reset the binding duration to zero.
[0098] When the conference member chooses not to unbind, the binding relationship between the conference numbers is not unbound. The conference can be entered through the first conference number and the second conference number. And the binding duration of the first conference number and the second conference number is cleared for confirming whether to unbind the binding relationship to the conference member again.
[0099] S96: maintaining the binding of the first conference number and the second conference number.
[0100] When it is judged that the binding duration is not greater than the set duration threshold, the binding relationship between the first conference number and the second conference number is continuously maintained.
[0101] As shown in Figure 10 , Fig. 1 is a structural schematic diagram of an embodiment of an electronic device of the present application. Figure 10 As shown in
[0102] The electronic device includes a processor 110 and a memory 120.
[0103] The processor 110 controls the operation of the electronic device, and the processor 110 can also be referred to as a CPU (Central Processing Unit). The processor 110 can be an integrated circuit chip with signal sequence processing capability. The processor 110 can also be a general-purpose processor, a digital signal sequence processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor or the like.
[0104] The memory 120 stores the instructions and program data required for the operation of the processor 110.
[0105] The processor 110 is configured to execute instructions to implement the method provided by any embodiment and possible combination of the conference creation method of the present application.
[0106] As shown in Figure 11 , Fig. 2 is a structural schematic diagram of an embodiment of a computer readable storage device of the present application. Figure 11 As shown in
[0107] An embodiment of the computer readable storage device of the present application includes a memory 210, and the memory 210 stores program data, which is executed to implement the method provided by any embodiment and possible combination of the conference creation method of the present application.
[0108] The memory 210 can include a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program instructions, or can be a server storing the program instructions, which can send the stored program instructions to other devices for running, or can run the stored program instructions.
[0109] In summary, the conference is created according to the obtained first conference number, i.e., the fast conference number, and the application of the normal conference number, i.e., the application of the second conference number, is performed according to the created conference. Then, when the normal conference number has not been applied, the conference can be entered and shared in advance through the fast conference number, and after the normal conference number is applied, the fast conference number is released to save server resources, and the conference is entered and shared through the second conference number.
[0110] In several embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device embodiments described above are only illustrative, for example, the division of the modules or units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed.
[0111] The units described as separate components can or can not be physically separated, and the components displayed as units can or can not be physical units, i.e., can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the present embodiment scheme.
[0112] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present alone, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software functional unit.
[0113] The integrated units in the above other embodiments, if implemented in the form of software function units and sold or used as independent products, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, essentially or in other words, the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.
[0114] The above is only an embodiment of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent flow transformation made by using the content of the specification and drawings, or directly or indirectly applied to other related technical fields, is also included in the patent protection scope of the present application.
Claims
1. A conference creation method, characterized by, The method comprises: acquiring an input first conference number; inquiring whether a second conference corresponding to the first conference number exists; if not, creating a corresponding first conference based on the first conference number, and generating a corresponding second conference number based on the first conference, the first conference being able to be inquired into through the first conference number; binding the first conference number and the second conference number, so that the first conference can be inquired into through both the first conference number and the second conference number; if so, displaying identification information of the second conference; wherein the identification information of the second conference can be responded to a triggering operation to enable a user to join the second conference.
2. The method of claim 1, wherein after the step of displaying the identification information of the second conference, the method further comprises: displaying a conference creation button; in response to a click operation on the conference creation button, acquiring a conference name input by a user; creating a corresponding first conference based on the first conference number and the conference name; wherein the conference names of the first conference and the second conference are different.
3. The method of claim 2, wherein the method further comprises: determining whether the number of conferences corresponding to the first conference number that already exist is less than a set number threshold; if so, performing the step of displaying the conference creation button.
4. The method of claim 1, wherein after the step of displaying the identification information of the second conference, the method further comprises: generating a corresponding third conference number based on the first conference number; wherein the character length of the third conference number is greater than the character length of the first conference number, and the third conference number contains all characters of the first conference number; displaying a conference creation inquiry button based on the third conference number; in response to a click operation on the conference creation inquiry button, creating a corresponding first conference based on the third conference number.
5. The method of claim 1 or 4, wherein the method further comprises: determining whether the conference number when entering a corresponding conference is the first conference number or the third conference number; if so, sending a confirmation message to members in the corresponding conference for determining whether to allow the user to enter.
6. The method of claim 1, wherein after the step of binding the first conference number and the second conference number, the method further comprises: unbinding the first conference number and the second conference number, so that the first conference can only be inquired into through the second conference number.
7. The method of claim 6, wherein the step of unbinding the first conference number and the second conference number comprises: in response to acquiring an unbinding operation, unbinding the first conference number and the second conference number; or in response to the binding of the first conference number and the second conference number lasting longer than a set time threshold, unbinding the first conference number and the second conference number. A device comprising a memory and a processor, the memory being used to store program data, the program data being executable by the processor to implement the method of any one of claims 1-7. 8. An electronic device, comprising: 9. A computer readable storage device, characterized in that, program data stored thereon, capable of being executed by a processor to implement the method of any one of claims 1-7.
Citation Information
Patent Citations
Conference joining method and device, conference platform and computer readable storage medium
CN114125362A
Method for holding multi-point video conference by terminal dialing
CN1756343A