CN101287169B - Transmission method of S1 interface application protocol identification - Google Patents
Transmission method of S1 interface application protocol identification Download PDFInfo
- Publication number
- CN101287169B CN101287169B CN2008101113266A CN200810111326A CN101287169B CN 101287169 B CN101287169 B CN 101287169B CN 2008101113266 A CN2008101113266 A CN 2008101113266A CN 200810111326 A CN200810111326 A CN 200810111326A CN 101287169 B CN101287169 B CN 101287169B
- Authority
- CN
- China
- Prior art keywords
- s1ap
- mme
- enodeb
- message
- carry
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method for transmitting an S1 interface application protocol mark, which avoids the inconsistence of UE S1AP ID between network elements caused by the change of the UE S1AP ID. The S1 interface is connected with an evolutive node B eNodeB and a mobile management entity (MME). The method comprises that: when the mark of the UE S1AP ID of certain user equipment on the S1 interface which is the exclusive mark distributed by a self-terminal changes, a message sent to an opposite terminal carries a newly distributed UE S1AP ID; after receiving the message sent by the self-terminal, the opposite terminal judges whether the message carries the UE S1AP ID or not distributed by the self-terminal, if yes, the opposite terminal uses the UE S1AP ID carried in the message and newly distributed by the self-terminal to replace the old UE S1AP ID saved by the opposite terminal locally.
Description
Technical field
The present invention relates to field of wireless communication, particularly a kind of method of in System Architecture Evolution (SAE), transmitting S1AP ID (S1 interface application protocol identification).
Background technology
3GPP (3rd Generation Partnership Project, third generation partner program) to the project of mobile wireless network of future generation System Architecture Evolution (System Architecture Evolution is called for short SAE).The security architecture of SAE has wherein comprised following network element as shown in Figure 1:
E-RAN (Evolved RAN): the wireless access network of evolution can provide higher up-downgoing speed, lower transmission delay and reliable more wireless transmission.The network element that comprises among the E-RAN is eNodeB (Evolved NodeB, the Node B of evolution), for the access of terminal provides Radio Resource.
HSS (Home Subscriber Server): home subscriber server, permanent storage user contracting data.
PDN (Packet Data Network): Packet Data Network, for the user provides professional network.
E-Packet Core: the Packet Based Network of evolution, improved lower delay, and allowed more wireless access system to insert.Comprised following network element:
MME (Mobility Management Entity, mobile management entity): the chain of command functional entity, the server of interim storaging user data, be in charge of and store the UE context (such as the UE/ user ID, mobility management states, user security parameters etc.), for the user distributes temporary mark, when quartering at this tracing area or this network, is responsible for UE this user is carried out authentication; Handle all non-access layer informations between MME and the UE; Triggering is in the paging of SAE.
Serving GW (Gateway): gateway, this gateway are user entities, are responsible for the user face data route and handle, and termination is in the downlink data of the UE of idle condition.SAE carrying (bearer) context of management and storage UE is such as IP bearer service parameter and network internal routing iinformation etc.Be the anchor point of 3GPP internal system user face, a user can only have a Serving GW a moment;
PDN GW: packet data network gateway, be responsible for the gateway that UE inserts PDN, distributing user IP address is the mobility anchor point of 3GPP and non-3GPP connecting system simultaneously.The user can insert a plurality of PDN GW at synchronization.
PCRF (Policy and Charging Rule Functionality): "Policy and Charging Rules Function entity, this functional entity mainly produces Qos (Quality of Service, service quality) rule and the charging regulation of control user data delivery according to the configuration information of business information and user signing contract information and operator.This functional entity also can be controlled the foundation and the release of carrying in the Access Network.
Physically, Serving GW and PDN GW may unify.
In SAE, eNB UE S1AP ID (Unique identity of the UE over the S1 interfacewithin eNodeB) is in the eNB internal distribution, identifies a UE on the S1 interface uniquely.After MME receives eNB UE S1AP ID, should connect duration of existence at the relevant logic S1 of UE and preserve.Similarly, MME UE S1AP ID (Unique identity of the UE over the S1 interfacewithin MME) is in the MME internal distribution, identifies a UE on the S1 interface uniquely.After eNB receives MME UE S1AP ID, should connect duration of existence at the relevant logic S1 of UE and preserve.
Under the normal condition, eNB UE S1AP ID and the MME UE S1AP ID relevant with a UE do not change, and just relevant with this UE S1AP links the sign unanimity that both sides preserve when setting up.But scene that UE S1AP ID changes (for example switching), problem that network element internal is realized are taking place, taking place under the situation such as exception error, the UE S1AP ID that brings the other side's local terminal distribution may change, at this moment the opposite end UE S1AP ID and local inconsistent situation of preserving that carries in the message can appear receiving in the opposite end network element, the situation of should planting is also had no idea to handle at present, the probability height of makeing mistakes, and can influence user's regular traffic.
Summary of the invention
The technical problem to be solved in the present invention provides a kind of transmission method of S1 interface application protocol identification, avoids causing the UE S1AP ID between network element inconsistent owing to UE S1AP ID changes.
In order to solve the problems of the technologies described above, the invention provides a kind of transmission method of S1 interface application protocol identification, described S1 interface is connecting the Node B eNodeB and the mobile management entity MME of evolution, described method comprises: when the sign UE S1APID of certain subscriber equipment on the unique identification S1 interface that local terminal distributes changes, carry newly assigned UE S1AP ID in the message that sends to the opposite end; After the message of local terminal transmission is received in the opposite end,, then replace the old UE S1APID that preserve the opposite end with the newly assigned UE S1AP of the local terminal that carries in message ID if judge the UE S1AP ID that has carried the local terminal distribution in the message.
Further, when the UE S1AP ID of local terminal distribution does not change, in the message that sends to the opposite end, do not carrying the UE S1AP ID that local terminal distributes.
Further, described local terminal is MME, and described opposite end is eNodeB, said method comprising the steps of:
(a) MME sends the S1AP request message to eNodeB, and MME carries the local eNodeB UE S1AP ID that keeps in this message, if MME redistributed MME UE S1APID before this, then also carry MME UE S1AP ID in message, otherwise do not carry;
(b) after eNodeB receives the S1AP request message, search corresponding S1AP link information according to the eNodeB UES1AP ID in the S1AP request message, judge and whether also carry MME UE S1APID in the message, if do not carry, then do not revise the local MME UE S1AP ID that preserves, if carried, then directly replace the local MME UE S1AP ID that preserves;
(c) eNodeB returns response message to MME, and eNodeB carries the MME UE S1AP ID that local terminal keeps in this response message.
Further, in described step (c),, then in response message, carry new distribution eNodeB UE S1APID, otherwise do not carry if eNodeB redistributed eNodeB UE S1AP ID before sending response message; After MME receives response message, search corresponding S1AP link information according to the MME UE S1AP ID in the message, judge and whether carry eNodeB UE S1AP ID in the response message, if do not carry, then do not revise the local eNodeB UE S1AP ID that preserves, if carried, then directly replace the local eNodeB UE S1AP ID that preserves.
Further, the described S1AP request message that MME sends to eNodeB, with eNodeB to the described response message that MME returns, be any a group in the following message groups: carrying is set up request and is set up response with carrying; Bearing modification request and bearing modification response; Initial context is set up request and is set up response with initial context; Initial context is revised request and is revised response with initial context; Handoff request and Handover Request Acknowledge.
Further, described local terminal is eNodeB, and described opposite end is MME, said method comprising the steps of:
(x) eNodeB sends the S1AP request message to MME, and eNodeB carries the local MME UE S1AP ID that keeps in this message, if eNodeB redistributed eNodeB UES1AP ID before this, then carry eNodeB UE S1AP ID, otherwise do not carry;
(y) after MME receives the S1AP request message, search corresponding S1AP link information according to the MME UE S1AP ID in the message, judge and whether carry eNodeB UE S1AP ID in the message, if do not carry, then do not revise the local eNodeB UE S1AP ID that preserves, if carried, then directly replace the local eNodeB UE S1AP ID that preserves;
(z) MME returns response message to eNodeB, and MME carries the eNodeB UE S1AP ID that local terminal keeps in this response message.
Further, in described step (z),, then in response message, carry newly assigned MME UE S1AP ID, otherwise do not carry if MME redistributed MME UE S1AP ID before sending response message; After eNodeB receives response message, search corresponding S1AP link information according to the eNodeB UE S1AP ID in the message, judge and whether carry MME UE S1AP ID in the message, if do not carry, then do not revise the local MME UE S1AP ID that preserves, if carried, then directly replace the local MME UE S1AP ID that preserves.
Further, the described S1AP request message that eNodeB sends to MME, with MME to the response message that eNodeB returns, be any a group in the following message groups: switching demand and switching command; Path conversion request and path transition response; Handover cancelling request and handover cancelling are confirmed.
Adopt all methods of the present invention, the mistake coverage condition of both having avoided this field exception error to cause largely, treatment mechanism when providing the opposite end is distributed in the message UE S1AP ID again with local terminal preservation information inconsistency, the problem under some abnormal conditions when solving UE S1AP ID preferably and using on stream.
Description of drawings
Fig. 1 is a SAE Organization Chart in the prior art;
The distribution of Fig. 2 initial UE S1AP ID and preservation flow chart;
Fig. 3 is MME start flow figure;
Fig. 4 is eNodeB start flow figure.
Embodiment
Main design of the present invention is:
ENodeB and MME if the UES1AP ID that local terminal distributes does not change, just no longer fill in this field in the S1AP message that follow-up this UE is correlated with after certain user's S1AP link is set up successfully, can avoid this field generation exception error like this; If the UE S1AP ID that local terminal distributes changes, then in message, fill in new UE S1AP ID.ENodeB or MME judge whether the UE S1AP ID that the other side distributes carries after the message of receiving the opposite end network element, if do not carry, then do not revise the local relevant UE S1AP ID that preserves; If carried, then directly replace the UE S1AP ID that local opposite end of preserving is distributed.
Situation about not changing for UE S1AP ID, just no longer fill in this field in the S1AP message that follow-up this UE is correlated with, therefore reduced field and do not changed, but because the exception error of rewriting takes place in this field that abnormal causes such as for example encoding and decoding mistake, internal memory rewriting cause.
The present invention is described in detail below in conjunction with drawings and the specific embodiments.
As shown in Figure 2, the distribution of initial UE S1AP ID and preservation process are as follows:
Step 200, when eNodeB received the initial UE message of UE, the eNodeB local terminal distributed an eNodeB UE S1AP ID, and this forwards is given MME then, and carries the eNodeB UE S1AP ID that local terminal distributes in this message;
Step 201, MME keeps eNodeB UE S1AP ID, and distributes a MME UES1AP ID at local terminal;
Step 202, MME returns response message (this message be to receive initial UE message after, MME returns to article one message of eNodeB) to eNodeB, carries MME UE S1AP ID and eNodeB UE S1AP ID in this message;
Step 203, eNodeB searches corresponding S1AP link information according to the eNodeB UE S1AP ID in the message earlier, after finding, MME UE S1AP ID is saved in this S1AP link information.
By above-mentioned flow process, MME and eNodeB have distributed the UE S1AP ID of local terminal, and have also kept the UE S1AP ID of opposite end, and a S1AP link between MME and eNodeB is set up successfully.
As shown in Figure 3, be the embodiment of MME start flow.
Step 300, MME sends the S1AP request message to eNodeB, and MME carries the local eNodeB UE S1AP ID that keeps in this message, if MME redistributed MME UES1AP ID before this, then carry MME UE S1AP ID, otherwise do not carry;
The S1AP request message that MME sends to eNodeB can be carrying foundation request, bearing modification request, initial context is set up asks, initial context is revised all request messages that sent by MME such as request, handoff request on S1AP.
The situation that MME redistributes MME UE S1AP ID comprises: distribute new MME UE S1AP ID, the reason in the MME realization to cause distributing new MME UE S1AP ID or under certain abnormal conditions, redistributed MME UE S1AP ID between two parties in the flow process, for example:
In the interoffice flow process, the user is linked into new MME from old MME, and then new MME need distribute new MME UE S1AP ID for this user;
When realizing, change has taken place when MME finds the eNodeB that the user inserts, perhaps situations such as change have taken place in user's tracking area, and then MME can freely determine whether to redistribute a MME UE S1AP ID for this user;
Under abnormal conditions, occurred conflicting with other user as the MME UE S1AP ID that distributed for this user originally among the MME, or user profile is lost etc. among the MME.
On MME, it can write down the behavior that heavily distributes MME UE S1AP ID by a mark, and keeps new and old two MME UE S1AP ID simultaneously, treat that the opposite end is revised successfully after, revise local data again.
Step 301, after eNodeB receives the S1AP request message, search corresponding S1AP link information according to the eNodeB UES1AP ID in the message earlier, after finding, judge whether carry MME UES1AP ID in the message,, then do not revise the local MME UE S1AP ID that preserves if do not carry, if carried, then directly replace the local MME UE S1AP ID that preserves;
Step 302, eNodeB returns response message to MME, eNodeB carries the MME UE S1AP ID that local terminal keeps in this message, if eNodeB redistributed eNodeB UES1AP ID (may be reason or certain abnormal conditions in interoffice flow process, the eNodeB realization) before this, then carry eNodeB UE S1AP ID, otherwise do not carry;
Corresponding to the S1AP request message that MME sends to eNodeB, the response message that eNodeB returns to MME can be all corresponding response message such as carrying foundation response, bearing modification respond, initial context is set up response, initial context modification response, Handover Request Acknowledge.
Step 303, after MME receives response message, search corresponding S1AP link information according to the MME UE S1AP ID in the message earlier, after finding, judge whether carry eNodeB UE S1APID in the message,, then do not revise the local eNodeB UE S1AP ID that preserves if do not carry, if carried, then directly replace the local eNodeB UE S1AP ID that preserves.
As shown in Figure 4, be the embodiment of eNodeB start flow.
Step 400, eNodeB sends the S1AP request message to MME, eNodeB carries the MME UE S1AP ID that local terminal keeps in this message, if eNodeB redistributed eNodeBUE S1AP ID (may be reason or certain abnormal conditions in interoffice flow process, the eNodeB realization) before this, then carry eNodeB UE S1AP ID, otherwise do not carry;
The S1AP request message that eNodeB sends to MME can be all request messages that sent by eNodeB on S1AP such as switching demand, path conversion request, handover cancelling request.
Step 401, after MME receives the S1AP request message, search corresponding S1AP link information according to the MME UE S1APID in the message earlier, after finding, judge whether carry eNodeB UES1AP ID in the message,, then do not revise the local eNodeB UE S1AP ID that preserves if do not carry, if carried, then directly replace the local eNodeB UE S1AP ID that preserves;
Step 402, MME returns response message to eNodeB, MME carries the eNodeB UE S1AP ID that local terminal keeps in this message, if MME redistributed MME UE S1APID (may be reason or certain abnormal conditions in interoffice flow process, the MME realization) before this, then carry MMEUE S1AP ID, otherwise do not carry;
Corresponding to the S1AP request message that eNodeB sends to MME, the response message that MME returns to eNodeB can be all corresponding response message such as switching command, path transition response, handover cancelling affirmation.
Step 403, after eNodeB receives response message, search corresponding S1AP link information according to the eNodeB UE S1AP ID in the message earlier, after finding, judge whether carry MME UE S1AP ID in the message,, then do not revise the local MME UE S1AP ID that preserves if do not carry, if carried, then directly replace the local MME UE S1AP ID that preserves.
Certainly; the present invention also can have other various embodiments; under the situation that does not deviate from spirit of the present invention and essence thereof; those of ordinary skill in the art work as can make various corresponding changes and distortion according to the present invention, but these corresponding changes and distortion all should belong to the protection range of the appended claim of the present invention.
Claims (7)
1. the transmission method of a S1 interface application protocol identification, described S1 interface is connecting the Node B eNodeB and the mobile management entity MME of evolution, it is characterized in that,
When the sign UE S1AP ID of certain subscriber equipment on the unique identification S1 interface that local terminal distributes changes, in the message that sends to the opposite end, carry newly assigned UE S1AP ID;
After the message of local terminal transmission is received in the opposite end,, then replace the old UE S1AP ID that preserve the opposite end with the newly assigned UE S1AP of the local terminal that carries in message ID if judge the UE S1AP ID that has carried the local terminal distribution in the message;
When the UE S1AP ID of local terminal distribution does not change, in the message that sends to the opposite end, do not carrying the UE S1AP ID that local terminal distributes.
2. the method for claim 1 is characterized in that, described local terminal is MME, and described opposite end is eNodeB, said method comprising the steps of:
(a) MME sends the S1AP request message to eNodeB, and MME carries the local eNodeB UE S1AP ID that keeps in this message, if MME redistributed MME UE S1AP ID before this, then also carry MME UE S1AP ID in message, otherwise do not carry;
(b) after eNodeB receives the S1AP request message, search corresponding S1AP link information according to the eNodeB UE S1AP ID in the S1AP request message, judge and whether also carry MME UE S1AP ID in the message, if do not carry, then do not revise the local MME UE S1AP ID that preserves, if carried, then directly replace the local MME UE S1AP ID that preserves;
(c) eNodeB returns response message to MME, and eNodeB carries the MME UE S1AP ID that local terminal keeps in this response message.
3. method as claimed in claim 2 is characterized in that,
In described step (c),, then in response message, carry new distribution eNodeB UE S1AP ID, otherwise do not carry if eNodeB redistributed eNodeB UE S1AP ID before sending response message;
After MME receives response message, search corresponding S1AP link information according to the MME UE S1AP ID in the message, judge and whether carry eNodeB UE S1AP ID in the response message, if do not carry, then do not revise the local eNodeB UE S1AP ID that preserves, if carried, then directly replace the local eNodeB UE S1AP ID that preserves.
4. as claim 2 or 3 described methods, it is characterized in that,
The described S1AP request message that MME sends to eNodeB, with eNodeB to the described response message that MME returns, be any a group in the following message groups:
Carrying is set up request and is set up response with carrying; Bearing modification request and bearing modification response; Initial context is set up request and is set up response with initial context; Initial context is revised request and is revised response with initial context; Handoff request and Handover Request Acknowledge.
5. the method for claim 1 is characterized in that, described local terminal is eNodeB, and described opposite end is MME, said method comprising the steps of:
(x) eNodeB sends the S1AP request message to MME, and eNodeB carries the local MME UE S1AP ID that keeps in this message, if eNodeB redistributed eNodeB UE S1AP ID before this, then carry eNodeB UE S1AP ID, otherwise do not carry;
(y) after MME receives the S1AP request message, search corresponding S1AP link information according to the MME UE S1AP ID in the message, judge and whether carry eNodeB UE S1AP ID in the message, if do not carry, then do not revise the local eNodeB UE S1AP ID that preserves, if carried, then directly replace the local eNodeB UE S1AP ID that preserves;
(z) MME returns response message to eNodeB, and MME carries the eNodeB UE S1AP ID that local terminal keeps in this response message.
6. method as claimed in claim 5 is characterized in that,
In described step (z),, then in response message, carry newly assigned MME UE S1AP ID, otherwise do not carry if MME redistributed MME UE S1AP ID before sending response message;
After eNodeB receives response message, search corresponding S1AP link information according to the eNodeB UE S1AP ID in the message, judge and whether carry MME UE S1AP ID in the message, if do not carry, then do not revise the local MME UE S1AP ID that preserves, if carried, then directly replace the local MME UE S1AP ID that preserves.
7. as claim 5 or 6 described methods, it is characterized in that,
The described S1AP request message that eNodeB sends to MME, with MME to the response message that eNodeB returns, be any a group in the following message groups:
Switching demand and switching command; Path conversion request and path transition response; Handover cancelling request and handover cancelling are confirmed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101113266A CN101287169B (en) | 2008-05-27 | 2008-05-27 | Transmission method of S1 interface application protocol identification |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008101113266A CN101287169B (en) | 2008-05-27 | 2008-05-27 | Transmission method of S1 interface application protocol identification |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101287169A CN101287169A (en) | 2008-10-15 |
| CN101287169B true CN101287169B (en) | 2011-09-21 |
Family
ID=40059094
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008101113266A Expired - Fee Related CN101287169B (en) | 2008-05-27 | 2008-05-27 | Transmission method of S1 interface application protocol identification |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101287169B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101657028B (en) * | 2009-09-10 | 2011-09-28 | 新邮通信设备有限公司 | Method, device and system for establishing S1 interface connection |
| CN102056203B (en) * | 2009-10-29 | 2013-06-12 | 华为技术有限公司 | Method, device and system for analyzing user interface |
| CN102573066B (en) * | 2012-02-02 | 2016-08-03 | 电信科学技术研究院 | A kind of transmit RN information, the method and device of paging UE |
| EP3585110B1 (en) * | 2017-03-20 | 2022-04-20 | Huawei Technologies Co., Ltd. | Communication method and device thereof |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1715715A1 (en) * | 2005-04-19 | 2006-10-25 | Vodafone Group PLC | Load balancing in a communication network |
| CN101047992A (en) * | 2006-06-21 | 2007-10-03 | 华为技术有限公司 | Switchover control method |
| CN201057653Y (en) * | 2006-04-19 | 2008-05-07 | 美商内数位科技公司 | Equipment for supporting routing area update |
-
2008
- 2008-05-27 CN CN2008101113266A patent/CN101287169B/en not_active Expired - Fee Related
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1715715A1 (en) * | 2005-04-19 | 2006-10-25 | Vodafone Group PLC | Load balancing in a communication network |
| CN201057653Y (en) * | 2006-04-19 | 2008-05-07 | 美商内数位科技公司 | Equipment for supporting routing area update |
| CN101047992A (en) * | 2006-06-21 | 2007-10-03 | 华为技术有限公司 | Switchover control method |
Non-Patent Citations (4)
| Title |
|---|
| 3GPP.3rd Generation Partnership Project * |
| Evolved Universal Terrestrial Access Network (E-UTRAN) * |
| S1 Application Protocol (S1AP)(Release 8).《3GPP TS 36.413 V8.1.0》.2008,10,27-28,55-56,149. * |
| Technical Specification Group Radio Access Network * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101287169A (en) | 2008-10-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2512176B1 (en) | Congestion control method and operations maintenance center | |
| CN101883352B (en) | Method for supporting PDNGW selection | |
| CN101136835B (en) | Bearing establishment method under idle mode | |
| RU2407237C2 (en) | Method for decentralisation of events count in abnormal withdrawal of call based on each cellular cell in digital cellular communication networks | |
| CN101052209B (en) | User's face entity reselecting method for user's equipment mobility managing entity | |
| CN103052053B (en) | Priority service processing method, device and system | |
| CN102598786B (en) | Switching method between base stations, base stations and communication system | |
| CN103125142B (en) | For the group of mobile entity implements common service quality | |
| US8867471B2 (en) | Method, device, and system for reporting radio access network element information | |
| US7773571B1 (en) | Transfer of policy and charging rules during MIP handover | |
| US20130122921A1 (en) | Dynamic optimization of radio network resources based on user equipment type | |
| US7308271B2 (en) | Mobile communication control method and radio network controller | |
| CN101272318B (en) | Method for preventing false resource release in tracing section updating or switching course | |
| CN101248629A (en) | Reserved bearing | |
| CN102577449B (en) | Method, device and system for activation and deactivation of priority service | |
| CN101730073B (en) | Method and system for acquiring user contracting data | |
| CN107251611A (en) | A kind of method for processing business, relevant apparatus and system | |
| CN101730193B (en) | Method and system for selecting gateway node | |
| CN101730062A (en) | Method for processing exception between nonadjacent nodes | |
| CN101577970B (en) | Method for releasing wireless resources | |
| CN101287169B (en) | Transmission method of S1 interface application protocol identification | |
| CN101296496B (en) | Method for preventing false resource release in tracing section updating or switching course | |
| CN102014434B (en) | Load re-distribution method and system for service gateway | |
| CN101795442A (en) | Load establishing method in mobile communication system | |
| CN101583192B (en) | Method for processing bearer reconstruction failure |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20110921 Termination date: 20190527 |