CN101795442A - Load establishing method in mobile communication system - Google Patents
Load establishing method in mobile communication system Download PDFInfo
- Publication number
- CN101795442A CN101795442A CN200910009896A CN200910009896A CN101795442A CN 101795442 A CN101795442 A CN 101795442A CN 200910009896 A CN200910009896 A CN 200910009896A CN 200910009896 A CN200910009896 A CN 200910009896A CN 101795442 A CN101795442 A CN 101795442A
- Authority
- CN
- China
- Prior art keywords
- enb
- mme
- default bearer
- message
- carrying
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention relates to a load establishing method in a mobile communication system, which comprises the following steps that: MME sends default load configuration parameters and default load instructions to be established to eNB; if eNB can successfully establish the default load, eNB notifies MME that the load establishment succeeds, and the default load with UE is established; and if eNB cannot successfully establish the default load, the eNB notifies MME that the default load establishment fails. The method can let eNB know the default load; when the default load establishment fails, eNB instructs the corresponding information to MME, thereby ending the process as soon as possible, preventing the problems of the UE end, reducing the unnecessary information interaction of the UE and a network end, and solving the problems.
Description
Technical field
The present invention relates to the communications field, particularly, relate to the method that carrying is set up in a kind of mobile communication system.
Background technology
The system configuration of SAE as shown in Figure 1.Be description below to Fig. 1 SAE system configuration.
101 subscriber equipmenies (hereinafter to be referred as UE) are the terminal equipments that is used for receiving data.102 EUTRAN are the Radio Access Networks among the evolution system SAE, also can be eNB, be responsible for providing the interface of access of radio network, and be connected by the S1 interface with user plane entity 104 Serving Gateway with the mobile management entity 103MME of mobile phone to LTE (Long Term Evolution) mobile phone.103MME is in charge of mobile context, the session context of subscriber equipment, preserves user and security-related information.104 ServingGateway (Serving GW) mainly provide the function of user plane.S1-MME interface is responsible for providing RAB to set up to UE, and UE is sent to the forwarding of the message of MME from wireless access network.Some is similar for function that 103MME and 104 Serving Gateway combine and original 106SGSN (GPRS (hereinafter to be referred as GPRS) support node), and MME and ServingGateway might be in same physical entity.105PDN Gateway is responsible for functions such as charging, Lawful Interception.Serving Gateway and PDN Gateway might be in same physical entity.106SGSN is that the transmission for data provides route among the present UMTS.Existing SGSN finds corresponding Gateway GPRS Support Node (hereinafter to be referred as GGSN) according to access point name (hereinafter to be referred as APN).107HSS is the local ownership subsystem of subscriber equipment, it is responsible for preserving user's information, comprises the current location of subscriber equipment, the address of service node, user's security-related information, packet data protocol (hereinafter to be referred as PDP) context that subscriber equipment activates or the like.108PCRF provides Qos policy and charging criterion by the S7 interface.
Usually, customer traffic is to 104 Serving Gateway through 105PDN Gateway, Serving Gateway sends to the eNB at UE place to data by GPRS Tunnel Protocol (hereinafter to be referred as GTP) passage, and eNB sends to corresponding user equipment to data.
Fig. 2 is that UE connects (Attach) basic procedure to network.Here the UE that only drawn, the signaling process between eNB and the MME does not come out the process prescription between MME and S-GW and the PDN GW.Process between MME and S-GW and the PDN GW sees 3GPP TS23.401 for details.And the optional process between UE and eNB and the MME for example identification request has also been ignored detailed explanation here.Be detailed description below to Fig. 2.
201 UE initiate the Attach process.UE sends NAS message connection request to eNB by RRC message.RRC message comprises the network of UE selection and old GUMMEI.
202 eNB obtain MME according to the PLMN that old GUMMEI and UE select, if the MME that obtains is not connected with this eNB or old GUMMEI is unavailable, eNB is according to MME selection function selection MME among the 4.3.8.3 among the 3GPP TS23.401.ENB transmits by the initial UE message of S1 interface and connects (Attach) request message to selected MME.
" initial context is set up request information and is given eNB in 203 MME transmission.Described message comprises the safe context information of UE Access Layer, switches the restriction tabulation.Set up at initial context and also to comprise the beared information (can comprise default bearer and dedicated bearer simultaneously) that to set up in the request message, bearer setup message such as bearing identification, Qos information, transport layer address, channel end number (TEID) and NAS PDU that S-GW distributes.Wherein NAS PDU connects to accept or dedicated bearer context activation request message.Accept to comprise in the message default bearer context activation message.
If eNB can not set up S1 UE context or can not set up the carrying of a non-assurance bit rate (non-GBR), eNB thinks that this procedure failure, eNB send the initial context failed message to MME.
The Data Radio Bearer that corresponding success is set up, eNB passes to Radio interface protocols to bearing identification (E-RAB ID) and NAS PDU.Corresponding Data Radio Bearer in eNB foundation failure, eNB does not issue UE to the NAS PDU of correspondence.
204 eNB send RRC and connect reconfiguration message to UE.Comprise radio bearer sign and corresponding NAS PDU in the described message.More detailed information please refer to 3GPP TS36.331.
205 UE transmission RRC connection is reshuffled and is finished message to eNB.More detailed information please refer to 3GPP TS36.331.
206 eNB send the initial context response message to MME.Described message comprises enhancing RAB (E-RAB) tabulation of foundation and the E-RAB tabulation of failure.Comprise the TEID of eNB distribution and the transmission that the transport layer address is used for S1 interface user plane downlink data for the E-RAB item information element of setting up.
207 UE send direct Transfer Message to eNB, and described message comprises the connection of NAS message and finishes.
208 eNB send to connect by up NAS transmission and finish message to MME.
In the SAE system, for speed call settling time,, guarantee to have set up a default bearer (default bearer is the non-GBR carrying) in case UE connects (attach) to network, be used to transmit high-rise signaling, otherwise UE just needs attach again.And default bearer is transparent to eNB.
In above-mentioned Attach process, when eNB received that initial context is set up request message, eNB did not know which is a default bearer.When setting up two non-GBR carryings simultaneously, if default bearer has been failed, another one non-GBR has carried successfully.ENB will continue to send the RRC reconfiguration request message to UE, and the non-GBR that comprises successfully configuration in the RRC reconfiguration request message carries pairing NAS PDU, and Attach accepts and the information of default bearer context activation but do not comprise in this message.UE receives described RRC reconfiguration request message, the carrying of meeting configuring request.Like this, at the UE end, dedicated bearer may successfully dispose, but UE does not receive that Attach accepts message, does not also have a kind of like this state at present in the state machine of UE.And how recovering this state also is present standard open question to normal state.
The PDN that initiates at UE connects to set up and also has similar problem in the process, sets up as default bearer and has failed, and the foundation of dedicated bearer is also continuing, and dedicated bearer also needs deletion after setting up and finishing.Cause resource waste.
Summary of the invention
The purpose of this invention is to provide the method that carrying is set up in a kind of mobile communication system.
For achieving the above object, set up the method for carrying in a kind of mobile communication system, comprise step:
MME sends default bearer configuration parameter and the default bearer indication that will set up to eNB;
If eNB can successfully set up described default bearer, eNB notice MME carrying is set up successfully, and the default bearer between foundation and the UE;
If eNB can not successfully set up described default bearer, the described default bearer of eNB notice MME is set up failure.
The invention enables eNB can know default bearer, when default bearer was set up failure, eNB indicated corresponding information to give MME, finishes this process as early as possible, had avoided the problem of UE end, had reduced the unnecessary information interaction of UE and network terminal.Solved the problem of above-mentioned existence.
Description of drawings
Fig. 1 is the SAE system network architecture;
Fig. 2 is that UE connects (Attach) process to network;
Fig. 3 is a carrying establishing method flow chart of the present invention;
Fig. 4 is that the carrying in the Attach process is set up;
Fig. 5 is that the carrying in the UE request PDN connection procedure is set up.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, the present invention is described in further detail below in conjunction with the accompanying drawings and the specific embodiments.
As shown in Figure 3, the carrying establishing method in mobile communication system of the present invention's proposition can may further comprise the steps:
Step 301:MME sends carrying and sets up request message to eNB, and when comprising the default bearer that will set up in the described message, MME indicates default bearer to eNB.
Step 302:eNB sends successful carrying and sets up response message to MME when default bearer can successfully be set up, otherwise the response message of transmission failure is to MME.
According to a kind of implementation of the present invention, it can be that initial context is set up request message that request message is set up in described carrying.MME indication default bearer comprises following several for the method for eNB:
One, set up in the request message (setting up request) in carrying and to comprise the indication of information element default bearer as initial context.For example can be in the carrying tabulation that will set up, the RAB E-RAB of the enhancing of corresponding default bearer sets up indication (defaultbearer indicator) information element that comprises default bearer in the information element.
Two, MME is provided with the priority of ARP of default bearer for the highest.ENB is according to receiving that the priority of ARP knows which is a default bearer in the message.
Three, reserve the value of the priority of the value of an ARP or ARP for default bearer.MME is provided with the ARP of default bearer according to this reserved value, and which eNB parses according to this reserved value is default bearer.
Four, send in the carrying that will the set up tabulation of eNB at MME, first non-GBR (non-assurance bit rate) is carried as default bearer.
Five, send in the carrying that will the set up tabulation of eNB at MME, first is carried as default bearer.
ENB knows that according to above-mentioned method which carrying is a default bearer after receiving that initial context is set up request message, if eNB can not set up the S1 context of UE or can not set up default bearer, eNB sends failure of establishing initial context message to MME.The reason of failure is the default bearer failure.
ENB sets up response message by initial context and tells MME the result of all request carryings, the E-RAB tabulation that comprises the E-RAB tabulation of successfully setting up and fail and set up.
According to another kind of implementation of the present invention, it can be that E-RAB sets up request message that request message is set up in described carrying.If comprise default bearer in the carrying that the MME request is set up, MME indicates to eNB, and MME indication default bearer gives the method for eNB same as described above.
ENB knows that according to above-mentioned method which carrying is a default bearer after receiving that E-RAB sets up request message, if eNB can not set up default bearer, eNB sends E-RAB and sets up response message to MME.ENB indicates all carrying failures, and the reason of failure is the default bearer failure.
Under case of successful, eNB sets up response message by E-RAB and tells MME the result of all request carryings, the E-RAB tabulation that comprises the E-RAB tabulation of successfully setting up and fail and set up.
Fig. 4 is the embodiment that method of the present invention is used for the Attach process.Be detailed description below to this figure.Here the UE that only drawn, the signaling process between eNB and the MME does not come out the process prescription between MME and S-GW and the PDN GW.Process between MME and S-GW and the PDN GW sees 3GPPTS23.401 for details.And the optional process between UE and eNB and the MME for example identification request has also been ignored detailed explanation here.Be detailed description below to Fig. 4.
401 UE initiate connection procedure.UE sends NAS message connection request to eNB by RRC message.RRC message comprises the network of UE selection and old GUMMEI.
402 eNB obtain MME according to the PLMN that old GUMMEI and UE select, if the MME that obtains is not connected with this eNB or old GUMMEI is unavailable, eNB is according to MME selection function selection MME among the 4.3.8.3 among the 3GPP TS23.401.ENB transmits connection request message by the initial UE message of S1 interface and gives selected MME.
" initial context is set up request information and is given eNB in 403 MME transmission.Described message comprises the safe context information of UE Access Layer, switches the restriction tabulation.Set up at initial context and also to comprise the beared information (can comprise default bearer and dedicated bearer simultaneously) that to set up in the request message, bearer setup message such as bearing identification, Qos information, transport layer address, channel end number (TEID) and NAS PDU that S-GW distributes.Wherein NAS PDU connects to accept or dedicated bearer context activation request message.Accept to comprise in the message default bearer context activation message.If comprise default bearer in the carrying of setting up, MME indicates default bearer to eNB.MME indication default bearer sees described in Fig. 2 for the method for eNB.
If 404 eNB can not set up S1 UE context or can not set up default bearer, eNB thinks that this procedure failure, eNB send the initial context failed message to MME.If the reason of failure is that eNB can not set up default bearer, eNB comprises the reason " default bearer failure " of failure in described message.This process finishes at eNB, the loading establishing process that eNB does not initiate to eat dishes without rice or wine (connect reshuffle as RRC).
The Data Radio Bearer that 405 corresponding successes are set up, eNB passes to Radio interface protocols to bearing identification (E-RAB ID) and NAS PDU.Corresponding Data Radio Bearer in eNB foundation failure, eNB does not issue UE to the NAS PDU of correspondence.ENB sends RRC and connects reconfiguration message to UE.Comprise radio bearer sign and corresponding NAS PDU in the described message.More detailed information please refer to 3GPPTS36.331.
406 UE transmission RRC connection is reshuffled and is finished message to eNB.More detailed information please refer to 3GPP TS36.331.
407 eNB send the initial context response message to MME.Described message comprises the E-RAB tabulation of foundation and the E-RAB tabulation of failure.Comprise the TEID of eNB distribution and the transmission that the transport layer address is used for S1 interface user plane downlink data for the E-RAB item information element of setting up.
408 UE send direct Transfer Message to eNB, and described message comprises the connection of NAS message and finishes.
409 eNB send to connect by up NAS transmission and finish message to MME.
Fig. 5 is that method of the present invention is used for the embodiment that UE request PDN connects (connectivity) process.Down but to the detailed description of this figure.Here the UE that only drawn, the signaling process between eNB and the MME does not come out the process prescription between MME and S-GW and the PDN GW.Process between MME and S-GW and the PDNGW sees 3GPP TS23.401 for details.
501 UE initiate the PDN connectivity process of UE request.UE sends PDN connection request message to MME.Described message comprises PDN type, protocol configuration option, information elements such as request type.
502 MME send E-RAB and set up request message to eNB.Described message comprises will set up beared information, as bearing identification, and Qos information, transport layer address, channel end number (TEID) and NAS PDU that S-GW distributes.Wherein NAS PDU is that PDN connects acceptance or request of default bearer context activation or dedicated bearer context activation request message.If comprise default bearer in the carrying of setting up, MME indicates default bearer to eNB.MME indication default bearer sees described in Fig. 2 for the method for eNB.
503 eNB are after receiving that E-RAB sets up request message, if eNB can not set up the default bearer of indication, eNB sends E-RAB and sets up response message to MME.ENB indicates all carrying failures, and the reason of failure is the default bearer failure.This process finishes at eNB, the loading establishing process that eNB does not initiate to eat dishes without rice or wine (connect reshuffle as RRC).
The Data Radio Bearer that 504 corresponding successes are set up, eNB passes to Radio interface protocols to bearing identification (E-RAB ID) and NASPDU.Corresponding Data Radio Bearer in eNB foundation failure, eNB does not issue UE to the NAS PDU of correspondence.ENB sends RRC and connects reconfiguration message to UE.Comprise radio bearer sign and corresponding NAS PDU in the described message.More detailed information please refer to 3GPP TS36.331.
505 UE transmission RRC connection is reshuffled and is finished message to eNB.More detailed information please refer to 3GPP TS36.331.
506 eNB set up response message by E-RAB and tell MME the result of all request carryings, the E-RAB tabulation that comprises the E-RAB tabulation of successfully setting up and fail and set up.For the E-RAB that success is set up, comprise the TEID of eNB distribution and the transmission that the transport layer address is used for S1 interface user plane downlink data.
507 UE send direct Transfer Message to eNB, and described message comprises NAS message PDN connection and finishes.
508 eNB send the PDN connection by up NAS transmission and finish message to MME.
In sum, more than be preferred embodiment of the present invention only, be not to be used to limit protection scope of the present invention.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (6)
1. set up the method for carrying in a mobile communication system, comprise step:
MME sends default bearer configuration parameter and the default bearer indication that will set up to eNB;
If eNB can successfully set up described default bearer, eNB notice MME carrying is set up successfully, and the default bearer between foundation and the UE;
If eNB can not successfully set up described default bearer, the described default bearer of eNB notice MME is set up failure.
2. method according to claim 1 is characterized in that, MME sets up request message by initial context and sends default bearer configuration parameter and the default bearer indication that will set up to eNB.
3. method according to claim 1 is characterized in that, MME sets up request message by the RAB E-RAB that strengthens and sends default bearer configuration parameter and the default bearer indication that will set up to eNB.
4. method according to claim 1 is characterized in that default bearer indication is carried by first non-assurance bit rate to represent.
5. method according to claim 1 is characterized in that default bearer indication is carried by first to represent.
6. method according to claim 1 is characterized in that, eNB sets up the described default bearer of failed message notice MME by carrying and sets up failure.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910009896A CN101795442A (en) | 2009-02-02 | 2009-02-02 | Load establishing method in mobile communication system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200910009896A CN101795442A (en) | 2009-02-02 | 2009-02-02 | Load establishing method in mobile communication system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101795442A true CN101795442A (en) | 2010-08-04 |
Family
ID=42587820
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200910009896A Pending CN101795442A (en) | 2009-02-02 | 2009-02-02 | Load establishing method in mobile communication system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101795442A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102724718A (en) * | 2012-06-05 | 2012-10-10 | 大唐移动通信设备有限公司 | Method and device for notifying bearer information |
| WO2015055028A1 (en) * | 2013-10-15 | 2015-04-23 | 华为技术有限公司 | Message processing method and mme selection method and device |
| WO2015058393A1 (en) * | 2013-10-25 | 2015-04-30 | 华为技术有限公司 | Communication method, device and system |
| US20170171904A1 (en) * | 2015-09-15 | 2017-06-15 | Huawei Technologies Co., Ltd. | Service processing method and service processing apparatus |
| WO2018202129A1 (en) * | 2017-05-05 | 2018-11-08 | 华为技术有限公司 | Communication method, base station, and terminal device |
| WO2020063891A1 (en) * | 2018-09-28 | 2020-04-02 | 中兴通讯股份有限公司 | Data transmission method and apparatus, data sending method and apparatus, and data transmission system |
| CN114364060A (en) * | 2021-12-16 | 2022-04-15 | 上海瀚讯信息技术股份有限公司 | Method for improving air interface data bearing configuration efficiency |
-
2009
- 2009-02-02 CN CN200910009896A patent/CN101795442A/en active Pending
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102724718A (en) * | 2012-06-05 | 2012-10-10 | 大唐移动通信设备有限公司 | Method and device for notifying bearer information |
| WO2015055028A1 (en) * | 2013-10-15 | 2015-04-23 | 华为技术有限公司 | Message processing method and mme selection method and device |
| US10104700B2 (en) | 2013-10-15 | 2018-10-16 | Huawei Technologies Co., Ltd. | Message processing method, MME selection method, and apparatuses |
| WO2015058393A1 (en) * | 2013-10-25 | 2015-04-30 | 华为技术有限公司 | Communication method, device and system |
| CN104838718A (en) * | 2013-10-25 | 2015-08-12 | 华为技术有限公司 | Communication method, device and system |
| EP3046389A4 (en) * | 2013-10-25 | 2016-10-26 | Huawei Tech Co Ltd | Communication method, device and system |
| US10212634B2 (en) | 2013-10-25 | 2019-02-19 | Huawei Technologies Co., Ltd. | Communication method, device, and system |
| US20170171904A1 (en) * | 2015-09-15 | 2017-06-15 | Huawei Technologies Co., Ltd. | Service processing method and service processing apparatus |
| US11497076B2 (en) | 2015-09-15 | 2022-11-08 | Huawei Technologies Co., Ltd. | Service processing method and service processing apparatus |
| US10694571B2 (en) * | 2015-09-15 | 2020-06-23 | Huawei Technologies Co., Ltd. | Service processing method and service processing apparatus |
| CN110603845A (en) * | 2017-05-05 | 2019-12-20 | 华为技术有限公司 | Communication method, base station and terminal equipment |
| KR20200003096A (en) * | 2017-05-05 | 2020-01-08 | 후아웨이 테크놀러지 컴퍼니 리미티드 | Communication method, base station and terminal device |
| CN110856223A (en) * | 2017-05-05 | 2020-02-28 | 华为技术有限公司 | Communication method, centralized unit, distributed unit, base station and terminal equipment |
| CN108811153A (en) * | 2017-05-05 | 2018-11-13 | 华为技术有限公司 | Communication means, centralized unit, distributed unit, base station and terminal device |
| CN110856223B (en) * | 2017-05-05 | 2020-10-27 | 华为技术有限公司 | Communication method, centralized unit, distributed unit, base station and terminal equipment |
| US10869324B2 (en) | 2017-05-05 | 2020-12-15 | Huawei Technologies Co., Ltd. | Communication method based on a CU-DU architecture |
| KR102271766B1 (en) * | 2017-05-05 | 2021-06-30 | 후아웨이 테크놀러지 컴퍼니 리미티드 | Communication method, base station and terminal device |
| WO2018202129A1 (en) * | 2017-05-05 | 2018-11-08 | 华为技术有限公司 | Communication method, base station, and terminal device |
| CN110603845B (en) * | 2017-05-05 | 2024-03-15 | 华为技术有限公司 | Communication method, base station and terminal equipment |
| WO2020063891A1 (en) * | 2018-09-28 | 2020-04-02 | 中兴通讯股份有限公司 | Data transmission method and apparatus, data sending method and apparatus, and data transmission system |
| US11743758B2 (en) | 2018-09-28 | 2023-08-29 | Zte Corporation | Data transmission method and apparatus, data sending method and apparatus, and data transmission system |
| CN114364060A (en) * | 2021-12-16 | 2022-04-15 | 上海瀚讯信息技术股份有限公司 | Method for improving air interface data bearing configuration efficiency |
| CN114364060B (en) * | 2021-12-16 | 2024-02-09 | 上海瀚讯信息技术股份有限公司 | Method for improving air interface data bearing configuration efficiency |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101400153B (en) | Method for direct communication by user equipment through HNB access system | |
| CN111757557B (en) | Method for supporting access to closed network, UE, base station and readable storage medium | |
| CN105338655B (en) | Method and device for establishing user plane bearer | |
| CN106961456B (en) | IOT service determining method and device and IOT service behavior control method and device | |
| US11129054B2 (en) | Methods, systems and devices for supporting local breakout in small cell architecture | |
| CN101500213B (en) | Method, equipment and system for user equipment urgent access | |
| US20120069737A1 (en) | Overload avoidance with home node b gateway (henb gw) in lte | |
| EP2947951A1 (en) | Double-connection implementation method and base station | |
| CN101115292B (en) | Method for paging and connecting terminal and terminal and system for fast activating data transmission | |
| US8867471B2 (en) | Method, device, and system for reporting radio access network element information | |
| US11937319B2 (en) | Integrity protection handling at the gNB-CU-UP | |
| CN110178433B (en) | Communication method, related equipment and system | |
| US9363835B2 (en) | Methods and nodes for improved network signaling | |
| CN102869122B (en) | The method for avoiding handover failure | |
| CN101686520A (en) | Method supporting home base station context management | |
| CN101860910B (en) | Bearer establishing method, system and device of local network | |
| CN101795442A (en) | Load establishing method in mobile communication system | |
| CN101547521A (en) | Method for releasing UE resources | |
| KR20190017026A (en) | Multiple connection communication method and device | |
| CN102131251A (en) | Method for data forwarding | |
| CN104066133A (en) | Method for supporting switching | |
| CN107251611A (en) | A kind of method for processing business, relevant apparatus and system | |
| CN104244450A (en) | Rebuilding method used for concurrence of long term evolution service and cluster service, base station and user equipment | |
| CN101299882A (en) | Method for recognizing and indicating load bearing types | |
| CN102088795A (en) | SIPTO (Selected IP Traffic Offload) realization method and mobility management control node device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20100804 |