WO2013015188A1 - 通信システム、通信方法、基地局、および、管理装置 - Google Patents
通信システム、通信方法、基地局、および、管理装置 Download PDFInfo
- Publication number
- WO2013015188A1 WO2013015188A1 PCT/JP2012/068315 JP2012068315W WO2013015188A1 WO 2013015188 A1 WO2013015188 A1 WO 2013015188A1 JP 2012068315 W JP2012068315 W JP 2012068315W WO 2013015188 A1 WO2013015188 A1 WO 2013015188A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- management information
- base station
- henb
- mobile station
- station
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 84
- 238000000034 method Methods 0.000 title claims description 139
- 230000004044 response Effects 0.000 claims abstract description 33
- 230000008859 change Effects 0.000 claims description 5
- 238000012545 processing Methods 0.000 description 65
- 230000008569 process Effects 0.000 description 54
- 230000006870 function Effects 0.000 description 33
- 238000010586 diagram Methods 0.000 description 28
- 230000005540 biological transmission Effects 0.000 description 20
- 230000000694 effects Effects 0.000 description 8
- 230000004048 modification Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000001360 synchronised effect Effects 0.000 description 4
- 230000002093 peripheral effect Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
- H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/20—Interfaces between hierarchically similar devices between access points
Definitions
- the present invention relates to a communication system including a gateway connected to a base station, a communication method in the system, a base station directed to the system, and a management device directed to the system.
- LTE Long Term Evolution
- LTE-A Long Term Evolution-Advanced
- HeNB Home evolved Node B
- Patent Documents 1 to 3 disclose an example of procedures related to such handover.
- an S1 interface and an X2 interface are prepared in the LTE method or the LTE-A method.
- the S1 interface performs handover using a control channel between each base station and the corresponding gateway.
- the handover using the S1 interface requires the exchange of control information via the core network, so that the network load becomes relatively large.
- the X2 interface performs pseudo-direct connection between base stations and performs handover without going through data processing in the core network. Therefore, the network load can be relatively small.
- the base station and the gateway connected to the base station hold UE_context which is management information for managing mobile stations existing in the cell area managed by the base station.
- UE_context is management information for managing mobile stations existing in the cell area managed by the base station.
- a base station connected to a mobility management function (Mobility Management Entity: hereinafter also referred to as “MME”) via a gateway is connected to the mobility management function without going through the gateway.
- MME mobility Management Entity
- UE_context held by the gateway is not released (see Non-Patent Document 1).
- a procedure for updating UE_context held by the base station of the movement source and the corresponding gateway is proposed by a command from the mobility management function.
- the processing load on the mobility management function may increase.
- the present invention has been made to solve such a problem, and an object thereof is to provide a configuration capable of suppressing an increase in processing load of the mobility management function even when a handover occurs.
- a communication system provides a mobile station, a management device that manages the position of the mobile station, a first cell area, and a management for managing the mobile station in the first cell area.
- a first base station that holds information, a gateway that is arranged between the first base station and the management device, and holds management information for managing mobile stations in the first cell area;
- a second base station that provides a cell area.
- the first base station receives management information associated with the mobile station from among the management information held by itself.
- a command for updating the management information associated with the mobile station is transmitted to the gateway.
- a management apparatus that manages the position of a mobile station, first and second base stations, and a gateway that is disposed between the first base station and the management apparatus are provided.
- a communication method in a communication system is provided. The communication method is held by the first base station in response to the movement of the mobile station from the first cell area provided by the first base station to the second cell area provided by the second base station. Updating the management information associated with the mobile station, and in response to the management entity of the mobile station being changed from the local station to the second base station, the first base station associates with the mobile station. Sending to the gateway a command to update the received management information.
- a base station that provides a cell area.
- the base station is connected to a gateway that holds management information for managing mobile stations in the cell area, and the gateway is connected to a management device that manages the position of the mobile station.
- the base station holds the management information for managing the mobile station in the cell area, and holds in response to the change of the management entity of the mobile station from its own station to another base station. Updating the management information associated with the mobile station in the management information, and transmitting a command for updating the management information associated with the mobile station to the gateway.
- a management device that manages the position of a mobile station.
- a first base station is connected to the management apparatus via a gateway, and a second base station that provides a second cell area is directly connected to the management apparatus.
- the first base station provides a first cell area and holds management information for managing mobile stations in the first cell area.
- the gateway holds management information for managing mobile stations in the first cell area.
- the first base station receives management information associated with the mobile station from among the management information held by itself. Update.
- the management device In response to the movement of the mobile station from the first cell area to the second cell area, the management device sends a response to the mobile station independently of the notification that the first base station has updated the management information. Means are included for sending a command to update the associated management information to the gateway.
- an increase in the processing load of the mobility management function can be suppressed even when a handover occurs.
- FIG. 1 is a schematic diagram showing a configuration of a communication system 1 assumed in the embodiment of the present invention. As a typical example, it is assumed that the communication system 1 supports a communication method according to the LTE method or the LTE-A method.
- a communication system 1 is also referred to as a mobile station (User Equipment: hereinafter referred to as “UE”) 100 and a plurality of small evolved base stations (Home evolved Node B: hereinafter referred to as “HeNB”). ) 200-1 to 200-3, a gateway 300, a mobility management function (Mobility Management Entity: hereinafter also referred to as “MME”) 400, and a core network 500.
- MME Mobility Management Entity
- the communication system 1 comprised from HeNB is shown in FIG. 1 exemplarily, instead of the HeNB or in addition to the HeNB, a normal evolved base station (evolved Node B: “eNB” hereinafter) It is also possible to adopt a configuration including the same. In some cases, the eNB and the HeNB are simply referred to as a “base station”.
- the UE 100 is typically a mobile phone, a PDA (Personal Digital Assistant), a data communication terminal, and the like, and exchanges data with the other party via any HeNB.
- PDA Personal Digital Assistant
- HeNBs 200-1 to 200-3 (hereinafter collectively referred to as “HeNB200”) provide cell areas 250-1 to 250-3, respectively. Adjacent cell areas are set to overlap each other. Each of HeNB200 hold
- identifier identifier
- IP Internet Protocol
- the HeNBs 200-1 to 200-3 have an X2 interface with other HeNBs in order to support the handover of the UE 100.
- the gateway 300 is disposed between the HeNB 200 and the MME 400, and mediates data communication between the HeNB 200 and / or data communication between the HeNB 200 and the MME 400.
- the gateway 300 also holds management information for managing the UE 100 in the cell area provided by the HeNB 200 connected to the own station. This management information is typically UE_text as well.
- the gateway 300 substantially includes the management information held by the HeNBs 200-1 and / or 200-3. Keep the same management information.
- the MME 400 is connected to the core network 500 and is connected to the gateway 300 or the HeNB 200.
- MME400 manages the position of UE100.
- the MME 400 realizes a call and / or communication between the UE 100 and the other party by appropriately routing data according to the position where the UE 100 exists. More specifically, the MME 400 performs control such as setting and release of a session (connection) for packet communication and handover (switching of base stations).
- the MME 400 enables a call and / or communication between the UEs 100 existing in different cell areas.
- the core network 500 is assumed to be a network in which all information is packetized.
- the UE 100 is carried by a user and moves between cell areas as the user moves. For example, as shown in FIG. 1, when the UE 100 that existed in the cell area 250-1 provided by the HeNB 200-1 moves into the cell area 250-2 provided by the HeNB 200-2, the HeNB 200-1 and the HeNB 200 -2, handover processing according to the X2 interface is executed. When this handover process is completed, the completion is transmitted to the MME 400. And MME400 updates the management information of UE100.
- the HeNB 200 that provides the cell area where the UE 100 existed before the handover is referred to as “source HeNB”, and the HeNB 200 that provides the cell area to which the UE 100 has been handed over is also referred to as “target HeNB”.
- the gateway 300 when the gateway 300 is connected to the HeNB 200 that has become the source HeNB, the gateway 300 is also referred to as “source HeNB_GW”.
- FIG. 2 is a block diagram showing a schematic configuration of mobile station (UE) 100 according to the embodiment of the present invention.
- UE 100 includes a housing 130 provided with a transmission antenna 114 for transmitting a radio signal and a reception antenna 118 for receiving the radio signal.
- the housing 130 includes a central processing unit 102, a signal processing unit 106, a wireless transmission unit 112, and a wireless reception unit 116.
- the central processing unit 102 includes, as main components, a processor, a nonvolatile memory for holding a program executed by the processor, and a volatile memory functioning as a work memory.
- a part or all of the functions provided by the central processing unit 102 may be implemented as dedicated hardware (for example, an integrated circuit).
- one chip including all or part of the functions provided by the signal processing unit 106, the wireless transmission unit 112, and the wireless reception unit 116 May be used.
- SoC System On a Chip
- components such as a processor, a memory, and a controller for peripheral devices are integrated into one chip can be used.
- all or part of the functions provided by the signal processing unit 106, the wireless transmission unit 112, and the wireless reception unit 116 may be implemented as software.
- an arithmetic device such as a CPU (Central Processing Unit) or a DSP (Digital Signal Processor) executes a preinstalled instruction set.
- the signal processing unit 106 processes a radio signal exchanged with the HeNB 200 that manages the cell area in which the device itself exists. More specifically, the signal processing unit 106 outputs information to be transmitted to the HeNB 200 to the radio transmission unit 112 in accordance with an internal command given from the central processing unit 102 or the like.
- the wireless transmission unit 112 encodes and modulates information received from the signal processing unit 106, and radiates a wireless signal obtained as a result to the outside via the transmission antenna 114.
- Radio receiving section 116 demodulates and decodes the radio signal received via receiving antenna 118, and outputs the information obtained as a result to signal processing section 106.
- the casing 130 further includes a display unit 120 for displaying various types of information, a microphone 122 for acquiring user's voice, a speaker 124 for reproducing received voice, and a user operation. And an input unit 126. These parts are typically arranged so as to be exposed from the housing 130.
- FIG. 3 is a block diagram showing a schematic configuration of base station (HeNB) 200 according to the embodiment of the present invention.
- the HeNB 200 includes a central processing unit 202, a signal processing unit 206, a storage unit 208, a radio transmission unit 212, a transmission antenna 214, a radio reception unit 216, a reception antenna 218, and a host.
- a network interface (I / F) 220 and a control interface (I / F) 222 are included.
- the central processing unit 202 includes, as main components, a processor, a nonvolatile memory for holding a program executed by the processor, and a volatile memory functioning as a work memory. Further, the central processing unit 202 includes a handover logic 204 and an X2 interface logic 205. These logics are typically provided by the central processing unit 202 executing a program. For example, modules corresponding to each logic are stored in advance in a non-volatile memory, and the functions described later are realized by the central processing unit 202 reading and executing these modules.
- the handover logic 204 performs a handover with at least one other HeNB 200. This handover is started in response to various information transmitted from the UE 100.
- the handover logic 204 operates the X2 interface logic 205 for handover between the HeNBs 200.
- HeNB200 or eNB which does not have X2 interface
- the X2 interface logic 205 performs a handover operation using a line directly connecting the own station and another HeNB 200.
- the handover logic 204 updates the management information (UE_context) stored in the storage unit 208 when the handover of any UE 100 is completed.
- UE_context management information
- the central processing unit 202 may be implemented as dedicated hardware (for example, an integrated circuit).
- one chip including all or part of the functions provided by the signal processing unit 206, the wireless transmission unit 212, and the wireless reception unit 216. May be used.
- all or part of the functions provided by the signal processing unit 206, the wireless transmission unit 212, and the wireless reception unit 216 may be implemented as software.
- an arithmetic unit (processor) such as a CPU or DSP executes a preinstalled instruction set.
- the signal processing unit 206 processes a radio signal exchanged with the UE 100 existing in the cell area provided by the own station. More specifically, the signal processing unit 206 outputs information to be transmitted to the UE 100 to the radio transmission unit 212 in accordance with an internal command given from the central processing unit 202 or the like.
- the wireless transmission unit 212 encodes and modulates the information received from the signal processing unit 206 and radiates a wireless signal obtained as a result to the outside via the transmission antenna 214.
- Radio receiving section 216 demodulates and decodes the radio signal received via receiving antenna 218 and outputs the information obtained as a result to signal processing section 206.
- the host network interface 210 exchanges user data, control information, management information, and the like with the gateway 300 or the MME 400 that manages its own station. Similarly, the control interface 222 exchanges control information with other HeNBs 200.
- FIG. 4 is a block diagram showing a schematic configuration of gateway 300 according to the embodiment of the present invention.
- gateway 300 includes a central processing unit 302, a storage unit 308, an upper network interface (I / F) 320, lower network interfaces (I / F) 322-1, 322-2,. , 322-n.
- I / F upper network interface
- I / F lower network interfaces
- the central processing unit 302 includes, as main components, a processor, a non-volatile memory for holding a program executed by the processor, and a volatile memory functioning as a work memory. Further, the central processing unit 302 includes UE management logic 304. This logic is typically provided by the central processing unit 302 executing a program. For example, modules corresponding to the UE management logic 304 are stored in advance in a non-volatile memory, and the functions described later are realized by the central processing unit 302 reading and executing these modules.
- the UE management logic 304 detects movement between the cell areas of the UE 100 based on a notification from any HeNB 200 managed by the own station, and is stored in the storage unit 308 based on the detection result. Management information (UE_context) is updated.
- a part or all of the functions provided by the central processing unit 302 may be implemented as dedicated hardware (for example, an integrated circuit).
- all or one of the functions provided by the upper network interface 320 and the lower network interfaces 322-1, 322-2 may be made into one chip including the part.
- SoC SoC in which components such as a processor, a memory, and a controller for peripheral devices are integrated into one chip.
- the host network interface 320 exchanges user data, control information, management information, and the like with the MME 4 that manages its own station.
- the lower network interfaces 322-1, 322-2,..., 322-n exchange user data, control information, management information, and the like with the HeNB 200 managed by the own station.
- the UE 100 moves from the cell area 250-1 provided by the HeNB 200-1 connected to the gateway 300 to the cell area 250-2 provided by the HeNB 200-2.
- the HeNB 200-2 is not connected to the gateway 300 but directly connected to the MME 400.
- FIG. 5 is a sequence diagram showing a procedure related to the handover shown in FIG. 1 under the current standard.
- a handover process in this example, an X2 interface
- Is executed sequence SQ200.
- the target HeNB transmits Path_Switch_Request for updating the routing information of data to the UE 100 to the MME 400 (sequence SQ202).
- MME 400 updates the routing information of the local station and transmits Path_Switch_Request_ACK indicating receipt of Path_Switch_Request to target HeNB (sequence SQ204).
- the target HeNB When receiving the Path_Switch_Request_ACK, the target HeNB transmits Path_Switch_Request to the source HeNB (sequence SQ206).
- the source HeNB releases (Releases) the management information (UE_text) corresponding to the handed over UE 100 held by the source HeNB (sequence SQ208). Then, a series of processing ends.
- the source HeNB_GW may hold the management information of the UE 100 that does not already exist in the cell area provided by the source HeNB indefinitely.
- the management information (UE_context) held by the source HeNB_GW is updated by the MME 400 performing the process in an initiative manner. To do.
- FIG. 6 is a schematic diagram showing a procedure related to handover according to the proposed scheme.
- FIG. 7 is a sequence diagram showing a procedure related to handover according to the proposed scheme.
- a handover process between the UE 100, the source HeNB, the target HeNB, and the MME 400 is executed (sequence SQ200A).
- the target HeNB transmits Path_Switch_Request to the MME 400 as described above (sequence SQ202).
- MME 400 updates the routing information of the local station and transmits Path_Switch_Request_ACK indicating receipt of Path_Switch_Request to target HeNB (sequence SQ204).
- MME 400 transmits a UE_Context_Release command for releasing management information (UE_context) held by source HeNB to source HeNB (sequence SQ220).
- the source HeNB When the source HeNB receives the UE_Context_Release command, the source HeNB releases the management information (UE_context) corresponding to the handed over UE 100 held in the local station according to the command (sequence SQ208). Subsequently, the source HeNB transmits UE_Context_Release_Complete indicating that the release of the management information corresponding to the handed over UE 100 held by itself is completed to the source HeNB_GW (sequence SQ224).
- UE_Context_Release_Complete indicating that the release of the management information corresponding to the handed over UE 100 held by itself is completed to the source HeNB_GW (sequence SQ224).
- the source HeNB_GW When the source HeNB_GW receives the UE_Context_Release_Complete, the source HeNB_GW releases the management information (UE_context) corresponding to the handed over UE 100 held by itself (sequence SQ226). Subsequently, the source HeNB_GW transmits to the MME 400 UE_Context_Release_Complete indicating that the release of the management information corresponding to the handed over UE 100 held by itself is completed (sequence SQ228).
- the management information held by the source HeNB_GW is updated by the MME 400 taking the lead.
- this method can cause the following problems.
- the MME 400 since the MME 400 detects the completion of the update of the management information in the source HeNB_GW by the UE_Context_Release_Complete from the source HeNB_GW, it takes time. That is, it takes a relatively long time for the MME 400 to recognize that the management information held by the gateway 300 has been updated. Moreover, MME400 needs to wait until it receives UE_Context_Release_Complete from source HeNB_GW.
- the processing load on the MME 400 may increase.
- the solving means described later is adopted.
- Embodiment 1 In the communication system according to the first embodiment, at the time of handover from the source HeNB to the target HeNB, the management information (UE_context) held by the source HeNB_GW is updated by the source HeNB performing a leading process. That is, in response to the movement of the UE 100 from the cell area provided by the source HeNB to the cell area provided by the target HeNB, the source HeNB updates the management information associated with the UE 100 among the management information held by the source HeNB. In addition, a command for updating the management information associated with the UE 100 is transmitted to the gateway (source HeNB_GW) that manages the local station.
- the gateway gateway
- FIG. 8 is a schematic diagram showing a procedure for handover in the communication system according to the first embodiment of the present invention.
- FIG. 9 is a sequence diagram showing a procedure for handover in the communication system according to Embodiment 1 of the present invention.
- the procedure illustrated in FIGS. 8 and 9 transmits a message for updating the management information (UE_context) held by the source HeNB_GW and the point that the source HeNB receives the Path_Switch_Request compared to the procedure illustrated in FIG.
- the point is different. That is, in the communication system according to the first embodiment, the source HeNB has means for updating the management information held by the source HeNB_GW.
- the target HeNB transmits Path_Switch_Request for updating the routing information of data to the UE 100 to the MME 400 (sequence SQ102).
- MME 400 updates the routing information of the local station and transmits Path_Switch_Request_ACK indicating reception of Path_Switch_Request to target HeNB (sequence SQ104).
- the target HeNB When the target HeNB receives the Path_Switch_Request_ACK, the target HeNB transmits the Path_Switch_Request to the source HeNB (sequence SQ106).
- the source HeNB When receiving the Path_Switch_Request, the source HeNB transmits UE_Context_Release_Indication, which is a message for updating the held management information, to the source HeNB_GW (sequence SQ108).
- the source HeNB_GW receives the UE_Context_Release_Indication, the source HeNB_GW releases the management information (UE_context) corresponding to the handed over UE 100 held in the local station (sequence SQ112).
- This management information release process is a process for excluding the handed over UE 100 from the management target. More specifically, a method for deleting the UE_text corresponding to the handed over UE 100, a method for adding information (such as a flag) indicating that the UE 100 has moved outside the cell area of the source HeNB, and a management for managing the UE 100 For example, a method to re-save the contents of information.
- This management information release process is a process for excluding the handed over UE 100 from the management target, as in the case of the source HeNB_GW described above. More specifically, a method for deleting the UE_text corresponding to the handed over UE 100, a method for adding information (such as a flag) indicating that the UE 100 has moved outside the cell area of the source HeNB, and a management for managing the UE 100 For example, a method to re-save the contents of information.
- the source HeNB is the UE 100 whose management entity is changed from the source HeNB to the target HeNB (typically, the cell area provided by the target HeNB from the cell area provided by the source HeNB.
- the management information associated with the UE 100 among the management information held by the own station is updated.
- FIG. 10 is a flowchart showing a procedure in the source HeNB in the communication system according to Embodiment 1 of the present invention.
- HeNB 200 determines whether a report indicating that a predetermined condition has been satisfied is received from any UE 100 residing in a cell area provided by the own station (step S100). ).
- This predetermined condition is set in advance by a network (such as the MME 400). As such a predetermined condition, it is assumed that "the reception level in another cell area (provided by the target HeNB) is higher than the reception level in the cell area where the park is present (provided by the source HeNB)" Is done.
- step S100 determines whether or not the UE 100 has notified the UE 100 of a report that triggers a handover process described later.
- step S100 If no report has been received from any UE 100 that a predetermined condition has been received (NO in step S100), the process of step S100 is repeated.
- step S100 When a report indicating that a report indicating that the predetermined condition is satisfied is received from any UE 100 (YES in step S100), the HeNB 200 determines that the handover request is received from the UE 100 that is the report source, and the target A handover process is executed with the other HeNB 200 (step S102). Then, HeNB200 judges whether Path_Switch_Request was received from the other HeNB200 (target HeNB) which performed the handover process (step S104). If Path_Switch_Request has not been received (NO in step S104), the process of step S104 is repeated.
- the HeNB 200 transmits UE_Context_Release_Indication to the source HeNB_GW (Step S106). Subsequently, the HeNB 200 updates the management information (UE_context) corresponding to the handed over UE 100 held in the local station (step S108). Then, a series of processing ends.
- Embodiment 1 since the reliability of message transmission between the source HeNB and the source HeNB_GW is sufficiently ensured, transmission of UE_Context_Release_Complete to the MME 400 is omitted. Accordingly, there is no need to wait until the MME 400 as shown in FIG. 7 receives the UE_Context_Release_Complete. Further, it is sufficient for the source HeNB to transmit only a message for updating the held management information to the source HeNB_GW. Therefore, the processing load can be reduced for both the MME 400 and the source HeNB.
- management information (UE_Context) can be updated quickly.
- the management information (UE_context held by the source HeNB_GW is performed by the source HeNB performing a process at the time of handover from the source HeNB to the target HeNB. ). That is, in response to the movement of the UE 100 from the cell area provided by the source HeNB to the cell area provided by the target HeNB, the source HeNB updates the management information associated with the UE 100 among the management information held by the source HeNB. In addition, a command for updating the management information associated with the UE 100 is transmitted to the gateway (source HeNB_GW) that manages the local station.
- FIG. 11 is a sequence diagram showing a procedure related to handover in the communication system according to the second embodiment of the present invention.
- the procedure illustrated in FIG. 11 is different from the procedure illustrated in FIG. 9 in that the source HeNB transmits UE_Context_Release_Indication to the source HeNB_GW.
- the source HeNB is a UE 100 (typically a cell area provided by the source HeNB) whose management entity is changed from the source HeNB to the target HeNB among the management information held by the own station.
- a command for updating the management information associated with the UE 100 is transmitted to the source HeNB_GW.
- sequences SQ100 to SQ106 in FIG. 11 are the same as the sequences SQ100 to SQ106 in FIG.
- the source HeNB releases the management information (UE_context) corresponding to the handed over UE 100 held by itself (sequence SQ110).
- the source HeNB transmits UE_Context_Release_Indication, which is a message for updating the held management information, to the source HeNB_GW (sequence SQ108A).
- the source HeNB_GW receives the UE_Context_Release_Indication
- the source HeNB_GW releases the management information (UE_context) corresponding to the handed over UE 100 held in the local station (sequence SQ112).
- the UE_Context_Release_Indication transmitted in sequence SQ108A may reflect the contents of the management information updated by source HeNB in sequence SQ110. That is, the source HeNB generates UE_Context_Release_Indication based on the content of the updated UE_context.
- This UE_Context_Release_Indication may include only the changed part of the management information, or may include all the management information held by the source HeNB in addition to the part that has not been changed.
- the management information after the update in the source HeNB is transmitted to the source HeNB_GW, the amount of information to be transmitted can be increased, but the management information held by the source HeNB_GW is the management information after the update in the source HeNB. Can be matched (synchronized).
- FIG. 12 is a flowchart showing a procedure in the source HeNB in the communication system according to the second embodiment of the present invention.
- HeNB 200 determines whether or not a report indicating that a predetermined condition has been satisfied is received from any UE 100 residing in a cell area provided by the own station (step S200). ). Since this predetermined condition has been described in the first embodiment, detailed description thereof will not be repeated. If no report has been received from any UE 100 that a predetermined condition has been received (NO in step S200), the process of step S200 is repeated.
- step S200 When a report indicating that a report indicating that the predetermined condition is satisfied is received from any UE 100 (YES in step S200), the HeNB 200 determines that the handover request is from the notification source UE 100, and the target A handover process is executed with the other HeNB 200 (step S202). Then, HeNB200 judges whether Path_Switch_Request was received from the other HeNB200 (target HeNB) which performed the handover process (step S204). If Path_Switch_Request has not been received (NO in step S204), the process of step S204 is repeated.
- the HeNB 200 updates the management information (UE_context) corresponding to the handed over UE 100 held in the own station (step S206). Then, HeNB200 produces
- the management information can be synchronized between the source HeNB and the source HeNB_GW.
- the UE_Context_Release_Indication when the UE_Context_Release_Indication is received, it is guaranteed that the management information has already been updated in the HeNB managed by the own station, so the management can be performed without considering the state of the HeNB. Information can be updated. Therefore, in the source HeNB_GW, processing necessary for considering the state of the HeNB can be omitted.
- the management information (UE_context held by the source HeNB_GW is performed by the source HeNB performing a process at the time of handover from the source HeNB to the target HeNB. ). That is, in response to the movement of the UE 100 from the cell area provided by the source HeNB to the cell area provided by the target HeNB, the source HeNB updates the management information associated with the UE 100 among the management information held by the source HeNB. In addition, a command for updating the management information associated with the UE 100 is transmitted to the gateway (source HeNB_GW) that manages the local station.
- the gateway gateway
- the source HeNB updates its own management information in response to the notification of the completion of the management information update from the source HeNB_GW. That is, the source HeNB is associated with the UE 100 whose management entity is changed from the source HeNB to the target HeNB (typically, the UE 100 that has moved from the cell area provided by the source HeNB to the cell area provided by the target HeNB). In response to the notification from the source HeNB_GW that the management information has been updated, the management information associated with the UE 100 among the management information held by the own station is updated.
- FIG. 13 is a sequence diagram showing a procedure for handover in the communication system according to the third embodiment of the present invention. Sequences SQ100 to SQ106 in FIG. 13 are the same as sequences SQ100 to SQ106 in FIG. Then, when receiving the Path_Switch_Request, the source HeNB transmits a UE_Context_Release command, which is a command for updating the held management information, to the source HeNB_GW (sequence SQ107).
- the UE_Context_Release command may include an instruction code for updating management information and an instruction code for notifying update of management information.
- the source HeNB_GW When the source HeNB_GW receives the UE_Context_Release command, the source HeNB_GW updates the management information (UE_context) corresponding to the handed over UE 100 held in the local station according to the command (sequence SQ112). Subsequently, the source HeNB_GW transmits UE_Context_Release_Complete indicating that the update of the management information corresponding to the handed over UE 100 held by itself is completed to the source HeNB (sequence SQ111).
- UE_Context_Release_Complete indicating that the update of the management information corresponding to the handed over UE 100 held by itself is completed to the source HeNB (sequence SQ111).
- the source HeNB When the source HeNB receives UE_Context_Release_Complete, the source HeNB releases management information (UE_context) corresponding to the handed over UE 100 held by itself (sequence SQ110). Then, a series of processing ends.
- management information UE_context
- FIG. 14 is a flowchart showing a procedure in the source HeNB in the communication system according to the third embodiment of the present invention.
- HeNB 200 determines whether a report indicating that a predetermined condition has been satisfied is received from any UE 100 residing in the cell area provided by the own station (step S300). ). Since this predetermined condition has been described in the first embodiment, detailed description thereof will not be repeated. If no report has been received from any UE 100 that a predetermined condition has been received (NO in step S300), the process of step S300 is repeated.
- step S300 When a report indicating that a report indicating that the predetermined condition is satisfied is received from any UE 100 (YES in step S300), the HeNB 200 determines that the handover request is from the notification source UE 100, and the target A handover process is executed with the other HeNB 200 (step S302). Then, HeNB200 judges whether Path_Switch_Request was received from the other HeNB200 (target HeNB) which performed the handover process (step S304). If Path_Switch_Request has not been received (NO in step S304), the process of step S304 is repeated.
- the HeNB 200 transmits a UE_Context_Release command to the source HeNB_GW (step S306). Then, HeNB200 judges whether UE_Context_Release_Complete was received from source HeNB_GW (step S308). If UE_Context_Release_Complete has not been received (NO in step S308), the process of step S308 is repeated.
- the HeNB 200 updates the management information (UE_context) corresponding to the handed over UE 100 held in the own station (step S310). Then, a series of processing ends.
- the source HeNB updates its own management information in response to the completion of the update of the management information in the source HeNB_GW. Therefore, management information can be synchronized between the source HeNB and the source HeNB_GW. That is, when viewed from the source HeNB, the management information of the own station can be updated in a state where it is guaranteed that the management information in the source HeNB_GW has been updated. Further, when viewed from the source HeNB_GW, the management information can be updated without considering the state of the HeNB. Therefore, in the source HeNB_GW, processing necessary for considering the state of the HeNB can be omitted.
- the management information (UE_context) held by the source HeNB_GW is performed by the source HeNB performing processing at the time of handover from the source HeNB to the target HeNB. ). That is, in response to the movement of the UE 100 from the cell area provided by the source HeNB to the cell area provided by the target HeNB, the source HeNB updates the management information associated with the UE 100 among the management information held by the source HeNB. In addition, a command for updating the management information associated with the UE 100 is transmitted to the gateway (source HeNB_GW) that manages the local station.
- FIG. 15 is a sequence diagram showing a procedure related to handover in the communication system according to the fourth embodiment of the present invention.
- the procedure shown in FIG. 15 differs from the procedure according to the third embodiment shown in FIG. 13 in that the source HeNB transmits a UE_Context_Release command to the source HeNB_GW. That is, in Embodiment 4, the source HeNB moves from the cell area provided by the source HeNB to the cell area provided by the target HeNB (typically, the UE 100 whose management entity has been changed from the source HeNB to the target HeNB. After transmitting a command for updating the management information associated with the UE 100) to the source HeNB_GW, it waits for a notification that the management information from the source HeNB_GW has been updated.
- sequences SQ100 to SQ106 in FIG. 15 are the same as sequences SQ100 to SQ106 in FIG.
- the source HeNB releases the management information (UE_context) corresponding to the handed over UE 100 held by itself (sequence SQ110).
- the source HeNB transmits a UE_Context_Release command, which is a command for updating the held management information, to the source HeNB_GW (sequence SQ107).
- the source HeNB_GW When the source HeNB_GW receives the UE_Context_Release command, the source HeNB_GW releases the management information (UE_context) corresponding to the handed over UE 100 held in the local station according to the command (sequence SQ112). Subsequently, the source HeNB_GW transmits UE_Context_Release_Complete indicating that the update of the management information corresponding to the handed over UE 100 held by itself is completed to the source HeNB (sequence SQ111). Then, a series of processing ends.
- UE_Context_Release_Complete indicating that the update of the management information corresponding to the handed over UE 100 held by itself is completed to the source HeNB (sequence SQ111).
- the UE_Context_Release command transmitted in sequence SQ107 may reflect the content of the management information updated by source HeNB in sequence SQ110. That is, the source HeNB generates a UE_Context_Release command based on the content of the updated UE_context.
- This UE_Context_Release command may include only the changed portion of the management information, or may include all the management information held by the source HeNB in addition to the unchanged portion.
- the management information after the update in the source HeNB is transmitted to the source HeNB_GW, the amount of information to be transmitted can be increased, but the management information held by the source HeNB_GW is the management information after the update in the source HeNB. Can be matched (synchronized).
- FIG. 16 is a flowchart showing a procedure in the source HeNB in the communication system according to the fourth embodiment of the present invention.
- HeNB 200 determines whether a report indicating that a predetermined condition has been satisfied is received from any UE 100 residing in a cell area provided by the own station (step S400). ). Since this predetermined condition has been described in the first embodiment, detailed description thereof will not be repeated. If no report has been received from any UE 100 that a predetermined condition has been received (NO in step S400), the process of step S400 is repeated.
- step S400 When a report indicating that a report indicating that the predetermined condition is satisfied is received from any UE 100 (YES in step S400), the HeNB 200 determines that the handover request is from the notification source UE 100, and the target A handover process is executed with the other HeNB 200 (step S402). Then, HeNB200 judges whether Path_Switch_Request was received from the other HeNB200 (target HeNB) which performed the handover process (step S404). If Path_Switch_Request has not been received (NO in step S404), the process of step S404 is repeated.
- the HeNB 200 updates the management information (UE_context) corresponding to the handed over UE 100 held in the own station (step S406). Subsequently, the HeNB 200 generates a UE_Context_Release command based on the updated management information (step S408), and transmits the generated UE_Context_Release command to the source HeNB_GW (step S410). Then, a series of processing ends.
- UE_context management information corresponding to the handed over UE 100 held in the own station
- the source HeNB can confirm that the management information held by the source HeNB_GW has been updated. For this reason, even if a communication error occurs and the management information is not appropriately updated in the source HeNB_GW, it can be corrected.
- Embodiment 4 the source HeNB updates UE-Context_Release, which is a command for updating management information after updating management information (UE_context) corresponding to the handed over UE 100 held by itself. Send command to source HeNB_GW.
- the source HeNB may update the management information corresponding to the handed over UE 100 held by the source HeNB after transmitting the UE_Context_Release command, which is a command for updating the management information, to the source HeNB_GW. Good (see block indicated by broken line in FIG. 15).
- the following functions and effects are achieved. That is, since the source HeNB and the source HeNB_GW update the management information in parallel, the time required for a series of processes can be shortened.
- the management information (UE_context held by the source HeNB_GW is performed by the source HeNB performing processing at the time of handover from the source HeNB to the target HeNB. ). That is, in response to the movement of the UE 100 from the cell area provided by the source HeNB to the cell area provided by the target HeNB, the source HeNB updates the management information associated with the UE 100 among the management information held by the source HeNB. In addition, a command for updating the management information associated with the UE 100 is transmitted to the gateway (source HeNB_GW) that manages the local station.
- the MME 400 in response to the completion of the management information update in the source HeNB_GW, the MME 400 Notify that. That is, in Embodiment 5, the source HeNB moves from the cell area provided by the source HeNB to the cell area provided by the target HeNB (typically, the UE 100 whose management entity has been changed from the source HeNB to the target HeNB. In response to the notification from the source HeNB_GW that the management information associated with the UE 100) has been updated, the management information update completion is transmitted to the MME 400.
- FIG. 17 is a sequence diagram showing a procedure for handover in the communication system according to the fifth embodiment of the present invention. Compared with the procedure shown in FIG. 13, the procedure shown in FIG. 17 is a process after updating management information (UE_text) corresponding to the handed over UE 100 held by the source HeNB in its own station (sequence SQ110). Is different.
- UE_text management information
- the source HeNB releases the management information (UE_context) corresponding to the handed over UE 100 held in its own station (sequence SQ110), and then sets the UE_Context_Release_Indication based on the UE_Context_Release_Complete from the source HeNB_GW. (Sequence SQ115). That is, in response to the notification from the source HeNB_GW, the source HeNB notifies the MME 400 that the management information update in the source HeNB and the source HeNB_GW has been completed.
- UE_context management information corresponding to the handed over UE 100 held in its own station
- FIG. 18 is a flowchart showing a procedure in the source HeNB in the communication system according to the fifth embodiment of the present invention.
- HeNB 200 determines whether a report indicating that a predetermined condition has been satisfied is received from any UE 100 residing in a cell area provided by the own station (step S500). ). Since this predetermined condition has been described in the first embodiment, detailed description thereof will not be repeated. When no report has been received from any UE 100 that a predetermined condition has been received (NO in step S500), the process of step S500 is repeated.
- step S500 When a report indicating that a report indicating that the predetermined condition is satisfied is received from any UE 100 (YES in step S500), the HeNB 200 determines that the handover request is from the notification source UE 100, and the target A handover process is executed with the other HeNB 200 (step S502). Subsequently, the HeNB 200 determines whether a Path_Switch_Request has been received from another HeNB 200 (target HeNB) that has performed the handover process (step S504). If Path_Switch_Request has not been received (NO in step S504), the process of step S504 is repeated.
- target HeNB another HeNB 200
- the HeNB 200 transmits a UE_Context_Release command to the source HeNB_GW (step S506). Subsequently, the HeNB 200 determines whether or not UE_Context_Release_Complete is received from the source HeNB_GW (step S508). If UE_Context_Release_Complete has not been received (NO in step S508), the process of step S508 is repeated.
- the HeNB 200 updates the management information (UE_context) corresponding to the handed over UE 100 held in the own station (step S510). Subsequently, HeNB 200 transmits UE_Context_Release_Indication to MME 400 (sequence SQ512). Then, a series of processing ends.
- the management information corresponding to the handed over UE 100 held by the source HeNB in the own station may be updated.
- the fifth embodiment in addition to the same functions and effects as those of the third embodiment, the fourth embodiment, or the modification of the fourth embodiment described above, the following functions and effects are provided. That is, when viewed from the MME 400, it is possible to explicitly detect that the management information has been updated in the source HeNB and the source HeNB_GW. Therefore, consistency between the management by the MME 400 and the source HeNB and the source HeNB_GW can be maintained.
- Embodiment 6 In the above-described first to fifth embodiments, an example has been described in which the management information held by the source HeNB_GW is updated by the source HeNB leading the process. On the other hand, in Embodiment 6 described below, an example in which the MME 400 notifies an opportunity for updating the management information held by the source HeNB_GW is shown.
- the MME 400 at the time of handover from the source HeNB to the target HeNB, notifies information for updating the management information (UE_context) held by the source HeNB_GW.
- the management information (UE_context) held by the source HeNB is updated according to a conventional procedure. That is, the MME 400 associates with the UE 100 independently from the notification that the source HeNB has updated the management information in response to the movement of the UE 100 from the cell area provided by the source HeNB to the cell area provided by the target HeNB.
- a command for updating the received management information is transmitted to the gateway (source HeNB_GW) that manages the source HeNB.
- FIG. 19 is a sequence diagram showing a procedure for handover in the communication system according to the sixth embodiment of the present invention.
- the procedure shown in FIG. 19 differs from the procedure shown in FIG. 5 in that, when the MME 400 receives Path_Switch_Request, a message for updating the management information (UE_context) held by the source HeNB_GW is transmitted. That is, in the communication system according to the sixth embodiment, MME 400 has means for updating management information held by source HeNB_GW.
- a handover process between the UE 100, the source HeNB, and the target HeNB is executed (sequence SQ100).
- the target HeNB transmits Path_Switch_Request for updating the routing information of data to the UE 100 to the MME 400 (sequence SQ102).
- MME 400 updates the routing information of the local station and transmits Path_Switch_Request_ACK indicating reception of Path_Switch_Request to target HeNB (sequence SQ104).
- the target HeNB When the target HeNB receives the Path_Switch_Request_ACK, the target HeNB transmits the Path_Switch_Request to the source HeNB (sequence SQ106). When receiving the Path_Switch_Request, the source HeNB releases the management information (UE_text) corresponding to the handed over UE 100 held by itself (sequence SQ110).
- UE_text management information
- the MME 400 transmits UE_Context_Release_Request for updating the management information (UE_context) held by the source HeNB_GW to the source HeNB_GW following the transmission of the above-described Path_Switch_Request_ACK (sequence SQ109).
- the UE_Context_Release_Request includes information for specifying the UE 100 that has moved out of the cell area provided by the source HeNB connected to the source HeNB_GW.
- the source HeNB_GW When the source HeNB_GW receives the UE_Context_Release_Request, the source HeNB_GW releases the management information (UE_context) corresponding to the handed over UE 100 held by itself (sequence SQ112).
- the source HeNB_GW transmits UE_Context_Release_Complete indicating that the management information corresponding to the handed over UE 100 held by the own station has been completed to the MME 400 (sequence SQ113).
- the transmission of the response message indicating the update (release) of the management information by the source HeNB_GW to the MME 400 may be omitted.
- FIG. 20 is a flowchart showing a procedure in the source HeNB in the communication system according to the sixth embodiment of the present invention.
- HeNB 200 determines whether a report indicating that a predetermined condition has been satisfied is received from any UE 100 residing in the cell area provided by the own station (step S600). ). Since this predetermined condition has been described in the first embodiment, detailed description thereof will not be repeated. If no report has been received from any UE 100 that a predetermined condition has been received (NO in step S600), the process of step S600 is repeated.
- step S600 When a report indicating that a report indicating that the predetermined condition is satisfied is received from any UE 100 (YES in step S600), the HeNB 200 determines that the handover request is received from the UE 100 that is the notification source, and the target A handover process is executed with the other HeNB 200 (step S602). Subsequently, the HeNB 200 determines whether a Path_Switch_Request has been received from another HeNB 200 (target HeNB) that has performed the handover process (step S604). If Path_Switch_Request has not been received (NO in step S604), the process of step S604 is repeated.
- target HeNB another HeNB 200
- the HeNB 200 updates the management information (UE_context) corresponding to the handed over UE 100 held in the local station (step S606). Then, a series of processing ends.
- the handover operation of UE 100 is under the control of the target HeNB by the procedure related to Path_Switch_Request. Therefore, even if MME 400 executes a procedure independent of this procedure, the management information of source HeNB_GW Updates can be made reliably. Thereby, MME400 can update the management information (UE_context) which source HeNB_GW holds reliably.
- the procedure according to the sixth embodiment can be easily implemented because there are few changes to the handover procedure in the conventional LTE macro cell.
- the present embodiment it is possible to reduce the load shared by the MME by causing the source HeNB to share a part of the load. Therefore, even when a plurality of UEs are handed over at the same time, the source HeNBs corresponding to the UEs are distributed and processed, so that overall efficiency can be improved.
- the management information held in the management apparatus can be updated more quickly. Furthermore, the management information held by the source HeNB_GW can be updated more quickly.
- the source HeNB detects that the UE has been handed over before the management apparatus (MME), a series of procedures can be completed at a higher speed.
- MME management apparatus
- HeNBs small evolved radio base stations
- eNB normal evolved base station
- a communication method according to an aspect of the present invention includes several preferred forms as follows.
- the gateway transmits a command to the gateway to update management information associated with the mobile station whose management entity has been changed from the first base station to the second base station, Of the management information held by the own station, the management information associated with the mobile station is updated.
- the first base station has updated the management information associated with the mobile station whose management entity has been changed from the first base station to the second base station, among the management information held by the first base station Later, a command for updating the management information associated with the mobile station is transmitted to the gateway.
- the first base station responds to a notification from the gateway that the management information associated with the mobile station whose management entity has been changed from the first base station to the second base station has been updated.
- the management information associated with the mobile station is updated among the management information held by the own station.
- the gateway Preferably, after the first base station transmits a command to the gateway to update management information associated with the mobile station whose management entity has been changed from the first base station to the second base station, Wait for notification that the management information from the gateway has been updated.
- the first base station responds to the notification from the gateway that the management information associated with the mobile station whose management entity has been changed from the first base station to the second base station has been updated. Then, the management information update is transmitted to the management apparatus.
- a communication system provides a mobile station, a management device that manages the position of the mobile station, a first cell area, and a mobile station in the first cell area.
- a first base station that holds management information, and is arranged between the first base station and the management device;
- a gateway that holds management information for managing mobile stations in the cell area, and a second base station that provides the second cell area.
- the first base station receives management information associated with the mobile station from among the management information held by itself. Update.
- the management device sends a response to the mobile station independently of the notification that the first base station has updated the management information.
- a command for updating the associated management information is transmitted to the gateway.
- a management device that manages the position of a mobile station, first and second base stations, and a gateway that is disposed between the first base station and the management device.
- a communication method in a communication system provided. The communication method is held by the first base station in response to the movement of the mobile station from the first cell area provided by the first base station to the second cell area provided by the second base station.
- the management device Independently of the notification that the station has updated the management information, a command for updating the management information associated with the mobile station is transmitted to the gateway.
- 1 communication system 100 mobile station (UE), 102, 202, 302 central processing unit, 106, 206 signal processing unit, 112, 212 wireless transmission unit, 114, 214 transmission antenna, 116, 216 wireless reception unit, 118, 218 Receiving antenna, 120 display unit, 122 microphone, 124 speaker, 126 input unit, 130 housing, 200 small evolved base station (HeNB), 204 handover logic, 205 interface logic, 208, 308 storage unit, 210, 320 Upper network interface, 222 control interface, 250 cell area, 300 gateway, 304 management logic, 322-1, 322-2, ..., 322-n lower network interface, 400 MME 500 core network.
- HeNB small evolved base station
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
まず、本発明の実施の形態が適用される通信システムの典型例について説明する。
次に、図1に示す通信システム1を構成する各装置について説明する。
まず、本実施の形態に従う通信システム1において利用されるUE100の構成について説明する。図2は、本発明の実施の形態に従う移動局(UE)100の概略構成を示すブロック図である。
次に、本実施の形態に従う通信システム1において利用されるHeNB200の構成について説明する。図3は、本発明の実施の形態に従う基地局(HeNB)200の概略構成を示すブロック図である。
次に、本実施の形態に従う通信システム1において利用されるゲートウェイ300の構成について説明する。図4は、本発明の実施の形態に従うゲートウェイ300の概略構成を示すブロック図である。
本実施の形態に従う通信システム1において利用されるMME400の構成については、図4に示すゲートウェイ300の構成とほぼ同様であるので、詳細な説明は繰返さない。但し、MME400においては、管理情報を保持する記憶部308を設ける必要はない。
まず、図1に示すようなハンドオーバーに係る課題について説明する。図1に示す例では、UE100が、ゲートウェイ300に接続されているHeNB200-1が提供するセルエリア250-1からHeNB200-2が提供するセルエリア250-2へ移動する例を示す。ここで、HeNB200-2は、ゲートウェイ300に接続されず、MME400に直接接続されている。
上述したように、LTE方式またはLTE-A方式に係る現行の規格では、ゲートウェイによって管理されているHeNB(ソースHeNB)からゲートウェイによって管理されていない別のHeNB(ターゲットHeNB)へハンドオーバーした場合に、ソースHeNBを管理するソースHeNB_GWが保持する管理情報(UE_context)を更新する方法は定められていない。ゲートウェイが保持するUE100の管理情報(UE_context)を解放しないと、ゲートウェイは、常にUE100に関する情報を管理することになる。UE100が多数存在する場合には、ゲートウェイ300の保持する管理情報が膨大になり処理負荷が大きくなる。また、ゲートウェイ300に要求されるリソース(メモリ容量など)も大きくなり、コストアップにつながる。そのため、ゲートウェイ300では、必要な管理情報のみを保持し、不要になった管理情報は迅速に解放する必要がある。
実施の形態1に従う通信システムにおいては、ソースHeNBからターゲットHeNBへのハンドオーバー時に、ソースHeNBが主導的に処理を行なうことで、ソースHeNB_GWが保持する管理情報(UE_context)を更新する。すなわち、ソースHeNBは、ソースHeNBが提供するセルエリアからターゲットHeNBが提供するセルエリアへのUE100の移動に応答して、自局が保持する管理情報のうち当該UE100に関連付けられた管理情報を更新するとともに、当該UE100に関連付けられた管理情報を更新するための指令を、自局を管理するゲートウェイ(ソースHeNB_GW)へ送信する。
実施の形態2に従う通信システムにおいては、実施の形態1と同様に、ソースHeNBからターゲットHeNBへのハンドオーバー時に、ソースHeNBが主導的に処理を行なうことで、ソースHeNB_GWが保持する管理情報(UE_context)を更新する。すなわち、ソースHeNBは、ソースHeNBが提供するセルエリアからターゲットHeNBが提供するセルエリアへのUE100の移動に応答して、自局が保持する管理情報のうち当該UE100に関連付けられた管理情報を更新するとともに、当該UE100に関連付けられた管理情報を更新するための指令を、自局を管理するゲートウェイ(ソースHeNB_GW)へ送信する。
実施の形態3に従う通信システムにおいては、実施の形態1と同様に、ソースHeNBからターゲットHeNBへのハンドオーバー時に、ソースHeNBが主導的に処理を行なうことで、ソースHeNB_GWが保持する管理情報(UE_context)を更新する。すなわち、ソースHeNBは、ソースHeNBが提供するセルエリアからターゲットHeNBが提供するセルエリアへのUE100の移動に応答して、自局が保持する管理情報のうち当該UE100に関連付けられた管理情報を更新するとともに、当該UE100に関連付けられた管理情報を更新するための指令を、自局を管理するゲートウェイ(ソースHeNB_GW)へ送信する。
実施の形態4に従う通信システムにおいては、実施の形態1と同様に、ソースHeNBからターゲットHeNBへのハンドオーバー時に、ソースHeNBが主導的に処理を行なうことで、ソースHeNB_GWが保持する管理情報(UE_context)を更新する。すなわち、ソースHeNBは、ソースHeNBが提供するセルエリアからターゲットHeNBが提供するセルエリアへのUE100の移動に応答して、自局が保持する管理情報のうち当該UE100に関連付けられた管理情報を更新するとともに、当該UE100に関連付けられた管理情報を更新するための指令を、自局を管理するゲートウェイ(ソースHeNB_GW)へ送信する。
図15に示す実施の形態4においては、ソースHeNBは、自局で保持しているハンドオーバーしたUE100に対応する管理情報(UE_context)を更新した後に、管理情報を更新するための命令であるUE_Context_ReleaseコマンドをソースHeNB_GWへ送信する。これに代えて、ソースHeNBは、管理情報を更新するための命令であるUE_Context_ReleaseコマンドをソースHeNB_GWへ送信した後に、自局で保持しているハンドオーバーしたUE100に対応する管理情報を更新してもよい(図15の破線で示したブロック参照)。
実施の形態5に従う通信システムにおいては、実施の形態1と同様に、ソースHeNBからターゲットHeNBへのハンドオーバー時に、ソースHeNBが主導的に処理を行なうことで、ソースHeNB_GWが保持する管理情報(UE_context)を更新する。すなわち、ソースHeNBは、ソースHeNBが提供するセルエリアからターゲットHeNBが提供するセルエリアへのUE100の移動に応答して、自局が保持する管理情報のうち当該UE100に関連付けられた管理情報を更新するとともに、当該UE100に関連付けられた管理情報を更新するための指令を、自局を管理するゲートウェイ(ソースHeNB_GW)へ送信する。
上述の実施の形態1~5においては、ソースHeNBが主導的に処理を行なうことで、ソースHeNB_GWが保持する管理情報を更新する例を示した。これに対して、次に述べる実施の形態6においては、ソースHeNB_GWが保持する管理情報を更新するための契機をMME400が通知する例を示す。
本実施の形態は、LTE方式またはLTE-A方式のシステムにおいて、移動局(UE)が基地局(HeNB)と通信中に、他のHeNBへハンドオーバーしたときに、元のHeNB(ソースHeNB)を管理するゲートウェイ(ソースHeNB_GW)の保持する当該UEに関する管理情報を更新する提供する。
本発明のある局面に従う通信方法は、以下のようないくつかの好ましい形態を含む。
のセルエリア内の移動局を管理するための管理情報を保持するゲートウェイと、第2のセルエリアを提供する第2の基地局とを含む。第1の基地局は、移動局の管理主体が自局から第2の基地局へ変更されたことに応答して、自局が保持する管理情報のうち当該移動局に関連付けられた管理情報を更新する。管理装置は、第1のセルエリアから第2のセルエリアへの移動局の移動に応答して、第1の基地局が管理情報を更新したとの通知とは独立して、当該移動局に関連付けられた管理情報を更新するための指令をゲートウェイへ送信する。
Claims (9)
- 通信システムであって、
移動局と、
前記移動局の位置を管理する管理装置と、
第1のセルエリアを提供するとともに、前記第1のセルエリア内の移動局を管理するための管理情報を保持する第1の基地局と、
前記第1の基地局と前記管理装置との間に配置され、前記第1のセルエリア内の移動局を管理するための管理情報を保持するゲートウェイと、
第2のセルエリアを提供する第2の基地局とを備え、
前記第1の基地局は、前記移動局の管理主体が自局から前記第2の基地局へ変更されたことに応答して、自局が保持する前記管理情報のうち当該移動局に関連付けられた管理情報を更新するとともに、当該移動局に関連付けられた管理情報を更新するための指令を前記ゲートウェイへ送信する、通信システム。 - 前記第1の基地局は、その管理主体が第1の基地局から前記第2の基地局へ変更された移動局に関連付けられた管理情報を更新するための指令を前記ゲートウェイへ送信した後に、自局が保持する管理情報のうち当該移動局に関連付けられた管理情報を更新する、請求項1に記載の通信システム。
- 前記第1の基地局は、自局が保持する管理情報のうち、その管理主体が前記第1の基地局から前記第2の基地局へ変更された移動局に関連付けられた管理情報を更新した後に、当該移動局に関連付けられた管理情報を更新するための指令を前記ゲートウェイへ送信する、請求項1に記載の通信システム。
- 前記第1の基地局は、その管理主体が前記第1の基地局から前記第2の基地局へ変更された移動局に関連付けられた管理情報が更新されたとの前記ゲートウェイからの通知に応答して、自局が保持する管理情報のうち当該移動局に関連付けられた管理情報を更新する、請求項1に記載の通信システム。
- 前記第1の基地局は、その管理主体が前記第1の基地局から前記第2の基地局へ変更された移動局に関連付けられた管理情報を更新するための指令を前記ゲートウェイへ送信した後に、ゲートウェイからの管理情報が更新されたとの通知を待つ、請求項1に記載の通信システム。
- 前記第1の基地局は、その管理主体が前記第1の基地局から前記第2の基地局へ変更された移動局に関連付けられた管理情報が更新されたとの前記ゲートウェイからの通知に応答して、管理情報の更新を前記管理装置へ送信する、請求項5に記載の通信システム。
- 移動局の位置を管理する管理装置と、第1および第2の基地局と、前記第1の基地局と前記管理装置との間に配置されたゲートウェイとを備えた通信システムにおける通信方法であって、
前記第1の基地局が提供する第1のセルエリアから前記第2の基地局が提供する第2のセルエリアへの前記移動局の移動に応答して、前記第1の基地局が保持する当該移動局に関連付けられた管理情報を更新するステップと、
前記移動局の管理主体が前記第1の基地局から前記第2の基地局へ変更されたことに応答して、前記第1の基地局が当該移動局に関連付けられた管理情報を更新するための指令を前記ゲートウェイへ送信するステップとを備える、通信方法。 - セルエリアを提供する基地局であって、前記基地局は、セルエリア内の移動局を管理するための管理情報を保持するゲートウェイに接続されており、前記ゲートウェイは、移動局の位置を管理する管理装置と接続されており、
前記セルエリア内の移動局を管理するための管理情報を保持するための手段と、
前記移動局の管理主体が自局から他の基地局へ変更されたことに応答して、保持する前記管理情報のうち当該移動局に関連付けられた管理情報を更新するとともに、当該移動局に関連付けられた管理情報を更新するための指令を前記ゲートウェイへ送信するための手段とを備える、基地局。 - 移動局の位置を管理する管理装置であって、前記管理装置には、ゲートウェイを介して第1の基地局が接続されるとともに、第2のセルエリアを提供する第2の基地局が直接接続され、
前記第1の基地局は、第1のセルエリアを提供するとともに、前記第1のセルエリア内の移動局を管理するための管理情報を保持し、
前記ゲートウェイは、前記第1のセルエリア内の移動局を管理するための管理情報を保持し、
前記第1の基地局は、前記移動局の管理主体が自局から前記第2の基地局へ変更されたことに応答して、自局が保持する前記管理情報のうち当該移動局に関連付けられた管理情報を更新し、
前記管理装置は、前記第1のセルエリアから前記第2のセルエリアへの前記移動局の移動に応答して、前記第1の基地局が管理情報を更新したとの通知とは独立して、当該移動局に関連付けられた管理情報を更新するための指令を前記ゲートウェイへ送信するための手段を備える、管理装置。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/128,134 US20140120917A1 (en) | 2011-07-22 | 2012-07-19 | Communication system, communication method, base station , and management device |
BR112014001379A BR112014001379A2 (pt) | 2011-07-22 | 2012-07-19 | sistema de comunicações, método de comunicações, estação base, e dispositivo de gerenciamento |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2011-160866 | 2011-07-22 | ||
JP2011160866A JP5665680B2 (ja) | 2011-07-22 | 2011-07-22 | 通信システム、通信方法、基地局、および、管理装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013015188A1 true WO2013015188A1 (ja) | 2013-01-31 |
Family
ID=47601036
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2012/068315 WO2013015188A1 (ja) | 2011-07-22 | 2012-07-19 | 通信システム、通信方法、基地局、および、管理装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20140120917A1 (ja) |
JP (1) | JP5665680B2 (ja) |
BR (1) | BR112014001379A2 (ja) |
WO (1) | WO2013015188A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11344299B2 (en) | 2015-09-23 | 2022-05-31 | Cilag Gmbh International | Surgical stapler having downstream current-based motor control |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9681415B2 (en) * | 2012-09-25 | 2017-06-13 | Nec Corporation | Gateway device, mobile communication system, and paging method |
WO2015115356A1 (ja) * | 2014-01-31 | 2015-08-06 | 京セラ株式会社 | 通信制御方法及び基地局 |
US9900756B2 (en) * | 2015-04-24 | 2018-02-20 | Kony, Inc. | Dynamically updating policy controls for mobile devices and applications via policy notifications |
US9949185B2 (en) * | 2015-10-08 | 2018-04-17 | At&T Intellectual Property I, L.P. | Facilitating mobile service anchor management |
CN106936488B (zh) * | 2015-12-31 | 2021-02-12 | 华为技术有限公司 | 一种csi接收方法及接入网设备 |
WO2020030712A1 (en) * | 2018-08-08 | 2020-02-13 | Sony Corporation | Infrastructure equipment, communications devices and methods |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010059099A1 (en) * | 2008-11-21 | 2010-05-27 | Telefonaktiebolaget L M Ericsson (Publ) | Network gateway configured to provide a handover, converting and routing function |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010059100A1 (en) * | 2008-11-21 | 2010-05-27 | Telefonaktiebolaget L M Ericsson (Publ) | Gateway configured to provide a handover, converting and routing function |
US9801102B2 (en) * | 2010-04-28 | 2017-10-24 | Samsung Electronics Co., Ltd. | Method and apparatus for handover using X2 interface based on closed subscriber group in mobile communication system |
CN102421198B (zh) * | 2010-09-28 | 2016-03-30 | 中兴通讯股份有限公司 | 一种将更新信息通知核心网的方法及系统 |
US8937924B2 (en) * | 2010-09-28 | 2015-01-20 | Blackberry Limited | Releasing connections with local GW when UE moves out of residential/enterprise network coverage |
GB2488167A (en) * | 2011-02-18 | 2012-08-22 | Nec Corp | Handover procedure in a home base station connected to a home base station gateway |
US9131424B2 (en) * | 2011-03-25 | 2015-09-08 | Lg Electronics Inc. | Method and apparatus for releasing user equipment context in wireless communication system |
EP2727401A1 (en) * | 2011-07-01 | 2014-05-07 | InterDigital Patent Holdings, Inc. | Method and apparatus for supporting local ip access -lipa- mobility |
-
2011
- 2011-07-22 JP JP2011160866A patent/JP5665680B2/ja active Active
-
2012
- 2012-07-19 BR BR112014001379A patent/BR112014001379A2/pt not_active IP Right Cessation
- 2012-07-19 US US14/128,134 patent/US20140120917A1/en not_active Abandoned
- 2012-07-19 WO PCT/JP2012/068315 patent/WO2013015188A1/ja active Application Filing
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2010059099A1 (en) * | 2008-11-21 | 2010-05-27 | Telefonaktiebolaget L M Ericsson (Publ) | Network gateway configured to provide a handover, converting and routing function |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11344299B2 (en) | 2015-09-23 | 2022-05-31 | Cilag Gmbh International | Surgical stapler having downstream current-based motor control |
Also Published As
Publication number | Publication date |
---|---|
JP2013026890A (ja) | 2013-02-04 |
BR112014001379A2 (pt) | 2017-03-01 |
US20140120917A1 (en) | 2014-05-01 |
JP5665680B2 (ja) | 2015-02-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3624493B1 (en) | Handover method, apparatus and system | |
JP5665680B2 (ja) | 通信システム、通信方法、基地局、および、管理装置 | |
KR102284317B1 (ko) | 통신 방법, 코어 네트워크 디바이스 및 액세스 네트워크 디바이스 | |
WO2022257549A1 (zh) | 网络切片方法、设备及存储介质 | |
JP6343673B2 (ja) | 小型基地局環境で情報インタラクションを行う方法、基地局、及びモビリティ管理エンティティ | |
US20170019945A1 (en) | Dual Connectivity Re-Establishment | |
JP5348340B2 (ja) | 移動通信システムおよび通信制御方法 | |
JP6745346B2 (ja) | 無線通信方法、及び装置 | |
US20150172964A1 (en) | Ue context release method, enb and home enb gateway | |
TW201836386A (zh) | 切換方法、網路設備和終端設備 | |
JP2012186814A (ja) | セルフバックホールセルにおけるハンドオーバ中のデータ送信 | |
CN110225529A (zh) | 主基站及其方法 | |
US9756670B2 (en) | Method and system for notifying transport layer address | |
KR20160026503A (ko) | 무선 통신 시스템에서 단말이 서비스 연결을 유지하는 장치 및 방법 | |
JP2023535969A (ja) | 論理チャネルlch設定方法、通信装置、および通信システム | |
EP3282759B1 (en) | Cross-menb switching method and apparatus and base station | |
JP2020511844A (ja) | 通信方法、セカンダリネットワークノード及び端末 | |
CN112105092A (zh) | 双连接重建立中数据的处理方法及装置 | |
JP5671139B2 (ja) | 通信制御方法及びホーム基地局 | |
CN102273260B (zh) | 用于单个无线电语音呼叫连续性的源标识的方法、装置和设备 | |
JPWO2014106936A1 (ja) | 発明の名称:ユーザ端末、プロセッサ及び基地局 | |
WO2018207368A1 (ja) | 無線通信システム、セカンダリノード及び無線通信方法 | |
WO2022206393A1 (zh) | 通信方法及装置 | |
JPWO2013001611A1 (ja) | 通信制御方法及びホーム基地局 | |
JP2011166372A (ja) | 移動通信方法及び無線基地局 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 12816911 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14128134 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112014001379 Country of ref document: BR |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 12816911 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 112014001379 Country of ref document: BR Kind code of ref document: A2 Effective date: 20140121 |