Communication resource management method, device, terminal equipment and storage medium

Abstract

The present invention discloses a communication resource management method, device, terminal equipment and storage medium, which relates to the field of multi-terminal communication. The communication resource management method acquires conference resources from the WEB server, sends the conference resources to the MCU server corresponding to the conference resources through the WEB server, and analyzes whether the conference resources are E1 resources through the MCU server. If the conference resources are E1 resources, the MCU server matches the corresponding E1 server and E1 chip, forms a message, and sends the conference resources to the corresponding E1 server and the corresponding E1 chip. The technical problem that the E1 conference capability cannot be expanded and compatible on the basis of the current IP MCU is solved. The technology stack used for multi-terminal video conferencing is expanded, which has the effect of improving the stability of multi-terminal video conferencing data.

Description

Technical Field

[0001] This invention relates to the field of multi-terminal communication, and in particular to a communication resource management method, apparatus, terminal equipment, and storage medium. Background Technology

[0002] With societal progress and the development of information transmission channels, people have increasingly higher demands for communication quality. Especially with the rapid development of network technology, the demand for communication is gradually shifting towards high-quality multimedia communication, primarily audio and video. IP conferencing and E1 conferencing are the mainstream directions for multimedia conferencing. IP network video conferencing systems, based on statistical multiplexing and packet switching technologies, reveal many problems with their traditional "best-effort" mechanism when simultaneously transmitting multiple services such as voice, data, and video. The most significant issue is the inability to provide end-to-end bandwidth guarantees for each service, leading to significant transmission delays and jitter. E1, a data transmission standard for physical lines issued by the CCITT, uses 30-channel Pulse Code Modulation (PCM) for short (E1), commonly known as a single-pass group signal, with a rate of 2048 kb / s. It is generally used in telecommunications-grade service transmission and is based on circuit switching and time-division multiplexing technologies, providing dedicated end-to-end bandwidth. Therefore, the network itself has a robust transmission quality guarantee mechanism. IP MCU conferencing is now widely used, but if you want to use multi-point video conferencing based on E1 leased lines at the same time, you need to consider the handling of compatibility between IP conferencing and E1 conferencing.

[0003] Existing technologies lack provisions for handling both IP and E1 conferencing, and most rely on separate IP and E1 lines. Therefore, the use of existing technologies has limitations, necessitating the development of a communication resource management method, apparatus, terminal equipment, and storage medium.

[0004] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main objective of this invention is to provide a communication resource management method, apparatus, terminal device, and storage medium, aiming to solve the technical problem that the current IP MCU cannot be expanded and compatible with E1 conferencing capabilities.

[0006] To achieve the above objectives, the present invention provides a communication resource management method, the communication resource management method comprising:

[0007] Obtain meeting resources from the web server;

[0008] The meeting resources are distributed from the WEB server to the MCU server corresponding to the meeting resources.

[0009] The MCU server parses whether the conference resource is an E1 resource.

[0010] If the meeting resource is an E1 resource, then the corresponding E1 server and E1 chip are matched through the MCU server;

[0011] The system sends out messages to distribute the meeting resources to the corresponding E1 servers and E1 chips.

[0012] Optionally, when the meeting resource in the step of obtaining meeting resources is a number resource, the step of sending a message to distribute the meeting resource to the corresponding E1 server and the corresponding E1 chip includes:

[0013] The system is designed to send messages and select the appropriate method for sending number resources based on available numbers.

[0014] Based on the appropriate method of distributing number resources, the number resources are distributed to the corresponding E1 server and the corresponding E1 chip.

[0015] Optionally, when the meeting resources in the step of obtaining meeting resources are number addition, deletion, and modification resources, the step of the component sending a message to send the meeting resources to the corresponding E1 server and the corresponding E1 chip includes:

[0016] The MCU server operates on the number resources corresponding to the E1 chip based on the addition, deletion, and modification of the number;

[0017] The MCU server operates on the number resources corresponding to the E1 chip based on the addition, deletion, and modification of the number;

[0018] The system sends a message to refresh the E1 chip via the E1 server.

[0019] Optionally, when the conference resource in the step of obtaining conference resources is a call / hang-up resource for a number, the step of sending a message to distribute the conference resource to the corresponding E1 server and the corresponding E1 chip includes the following:

[0020] The E1 chip performs signaling conversion on the call / hang-up resources of the number to obtain response signaling;

[0021] Based on the response signaling, the E1 chip performs call / hang-up operations on the E1 terminal corresponding to the call / hang-up resource of the number.

[0022] Optionally, the step of sending a message to distribute the meeting resources to the corresponding E1 server and the corresponding E1 chip includes:

[0023] Based on the aforementioned meeting resources, messages are sent and message resources are obtained.

[0024] The message resource is sent to the corresponding E1 server through the MCU server;

[0025] The E1 server then matches the corresponding E1 chip based on the message resource and sends the message resource to the corresponding E1 chip.

[0026] Optionally, the step of matching the corresponding E1 chip based on the message resource through the E1 server and sending the message resource to the corresponding E1 chip includes:

[0027] Initialize the E1 server;

[0028] Obtain the location information of the E1 server;

[0029] The location of the E1 chip is detected based on the location information;

[0030] If the location detection is successful, check if the E1 chip has any conference resources to be distributed;

[0031] If the E1 chip has conference resources to be distributed, the E1 resources will be distributed to the E1 chip through the E1 server.

[0032] Optionally, the communication resource management system further includes an IP terminal, and after the step of resolving whether the conference resource is an E1 resource through the MCU server, it further includes:

[0033] If the meeting resource is an IP resource, then the MCU server matches the corresponding IP terminal;

[0034] The system sends out messages, and the MCU server distributes the meeting resources to the IP terminals.

[0035] Furthermore, to achieve the above objectives, the present invention also provides a communication resource management device, the communication resource management device comprising:

[0036] The acquisition module is used to acquire meeting resources to the web server;

[0037] The transmission module is used to send the conference resources to the MCU server corresponding to the conference resources through the WEB server;

[0038] The parsing module is used to parse whether the conference resource is an E1 resource through the MCU server;

[0039] The matching module is used to match the corresponding E1 server and E1 chip through the MCU server if the meeting resource is an E1 resource.

[0040] The module is used to create and send messages, distributing the meeting resources to the corresponding E1 server and the corresponding E1 chip.

[0041] In addition, to achieve the above objectives, the present invention also provides a terminal device, the terminal device including a memory, a processor, and a communication resource management program stored in the memory and executable on the processor, wherein the communication resource management program, when executed by the processor, implements the steps of the communication resource management method as described above.

[0042] In addition, to achieve the above objectives, the present invention also provides a computer-readable storage medium storing a communication resource management program, which, when executed by a processor, implements the steps of the communication resource management method as described above.

[0043] This invention proposes a communication resource management method, apparatus, terminal device, and storage medium. The method involves acquiring conference resources from a web server, distributing these resources to a corresponding MCU server via the web server, and then using the MCU server to determine if the conference resource is an E1 resource. If it is, the MCU server matches the corresponding E1 server and E1 chip, assembles a delivery message, and distributes the conference resource to the corresponding E1 server and E1 chip. This solves the technical problem of not being able to expand and support E1 conferencing capabilities on the current IP MCU platform, improves the resource management efficiency of multi-terminal conferencing, and provides an effective technical criterion for conference communication resource management. Attached Figure Description

[0044] Figure 1 This is a schematic diagram of the functional modules of the terminal equipment to which the communication resource management device of the present invention belongs;

[0045] Figure 2 This is a flowchart illustrating a first exemplary embodiment of the communication resource management method of the present invention;

[0046] Figure 3 This is a schematic diagram of the E1 server matching the corresponding E1 chip based on the message resource and sending the message resource to the corresponding E1 chip in the communication resource management method of the present invention.

[0047] Figure 4 This is a flowchart illustrating a second exemplary embodiment of the communication resource management method of the present invention;

[0048] Figure 5 This is a schematic diagram of a second exemplary embodiment of the communication resource management method of the present invention;

[0049] Figure 6 This is a flowchart illustrating a third exemplary embodiment of the communication resource management method of the present invention;

[0050] Figure 7 This is a schematic diagram of a third exemplary embodiment of the communication resource management method of the present invention;

[0051] Figure 8 This is a flowchart illustrating a fourth exemplary embodiment of the communication resource management method of the present invention;

[0052] Figure 9 This is a schematic diagram of a fourth exemplary embodiment of the communication resource management method of the present invention;

[0053] Figure 10 This is a schematic diagram of the communication resource management device of the present invention.

[0054] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0055] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0056] This invention proposes a communication resource management method, apparatus, terminal device, and storage medium. The method involves acquiring conference resources from a web server, distributing these resources to a corresponding MCU server via the web server, and then using the MCU server to determine if the conference resource is an E1 resource. If it is, the MCU server matches the corresponding E1 server and E1 chip, assembles a delivery message, and distributes the conference resource to the corresponding E1 server and E1 chip. This solves the technical problem of not being able to expand and support E1 conferencing capabilities on the current IP MCU platform, improves the resource management efficiency of multi-terminal conferencing, and provides an effective technical criterion for conference communication resource management.

[0057] Technical terms involved in the embodiments of this invention:

[0058] E1 is a channel standard that uses synchronous time division multiplexing technology to combine 30 voice channels and 2 control channels onto a single high-speed channel of 2.048 Mbit / s.

[0059] MCU, or Microcontroller Unit, also known as a Single-Chip Microcomputer, is a chip-level computer that integrates a central processing unit (CPU) with a reduced frequency and specifications. It combines memory, timers, USB, A / D converters, UART, PLC, DMA, and even LCD driver circuitry onto a single chip, creating a chip-level computer for various applications. MCUs are found in everything from mobile phones and PC peripherals to remote controls, automotive electronics, and industrial applications such as stepper motor and robotic arm control.

[0060] IP, short for Internet Protocol, is a network layer protocol in the TCP / IP architecture. The purpose of IP is to improve network scalability: first, to solve internet problems and achieve interconnection of large-scale, heterogeneous networks; and second, to separate the coupling between top-level network applications and underlying network technologies, facilitating their independent development. Based on end-to-end design principles, IP provides only one connectionless, unreliable, best-effort packet transmission service to hosts.

[0061] With societal progress and the development of information transmission channels, people's demands for communication are increasing. Especially with the continuous upgrading of network technology, these demands are gradually shifting towards multimedia MCU communication, primarily based on audio and video. The MCU server is the core component of an MCU video conferencing system, acting as a switch. It synchronously separates the information streams from various meeting points, extracting audio, video, data, and signaling information. Then, it sends the information and signaling from each meeting point to the same processing module to complete corresponding audio mixing or switching, video mixing or switching, data broadcasting and routing, timing, and conference control processes. Finally, it distributes the various information required by each meeting point. The information is reassembled and sent to the corresponding video conferencing terminal system devices. Current video conferencing terminals support both IP lines and E1 lines, supporting the protocols H.323 and H.320 respectively. IP refers to the IP address, which is the address given on the intranet, public network, or private network. Leased lines refer to the independence of network resources, but IP leased lines are actually shared leased lines, and there are differences and fluctuations in uplink and downlink speeds compared to the nominal speed. E1 leased lines are end-to-end lines, which are more stable. Many manufacturers' video conferencing terminals only support IP lines and do not support E1 lines. E1 leased lines are based on circuit switching and time division multiplexing technology, which can provide end-to-end dedicated bandwidth. Therefore, the network itself has a complete transmission quality assurance mechanism.

[0062] Existing technologies do not take into account the processing of IP conferencing and E1 conferencing, and most of them use IP lines and E1 lines separately.

[0063] The communication resource management method proposed in this invention acquires conference resources from a web server, distributes these resources to a corresponding MCU server via the web server, and then the MCU server parses whether the conference resource is an E1 resource. If it is, the MCU server matches the corresponding E1 server and E1 chip, assembles a delivery message, and distributes the conference resource to the corresponding E1 server and E1 chip. This solves the technical problem of not being able to expand and be compatible with E1 conferencing capabilities on the current IP MCU basis. It expands the technology stack for multi-terminal video conferencing and improves the stability of multi-terminal video conferencing data.

[0064] Reference Figure 1 , Figure 1 This is a schematic diagram of the functional modules of the terminal device to which the communication resource management device of the present invention belongs. The communication resource management device can be an independent device capable of managing communication resources, and it can be implemented on the terminal device in hardware or software form. The terminal device can be a smart mobile terminal with data processing capabilities, such as a mobile phone or tablet computer, or it can be a fixed terminal device or server with data processing capabilities.

[0065] In this embodiment, the terminal device to which the communication resource management device belongs includes at least an output module 110, a processor 120, a memory 130, and a communication module 140.

[0066] The memory 130 stores the operating system and communication resource management program. The communication resource management device can acquire conference resources from the WEB server, and then distribute the conference resources to the corresponding MCU server via the WEB server. The MCU server parses whether the conference resource is an E1 resource. If the conference resource is an E1 resource, the MCU server matches the corresponding E1 server and E1 chip, assembles a message, and distributes the conference resource to the corresponding E1 server and E1 chip. The acquired conference resources are stored in the memory 130. The output module 110 can be a display screen, etc. The communication module 140 can include a WIFI module, a mobile communication module, and a Bluetooth module, etc., and communicates with external devices or servers through the communication module 140.

[0067] When the communication resource management program in memory 130 is executed by the processor, it performs the following steps:

[0068] Obtain meeting resources from the web server;

[0069] The meeting resources are distributed from the WEB server to the MCU server corresponding to the meeting resources.

[0070] The MCU server parses whether the conference resource is an E1 resource.

[0071] If the meeting resource is an E1 resource, then the corresponding E1 server and E1 chip are matched through the MCU server;

[0072] The system sends out messages to distribute the meeting resources to the corresponding E1 servers and E1 chips.

[0073] Furthermore, when the communication resource management program in memory 130 is executed by the processor, it also performs the following steps:

[0074] The system is designed to send messages and select the appropriate method for sending number resources based on available numbers.

[0075] Based on the appropriate method of distributing number resources, the number resources are distributed to the corresponding E1 server and the corresponding E1 chip.

[0076] Furthermore, when the communication resource management program in memory 130 is executed by the processor, it also performs the following steps:

[0077] The MCU server operates on the number resources corresponding to the E1 chip based on the addition, deletion, and modification of the number;

[0078] The system sends a message to refresh the E1 chip via the E1 server.

[0079] Furthermore, when the communication resource management program in memory 130 is executed by the processor, it also performs the following steps:

[0080] The E1 chip performs signaling conversion on the call / hang-up resources of the number to obtain response signaling;

[0081] Based on the response signaling, the E1 chip performs call / hang-up operations on the E1 terminal corresponding to the call / hang-up resource of the number.

[0082] Furthermore, when the communication resource management program in memory 130 is executed by the processor, it also performs the following steps:

[0083] Based on the aforementioned meeting resources, messages are sent and message resources are obtained.

[0084] The message resource is sent to the corresponding E1 server through the MCU server;

[0085] The E1 server then matches the corresponding E1 chip based on the message resource and sends the message resource to the corresponding E1 chip.

[0086] Furthermore, when the communication resource management program in memory 130 is executed by the processor, it also performs the following steps:

[0087] Initialize the E1 server;

[0088] Obtain the location information of the E1 server;

[0089] The location of the E1 chip is detected based on the location information;

[0090] If the location detection is successful, check if the E1 chip has any conference resources to be distributed;

[0091] If the E1 chip has conference resources to be distributed, the E1 resources will be distributed to the E1 chip through the E1 server.

[0092] Furthermore, when the communication resource management program in memory 130 is executed by the processor, it also performs the following steps:

[0093] If the meeting resource is an IP resource, then the MCU server matches the corresponding IP terminal;

[0094] The system sends out messages, and the MCU server distributes the meeting resources to the IP terminals.

[0095] This embodiment, through the above-described scheme, acquires meeting resources to the WEB server, distributes the meeting resources to the corresponding MCU server via the WEB server, and then the MCU server parses whether the meeting resource is an E1 resource. If the meeting resource is an E1 resource, the MCU server matches the corresponding E1 server and E1 chip, constructs a delivery message, and distributes the meeting resource to the corresponding E1 server and E1 chip. This solves the technical problem of not being able to expand and be compatible with E1 conferencing capabilities on the basis of current IP MCUs, achieves multi-point video conferencing compatible with both IP and E1 conferencing, improves the resource management efficiency of multi-terminal conferencing, and provides an effective technical criterion for conferencing communication resource management.

[0096] Based on, but not limited to, the terminal device architecture described above, this application proposes method embodiments.

[0097] The execution subject of the method of the present invention can be a communication resource management device or system. In this embodiment, a communication resource management device is selected as the execution subject.

[0098] Reference Figure 2 , Figure 2 This is a flowchart illustrating an exemplary embodiment of the communication resource management method of the present invention. In this embodiment, the communication resource management method includes:

[0099] Step S10: Obtain meeting resources from the WEB server;

[0100] The meeting resources can be obtained by downloading them from a cloud server or by copying information and storing them on a web server.

[0101] Step S20: The meeting resources are distributed from the WEB server to the MCU server corresponding to the meeting resources;

[0102] After receiving the instruction to send meeting resources to the MCU server, check whether the WEB server has established a TCP communication connection with the MCU server;

[0103] The corresponding MCU server is determined based on the corresponding E1 server, and the WEB server distributes the meeting resources to the corresponding MCU server through the TCP connection.

[0104] Step S30: The MCU server parses whether the meeting resource is an E1 resource;

[0105] The MCU server identifies the corresponding E1 server based on the terminal number in the message field of the conference resource. For example, it adds an E1 number type structure as a terminal template sub-attribute, where the terminal type represents the E1 terminal capability and the terminal number identifies the E1 number.

[0106] Typedef struct

[0107] {

[0108] String e164; / / Terminal number

[0109] String cascade; / / Terminal type (normal terminal or cascade port)

[0110] }

[0111] The MCU server determines whether the meeting room type is an IP meeting room or an E1 meeting room based on the value assigned to the Type field of type Int at a specific position in the message field.

[0112] Specifically, if the Type object of type Int is assigned a value of 0, the meeting resource with this field will be considered to belong to the meeting room type E1. If the Type object of type Int is assigned a value of 1, the meeting resource with this field will be considered to belong to the meeting room type IP. Furthermore, if new meeting room types need to be added later as information technology develops, it is only necessary to assign a new value to the Type field of type Int at a specific position in the message field to distinguish the previous types, so as to facilitate the addition of new types. For the Type object of type int, the value range can be -2147483648 to 2147483647.

[0113] If the special meeting room is identified based on the newly added fields, the MCU server will divide the meeting resources and then perform special processing. Specifically, after confirming that the meeting resources belong to the E1 meeting room, the meeting resources will be parsed, and the corresponding E1 chip will be determined according to the special fields in the distributed resources. The information of the E1 chip to which the meeting resources belong will be checked to see if it corresponds one-to-one with the information of the meeting resources. If the information of the E1 chip to which the meeting resources belong corresponds one-to-one with the information of the meeting resources, the status of the meeting resources will be changed to pending distribution.

[0114] If the Type value in the special location message field of the meeting resource is set to 0, indicating that the meeting resource belongs to an IP meeting room, then the MCU server will distribute the meeting resource to the IP terminal.

[0115] If the Type field in the special location message field of the meeting resource is identified as having a value of 1, meaning that the meeting resource belongs to the E1 venue, then the MCU server first determines whether to establish a TCP connection with the E1 server corresponding to the meeting resource, and positions the meeting resource status as pending distribution.

[0116] Step S50: If the meeting resource is an E1 resource, then the corresponding E1 server and E1 chip are matched through the MCU server.

[0117] The E1 venue number is generally composed of the following format:

[0118] MCU server registration number prefix + E1 server slot number + E1 number start index number + E1 number end index number.

[0119] Specifically, if the MCU server uses the registration number prefix 135, the E1 chip corresponding to this number is in slot 1, the starting index number is 00, and the ending index number is 03, then the E1 venue number is 135010003.

[0120] Therefore, the corresponding E1 server and E1 chip can be directly matched based on the E1 venue number.

[0121] Step S60: Message distribution is initiated to distribute the meeting resources to the corresponding E1 server and the corresponding E1 chip.

[0122] The MCU server has a daemon thread that periodically checks the status of meeting resources that are ready for distribution, as well as the status of the E1 servers and corresponding E1 chips managed by the MCU server. If the check shows that the E1 servers and corresponding E1 chips managed by the MCU server have established TCP connections, the meeting resources are distributed to the corresponding E1 chips, and the status of the meeting resources is changed to "distribution complete." If the check shows that the E1 servers and corresponding E1 chips managed by the MCU server have not established TCP connections, the thread waits for the E1 servers and corresponding E1 chips to establish TCP connections before distributing the meeting resources to the corresponding E1 chips and changing the status of the meeting resources to "distribution complete."

[0123] Reference Figure 3 , Figure 3 This is a schematic diagram illustrating the principle of the E1 server matching the corresponding E1 chip based on the message resource and sending the message resource to the corresponding E1 chip in the communication resource management method of the present invention. Since the E1 server contains registration information for all E1 chips belonging to the MCU device, the E1 server can determine whether it can configure and send conference resources to the corresponding E1 chip based on the online status of the E1 chip. Furthermore, the E1 server also needs to report the presence and working status of the E1 chips managed by the E1 server to the corresponding MCU server for call / hang-up of number resources.

[0124] If the E1 chip is displayed as registered and online in the E1 server, it means that the E1 server has established a connection with the E1 chip. At this time, the E1 server will configure the corresponding conference resources of the E1 chip and send the conference resources to the E1 chip through the TCP connection, and change the status of the conference resources to "sending completed" in the MCU server.

[0125] If the E1 chip is temporarily unavailable, the configuration and distribution will be delayed until the E1 chip is registered and online. At this time, the conference data display status will be "pending distribution".

[0126] This embodiment, through the above-described scheme, acquires conference resources to the WEB server, and then distributes these resources to the corresponding MCU server. The MCU server parses whether the conference resource is an E1 resource. If it is, the MCU server matches the corresponding E1 server and E1 chip, assembles a delivery message, and distributes the conference resource to the corresponding E1 server and E1 chip. By using the MCU and WEB server to jointly manage conference resources and adding a new field to the communication message for easy identification of the conference resources, this embodiment solves the technical problem of not being able to expand and be compatible with E1 conferencing capabilities on the current IP MCU basis. It expands the technology stack for multi-terminal video conferencing and improves the stability of multi-terminal video conferencing.

[0127] Furthermore, referring to Figure 4 , Figure 4 This is a flowchart illustrating a second exemplary embodiment of the communication resource management method of the present invention, with reference to... Figure 5 , Figure 5 This is a schematic diagram of a second exemplary embodiment of the communication resource management method of the present invention.

[0128] Based on the above Figure 2 In the embodiment shown, when step S10 of the above embodiment, which involves acquiring conference resources, is a number resource, the communication resource management method includes:

[0129] Step S11: Obtain the number resources to the WEB server;

[0130] The number resources are obtained through the Internet, and the method of obtaining them may be to download the number resources from a cloud server or to store the number resources in a WEB server by copying information, etc.

[0131] Determine whether to import the number resources based on the current meeting progress.

[0132] The meeting schedule can be a set of start switches or operation commands.

[0133] Step S21: The number resource is sent to the MCU server corresponding to the number resource through the WEB server;

[0134] After receiving the instruction to send the number resources to the MCU server, check whether the WEB server has established a TCP communication connection with the MCU server;

[0135] The corresponding MCU server is determined based on the corresponding E1 server, and the WEB server sends the number resources to the corresponding MCU server through the TCP connection.

[0136] Specifically, considering the working characteristics of web servers, HTTP is used to distribute number resources, and the number resource array is encapsulated in XML format.

[0137]

[0138]

[0139]

[0140] Specifically, the first number is: E1.

[0141] <name> _type< / name> <value> <int> 0< / int> < / value> This indicates that the number resource is an E1 number resource.

[0142] <name> _terminal_id< / name> <value> <string> 1< / string> < / value> This indicates that the ID of the endpoint is endpoint number 1 in string form.

[0143] <name> _E1_option< / name> <value> <struct>< / struct> < / value> This represents the structure of the number resource.

[0144] <name> _name< / name> <value> <string> H323_233< / string> < / value> This indicates the name of the E1 number resource.

[0145] <name> _e164< / name> <value> <string> 174051010< / string> < / value> This indicates the terminal number in the E1 number type structure of the E1 number.

[0146] The second number is the IP address:

[0147] <name> _type< / name> <value> <int> 1< / int> < / value> This indicates that the number resource is an IP number resource.

[0148] <name> _terminal_id< / name> <value> <string> 2< / string> < / value> This indicates that the ID of the endpoint is endpoint number 2 in string form.

[0149] <name> _H323_option< / name> <value> <struct>< / struct> < / value> This represents the structure of the number resource.

[0150] <name> _alias< / name> <value> <string> H323_233< / string> < / value> This indicates the second name of the IP number resource.

[0151] <name> _src_ip< / name> <value> <string> 201.0.1.1< / string> < / value> This indicates the IP address of the IP number.

[0152] When the MCU server receives the number resource from the WEB server, it registers the meeting room type information and checks whether the meeting room to which the number resource was sent includes an E1 meeting room. If the number resource is an E1 number resource, it checks the chassis number, slot number, and index number of the E1 chip corresponding to the E1 number resource, fills the E1 chip data structure into the E1 number resource, and modifies the resource status of the E1 chip to "pending delivery".

[0153] Meanwhile, the MCU server has a daemon thread that can periodically check the resource status of the E1 chip. If the check finds that the resource status of the E1 chip is pending, it obtains the number resource corresponding to the E1 chip, assembles it, and sends it to the E1 server. Finally, the MCU server modifies the resource status of the E1 chip to "sending completed".

[0154] Step S31: The MCU server parses whether the number resource is an E1 resource;

[0155] The MCU server identifies the corresponding E1 server based on the terminal number in the message field of the number resource. For example, it adds an E1 number type structure as a terminal template sub-attribute. The terminal type is used to represent the E1 terminal capability, and the terminal number is used to identify the E1 number.

[0156] Typedef struct

[0157] {

[0158] String e164; / / Terminal number

[0159] String cascade; / / Terminal type (normal terminal or cascade port)

[0160] }

[0161] The MCU server determines whether the meeting room type is an IP meeting room or an E1 meeting room based on the value assigned to the Type field of type Int at a specific position in the message field.

[0162] Specifically, if the Type object of type Int is assigned a value of 0, the number resource with that field will be considered to belong to the venue type E1. If the Type object of type Int is assigned a value of 1, the number resource with that field will be considered to belong to the venue type IP. Furthermore, if new venue types need to be added as information technology develops, it is only necessary to assign a new value to the Type field of type Int at a specific position in the message field to distinguish the previous types, so as to facilitate the addition of new types. For the Type object of type int, the value range can be -2147483648 to 2147483647.

[0163] If the special venue is identified based on the newly added fields, the MCU server will divide the number resources and then perform special processing. Specifically, after confirming that the number resources belong to the E1 venue, the number resources will be parsed, and the corresponding E1 chip will be determined according to the special fields in the distributed resources. The information of the E1 chip to which the number resources belong will be checked to see if it corresponds one-to-one with the information of the number resources. If the information of the E1 chip to which the number resources belong corresponds one-to-one with the information of the number resources, the status of the number resources will be changed to pending distribution.

[0164] If the Type value in the special location message field of the number resource is set to 0, indicating that the number resource belongs to the IP venue, then the MCU server will send the number resource to the IP terminal.

[0165] If the Type field in the special location message field of the number resource is identified as having a value of 1, meaning that the number resource belongs to the E1 venue, then the MCU server first determines whether to establish a TCP connection with the E1 server corresponding to the number resource, and positions the number resource as pending distribution.

[0166] Step S41: If the number resource is an E1 resource, then the corresponding E1 server and E1 chip are matched through the MCU server.

[0167] The E1 venue number is generally composed of the following format:

[0168] MCU server registration number prefix + E1 server slot number + E1 number start index number + E1 number end index number.

[0169] Specifically, if the MCU server uses the registration number prefix 135, the E1 chip corresponding to this number is in slot 1, the starting index number is 00, and the ending index number is 03, then the E1 venue number is 135010003.

[0170] Therefore, the corresponding E1 server and E1 chip can be directly matched based on the E1 venue number.

[0171] Step S51: Build a message delivery system and select an appropriate method for delivering number resources based on the number resources.

[0172] Step S61: Based on the appropriate method of distributing number resources, the number resources are distributed to the corresponding E1 server and the corresponding E1 chip.

[0173] If the MCU server establishes a TCP connection with the E1 server, the MCU server will distribute the number resources. The method by which the MCU server distributes the number resources is quite flexible. Since the terminal template has been expanded, it can choose to distribute all number resources according to the existing distribution method, or it can choose to distribute E1 number resources individually.

[0174] A: In existing technology, when distributing number resources, the MCU server needs to distinguish each number resource information and then make a judgment. If it is an E1 number resource, the distribution operation is performed based on the E1 chip corresponding to the E1 number resource, and the resource status of the E1 number resource corresponding to the E1 chip is changed to a pending distribution state. If it is an IP number resource, the IP number resource is directly distributed to the IP terminal, and the resource status of the IP number resource is changed to a pending distribution state.

[0175] B: E1 number resources can be distributed individually, or the MCU server can distribute all E1 number resources in batches. The distribution of all E1 numbers includes the following methods:

[0176] B1: Download the E1 number resource using the E1 chip as a reference unit. The downloaded E1 number resource must include the following parameters: the chassis number of the E1 chip mounting location corresponding to the E1 number resource, the slot number of the E1 chip mounting location corresponding to the E1 number resource, the index number in the slot of the E1 chip mounting location corresponding to the E1 number resource, and all E1 number resources on the E1 chip corresponding to the E1 number resource.

[0177] B2: Download the E1 number resource using the slot where the E1 chip is located as the reference unit. At this time, the downloaded E1 number resource needs to include the following parameters: the chassis number of the E1 chip installation location corresponding to the E1 number resource, the slot number of the E1 chip installation location corresponding to the E1 number resource, and all E1 number resources corresponding to the slot number of the E1 chip installation location corresponding to the E1 number resource.

[0178] B3: Download the E1 number resource using the chassis where the E1 chip is located as the reference unit. The downloaded E1 number resource must include the following parameters: the chassis number of the E1 chip's installation location corresponding to the E1 number resource, and all E1 number resources on the chassis number corresponding to the E1 chip's installation location.

[0179] Furthermore, the E1 server establishes a long TCP connection with the MCU server for message communication, and can use JSON format to send E1 number resource information in batches.

[0180]

[0181]

[0182] To further explain, the E1 server is used to uniformly manage the E1 devices connected to the MCU device. It needs to obtain the E1 chip's presence status and the E1 line status, which includes normal, crossover, and loopback states.

[0183] Specifically, since the E1 server contains registration information for all E1 chips belonging to the MCU device, the E1 server can determine whether to configure and distribute the E1 number resource to the corresponding E1 chip based on whether the E1 chip is online. If the E1 chip is temporarily offline, the E1 server will wait for the offline E1 chip to register and come online before configuring and distributing the resource.

[0184] Since the E1 server contains registration information for all E1 chips belonging to the MCU device, it can determine whether to configure and distribute number resources to the corresponding E1 chip based on the chip's online status. Furthermore, the E1 server also needs to report the presence and operational status of the E1 chips it manages to the corresponding MCU server.

[0185] If the E1 chip is displayed as registered and online in the E1 server, it means that the E1 server has established a connection with the E1 chip. At this time, the E1 server will configure the corresponding number resources of the E1 chip and send the number resources to the E1 chip through a TCP connection, and change the status of the number resources to "sending completed".

[0186] If the E1 chip is temporarily unavailable, it will be configured and issued after the E1 chip is registered and online. At this time, the number resource will be displayed as pending issuance.

[0187] In this embodiment, when the meeting resource in the step of obtaining meeting resources is a number resource,

[0188] By acquiring number resources from the web server, the number resources are then distributed to the corresponding MCU server via the web server. The MCU server parses whether the number resource is an E1 resource. If the number resource is an E1 resource, the MCU server matches the corresponding E1 server and E1 chip, constructs a distribution message, selects an appropriate distribution method based on the number resource, and distributes the number resource to the corresponding E1 server and E1 chip based on the appropriate distribution method. This achieves joint control of number resource distribution by the MCU server and web server, ensuring that number resources can be quickly and stably distributed to the corresponding terminals.

[0189] Furthermore, referring to Figure 6 , Figure 6 This is a flowchart illustrating a third exemplary embodiment of the communication resource management method of the present invention, with reference to... Figure 7 , Figure 7 This is a schematic diagram of a third exemplary embodiment of the communication resource management method of the present invention.

[0190] Based on the above Figure 2 In the embodiment shown, when step S10 of the above embodiment, which involves acquiring conference resources, refers to the addition, deletion, and modification of phone numbers, the communication resource management method includes:

[0191] Step S12: Obtain the resources for adding, deleting, and modifying numbers to the WEB server;

[0192] The method of obtaining the resource for adding, deleting, and modifying the number may be to download the resource from a cloud server or to store the resource in a web server by copying information.

[0193] Step S22: The resources for adding, deleting, and modifying the number are sent from the WEB server to the MCU server corresponding to the resources for adding, deleting, and modifying the number.

[0194] After receiving the instruction to send the resources for adding, deleting, and modifying numbers to the MCU server, check whether the WEB server has established a TCP communication connection with the MCU server;

[0195] The corresponding MCU server is determined based on the corresponding E1 server, and the WEB server sends the resources for adding, deleting, and modifying the number to the corresponding MCU server through the TCP connection;

[0196] Step S32: The MCU server parses whether the add, delete, or modify resource of the number is an E1 resource;

[0197] The MCU server determines whether the resource venue type for adding, deleting, or modifying the number is an IP venue or an E1 venue based on the value assigned to the Type field of type Int at a specific position in the message field.

[0198] Specifically, if the Type object of type Int is assigned a value of 0, the resource whose number is added, deleted, or modified with that field will be considered to belong to the E1 venue. If the Type object of type Int is assigned a value of 1, the resource whose number is added, deleted, or modified with that field will be considered to belong to the IP venue. Furthermore, if new venue types need to be added as information technology develops, it is only necessary to assign a new value to the Type field of type Int at a specific position in the message field to distinguish it from the previous types, so as to facilitate the addition of new types. For the Type object of type int, the value range can be -2147483648 to 2147483647.

[0199] If the special venue is identified based on the newly added field, the MCU server will divide the added, deleted, and modified resources of the number and then perform special processing. Specifically, after confirming that the added, deleted, and modified resources of the number belong to the E1 venue, the added, deleted, and modified resources of the number will be parsed, and the corresponding E1 chip will be determined according to the special fields in the distributed resources. It will be checked whether the information of the E1 chip to which the added, deleted, and modified resources of the number belong corresponds one-to-one with the information of the added, deleted, and modified resources of the number. If the information of the E1 chip to which the added, deleted, and modified resources of the number belong corresponds one-to-one with the information of the added, deleted, and modified resources of the number, the status of the added, deleted, and modified resources of the number will be changed to pending distribution.

[0200] If the Type value in the special location message field of the added, deleted, or modified resource of the number is set to 0, which means that the added, deleted, or modified resource of the number belongs to the IP venue, then the MCU server will send the added, deleted, or modified resource of the number to the IP terminal.

[0201] If the Type value in the special location message field of the added, deleted, or modified resource of the number is set to 1, which means that the added, deleted, or modified resource of the number belongs to the E1 venue, then the MCU server first determines whether to establish a TCP connection with the E1 server corresponding to the added, deleted, or modified resource of the number, and positions the added, deleted, or modified resource of the number as pending distribution.

[0202] Step S42: If the resource for adding, deleting, or modifying the number is an E1 resource, then the corresponding E1 server and E1 chip are matched through the MCU server.

[0203] The MCU server indexes the corresponding E1 chip and E1 server based on the terminal number index in the message field of the added, deleted, or modified resources of the number. For example, it adds an E1 number type structure as a sub-attribute of the terminal template. The terminal type is used to represent the E1 terminal capability, and the terminal number is used to identify the E1 number.

[0204] Typedef struct

[0205] {

[0206] String e164; / / Terminal number

[0207] String cascade; / / Terminal type (normal terminal or cascade port)

[0208] }

[0209] Specifically, the format of the E1 venue number is generally as follows:

[0210] MCU server registration number prefix + E1 server slot number + E1 number start index number + E1 number end index number.

[0211] Specifically, if the MCU server uses the registration number prefix 135, the E1 chip corresponding to this number is in slot 1, the starting index number is 00, and the ending index number is 03, then the E1 venue number is 135010003.

[0212] Therefore, the corresponding E1 server and E1 chip can be directly matched based on the E1 venue number.

[0213] Step S52: The MCU server operates on the number resources corresponding to the E1 chip based on the addition, deletion and modification of the number resources;

[0214] The MCU server has a daemon thread that periodically checks the status of the added, deleted, and modified number resources (those with the status of being sent out) and the status of the E1 servers and corresponding E1 chips managed by the MCU server. If the status of the E1 servers and corresponding E1 chips managed by the MCU server shows that a TCP connection has been established, the daemon thread performs the corresponding add, delete, or modify operation on the number resources of the E1 chip and changes the status of the added, deleted, or modified number resources to "sent out completely." If the status of the E1 servers and corresponding E1 chips managed by the MCU server shows that a TCP connection has not been established, the daemon thread waits for the E1 servers and corresponding E1 chips to establish a TCP connection before sending the added, deleted, or modified number resources to the corresponding E1 chips and changing the status of the added, deleted, or modified number resources to "sent out completely."

[0215] Since the E1 server contains registration information for all E1 chips belonging to the MCU device, it can determine whether to configure and modify number addition, deletion, and modification resources to the corresponding E1 chip based on the online status of the E1 chip. Furthermore, the E1 server also needs to report the presence and working status of the E1 chips it manages to the corresponding MCU server for number addition, deletion, and modification.

[0216] If the E1 chip is displayed as registered and online in the E1 server, it means that the E1 server has established a connection with the E1 chip. At this time, the E1 server will configure the corresponding E1 chip number addition, deletion and modification resources and modify the number addition, deletion and modification resources to the E1 chip through TCP connection, and change the status of the number addition, deletion and modification resources in the MCU server to "distribution completed".

[0217] If the E1 chip is not available temporarily, the configuration will be modified after the E1 chip is registered and online. At this time, the resource status for adding, deleting, and modifying the number will be displayed as pending modification.

[0218] Step S62: The assembly sends a message to refresh the E1 chip through the E1 server.

[0219] After receiving the added, deleted, or modified resources for the number, the E1 server determines whether to send a refresh command based on the online status of the E1 chip.

[0220] If the E1 chip is online, the E1 server assembly message sends a refresh command to the E1 chip.

[0221] If the E1 chip is offline, a refresh command will be sent after the E1 chip comes online.

[0222] In this embodiment, when the meeting resource in the step of acquiring meeting resources is a number addition, deletion, and modification resource, the number addition, deletion, and modification resource is acquired and sent to the WEB server. The WEB server then distributes this resource to the MCU server corresponding to the number addition, deletion, and modification resource. The MCU server parses whether the number addition, deletion, and modification resource is an E1 resource. If it is, the MCU server matches the corresponding E1 server and E1 chip. The MCU server then operates on the number resource corresponding to the E1 chip based on the number addition, deletion, and modification resource, constructs and sends a message, and the E1 server refreshes the E1 chip. This achieves the technical effect of joint management of number addition, deletion, and modification by the MCU server and the WEB server.

[0223] Furthermore, referring to Figure 8 , Figure 8This is a flowchart illustrating a fourth exemplary embodiment of the communication resource management method of the present invention, with reference to... Figure 9 , Figure 9 This is a schematic diagram of a fourth exemplary embodiment of the communication resource management method of the present invention.

[0224] Based on the above Figure 2 In the embodiment shown, when step S10 of the above embodiment, which involves acquiring conference resources, is a call / hang-up resource for a number, the communication resource management method includes:

[0225] Step S13: Obtain the call / hang-up resources of the number to the WEB server;

[0226] The call / hang-up resources of the number can be obtained by downloading the call / hang-up resources of the number from a cloud server or by storing the call / hang-up resources of the number in a WEB server by copying information, etc.

[0227] Step S23: The call / hang-up resource of the number is sent to the MCU server corresponding to the call / hang-up resource of the number through the WEB server;

[0228] After receiving the instruction to send the call / hang-up resources of the number to the MCU server, check whether the WEB server has established a TCP communication connection with the MCU server;

[0229] The corresponding MCU server is determined based on the corresponding E1 server, and the WEB server sends the call / hang-up resources of the number to the corresponding MCU server through the TCP connection;

[0230] Step S33: The MCU server parses whether the call / hang-up resource of the number is an E1 resource;

[0231] The MCU server determines whether the meeting room type is an IP meeting room or an E1 meeting room based on the value assigned to the Type field of type Int at a specific position in the message field.

[0232] Specifically, if the Type object of type Int is assigned a value of 0, the resource with that field will be considered to belong to the E1 venue. If the Type object of type Int is assigned a value of 1, the resource with that field will be considered to belong to the IP venue. Furthermore, if new venue types need to be added as information technology develops, it is only necessary to assign a new value to the Type field of type Int at a specific position in the message field to distinguish it from the previous types, so as to facilitate the addition of new types. For the Type object of type int, the value range can be -2147483648 to 2147483647.

[0233] If the special venue is identified based on the newly added fields, the MCU server will divide the resources and then perform special processing. Specifically, after confirming that the resource belongs to the E1 venue, the resource will be parsed, and the corresponding E1 chip will be determined according to the special fields in the resource. The information of the E1 chip to which the resource belongs will be checked to see if it corresponds one-to-one with the information of the resource. If the information of the E1 chip to which the resource belongs corresponds one-to-one with the information of the resource, the status of the resource will be changed to pending distribution.

[0234] If the Type field in the resource special location message field is set to 0, meaning the resource belongs to an IP venue, then the MCU server will send the call / hang-up resource of the number to the IP terminal.

[0235] If the Type value in the special location message field of the call / hang-up resource of the number is set to 1, which means that the call / hang-up resource of the number belongs to the E1 venue, then the MCU server first determines whether to establish a TCP connection with the E1 server corresponding to the call / hang-up resource of the number, and positions the call / hang-up resource status of the number as pending distribution.

[0236] Step S43: If the call / hang-up resource of the number is an E1 resource, then the corresponding E1 server and E1 chip are matched through the MCU server.

[0237] The MCU server identifies the corresponding E1 server based on the terminal number in the message field of the call / hang-up resource of the number. For example, it adds an E1 number type structure as a sub-attribute of the terminal template. The terminal type is used to represent the E1 terminal capability, and the terminal number is used to identify the E1 number.

[0238] Typedef struct

[0239] {

[0240] String e164; / / Terminal number

[0241] String cascade; / / Terminal type (normal terminal or cascade port)

[0242] }

[0243] The E1 venue number is generally composed of the following format:

[0244] MCU server registration number prefix + E1 server slot number + E1 number start index number + E1 number end index number.

[0245] Specifically, if the MCU server uses the registration number prefix 135, the E1 chip corresponding to this number is in slot 1, the starting index number is 00, and the ending index number is 03, then the E1 venue number is 135010003.

[0246] Therefore, the corresponding E1 server and E1 chip can be directly matched based on the E1 venue number.

[0247] The MCU server has a built-in daemon thread that periodically checks the call / hang-up resources of numbers with a pending status, as well as the status of the E1 servers and corresponding E1 chips managed by the MCU server. If the E1 servers and corresponding E1 chips managed by the MCU server have established a TCP connection, the call / hang-up resource for the number is sent to the corresponding E1 chip, and the status of the call / hang-up resource for the number is changed to "sent-up complete." If the E1 servers and corresponding E1 chips managed by the MCU server have not established a TCP connection, the daemon thread waits for the E1 servers and corresponding E1 chips to establish a TCP connection before sending the call / hang-up resource for the number to the corresponding E1 chip, and the status of the call / hang-up resource for the number is changed to "sent-up complete."

[0248] If the E1 chip is temporarily unavailable, the configuration and distribution will be delayed until the E1 chip is registered and online. At this time, the conference data display status will be "pending distribution".

[0249] Since the E1 server contains registration information for all E1 chips belonging to the MCU device, the E1 server can determine whether it can configure and send call / hang-up resources to the corresponding E1 chip based on the online status of the E1 chip.

[0250] Step S53: The call / hang-up resources of the number are converted into signaling through the E1 chip to obtain response signaling;

[0251] Step S63: Based on the response signaling, the E1 chip performs a call / hang-up operation on the E1 terminal corresponding to the call / hang-up resource of the number.

[0252] After receiving the call / hang-up resource for the number, the E1 server determines whether to issue a call / hang-up command based on the online status of the E1 chip.

[0253] If the E1 chip is online, a call / hang-up command is sent to the E1 chip.

[0254] If the E1 chip is offline, the status will be reported to the MCU server for manual processing.

[0255] The E1 chip performs signaling conversion based on call / hang-up commands. Specifically, it converts the issued call / hang-up commands into responsive H.320 signaling and processes the call / hang-up calls to the E1 terminal through the E1 leased line.

[0256] In this embodiment, when the conference resource in the step of acquiring conference resources is a call / hang-up resource for a number, the call / hang-up resource is acquired by sending it to the WEB server. The WEB server then sends the call / hang-up resource to the corresponding MCU server. The MCU server parses whether the call / hang-up resource is an E1 resource. If it is, the MCU server matches the corresponding E1 server and E1 chip, constructs a message, and sends the call / hang-up resource to the corresponding E1 server and E1 chip. The E1 chip performs signaling conversion on the call / hang-up resource to obtain response signaling. Based on the response signaling, the E1 chip performs a call / hang-up operation on the E1 terminal corresponding to the call / hang-up resource. This achieves the technical effect of joint management of call / hang-up resources by the WEB server and MCU server.

[0257] Furthermore, embodiments of the present invention also propose a communication resource management device, the communication resource management device comprising:

[0258] The acquisition module is used to acquire meeting resources to the web server;

[0259] The transmission module is used to send the conference resources to the MCU server corresponding to the conference resources through the WEB server;

[0260] The parsing module is used to parse whether the conference resource is an E1 resource through the MCU server;

[0261] The matching module is used to match the corresponding E1 server and E1 chip through the MCU server if the meeting resource is an E1 resource.

[0262] The module is used to create and send messages, distributing the meeting resources to the corresponding E1 server and the corresponding E1 chip.

[0263] Specifically, refer to Figure 10 , Figure 10 This is a schematic diagram of the communication resource management device of the present invention. It acquires conference resources from the WEB server and then distributes these resources to the corresponding MCU server. The MCU server parses whether the conference resource is an E1 resource. If it is, the MCU server matches the corresponding E1 server and E1 chip, assembles a message, and distributes the conference resource to the corresponding E1 server and E1 chip. By using the MCU and WEB server to jointly manage conference resources, and adding a new field to the communication message for easy identification of the conference resources, this invention solves the technical problem of not being able to expand and be compatible with E1 conferencing capabilities on the current IP MCU basis. It expands the technology stack for multi-terminal video conferencing and improves the stability of multi-terminal video conferencing.

[0264] In this embodiment, conference resources are acquired from the web server and then distributed to the corresponding MCU server via the web server. The MCU server parses whether the conference resource is an E1 resource. If the conference resource is an E1 resource, the MCU server matches the corresponding E1 server and E1 chip, assembles a distribution message, and distributes the conference resource to the corresponding E1 server and E1 chip. By using the MCU and web server to jointly manage conference resources and adding a new field to the communication message to facilitate the identification of the conference resource, the technical problem of not being able to expand and be compatible with E1 conferencing capabilities on the current IP MCU basis is solved. This expands the technology stack for multi-terminal video conferencing and improves the stability of multi-terminal video conferencing.

[0265] Furthermore, the present invention also provides a terminal device, the terminal device including a memory, a processor, and a communication resource management program stored in the memory and executable on the processor, wherein the communication resource management program, when executed by the processor, implements the steps of the communication resource management method as described above.

[0266] Since this communication resource management program employs all the technical solutions of all the foregoing embodiments when executed by the processor, it has at least all the beneficial effects brought about by all the technical solutions of all the foregoing embodiments, which will not be repeated here.

[0267] Furthermore, the present invention also provides a computer-readable storage medium storing a communication resource management program, which, when executed by a processor, implements the steps of the communication resource management method described above.

[0268] Since this communication resource management program employs all the technical solutions of all the foregoing embodiments when executed by the processor, it has at least all the beneficial effects brought about by all the technical solutions of all the foregoing embodiments, which will not be repeated here.

[0269] Compared to existing technologies, the communication resource management method, apparatus, terminal device, and storage medium proposed in this invention acquire conference resources and check whether the WEB server has successfully connected with the MCU server corresponding to the conference resources. If the WEB server and the MCU server are successfully connected, the conference resources are sent from the WEB server to the MCU server. The MCU server then parses whether the conference resources are E1 resources. If the conference resources are E1 resources, the MCU server matches the corresponding E1 server and E1 chip. After the MCU server successfully matches the corresponding E1 server and E1 chip, it assembles a message to send the conference resources to the corresponding E1 server and E1 chip. By using the MCU and WEB server to jointly manage conference resources and adding new fields to the communication messages to facilitate the identification of conference resources, this invention solves the technical problem of not being able to expand and be compatible with E1 conferencing capabilities on the basis of current IP MCUs, expands the technology stack for multi-terminal video conferencing, and improves the stability of multi-terminal video conferencing.

[0270] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0271] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0272] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, controlled terminal, or network device, etc.) to execute the methods of each embodiment of this application.

[0273] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A communication resource management method, characterized in that: The communication resource management method is applied to a communication resource management system, the communication resource management system includes an MCU server, an E1 server, an E1 chip, and a WEB server, and the communication resource management method includes: Acquire conference resources from the WEB server; Sending the conference resource to the MCU server corresponding to the conference resource through the WEB server; Based on the value of the corresponding message field in the conference resource, the MCU server analyzes whether the conference resource is an E1 resource; If the conference resource is an E1 resource, the MCU server matches the corresponding E1 server and E1 chip according to the E1 venue number of the E1 resource, wherein the E1 venue number is composed of: MCU server registration number prefix + E1 server slot number + E1 number start index number + E1 number end index number; The message is sent to send the conference resources to the corresponding E1 server and the corresponding E1 chip; Wherein, when the conference resource in the step of obtaining the conference resource is a number resource, the step of forming a message to send the conference resource to the corresponding E1 server and the corresponding E1 chip includes: Build and send messages, and select the appropriate method for sending number resources based on number resources; Based on the appropriate method for issuing number resources, the number resources are issued to the corresponding E1 server and the corresponding E1 chip; Wherein, when the conference resource in the step of obtaining the conference resource is a resource of adding, deleting or modifying a number, the step of forming a message to send the conference resource to the corresponding E1 server and the corresponding E1 chip includes: The MCU server operates the number resources corresponding to the E1 chip based on the number addition, deletion and modification resources; The component sends a message to refresh the E1 chip through the E1 server; Wherein, when the conference resource in the step of obtaining the conference resource is a call / hang-up resource of a number, the step of forming a message to send the conference resource to the corresponding E1 server and the corresponding E1 chip includes: Performing signaling conversion on the call / hang-up resource of the number through the E1 chip to obtain a response signaling; Based on the response signaling, the E1 chip performs a call / hang-up operation on the E1 terminal corresponding to the call / hang-up resource of the number.

2. The communication resource management method according to claim 1, characterized in that: The step of forming a message to send the conference resources to the corresponding E1 server and the corresponding E1 chip includes: Sending a message based on the conference resource formation to obtain a message resource; Sending the message resource to the corresponding E1 server through the MCU server; The E1 server matches the corresponding E1 chip based on the message resources and sends the message resources to the corresponding E1 chip.

3. The communication resource management method according to claim 2, characterized in that: The step of matching the corresponding E1 chip based on the message resource by the E1 server and sending the message resource to the corresponding E1 chip comprises: Initialize the E1 server; Obtaining location information of the E1 server; Performing position detection on the E1 chip based on the position information; If the location detection is successful, check whether the E1 chip has conference resources to be issued; If the E1 chip has conference resources to be sent, the E1 resources are sent to the E1 chip through the E1 server.

4. The communication resource management method according to claim 1, characterized in that: The communication resource management system further includes an IP terminal, and after the step of parsing whether the conference resource is an E1 resource by the MCU server, the following steps are further included: If the conference resource is an IP resource, the MCU server matches the corresponding IP terminal; A message is sent to send the conference resources to the IP terminal through the MCU server.

5. A communication resource management device, characterized in that: The communication resource management device comprises: The acquisition module is used to acquire conference resources from the WEB server; A transmission module, used for sending the conference resources to the MCU server corresponding to the conference resources through the WEB server; A parsing module, configured to parse, through the MCU server, whether the conference resource is an E1 resource based on the value of the corresponding message field in the conference resource; A matching module, for matching the corresponding E1 server and E1 chip according to the E1 venue number of the E1 resource through the MCU server if the conference resource is an E1 resource, wherein the E1 venue number is composed of: MCU server registration number prefix + E1 server slot number + E1 number start index number + E1 number end index number; A building module, used for building and sending messages, sending the conference resources to the corresponding E1 server and the corresponding E1 chip; Wherein, when the conference resource in the step of obtaining the conference resource in the obtaining module is a number resource, the forming module is further used to: form a message to be sent, and select a suitable method for sending the number resource based on the number resource; Based on the appropriate method for issuing number resources, the number resources are issued to the corresponding E1 server and the corresponding E1 chip; Wherein, when the conference resource in the step of acquiring the conference resource in the acquisition module is a number addition, deletion, and modification resource, the assembly module is further used to: operate the number resource corresponding to the E1 chip based on the number addition, deletion, and modification resource through the MCU server; The component sends a message to refresh the E1 chip through the E1 server; Wherein, when the conference resource in the step of obtaining the conference resource in the obtaining module is a call / hang-up resource of a number, the forming module is further used to: perform signaling conversion on the call / hang-up resource of the number through the E1 chip to obtain a response signaling; Based on the response signaling, the E1 chip performs a call / hang-up operation on the E1 terminal corresponding to the call / hang-up resource of the number.

6. A terminal device, characterized in that: The terminal device includes a memory, a processor, and a communication resource management program stored in the memory and executable on the processor. When the communication resource management program is executed by the processor, the steps of the communication resource management method as described in any one of claims 1 to 4 are implemented.

7. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a communication resource management program, and when the communication resource management program is executed by the processor, the steps of the communication resource management method according to any one of claims 1 to 4 are implemented.

Images