US20110314162A1 - Method for establishing connection by hnb - Google Patents
Method for establishing connection by hnb Download PDFInfo
- Publication number
- US20110314162A1 US20110314162A1 US12/673,223 US67322308A US2011314162A1 US 20110314162 A1 US20110314162 A1 US 20110314162A1 US 67322308 A US67322308 A US 67322308A US 2011314162 A1 US2011314162 A1 US 2011314162A1
- Authority
- US
- United States
- Prior art keywords
- hnb
- mme
- csg
- omc
- message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/02—Arrangements for optimising operational condition
-
- 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
- H04W36/0061—Transmission or use of information for re-establishing the radio link of neighbour cell information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
- H04W84/042—Public Land Mobile systems, e.g. cellular systems
- H04W84/045—Public Land Mobile systems, e.g. cellular systems using private Base Stations, e.g. femto Base Stations, home Node B
Definitions
- the present invention generally relates to communication technology, especially to a method for accessing a network by an HNB (home Node B).
- HNB home Node B
- FIG. 1 A system structure of SAE is illustrated in FIG. 1 .
- the system structure of SAE in FIG. 1 is described as following.
- EUTRAN also called ENB
- ENB is a radio access network of the LTE SAE, for providing interface through which an LTE mobile station accesses the radio network.
- EUTRAN connects to a mobility management entity (MME) 103 and a user plane entity Serving Gateway 104 in the mobile station.
- MME mobility management entity
- Serving Gateway primarily provides a function of user plane.
- An interface S 1 -MME is adapted for establishing radio access bearer, forwarding messages from UE to MME through a wireless access network.
- the combination of 103 MME and 104 Serving Gateway is similar to the original 106 SGSN (general packet radio service (GPRS) supporting node). It is possible that both MME and Serving Gateway locate at the same physical entity.
- 105 PDN Gateway is adapted for the functions like accounting, legally monitoring, etc. And it is possible that both the Serving Gateway and the PDN Gateway locate at the same physical entity.
- 106 SGSN provides routing for data transmission in existing UMTS. An existing SGSN finds a corresponding gateway GPRS supporting node (GGSN) according to an access point name (APN).
- GGSN gateway GPRS supporting node
- API access point name
- HSS is a home subscription sub-system for the UE and is adapted for storing user information such as the current location of UE, address of the serving node, security information on the user, activated packet data protocol (PDP) context for the UE and so on.
- PDP packet data protocol
- 108 PCRF provides QoS policy and accounting rules through interface S 7 .
- a user data stream reaches the 104 Serving Gateway through 105 PDN Gateway. Then, through the GPRS tunnel protocol (GTP) channel, data is sent by the Serving Gateway to the ENB where the UE locates in, and now it is sent by the ENB to corresponding UE.
- GTP GPRS tunnel protocol
- HNB refers to a Node B applied in a home. It also can be applied in such site as a university, a company and so on. HNB is a plug and play device. Difference between an HNB and a general macro node B is that: in general not all UEs can access an HNB. For example, only the UEs in a user's home or that are allowed to access the HNB can access the corresponding HNB. And for the HNB in a company, only the company's staff and its allowed partners can access the HNB.
- the HNB group (e.g., the HNB in a company) bearing the same access subscriber cluster is called CSG (closed subscriber group).
- No interface X 2 (interface between Node Bs in SAE) exists between general HNBs (e.g., the HNBs in homes) or between an HNB and a macro Node B.
- a UE switches between HNBs or between an HNB and a macro Node B.
- a UE For an HNB applied in a company or university or the like, a UE frequently moves between two HNBs in the same company. In this case, the switch is always implemented through interface S 1 so that great delay causes and efficiency is very poor. In addition, information such as radio resource management and so on can not be exchanged between two HNBs in the same company so that resources can not be utilized effectively.
- a method for establishing a connection by a HNB comprising steps of:
- the HNB transmitting an “attachment request” message to an operation and maintenance center (OMC);
- OMC operation and maintenance center
- the OMC transmitting an “attachment response” message to the HNB;
- a UE can switch between HNBs in the same CSG through interface X 2 . Meanwhile, such information as the radio resource management and so on can be exchanged between two HNBs.
- FIG. 1 shows a network structure of SAE
- FIG. 2 shows a process that a connection is established for HNB in embodiment 1 of present invention
- FIG. 3 shows the process that a connection is established for HNB in embodiment 2 of present invention
- FIG. 4 shows an operation flows at HNB according to embodiment 1 and embodiment 2 respectively;
- FIG. 5 shows an operation flows at OMC according to embodiment 1 and embodiment 2 respectively;
- FIG. 6 shows an operation flows at MME according to embodiment 1 and embodiment 2 respectively.
- FIG. 7 shows a process of reconfiguring MME or S-GW.
- HNB 1 is a first HNB that accesses the network.
- HNB 1 transmits an “attachment request” message to the OMC.
- This message contains information on a location of the HNB.
- the “attachment request” message contains an identifier of the CSG to which the HNB belongs.
- the network assigns the CSG identifier to HNB (the first HNB or the first group of HNBs within the CSG) when HNB signs in, or knows the identifier of the CSG to which the HNB (not the first signed in group of HNBs in the CSG) belongs when HNB signs in.
- the process of selecting S-GW for HNB can be implemented by the MME connected to the HNB when data is transferred through the HNB. Therefore, the HNBs in the same CSG connect to the same S-GW. If it is necessary for the first HNB in the CSG to establish the user plane, MME selects an S-GW for the CSG according to such rules as to balance load or to reduce the possibility of changing S-GW when a UE moves, and so on.
- OMC transmits an “attachment response” message to the HNB.
- This message indicates the MME selected by the OMC for the HNB.
- this message indicates other HNBs necessary to establish X 2 connection and adjacent to the HNB.
- the message contains the frequency for using the HNB.
- the “attachment response” message contains the information on adjacent cells.
- the “attachment response” message contains a track area identifier (TAI) for the HNB.
- TAI track area identifier
- the “attachment response” message contains the identifier assigned to the HNB.
- the message contains an address of the S-GW that OMC selected for the HNB.
- HNB initiates a process to establish a connection with the MME indicated by the message.
- HNB transmits a “connection request” message to MME.
- the message contains the information on “cells which are overlapped with HNB or CSG”.
- the message contains an information element of the identifier of the TAI where HNB locates in.
- the message contains the information element of the identifier of HNB.
- the message contains the information element of the identifier of the CSG where HNB locates.
- MME transmits a “connection response” message to HNB.
- Embodiment 2 of the present invention is illustrated in FIG. 3 . Following is detailed description to the figure. Detailed technical description for known components is omitted.
- HNB 1 and HNB 2 belong to the same CSG.
- HNB 1 has accessed the network.
- HNB 2 begins to accessing the network for a first time.
- HNB 2 transmits the “attachment request” message to the OMC.
- This message contains the information on the location of HNB 2 .
- the “attachment request” message contains the identifier of the CSG to which the HNB 2 belongs.
- the network knows the identifier of the CSG to which the HNB belongs when HNB signs in.
- Step 302 OMC selects an MME for the HNB. If the HNB is not the first to access the network in the CSG, the MME selected by OMC for other HNBs in this CSG is just the one that the HNB should connect to. In this embodiment, OMC assigns both the MME and the S-GW selected for HNB 1 to the HNB. Optionally, the address the HNB should be considered when OMC selects MME for the HNB. For example, if two HNBs that are in different countries but in the same company belong to the same CSG, they may not be able to connect to the same MME.
- OMC thinks that this HNB is the first one which accesses the network in the CSG and selects an MME for it according to rules such as balancing load or reducing possibility of changing MME when a UE moves, and so on.
- selection of S-GW for the HNB can be implemented by OMC according to the same rules on the selection of MME.
- OMC checks other HNBs in the CSG which need to establish X 2 connection with the HNB. And according to the CSG identifier, OMC checks other HNBs in the CSG which need to establish X 2 connection with the HNB.
- the addresses of the HNBs, as well as whether the HNBs share the same CSG or not, are considered when OMC checks other HNBs in the CSG which need to establish X 2 connection with the HNB.
- OMC checks other HNBs in the CSG which need to establish X 2 connection with the HNB For example, it is not necessary to establish interface X 2 between two HNBs if the two HNBs that are in different countries but in the same company belong to the same CSG. In this embodiment, for example, it is necessary to establish X 2 connection between HNB 1 and HNB 2 .
- the process of selecting S-GW for HNB can be implemented by the MME connected to the HNB when data is transferred through the HNB. Therefore, the HNBs in the same CSG connect to the same S-GW. If it is necessary for the first HNB in the CSG to establish the user plane, MME selects an S-GW for the CSG according to such rules as to balance load or to reduce the possibility of changing S-GW when a UE moves, and so on. If the HNB is not the first necessary to establish a user plane in the CSG, the S-GW selected by MME for other HNBS in this CSG is just the one that the HNB should connect to.
- OMC transmits the “attachment response” message to the HNB 2 .
- This message indicates the MME that the OMC selected for the HNB.
- the MME information included in the message may be the IP address of the MME.
- this message contains a list of other HNBs necessary to establish X 2 and adjacent to the HNB.
- the HNB list information included in the message is an IP address list for the HNB.
- the message contains a frequency for using the HNB.
- the “attachment response” message contains the information on adjacent cells.
- the “attachment response” message contains the track area identifier (TAI) for the HNB.
- the “attachment response” message contains the identifier assigned to the HNB.
- the message contains the address of the S-GW that OMC selected for the HNB.
- Step 304 HNB 2 initiates a process to establish a connection with the HNB indicated by the message.
- HNB 2 transmits the “connection request” message to the other HNB (e.g., HNB 1 ).
- HNB 1 transmits the “connection response” message to HNB 2 .
- HNB 2 initiates a process to establish a connection with the MME indicated by the message.
- HNB 2 transmits the “connection request” message to MME.
- the message contains the information on “cells which are overlapped with the HNB or CSG”.
- the message contains the information element of the identifier of the TAI where HNB locates.
- the message contains the information element of the identifier of HNB.
- the message contains the information element of the identifier of the CSG where HNB locates.
- MME transmits the “connection response” message to HNB 2 .
- step 304 and step 305 The sequence of performing step 304 and step 305 is not limited.
- HNB operation flow of HNB is illustrated in FIG. 4 .
- detailed technical description for known components is omitted.
- HNB transmits the “attachment request” message to the OMC. This message contains the information on the location of HNB. Optionally, the “attachment request” message contains the identifier of the CSG to which the HNB 2 belongs.
- HNB waits for the response message.
- HNB receives a “successful attachment response” message, it saves the information that is included in the message, such as information on MME and the information on other HNBs, TAI, the HNB identifier and so on.
- HNB initiates the process to establish a connection with the MME indicated by the message. HNB transmits the “connection request” message to MME.
- the message contains the information on “cells which are overlapped with the HNB or CSG”.
- the message contains the information element of the identifier of the TAI where HNB locates.
- the message contains the information element of the identifier of HNB.
- the message contains the information element of the identifier of the CSG where HNB locates.
- MME transmits the “connection response” message to HNB. 405
- HNB initiates the process to establish connections with other HNBs.
- HNB transmits the “connection request” to another HNB.
- An another HNB transmits the “connection response” message to the HNB.
- step 404 and step 405 The sequence of performing step 404 and step 405 is not limited.
- OMC receives messages.
- OMC receives the “attachment request” message from HNB, in 503 it saves HNB related information. And if the message contains the location information for HNB, OMC saves this information. And if the message contains the identifier of the CSG where the HNB belongs, OMC saves this information.
- OMC selects an MME for HNB in this CSG.
- OMC selects the MME according to either the address of HNB, or the rule to balance load or to reduce the possibility of changing MME when a UE moves, etc.
- OMC can select an S-GW for the HNB according to the same rule as on the selection of MME.
- Step 506 if HNB is not the first to access the network in the CSG, 507 OMC checks other HNBs in the CSG. 508 OMC transmits the “attachment response” message to the requesting HNB. And information on the MME OMC selected for HNB in this CSG is included in the message.
- the “attachment response” message contains the information on the S-GW selected by OMC for HNB in this CSG.
- the message contains the information on other HNBs in this CSG, such as the IP address list for the HNB.
- the message contains the identifier of the TAI where the HNB locates.
- the message contains the HNB identifier allocated to the HNB.
- the HNBs in the CSG are not far away from one another.
- two HNBs belong to the same CSG in different countries but in the same company, if no adjacent HNB accesses the network, OMC thinks that this HNB is the first one which accesses the network in the CSG and selects an MME for it according to such rules as to balance load or to reduce possibility of changing MME when a UE moves, and so on.
- OMC can select an S-GW for the HNB according to the same rule as on the selection of MME.
- OMC finds the other HNB is the one necessary to establish a X 2 connection with the HNB in the CSG according to not only the CSG ID. Meanwhile, it should consider the location of the HNB. For example, it is not necessary to establish interface X 2 between two HNBs if the two HNBs that are in different countries but in the same company belong to the same CSG.
- MME receives messages.
- MME saves the information which is included in this message, such as the information on “cells which is overlapped with the HNB or CSG”, the identifier of the TAI where HNB locates, the HNB identifier.
- 604 MME transmits the “connection response” message to HNB.
- FIG. 7 illustrates the process that OMC reconfigures CSG's MME or S-GW when overload or fault comes across the MME or the S-GW.
- Step 701 OMC finds that overload or fault comes across the MME or S-GW connected to a certain CSG.
- Step 702 OMC transmits a “reconfiguration request” message to the HNB in CSG.
- the information on the reconfigured MME or S-GW and the reason for the reconfiguration are included.
- the reconfiguration can be done to the IP address of the MME or the S-GW.
- the HNB that has received the “reconfiguration request” message transmits the “connection request” message to the new MME or S-GW.
- the “connection request” message sent to MME includes the information on “cells which are overlapped with the HNB or CSG”.
- the “connection request” message sent to MME contains the information element of the identifier of the TAI where HNB locates.
- the new MME or S-GW transmits the “connection response” message to the HNB.
- Step 704 the HNB transmits a “reconfiguration response” message to OMC.
- HNB initiates the process of releasing the connection with original MME or S-GW.
Abstract
Description
- The present invention generally relates to communication technology, especially to a method for accessing a network by an HNB (home Node B).
- A system structure of SAE is illustrated in
FIG. 1 . The system structure of SAE inFIG. 1 is described as following. - User Equipment 101 (hereinafter referred to as UE) is a terminal device used to receive data. 102 EUTRAN, also called ENB, is a radio access network of the LTE SAE, for providing interface through which an LTE mobile station accesses the radio network. Through interface S1, EUTRAN connects to a mobility management entity (MME) 103 and a user plane entity Serving Gateway 104 in the mobile station. 103 MME is adapted for managing mobile context, session context for the UE, and holding user information on security. 104 Serving Gateway primarily provides a function of user plane. An interface S1-MME is adapted for establishing radio access bearer, forwarding messages from UE to MME through a wireless access network. The combination of 103 MME and 104 Serving Gateway is similar to the original 106 SGSN (general packet radio service (GPRS) supporting node). It is possible that both MME and Serving Gateway locate at the same physical entity. 105 PDN Gateway is adapted for the functions like accounting, legally monitoring, etc. And it is possible that both the Serving Gateway and the PDN Gateway locate at the same physical entity. 106 SGSN provides routing for data transmission in existing UMTS. An existing SGSN finds a corresponding gateway GPRS supporting node (GGSN) according to an access point name (APN). 107 HSS is a home subscription sub-system for the UE and is adapted for storing user information such as the current location of UE, address of the serving node, security information on the user, activated packet data protocol (PDP) context for the UE and so on. 108 PCRF provides QoS policy and accounting rules through interface S7.
- In general, a user data stream reaches the 104 Serving Gateway through 105 PDN Gateway. Then, through the GPRS tunnel protocol (GTP) channel, data is sent by the Serving Gateway to the ENB where the UE locates in, and now it is sent by the ENB to corresponding UE.
- HNB refers to a Node B applied in a home. It also can be applied in such site as a university, a company and so on. HNB is a plug and play device. Difference between an HNB and a general macro node B is that: in general not all UEs can access an HNB. For example, only the UEs in a user's home or that are allowed to access the HNB can access the corresponding HNB. And for the HNB in a company, only the company's staff and its allowed partners can access the HNB. The HNB group (e.g., the HNB in a company) bearing the same access subscriber cluster is called CSG (closed subscriber group). No interface X2 (interface between Node Bs in SAE) exists between general HNBs (e.g., the HNBs in homes) or between an HNB and a macro Node B. Through interface S1, a UE switches between HNBs or between an HNB and a macro Node B.
- For an HNB applied in a company or university or the like, a UE frequently moves between two HNBs in the same company. In this case, the switch is always implemented through interface S1 so that great delay causes and efficiency is very poor. In addition, information such as radio resource management and so on can not be exchanged between two HNBs in the same company so that resources can not be utilized effectively.
- The object of this invention is to provide a method for establishing a connection by a Home Node B HNB.
- To achieve the object mentioned above, a method for establishing a connection by a HNB comprising steps of:
- the HNB transmitting an “attachment request” message to an operation and maintenance center (OMC);
- the OMC transmitting an “attachment response” message to the HNB;
- the HNB establishing a connection with an MME indicated by the “attachment response” message;
- With the method proposed in the present invention, a UE can switch between HNBs in the same CSG through interface X2. Meanwhile, such information as the radio resource management and so on can be exchanged between two HNBs.
- The above and other objects, features and advantages of the present invention will be more apparent from the following detailed description in conjunction with the accompanying drawings, in which:
-
FIG. 1 shows a network structure of SAE; -
FIG. 2 shows a process that a connection is established for HNB inembodiment 1 of present invention; -
FIG. 3 shows the process that a connection is established for HNB inembodiment 2 of present invention; -
FIG. 4 shows an operation flows at HNB according toembodiment 1 andembodiment 2 respectively; -
FIG. 5 shows an operation flows at OMC according toembodiment 1 andembodiment 2 respectively; -
FIG. 6 shows an operation flows at MME according toembodiment 1 andembodiment 2 respectively; and -
FIG. 7 shows a process of reconfiguring MME or S-GW. - An
embodiment 1 of the present invention is illustrated inFIG. 2 . Following is a detailed description with reference toFIG. 2 . Detailed technical description for the known components is omitted. In this embodiment, within a CSG, HNB1 is a first HNB that accesses the network. - In
Step 201, HNB1 transmits an “attachment request” message to the OMC. This message contains information on a location of the HNB. Optionally, the “attachment request” message contains an identifier of the CSG to which the HNB belongs. Optionally, the network assigns the CSG identifier to HNB (the first HNB or the first group of HNBs within the CSG) when HNB signs in, or knows the identifier of the CSG to which the HNB (not the first signed in group of HNBs in the CSG) belongs when HNB signs in. -
- In
Step 202, OMC selects an MME for the HNB. Within the CSG, the HNB is the first one that accesses the network. OMC selects an MME for it among the MMEs adjacent to the HNB according to a certain rule such as for balancing the load, reducing a possibility of changing MME when UE moves, and so on. Optionally, OMC may select an S-GW for the HNB according to the same rule as on the selection of MME. HNB and OMC check other HNBs in the CSG which need to establish X2 connection with the HNB. According to the CSG identifier, OMC checks other HNBs in the CSG which need to establish X2 connection with the HNB. Optionally, the addresses of the HNBs are considered when OMC checks other HNBs in the CSG which need to establish X2 connection with the HNB. For example, it is not necessary to establish interface X2 between two HNBs if the two HNBs that are in different countries but in the same company belong to the same CSG. In this embodiment, no other HNB exists in the CSG.
- In
- The process of selecting S-GW for HNB can be implemented by the MME connected to the HNB when data is transferred through the HNB. Therefore, the HNBs in the same CSG connect to the same S-GW. If it is necessary for the first HNB in the CSG to establish the user plane, MME selects an S-GW for the CSG according to such rules as to balance load or to reduce the possibility of changing S-GW when a UE moves, and so on.
- In Step 203, OMC transmits an “attachment response” message to the HNB. This message indicates the MME selected by the OMC for the HNB. Optionally, this message indicates other HNBs necessary to establish X2 connection and adjacent to the HNB. Optionally, the message contains the frequency for using the HNB. The “attachment response” message contains the information on adjacent cells. The “attachment response” message contains a track area identifier (TAI) for the HNB. The “attachment response” message contains the identifier assigned to the HNB. Optionally, the message contains an address of the S-GW that OMC selected for the HNB.
- In
Step 204, HNB initiates a process to establish a connection with the MME indicated by the message. HNB transmits a “connection request” message to MME. The message contains the information on “cells which are overlapped with HNB or CSG”. Optionally, the message contains an information element of the identifier of the TAI where HNB locates in. Optionally, the message contains the information element of the identifier of HNB. Optionally, the message contains the information element of the identifier of the CSG where HNB locates. MME transmits a “connection response” message to HNB. -
Embodiment 2 of the present invention is illustrated inFIG. 3 . Following is detailed description to the figure. Detailed technical description for known components is omitted. In this embodiment, HNB1 and HNB2 belong to the same CSG. HNB1 has accessed the network. And HNB2 begins to accessing the network for a first time. - In Step 301, HNB2 transmits the “attachment request” message to the OMC. This message contains the information on the location of HNB2. Optionally, the “attachment request” message contains the identifier of the CSG to which the HNB2 belongs. Optionally, the network knows the identifier of the CSG to which the HNB belongs when HNB signs in.
-
Step 302, OMC selects an MME for the HNB. If the HNB is not the first to access the network in the CSG, the MME selected by OMC for other HNBs in this CSG is just the one that the HNB should connect to. In this embodiment, OMC assigns both the MME and the S-GW selected for HNB1 to the HNB. Optionally, the address the HNB should be considered when OMC selects MME for the HNB. For example, if two HNBs that are in different countries but in the same company belong to the same CSG, they may not be able to connect to the same MME. In this case, if no adjacent HNB accesses the network, OMC thinks that this HNB is the first one which accesses the network in the CSG and selects an MME for it according to rules such as balancing load or reducing possibility of changing MME when a UE moves, and so on. Optionally, selection of S-GW for the HNB can be implemented by OMC according to the same rules on the selection of MME. OMC checks other HNBs in the CSG which need to establish X2 connection with the HNB. And according to the CSG identifier, OMC checks other HNBs in the CSG which need to establish X2 connection with the HNB. Optionally, the addresses of the HNBs, as well as whether the HNBs share the same CSG or not, are considered when OMC checks other HNBs in the CSG which need to establish X2 connection with the HNB. For example, it is not necessary to establish interface X2 between two HNBs if the two HNBs that are in different countries but in the same company belong to the same CSG. In this embodiment, for example, it is necessary to establish X2 connection between HNB1 and HNB2. - The process of selecting S-GW for HNB can be implemented by the MME connected to the HNB when data is transferred through the HNB. Therefore, the HNBs in the same CSG connect to the same S-GW. If it is necessary for the first HNB in the CSG to establish the user plane, MME selects an S-GW for the CSG according to such rules as to balance load or to reduce the possibility of changing S-GW when a UE moves, and so on. If the HNB is not the first necessary to establish a user plane in the CSG, the S-GW selected by MME for other HNBS in this CSG is just the one that the HNB should connect to.
- In Step 303, OMC transmits the “attachment response” message to the HNB2. This message indicates the MME that the OMC selected for the HNB. And the MME information included in the message may be the IP address of the MME. Optionally, this message contains a list of other HNBs necessary to establish X2 and adjacent to the HNB. The HNB list information included in the message is an IP address list for the HNB. Optionally, the message contains a frequency for using the HNB. The “attachment response” message contains the information on adjacent cells. The “attachment response” message contains the track area identifier (TAI) for the HNB. The “attachment response” message contains the identifier assigned to the HNB. Optionally, the message contains the address of the S-GW that OMC selected for the HNB.
- In
Step 304, HNB2 initiates a process to establish a connection with the HNB indicated by the message. HNB2 transmits the “connection request” message to the other HNB (e.g., HNB1). HNB1 transmits the “connection response” message to HNB2. - In
Step 305, HNB2 initiates a process to establish a connection with the MME indicated by the message. HNB2 transmits the “connection request” message to MME. The message contains the information on “cells which are overlapped with the HNB or CSG”. The message contains the information element of the identifier of the TAI where HNB locates. Optionally, the message contains the information element of the identifier of HNB. Optionally, the message contains the information element of the identifier of the CSG where HNB locates. MME transmits the “connection response” message to HNB2. - The sequence of performing
step 304 and step 305 is not limited. - In this embodiment, the operation flow of HNB is illustrated in
FIG. 4 . Here, detailed technical description for known components is omitted. - In 401, HNB transmits the “attachment request” message to the OMC. This message contains the information on the location of HNB. Optionally, the “attachment request” message contains the identifier of the CSG to which the HNB2 belongs. In 402, HNB waits for the response message. In 403, if HNB receives a “successful attachment response” message, it saves the information that is included in the message, such as information on MME and the information on other HNBs, TAI, the HNB identifier and so on. In 404, HNB initiates the process to establish a connection with the MME indicated by the message. HNB transmits the “connection request” message to MME. Optionally, the message contains the information on “cells which are overlapped with the HNB or CSG”. Optionally, the message contains the information element of the identifier of the TAI where HNB locates. Optionally, the message contains the information element of the identifier of HNB. Optionally, the message contains the information element of the identifier of the CSG where HNB locates. MME transmits the “connection response” message to HNB. 405 Optionally, if the “attachment response” message contains information on other HNBs, such as HNB IP address list, HNB initiates the process to establish connections with other HNBs. HNB transmits the “connection request” to another HNB. An another HNB transmits the “connection response” message to the HNB.
- The sequence of performing
step 404 and step 405 is not limited. - In this embodiment, the operation flow of OMC is illustrated in
FIG. 5 . Here, detailed technical description for known components is omitted. - In 501, OMC receives messages. In 502, if OMC receives the “attachment request” message from HNB, in 503 it saves HNB related information. And if the message contains the location information for HNB, OMC saves this information. And if the message contains the identifier of the CSG where the HNB belongs, OMC saves this information.
- In 504, if the HNB is the first to access the network in corresponding CSG, in 505, OMC selects an MME for HNB in this CSG. OMC selects the MME according to either the address of HNB, or the rule to balance load or to reduce the possibility of changing MME when a UE moves, etc. Optionally, OMC can select an S-GW for the HNB according to the same rule as on the selection of MME.
- In
Step 506, if HNB is not the first to access the network in the CSG, 507 OMC checks other HNBs in the CSG. 508 OMC transmits the “attachment response” message to the requesting HNB. And information on the MME OMC selected for HNB in this CSG is included in the message. Optionally, the “attachment response” message contains the information on the S-GW selected by OMC for HNB in this CSG. Optionally, the message contains the information on other HNBs in this CSG, such as the IP address list for the HNB. Optionally, the message contains the identifier of the TAI where the HNB locates. Optionally, the message contains the HNB identifier allocated to the HNB. The case described above is for that the HNBs in the CSG are not far away from one another. In another case, for example, two HNBs belong to the same CSG in different countries but in the same company, if no adjacent HNB accesses the network, OMC thinks that this HNB is the first one which accesses the network in the CSG and selects an MME for it according to such rules as to balance load or to reduce possibility of changing MME when a UE moves, and so on. Optionally, OMC can select an S-GW for the HNB according to the same rule as on the selection of MME. In this case, OMC finds the other HNB is the one necessary to establish a X2 connection with the HNB in the CSG according to not only the CSG ID. Meanwhile, it should consider the location of the HNB. For example, it is not necessary to establish interface X2 between two HNBs if the two HNBs that are in different countries but in the same company belong to the same CSG. - In this embodiment, the operation flow of MME is illustrated in
FIG. 6 . Here, detailed technical description for the known components is omitted. - In 601 MME receives messages. In 602 if MME receives the “connection request” message from HNB, in 603 MME saves the information which is included in this message, such as the information on “cells which is overlapped with the HNB or CSG”, the identifier of the TAI where HNB locates, the HNB identifier. 604 MME transmits the “connection response” message to HNB.
-
FIG. 7 illustrates the process that OMC reconfigures CSG's MME or S-GW when overload or fault comes across the MME or the S-GW. - In
Step 701, OMC finds that overload or fault comes across the MME or S-GW connected to a certain CSG. - In Step 702, OMC transmits a “reconfiguration request” message to the HNB in CSG. In this message, the information on the reconfigured MME or S-GW and the reason for the reconfiguration are included. And the reconfiguration can be done to the IP address of the MME or the S-GW.
- In
Step 703, the HNB that has received the “reconfiguration request” message transmits the “connection request” message to the new MME or S-GW. Optionally, the “connection request” message sent to MME includes the information on “cells which are overlapped with the HNB or CSG”. Optionally, the “connection request” message sent to MME contains the information element of the identifier of the TAI where HNB locates. The new MME or S-GW transmits the “connection response” message to the HNB. - In Step 704, the HNB transmits a “reconfiguration response” message to OMC.
- Optionally, if the reconfiguration results from the overload of MME or S-GW, HNB initiates the process of releasing the connection with original MME or S-GW.
- While the invention has been shown and described with reference to certain exemplary embodiments of the present invention thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present invention as defined by the appended claims and their equivalents.
Claims (25)
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200710164106 | 2007-09-29 | ||
CN2007101641065A CN101400160B (en) | 2007-09-29 | 2007-09-29 | Method for establishing connection by HNB |
CN200710164106.5 | 2007-09-29 | ||
PCT/KR2008/005445 WO2009045007A1 (en) | 2007-09-29 | 2008-09-16 | Method for establishing connection by hnb |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2008/005445 A-371-Of-International WO2009045007A1 (en) | 2007-09-29 | 2008-09-16 | Method for establishing connection by hnb |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/046,023 Continuation US9560514B2 (en) | 2007-09-29 | 2016-02-17 | Method for establishing connection by HNB |
Publications (2)
Publication Number | Publication Date |
---|---|
US20110314162A1 true US20110314162A1 (en) | 2011-12-22 |
US9271165B2 US9271165B2 (en) | 2016-02-23 |
Family
ID=40518348
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/673,223 Active 2031-01-30 US9271165B2 (en) | 2007-09-29 | 2008-09-16 | Method for establishing connection by HNB |
US15/046,023 Active US9560514B2 (en) | 2007-09-29 | 2016-02-17 | Method for establishing connection by HNB |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/046,023 Active US9560514B2 (en) | 2007-09-29 | 2016-02-17 | Method for establishing connection by HNB |
Country Status (3)
Country | Link |
---|---|
US (2) | US9271165B2 (en) |
CN (1) | CN101400160B (en) |
WO (1) | WO2009045007A1 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110032871A1 (en) * | 2007-09-29 | 2011-02-10 | Samsung Electronics Co., Ltd. | Method for establishing connection by hnb |
US20110098050A1 (en) * | 2009-10-22 | 2011-04-28 | Jacob Eipe | Systems and methods for selecting serving gateways to service user equipment |
US20110098031A1 (en) * | 2009-10-22 | 2011-04-28 | Pradeep Dakshayani | Systems and methods for reduced latency tracking area selection |
US20110096721A1 (en) * | 2009-10-22 | 2011-04-28 | Kamalaraj Vinod | Systems and methods for selecting tracking areas and reducing paging |
US20110171915A1 (en) * | 2010-01-08 | 2011-07-14 | Interdigital Patent Holdings, Inc. | Method and apparatus for adding csg identities to a white list in connected mode |
US8417236B2 (en) | 2009-10-22 | 2013-04-09 | Cisco Technology, Inc. | Systems and methods for classifying user equipment and selecting tracking areas |
CN103220729A (en) * | 2012-01-18 | 2013-07-24 | 中兴通讯股份有限公司 | User context releasing method, base station and femtocell gateway |
US8903402B2 (en) | 2010-03-23 | 2014-12-02 | Huawei Technologies Co., Ltd. | Method, apparatus, and system for access control handover of user between base stations |
US9913206B2 (en) | 2008-03-21 | 2018-03-06 | Interdigital Patent Holdings, Inc. | Method and apparatus for searching for closed subscriber group cells |
US10582428B2 (en) | 2012-09-29 | 2020-03-03 | Samsung Electronics Co., Ltd. | Method and apparatus for performing a handover in a wireless communication system |
Families Citing this family (29)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103179683B (en) * | 2007-09-29 | 2016-08-03 | 北京三星通信技术研究有限公司 | HNB sets up the method connected |
CN101860910B (en) * | 2009-04-09 | 2013-05-08 | 电信科学技术研究院 | Bearer establishing method, system and device of local network |
CN101860976B (en) * | 2009-04-10 | 2012-10-10 | 电信科学技术研究院 | Method, equipment and system for realizing local IP access of user equipment |
EP2437545A4 (en) * | 2009-05-27 | 2017-06-14 | Sharp Kabushiki Kaisha | Mobile communication system, base station device, mobile station device, and handover method |
CN101938783B (en) * | 2009-06-30 | 2013-07-03 | 中兴通讯股份有限公司 | Method and system for realizing load balance |
WO2011023234A1 (en) * | 2009-08-27 | 2011-03-03 | Nokia Siemens Networks Oy | Method and apparatus for operation of a communication network |
CN102006682B (en) * | 2009-08-28 | 2015-11-25 | 中兴通讯股份有限公司 | A kind of method of transmitting closed subscriber group information and base station |
CN102036289B (en) * | 2009-09-25 | 2013-01-16 | 中国移动通信集团公司 | Comprehensive network agent system and method for home nodeB (HNB) |
CN102045691B (en) * | 2009-10-10 | 2014-06-11 | 中兴通讯股份有限公司 | Method and device for acquiring grouped identifiers of machine type communication (MTC) equipment |
JP4870201B2 (en) * | 2009-10-14 | 2012-02-08 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication method and radio base station |
CN102045895A (en) * | 2009-10-20 | 2011-05-04 | 中兴通讯股份有限公司 | Management method and device of members in closed subscriber group (CSG) |
US8630642B2 (en) * | 2009-10-30 | 2014-01-14 | Htc Corporation | Method of handling proximity information transmission and related communication device |
US8391871B2 (en) * | 2009-10-30 | 2013-03-05 | Htc Corporation | Method of handling proximity information transmission and related communication device |
CN102056347B (en) * | 2009-11-09 | 2014-07-09 | 华为终端有限公司 | Method, equipment and system for transferring IP service of core network |
CN102014449B (en) * | 2009-11-27 | 2013-12-25 | 电信科学技术研究院 | User equipment switching method and home evolved base station |
JP4790057B2 (en) * | 2009-12-04 | 2011-10-12 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication method and switching center |
WO2011082538A1 (en) * | 2010-01-08 | 2011-07-14 | 上海贝尔股份有限公司 | Method and apparatus for mobility optimization based on group in machine-type communications |
CN102143538B (en) * | 2010-01-29 | 2013-08-14 | 电信科学技术研究院 | Method for switching radio access network (RAN) and base station |
CN101867984A (en) * | 2010-02-26 | 2010-10-20 | 新邮通信设备有限公司 | Switching method, donor base station and relay node in long-term evolution enhancement system |
US8600387B2 (en) * | 2010-04-29 | 2013-12-03 | Qualcomm Incorporated | Method and apparatus for performing intra closed subscriber group handover |
CN102238667B (en) * | 2010-05-07 | 2015-09-16 | 北京三星通信技术研究有限公司 | A kind ofly set up the method connected between base station |
CN102238703B (en) * | 2010-05-07 | 2015-09-16 | 中兴通讯股份有限公司 | A kind of direct interface selects the method and system set up |
CN102256326B (en) * | 2010-05-19 | 2016-06-15 | 中兴通讯股份有限公司 | A kind of method and apparatus realizing Route Selection |
US20120002637A1 (en) * | 2010-06-18 | 2012-01-05 | Interdigital Patent Holdings, Inc. | Method and apparatus for supporting home node-b mobility |
CN102006642A (en) * | 2010-09-03 | 2011-04-06 | 北京邮电大学 | Method for switching between home base station and relay station |
KR101651120B1 (en) * | 2011-01-06 | 2016-08-25 | 삼성전자주식회사 | Method and apparatus for x2 interface between bs using gateway in wireless communication system having hierarchical cell structure |
CN102625411B (en) * | 2011-01-27 | 2016-08-03 | 中兴通讯股份有限公司 | User's method for releasing of a kind of network element overload and system |
CN102761925B (en) * | 2011-04-29 | 2017-04-05 | 中兴通讯股份有限公司 | Judge the method and base station from home of base station from home and home base-station gateway annexation |
CN104581652B (en) * | 2013-10-15 | 2018-12-07 | 华为技术有限公司 | Message treatment method, the method and apparatus for selecting MME |
Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20010055285A1 (en) * | 2000-06-21 | 2001-12-27 | Nec Corporation | Mobile communication system and gateway selecting method thereof |
US20030087648A1 (en) * | 2000-05-05 | 2003-05-08 | Mezhvinsky Alex Naum | End user to mobile service provider message exchange system based on proximity |
US20030095520A1 (en) * | 2001-11-19 | 2003-05-22 | Aalbers Roeland G.D. | Method and apparatus for identifying a node for data communications using its geographical location |
US20030148771A1 (en) * | 2002-02-07 | 2003-08-07 | De Verteuil Andre Laurent | Efficient location determination for mobile units |
US20060073838A1 (en) * | 2004-09-10 | 2006-04-06 | Kamali Tayeb A | Automatic critical health care service system using wireless communication, positioning and/or RF ID |
US20070179843A1 (en) * | 2006-02-02 | 2007-08-02 | France Telecom | Information engine and associated method of delivering targeted metrics |
US20080049696A1 (en) * | 1995-06-06 | 2008-02-28 | Stewart Brett B | Method and apparatus for geographic-based communications service |
US20080244148A1 (en) * | 2007-04-02 | 2008-10-02 | Go2Call.Com, Inc. | VoIP Enabled Femtocell with a USB Transceiver Station |
US20080316994A1 (en) * | 2007-06-22 | 2008-12-25 | Ubiquisys Limited | Synchronization in a mobile communications network |
US20090191844A1 (en) * | 2007-10-04 | 2009-07-30 | Morgan Todd C | Method for authenticating a mobile unit attached to a femtocell that operates according to code division multiple access |
US20090225743A1 (en) * | 2008-03-07 | 2009-09-10 | Charles Nicholls | Using a network frequency reference to augment timing synchronization in a wireless base station |
US20100029283A1 (en) * | 2007-01-05 | 2010-02-04 | Ntt Docomo, Inc. | User equipment and method used in mobile communication system |
US20100061232A1 (en) * | 2008-09-05 | 2010-03-11 | Wei Hua Zhou | Load balancing mechanism for dynamic serving functional elements selection |
US20100265867A1 (en) * | 2007-10-02 | 2010-10-21 | Ralf Becker | Management of session control signaling for multicast/broadcast services |
US20110038431A1 (en) * | 2008-04-30 | 2011-02-17 | Nokia Siemens Networks Oy | Transmitting Node B Load Status Information in a Self Organising Network |
US8050653B2 (en) * | 2004-03-22 | 2011-11-01 | Research In Motion Limited | System and method for viewing message attachments |
Family Cites Families (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002163297A (en) * | 2000-11-27 | 2002-06-07 | Ntt Docomo Inc | Information retrieving method and relay device |
KR20020091791A (en) * | 2001-05-30 | 2002-12-06 | 미츠비시 마테리알 가부시키가이샤 | Communication system management server, wireless server, mobile management server and information management server |
JP3769533B2 (en) * | 2002-11-29 | 2006-04-26 | Necインフロンティア株式会社 | Wireless LAN communication method and system |
US20050136988A1 (en) * | 2003-12-19 | 2005-06-23 | Villamil Camilo E. | Method for reporting personal status of a mobile communication device user and method therefor |
CN1989746B (en) * | 2004-07-30 | 2011-05-04 | 夏普株式会社 | Control system of communication network |
CN100456879C (en) * | 2005-06-21 | 2009-01-28 | 华为技术有限公司 | Mobile communication network and its communication method |
US8532606B2 (en) * | 2005-10-07 | 2013-09-10 | Lg Electronics Inc. | Method and system for providing an emergency location service using interoperability between IMS core and access network |
DE102006015033B4 (en) * | 2005-12-16 | 2016-07-07 | Siemens Aktiengesellschaft | Mobile station as a gateway for mobile terminals to an access network and method for network registration of the mobile station and the mobile terminals |
JP4692760B2 (en) * | 2006-03-16 | 2011-06-01 | 日本電気株式会社 | Mobile communication system and mobility management control method thereof |
US8412274B2 (en) * | 2006-06-08 | 2013-04-02 | Hitachi Kokusai Electric Inc. | Wireless base station device |
US20080076425A1 (en) * | 2006-09-22 | 2008-03-27 | Amit Khetawat | Method and apparatus for resource management |
CN101690290A (en) * | 2007-04-27 | 2010-03-31 | 株式会社Ntt都科摩 | Method for controlling access to base station intended for particular users, base station apparatus and mobile communication management apparatus |
US20090005052A1 (en) * | 2007-06-30 | 2009-01-01 | David Abusch-Magder | Method and Apparatus for Dynamically Creating and Updating Base Station Neighbor Lists |
US20090067420A1 (en) * | 2007-09-11 | 2009-03-12 | General Instrument Corporation | Location Determination for a Packet-Switched Device for Providing Location-Based Services |
-
2007
- 2007-09-29 CN CN2007101641065A patent/CN101400160B/en active Active
-
2008
- 2008-09-16 US US12/673,223 patent/US9271165B2/en active Active
- 2008-09-16 WO PCT/KR2008/005445 patent/WO2009045007A1/en active Application Filing
-
2016
- 2016-02-17 US US15/046,023 patent/US9560514B2/en active Active
Patent Citations (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080049696A1 (en) * | 1995-06-06 | 2008-02-28 | Stewart Brett B | Method and apparatus for geographic-based communications service |
US20030087648A1 (en) * | 2000-05-05 | 2003-05-08 | Mezhvinsky Alex Naum | End user to mobile service provider message exchange system based on proximity |
US20010055285A1 (en) * | 2000-06-21 | 2001-12-27 | Nec Corporation | Mobile communication system and gateway selecting method thereof |
US20030095520A1 (en) * | 2001-11-19 | 2003-05-22 | Aalbers Roeland G.D. | Method and apparatus for identifying a node for data communications using its geographical location |
US20030148771A1 (en) * | 2002-02-07 | 2003-08-07 | De Verteuil Andre Laurent | Efficient location determination for mobile units |
US8050653B2 (en) * | 2004-03-22 | 2011-11-01 | Research In Motion Limited | System and method for viewing message attachments |
US20060073838A1 (en) * | 2004-09-10 | 2006-04-06 | Kamali Tayeb A | Automatic critical health care service system using wireless communication, positioning and/or RF ID |
US20070179843A1 (en) * | 2006-02-02 | 2007-08-02 | France Telecom | Information engine and associated method of delivering targeted metrics |
US20100029283A1 (en) * | 2007-01-05 | 2010-02-04 | Ntt Docomo, Inc. | User equipment and method used in mobile communication system |
US20080244148A1 (en) * | 2007-04-02 | 2008-10-02 | Go2Call.Com, Inc. | VoIP Enabled Femtocell with a USB Transceiver Station |
US7990912B2 (en) * | 2007-04-02 | 2011-08-02 | Go2Call.Com, Inc. | VoIP enabled femtocell with a USB transceiver station |
US20080316994A1 (en) * | 2007-06-22 | 2008-12-25 | Ubiquisys Limited | Synchronization in a mobile communications network |
US20100265867A1 (en) * | 2007-10-02 | 2010-10-21 | Ralf Becker | Management of session control signaling for multicast/broadcast services |
US20090191844A1 (en) * | 2007-10-04 | 2009-07-30 | Morgan Todd C | Method for authenticating a mobile unit attached to a femtocell that operates according to code division multiple access |
US20090225743A1 (en) * | 2008-03-07 | 2009-09-10 | Charles Nicholls | Using a network frequency reference to augment timing synchronization in a wireless base station |
US20110038431A1 (en) * | 2008-04-30 | 2011-02-17 | Nokia Siemens Networks Oy | Transmitting Node B Load Status Information in a Self Organising Network |
US20100061232A1 (en) * | 2008-09-05 | 2010-03-11 | Wei Hua Zhou | Load balancing mechanism for dynamic serving functional elements selection |
Cited By (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110032871A1 (en) * | 2007-09-29 | 2011-02-10 | Samsung Electronics Co., Ltd. | Method for establishing connection by hnb |
US8824365B2 (en) * | 2007-09-29 | 2014-09-02 | Samsung Electronics Co., Ltd. | Method for establishing connection by HNB |
US9913206B2 (en) | 2008-03-21 | 2018-03-06 | Interdigital Patent Holdings, Inc. | Method and apparatus for searching for closed subscriber group cells |
US8958341B2 (en) | 2009-10-22 | 2015-02-17 | Cisco Technology, Inc. | Systems and methods for selecting serving gateways to service user equipment |
US20110098050A1 (en) * | 2009-10-22 | 2011-04-28 | Jacob Eipe | Systems and methods for selecting serving gateways to service user equipment |
US20110098031A1 (en) * | 2009-10-22 | 2011-04-28 | Pradeep Dakshayani | Systems and methods for reduced latency tracking area selection |
US20110096721A1 (en) * | 2009-10-22 | 2011-04-28 | Kamalaraj Vinod | Systems and methods for selecting tracking areas and reducing paging |
US8358593B2 (en) * | 2009-10-22 | 2013-01-22 | Cisco Technology, Inc. | Systems and methods for selecting serving gateways to service user equipment |
US8417236B2 (en) | 2009-10-22 | 2013-04-09 | Cisco Technology, Inc. | Systems and methods for classifying user equipment and selecting tracking areas |
US8594014B2 (en) | 2009-10-22 | 2013-11-26 | Cisco Technology, Inc. | Systems and methods for selecting tracking areas and reducing paging |
US9872269B2 (en) | 2009-10-22 | 2018-01-16 | Cisco Technology, Inc. | Systems and methods for reduced latency tracking area selection |
US20110171915A1 (en) * | 2010-01-08 | 2011-07-14 | Interdigital Patent Holdings, Inc. | Method and apparatus for adding csg identities to a white list in connected mode |
US9467884B2 (en) | 2010-01-08 | 2016-10-11 | Interdigital Patent Holdings, Inc. | Method and apparatus for adding CSG identities to a white list in connected mode |
US10165481B2 (en) | 2010-01-08 | 2018-12-25 | Interdigital Patent Holdings, Inc. | Method and apparatus for adding CSG identities to a white list in connected mode |
US8903402B2 (en) | 2010-03-23 | 2014-12-02 | Huawei Technologies Co., Ltd. | Method, apparatus, and system for access control handover of user between base stations |
CN103220729A (en) * | 2012-01-18 | 2013-07-24 | 中兴通讯股份有限公司 | User context releasing method, base station and femtocell gateway |
US10582428B2 (en) | 2012-09-29 | 2020-03-03 | Samsung Electronics Co., Ltd. | Method and apparatus for performing a handover in a wireless communication system |
US11419020B2 (en) | 2012-09-29 | 2022-08-16 | Samsung Electronics Co., Ltd. | Method and apparatus for performing a handover in a wireless communication system |
Also Published As
Publication number | Publication date |
---|---|
WO2009045007A1 (en) | 2009-04-09 |
US9271165B2 (en) | 2016-02-23 |
US9560514B2 (en) | 2017-01-31 |
CN101400160A (en) | 2009-04-01 |
CN101400160B (en) | 2013-04-10 |
US20160165430A1 (en) | 2016-06-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9271165B2 (en) | Method for establishing connection by HNB | |
US8824365B2 (en) | Method for establishing connection by HNB | |
EP3834384B1 (en) | Control plane based configuration for time sensitive networking | |
US11115919B2 (en) | Network selection method and base station | |
US9357571B2 (en) | Local network and method for establishing connection between local gateway and home base station | |
US8620329B2 (en) | Method and apparatus for performing switching in mobile communication system | |
EP2667551B1 (en) | Method and system for setting up a bearer | |
US10779357B2 (en) | Method for avoiding handover failure | |
US11129054B2 (en) | Methods, systems and devices for supporting local breakout in small cell architecture | |
US20140113637A1 (en) | Method, Apparatus, and System for Performing Handover Between Home Base Stations | |
EP4008128A1 (en) | Configuration of time sensitive bridge during handover | |
US20150138952A1 (en) | Communication system and method for path control | |
CN114946268A (en) | Control of network slices | |
KR102160743B1 (en) | Method and apparatus for acquiring location information of user equipment based on event | |
CN103179683B (en) | HNB sets up the method connected |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SAMSUNG ELECTRONICS CO., LTD., KOREA, REPUBLIC OF Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:XU, LIXIANG;SUN, CHUNYING;WANG, HONG;AND OTHERS;REEL/FRAME:023930/0856 Effective date: 20100203 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |