US2017041832A1PendingUtilityA1
Mobile communication system, base station, higher-order apparatus, gateway apparatus, communication method, and program
Est. expiryAug 12, 2029(~3.1 yrs left)· nominal 20-yr term from priority
H04W 88/16H04W 84/045H04W 88/08H04W 36/38H04W 36/0064H04W 36/08H04W 36/0016H04W 36/0022H04W 36/0055
55
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
A mobile communication system includes a first Home Node B (HNB); a second HNB; and a HNB gateway (HNB-GW) that is connected to a core network, wherein the first HNB is configured to communicate with a user equipment (UE) before a relocation of intra HNB-GW in which the UE is relocated from the first HNB to the second HNB, wherein the second HNB is configured to communicate with a user equipment (UE) after the relocation and send Iu-UP Initialization comprising an RFCI information to the HNB-GW during the relocation, and wherein the HNB-GW is configured to receive the Iu-UP Initialization.
Claims
exact text as granted — not AI-modifiedWhat is claimed:
1 . A mobile communication system comprising:
a first Home Node B (HNB); a second HNB; and a HNB gateway (HNB-GW) that is connected to a core network, wherein the first HNB comprises a transceiver configured to communicate with a user equipment (UE) and send a first message, comprising Radio Access Bearer sub-Flow Combination Indicator (RFCI) information, to the HNB-GW during an intra HNB-GW relocation in which the UE is relocated from the first HNB to the second HNB, wherein the HNB-GW comprises a transceiver configured to receive the first message and to send a second message, comprising the RFCI information, to the second HNB, and wherein the second HNB comprises a transceiver configured to communicate with the UE and to receive the second message.
2 . A mobile communication system according to claim 1 ,
wherein the first message is a message that requests relocation.
3 . The mobile communication system according to claim 1 ,
wherein the second message is a relocation request message.
4 . The mobile communication system according to one of claim 1 ,
wherein the first message is a Direct Transfer message.
5 . The mobile communication system according to one of claim 1 ,
wherein the second message is a Direct Transfer message.
6 . The mobile communication system according to one of claim 1 ,
wherein the transceiver of the second HNB is configured to receive the RFCI information without execution of an Iu-UP Initialization procedure.
7 . The mobile communication system according to one of claim 1 ,
wherein the transceiver of the second HNB is further configured to send a Relocation Complete message to the HNB-GW.
8 . The mobile communication system according to one of claim 1 ,
wherein the transceiver of the first HNB is further configured to send an RRC Reconfiguration message to the UE during the relocation and the transceiver of the second HNB is further configured to receive an RRC Reconfiguration Complete message from the UE during the relocation.
9 . A second Home Node B (HNB), the second HNB comprising a transceiver configured to:
communicate with a user equipment (UE); and receive a message comprising Radio Access Bearer sub-Flow Combination Indicator (RFCI) information from a HNB gateway (HNB-GW) that is connected to a core network, during an intra HNB-GW relocation in which the UE is relocated from a first HNB to the second HNB.
10 . The second HNB according to claim 9 ,
wherein the message is a message that requests relocation.
11 . The second HNB according to claim 9 ,
wherein the message is a relocation request message.
12 . The second HNB according to claim 9 ,
wherein the message is a Direct Transfer message.
13 . The second HNB according to claim 9 ,
wherein the message is a Direct Transfer message.
14 . The second HNB according to claim 9 , wherein the transceiver is configured to receive the RFCI information without execution of an Iu-UP Initialization procedure.
15 . The second HNB according to one of claim 9 , wherein the transceiver is further configured to send a Relocation Complete message to the HNB-GW.
16 . The second HNB according to claim 9 , wherein the transceiver is further configured to receive an RRC Reconfiguration Complete message from the UE during the relocation, and
wherein an RRC Reconfiguration message is sent from the first HNB to the UE during the relocation.
17 . A Home Node B gateway (HNB-GW) that is connected to a core network, the HNB-GW comprising:
a transceiver configured to receive a first message, comprising Radio Access Bearer sub-Flow Combination Indicator (RFCI) information, from a first HNB during an intra HNB-GW relocation in which the UE is relocated from the first HNB to a second HNB; wherein the transceiver is further configured to send a second message, comprising the RFCI information, to the second HNB.
18 . The HNB-GW according to one of claim 17 ,
wherein the transceiver is configured to send the second message comprising the RFCI information to the second HNB without execution of an Iu-UP Initialization procedure
19 . The HNB-GW according to claim 17 , wherein the transceiver is further configured to receive a Relocation Complete message from the second HNB.
20 . A user equipment (UE), the UE comprising:
a transceiver configured to communicate with a first Home Node B (HNB) and a second HNB; a controller comprising a memory storing instructions and a processor configured to execute the instructions and thereby trigger an intra-HNB gateway (HNB-GW) relocation in which the UE is relocated from the first HNB to the second HNB; wherein the transceiver is further configured to receive a Radio Resource Control (RRC) Reconfiguration message from the first HNB during the relocation, and to send an RRC Reconfiguration Complete message to the second HNB during the relocation, wherein the HNB-GW is connected to a core network, and wherein, during the relocation, a first message comprising Radio Access Bearer Sub-Flow Combination Indicator (RFCI) information is sent from the first HNB to the HNB-GW and a second message comprising the RFCI information is sent from the HNB-GW to the second HNB.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.