CN117939058A - Method, device, equipment and medium for processing conference service request - Google Patents

Method, device, equipment and medium for processing conference service request Download PDF

Info

Publication number
CN117939058A
CN117939058A CN202410193814.5A CN202410193814A CN117939058A CN 117939058 A CN117939058 A CN 117939058A CN 202410193814 A CN202410193814 A CN 202410193814A CN 117939058 A CN117939058 A CN 117939058A
Authority
CN
China
Prior art keywords
service
request
nodes
node
processing
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202410193814.5A
Other languages
Chinese (zh)
Inventor
郭翔宇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Haoxin Cloud Beijing Network Communication Co ltd
Original Assignee
Haoxin Cloud Beijing Network Communication Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Haoxin Cloud Beijing Network Communication Co ltd filed Critical Haoxin Cloud Beijing Network Communication Co ltd
Priority to CN202410193814.5A priority Critical patent/CN117939058A/en
Publication of CN117939058A publication Critical patent/CN117939058A/en
Pending legal-status Critical Current

Links

Landscapes

  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The embodiment of the application provides a method, a device, equipment and a medium for processing a conference service request, wherein the method is executed by a service gateway in a conference system, the conference system comprises a client, the service gateway, a website server and a plurality of service nodes, and the method comprises the following steps: acquiring a service request of the client after domain name resolution, which is sent by the website server; selecting a service node for processing the service request from the plurality of service nodes according to the locally stored service information of the plurality of service nodes, wherein the service information of the plurality of service nodes is acquired by the service gateway when the plurality of service nodes are started; the service request is sent to a service node for processing the service request. By the technical scheme of the embodiment of the application, the delay of processing the service request can be reduced.

Description

Method, device, equipment and medium for processing conference service request
Technical Field
The present application relates to the field of video conferencing, and in particular, to a method, apparatus, device, and medium for processing a conference service request.
Background
In order to meet the requirements of high concurrency and high traffic, various existing services, such as Web Real-time communication (WebRTC) video conference service, mini-service, etc., all adopt distributed cluster services, in which application services can be deployed on multiple servers, and then load balancing is performed through Web servers, such as nmlnx. However, for some services, unified load balancing with nginnx may have a problem of network delay.
Therefore, how to provide a low-latency processing service is a problem to be solved.
Disclosure of Invention
An object of an embodiment of the present application is to provide a method, an apparatus, a device, and a medium for processing a conference service request, where a delay in processing a service can be reduced by using a technical solution of the embodiment of the present application.
In a first aspect, an embodiment of the present application provides a method for processing a conference service request, the method being performed by a service gateway in a conference system, the conference system including a client, the service gateway, a website server, and a plurality of service nodes, the method comprising: acquiring a service request of the client after domain name resolution, which is sent by the website server; selecting a service node for processing the service request from the plurality of service nodes according to the locally stored service information of the plurality of service nodes, wherein the service information of the plurality of service nodes is acquired by the service gateway when the plurality of service nodes are started; the service request is sent to a service node for processing the service request.
The service gateway can directly forward the request to the corresponding service node according to the locally stored information, and the gateway can solve the problem of network delay in the prior art because the gateway does not need to go to a registration center to acquire registration information.
In one embodiment, before selecting a service node for processing the service request from the plurality of service nodes based on the locally stored service information of the plurality of service nodes, the method further comprises: and analyzing the service request to determine that the service request is legal.
In one embodiment, the selecting a service node from the plurality of service nodes for processing the service request according to the locally stored service information of the plurality of service nodes includes: selecting a service node group for processing the service request from the plurality of service nodes according to the service identifier in the service request, wherein the service node group comprises at least one service node, and one service node group corresponds to one service; selecting a service node for processing the service request from a group of service nodes for processing the service request according to a load balancing policy.
In one embodiment, before obtaining the service request of the client after domain name resolution sent by the website server, the method further includes: receiving service information of the plurality of service nodes, wherein the plurality of service nodes comprise service nodes in an initial service scale and/or expanded service nodes; dividing the plurality of service nodes into at least one node group according to the service information of the plurality of service nodes, wherein each node group comprises at least one service node, and one service node group corresponds to one service.
In one embodiment, the method further comprises: acquiring a communication message of a first node from the plurality of service nodes; forwarding the communication message to the second node.
In one embodiment, the method further comprises: acquiring a heartbeat request sent by each service node in the plurality of service nodes, wherein the heartbeat request carries the heartbeat time of each service node; updating the heartbeat time of each service node according to the heartbeat request; and updating the states of the plurality of service nodes according to the heartbeat time of each service node.
In one embodiment, the plurality of service nodes comprises a plurality of media distribution servers or a plurality of media mixed stream servers.
In a second aspect, an embodiment of the present application provides an apparatus for processing a conference service request, the apparatus being applied to a service gateway in a conference system, the conference system including a client, the service gateway, a website server, and a plurality of service nodes, the apparatus comprising: the acquisition unit is used for acquiring the service request of the client after domain name resolution, which is sent by the website server; a processing unit, configured to select a service node for processing the service request from the plurality of service nodes according to locally stored service information of the plurality of service nodes, where the service information of the plurality of service nodes is acquired by the service gateway when the plurality of service nodes are started; and the sending unit is used for sending the service request to a service node for processing the service request.
In one embodiment, the processing unit is further configured to parse the service request and determine that the service request is legal before the selecting unit selects a service node for processing the service request from the plurality of service nodes according to the locally stored service information of the plurality of service nodes.
In one embodiment, the processing unit is specifically configured to select, from the plurality of service nodes, a service node group for processing the service request according to a service identifier in the service request, where the service node group includes at least one service node, and one service node group corresponds to one service; selecting a service node for processing the service request from a group of service nodes for processing the service request according to a load balancing policy.
In one embodiment, the obtaining unit is further configured to receive service information of the plurality of service nodes before obtaining the service request of the client after domain name resolution sent by the website server, where the plurality of service nodes include service nodes in an initial service scale and/or expanded service nodes; the processing unit is further configured to divide the plurality of service nodes into at least one node group according to service information of the plurality of service nodes, where each node group includes at least one service node, and one service node group corresponds to one service.
In one embodiment, the obtaining unit is further configured to obtain a communication message sent by a first node to a second node in the plurality of service nodes; the sending unit is further configured to forward the communication message to the second node.
In an embodiment, the obtaining unit is further configured to obtain a heartbeat request sent by each service node in the plurality of service nodes, where the heartbeat request carries a heartbeat time of each service node; the processing unit is further used for updating the heartbeat time of each service node according to the heartbeat request; and updating the states of the plurality of service nodes according to the heartbeat time of each service node.
In one embodiment, the plurality of service nodes comprises a plurality of media distribution servers or a plurality of media mixed stream servers.
In a third aspect, an embodiment of the present application provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs the method according to any of the first aspect and the implementation manner of the first aspect.
In a fourth aspect, an embodiment of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor can implement the method according to any implementation of the first aspect and the first aspect when executing the program.
In a fifth aspect, an embodiment of the present application provides a computer program product, the computer program product comprising a computer program, wherein the computer program, when executed by a processor, is capable of implementing a method according to any implementation of the first aspect or the first aspect.
Drawings
In order to more clearly illustrate the technical solution of one embodiment of the present application, the following description will briefly explain the drawings required to be used in one embodiment of the present application, it being understood that the following drawings illustrate only some embodiments of the present application and are therefore not to be considered limiting of the scope, since other related drawings may be obtained by those skilled in the art without inventive effort.
FIG. 1 is a schematic diagram of a conventional cluster service system;
fig. 2 is a schematic diagram of a conference cluster service system according to an embodiment of the present application;
FIG. 3 is a flow chart of a method for handling a conference service request provided by one embodiment of the present application;
Fig. 4 is a schematic diagram of an apparatus for processing a conference service request according to an embodiment of the present application;
fig. 5 is a schematic diagram illustrating an internal module of a service gateway according to an embodiment of the present application;
Fig. 6 is a schematic diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application.
In the existing cluster service, application service can be deployed on a plurality of servers, and then load balancing is performed through Nginx. Fig. 1 is a schematic diagram of a conventional cluster service system, where the cluster service system shown in fig. 1 includes a client, a web server (e.g., nginnx), a plurality of service gateways, a service registry, and a plurality of service nodes.
In the system shown in fig. 1, the service gateway may be a component that is a direct request, and the downstream service information is basically obtained through a service registry component, and after the nginx obtains the service request, load balancing is performed to determine a corresponding service gateway, and the service gateway obtains the registration information of the service node through the registry to forward the request to the corresponding service node. In the service manner shown in fig. 1, load balancing is performed through a website server, so that the service gateway needs to acquire registration information of a service node through a registration center, which results in higher cost, difficult subsequent maintenance and certain requirements on the number of servers and hardware.
In view of the above problems, the present application provides a method for processing a conference service request, which can rely on a service gateway as an external access point, and provide a service registration function in the service gateway, where downstream service (i.e. a service of a service node) can be registered through a relevant interface, and after the service gateway receives the registration, service information is saved, and then the corresponding service node can be directly forwarded to the request according to locally stored information. The service gateway does not need to go to the registration center to acquire the registration information, so the embodiment of the application can solve the problem of network delay in the prior art.
In the following, for ease of understanding and explanation, by way of example and not limitation, the execution process and actions of the method of real-time communication of the present application in a real-time communication system will be described.
A schematic view of a conference cluster service system according to an embodiment of the present application is exemplarily described below with reference to fig. 2.
The system as shown in fig. 2 includes: the system comprises a client, a website server, a service gateway and a plurality of service nodes.
In the embodiment of the application, the client can also be called a user terminal, user equipment or terminal equipment, and in the real-time embodiment of the application, the terminal equipment can be provided with a browser and can carry out real-time communication through the browser, or an APP or an applet is installed and carries out real-time communication through the APP or the applet. The terminal device in the present application may include a smart phone, a tablet computer, (personal DIGITAL ASSISTANT, PDA personal digital assistant), a computer, a game machine, a wearable device, a tablet computer (portable android device, PAD), etc., which is not limited thereto.
It should be understood that the operating system running on the electronic device may be a Linux kernel-based operating system such as Android (Android) mobile version, ubuntu (Ubuntu) mobile version, tazier (Tizen) or the like, and a desktop operating system such as Windows, mac OS, linux or the like, but the present invention is not limited thereto.
In the embodiment of the present application, a terminal device may refer to an access terminal, a User Equipment (UE), a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initia tion Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a Personal digital assistant (Personal DIGITAL ASSISTANT, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN), etc.
In the embodiment of the application, the website server can be used for carrying out domain name resolution on the service request, and then sending the resolved service request to the service gateway. The website server may be Nginx, apache, IIS, and the website server is hereinafter exemplified by ng ginx, but the embodiment of the application is not limited thereto.
In the embodiment of the present application, the number of service gateways shown in fig. 2 is one, after the website server resolves the domain name of the service request, the request is directly forwarded to only the service gateway, and the service gateway can be used to obtain registration information of the service node when the service node is started, and after the service request is obtained, load balancing is performed to select the corresponding service node.
In the embodiment of the application, the service node is used for providing corresponding service, the service node can send the registration information to the service gateway when being started, for example, after the service node is started, the service node registers the service information to the gateway through an http interface built in the gateway, and periodically initiates a heartbeat request to the gateway, the gateway can update the heartbeat time of the current node every time the heartbeat request is sent, and can calculate whether the service node is in a health state according to the interval time, and if not, the service node can be subjected to weight reduction treatment.
It should be understood that in the embodiment of the present application, the service node may be a media distribution server or a media mixed stream server.
The media distribution server may also be called a data stream forwarding server or media server or selective forwarding unit (SELECTIVE FORWARDING UNIT, SFU) server. In the embodiment of the application, the media distribution server can receive the data streams sent by each client in the same conference room, send the data streams to the media mixed stream server, receive the unified media streams sent by the media mixed stream server, and send the unified media streams to the clients. Or the media distribution server receives the data streams sent by each client, and then carries out mixed stream and forwards the data streams to the client, or directly sends the data streams to the corresponding client without carrying out mixed stream.
The media mixed stream server may also be called a mixed stream server or a multipoint conference unit (Multipoint Conferencing Unit, MCU) server, and in the embodiment of the present application, the media mixed stream server may receive media streams of each client in the same conference room sent by the media distribution server, and perform mixed stream (i.e. mixed encoding) on media streams of all terminals, and send the unified media stream after mixed stream to the media distribution server.
A method for handling conference service requests according to an embodiment of the application is exemplarily described below with reference to fig. 3.
The method shown in fig. 3 may be applied to a service gateway in the system shown in fig. 2, and the method shown in fig. 3 includes:
310, obtaining a service request of the client after domain name resolution sent by the website server.
Specifically, the client first sends a service request to a web server, such as nginnx, which performs domain name resolution on the service request, and then sends the service request to the service gateway.
In the embodiment of the application, the website server is not responsible for load balancing distribution, and sends the service request to the unique service gateway after resolving the domain name of the service request. The service gateway performs load balancing distribution.
Optionally, as another embodiment, before obtaining the service request of the client after domain name resolution sent by the website server, the method may further include:
receiving service information of the plurality of service nodes, wherein the plurality of service nodes comprise service nodes in an initial service scale and/or expanded service nodes;
Dividing the plurality of service nodes into at least one node group according to the service information of the plurality of service nodes, wherein each node group comprises at least one service node, and one service node group corresponds to one service.
Specifically, after the service gateway obtains the registration information (i.e., service information) of the service nodes, the service nodes are grouped according to the metadata specific service identifier in the service information, and the service nodes in the same class are divided into node groups, where one node group may correspond to a service registry in a load balancing component.
In the embodiment of the application, in the capacity expansion scene of the service node, the service node sends the metadata to the service gateway, and the configuration information in the website server is not changed, so that the website server does not need to be restarted during capacity expansion, and the continuity of the service can be ensured.
Optionally, as another embodiment, the method may further include:
Acquiring a heartbeat request sent by each service node in the plurality of service nodes, wherein the heartbeat request carries the heartbeat time of each service node;
updating the heartbeat time of each service node according to the heartbeat request;
and updating the states of the plurality of service nodes according to the heartbeat time of each service node.
Specifically, after the service node is started, service information can be registered on the service gateway through an http interface built in the service gateway, a heartbeat request is periodically initiated to the service gateway, the service gateway can update the heartbeat time of the current service node every time the heartbeat request is sent, meanwhile, whether the service node is in a health state or not can be calculated according to the interval time, and if the service node is unhealthy, the service node can be subjected to weight reduction processing, for example, processing such as deleting the service node from a service registry according to the heartbeat time.
It should be understood that, in the embodiment of the present application, the service information of the service node may include metadata information, including, for example, an IP address, a port number, a service identifier, a service weight, or other configuration information, and the embodiment of the present application is not limited thereto.
After the service node successfully registers to the service gateway, that is, after the service gateway acquires the registration information of the service node, the service gateway divides the service registry according to the prefix in the registration information and mounts the service registry on the load balancing component, and after the service node acquires the service request, the corresponding service node is selected through the load balancing component.
It should be understood that each service can only have a unique identifier in the service gateway, and when a service request enters the service gateway, the service gateway determines, according to the prefix identifier, to which service needs to be forwarded, where each service corresponds to a service registry, and the load balancing component further selects a service node for processing the service request according to the load condition of the service node corresponding to the service registry.
Alternatively, as an embodiment, the plurality of service nodes in the embodiment of the present application may include a plurality of media distribution servers or a plurality of media mixed stream servers.
The service request in the corresponding embodiment of the present application may be a connection establishment request, a data stream sending request, a data stream forwarding request, etc., which is not limited to this embodiment of the present application.
And 320, selecting a service node for processing the service request from the plurality of service nodes according to the locally stored service information of the plurality of service nodes, wherein the service information of the plurality of service nodes is acquired by the service gateway when the plurality of service nodes are started.
Optionally, as an embodiment, the selecting a service node for processing the service request from the plurality of service nodes according to the locally stored service information of the plurality of service nodes includes:
selecting a service node group for processing the service request from the plurality of service nodes according to the service identifier in the service request, wherein the service node group comprises at least one service node, and one service node group corresponds to one service;
Selecting a service node for processing the service request from a group of service nodes for processing the service request according to a load balancing policy.
For example, the service gateway may group the service nodes according to the registration information (i.e., the service information), for example, at least one service registry is included in a load balancing component in the service gateway, where a service registry corresponds to a service node group, and one service node group includes service nodes of the same type of service.
Optionally, when the service request enters the service gateway, the service gateway may also first use the service request filtering component to filter, then enter the forwarding component to forward, the forwarding component may call the load balancing component to obtain the service node to be forwarded, and then forward the request
It should be understood that in the embodiment of the application, the filtering component is mainly used for analyzing the message of the http request to determine whether the request is legal or not, and the illegal request can be automatically filtered, so that the downstream service can be ensured not to be infringed by the illegal request, and the safety of the downstream service is ensured to a certain extent.
Correspondingly, as another embodiment, before selecting a service node for processing the service request from the plurality of service nodes according to the service information of the plurality of service nodes acquired in advance, the method may further include:
and analyzing the service request to determine that the service request is legal.
330 Sending the service request to a service node for processing the service request.
After the service gateway determines the service node for processing the service request through the load balancing component, the service request is sent to the service node through the forwarding component.
Optionally, as another embodiment, the method may further include: acquiring a communication message of a first node from the plurality of service nodes; forwarding the communication message to the second node.
Specifically, in the embodiment of the application, since all service nodes are registered on the service gateway, metadata of all service nodes are available on the service gateway. In this way, the service nodes can realize communication among the service nodes through forwarding of the service gateway. In the embodiment of the application, the communication between different service nodes can be realized only through the forwarding of the service gateway without the participation of other nodes, so the embodiment of the application can realize the rapid communication between the nodes and save network resources.
The embodiment of the application directly registers the service node registration information to the gateway, and the gateway performs service equalization to determine the service node for processing the service request, thereby having the following beneficial effects:
The service gateway directly forwards the service without querying the service registration center again, so that a certain network delay can be reduced.
By integrating service gateway with service registration and gateway functionality, the system architecture can be simplified to some extent.
Meanwhile, in the embodiment of the application, the client does not need to care about the load balancing logic of the service, and only needs to send the request to the gateway, so that the logic of the client can be simplified, and the complexity of the implementation and maintenance work of the client are reduced.
In the embodiment of the application, because only one gateway exists, all requests entering the system pass through a single entry (gateway), thereby being convenient for monitoring and flow management and realizing unified request log record, monitoring and security check at the gateway level.
The embodiment of the application can realize the dynamic adjustment request distribution of the gateway according to the health state and the current load of the back-end service through the heartbeat request mechanism.
In the embodiment of the application, when the back-end service fails, the gateway can reroute the traffic to the healthy instance, thereby improving the availability of the whole system. Support to smoothly expand or contract service instances in response to changes in system load. Thus, usability and flexibility of the system can be improved:
The service gateway in the embodiment of the application can be integrated with a service discovery mechanism to automatically sense the change of the back-end service instance. There is no need to manually update or configure the address of the service instance.
Because the service node registers to the service gateway, the embodiment of the application can realize complex routing decisions based on various parameters (such as the source of the request, head information, paths and the like) and can realize flexible routing strategies.
Referring to fig. 4, fig. 4 is a block diagram illustrating an apparatus for processing a conference service request according to an embodiment of the present application. The apparatus 400 shown in fig. 4 may be a service gateway, and it should be understood that, corresponding to the service gateway in the foregoing method embodiment, the apparatus 400 is capable of executing each step executed by the service gateway in the foregoing method embodiment, and specific functions of the apparatus 400 may be referred to the foregoing description, and detailed descriptions are omitted herein as appropriate to avoid redundancy.
The apparatus 400 shown in fig. 4 includes at least one software functional module that can be stored in a memory in the form of software or firmware or cured in the apparatus, and the apparatus 400 shown in fig. 4 includes: an obtaining unit 410, configured to obtain a service request of the client after domain name resolution sent by the website server; a processing unit 420, configured to select a service node for processing the service request from the plurality of service nodes according to locally stored service information of the plurality of service nodes, where the service information of the plurality of service nodes is acquired by the service gateway when the plurality of service nodes are started; and a transmitting unit 430, configured to transmit the service request to a service node for processing the service request.
In one embodiment, the processing unit is further configured to parse the service request and determine that the service request is legal before the selecting unit selects a service node for processing the service request from the plurality of service nodes according to the locally stored service information of the plurality of service nodes.
In one embodiment, the processing unit is specifically configured to select, from the plurality of service nodes, a service node group for processing the service request according to a service identifier in the service request, where the service node group includes at least one service node, and one service node group corresponds to one service; selecting a service node for processing the service request from a group of service nodes for processing the service request according to a load balancing policy.
In one embodiment, the obtaining unit is further configured to receive service information of the plurality of service nodes before obtaining the service request of the client after domain name resolution sent by the website server, where the plurality of service nodes include service nodes in an initial service scale and/or expanded service nodes; the processing unit is further configured to divide the plurality of service nodes into at least one node group according to service information of the plurality of service nodes, where each node group includes at least one service node, and one service node group corresponds to one service.
In one embodiment, the obtaining unit is further configured to obtain a communication message sent by a first node to a second node in the plurality of service nodes; the sending unit is further configured to forward the communication message to the second node.
In an embodiment, the obtaining unit is further configured to obtain a heartbeat request sent by each service node in the plurality of service nodes, where the heartbeat request carries a heartbeat time of each service node; the processing unit is further used for updating the heartbeat time of each service node according to the heartbeat request; and updating the states of the plurality of service nodes according to the heartbeat time of each service node.
In one embodiment, the plurality of service nodes comprises a plurality of media distribution servers or a plurality of media mixed stream servers.
By way of example and not limitation, fig. 5 provides a schematic diagram of internal module components of a service gateway according to an embodiment of the present application, where, as shown in fig. 5, the service gateway may include a forwarding component, a log component, a request filtering component, an api interface component, and a load balancing component, where the service gateway may record registration information of a service node through the log component and classify the service node into a service registry in the load balancing component, the service gateway may further obtain a service request through the api interface component, verify validity of the service request through the request filtering component, determine a service node for processing the service request through the load balancing component, and finally send the service request to a corresponding service node through the forwarding component.
It will be clear to those skilled in the art that, for convenience and brevity of description, reference may be made to the corresponding procedure in the foregoing method for the specific working procedure of the apparatus described above, and this will not be repeated here.
As shown in fig. 6, one embodiment of the present application provides an electronic device 600, the electronic device 600 comprising: memory 610, processor 620, and a computer program stored on memory 610 and executable on processor 620, wherein processor 620, when reading the program from memory 610 and executing the program via bus 630, may implement the method performed by the service gateway as in any of the embodiments described above. Optionally, the device shown in fig. 6 may also include a transceiver, which may be used for transmission and/or reception of data streams. Alternative electronic device 600 may also include other input devices or other hardware devices, etc., and embodiments of the application are not limited in this respect.
The processor 620 may process the digital signals and may include various computing structures. Such as a complex instruction set computer architecture, a reduced instruction set computer architecture, or an architecture that implements a combination of instruction sets. In some examples, the processor 620 may be a microprocessor.
Memory 610 may be used for storing instructions to be executed by processor 620 or data related to execution of the instructions. Such instructions and/or data may include code to implement some or all of the functions of one or more of the modules described in embodiments of the present application. The processor 620 of the disclosed embodiments may be configured to execute instructions in the memory 610 to implement the methods illustrated above that are performed by a control or client. Memory 610 includes dynamic random access memory, static random access memory, flash memory, optical memory, or other memory known to those skilled in the art.
An embodiment of the present application also provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method performed by a service gateway in any of the above methods as provided in the above embodiments.
An embodiment of the present application also provides a computer program product, where the computer program product includes a computer program, where the computer program when executed by a processor may implement a method performed by a service gateway in any of the above methods provided in the above embodiments.
It should be noted that the processor (e.g., the processor of fig. 6) in embodiments of the present invention may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (field programmable GATE ARRAY, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
It will be appreciated that the memory in embodiments of the invention (e.g., the memory of FIG. 6) may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an erasable programmable ROM (erasable PROM), an electrically erasable programmable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as external cache memory. By way of example, and not limitation, many forms of RAM are available, such as static random access memory (STATIC RAM, SRAM), dynamic random access memory (DYNAMIC RAM, DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (doubledata RATE SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (ENHANCED SDRAM, ESDRAM), synchronous link dynamic random access memory (SYNCHLINK DRAM, SLDRAM), and direct memory bus random access memory (direct rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
Applications to which embodiments of the present application relate include any application installed on a requesting end, including but not limited to, browser, email, instant messaging service, word processing, keyboard virtualization, widgets (widgets), encryption, digital rights management, voice recognition, voice replication, positioning (e.g., functions provided by the global positioning system), music playback, and so forth.
It should be understood that the transceiver unit or transceiver in the embodiments of the present invention may also be referred to as a communication unit.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present invention are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a solid-state disk (solid-state drive STATE DISK, SSD)), or the like.
As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between 2 or more computers. Furthermore, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with one another in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).
It should be appreciated that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It should be understood that, in various embodiments of the present invention, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present invention.
In addition, the terms "system" and "network" are often used interchangeably herein. The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
It should be understood that in embodiments of the present invention, "B corresponding to a" means that B is associated with a, from which B may be determined. It should also be understood that determining B from a does not mean determining B from a alone, but may also determine B from a and/or other information.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps described in connection with the embodiments disclosed herein may be embodied in electronic hardware, in computer software, or in a combination of the two, and that the elements and steps of the examples have been generally described in terms of function in the foregoing description to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of elements is merely a logical functional division, and there may be additional divisions of actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices, or elements, or may be an electrical, mechanical, or other form of connection.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiment of the present invention.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
In summary, the foregoing description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims (10)

1. A method for handling a conference service request, the method being performed by a service gateway in a conference system, the conference system comprising a client, the service gateway, a web server, a plurality of service nodes, the method comprising:
Acquiring a service request of the client after domain name resolution, which is sent by the website server;
Selecting a service node for processing the service request from the plurality of service nodes according to the locally stored service information of the plurality of service nodes, wherein the service information of the plurality of service nodes is acquired by the service gateway when the plurality of service nodes are started;
the service request is sent to a service node for processing the service request.
2. The method of claim 1, wherein the step of determining the position of the substrate comprises,
Before selecting a service node from the plurality of service nodes for processing the service request based on locally stored service information of the plurality of service nodes, the method further comprises:
and analyzing the service request to determine that the service request is legal.
3. A method according to claim 1 or2, characterized in that,
The selecting a service node for processing the service request from the plurality of service nodes according to the locally stored service information of the plurality of service nodes, comprising:
selecting a service node group for processing the service request from the plurality of service nodes according to the service identifier in the service request, wherein the service node group comprises at least one service node, and one service node group corresponds to one service;
Selecting a service node for processing the service request from a group of service nodes for processing the service request according to a load balancing policy.
4. The method according to claim 1 or 2, wherein before obtaining the service request of the client after domain name resolution sent by the website server, the method further comprises:
receiving service information of the plurality of service nodes, wherein the plurality of service nodes comprise service nodes in an initial service scale and/or expanded service nodes;
Dividing the plurality of service nodes into at least one node group according to the service information of the plurality of service nodes, wherein each node group comprises at least one service node, and one service node group corresponds to one service.
5. The method according to claim 1 or 2, characterized in that the method further comprises:
acquiring a communication message of a first node from the plurality of service nodes;
forwarding the communication message to the second node.
6. The method according to claim 1 or 2, characterized in that the method further comprises:
Acquiring a heartbeat request sent by each service node in the plurality of service nodes, wherein the heartbeat request carries the heartbeat time of each service node;
updating the heartbeat time of each service node according to the heartbeat request;
and updating the states of the plurality of service nodes according to the heartbeat time of each service node.
7. The method according to claim 1 or 2, wherein the plurality of service nodes comprises a plurality of media distribution servers or a plurality of media mixed stream servers.
8. An apparatus for processing a conference service request, the apparatus being applied to a service gateway in a conference system, the conference system comprising a client, the service gateway, a web server, a plurality of service nodes, the apparatus comprising:
The acquisition unit is used for acquiring the service request of the client after domain name resolution, which is sent by the website server;
A processing unit, configured to select a service node for processing the service request from the plurality of service nodes according to locally stored service information of the plurality of service nodes, where the service information of the plurality of service nodes is acquired by the service gateway when the plurality of service nodes are started;
and the sending unit is used for sending the service request to a service node for processing the service request.
9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and running on the processor, wherein the computer program when run by the processor performs the method of any one of claims 1-7.
10. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program, wherein the computer program when run by a processor performs the method according to any of claims 1-7.
CN202410193814.5A 2024-02-21 2024-02-21 Method, device, equipment and medium for processing conference service request Pending CN117939058A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202410193814.5A CN117939058A (en) 2024-02-21 2024-02-21 Method, device, equipment and medium for processing conference service request

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202410193814.5A CN117939058A (en) 2024-02-21 2024-02-21 Method, device, equipment and medium for processing conference service request

Publications (1)

Publication Number Publication Date
CN117939058A true CN117939058A (en) 2024-04-26

Family

ID=90766462

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202410193814.5A Pending CN117939058A (en) 2024-02-21 2024-02-21 Method, device, equipment and medium for processing conference service request

Country Status (1)

Country Link
CN (1) CN117939058A (en)

Similar Documents

Publication Publication Date Title
CN111278031B (en) PDU type setting method, UE strategy setting method, entity and storage medium
CN114025021B (en) Communication method, system, medium and electronic equipment crossing Kubernetes cluster
US11533220B2 (en) Network-assisted consensus protocol
US10389848B2 (en) Message transmission method and core network interface device
EP2648392A1 (en) Application programming interface routing system and method of operating the same
CN112654100B (en) Information processing method and related network equipment
US20170155712A1 (en) Method and device for updating cache data
US20220248207A1 (en) Dynamically switching network cards
US9860736B1 (en) Providing network resource access based on a purpose identifier
US10129320B2 (en) QoS improvement method, apparatus, and system
US20140136597A1 (en) Relay enabled dynamic virtual private network
US20230100519A1 (en) Systems and methods of managing communication endpoints
US11778451B2 (en) 5G Network Exposure Function (NEF) capturing processor identity
CN117939058A (en) Method, device, equipment and medium for processing conference service request
EP4344259A1 (en) Session binding relationship processing method and apparatus, electronic device, and readable medium
WO2021224544A1 (en) Registration in communication networks
WO2022160422A1 (en) Dynamically switching network cards
WO2021160386A1 (en) Authorization service for providing access control
CN110557750B (en) Information transmission method, gateway device, core network device, and storage medium
US20230385139A1 (en) Network api credentials within a translation session
US20050198302A1 (en) Multi-client support
CN118138710A (en) Method, apparatus, device and medium for managing device status in video conference
CN113271229B (en) Equipment control method and device, storage equipment, safety equipment, switch, router and server
CN117440127A (en) Method, device, equipment and medium for processing concurrent consumption in video conference
CN116863970A (en) Multi-application concurrent recording method, system, computer equipment and medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination