Method and system for realizing resource management control in switching process
A switching process and resource management technology, applied in the field of resource management control, can solve problems such as switching failure
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
Embodiment 1
[0131] Embodiment 1 is based on the premise that the RG works in routing mode, that is to say, the CPE address is allocated to the RG, and it can be determined whether the H(e)NBs share a backhaul according to whether the CPE addresses are the same. The main idea of Embodiment 1 is: when the H(e)NB is powered on, it needs to obtain the IP address of the CPE, and when registering with the H(e)MS, report it to the H(e)MS, and the H(e)MS is the CPE H(e)NBs with the same address select the same H(e)NB GW / MME. When H(e)NB registers with H(e)NB GW / MME, it also carries the CPE address, so that H(e)NB GW can judge whether H(e)NB is connected to the same backhaul according to whether the CPE address is the same down, see Figure 4 .
[0132] When the UE switches between H(e)NBs under the same backhaul, both H(e)NB GW and MME can perceive it. At this time, H(e)NB GW or MME accepts the resource request from the target side (even if the Insufficient), to complete the switch, see Fi...
Embodiment 2
[0164] Embodiment 2 is based on the premise that the RG works in routing mode. The basic idea and mechanism are basically the same as in Embodiment 1. The difference in support lies in the way of transmitting the CPE address. The following describes the differences accordingly:
[0165] 501. Same as 401.
[0166]502. H(e)NB-1 establishes an IPsec tunnel between H(e)NB-1 and SeGW. (No CPE IP address sent, or even if sent, H(e)NB-1 does not process / perceive).
[0167] 503. Establish / update a binding relationship between the SeGW and the H(e)NB PF.
[0168] 503a. Triggered by step 502, SeGW sends the address of H(e)NB-1 (assigned to it in step 502, prior art) and CPE address to H(e)MS (the message passes between SeGW and H(e)MS The interface between is newly added for the present invention). This step happens before 504.
[0169] 504. H(e)NB-1 registers with H(e)MS, H(e)MS selects H(e)NB GW / MME for H(e)NB-1, and feeds back its IP address to H(e)MS )NB-1.
[0170] After 50...
Embodiment 3
[0191] The above two embodiments are based on the premise that the RG works in routing mode. At this time, the CPE address is the RG address, and the H(e)NB connected to the same RG (that is: belonging to the same backhual) reports to H(e) ) The CPE addresses of the MS and the H(e)NBGW / MME are the same, and the H(e)NB GW judges whether multiple H(e)NBs are under the same backhaul based on the same CPE addresses.
[0192] When the RG works in bridge mode, the CPE address is assigned to the H(e)NB, and even if multiple H(e)NBs connected to the same RG share a backhaul, their CPE addresses are different. At this time, the H(e)NB GW / MME cannot judge whether these H(e)NBs are under the same backhaul based on the CPE address. Here we make the following corrections and enhancements, which are applied to the bridge mode.
[0193] After the H(e)NB registers with the H(e)MS, the H(e)MS queries the fixed network (for example, the fixed network address server) for the backhual information...
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More 


