CN102868776B - Method and system for realizing meeting drift - Google Patents

Method and system for realizing meeting drift Download PDF

Info

Publication number
CN102868776B
CN102868776B CN201210334794.6A CN201210334794A CN102868776B CN 102868776 B CN102868776 B CN 102868776B CN 201210334794 A CN201210334794 A CN 201210334794A CN 102868776 B CN102868776 B CN 102868776B
Authority
CN
China
Prior art keywords
server
meeting
drift
conference
service process
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.)
Active
Application number
CN201210334794.6A
Other languages
Chinese (zh)
Other versions
CN102868776A (en
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.)
Codyy Education Technology Co Ltd
Original Assignee
Suzhou Codyy Network Technology 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 Suzhou Codyy Network Technology Co Ltd filed Critical Suzhou Codyy Network Technology Co Ltd
Priority to CN201210334794.6A priority Critical patent/CN102868776B/en
Publication of CN102868776A publication Critical patent/CN102868776A/en
Application granted granted Critical
Publication of CN102868776B publication Critical patent/CN102868776B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Landscapes

  • Telephonic Communication Services (AREA)

Abstract

The invention provides a method and a system for realizing meeting drift. The method comprises the following steps of: resolving meeting parameter information carried in a network meeting request sent by a user, by a domain name resolution server, and if a meeting number of the network meeting request does not exist in an exception routing rule list, judging whether the number of current meetings of a regional meeting type exceeds a corresponding maximal meeting number threshold or not according to a meeting load threshold table; if so, inquiring a drift record table by the domain name resolution server, and if the drift record table stores a corresponding target region after drift and a first target business processing server, directly routing the network meeting request to the first target business processing server by the domain name resolution server; and if the number of the network meetings processed by the first target business processing server reaches an early-warning value, determining a second target business processing server by the first target business processing server according to a first drift strategy, and updating the second target business processing server to the drift record table by the domain name resolution server.

Description

A kind of implementation method of meeting drift and system
Technical field
The invention belongs to network communication field, particularly relate to implementation method and the system of a kind of meeting drift.
Background technology
At present, along with the development of the network communications technology, in Web conference field, there is the demand of Web conference drift.But the mode that current industry uses is all the collective user of a region server corresponding in Web conference floated in another one region server.For example, company A arranges a machine room A1 in Beijing, arranges a machine room A2 in Hangzhou, and wherein, Pekinese user connects the server of Beijing machine room A1, and the user in Hangzhou connects the server of Hangzhou machine room A2.When the server stress of Pekinese machine room A1 is excessive or when breaking down, all user collectives of the server connecting Beijing machine room A1 will be floated on the server of Hangzhou machine room A2.But the mode of above-mentioned entirety drift not only significantly reduces the Experience Degree of Beijing user, and the server stress of Hangzhou machine room A2 can be caused excessive, can cause the system crash of all server in machine room what is more, have a strong impact on communication efficiency.
Summary of the invention
The invention provides implementation method and the system of a kind of meeting drift, to solve the problem.
The invention provides the implementation method of a kind of meeting drift.Said method comprises the following steps: domain name resolution server receives and resolves the conference parameters information of carrying in the Web conference request of user's transmission, determine meeting numbering, conference type and the region belonging to described user, if the meeting numbering of Web conference request is not present in exception routing rule table, then judge according to meeting load threshold table whether the active conference number of the described conference type in described region exceedes corresponding maximum meeting number threshold value; If exceed, domain name resolution server inquiry drift record sheet, if corresponding target area and first object Service Process Server after the described conference type drift of drift record sheet storage networking request for conference affiliated area, then Web conference request is routed directly to first object Service Process Server according to drift record sheet by domain name resolution server; If the Web conference number that first object Service Process Server works as pre-treatment reaches early warning value, first object Service Process Server is tactful in Web conference Request routing to the second target service processing server according to the first drift, and the second target service processing server is updated to drift record sheet by domain name resolution server.
What the present invention also provided a kind of meeting to drift about realizes system, comprises domain name resolution server, Region control server, load-balanced server and Service Process Server.Domain name resolution server directly connects Service Process Server or connects Service Process Server by Region control server and load-balanced server, and Region control server connects Service Process Server by load-balanced server.Domain name resolution server, for receiving and resolving the conference parameters information of carrying in the Web conference request of user's transmission, determine meeting numbering, conference type and the region belonging to described user, if the meeting numbering of Web conference request is not present in exception routing rule table, then judge according to meeting load threshold table whether the active conference number of the described conference type in described region exceedes corresponding maximum meeting number threshold value.If exceed, domain name resolution server, for inquiring about drift record sheet, if corresponding target area and first object Service Process Server after the described conference type drift of drift record sheet storage networking request for conference affiliated area, then domain name resolution server, for being routed directly to first object Service Process Server according to drift record sheet by Web conference request.If the Web conference number that first object Service Process Server works as pre-treatment reaches early warning value, first object Service Process Server, for tactful in Web conference Request routing to the second target service processing server according to the first drift, and domain name resolution server, for the second target service processing server is updated to drift record sheet.
Compared to prior art, the implementation method of drifting about according to meeting provided by the invention and system, when according to meeting load threshold table, domain name resolution server judges that the active conference number of corresponding conference type in respective regions exceedes corresponding maximum meeting number threshold value, domain name resolution server inquiry drift record sheet.If corresponding target area and first object Service Process Server after the conference type drift of drift record sheet storage networking request for conference affiliated area, then domain name resolution server directly by Web conference Request routing to first object Service Process Server.If corresponding target area and first object Service Process Server after the conference type drift of drift record sheet non-storage networking request for conference affiliated area, then domain name resolution server determines according to the second drift strategy the target area that Web conference is corresponding, the load-balanced server of target area is according to allocation strategy determination first object Service Process Server, or first object Service Process Server determines the second target service processing server according to the first drift strategy.So, the Web conference request of the corresponding conference type of respective regions is directly drifted about according to drift record sheet by domain name resolution server, through Region control server and load-balanced server, thus need not improve communication efficiency.In addition, drift is realized to the Web conference exceeding corresponding maximum meeting number threshold value, simultaneously, drift is realized to the Web conference exceeding Service Process Server early warning value, thus realize the drift of single game meeting, make server cluster load more balanced, improve communication efficiency.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide a further understanding of the present invention, and form a application's part, schematic description and description of the present invention, for explaining the present invention, does not form inappropriate limitation of the present invention.In the accompanying drawings:
Figure 1 shows that the flow chart of the implementation method of the meeting drift that preferred embodiment according to the present invention provides;
Figure 2 shows that the schematic diagram of the system that realizes of the meeting drift that preferred embodiment according to the present invention provides.
Embodiment
Hereinafter also describe the present invention in detail with reference to accompanying drawing in conjunction with the embodiments.It should be noted that, when not conflicting, the embodiment in the application and the feature in embodiment can combine mutually.
Figure 1 shows that the flow chart of the implementation method of the meeting drift that preferred embodiment according to the present invention provides.As shown in Figure 1, the implementation method that the meeting that preferred embodiment of the present invention provides is drifted about comprises step 101 ~ 103.
In step 101, domain name resolution server receives and resolves the conference parameters information of carrying in the Web conference request of user's transmission, determine meeting numbering, conference type and the region belonging to described user, if the meeting numbering of described Web conference request is not present in exception routing rule table, then judge according to meeting load threshold table whether the active conference number of the described conference type in described region exceedes corresponding maximum meeting number threshold value.In this, conference parameters information comprises meeting numbering, meeting number information, participant's area information and address information.Wherein, participant's area information refers to the area information that people with a part in a conference person distributes.
Specifically, during user's initiating network conference, after the meeting number of setting network meeting and participant's area information, Web conference request is sent to domain name resolution server.After domain name resolution server receives Web conference request, by resolving the address information (such as, IP address) of the conference parameters information acquisition user carried in Web conference request to determine the region belonging to described user.For example, if IP address is the user P initiating network conference of 202.91.251.148, then domain name resolution server can obtain IP address by the Web conference request of resolving user P and sending is 202.91.251.148, and to obtain region corresponding to above-mentioned IP address be Suzhou.
In the present embodiment, domain name resolution server stores exception routing rule table (such as, shown in table 1), and exception routing rule table stores the corresponding relation of the meeting numbering of the Web conference request of all drifts and the address information of corresponding Service Process Server.Wherein, the address information of Service Process Server such as comprises IP address information.Specifically, domain name resolution server resolves the conference parameters information of carrying in Web conference request, determines that meeting is numbered, and according to whether storing described meeting numbering in meeting numbering query exception routing rule table.If exception routing rule table stores described meeting numbering, then this Web conference request is routed directly to corresponding Service Process Server according to exception routing rule table by domain name resolution server.So, Web conference request without the need to the route assignment through Region control server and load-balanced server, thus improves communication efficiency.In addition, at the end of the Web conference that corresponding meeting is numbered, domain name resolution server deletes record corresponding in exception routing rule table.
Meeting is numbered Service Process Server
164173 Service Process Server 1(address 1)
164174 Service Process Server 2(address 2)
164175 Service Process Server 3(address 3)
164176 Service Process Server 4(address 4)
164177 Service Process Server 5(address 5)
164178 Service Process Server 3(address 3)
164179 Service Process Server 4(address 4)
164180 Service Process Server 2(address 2)
164181 Service Process Server 6(address 6)
164182 Service Process Server 4(address 4)
164183 Service Process Server 2(address 2)
164184 Service Process Server 3(address 3)
Table 1
In the present embodiment, domain name resolution server resolves the conference parameters information of carrying in Web conference request, determines conference type.In this, conference type such as comprises general meeting, one's respective area convention and trans-regional convention.The differentiation standard of conference type is such as shown in table 2.But the present invention does not limit this.In practical application, kind and the differentiation standard of conference type can be set as required.
Table 2
For example, if the conference parameters information of carrying in the Web conference request that user P sends comprises meeting number 200 people, participant's area information is Suzhou and Hangzhou, then domain name resolution server is known with reference to table 2 according to above-mentioned information, and this Web conference request belongs to general meeting.
In addition, in the present embodiment, domain name resolution server stores meeting load threshold table, and meeting load threshold table comprises maximum meeting number threshold value corresponding to different conference type in all regions and active conference number.Wherein, maximum meeting number threshold value corresponding to the different conference type in each region in meeting load threshold table can be determined according to actual conditions.The present invention does not limit this.In this, for Hangzhou, Beijing, Shanghai, region, four, Suzhou, the meeting load threshold table that domain name resolution server stores is such as shown in table 3.
Table 3
In the present embodiment, domain name resolution server is according to the active conference number in the Web conference request real-time update meeting load threshold table received.If domain name resolution server judges that the active conference number obtaining corresponding conference type in respective regions does not exceed corresponding maximum meeting number threshold value, then Web conference request is sent to the Region control server corresponding with described region by domain name resolution server, and Web conference request is sent to the load-balanced server corresponding with described conference type by Region control server.Web conference request is sent to corresponding Service Process Server, the request of Service Process Server process Web conference after receiving Web conference request by load-balanced server.For example, if this Web conference request is " user a sends text message to user b ", after Service Process Server receives this request, first to distributed cache server inquiring user b on which Service Process Server, and then send request to the Service Process Server at user b place, ask this Service Process Server to forward text message to user b.In this, the information in all Service Process Server all can be synchronized to distributed cache server.Service Process Server realizes trans-regional information interaction by distributed cache server.So, improve communication efficiency.
In step 102, if exceed, domain name resolution server inquiry drift record sheet, if described drift record sheet stores the described rear corresponding target area of conference type drift and the first object Service Process Server of described Web conference request affiliated area, then described Web conference request is routed directly to described first object Service Process Server according to described drift record sheet by domain name resolution server.
Specifically, in the present embodiment, if when domain name resolution server judges that the active conference number obtaining the corresponding conference type of Web conference request affiliated area exceedes corresponding maximum meeting number threshold value according to meeting load threshold table, domain name resolution server inquiry drift record sheet.In this, domain name resolution server determines the address information of the target area that the different conference type in former region are corresponding and first object Service Process Server according to up-to-date drift information.
In the present embodiment, domain name resolution server stores drift record sheet.Drift record sheet stores the rear corresponding target area of conference type drift of respective regions and the address information of first object Service Process Server.Wherein, the address information of first object Service Process Server such as comprises IP address information.The drift record sheet that domain name resolution server stores is such as shown in table 4.But the present invention is not limited thereto.
Table 4
In step 103, if the Web conference number that described first object Service Process Server works as pre-treatment reaches early warning value, described first object Service Process Server is tactful in described Web conference Request routing to the second target service processing server according to the first drift, and described second target service processing server is updated to described drift record sheet by domain name resolution server.
In a preferred embodiment, described first drift strategy is: described first object Service Process Server according to the priority determination targeted loads equalization server of conference type and by described Web conference Request routing to described targeted loads equalization server, described targeted loads equalization server according to described allocation strategy by described Web conference Request routing to the second target service processing server.Specifically, each Service Process Server all preserves the parameter information (such as, address information) of all load-balanced servers in corresponding region.Wherein, the corresponding conference type of each load-balanced server.Such as, and Service Process Server stores the corresponding migration strategy table of comparisons, shown in table 5.
Conference type Conference type priority Migration strategy
Trans-regional convention High Migrate to the load-balanced server that one's respective area convention is corresponding
One's respective area convention In Migrate to the load-balanced server that general meeting is corresponding
General meeting Low Do not move
Table 5
With reference to table 5, for three kinds of conference type, the priority of conference type is followed successively by from high to low: trans-regional convention, one's respective area convention, general meeting.In this, if first object Service Process Server is when the Web conference number of pre-treatment reaches early warning value, first object Service Process Server can determine transportable targeted loads equalization server according to table 5.Such as, the trans-regional convention of first object Service Process Server process, and when the Web conference number of pre-treatment exceedes early warning value, then first object Service Process Server is load-balanced server corresponding to one's respective area convention according to migration strategy determination targeted loads equalization server.
For example, if the Web conference request Y(conference type that Hangzhou zone user sends is such as one's respective area convention) drift to the Service Process Server B of the one's respective area convention of Beijing Area, now, Service Process Server B is then first object Service Process Server.If the Web conference number that Service Process Server B works as pre-treatment reaches early warning value (such as, 100), then this Web conference request Y is drifted to the second target service processing server according to the first drift strategy by Service Process Server B.Because the priority of one's respective area convention is higher than the priority of general meeting, with reference to table 5, Service Process Server B determines this Web conference request Y to route to load-balanced server corresponding to the general meeting of Beijing Area.Specifically, Service Process Server B by Socket connection route proprietary under this Web conference to load-balanced server corresponding to the general meeting of Beijing Area, load-balanced server corresponding to the general meeting of Beijing Area receives after these connect, and these connections is loaded on the second target service processing server according to allocation strategy.Wherein, allocation strategy comprises: select the Service Process Server that CPU idleness is the highest, or, select the Service Process Server that priority is the highest.But the present invention does not limit this.In this, the second target service processing server is such as Service Process Server C.Meanwhile, the address information of the meeting numbering of Web conference request Y, area information and the second target service processing server is sent to domain name resolution server by Pekinese's Region control server.The address information of the meeting of Web conference request Y numbering and the second target service processing server is updated to exception routing rule table by domain name resolution server.Simultaneously, domain name resolution server is according to the former region of Web conference request Y and conference type, the address information of the target area (that is, Beijing Area) of Web conference request Y and the second target service processing server (that is, Service Process Server C) is updated to drift record sheet.
In another preferred embodiment, described first drift strategy is: described first object Service Process Server is by the load-balanced server corresponding with described conference type, meeting drift request is sent to affiliated Region control server, described Region control server is according to the priority of described meeting drift request and conference type, determine targeted loads equalization server, and by the load-balanced server corresponding with described conference type, the address information of described targeted loads equalization server is sent to described first object Service Process Server, described first object Service Process Server is according to described address information, by described Web conference Request routing to described targeted loads equalization server, described targeted loads equalization server according to described allocation strategy by described Web conference Request routing to the second target service processing server.
For example, if the Web conference request Y(conference type that Hangzhou zone user sends is such as one's respective area convention) drift to the Service Process Server B of the one's respective area convention of Beijing Area, now, Service Process Server B is then first object Service Process Server.If the Web conference number that Service Process Server B works as pre-treatment reaches early warning value (such as, 100), then this Web conference request Y is drifted to the second target service processing server according to the first drift strategy by Service Process Server B.Specifically, Service Process Server B is by the load-balanced server corresponding with one's respective area convention, and the Region control server to Beijing Area sends meeting drift request.The Region control server of Beijing Area, according to described meeting drift request, according to the priority of conference type, determines targeted loads equalization server.Specifically, the migration strategy table of comparisons of the Region control server stores of Beijing Area such as shown in table 5.In this, the Region control server determination targeted loads equalization server of Beijing Area is the load-balanced server of corresponding general meeting.The Region control server of Beijing Area passes through load-balanced server corresponding to one's respective area convention, and the address information of load-balanced server corresponding for general meeting is sent to Service Process Server B.Service Process Server B is according to described address information, Web conference request Y is routed to load-balanced server corresponding to general meeting, and Web conference request Y is routed to the second target service processing server according to allocation strategy by load-balanced server corresponding to general meeting.Wherein, allocation strategy comprises: select the Service Process Server that CPU idleness is the highest, or, select the Service Process Server that priority is the highest.But the present invention does not limit this.In addition, other processing procedures in this preferred embodiment are as above described in a preferred embodiment.Therefore repeat no more in this.
In addition, in the present embodiment, if according to meeting load threshold table, domain name resolution server judges that the active conference number obtaining the corresponding conference type of Web conference request affiliated area exceedes corresponding maximum meeting number threshold value, and drift record sheet does not store the described rear corresponding target area of conference type drift and the first object Service Process Server of described Web conference request affiliated area, then domain name resolution server determines target area according to the second drift strategy, the load-balanced server of the corresponding conference type in target area is according to allocation strategy determination first object Service Process Server, or, first object Service Process Server determines the second target service processing server according to the first drift strategy, target area and first object Service Process Server or the second target service processing server are updated to drift record sheet by domain name resolution server.
In the present embodiment, the second drift strategy is: the meeting total number of persons according to the total play of the meeting of area priorities, regional and regional determines the target area that described Web conference request is corresponding.Specifically, determine the comparison parameter in each region according to the meeting total number of persons of the total play of the meeting of area priorities, regional and regional, the minimum region of selection and comparison parameter is as target area.Wherein, the comparison parameter acquiring mode in each region is: the meeting total number of persons comparing total play+area priorities × this region of meeting in parameter=area priorities × this region.In this, domain name resolution server stores the area priorities of zones of different, and inquiry obtains the total play of meeting and the meeting total number of persons of regional.
Then, for Beijing, Hangzhou, Suzhou, region, four, Shanghai.In this, the corresponding Region control server in each region.If the user T1 in region, Hangzhou sends Web conference request Y, conference parameters information is as follows: meeting number 1200 people, the address information of user T1 (such as, IP address 117.81.233.120), participant's area information comprises the address information of user T2 (such as, IP address 117.81.233.121) and user T3 address information (such as, IP address 117.81.233.122), after then domain name resolution server resolves the Web conference request Y of user T1, determine that user T1 belongs to region, Hangzhou according to the IP address of user T1.In addition, determine that described Web conference is one's respective area convention according to table 2.In addition, with reference to the meeting load threshold table shown in table 3, if add, this meeting exceedes maximum meeting number threshold value (such as, 400) corresponding to the one's respective area convention in region, Hangzhou, now, this Web conference request Y needs the Region control server being forwarded to other.In this, according to the second drift strategy, domain name resolution server determines this Web conference need drift to other which regions.Such as, domain name resolution server obtain Beijing, Shanghai, the trizonal priority in Suzhou, the total play of meeting and meeting total number of persons information as described in Table 6.Wherein, area priorities is embodied by priority parameters, and the total play of meeting and meeting total number of persons are the current information in each region.
Region Priority parameters The total play of meeting Meeting total number of persons Relatively parameter
Beijing 0.95 670 10432 0.95×670+0.95×10432=10546.9
Shanghai 0.9 795 13648 0.9×795+0.9×13648=12998.7
Suzhou 0.85 918 14688 0.85×918+0.85×14688=13265.1
Table 6
As shown in Table 6, the comparison parameter of Beijing Area is minimum, and therefore, domain name resolution server determines that target area is Beijing Area.The Region control server of Beijing Area determines corresponding targeted loads equalization server according to the conference type of Web conference request Y, and targeted loads equalization server is according to the allocation strategy determination first object Service Process Server preset.In this, the corresponding load-balanced server of each conference type in each region.Still for Web conference request Y, the Region control server of Beijing Area according to the conference type of Web conference request (such as, one's respective area convention), then determine that targeted loads equalization server is the load-balanced server corresponding to one's respective area convention, afterwards, this targeted loads equalization server is according to allocation strategy determination first object Service Process Server.Wherein, described allocation strategy comprises: select the highest Service Process Server of CPU idleness to distribute, or, select the highest Service Process Server of priority to distribute.But the present invention does not limit this.In addition, if first object Service Process Server does not reach early warning value when the meeting number of pre-treatment, then the address information of target area and first object Service Process Server is updated to drift record sheet by domain name resolution server.If the Web conference number that first object Service Process Server works as pre-treatment reaches early warning value, then first object Service Process Server is tactful in Web conference Request routing to the second target service processing server according to the first drift, meanwhile, target area and the second target service processing server are updated to drift record sheet by domain name resolution server.Now, domain name resolution server upgrades drift record sheet, the address information of the second target service processing server is replaced the address information of first object Service Process Server.Particular content about the first drift strategy is same as above, therefore repeats no more in this.
In addition, in the present embodiment, whether domain name resolution server exceedes corresponding maximum meeting number threshold value according to the active conference number of the different conference type in all regions of meeting load threshold table fixed time testing, if the active conference number of the corresponding conference type of respective regions exceedes corresponding maximum meeting number threshold value, domain name resolution server determines target area according to the second drift strategy, the load-balanced server of the corresponding conference type in target area is according to allocation strategy determination first object Service Process Server, or, described first object Service Process Server determines the second target service processing server according to the first drift strategy, described target area and described first object Service Process Server or described second target service processing server are updated to described drift record sheet by domain name resolution server.About the determination of target area and target service processing server and renewal process same as above, therefore to repeat no more in this.
Figure 2 shows that the schematic diagram of the system that realizes of the meeting drift that preferred embodiment according to the present invention provides.As shown in Figure 2, the system that realizes of the meeting drift that preferred embodiment of the present invention provides comprises domain name resolution server 20, Region control server 21a ~ 21c, load-balanced server 22a ~ 22c, 23a ~ 23c, 24a ~ 24c, Service Process Server a1 ~ a3, b1 ~ b3, c1 ~ c3, d1 ~ d3, e1 ~ e3, f1 ~ f3, g1 ~ g3, h1 ~ h3, k1 ~ k3 and distributed cache server 30.In this, be described for three Region control servers.Domain name resolution server 20 join domain Control Server 21a ~ 21c, each Region control server correspondence connects three load-balanced servers, and each load-balanced server correspondence connects three Service Process Server.Domain name resolution server 20 is directly connected Service Process Server or is connected with Service Process Server by Region control server, load-balanced server, and distributed cache server 30 connects Service Process Server.But, the number of the present invention not localized area Control Server, load-balanced server and Service Process Server.
In the present embodiment, domain name resolution server 20, for receiving and resolving the conference parameters information of carrying in the Web conference request of user's transmission, determine meeting numbering, conference type and the region belonging to described user, if the meeting numbering of Web conference request is not present in exception routing rule table, then judge according to meeting load threshold table whether the active conference number of the described conference type in described region exceedes corresponding maximum meeting number threshold value.If exceed, domain name resolution server 20, for inquiring about drift record sheet, if corresponding target area and first object Service Process Server are (such as after the described conference type drift of drift record sheet storage networking request for conference affiliated area, Service Process Server a1), then domain name resolution server 20, for being routed directly to first object Service Process Server (such as, Service Process Server a1) according to drift record sheet by Web conference request.If first object Service Process Server (such as, Service Process Server a1) reach early warning value when the Web conference number of pre-treatment, first object Service Process Server (such as, Service Process Server a1), for tactful by Web conference Request routing to the second target service processing server (such as according to the first drift, Service Process Server b1), domain name resolution server 20, for the second target service processing server (such as, Service Process Server b1) is updated to drift record sheet.About the specific operation process of said system with described in said method, therefore repeat no more in this.
In sum, the implementation method of the meeting drift provided according to present pre-ferred embodiments and system, when according to meeting load threshold table, domain name resolution server judges that the active conference number of corresponding conference type in respective regions exceedes corresponding maximum meeting number threshold value, domain name resolution server inquiry drift record sheet.If corresponding target area and first object Service Process Server after the conference type drift of drift record sheet storage networking request for conference affiliated area, then domain name resolution server directly by Web conference Request routing to first object Service Process Server.If corresponding target area and first object Service Process Server after the conference type drift of drift record sheet non-storage networking request for conference affiliated area, then domain name resolution server determines according to the second drift strategy the target area that Web conference is corresponding, the load-balanced server of target area is according to allocation strategy determination first object Service Process Server, or first object Service Process Server determines the second target service processing server according to the first drift strategy.So, the Web conference request of the corresponding conference type of respective regions is directly drifted about according to drift record sheet by domain name resolution server, through Region control server and load-balanced server, thus need not improve communication efficiency.In addition, drift is realized to the Web conference exceeding corresponding maximum meeting number threshold value, simultaneously, drift is realized to the Web conference exceeding Service Process Server early warning value, thus realize the drift of single game meeting, make server cluster load more balanced, improve communication efficiency.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.

Claims (7)

1. an implementation method for meeting drift, is characterized in that, comprise the following steps:
Domain name resolution server receives and resolves the conference parameters information of carrying in the Web conference request of user's transmission, determine meeting numbering, conference type and the region belonging to described user, if the meeting numbering of described Web conference request is not present in exception routing rule table, then judge according to meeting load threshold table whether the active conference number of the described conference type in described region exceedes corresponding maximum meeting number threshold value;
If exceed, domain name resolution server inquiry drift record sheet, if described drift record sheet stores the described rear corresponding target area of conference type drift and the first object Service Process Server of described Web conference request affiliated area, then described Web conference request is routed directly to described first object Service Process Server according to described drift record sheet by domain name resolution server;
If the Web conference number that described first object Service Process Server works as pre-treatment reaches early warning value, described first object Service Process Server is tactful in described Web conference Request routing to the second target service processing server according to the first drift, and described second target service processing server is updated to described drift record sheet by domain name resolution server;
If according to described meeting load threshold table, domain name resolution server judges that the active conference number obtaining the corresponding conference type of described Web conference request affiliated area exceedes corresponding maximum meeting number threshold value, and described drift record sheet does not store the described rear corresponding target area of conference type drift and the first object Service Process Server of described Web conference request affiliated area, then domain name resolution server determines target area according to the second drift strategy, the load-balanced server of the corresponding conference type in described target area is according to allocation strategy determination first object Service Process Server, or, described first object Service Process Server determines the second target service processing server according to the first drift strategy, described target area and described first object Service Process Server or described second target service processing server are updated to described drift record sheet by domain name resolution server,
Described second drift strategy is: the meeting total number of persons according to the total play of the meeting of area priorities, regional and regional determines the target area that described Web conference request is corresponding.
2. method according to claim 1, it is characterized in that, whether domain name resolution server exceedes corresponding maximum meeting number threshold value according to the active conference number of the different conference type in all regions of described meeting load threshold table fixed time testing, if the active conference number of the corresponding conference type of respective regions exceedes corresponding maximum meeting number threshold value, domain name resolution server determines target area according to the second drift strategy, the load-balanced server of the corresponding conference type in target area is according to allocation strategy determination first object Service Process Server, or, described first object Service Process Server determines the second target service processing server according to the first drift strategy, described target area and described first object Service Process Server or described second target service processing server are updated to described drift record sheet by domain name resolution server.
3. method according to claim 1 and 2, it is characterized in that, described first drift strategy is: described first object Service Process Server according to the priority determination targeted loads equalization server of conference type and by described Web conference Request routing to described targeted loads equalization server, described targeted loads equalization server according to described allocation strategy by described Web conference Request routing to the second target service processing server.
4. method according to claim 1 and 2, it is characterized in that, described first drift strategy is: described first object Service Process Server is by the load-balanced server corresponding with described conference type, meeting drift request is sent to affiliated Region control server, described Region control server is according to the priority of described meeting drift request and conference type, determine targeted loads equalization server, and by the load-balanced server corresponding with described conference type, the address information of described targeted loads equalization server is sent to described first object Service Process Server, described first object Service Process Server is according to described address information, by described Web conference Request routing to described targeted loads equalization server, described targeted loads equalization server according to described allocation strategy by described Web conference Request routing to the second target service processing server.
5. method according to claim 1, is characterized in that, described conference parameters information comprises meeting numbering, meeting number information, participant's area information and address information.
6. method according to claim 1, is characterized in that, described conference type comprises general meeting, one's respective area convention and trans-regional convention.
7. method according to claim 1, it is characterized in that, domain name resolution server stores described exception routing rule table, and described exception routing rule table stores the corresponding relation of the meeting numbering of the Web conference request of all drifts and the address information of corresponding Service Process Server.
CN201210334794.6A 2012-09-12 2012-09-12 Method and system for realizing meeting drift Active CN102868776B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201210334794.6A CN102868776B (en) 2012-09-12 2012-09-12 Method and system for realizing meeting drift

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201210334794.6A CN102868776B (en) 2012-09-12 2012-09-12 Method and system for realizing meeting drift

Publications (2)

Publication Number Publication Date
CN102868776A CN102868776A (en) 2013-01-09
CN102868776B true CN102868776B (en) 2015-05-27

Family

ID=47447361

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201210334794.6A Active CN102868776B (en) 2012-09-12 2012-09-12 Method and system for realizing meeting drift

Country Status (1)

Country Link
CN (1) CN102868776B (en)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1529462A (en) * 2003-10-21 2004-09-15 中兴通讯股份有限公司 Device and method for realizing abnormal flow control
CN101127632A (en) * 2006-08-15 2008-02-20 腾讯科技(深圳)有限公司 A method, system and redirector for server traffic control
CN101729424A (en) * 2009-12-16 2010-06-09 杭州华三通信技术有限公司 Flow forwarding method, devices and system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1529462A (en) * 2003-10-21 2004-09-15 中兴通讯股份有限公司 Device and method for realizing abnormal flow control
CN101127632A (en) * 2006-08-15 2008-02-20 腾讯科技(深圳)有限公司 A method, system and redirector for server traffic control
CN101729424A (en) * 2009-12-16 2010-06-09 杭州华三通信技术有限公司 Flow forwarding method, devices and system

Also Published As

Publication number Publication date
CN102868776A (en) 2013-01-09

Similar Documents

Publication Publication Date Title
CN103379184B (en) The method and system of Network access
TW200633428A (en) Method of controlling communication between a head-end system and a plurality of client systems
CN109257789B (en) Vehicle-mounted network data communication method based on multi-hop cluster
CN102811133B (en) Method and system for web conference drifting control
CN101364889A (en) Method for multicast user quick access
CN105450774A (en) Load balancing method and load balancing device for DNS
CN105472025A (en) Load balancing method and device based on DNS (domain name system)
CN102801619B (en) Netmeeting drift processing method and system
CN102821167B (en) A kind of processing method of Web conference drift and system
CN102801620B (en) A kind of Web conference drift control treatment method and system
CN105897542A (en) Tunnel building method and video monitoring system
CN102868776B (en) Method and system for realizing meeting drift
CN102857431A (en) Method and system for processing of conference drift
CN102820978B (en) Method and system for realizing conference drifting
CN102868541B (en) A kind of method and system of net control meeting drift
CN102833153B (en) Network meeting drifting control method and system
CN102857351B (en) A kind of method and system of meeting drift
CN102843289B (en) Meeting drift method and system
CN202261363U (en) Group messaging transmission system and instant messaging server
CN102868777A (en) Method and system for controlling meeting drift
CN102857433A (en) Method and system for processing network meeting drift
CN105515799A (en) Method and system for realizing network meeting drift
CN102739414A (en) Netmeeting drifting method and system
CN102811134A (en) Method and system for controlling drift of net meeting
CN102843241A (en) Conference drift control method and system

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
C56 Change in the name or address of the patentee
CP01 Change in the name or title of a patent holder

Address after: Suzhou City, Jiangsu province 215121 Fengting Avenue Suzhou Industrial Park No. 666 Weiting Intelligent Industrial Park Building 8

Patentee after: Kuo Di education and science company limited

Address before: Suzhou City, Jiangsu province 215121 Fengting Avenue Suzhou Industrial Park No. 666 Weiting Intelligent Industrial Park Building 8

Patentee before: Suzhou Kuodi Network Technology Co., Ltd.