CN115037725B

CN115037725B - Account distribution method and device, storage medium and electronic equipment

Info

Publication number: CN115037725B
Application number: CN202210548964.4A
Authority: CN
Inventors: 李雪松
Original assignee: Shenzhen Huantai Technology Co Ltd
Current assignee: Shenzhen Huantai Technology Co Ltd
Priority date: 2022-05-20
Filing date: 2022-05-20
Publication date: 2024-01-05
Anticipated expiration: 2042-05-20
Also published as: CN115037725A

Abstract

The embodiment of the application discloses an account distribution method, an account distribution device, a storage medium and electronic equipment, wherein the method comprises the following steps: receiving an incoming request of a Session Initiation Protocol (SIP) client for a real-time communication (RTC) conference; responding to the incoming call request, determining a SIP gateway corresponding to the incoming call request, wherein the SIP gateway is associated with a plurality of pre-allocated virtual SIP accounts; and determining the virtual SIP account corresponding to the SIP client from a plurality of virtual SIP accounts associated with the SIP gateway. According to the technical scheme of the embodiment of the application, not only can the available virtual SIP account resources of each RTC meeting be ensured, but also the virtual SIP account resources can be recycled, the resource waste in the virtual SIP account allocation is reduced, and the resource utilization rate is improved.

Description

Account distribution method and device, storage medium and electronic equipment

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to an account allocation method, an apparatus, a storage medium, and an electronic device.

Background

With the development of internet technology, the application of audio and video conference systems is also becoming more and more widespread. An audio video conferencing system generally includes an RTC (Real Time Communication, real-time communication) conferencing system and a SIP (Session Initiation Protocol ) conferencing system, the RTC conferencing system being different from the signaling protocol typically employed by SIP conferencing systems.

In some application scenarios, the SIP client may need to communicate with the RTC client in the RTC audio-video conference system, and thus, the SIP service and the RTC service need to be converged. In one technical scheme, based on the SIP gateway, the SIP service and the RTC service are converged, for example, when the SIP client accesses the RTC conference, the SIP signaling protocol and the RTC signaling protocol are mapped and converted after being processed by the SIP gateway, that is, the accessed SIP client is simulated as a virtual RTC client accessing the RTC conference. However, in this technical solution, after the RTC conference is created, a certain number of virtual SIP accounts need to be allocated to the RTC conference, and as the number of conferences increases, a number of idle virtual SIP accounts are accumulated, which causes resource waste.

Therefore, how to reduce the resource waste in the virtual SIP account allocation becomes a technical problem to be solved.

Disclosure of Invention

The embodiment of the application provides an account allocation method, an account allocation device, a storage medium and electronic equipment, which can reduce resource waste in virtual SIP account allocation and improve resource utilization rate. The technical scheme is as follows:

in a first aspect, an embodiment of the present application provides an account allocation method, where the method includes:

Receiving an incoming request of a Session Initiation Protocol (SIP) client for a real-time communication (RTC) conference;

responding to the incoming call request, determining a SIP gateway corresponding to the incoming call request, wherein the SIP gateway is associated with a plurality of preassigned virtual SIP accounts;

and determining the virtual SIP account corresponding to the SIP client from the multiple virtual SIP accounts associated with the SIP gateway.

In a second aspect, an embodiment of the present application provides an account allocation device, where the device includes:

the request receiving module is used for receiving an incoming request of a Session Initiation Protocol (SIP) client for a real-time communication (RTC) conference;

a gateway determining module, configured to determine, in response to the incoming call request, a SIP gateway corresponding to the incoming call request, where the SIP gateway is associated with a plurality of pre-allocated virtual SIP accounts;

and the account assignment module is used for determining the virtual SIP account corresponding to the SIP client from the plurality of virtual SIP accounts associated with the SIP gateway.

In a third aspect, embodiments of the present application provide a computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the steps of the method described above.

In a fourth aspect, embodiments of the present application provide an electronic device, including: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to perform the steps of the method described above.

The technical scheme provided by some embodiments of the present application has the beneficial effects that at least includes:

on one hand, a plurality of virtual SIP accounts associated with the SIP gateway are pre-allocated, and memory fragments caused by continuous allocation and recovery of memory are avoided by adopting the plurality of virtual SIP accounts with global static resources pre-allocated; on the other hand, when the SIP client requests to call in the RTC conference, the virtual SIP account corresponding to the SIP client is determined from the plurality of virtual SIP accounts of the SIP gateway bound with the RTC conference, and because the mode of globally sharing the plurality of virtual SIP accounts is adopted for one-time allocation, not only can the available virtual SIP account resources of each RTC conference be ensured, but also the virtual SIP account resources can be repeatedly utilized, the resource waste in the virtual SIP account allocation is reduced, and the resource utilization rate is improved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 shows a schematic diagram of an application scenario of an account assignment method according to an embodiment of the present application;

fig. 2 illustrates a flow diagram of an account assignment method provided in accordance with some embodiments of the present application;

fig. 3 illustrates a flowchart of an account assignment method provided according to other embodiments of the present application;

fig. 4 illustrates a flowchart of an account assignment method according to further embodiments of the present application;

fig. 5 illustrates a flow diagram of an account assignment method provided according to further embodiments of the present application;

fig. 6 shows a schematic structural diagram of an account number distribution device according to an embodiment of the present application; and

fig. 7 shows a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

First, terms related to the embodiments of the present application will be explained and explained.

SIP (Session Initiation Protocol ): is an application layer control protocol for setting up, modifying and terminating multimedia sessions, which may be IP telephony, multimedia sessions or multimedia conferences. SIP is the core protocol of the IETF multimedia data and control architecture (the latest RFC document is RFC 3261).

Virtual SIP account number: the SIP account corresponding to the simulated RTC client on the SIP gateway is referred to as the virtual SIP account.

RTC (Real Time Communication, real-time communication): the real-time interaction method is short for real-time audio and video, is more generalized RTC technology, is not only limited to audio and video, but also belongs to the category of RTC technology, and comprises instant messaging, pictures, white boards, file sharing and other rich media.

In one technical solution, in order to implement an external SIP client to call into an RTC conference, the RTC client needs to be simulated on a SIP gateway, and the simulated RTC client on the SIP gateway needs to interact with an RTC signaling server not only by HTTP (HyperText Transfer Protocol ), but also by SIP messages, so that a corresponding SIP account needs to be allocated to the simulated RTC client for managing a signaling link for audio and video communication with the SIP client. The SIP account corresponding to the simulated RTC client needs to be globally unique, and the SIP account corresponding to the simulated RTC client is called as a virtual SIP account of the SIP gateway.

Further, after creating the RTC conference, the SIP gateway needs to allocate a fixed number of virtual SIP accounts for the RTC conference in advance, so that the SIP client can join the RTC conference at any time, and in order to support simultaneous joining of multiple SIP clients, in general, one RTC conference needs to allocate multiple virtual SIP accounts bound to the RTC conference in advance, so as to cope with the joining conference of the new SIP client in real time. Therefore, as the number of conferences increases, the virtual SIP account resources consumed by the overall audio-video system will continue to grow for time-to-time. However, in practical applications, it often happens that less SIP clients actually join the conference, and many RTC conference participants may be RTC clients, but the SIP gateway allocates virtual SIP account resources for them.

Furthermore, conference resources are typically reserved for a predetermined period of time, e.g., 24 hours, in the current business scenario, which accumulates many virtual SIP accounts, which are, however, mostly in idle states. Since each registered virtual SIP account consumes SIP gateway and SIP server resources, this results in a lot of resource waste.

Based on the foregoing, the basic idea of an embodiment of the present application is that: after the SIP gateway is started, a preset number of virtual SIP accounts associated with the SIP gateway are distributed in advance, after the RTC conference is started and the SIP client is accessed, an available virtual SIP account is distributed for the SIP client, the virtual SIP account and the RTC conference are associated and bound, after the SIP client calls are released, the virtual SIP account and the RTC conference are released, and account resources of the virtual SIP account are recovered. According to the technical scheme of the embodiment of the application, not only can the available virtual SIP account resources of each RTC meeting be ensured, but also the virtual SIP account resources can be reused to the greatest extent, the resource waste in the virtual SIP account allocation is reduced, and the resource utilization rate is improved.

The following describes in detail the technical solution of the account assignment method according to the embodiment of the present application with reference to the accompanying drawings.

Fig. 1 shows a schematic diagram of an application scenario of an account assignment method according to an embodiment of the present application.

Referring to fig. 1, the application scenario includes a SIP client 105, a SIP server 110, a SIP gateway 115, an RTC server 120, and an RTC client 125. The SIP server 110 is configured to process the SIP incoming call request, create a binding relationship between the SIP gateway and the virtual SIP account, and the like, for example, the SIP server 110 registers a binding relationship between the SIP gateway and the preassigned multiple virtual SIP accounts. The SIP gateway 115 is configured to map and convert the SIP signaling protocol with the RTC signaling protocol, for example, to convert SIP signaling into RTC signaling. The RTC server 120 includes a media server 122 and an RTC signaling processing module 124, where the RTC signaling processing module 124 is configured to process RTC signaling, and the media server 122 is configured to transmit a control media stream.

Further, the SIP client 105 and the SIP server 110 perform signaling interaction through the SIP protocol, the RTC server 120 and the RTC client 125 perform signaling interaction through the RTC protocol, and the SIP gateway 115 may be used as a communication link between the SIP server and the RTC server, for example, the SIP gateway 115 may perform signaling interaction with the SIP server 110 by adopting the SIP protocol on one hand, and may perform signaling interaction with the RTC server 120 by adopting the RTC protocol on the other hand, so as to implement conversion between the SIP protocol and the RTC protocol, and further enable the SIP client 105 to join in the RTC audio-video conference created by the RTC server 120, so as to implement communication between the SIP client 105 and the RTC client 125 in the RTC audio-video conference.

In an example embodiment, SIP client 105 initiates an incoming request for an RTC conference to SIP server 110, SIP server 110 determines a SIP gateway corresponding to the incoming request in response to the incoming request of the SIP client, the SIP gateway being associated with a pre-assigned plurality of virtual SIP accounts; the SIP server 110 determines a virtual SIP account corresponding to the SIP client from among a plurality of virtual SIP accounts associated with the SIP gateway.

Note that, the SIP client 105 and the RTC client 125 may include a smart phone, a notebook computer, a tablet computer, a palm computer, a MID (Mobile Internet Devices, mobile internet device), a desktop computer, a smart tv, a wearable device, a vehicle-mounted device, and the like, which are not limited herein.

The SIP server 110, the SIP gateway 115, and the RTC server 120 may be independent physical servers, or may be a server cluster or a distributed system formed by a plurality of physical servers, or may be cloud servers that provide cloud services, cloud databases, cloud computing, cloud storage, cloud functions, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and basic cloud computing services such as big data and artificial intelligence platforms. SIP gateway 115 may also be deployed on a server.

Fig. 2 illustrates a flow chart of an account assignment method provided according to some embodiments of the present application. The execution subject of the account assignment method may be a computing device having a computing processing function, such as a SIP server or a SIP gateway. The account assignment method includes steps S210 to S230, and the account assignment method in the exemplary embodiment is described in detail below with reference to the accompanying drawings.

Referring to fig. 2, in step S210, an incoming call request of the SIP client for the RTC conference is received.

In an example embodiment, the RTC conference is an RTC audio-visual conference created by the RTC server 120, e.g., the RTC conference may be created based on WebRTC (Web Real-Time Communication ). The SIP client may be a terminal device supporting the SIP protocol, such as a SIP hardware phone including a PSTN (Public Switched Telephone Network ) mobile phone, a PSTN landline phone, etc., an electronic device in which a SIP softphone is installed. The electronic device may include, but is not limited to, a smart phone, a notebook computer, a tablet computer, a palm top computer, a desktop computer, a smart television, a wearable device, a vehicle-mounted device, and the like.

Further, the SIP client initiates an incoming request to the SIP server for the RTC conference, which may include a conference identification, e.g., a conference number, of the RTC conference. The SIP server receives an incoming call request of the SIP client for the RTC conference. In some example embodiments, the SIP server may include an edge SIP server and a hub SIP server, the edge SIP server receiving an incoming request for the RTC conference from the SIP client, forwarding the incoming request to the hub SIP server via the SIP protocol.

It should be noted that, the RTC conference may be an audio-video conference in a teleconference, or may be a live room of a live platform, or may be another suitable audio-video conference, for example, a teleconference or a tele-education classroom, which is also within the scope of the embodiments of the present application.

In step S220, in response to the incoming call request, a SIP gateway corresponding to the incoming call request is determined, where the SIP gateway is associated with the pre-assigned plurality of virtual SIP accounts.

In an example embodiment, the SIP gateway is configured to map the SIP signaling protocol with the RTC signaling protocol, the SIP gateway being associated with a pre-assigned plurality of virtual SIP accounts. The SIP gateway may be used as a communication link between the SIP server and the RTC server, for example, the SIP gateway may use the SIP protocol to perform signaling interaction with the SIP server on one hand, and may use the RTC protocol to perform signaling interaction with the RTC server on the other hand, so as to implement conversion between the SIP protocol and the RTC protocol, and further enable the SIP client to join in the RTC audio-video conference created by the RTC server, so as to implement communication between the SIP client 105 and the RTC client 125 in the RTC audio-video conference.

In an example embodiment, a SIP server, in response to an incoming request for an RTC conference from a SIP client, determines a SIP gateway corresponding to the incoming request, the SIP gateway being associated with a pre-assigned plurality of virtual SIP accounts.

Further, in some example embodiments, the SIP gateway corresponding to the incoming request of the SIP client may be determined in the following two ways.

Mode one:

if the incoming call request is the first incoming call request of the RTC conference, determining the SIP gateway corresponding to the incoming call request from a plurality of SIP gateways in a load balancing mode, and establishing the corresponding relation between the conference identifier of the RTC conference in the incoming call request and the SIP gateway.

If the incoming call request is not the first incoming call request of the RTC conference, the conference identification of the RTC conference contained in the incoming call request is acquired, and the SIP gateway corresponding to the incoming call request is determined based on the corresponding relation between the conference identification of the RTC conference and the SIP gateway.

Mode two:

the method comprises the steps of establishing a corresponding relation between a meeting identifier of an RTC meeting and an SIP gateway in advance, responding to an incoming call request of an SIP client to the RTC meeting, acquiring the meeting identifier of the RTC meeting contained in the incoming call request, and determining the SIP gateway corresponding to the incoming call request based on the corresponding relation between the meeting identifier of the RTC meeting and the SIP gateway.

In step S230, a virtual SIP account corresponding to the SIP client is determined from a plurality of virtual SIP accounts associated with the SIP gateway.

In an example embodiment, an unused virtual SIP account is randomly selected from the multiple virtual SIP accounts associated with the SIP gateway, and the selected virtual SIP account is used as a virtual SIP account corresponding to the SIP client. For example, a virtual SIP account table of the virtual SIP account associated with SIP is stored in the database, and an unused virtual SIP account is randomly selected from the virtual SIP account table associated with the SIP gateway and is used as the virtual SIP account corresponding to the SIP client.

According to the technical solution in the exemplary embodiment of fig. 2, on one hand, a plurality of virtual SIP accounts associated with the SIP gateway are pre-allocated, and a plurality of virtual SIP accounts with global static resources pre-allocated are adopted, so that memory fragments caused by persistent allocation and recovery of memory are avoided; on the other hand, when the SIP client requests to call in the RTC conference, the virtual SIP account corresponding to the SIP client is determined from the plurality of virtual SIP accounts of the SIP gateway bound with the RTC conference, and because the mode of globally sharing the plurality of virtual SIP accounts is adopted for one-time allocation, not only can the available virtual SIP account resources of each RTC conference be ensured, but also the maximum repeated utilization of the virtual SIP account resources can be achieved, the resource waste in the virtual SIP account allocation is reduced, and the resource utilization rate is improved.

Further, in some example embodiments, a correspondence between the virtual SIP account corresponding to the SIP client and the conference identifier of the RTC conference in the incoming request is established, that is, a binding relationship between the virtual SIP account corresponding to the SIP client and the conference identifier of the RTC conference in the incoming request is established. For example, a binding relation table is stored in the database, and a correspondence between a virtual SIP account corresponding to the SIP client and a conference identifier of the RTC conference in the incoming request is recorded in the binding relation table. In some example embodiments, the binding relationship table further includes an incoming call status field, and an incoming call status of the virtual SIP account corresponding to the SIP client is set to an incoming call status.

By establishing the corresponding relation between the virtual SIP account corresponding to the SIP client and the conference identifier of the RTC conference, the binding consumption of virtual SIP account resources can be carried out only when the SIP equipment is accessed to the conference, and the corresponding binding relation is released when the SIP equipment exits from the conference, so that the resource waste caused by idle service expansion capacity increasing equipment can be avoided, and the resource utilization rate is improved.

Fig. 3 shows a flowchart of an account assignment method according to other embodiments of the present application.

Referring to fig. 3, in step S310, in response to an incoming call request from a SIP client to an RTC conference, a SIP gateway corresponding to the incoming call request is determined, and the SIP gateway is associated with a pre-allocated plurality of virtual SIP accounts.

In the exemplary embodiment, the implementation process and implementation effect of step S310 and step S220 are similar, and are not described herein.

In step S320, a virtual SIP account corresponding to the SIP client is determined from a plurality of virtual SIP accounts associated with the SIP gateway.

In the example embodiment, the implementation process and the implementation effect of step S320 are similar to those of step S230, and are not described herein.

In step S330, the proportion of the virtual SIP accounts that have been used among the plurality of virtual SIP accounts associated with the SIP gateway is determined.

In an example embodiment, the SIP gateway is associated with a plurality of pre-allocated virtual SIP accounts, after determining a virtual SIP account corresponding to the SIP client, an incoming state of the virtual SIP account corresponding to the SIP client is set to an incoming calling state, the incoming calling state indicates that the virtual SIP account is a used virtual SIP account, and a proportion of the used virtual SIP accounts in the plurality of virtual SIP accounts associated with the SIP gateway is determined according to the number of virtual SIP accounts in the calling state and the total number of the allocated virtual SIP accounts.

For example, if the number of virtual SIP accounts in the rolling state is 5 and the total number of pre-assigned virtual SIP accounts is 10, it is determined that the proportion of the virtual SIP accounts that have been used in the plurality of virtual SIP accounts associated with the SIP gateway is 50%.

In step S340, the virtual SIP account associated with the SIP gateway is subjected to expansion or contraction processing according to the ratio.

In some example embodiments, if the proportion of the virtual SIP accounts that have been used in the plurality of virtual SIP accounts associated with the SIP gateway is greater than a first predetermined threshold, the virtual SIP accounts associated with the SIP gateway are subjected to a capacity expansion process. For example, if the SIP gateway associates 10 virtual SIP accounts with which 8 virtual SIP accounts have been allocated, and the ratio is 80% or more than 70%, the virtual SIP accounts associated with the SIP gateway are subjected to capacity expansion, for example, 5 virtual SIP accounts are added each time.

Further, in some example embodiments, if the proportion of the virtual SIP accounts that have been used in the plurality of virtual SIP accounts associated with the SIP gateway is less than a second predetermined threshold, the virtual SIP accounts associated with the SIP gateway are scaled. For example, if the SIP gateway associates 20 virtual SIP accounts, if 5 virtual SIP accounts have been used, the ratio is 25 to less than 50%, and a predetermined number, e.g., 5 virtual SIP accounts, is contracted.

According to the technical solution in the example embodiment of fig. 3, on one hand, since the mode of globally sharing multiple virtual SIP accounts is adopted by one allocation, resource waste caused by idle service expansion capacity increasing equipment is avoided; on the other hand, the number of virtual SIP accounts is dynamically expanded and contracted in real time according to the call capacity, so that the resource use is ensured to be minimized and the resource utilization is ensured to be maximized. And resources are saved, and meanwhile, the overall effective throughput of the system is improved.

Further, in an example embodiment, the performing a scaling process on the virtual SIP account associated with the SIP gateway includes: registering a predetermined number of virtual SIP accounts associated with the SIP gateway; and recovering account resources of a predetermined number of virtual SIP accounts.

By carrying out capacity reduction processing on the virtual SIP account related to the SIP gateway, the account resources of the virtual SIP account are recovered, so that resource waste caused by idle service expansion capacity increasing equipment and the like can be avoided, and the system resources of the audio-video conference system are further saved.

Fig. 4 is a flow chart illustrating an account assignment method according to further embodiments of the present application.

Referring to fig. 4, in step S410, in response to an operation of creating the RTC conference, a preset correspondence between the conference identifier of the RTC conference and the SIP gateway is established.

In an example embodiment, a conference table, such as a meeting table, is added to a database of the audio-video conference system, where the conference table includes a correspondence between a conference identifier of the RTC conference and a SIP gateway serving the RTC conference, and the conference table is used to manage the correspondence between the conference identifier of the RTC conference and the SIP gateway serving the RTC conference, for example, adding, modifying, or deleting the conference identifier of the RTC conference and the SIP gateway serving the RTC conference.

Further, in response to a conference creation operation of the RTC client for creating the RTC conference, a preset correspondence between a conference identifier of the RTC conference and the SIP gateway is added to the conference table.

In step S420, a plurality of virtual SIP accounts associated with the SIP gateway are registered in the SIP server in response to the start-up operation of the SIP gateway.

In an exemplary embodiment, the SIP gateway performs pre-allocation of the virtual SIP accounts after being started, and allocates a predetermined number of virtual SIP accounts, for example, 10 virtual SIP accounts, to the SIP gateway, where the predetermined number may be configured according to service requirements.

Further, in an example embodiment, an account table, such as a users table, of the virtual SIP accounts associated with the SIP gateway is established, and information of the virtual SIP accounts allocated by the SIP gateway is recorded in the account table.

In S430, in response to an incoming call request from the SIP client for the RTC conference, a SIP gateway and a virtual SIP account corresponding to the incoming call request are determined.

In an example embodiment, when an incoming call request of a SIP device is received, if the incoming call request is a first incoming call request of an RTC conference, an edge SIP server performs load balancing scheduling management, and allocates a specifically scheduled SIP gateway to the incoming call request of the SIP device. For example, according to the load condition of each SIP gateway, a SIP gateway with a lower load is selected and allocated to the SIP device. Further, a correspondence between the conference identifier of the RTC conference in the incoming call request and the SIP gateway is established, for example, the correspondence between the conference identifier of the RTC conference in the incoming call request and the SIP gateway is recorded in a conference table.

If the incoming call request is not the first incoming call request of the RTC conference, the conference identification of the RTC conference contained in the incoming call request is acquired, and the SIP gateway corresponding to the incoming call request is determined based on the corresponding relation between the conference identification of the RTC conference and the SIP gateway. For example, the conference table contains a correspondence between a conference identifier of the RTC conference and a SIP gateway serving the RTC conference, and the corresponding SIP gateway is queried from the conference table according to the conference identifier of the RTC conference.

Further, an available virtual SIP account number is randomly selected from a plurality of virtual SIP account numbers associated with the allocated SIP gateway and used as a virtual SIP account number corresponding to the SIP equipment, and the incoming state of the virtual SIP account number corresponding to the SIP equipment is set as the incoming state. For example, the account table of the virtual SIP account includes an incoming call status field, and the value of the incoming call status field in the account table of the virtual SIP account is set to a rolling status.

In step S440, the SIP gateway performs the capacity expansion determination of the virtual SIP account after receiving the incoming call request.

In an example embodiment, after receiving an incoming call request, the SIP gateway determines a proportion of the virtual SIP accounts that have been used in the plurality of virtual SIP accounts associated with the SIP gateway, and determines whether to perform capacity expansion processing on the virtual SIP accounts associated with the SIP gateway according to the proportion.

In step S450, in response to the call release operation of the SIP client, resource recovery is performed on the virtual SIP account corresponding to the SIP client.

In an example embodiment, after the call is released, resource recovery of the virtual SIP account is performed, bound conference information is cleared, and an incoming call state of the virtual SIP account is set to be a idle state.

In step S460, it is determined whether to perform the capacity reduction processing on the virtual SIP account related to the SIP gateway according to the proportion of the virtual SIP accounts that have been used in the plurality of virtual SIP accounts related to the SIP gateway.

In an example embodiment, if the proportion of the used virtual SIP accounts in the plurality of virtual SIP accounts associated with the SIP gateway is smaller than a second predetermined threshold, the virtual SIP accounts associated with the SIP gateway are scaled. For example, if the SIP gateway associates 20 virtual SIP accounts, if 5 virtual SIP accounts have been used, the ratio is 25 to less than 50%, and a predetermined number, e.g., 5 virtual SIP accounts, is contracted. The performing the volume reduction processing on the virtual SIP accounts associated with the SIP gateway mainly includes logout of a predetermined number of virtual SIP accounts, and recovering virtual SIP account resources in a virtual SIP account table, such as a users table.

In step S470, in response to the conference release operation of the RTC conference, the reclamation of conference resources of the RTC conference is performed.

In an example embodiment, after the conference is released, the conference resource is reclaimed and the corresponding record in the conference table, for example, the meeting tables, is cleaned.

According to the technical solution in the exemplary embodiment of fig. 4, on one hand, a plurality of virtual SIP accounts with global static resources allocated in advance are adopted, while a certain static memory resource is occupied, the problem of memory fragmentation caused by persistent allocation and recovery of memory is avoided; on the other hand, the mode of one-time distribution and global sharing is adopted, so that the resource waste caused by idle equipment with increased service expansion capacity is solved, and a large amount of audio and video conference system resources are essentially saved; on the other hand, the binding consumption of resources is carried out when the SIP equipment enters a meeting (call access), the resource unbinding is carried out after the SIP equipment exits the meeting, and the number of virtual SIP accounts is dynamically expanded and contracted in real time according to the calling capacity, so that the resource use is ensured to be minimized, the resource utilization is ensured to be maximized, and the overall effective throughput of the audio-video conference system is improved while the resource is saved.

In addition, in the example embodiment, in response to a call release operation of the SIP client, resource reclamation is performed on the virtual SIP account corresponding to the SIP client. For example, in response to a call release operation of the SIP client, clearing a conference identifier bound by a virtual SIP account corresponding to the SIP client; and setting the incoming call state of the virtual SIP account corresponding to the SIP client to be an idle state.

After the SIP client releases the call, the account resources of the corresponding virtual SIP account are recovered, so that the resource waste caused by idle service expansion capacity increasing equipment and the like can be avoided, and the system resources of the audio-video conference system are further saved.

Fig. 5 illustrates a flowchart of an account assignment method provided according to further embodiments of the present application.

Referring to fig. 5, after the SIP gateway is started, a plurality of virtual SIP accounts bound to the SIP gateway are registered in step S505.

In the exemplary embodiment, SIP server 110 includes a central SIP server 112 and an edge SIP server 114. After the SIP gateway 115 is started, a plurality of virtual SIP accounts are pre-assigned, and a plurality of virtual SIP accounts bound with the SIP gateway are registered in the central SIP server 112.

In step S510, the RTC client creates an RTC conference.

In an example embodiment, the RTC client creates the RTC audio-video conference based on WebRTC, which is a set of APIs (Application Programming Interface, application program interfaces) that support Web browsers to conduct real-time voice conversations or video conversations, so that Web applications can directly provide real-time audio-video communication functions.

In step S515, the RTC conference is started.

In step S520, the conference number is recorded and bound to the corresponding SIP gateway, and written into the database.

In an example embodiment, a conference table, such as a meeting table, is added to a database of the audio-video conference system, the conference table containing a correspondence between a conference identifier of the RTC conference and a SIP gateway serving the RTC conference. Recording the conference number in the conference table and binding the conference number to the corresponding SIP gateway, that is, recording the corresponding relation between the conference number and the SIP gateway in the conference table of the database.

In step S525, the SIP client calls the RTC conference number, applying for joining the conference.

In an example embodiment, SIP client 105 initiates a call to the RTC conference number to edge server 114, applying for joining the RTC conference corresponding to the RTC conference number.

In step S530, the edge SIP server queries the associated available gateway, virtual SIP account number, according to the conference number.

In an exemplary embodiment, the conference table of the database 130 includes a correspondence between a conference identifier of the RTC conference and a SIP gateway serving the RTC conference, and the edge server 114 queries a corresponding SIP gateway from the conference table according to the conference number, and selects an available virtual SIP account number from the queried SIP gateway as the virtual SIP account number corresponding to the SIP client 105.

In step S535, the central SIP server initiates a call to the SIP gateway associated with the virtual SIP account number.

In an example embodiment, the edge server 114 sends the acquired SIP gateway corresponding to the SIP client 105 and the virtual SIP account to the central SIP server 112 through the SIP protocol, and the central SIP server 112 initiates a call to the SIP gateway associated with the virtual SIP account through the SIP protocol.

In step S540, the SIP gateway sends a SIP incoming call notification to the RTC signaling processing module.

In an example embodiment, the SIP gateway 115 converts the SIP protocol-based call into a RTC protocol call, sends a SIP incoming call notification to the RTC signaling processing module 124 of the RTC server 120 via an RTC protocol, such as an http protocol, and sends the SIP incoming call notification to the RTC signaling processing module 124 in JSON data format.

In step S545, the RTC signaling processing module returns a SIP call answer to the SIP gateway.

In an example embodiment, RTC signaling processing module 124 parses and processes the SIP incoming call notification, returns a SIP call answer to SIP gateway 115, for example, via an http protocol in the form of JSON data.

In step S550, the SIP gateway returns a SIP answer response to the central SIP server.

In an example embodiment, the SIP gateway 115 returns a SIP answer response to the central SIP server. The center SIP server returns the SIP answer response to the edge SIP server, the edge SIP server may obtain the audio and video stream of the corresponding RTC conference from the media server 122 through the RTP protocol, and send the obtained audio and video stream of the RTC conference to the SIP client 105 through the RTP protocol, and the SIP client 105 may obtain the conference information of the RTC conference through the audio and video stream. The RTP protocol is a packet format for streaming media data transmitted over the internet.

According to the technical scheme in the example embodiment of fig. 5, the optimization of the virtual SIP account management policy of the SIP gateway is realized, the maximum service capability is provided with the minimum resource consumption, the resources of the SIP gateway and the SIP server are saved, and meanwhile, the flexibility and the efficiency of the audio-video conference system are improved.

According to the technical scheme of the embodiment of the application, 800 conferences per day and 150+ participants per peak value are provided, at least 800 x 2 = 1600 virtual number SIP account resources are needed in the current technical scheme, and only 150+ virtual SIP account resources are guaranteed in the technical scheme of the embodiment of the application, so that the effective utilization rate of resources is increased by one order of magnitude in number.

The following are device embodiments of the present application, which may be used to perform method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

Fig. 6 is a schematic structural diagram of an account number distribution device according to an exemplary embodiment of the present application.

Referring to fig. 6, the account assignment device 600 may be implemented as all or a part of a device by software, hardware, or a combination of both, and the account assignment device 600 is applied to an electronic apparatus. The account assignment device 600 includes a request receiving module 610, a gateway determining module 620, and an account assignment module 630. Wherein:

A request receiving module 610, configured to receive an incoming request of a session initiation protocol SIP client for a real-time communication RTC conference;

a gateway determining module 620, configured to determine, in response to the incoming call request, a SIP gateway corresponding to the incoming call request, where the SIP gateway is associated with a plurality of pre-allocated virtual SIP accounts;

an account assignment module 630 determines a virtual SIP account corresponding to the SIP client from the plurality of virtual SIP accounts associated with the SIP gateway.

In some example embodiments, based on the above-described scheme, the incoming call request includes a conference identification of the RTC conference, and the gateway determination module 620 includes:

and the SIP gateway determining unit is used for determining the SIP gateway corresponding to the conference identifier based on the conference identifier and a preset corresponding relation, wherein the preset corresponding relation is the corresponding relation between the conference identifier of the RTC conference and the SIP gateway.

In some example embodiments, based on the foregoing solution, the incoming call request is a first incoming call request of the RTC conference, and the determining a SIP gateway corresponding to the incoming call request includes:

determining the SIP gateway corresponding to the incoming call request from a plurality of SIP gateways in a load balancing manner,

The apparatus further comprises:

and the first corresponding relation establishing module is used for establishing the corresponding relation between the conference identifier of the RTC conference and the SIP gateway.

In some example embodiments, based on the above-described aspects, the apparatus further comprises:

and the second corresponding relation establishing module is used for establishing the corresponding relation between the virtual SIP account corresponding to the SIP client and the conference identifier.

In some example embodiments, based on the above, the account assignment module is configured to:

randomly selecting an unused virtual SIP account number from the multiple virtual SIP accounts associated with the SIP gateway as a virtual SIP account number corresponding to the SIP client;

and setting the incoming call state of the virtual SIP account corresponding to the SIP client as an incoming call state.

In some example embodiments, based on the above-described aspects, the apparatus further includes:

a proportion determining module, configured to determine a proportion of a virtual SIP account number that has been used in a plurality of virtual SIP account numbers associated with the SIP gateway;

and the expansion and contraction processing module is used for carrying out expansion or contraction processing on the virtual SIP account related to the SIP gateway according to the proportion.

In some example embodiments, based on the above-described scheme, the scaling processing module is configured to:

If the proportion is larger than a first preset threshold value, performing capacity expansion processing on the virtual SIP account related to the SIP gateway;

and if the proportion is smaller than a second preset threshold value, carrying out capacity reduction processing on the virtual SIP account number associated with the SIP gateway.

In some example embodiments, based on the above-described scheme, the scalable processing module is further configured to:

deregistering a predetermined number of virtual SIP accounts associated with the SIP gateway;

and recovering account resources of the preset number of virtual SIP accounts.

and the first resource recycling module is used for responding to the call release operation of the SIP client and recycling resources of the virtual SIP account corresponding to the SIP client.

In some example embodiments, based on the above, the first resource reclamation module is configured to:

clearing the conference identifier bound by the virtual SIP account corresponding to the SIP client;

and setting the incoming state of the virtual SIP account corresponding to the SIP client to be an idle state.

and the account registration module is used for responding to the starting operation of the SIP gateway and registering the virtual SIP accounts associated with the SIP gateway in an SIP server.

the third corresponding relation establishing module is used for responding to conference establishing operation of establishing the RTC conference and establishing a preset corresponding relation between a conference identifier of the RTC conference and the SIP gateway.

and the second resource recycling module is used for responding to the conference release operation of the RTC conference and recycling conference resources of the RTC conference.

It should be noted that, when the account number distribution device provided in the foregoing embodiment performs the account number distribution method, only the division of the foregoing functional modules is used as an example, in practical application, the foregoing functional distribution may be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules, so as to complete all or part of the functions described above.

In addition, the account number distribution device and the account number distribution method provided in the foregoing embodiments belong to the same concept, which embody detailed implementation procedures in the method embodiments, and are not described herein again.

The embodiment of the present application further provides a computer storage medium, where the computer storage medium may store a plurality of instructions, where the instructions are adapted to be loaded and executed by a processor, where a specific implementation procedure may refer to a specific description of the foregoing embodiment, and details are not repeated herein.

The embodiment of the present application further provides a computer program product, where at least one instruction is stored in the computer program product, where the at least one instruction is loaded by the processor and executed by the processor, and a specific execution process may refer to a specific description of the foregoing embodiment, and a detailed description is omitted herein.

The embodiment of the present application further provides a chip configured to execute the account assignment method in the above embodiment, and the specific execution process may refer to the specific description of the above embodiment, which is not described herein.

In addition, referring to fig. 7, a schematic structural diagram of an electronic device is provided in an embodiment of the present application. As shown in fig. 7, the electronic device 700 may include: at least one processor 701, at least one communication module 704, an input output interface 703, a memory 705, at least one communication bus 702.

Wherein the communication bus 702 is used to enable connected communications between these components.

The input/output interface 703 may include a Display screen (Display) and a Camera (Camera), and the optional input/output interface 703 may further include a standard wired interface and a standard wireless interface.

The communication module 704 may optionally include a standard wired interface, a wireless interface (e.g., WIFI interface), among others.

Wherein the processor 701 may include one or more processing cores. The processor 701 utilizes various interfaces and lines to connect various portions of the overall electronic device 700, perform various functions of the electronic device 700, and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 705, and invoking data stored in the memory 705. Alternatively, the processor 701 may be implemented in hardware in at least one of digital signal processing (Digital Signal Processing, DSP), field programmable gate array (Field-Programmable Gate Array, FPGA), programmable logic array (Programmable Logic Array, PLA). The processor 701 may integrate one or a combination of several of a central processing unit (Central Processing Unit, CPU), an account distributor (Graphics Processing Unit, GPU), a modem, etc. The CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing the content required to be displayed by the display screen; the modem is used to handle wireless communications. It will be appreciated that the modem may not be integrated into the processor 701 and may be implemented by a single chip.

The Memory 705 may include a random access Memory (Random Access Memory, RAM) or a Read-Only Memory (Read-Only Memory). Optionally, the memory 705 includes a non-transitory computer readable medium (non-transitory computer-readable storage medium). Memory 705 may be used to store instructions, programs, code, sets of codes, or instruction sets. The memory 705 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, etc.; the storage data area may store data or the like referred to in the above respective method embodiments. The memory 705 may also optionally be at least one storage device located remotely from the processor 701. As shown in fig. 7, an operating system, a communication module, an input-output interface module, and an account assignment program may be included in the memory 705 as one type of computer storage medium.

In the electronic device 700 shown in fig. 7, the input/output interface 703 is mainly used for providing an input interface for a user, and acquiring data input by the user; and the processor 701 may be configured to invoke an account assignment program stored in the memory 705 such that the processor 701 performs steps in an account assignment method according to various exemplary embodiments of the present disclosure. For example, the processor 701 may perform the steps as shown in fig. 2: step S210, receiving an incoming call request of the SIP client for the RTC conference; step S220, responding to the incoming call request, determining a SIP gateway corresponding to the incoming call request, wherein the SIP gateway is associated with a plurality of pre-allocated virtual SIP accounts; in step S230, a virtual SIP account corresponding to the SIP client is determined from the multiple virtual SIP accounts associated with the SIP gateway.

The foregoing is an exemplary scenario of an electronic device according to an embodiment of the present disclosure, where the electronic device may be a SIP gateway, or may be another suitable device, such as a SIP server. It should be noted that, the technical solution of the electronic device and the technical solution of the account assignment processing method belong to the same concept, and details of the technical solution of the electronic device, which are not described in detail, can be referred to the description of the technical solution of the account assignment processing method.

In the description of the present application, it should be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. In the description of the present application, it is to be understood that the terms "comprise" and "have," and any variations thereof, are intended to cover non-exclusive inclusions, unless otherwise specifically defined and defined. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus. The specific meaning of the terms in this application will be understood by those of ordinary skill in the art in a specific context. Furthermore, in the description of the present application, unless otherwise indicated, "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

Those skilled in the art will appreciate that implementing all or part of the above-described methods in accordance with the embodiments may be accomplished by way of a computer program stored on a computer readable storage medium, which when executed may comprise the steps of the embodiments of the methods described above. The storage medium may be a magnetic disk, an optical disk, a read-only memory, a random access memory, or the like.

The foregoing disclosure is only illustrative of the preferred embodiments of the present application and is not intended to limit the scope of the claims herein, as the equivalent of the claims herein shall be construed to fall within the scope of the claims herein.

Claims

1. An account assignment method, which is characterized by comprising the following steps:

2. The method of claim 1, wherein the incoming call request includes a conference identification of the RTC conference, and wherein the determining the SIP gateway to which the incoming call request corresponds includes:

And determining the SIP gateway corresponding to the conference identifier based on the conference identifier and a preset corresponding relation, wherein the preset corresponding relation is the corresponding relation between the conference identifier of the RTC conference and the SIP gateway.

3. The method according to claim 1, wherein the incoming call request is a first incoming call request of the RTC conference, and the determining a SIP gateway to which the incoming call request corresponds comprises:

the method further comprises the steps of:

and establishing a corresponding relation between the conference identifier of the RTC conference and the SIP gateway.

4. The method according to claim 2, wherein the method further comprises:

and establishing a corresponding relation between the virtual SIP account corresponding to the SIP client and the conference identifier.

5. The method according to claim 1, wherein said determining a virtual SIP account number corresponding to the SIP client from the plurality of virtual SIP accounts associated with the SIP gateway comprises:

6. The method according to claim 1, wherein the method further comprises:

determining the proportion of the used virtual SIP accounts in a plurality of virtual SIP accounts associated with the SIP gateway;

and according to the proportion, performing capacity expansion or capacity reduction processing on the virtual SIP account number associated with the SIP gateway.

7. The method according to claim 6, wherein the expanding or shrinking the virtual SIP account number associated with the SIP gateway according to the ratio includes:

8. The method of claim 7, wherein the performing a scaling process on the virtual SIP account number associated with the SIP gateway comprises:

and recovering account resources of the preset number of virtual SIP accounts.

9. The method according to claim 1, wherein the method further comprises:

And responding to the call release operation of the SIP client, and recovering resources of the virtual SIP account corresponding to the SIP client.

10. The method according to claim 9, wherein the resource recycling of the virtual SIP account corresponding to the SIP client includes:

11. The method according to any one of claims 1 to 10, further comprising:

the plurality of virtual SIP accounts associated with the SIP gateway are registered in a SIP server in response to a start-up operation of the SIP gateway.

12. The method according to claim 2, wherein the method further comprises:

and responding to conference creation operation of creating the RTC conference, and establishing a preset corresponding relation between a conference identifier of the RTC conference and the SIP gateway.

13. The method according to claim 12, wherein the method further comprises:

and responding to the conference release operation of the RTC conference, and recycling conference resources of the RTC conference.

14. An account number distribution device, the device comprising:

15. A computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the steps of the method according to any one of claims 1 to 13.

16. An electronic device, comprising: a processor and a memory storing a computer program adapted to be loaded by the processor and to perform the steps of the method according to any one of claims 1 to 13.