WO2011046219A1 - 移動通信方法、移動管理用ノード及びパケット交換機 - Google Patents
移動通信方法、移動管理用ノード及びパケット交換機 Download PDFInfo
- Publication number
- WO2011046219A1 WO2011046219A1 PCT/JP2010/068207 JP2010068207W WO2011046219A1 WO 2011046219 A1 WO2011046219 A1 WO 2011046219A1 JP 2010068207 W JP2010068207 W JP 2010068207W WO 2011046219 A1 WO2011046219 A1 WO 2011046219A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- bearer
- mobile station
- gateway device
- releasing
- procedure
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 115
- 238000010295 mobile communication Methods 0.000 title claims abstract description 72
- 230000004044 response Effects 0.000 claims abstract description 26
- 230000008569 process Effects 0.000 claims description 35
- 230000015556 catabolic process Effects 0.000 abstract 1
- 230000004048 modification Effects 0.000 description 25
- 238000012986 modification Methods 0.000 description 25
- 238000010586 diagram Methods 0.000 description 9
- 239000000872 buffer Substances 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/04—Arrangements for maintaining operational condition
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
- H04W28/0257—Traffic management, e.g. flow control or congestion control per individual bearer or channel the individual bearer or channel having a maximum bit rate or a bit rate guarantee
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/18—Management of setup rejection or failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
- H04W76/38—Connection release triggered by timers
Definitions
- the present invention relates to a mobile communication method, a mobility management node, and a packet switch.
- a GBR bearer is set between the gateway device S-GW and the gateway device P-GW (PDN Gateway).
- step S1001 a failure occurs in the radio base station eNodeB, and a restart process is performed.
- step S1002 the radio base station eNodeB receives the packet addressed to the mobile station UE transferred via the gateway device P-GW and the gateway device S-GW.
- step S1003 the radio base station eNodeB , “Error Indication” is transmitted.
- step S1004 the gateway device S-GW releases GBR bearer resources for the radio base station eNodeB, and in step S1005, buffers the packet addressed to the mobile station UE received from the gateway device P-GW.
- step S1006 the gateway device S-GW transmits “Downlink Data Notification” for notifying a packet addressed to the mobile station UE being buffered to the mobility management node MME (Mobility Management Entity).
- MME Mobility Management Entity
- step S1007 the mobility management node MME transmits “Paging” addressed to the mobile station UE to the radio base station eNodeB and starts a paging timer.
- step S1008 even if the mobile management node MME does not respond to “Paging” from the mobile station UE before the paging timer expires, the mobility management node MME determines whether the gateway device S-GW and the gateway device P-GW Hold the GBR bearer in between without releasing it.
- step S2000 by performing the GBR bearer setting process in step S2000, between the mobile station UE and the radio base station eNodeB, between the radio base station eNodeB and the gateway device S-GW, and the gateway device.
- a GBR bearer is set between the S-GW and the gateway device P-GW.
- step S2001 a failure occurs in the radio base station eNodeB, and a restart process is performed.
- step S2002 the radio base station eNodeB transmits a RESET signal to the mobility management node MME.
- step S2003 the mobility management node MME transmits “Release Access Bearer Request” to the gateway device S-GW.
- the gateway device S-GW releases the GBR bearer resource for the radio base station eNodeB in step S2004, and transmits “Release Access Bearer Response” to the mobility management node MME in step S2005.
- the gateway device S-GW When the gateway device S-GW receives a packet addressed to the mobile station UE from the gateway device P-GW in step S2006, the gateway device S-GW buffers the packet in step S2007.
- step S2008 the gateway device S-GW transmits “Downlink Data Notification” for notifying a packet addressed to the mobile station UE being buffered to the mobility management node MME.
- step S2009 the mobility management node MME transmits “Paging” addressed to the mobile station UE to the radio base station eNodeB and starts a paging timer.
- step S2010 the mobility management node MME, even if there is no response to “Paging” from the mobile station UE before the paging timer expires, Hold the GBR bearer in between without releasing it.
- 3GPP TS 23.401 3GPP TS24.301 3GPP TS 23.007 3GPP TS 23.060
- the GBR bearer in the core network is disconnected at an appropriate timing.
- the GBR bearer provides a service by time billing, there is a similar problem that an event in which such billing cannot be stopped occurs.
- the present invention has been made in view of the above-described problems.
- a failure occurs in a device in the radio access network while the GBR bearer is set, the GBR bearer in the core network is appropriately selected. It is an object of the present invention to provide a mobile communication method, a mobility management node, and a packet switch that can be disconnected at appropriate timing.
- a first feature of the present invention is a mobile communication method in which a first bearer for a mobile station is set between a first gateway device and a radio base station, and the first gateway device and the second gateway When the first gateway device detects a failure of the radio base station in a state in which the second bearer for the mobile station is set up with the device, the first bearer is released and used for mobility management.
- a second feature of the present invention is a mobile communication method, in which a first bearer for a mobile station is set between a first gateway device and a radio base station, and the first gateway device and the second gateway When the mobility management node detects a failure of the radio base station in a state where the second bearer for the mobile station is set up with the device, a bearer release request is sent to the first gateway device. Transmitting and starting a predetermined timer; the first gateway device releasing the first bearer in response to the bearer release request; and the mobility management node before the predetermined timer expires. And a step of starting a procedure for releasing the second bearer when a connection request is not received from the mobile station.
- a third feature of the present invention is a mobility management node, in which a first bearer for a mobile station is set between a first gateway device and a radio base station. While the second bearer for the mobile station is set up with the gateway device, the first gateway device detects a failure of the radio base station, releases the first bearer, and moves the mobile When a downlink data notification for notifying a downlink data signal addressed to the mobile station being buffered is transmitted to the management node, a paging signal is transmitted to the mobile station And, when a response from the mobile station to the paging signal is not received within a predetermined period, the procedure for releasing the second bearer is started.
- a fourth feature of the present invention is a mobility management node, wherein a first bearer for a mobile station is set between a first gateway device and a radio base station.
- a bearer release request is transmitted to the first gateway device, and a predetermined timer In the case where a connection request is not received from the mobile station before the predetermined timer expires, a procedure for releasing the second bearer is started.
- a fifth feature of the present invention is a mobile communication method, wherein a first bearer for a mobile station is set between a first gateway device and a radio network controller, and the first gateway device and the second In a state where the second bearer for the mobile station is set with the gateway device, when the first gateway device detects a failure of the radio network controller, the first bearer is released and a packet
- a step of starting a procedure for releasing the second bearer when the packet switch does not receive a response from the mobile station to the paging signal within a predetermined period is summarized in that a and.
- a sixth feature of the present invention is a mobile communication method, wherein a first bearer for a mobile station is set between a first gateway device and a radio network controller, and the first gateway device and the second If the packet switch detects a failure of the radio network controller while the second bearer for the mobile station is set up with the gateway device, it issues a bearer release request to the first gateway device. Transmitting, starting a predetermined timer, the first gateway device releasing the first bearer in response to the bearer release request, and before the packet switch expires the predetermined timer, And a step of starting a procedure for releasing the second bearer when a connection request is not received from the mobile station.
- a seventh feature of the present invention is a packet switch, in which a first bearer for a mobile station is set between a first gateway device and a radio network controller, and the first gateway device and the second gateway In a state where the second bearer for the mobile station is set up with the device, the first gateway device detects a failure of the radio network controller, releases the first bearer, and the packet It is configured to transmit a paging signal to the mobile station when a downlink data notification for notifying a downlink data signal addressed to the mobile station being buffered is transmitted to the exchange. And when the response from the mobile station to the paging signal is not received within a predetermined period, the procedure for releasing the second bearer is started.
- An eighth feature of the present invention is a packet switch, in which a first bearer for a mobile station is set between a first gateway device and a radio network controller, and the first gateway device and the second gateway When a failure of the radio network controller is detected in a state where the second bearer for the mobile station is set up with the device, a bearer release request is transmitted to the first gateway device, and a predetermined timer In the case where a connection request is not received from the mobile station before the predetermined timer expires, a procedure for releasing the second bearer is started. And
- the GBR bearer in the core network is disconnected at an appropriate timing.
- a mobile communication method, a mobile management node, and a packet switch can be provided.
- FIG. 3 is a sequence diagram illustrating an operation of the mobile communication system according to the first embodiment of the present invention.
- 3 is a flowchart for explaining the operation of the mobile communication system according to the first embodiment of the present invention.
- FIG. 3 is a sequence diagram illustrating an operation of the mobile communication system according to the first embodiment of the present invention. It is a sequence diagram explaining operation
- Mobile communication system according to the first embodiment of the present invention A mobile communication system according to a first embodiment of the present invention will be described with reference to FIGS.
- the mobile communication system is an E-UTRAN mobile communication system.
- a server device PCRF Policy and Charge Rule Function
- a gateway device P-GW a gateway device P-GW
- a gateway device S-GW a mobility management node MME
- a radio base station eNodeB a radio base station eNodeB
- a GBR bearer is set between the gateway device S-GW and the gateway device P-GW.
- the GBR bearer between the radio base station eNodeB and the gateway device S-GW is referred to as a “first GBR bearer (first bearer)”, and the GBR bearer between the gateway device S-GW and the gateway device P-GW. Is referred to as a “second GBR bearer (second bearer)”.
- step S100B of FIG. 2 a failure occurs in the radio base station eNodeB, and a restart process is performed. Thereafter, in step S100C of FIG. 2, the process A shown in FIG. 15 or the process B shown in FIG. 16 is performed.
- step S101 the gateway device S-GW transmits “Downlink Data Notification” for notifying the mobile management node MME of a packet (downlink data signal) addressed to the buffered mobile station UE.
- step S102 the mobility management node MME transmits a “Paging (paging signal)” addressed to the mobile station UE to the radio base station eNodeB and starts a paging timer.
- Paging paging signal
- the mobility management node MME performs the GBR bearer determination process shown in FIG. 3 in step S104.
- step S104A the mobility management node MME determines whether or not the second GBR bearer for the mobile station UE exists. If “YES”, the operation proceeds to step S104B, and if “NO”, the operation proceeds to step S104D.
- step S104B the mobility management node MME determines whether or not the second GBR bearer for the mobile station UE is a bearer that provides a service by time charging. If “YES”, the operation proceeds to step S104C, and if “NO”, the operation proceeds to step S104D.
- step S104C the mobility management node MME starts the procedure after step S105 for releasing the second GBR bearer for the mobile station UE.
- step S104D the mobility management node MME maintains the second GBR bearer for the mobile station UE without releasing it, and completes the process.
- the mobility management node MME may send a signal requesting resource release for the radio base station eNodeB to the gateway device S-GW.
- the QCI is information indicating the QoS level of the second GBR bearer.
- Step S105 the mobility management node MME transmits “Delete Bearer Command” to the gateway device S-GW when it is determined in Step S104C that the second GBR bearer for the mobile station UE is released.
- step S106 the second GBR bearer for the mobile station UE is released by starting the GBR bearer release procedure shown in FIG.
- step S106A when the gateway device S-GW receives the “Delete Bearer Command”, the gateway device S-GW transmits the “Delete Bearer Command” to the gateway device P-GW.
- step S106B the “PCEF Initiated IP-CAN Session Modification” procedure is performed between the gateway apparatus P-GW and the server apparatus PCRF, and when the charging process is performed at the application level, the charging process is stopped.
- the gateway device P-GW transmits “Delete Bearer Request” to the gateway device S-GW in step S106D, and stops the charging process for the GBR bearer for the mobile station UE in step S106E.
- step S106F the gateway device S-GW transmits “Delete Bearer Request” to the mobility management node MME.
- step S106G the procedure shown in steps 4 to 7 of Fig. 5.4.4.1.1 of TS23.401 defined in 3GPP is executed.
- step S106H the mobility management node MME transmits “Delete Bearer Response” to the gateway device S-GW.
- step S106I the gateway device S-GW sends “ Send “Delete Bearer Response”.
- the second GBR bearer when a failure occurs in the radio base station eNodeB in a state where the GBR bearer is set, the second GBR bearer is disconnected at an appropriate timing, The billing process for the second GBR bearer can be stopped.
- Modification 1 With reference to FIG.5 and FIG.6, the mobile communication system which concerns on the example 1 of a change of the above-mentioned 1st Embodiment is demonstrated.
- the mobile communication system according to the first modification will be described by focusing on differences from the mobile communication system according to the first embodiment described above.
- steps S150A through S150C are the same as the operations in steps S100A through S100C shown in FIG.
- Step 151 the gateway device S-GW transmits “Downlink Data Notification” including “Cause: Error Indication received RNC / eNodeB (predetermined information)” to the mobility management node MME.
- step S152 the mobility management node MME transmits a “Paging (paging signal)” addressed to the mobile station UE to the radio base station eNodeB and starts a paging timer.
- Paging paging signal
- Step S153 If there is no response to “Paging” from the mobile station UE before the paging timer expires in Step S153, the mobility management node MME performs the GBR bearer determination process shown in FIG. 6 in Step S154.
- step S154A the mobility management node MME determines whether or not the second GBR bearer for the mobile station UE exists. If “YES”, the operation proceeds to step S154B, and if “NO”, the operation proceeds to step S154E.
- step S154B the mobility management node MME determines whether or not the second GBR bearer for the mobile station UE is a bearer that provides a service by time billing. If “YES”, the operation proceeds to step S154C, and if “NO”, the operation proceeds to step S154E.
- step S154C the mobility management node MME corresponds to the reason that “Cause: Error Indication received from RNC / eNodeB” is included in the received “Downlink Data Notification” and the contents of the information element should be disconnected. It is determined whether or not to do so. If “YES”, the operation proceeds to step S154D, and if “NO”, the operation proceeds to step S154E.
- step S154D the mobility management node MME releases the second GBR bearer for the mobile station UE.
- step S154E the mobility management node MME maintains the second GBR bearer for the mobile station UE without releasing it, and completes the process.
- the mobility management node MME may send a signal requesting resource release for the radio base station eNodeB to the gateway device S-GW.
- the mobility management node MME may be configured not to perform the determination in step S154B.
- the paging timer is different from the normal value. It may be configured to set to a value.
- steps S155 and S156 are the same as the operations in steps S105 and S106 shown in FIG.
- Modification 2 With reference to FIG.7 and FIG.8, the mobile communication system which concerns on the modification 2 of the above-mentioned 1st Embodiment is demonstrated.
- the mobile communication system according to the second modification will be described by focusing on differences from the mobile communication system according to the first embodiment described above.
- steps S200A and S200B are the same as the operations of steps S100A and S100B shown in FIG.
- step S201 the radio base station eNodeB transmits a RESET signal to the mobility management node MME.
- the mobility management node MME may perform the GBR bearer determination process shown in FIG. 3 or 6 in step S201A.
- the mobility management node MME activates the GBR bearer release wait timer in step S202, and transmits “Release Access Bearer Request” to the gateway device S-GW in step S203.
- step S204 the gateway device S-GW releases the GBR bearer resource for the radio base station eNodeB, and in step S205, transmits “Release Access Bearer Response” to the mobility management node MME.
- the mobility management node MME sends “Delete” to the gateway device S-GW in step S207. Send “Bearer Command”.
- step S208 the second GBR bearer for the mobile station UE is released by starting the GBR bearer release procedure shown in FIG.
- the second GBR bearer is disconnected at an appropriate timing, and the charging process for the second GBR bearer is stopped. be able to.
- the first feature of the present embodiment is a mobile communication method, which is a first GBR bearer (first bearer) for a mobile station UE between a gateway device S-GW (first gateway device) and a radio base station eNodeB. Is set, and the gateway device in the state where the second GBR bearer (second bearer) for the mobile station UE is set between the gateway device S-GW and the gateway device P-GW (second gateway device)
- the S-GW detects a failure of the radio base station eNodeB
- the S-GW releases the first GBR bearer and notifies the mobility management node MME of a downlink data signal addressed to the mobile station UE being buffered.
- the process A for transmitting “Downlink Data Notification (downlink data notification)” and the mobility management node MME The mobile station UE transmits “Paging (paging signal)” to the mobile station UE and the mobile management node MME responds to “Paging” within a period (predetermined period) defined by the paging timer.
- the gist of the present invention is to include a step C of starting a procedure for releasing the second GBR bearer.
- the mobility management node MME further releases the second GBR bearer when it is determined that the second GBR bearer is a bearer that provides service by time charging. May start.
- the procedure for releasing may be initiated.
- the mobility management node MME further includes “Cause: Error Indication received from RNC / eNodeB (predetermined information)” in “Downlink Data Notification”.
- a procedure for releasing the second GBR bearer may be started.
- the gateway device S-GW detects a failure of the radio base station eNodeB when receiving the “Error Indication (error instruction signal)” from the radio base station eNodeB. May be.
- a second feature of the present embodiment is a mobile communication method, in which a first GBR bearer for the mobile station UE is set between the gateway device S-GW and the radio base station eNodeB, and the gateway device S-GW
- the gateway device S-GW When the mobility management node MME detects a failure of the radio base station eNodeB in a state where the second GBR bearer for the mobile station UE is set between the gateway device P-GW and the gateway device P-GW, the gateway device S-GW In response to the “Release Access Bearer Request”, the gateway device S-GW sends a “Release Access Bearer Request (bearer release request)” to start the GBR bearer release wait timer (predetermined timer), Step for releasing 1GBR bearer and node M for mobility management E is, before the GBR bearer release wait timer expires, if it does not receive a connection request from the mobile station UE, and the gist that a step of initiating a procedure for releasing the first 2
- a third feature of the present embodiment is a mobility management node MME, in which a first GBR bearer for the mobile station UE is set between the gateway device S-GW and the radio base station eNodeB, and the gateway device S -although the second GBR bearer for the mobile station UE is set between the GW and the gateway device P-GW, the gateway device S-GW detects a failure of the radio base station eNodeB and releases the first GBR bearer
- “Downlink Data Notification” is transmitted to the mobility management node MME, it is configured to transmit “Paging” to the mobile station UE, and is defined by the paging timer. If a response from the mobile station UE to “Paging” is not received within the period, the second GBR base The gist is that it is configured to start a procedure to release the ara.
- the second GBR bearer may be configured to start a procedure for releasing the second GBR bearer when it is determined that the second GBR bearer is a bearer that provides a service by time charging. .
- a procedure for releasing the second GBR bearer may be started.
- Downlink Data Notification includes “Cause: Error Indication received received RNC / eNodeB”, and the contents of the information element fall under the reason to be disconnected. If determined, the procedure for releasing the second GBR bearer may be started.
- a fourth feature of the present embodiment is a mobility management node MME, in which a first GBR bearer for the mobile station UE is set between the gateway device S-GW and the radio base station eNodeB, and the gateway device S -When a failure of the radio base station eNodeB is detected in a state where the second GBR bearer for the mobile station UE is set between the GW and the gateway device P-GW, "Release Access” is issued to the gateway device S-GW. "Bearer Request" is transmitted, and the GBR bearer release wait timer is configured to be started. If the connection request is not received from the mobile station UE before the GBR bearer release wait timer expires, the second GBR bearer is released. The gist is that the procedure is configured to start.
- Mobile communication system according to the second embodiment With reference to FIG.9 and FIG.10, the mobile communication system which concerns on the above-mentioned 2nd Embodiment is demonstrated.
- the mobile communication system according to the second embodiment of the present invention will be described by focusing on differences from the above-described mobile communication system according to the first embodiment.
- the mobile communication system is a UTRAN mobile communication system, and as shown in FIGS. 9 and 10, a server apparatus PCRF, a gateway apparatus P-GW, a gateway apparatus S-GW, and a packet An exchange SGSN and a radio network controller RNC are provided.
- a GBR bearer is set between the gateway device S-GW and the gateway device P-GW.
- the GBR bearer between the radio network controller RNC and the gateway device S-GW is referred to as a “first GBR bearer (first bearer)”
- the GBR between the gateway device S-GW and the gateway device P-GW is referred to as a “second GBR bearer (second bearer)”.
- the GBR bearer between the radio network controller RNC and the gateway device S-GW is referred to as “Direct Tunnel”.
- a GBR bearer may be set between the radio network controller RNC and the packet switch SGSN, and between the packet switch SGSN and the gateway device S-GW.
- the GBR bearer is referred to as “Non-Direct Tunnel”.
- step S300B a failure occurs in the radio network controller RNC, and the restart process is performed. Thereafter, in step S300C, process A shown in FIG. 15 or process B shown in FIG. 16 is performed.
- the radio base station eNodeB in FIGS. 15 and 16 is regarded as a radio network controller RNC, and the mobility management node MME is regarded as a gateway device S-GW.
- step S301 the gateway device S-GW transmits "Downlink Data Notification" to the packet switch SGSN.
- step S302 the packet exchange SGSN transmits “Paging (paging signal)” addressed to the mobile station UE to the radio network controller RNC and starts a paging timer.
- Paging paging signal
- the packet switch SGSN performs the GBR bearer determination process shown in FIG. 3 in step S304.
- step S305 when the packet switch SGSN determines to release the second GBR bearer for the mobile station UE, the packet switch SGSN transmits “Delete Bearer Command” to the gateway device S-GW.
- Step S306 the second GBR bearer for the mobile station UE is released by starting the GBR bearer release procedure shown in FIG.
- the second GBR bearer when a failure occurs in the radio network controller RNC in a state where the GBR bearer is set, the second GBR bearer is disconnected at an appropriate timing. The charging process for the second GBR bearer can be stopped.
- Modification 1 With reference to FIG. 11, a mobile communication system according to Modification 1 of the second embodiment described above will be described. Hereinafter, the mobile communication system according to the first modification will be described by focusing on differences from the mobile communication system according to the second embodiment described above.
- steps S350A to S350C are the same as the operations in steps S300A to S300C shown in FIG.
- step 351 the gateway device S-GW transmits “Downlink Data Notification” including “Cause: Error Indication received from RNC / eNodeB (predetermined information)” to the packet switch SGSN.
- step S352 the packet switch SGSN transmits “Paging (paging signal)” addressed to the mobile station UE to the radio network controller RNC and starts a paging timer.
- Paging paging signal
- step S353 If there is no response to “Paging” from the mobile station UE before the paging timer expires in step S353, the packet switch SGSN performs the GBR bearer determination process shown in FIG. 6 in step S354.
- step S355 and S356 are the same as operation
- Modification 2 With reference to FIG.12 and FIG.13, the mobile communication system which concerns on the modification 2 of the above-mentioned 2nd Embodiment is demonstrated.
- the mobile communication system according to the second modification will be described by focusing on differences from the mobile communication system according to the second embodiment described above.
- “Direct Tunnel” is applied, that is, packets transferred from the gateway device P-GW to the gateway device S-GW are wirelessly transmitted without going through the packet switch SGSN. It is configured to be transferred to the line control station RNC.
- steps S400A and S400B are the same as the operations in steps S300A and S300B shown in FIG.
- step S401 the radio network controller RNC transmits a RESET signal to the packet switch SGSN.
- the packet switch SGSN may perform the GBR bearer determination process shown in FIG. 3 or 6 in step S401A.
- the packet switch SGSN activates a GBR bearer release waiting timer in step S402, and transmits “Release Access Bearer Request” to the gateway device S-GW in step S403.
- the gateway device S-GW releases the GBR bearer resource for the radio network controller RNC in step S404, and transmits "Release Access Bearer Response" to the packet switch SGSN in step S405.
- the packet switch SGSN sends a “Delete Bearer Command” to the gateway device S-GW in step S407. ".
- step S408 the second GBR bearer for the mobile station UE is released by starting the GBR bearer release procedure shown in FIG.
- the packet switch SGSN may be configured to detect a failure in the radio network controller RNC by a method other than receiving a RESET signal from the radio network controller RNC.
- the packet switch SGSN may be configured to detect a failure in the radio network controller RNC using RANAP signal processing or the like.
- Modification 3 With reference to FIG. 14, a mobile communication system according to Modification 3 of the above-described second embodiment will be described. Hereinafter, the mobile communication system according to the third modification will be described by focusing on differences from the mobile communication system according to the second embodiment described above.
- Non-Direct Tunnel is applied, that is, a packet transferred from the gateway device P-GW to the gateway device S-GW passes through the packet switch SGSN. It is configured to be transferred to the radio network controller RNC.
- step S501 the radio network controller RNC transmits a RESET signal to the packet switch SGSN.
- the packet switch SGSN may perform the GBR bearer determination process shown in FIG. 3 or FIG. 6 when receiving the RESET signal.
- the packet switch SGSN activates a GBR bearer release waiting timer in step S502, and releases a GBR bearer resource for the radio network controller RNC in step S503.
- step S504 If there is no connection request from the mobile station UE before the GBR bearer release waiting timer expires in step S504, the packet switch SGSN starts the GBR bearer release procedure shown in FIG. Release the second GBR bearer for use.
- the first feature of the present embodiment is a mobile communication method, which is between a gateway device S-GW and a radio network controller RNC, or between a radio network controller RNC and a packet switch SGSN, and a packet.
- the first GBR bearer for the mobile station UE is set between the exchange SGSN and the gateway device S-GW
- the second GBR bearer for the mobile station UE is set between the gateway device S-GW and the gateway device P-GW.
- the gist is to include the step C.
- step C the packet switch SGSN further starts a procedure for releasing the second GBR bearer when it is determined that the second GBR bearer is a bearer that provides service by time charging. May be.
- the packet switch SGSN further includes “Cause: Error Received from RNC / eNodeB” in “Downlink Data Notification”, and this information element
- a procedure for releasing the second GBR bearer may be started.
- the gateway device S-GW may detect a failure of the radio network controller RNC when “Error Indication” is received from the radio network controller RNC. .
- a second feature of the present embodiment is a mobile communication method, in which a first GBR bearer for the mobile station UE is set between the gateway device S-GW and the radio network controller RNC, and the gateway device S-
- the packet switch SGSN detects a failure of the radio base station eNodeB in a state where the second GBR bearer for the mobile station UE is set between the GW and the gateway device P-GW
- the gateway device S-GW “Release Access Bearer Request” is transmitted to start the GBR bearer release waiting timer
- the gateway device S-GW releases the first GBR bearer according to “Release Access Bearer Request”
- the packet switch SGSN, GBR bearer release waiting timer Before the expiration does not receive a connection request from the mobile station UE, and the gist that a step of initiating a procedure for releasing the first 2GBR bearer.
- the third feature of the present embodiment is a packet switch SGSN, in which a first GBR bearer for the mobile station UE is set between the gateway device S-GW and the radio network controller RNC, and the gateway device S- While the second GBR bearer for the mobile station UE is set between the GW and the gateway device P-GW, the gateway device S-GW detects a failure of the radio network controller RNC and releases the first GBR bearer.
- the gateway device S-GW detects a failure of the radio network controller RNC and releases the first GBR bearer.
- “Downlink Data Notification” is transmitted to the packet switch SGSN, it is configured to transmit “Paging” to the mobile station UE, and within the period specified by the paging timer. If the mobile station UE does not receive a response to “Paging”, the second GBR bearer
- the gist of the present invention is that it is configured to start a procedure for releasing.
- the second GBR bearer may be configured to start a procedure for releasing the second GBR bearer when it is determined that the second GBR bearer is a bearer that provides a service by time charging. .
- a procedure for releasing the second GBR bearer may be started.
- Downlink Data Notification includes “Cause: Error Indication received received RNC / eNodeB”, and the contents of the information element fall under the reason to be disconnected. If determined, the procedure for releasing the second GBR bearer may be started.
- a fourth feature of the present embodiment is a packet switch SGSN, in which a first GBR bearer for the mobile station UE is set between the gateway device S-GW and the radio network controller RNC, and the gateway device S- When a failure of the radio network controller RNC is detected in a state where the second GBR bearer for the mobile station UE is set between the GW and the gateway device P-GW, the gateway device S-GW is notified of “Release Access”. "Bearer Request" is transmitted, and the GBR bearer release wait timer is configured to be started. If the connection request is not received from the mobile station UE before the GBR bearer release wait timer expires, the second GBR bearer is released. The gist is that the procedure is configured to start.
- the operations of the mobile station UE, the radio base station eNodeB, the mobility management node MME, the gateway device S-GW, the gateway device P-GW, the packet switch SGSN, the radio network controller RNC, and the like are performed by hardware. It may be implemented by a software module executed by a processor, or may be implemented by a combination of both.
- Software modules include RAM (Random Access Memory), flash memory, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electronically Erasable and Programmable, Removable ROM, and Hard Disk). Alternatively, it may be provided in a storage medium of an arbitrary format such as a CD-ROM.
- Such a storage medium is connected to the processor so that the processor can read and write information from and to the storage medium. Further, such a storage medium may be integrated in the processor.
- Such a storage medium and processor may be provided in the ASIC.
- Such an ASIC may be provided in the mobile station UE, the radio base station eNodeB, the mobility management node MME, the gateway device S-GW, the gateway device P-GW, the packet switching device SGSN, or the radio network controller RNC.
- the storage medium and the processor are provided as discrete components in the mobile station UE, the radio base station eNodeB, the mobility management node MME, the gateway device S-GW, the gateway device P-GW, the packet switching device SGSN, and the radio network controller RNC. May be provided.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
図1乃至図4を参照して、本発明の第1の実施形態に係る移動通信システムについて説明する。
図5及び図6を参照して、上述の第1の実施形態の変更例1に係る移動通信システムについて説明する。以下、本変更例1に係る移動通信システムについて、上述の第1の実施形態に係る移動通信システムとの相違点に着目して説明する。
図7及び図8を参照して、上述の第1の実施形態の変更例2に係る移動通信システムについて説明する。以下、本変更例2に係る移動通信システムについて、上述の第1の実施形態に係る移動通信システムとの相違点に着目して説明する。
図9及び図10を参照して、上述の第2の実施形態に係る移動通信システムについて説明する。以下、本発明の第2の実施形態に係る移動通信システムについて、上述の第1の実施形態に係る移動通信システムとの相違点に着目して説明する。
図11を参照して、上述の第2の実施形態の変更例1に係る移動通信システムについて説明する。以下、本変更例1に係る移動通信システムについて、上述の第2の実施形態に係る移動通信システムとの相違点に着目して説明する。
図12及び図13を参照して、上述の第2の実施形態の変更例2に係る移動通信システムについて説明する。以下、本変更例2に係る移動通信システムについて、上述の第2の実施形態に係る移動通信システムとの相違点に着目して説明する。
図14を参照して、上述の第2の実施形態の変更例3に係る移動通信システムについて説明する。以下、本変更例3に係る移動通信システムについて、上述の第2の実施形態に係る移動通信システムとの相違点に着目して説明する。
Claims (20)
- 第1ゲートウェイ装置と無線基地局との間で移動局用の第1ベアラが設定されており、該第1ゲートウェイ装置と第2ゲートウェイ装置との間で該移動局用の第2ベアラが設定されている状態で、該第1ゲートウェイ装置が、該無線基地局からエラー指示信号を受信すると、該第1ベアラを解放すると共に、移動管理用ノードに対して、バッファリング中の該移動局宛ての下りリンクデータ信号を通知するための下りリンクデータ通知を送信する工程Aと、
前記移動管理用ノードが、前記移動局に対して、ページング信号を送信する工程Bと、
前記移動管理用ノードが、所定期間内に前記ページング信号に対する前記移動局からの応答を受信しない場合、前記第2ベアラを解放する手順を開始する工程Cとを有することを特徴とする移動通信方法。 - 前記工程Cにおいて、前記移動管理用ノードは、更に、前記第2ベアラが時間課金によってサービスを提供するベアラであると判定した場合に、前記第2ベアラを解放する手順を開始することを特徴とする請求項1に記載の移動通信方法。
- 前記工程Cにおいて、前記移動管理用ノードは、更に、前記第2ベアラに所定QCIが割り当てられていると判定した場合に、前記第2ベアラを解放する手順を開始することを特徴とする請求項1に記載の移動通信方法。
- 前記工程Cにおいて、前記移動管理用ノードは、更に、前記第2ベアラがGBRベアラである場合に、前記第2ベアラを解放する手順を開始することを特徴とする請求項1に記載の移動通信方法。
- 前記工程Cにおいて、前記移動管理用ノードは、更に、前記下りリンクデータ通知に所定情報が含まれていると判定した場合に、前記第2ベアラを解放する手順を開始することを特徴とする請求項2乃至4のいずれか一項に記載の移動通信方法。
- 移動管理用ノードであって、
第1ゲートウェイ装置と無線基地局との間で移動局用の第1ベアラが設定されており、該第1ゲートウェイ装置と第2ゲートウェイ装置との間で該移動局用の第2ベアラが設定されている状態で、該第1ゲートウェイ装置が、該無線基地局からエラー指示信号を受信し、該第1ベアラを解放すると共に、前記移動管理用ノードに対して、バッファリング中の該移動局宛ての下りリンクデータ信号を通知するための下りリンクデータ通知を送信した場合に、前記移動局に対して、ページング信号を送信するように構成されており、
所定期間内に前記ページング信号に対する前記移動局からの応答を受信しない場合、前記第2ベアラを解放する手順を開始するように構成されていることを特徴とする移動管理用ノード。 - 更に、前記第2ベアラが時間課金によってサービスを提供するベアラであると判定した場合に、前記第2ベアラを解放する手順を開始するように構成されていることを特徴とする請求項6に記載の移動管理用ノード。
- 更に、前記第2ベアラに所定QCIが割り当てられていると判定した場合に、前記第2ベアラを解放する手順を開始するように構成されていることを特徴とする請求項6に記載の移動管理用ノード。
- 更に、前記第2ベアラがGBRベアラである場合に、前記第2ベアラを解放する手順を開始するように構成されていることを特徴とする請求項6に記載の移動管理用ノード。
- 更に、前記下りリンクデータ通知に所定情報が含まれていると判定した場合に、前記第2ベアラを解放する手順を開始するように構成されていることを特徴とする請求項7乃至9のいずれか一項に記載の移動管理用ノード。
- 第1ゲートウェイ装置と無線回線制御局との間で移動局用の第1ベアラが設定されており、該第1ゲートウェイ装置と第2ゲートウェイ装置との間で該移動局用の第2ベアラが設定されている状態で、該第1ゲートウェイ装置が、該無線回線制御局からエラー指示信号を受信すると、該第1ベアラを解放すると共に、パケット交換機に対して、バッファリング中の該移動局宛ての下りリンクデータ信号を通知するための下りリンクデータ通知を送信する工程Aと、
前記パケット交換機が、前記移動局に対して、ページング信号を送信する工程Bと、
前記パケット交換機が、所定期間内に前記ページング信号に対する前記移動局からの応答を受信しない場合、前記第2ベアラを解放する手順を開始する工程Cとを有することを特徴とする移動通信方法。 - 前記工程Cにおいて、前記パケット交換機は、更に、前記第2ベアラが時間課金によってサービスを提供するベアラであると判定した場合に、前記第2ベアラを解放する手順を開始することを特徴とする請求項11に記載の移動通信方法。
- 前記工程Cにおいて、前記パケット交換機は、更に、前記第2ベアラに所定QCIが割り当てられていると判定した場合に、前記第2ベアラを解放する手順を開始することを特徴とする請求項11に記載の移動通信方法。
- 前記工程Cにおいて、前記パケット交換機は、更に、前記第2ベアラがGBRベアラである場合に、前記第2ベアラを解放する手順を開始することを特徴とする請求項11に記載の移動通信方法。
- 前記工程Cにおいて、前記パケット交換機は、更に、前記下りリンクデータ通知に所定情報が含まれていると判定した場合に、前記第2ベアラを解放する手順を開始することを特徴とする請求項12乃至14のいずれか一項に記載の移動通信方法。
- パケット交換機であって、
第1ゲートウェイ装置と無線回線制御局との間で移動局用の第1ベアラが設定されており、該第1ゲートウェイ装置と第2ゲートウェイ装置との間で該移動局用の第2ベアラが設定されている状態で、該第1ゲートウェイ装置が、該無線回線制御局からエラー指示信号を受信し、該第1ベアラを解放すると共に、前記パケット交換機に対して、バッファリング中の該移動局宛ての下りリンクデータ信号を通知するための下りリンクデータ通知を送信した場合に、前記移動局に対して、ページング信号を送信するように構成されており、
所定期間内に前記ページング信号に対する前記移動局からの応答を受信しない場合、前記第2ベアラを解放する手順を開始するように構成されていることを特徴とするパケット交換機。 - 更に、前記第2ベアラが時間課金によってサービスを提供するベアラであると判定した場合に、前記第2ベアラを解放する手順を開始するように構成されていることを特徴とする請求項16に記載のパケット交換機。
- 更に、前記第2ベアラに所定QCIが割り当てられていると判定した場合に、前記第2ベアラを解放する手順を開始するように構成されていることを特徴とする請求項16に記載のパケット交換機。
- 更に、前記第2ベアラがGBRベアラである場合に、前記第2ベアラを解放する手順を開始するように構成されていることを特徴とする請求項16に記載のパケット交換機。
- 更に、前記下りリンクデータ通知に所定情報が含まれていると判定した場合に、前記第2ベアラを解放する手順を開始するように構成されていることを特徴とする請求項17乃至19のいずれか一項に記載のパケット交換機。
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP10823487.3A EP2490474B1 (en) | 2009-10-16 | 2010-10-15 | GBR bearer release when the MME/SGSN fails to page the UE |
US13/501,313 US8693400B2 (en) | 2009-10-16 | 2010-10-15 | Mobile communication method, mobility management node, and packet exchanger |
KR20127009695A KR101182744B1 (ko) | 2009-10-16 | 2010-10-15 | 이동통신방법, 이동관리용 노드 및 패킷 교환기 |
CN201080046675.XA CN102577481B (zh) | 2009-10-16 | 2010-10-15 | 移动通信方法、移动管理用节点以及分组交换机 |
MX2012004389A MX2012004389A (es) | 2009-10-16 | 2010-10-15 | Metodo de comunicacion movil, nodo de manejo de movilidad e intercambiador de paquetes. |
RU2012118482/07A RU2510593C2 (ru) | 2009-10-16 | 2010-10-15 | Способ мобильной связи, узел управления мобильностью и коммутатор пакетов |
CA 2777580 CA2777580C (en) | 2009-10-16 | 2010-10-15 | Mobile communication method, mobility management node, and packet exchanger |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2009-239881 | 2009-10-16 | ||
JP2009239881A JP4648479B1 (ja) | 2009-10-16 | 2009-10-16 | 移動通信方法、移動管理用ノード及びパケット交換機 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011046219A1 true WO2011046219A1 (ja) | 2011-04-21 |
Family
ID=43836083
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2010/068207 WO2011046219A1 (ja) | 2009-10-16 | 2010-10-15 | 移動通信方法、移動管理用ノード及びパケット交換機 |
PCT/JP2010/068208 WO2011046220A1 (ja) | 2009-10-16 | 2010-10-15 | 移動通信方法、移動管理用ノード及びパケット交換機 |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2010/068208 WO2011046220A1 (ja) | 2009-10-16 | 2010-10-15 | 移動通信方法、移動管理用ノード及びパケット交換機 |
Country Status (12)
Country | Link |
---|---|
US (2) | US8462801B2 (ja) |
EP (2) | EP2490474B1 (ja) |
JP (1) | JP4648479B1 (ja) |
KR (2) | KR101182744B1 (ja) |
CN (2) | CN102577481B (ja) |
AU (1) | AU2010307635B2 (ja) |
BR (1) | BR112012008953A2 (ja) |
CA (2) | CA2777580C (ja) |
HK (1) | HK1172768A1 (ja) |
MX (2) | MX2012004393A (ja) |
RU (1) | RU2510593C2 (ja) |
WO (2) | WO2011046219A1 (ja) |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2544470A1 (en) * | 2011-07-04 | 2013-01-09 | Koninklijke KPN N.V. | Triggering with QoS parameters |
GB2493349A (en) * | 2011-07-29 | 2013-02-06 | Intellectual Ventures Holding 81 Llc | Mobile communications network with simplified handover |
JP5421969B2 (ja) * | 2011-10-03 | 2014-02-19 | 株式会社Nttドコモ | 移動通信方法、移動管理ノード、パケット交換機及び移動局 |
JP6403402B2 (ja) * | 2014-03-12 | 2018-10-10 | Kddi株式会社 | 通信装置、基地局装置、通信システムおよび通信方法 |
US10517132B2 (en) * | 2015-07-17 | 2019-12-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Terminal devices, network nodes and methods of operating the same |
EP3393153B1 (en) | 2015-12-31 | 2021-02-17 | Huawei Technologies Co., Ltd. | Method and device for processing packets |
US10003454B2 (en) | 2016-04-22 | 2018-06-19 | Kandou Labs, S.A. | Sampler with low input kickback |
IT201700018570A1 (it) * | 2017-02-20 | 2018-08-20 | Telecom Italia Spa | Comunicazione machine-to-machine in una rete di comunicazione mobile |
CN109600829B (zh) * | 2017-09-30 | 2020-11-06 | 深圳市海思半导体有限公司 | 一种恢复网络的方法及设备 |
KR20230099050A (ko) | 2021-12-27 | 2023-07-04 | 주영민 | 휴대용 애완견 배설물 수거기 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008172294A (ja) * | 2007-01-05 | 2008-07-24 | Ntt Docomo Inc | 移動通信システム、移動通信方法、アクセス装置及びゲートウェイ情報記憶装置 |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FI111312B (fi) * | 2000-08-25 | 2003-06-30 | Nokia Corp | Yhteyden päätelaitteeseen valvonta tietoliikennejärjestelmässä |
WO2002032166A1 (en) * | 2000-10-09 | 2002-04-18 | Nokia Corporation | Connection release in a two-layer communication network |
WO2003084156A1 (fr) * | 2002-03-29 | 2003-10-09 | Ntt Docomo, Inc. | Procede d'administration de communication dans une communication de type connexion, dispositif de relais associe et dispositif de gestion de comptabilite |
KR20050007977A (ko) * | 2003-07-12 | 2005-01-21 | 삼성전자주식회사 | 이동 통신 시스템에서의 보코더의 모드 및 전송율 제어 방법 |
CN100499636C (zh) * | 2004-06-14 | 2009-06-10 | 华为技术有限公司 | 一种实现端到端服务质量可靠性保证的方法 |
CN101022648B (zh) * | 2006-02-14 | 2010-06-09 | 中兴通讯股份有限公司 | 宽带码分多址***寻呼触发的资源释放方法 |
FI20075062A0 (fi) * | 2007-02-01 | 2007-02-01 | Nokia Corp | Menetelmä, laite, järjestelmä, tietokoneohjelmatuote ja tietokoneohjelman jakeluväline |
JP5025440B2 (ja) * | 2007-12-04 | 2012-09-12 | 株式会社日立国際電気 | 通信システム及びゲートウェイ |
CN101534497B (zh) * | 2008-03-10 | 2010-12-08 | 大唐移动通信设备有限公司 | 分组数据网连接中承载处理的方法及移动性管理实体设备 |
US8179903B2 (en) * | 2008-03-12 | 2012-05-15 | Qualcomm Incorporated | Providing multiple levels of service for wireless communication devices communicating with a small coverage access point |
US8218436B2 (en) * | 2008-03-21 | 2012-07-10 | Research In Motion Limited | Dynamic aggregated maximum bit rate for evolved packet system non-guaranteed bit rate quality of service enforcement and network bandwidth utilization |
CN102227150B (zh) * | 2008-04-30 | 2014-11-05 | 华为技术有限公司 | 资源处理的方法、通信***和移动性管理网元 |
CN101572942B (zh) * | 2008-04-30 | 2012-04-04 | 华为技术有限公司 | 一种隐分离方法、***和装置 |
-
2009
- 2009-10-16 JP JP2009239881A patent/JP4648479B1/ja active Active
-
2010
- 2010-10-15 KR KR20127009695A patent/KR101182744B1/ko active IP Right Grant
- 2010-10-15 US US13/501,361 patent/US8462801B2/en active Active
- 2010-10-15 CN CN201080046675.XA patent/CN102577481B/zh active Active
- 2010-10-15 CA CA 2777580 patent/CA2777580C/en active Active
- 2010-10-15 MX MX2012004393A patent/MX2012004393A/es active IP Right Grant
- 2010-10-15 US US13/501,313 patent/US8693400B2/en active Active
- 2010-10-15 WO PCT/JP2010/068207 patent/WO2011046219A1/ja active Application Filing
- 2010-10-15 WO PCT/JP2010/068208 patent/WO2011046220A1/ja active Application Filing
- 2010-10-15 RU RU2012118482/07A patent/RU2510593C2/ru active
- 2010-10-15 CN CN201080046692.3A patent/CN102577482B/zh active Active
- 2010-10-15 MX MX2012004389A patent/MX2012004389A/es active IP Right Grant
- 2010-10-15 KR KR20127009564A patent/KR101224000B1/ko active IP Right Grant
- 2010-10-15 AU AU2010307635A patent/AU2010307635B2/en active Active
- 2010-10-15 BR BR112012008953-6A patent/BR112012008953A2/pt not_active IP Right Cessation
- 2010-10-15 CA CA2777581A patent/CA2777581C/en active Active
- 2010-10-15 EP EP10823487.3A patent/EP2490474B1/en active Active
- 2010-10-15 EP EP10823488.1A patent/EP2490475B1/en active Active
-
2012
- 2012-12-28 HK HK12113545.9A patent/HK1172768A1/zh unknown
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2008172294A (ja) * | 2007-01-05 | 2008-07-24 | Ntt Docomo Inc | 移動通信システム、移動通信方法、アクセス装置及びゲートウェイ情報記憶装置 |
Non-Patent Citations (1)
Title |
---|
"3GPP TS23.007, V9.1.0.", 3GPP, September 2009 (2009-09-01) * |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP4648479B1 (ja) | 移動通信方法、移動管理用ノード及びパケット交換機 | |
US10506465B2 (en) | Overload control in a packet mobile communication system | |
US9282534B2 (en) | Mobile communication method, session control node, gateway device, and mobility management node | |
JP2020507274A (ja) | Ranを統合された免許が不要なスペクトルの区別 | |
EP2480022A1 (en) | Bearer processing method and mobile management device | |
WO2013051512A1 (ja) | 移動通信方法、移動管理ノード、パケット交換機及び移動局 | |
JP6561995B2 (ja) | 制御装置及びその方法 | |
JP5309078B2 (ja) | 移動通信システム及び無線アクセスネットワーク装置 | |
JP4647720B1 (ja) | 移動通信方法、移動管理用ノード及びパケット交換機 | |
JP2011087321A (ja) | 移動通信方法、移動管理用ノード及びパケット交換機 | |
CN101267587A (zh) | 一种实现负载重分配的方法、装置及*** | |
WO2014050396A1 (ja) | 移動通信方法及び無線基地局 | |
JP2012039248A (ja) | 移動通信方法及び無線アクセスネットワーク装置 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201080046675.X Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10823487 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2777580 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: MX/A/2012/004389 Country of ref document: MX |
|
ENP | Entry into the national phase |
Ref document number: 20127009695 Country of ref document: KR Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 3687/CHENP/2012 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010823487 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012118482 Country of ref document: RU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13501313 Country of ref document: US |