CN102802203B - The load-balancing method of LTE system, device and base station - Google Patents
The load-balancing method of LTE system, device and base station Download PDFInfo
- Publication number
- CN102802203B CN102802203B CN201210272353.8A CN201210272353A CN102802203B CN 102802203 B CN102802203 B CN 102802203B CN 201210272353 A CN201210272353 A CN 201210272353A CN 102802203 B CN102802203 B CN 102802203B
- Authority
- CN
- China
- Prior art keywords
- mobile management
- management entity
- address
- allocation list
- real time
- 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
Links
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
This application provides the load-balancing method of a kind of LTE system, comprise the following steps: receive the configuration update message that mobile management entity sends; Resolve the IP address and real time capacity that obtain the mobile management entity comprised in configuration update message; Judge whether allocation list has the target ip address record identical with described IP address, if having, then described real time capacity being inserted position corresponding with target ip address in described allocation list, if not having, then described IP address and real time capacity being added in described allocation list as new record; The mobile management entity mobile management entity as new access user is chosen according to the real time capacity size of each mobile management entity. Present invention also provides the load balancing apparatus of a kind of LTE system realizing preceding method and base station. The load-balancing method of the LTE system of the application, device and base station, it is possible in config update process, ensure that the real time capacity updated is all accurately, enable load balancing normally to realize.
Description
Technical field
The application relates to mobile communication signal processing technology field, particularly relates to the load-balancing method of a kind of LTE system, device and base station.
Background technology
In a mobile network, subscriber equipment (UE, UserEquipment) multiformity of the randomness of position and business demand, can cause that the situation that cell load skewness weighs occurs, namely a part of cell load is overweight, even produce data congestion, simultaneously another part community relative free, light load. When the above-mentioned load unbalanced situation of distribution occurs, system can adopt the method for load balancing, transfers in low-load community by certain customers' equipment of high capacity community, reduces the load of high capacity community. By the portfolio distribution of balanced minizone, improve the utilization rate of Radio Resource, thus reducing cutting off rate.
In LTE system, generally reach the purpose of load balancing by operations such as switchings. One of which method is: open the S1-Flex switch of base station, by mobile management entity (MME, MobilityManagementEntity) to evolved base station (eNB, evolvedNodeB) send configuration update message (MMEConfigurationUpdate), message comprises the real time capacity (RelativeMMECapacity) of this mobile management entity. When there being new user to access, evolved base station meeting prioritizing selection real time capacity is relatively big, and the mobile management entity that namely RelativeMMECapacity value is big realizes the equilibrium of load. Such as, " RelativeMMEcapacity " of certain mobile management entity is configured to 1, and " RelativeMMEcapacity " of another mobile management entity is configured to 254, when there being new user to register, be configured to 1 the selected probability of mobile management entity only small, be 1/255; Being configured to the selected probability of mobile management entity of 254 be then greatly increased, be 254/255, the mobile management entity that namely prioritizing selection real time capacity is stronger, thus realizing load balancing.
Under normal circumstances, different mobile management entities are identified by evolved base station by the MMECode value of mobile management entity. When initiating the MMECode value of different mobile management entities of configuration update message and being identical, evolved base station will be considered that configuration update message is from same mobile management entity, consequently, it is possible to the config update led to errors, thus occurring that the actual capacity of mobile management entity and the record of evolved base station do not correspond, cause realizing load balancing. Additionally; because evolved going to the station to meet somebody can receive the configuration update message that two mobile management entities send simultaneously; if the MMECode value of these two mobile management entities is identical; evolved base station will be considered that configuration update message is from same mobile management entity equally; now it would generally think that the configuration update message first received is effective; the configuration update message of rear reception is invalid; now evolved base station cannot selecting according to the real time capacity of each mobile management entity, therefore also just cannot realize load balancing. In some situation, even without comprising MMECode in configuration update message, config update and load balancing now also cannot be realized.
Summary of the invention
The application provides the load-balancing method of a kind of LTE system, device and base station, it is possible to solve the problem that load balancing cannot normally realize.
In order to solve the problems referred to above, this application discloses the load-balancing method of a kind of LTE system, comprise the following steps:
Receive the configuration update message that mobile management entity sends;
Resolve the IP address and real time capacity that obtain the mobile management entity comprised in configuration update message;
Judge whether allocation list has the target ip address record identical with described IP address, if having, then described real time capacity being inserted position corresponding with target ip address in described allocation list, if not having, then described IP address and real time capacity being added in described allocation list as new record;
The mobile management entity mobile management entity as new access user is chosen according to the real time capacity size of each mobile management entity.
Further, described choose mobile management entity according to the real time capacity size of each mobile management entity and include as the mobile management entity of new access user:
Select the mobile management entity with maximum real time capacity as the mobile management entity of new access user; Or
Set capacity threshold, an optional mobile management entity as new access user from the multiple mobile management entities exceeding this capacity threshold, if being not above the mobile management entity of this capacity threshold, then choose the mobile management entity with maximum real time capacity as the mobile management entity of new access user.
Further, also include after the described IP address resolving the mobile management entity comprised in acquisition configuration update message and real time capacity:
Resolve the MMECode obtaining the mobile management entity comprised in configuration update message, judge whether allocation list has the target MMECode record identical with described MMECode, if having, then carry out the step after the described IP address and real time capacity resolving and obtaining the mobile management entity comprised in configuration update message;
Otherwise, then described MMECode, real time capacity and IP address are added in described allocation list as new record, and choose the mobile management entity mobile management entity as new access user according to the real time capacity size of each mobile management entity.
Further, also include before the configuration update message that described reception mobile management entity sends:
The IP address of the mobile management entity in acquisition base station signal coverage;
Send to the IP address of described each mobile management entity and initially set request;
The IP address responding the described initial mobile management entity setting request be recorded in allocation list.
Disclosed herein as well is the load balancing apparatus of a kind of LTE system, including:
Message reception module, for receiving the configuration update message that mobile management entity sends;
Message resolution module, for resolving the IP address and real time capacity obtaining the mobile management entity comprised in configuration update message;
Judge module, for judging whether allocation list has the target ip address record identical with described IP address, if having, then described real time capacity is inserted position corresponding with target ip address in described allocation list, if no, then described IP address and real time capacity being added in described allocation list as new record;
Mobile management entity distribution module, for choosing the mobile management entity mobile management entity as new access user according to the real time capacity size of each mobile management entity.
Further, described mobile management entity distribution module includes:
Capability value comparison module, for selecting the mobile management entity with maximum real time capacity as the mobile management entity of new access user; Or
Set capacity threshold, an optional mobile management entity as new access user from the multiple mobile management entities exceeding this capacity threshold, if being not above the mobile management entity of this capacity threshold, then choose the mobile management entity with maximum real time capacity as the mobile management entity of new access user.
Further, described message resolution module is additionally operable to resolve the MMECode obtaining the mobile management entity comprised in configuration update message, and described judge module is additionally operable to judge whether there be the target MMECode record identical with described MMECode in allocation list.
Further, described device also includes:
IP address acquisition unit, for obtaining the IP address of the mobile management entity in base station signal coverage;
Request transceiver module, initially sets request for sending to the IP address of described each mobile management entity;
Information logging modle, for recorded the IP address responding the described initial mobile management entity setting request in allocation list.
Disclosed herein as well is a kind of base station, including foregoing load balancing apparatus.
Compared with prior art, the application includes advantages below:
The load-balancing method of the LTE system of the application, device and base station are by being identified the IP address of mobile management entity as the identifier of mobile management entity. Because for mobile management entity, its IP address is unique fixing, the accuracy of identification is can ensure that, thus ensureing that in the process of config update the real time capacity updated is all accurately, thus proof load equilibrium can normally realize by this kind of mode.
Secondly, by the mode that IP address and MMECode combine, it is possible to quickly determine the mobile management entity needing config update. If MMECode is different, then can carry out config update, it is not necessary to compare IP address again. Identical for MMECode, then carry out IP address and compare, if different, it is also possible to carry out config update, therefore can ensure that the accuracy of config update, thus realizing load balancing.
It addition, receive before configuration update message in base station, in advance by the mobile management entity relevant information record that may relate in allocation list, when receiving configuration update message, then can be made directly renewal, it is not necessary to typing extraneous information in real time, it is possible to improve the treatment effeciency of config update. When recording mobile management entity relevant information, by whether the mode that the request of base station is responded, determine the mobile management entity having normal data mutual with base station, such that it is able to the IP address of original typing is screened, thus reducing the data volume of allocation list, avoid taking too much memory space, workload and the cost of data maintenance can be reduced simultaneously.
Certainly, the arbitrary product implementing the application is not necessarily required to reach all the above advantage simultaneously.
Accompanying drawing explanation
In order to be illustrated more clearly that the embodiment of the present application or technical scheme of the prior art, the accompanying drawing used required in embodiment will be briefly described below, apparently, accompanying drawing in the following describes is only some embodiments of the application, for those of ordinary skill in the art, under the premise not paying creative work, it is also possible to obtain other accompanying drawing according to these accompanying drawings.
Fig. 1 is the flow chart of the load-balancing method embodiment one of the LTE system of the application;
Fig. 2 is the flow chart of the load-balancing method embodiment two of the LTE system of the application;
Fig. 3 is the flow chart of the load-balancing method embodiment three of the LTE system of the application;
Fig. 4 is the structural representation of the load balancing apparatus embodiment one of the LTE system of the application;
Fig. 5 is the structural representation of the load balancing apparatus embodiment two of the LTE system of the application.
Detailed description of the invention
Below in conjunction with the accompanying drawing in the embodiment of the present application, the technical scheme in the embodiment of the present application is clearly and completely described, it is clear that described embodiment is only some embodiments of the present application, rather than whole embodiments. Based on the embodiment in the application, the every other embodiment that those of ordinary skill in the art obtain, broadly fall into the scope of the application protection.
With reference to Fig. 1, it is shown that the load-balancing method embodiment one of a kind of LTE system of the application, comprise the following steps:
Step 101, receives the configuration update message that mobile management entity sends.
Step 102, resolves the IP address and real time capacity that obtain the mobile management entity comprised in configuration update message.
Base station is receiving mobile management entity (MME, MobilityManagementEntity) after configuration update message (MMEConfigurationUpdate), according to configuration update message form, it is resolved, obtain IPIE therein, Src parameter and RelativeMMECapacity, respectively obtain IP address and the real time capacity of mobile management entity.
Step 103, judge whether allocation list has the target ip address record identical with described IP address, if having, then described real time capacity is inserted position corresponding with target ip address in described allocation list, if no, then described IP address and real time capacity being added in described allocation list as new record.
Base station can safeguard that allocation list is to store the relevant informations such as the IP address of each mobile management entity, real time capacity, MMECode in advance. Shown in table 1 specific as follows:
Table 1
| Record | MME IP Src | MME Code | Relative MME Capacity |
| 0 | 192.168.20.51 | 0 | 1 |
| 1 | 192.168.20.10 | 0 | 254 |
It is appreciated that table 1 is a concrete example, in concrete processing procedure, if MMECode will not be used, it is also possible to omit from allocation list, if desired other information, it is also possible to accordingly increase.
After being analyzed and acquired by the IP address of mobile management entity of transmission configuration update message, this IP address can be carried out matched and searched with the IP address of record in allocation list by base station, if can find, then illustrate allocation list have recorded the relevant information of this mobile management entity, now, then directly real time capacity is filled in position corresponding in allocation list, it is achieved the config update of this mobile management entity. If can not find, then illustrate this allocation list not yet records the relevant information of this mobile management entity, now, then need to add in allocation list real time capacity and IP address to as new record. Being appreciated that the mode of matched and searched can adopt string matching or other lookup modes, this is not limiting as by the application.
Step 104, chooses the mobile management entity mobile management entity as new access user according to the real time capacity size of each mobile management entity.
Wherein, choosing according to the real time capacity size of each mobile management entity can be select the mobile management entity with maximum real time capacity as the mobile management entity of new access user. Capacity threshold can also be set, an optional mobile management entity as new access user from the multiple mobile management entities exceeding this capacity threshold, if being not above the mobile management entity of this capacity threshold, then choose the mobile management entity with maximum real time capacity as the mobile management entity of new access user.
The load-balancing method of the LTE system of the application is by being identified the IP address of mobile management entity as the identifier of mobile management entity. Because for mobile management entity, its IP address is unique fixing, the accuracy of identification is can ensure that, thus ensureing that in the process of config update the real time capacity updated is all accurately, thus proof load equilibrium can normally realize by this kind of mode.
Preferably, the load-balancing method embodiment one of the LTE system of the application uniquely identifies mobile management entity by IP address. Because in most cases, the MMECode of each mobile management entity or different, for this, it is also possible to identify mobile management entity first with MMECode, if during None-identified, recycling IP address is identified. Now, at least need to record MMECode, real time capacity and IP address information in the allocation list of base station simultaneously.
With reference to Fig. 2, it is shown that the load-balancing method embodiment two of the LTE system of the application, can also comprise the following steps between step 102 and the step 103 of embodiment one:
Step 201, resolves the MMECode obtaining the mobile management entity comprised in configuration update message, it is judged that whether having the target MMECode record identical with described MMECode in allocation list, if having, then carrying out step 103; Otherwise, then described MMECode, real time capacity and IP address are added in described allocation list as new record, and carry out step 104.
If that is, mobile management entity can be identified by MMECode, then be no need for recycling IP address and be identified. But, mobile management entity situation of not this mobile management entity relative recording suitable in allocation list is identified by MMECode, if have recorded, in order to ensure the accuracy of config update, it is accomplished by carrying out the comparison of IP geology, only when IP address is identical, just can think same mobile management entity. If being only that MMECode is identical, then it is not construed as unified mobile management entity. As long as namely IP address differs, it is possible to the relevant configuration information of this mobile management entity in allocation list is updated by the relevant parameter according to resolving acquisition from configuration update message. It is appreciated that, for the MMECode resolving the mobile management entity comprised in acquisition configuration update message in this step, judging whether there be the target MMECode record identical with described MMECode in allocation list, it is also possible to before step 102, its order does not limit.
By the mode that IP address and MMECode combine, it is possible to quickly determine the mobile management entity needing config update. If MMECode is different, then can carry out config update, it is not necessary to compare IP address again. Identical for MMECode, then carry out IP address and compare, if different, it is also possible to carry out config update, therefore can ensure that the accuracy of config update, thus realizing load balancing.
For the relevant information in allocation list, it is possible to resolving record after obtaining from the configuration update message that mobile management entity sends, namely the primary data in allocation list can be empty, when base station is further filled with after resolving from which after have received new configuration update message and obtaining. Preferably, in order to improve the treatment effeciency of config update, base station can also be collected the relevant information of each mobile management entity in advance and is filled in allocation list, and detailed process is as follows:
With reference to Fig. 3, it is shown that the load-balancing method embodiment three of the LTE system of the application, can also comprise the following steps before the step 101 of embodiment one and/or embodiment two:
Step 301, the IP address of the mobile management entity in acquisition base station signal coverage.
Wherein, the IP address of mobile management entity and other data are obtained by core net producer when network design by BTS management side. Can directly enter in the data base that base station is corresponding, it is also possible to exist somewhere, base station obtain from the reading of this place. Preferably, BTS management side is when typing IP address, in addition it is also necessary to IP address and routing relation are configured, for instance the information such as the type of IP address, routing index.
Step 302, sends to the IP address of described each mobile management entity and initially sets request.
Step 303, recorded the IP address responding the described initial mobile management entity setting request in allocation list.
Concrete initial setting request can be S1-SetupRequest message, if having normal data interaction with base station, mobile management entity can respond S1-SetupResponse message. Namely the IP address having the mobile management entity of response can be recorded in allocation list by base station. When subsequent movement management entity sends configuration update message, base station then can resolve IP address therein, and carries out matching ratio relatively with the IP address in allocation list, thus realizing config update.
Because it is possible that in the mobile management entity corresponding to IP address that records of base station, have part and base station be likely to and cannot normal data mutual, by whether the mode that the request of base station is responded, can determine that the mobile management entity having normal data mutual with base station, such that it is able to the IP address of original typing is screened, thus reducing the data volume of allocation list, it is to avoid take too much memory space, workload and the cost of data maintenance can be reduced simultaneously.
It is appreciated that, in the aforementioned embodiment, when base station receives the configuration update message of two or more mobile management entity simultaneously, even if these mobile management entities have identical MMECode, as long as its IP address is different, it can also be carried out config update by base station respectively, thus avoiding the mobile entity with identical MMECode cannot all realize the situation of config update or config update mistake.
With reference to Fig. 4, it is shown that the load balancing apparatus embodiment one of the LTE system of the application, distribute module 40 including message reception module 10, message resolution module 20, judge module 30 and mobile management entity.
Message reception module 10, for receiving the configuration update message that mobile management entity sends.
Message resolution module 20, for resolving the IP address and real time capacity obtaining the mobile management entity comprised in configuration update message.
Judge module 30, for judging whether allocation list has the target ip address record identical with described IP address, if having, then described real time capacity is inserted position corresponding with target ip address in described allocation list, if no, then described IP address and real time capacity being added in described allocation list as new record.
Mobile management entity distribution module 40, for choosing the mobile management entity mobile management entity as new access user according to the real time capacity size of each mobile management entity. Preferably, mobile management entity distribution module includes capability value comparison module, for selecting the mobile management entity with maximum real time capacity as the mobile management entity of new access user; Or setting capacity threshold, an optional mobile management entity as new access user from the multiple mobile management entities exceeding this capacity threshold, if being not above the mobile management entity of this capacity threshold, then choose the mobile management entity with maximum real time capacity as the mobile management entity of new access user.
Preferably, message resolution module 20 is additionally operable to resolve the MMECode obtaining the mobile management entity comprised in configuration update message, described judge module 30 is additionally operable to judge whether there be the target MMECode record identical with described MMECode in allocation list, if having, then continue to judge whether allocation list has the target ip address record identical with described IP address, otherwise, then described MMECode, real time capacity and IP address are added in described allocation list as new record.
With reference to Fig. 5, it is shown that the load balancing apparatus embodiment two of the LTE system of the application, this device also includes IP address acquisition unit 51, request transceiver module 53 and information logging modle 55.
IP address acquisition unit 51, for obtaining the IP address of the mobile management entity in base station signal coverage.
Request transceiver module 53, initially sets request for sending to the IP address of described each mobile management entity.
Information logging modle 55, for recorded the IP address responding the described initial mobile management entity setting request in allocation list.
The application also provides for a kind of base station, including foregoing load balancing apparatus.
As seen through the above description of the embodiments, those skilled in the art is it can be understood that can add the mode of required general hardware platform by software to the application and realize. Based on such understanding, the part that prior art is contributed by the technical scheme of the application substantially in other words can embody with the form of software product, this computer software product can be stored in storage medium, such as ROM/RAM, magnetic disc, CD etc., including some instructions with so that a computer equipment (can be personal computer, server, or the network equipment etc.) perform the method described in some part of each embodiment of the application or embodiment.
Each embodiment in this specification all adopts the mode gone forward one by one to describe, between each embodiment identical similar part mutually referring to, what each embodiment stressed is the difference with other embodiments. Especially for device or system embodiment, owing to it is substantially similar to embodiment of the method, so describing fairly simple, relevant part illustrates referring to the part of embodiment of the method. Device described above and device embodiment are merely schematic, the wherein said unit illustrated as separating component can be or may not be physically separate, the parts shown as unit can be or may not be physical location, namely may be located at a place, or can also be distributed on multiple NE. Some or all of module therein can be selected according to the actual needs to realize the purpose of the present embodiment scheme. Those of ordinary skill in the art, when not paying creative work, are namely appreciated that and implement.
Above the load-balancing method of LTE system provided herein, device and base station are described in detail, principle and the embodiment of the application are set forth by specific case used herein, and the explanation of above example is only intended to help and understands the present processes and core concept thereof; Simultaneously for one of ordinary skill in the art, according to the thought of the application, all will change in specific embodiments and applications, in sum, this specification content should not be construed as the restriction to the application.
Claims (7)
1. the load-balancing method of a LTE system, it is characterised in that comprise the following steps:
Receive the configuration update message that mobile management entity sends;
Resolve the IP address and real time capacity that obtain the mobile management entity comprised in configuration update message;
Resolve the MMECode obtaining the mobile management entity comprised in configuration update message, it is judged that whether allocation list has the target MMECode record identical with described MMECode;
If allocation list has the target MMECode record identical with described MMECode, then judge whether allocation list has the target ip address record identical with described IP address, if allocation list has the target ip address record identical with described IP address, then described real time capacity is inserted position corresponding with target ip address in described allocation list, if target ip address record not identical with described IP address in allocation list, then described IP address and real time capacity are added in described allocation list as new record; Wherein, described allocation list is safeguarded in advance and stores the allocation list having the relevant information of each mobile management entity of collection in advance; Described relevant information includes: the IP address of each mobile management entity, real time capacity and MMECode;
If target MMECode record not identical with described MMECode in allocation list, then described MMECode, real time capacity and IP address are added in described allocation list as new record;
The mobile management entity mobile management entity as new access user is chosen according to the real time capacity size of each mobile management entity of record in the allocation list after updating.
2. the load-balancing method of LTE system as claimed in claim 1, it is characterised in that described choose mobile management entity according to the real time capacity size of each mobile management entity and include as the mobile management entity of new access user:
Select the mobile management entity with maximum real time capacity as the mobile management entity of new access user; Or
Set capacity threshold, an optional mobile management entity as new access user from the multiple mobile management entities exceeding this capacity threshold, if being not above the mobile management entity of this capacity threshold, then choose the mobile management entity with maximum real time capacity as the mobile management entity of new access user.
3. the load-balancing method of LTE system as claimed in claim 1 or 2, it is characterised in that also include before the configuration update message that described reception mobile management entity sends:
The IP address of the mobile management entity in acquisition base station signal coverage;
Send to the IP address of described each mobile management entity and initially set request;
The IP address responding the described initial mobile management entity setting request be recorded in allocation list.
4. the load balancing apparatus of a LTE system, it is characterised in that including:
Message reception module, for receiving the configuration update message that mobile management entity sends;
Message resolution module, for resolving the IP address and real time capacity obtaining the mobile management entity comprised in configuration update message;
Judge module, for judging whether allocation list has the target ip address record identical with described IP address, if having, then described real time capacity is inserted position corresponding with target ip address in described allocation list, if no, then described IP address and real time capacity being added in described allocation list as new record; Wherein, described allocation list is safeguarded in advance and stores the allocation list having the relevant information of each mobile management entity of collection in advance; Described relevant information includes: the IP address of each mobile management entity, real time capacity and MMECode;
Mobile management entity distribution module, for choosing the mobile management entity mobile management entity as new access user according to the real time capacity size of each mobile management entity of record in the allocation list after updating;
Wherein, described message resolution module is additionally operable to resolve the MMECode obtaining the mobile management entity comprised in configuration update message; Described judge module is additionally operable to judge whether there be the target MMECode record identical with described MMECode in allocation list; If having, then continue to judge whether allocation list has the target ip address record identical with described IP address, otherwise, then described MMECode, real time capacity and IP address are added in described allocation list as new record.
5. the load balancing apparatus of LTE system as claimed in claim 4, it is characterised in that described mobile management entity distribution module includes:
Capability value comparison module, for selecting the mobile management entity with maximum real time capacity as the mobile management entity of new access user; Or
Set capacity threshold, an optional mobile management entity as new access user from the multiple mobile management entities exceeding this capacity threshold, if being not above the mobile management entity of this capacity threshold, then choose the mobile management entity with maximum real time capacity as the mobile management entity of new access user.
6. the load balancing apparatus of the LTE system as described in claim 4 or 5, it is characterised in that described device also includes:
IP address acquisition unit, for obtaining the IP address of the mobile management entity in base station signal coverage;
Request transceiver module, initially sets request for sending to the IP address of described each mobile management entity;
Information logging modle, for recorded the IP address responding the described initial mobile management entity setting request in allocation list.
7. a base station, it is characterised in that include the load balancing apparatus as described in any one of claim 4 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210272353.8A CN102802203B (en) | 2012-08-01 | 2012-08-01 | The load-balancing method of LTE system, device and base station |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210272353.8A CN102802203B (en) | 2012-08-01 | 2012-08-01 | The load-balancing method of LTE system, device and base station |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102802203A CN102802203A (en) | 2012-11-28 |
| CN102802203B true CN102802203B (en) | 2016-06-15 |
Family
ID=47201144
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210272353.8A Active CN102802203B (en) | 2012-08-01 | 2012-08-01 | The load-balancing method of LTE system, device and base station |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102802203B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101754492A (en) * | 2008-12-02 | 2010-06-23 | 大唐移动通信设备有限公司 | S1-MME interface automatic configuration method, system and device |
| CN102084705A (en) * | 2008-11-17 | 2011-06-01 | 思达伦特网络有限责任公司 | Dynamic load balancing in a communication network |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101577964B (en) * | 2008-11-11 | 2014-06-11 | 中兴通讯股份有限公司南京分公司 | Method for addressing interworking gateways |
-
2012
- 2012-08-01 CN CN201210272353.8A patent/CN102802203B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102084705A (en) * | 2008-11-17 | 2011-06-01 | 思达伦特网络有限责任公司 | Dynamic load balancing in a communication network |
| CN101754492A (en) * | 2008-12-02 | 2010-06-23 | 大唐移动通信设备有限公司 | S1-MME interface automatic configuration method, system and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102802203A (en) | 2012-11-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102476531B1 (en) | Data Synchronization Method and Apparatus, Media, and Electronic Device for Distributed Systems | |
| KR102009614B1 (en) | Communication system, base station, communication method, and non-transitory computer readable medium storing program | |
| CN103002415B (en) | A kind of method and apparatus by short message sending identifying code | |
| US10887751B1 (en) | Systems and methods for facilitating network function device discovery | |
| CN108259328B (en) | Message forwarding method and device | |
| CN104572727A (en) | Data querying method and device | |
| US10430414B2 (en) | Method and apparatus for sharing environment context | |
| CN105653662A (en) | Flume based data processing method and apparatus | |
| US20150088995A1 (en) | Method and apparatus for sharing contents using information of group change in content oriented network environment | |
| CN104954431A (en) | Network selection method, device and system | |
| CN108984433B (en) | Cache data control method and equipment | |
| US11463376B2 (en) | Resource distribution method and apparatus in Internet of Things, device, and storage medium | |
| GB2449173A (en) | Resource management in a wireless access network | |
| JPWO2018131413A1 (en) | Mobile communication system and congestion control method | |
| CN109783564A (en) | Support the distributed caching method and equipment of multinode | |
| CN107172214A (en) | A kind of service node with load balancing finds method and device | |
| CN103259869A (en) | Concentrated information management method based on distributed data storage | |
| CN104144170A (en) | URL filtering method, device and system | |
| CN104426816A (en) | Virtual machine communication method and device | |
| CN103106242A (en) | Phone bill query method and phone bill query system | |
| US10009265B2 (en) | Communication control apparatus, communication control method, communication system, and recording medium | |
| CN105578566A (en) | Terminal network searching method and terminal | |
| CN102802203B (en) | The load-balancing method of LTE system, device and base station | |
| CN105657014A (en) | Load balancing method, system and system | |
| CN105340238A (en) | System and method of ANQP querying using common ANQP group version |
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 |