Communications system

Communication Systems

[0001] This application is a divisional application of an invention patent with an application date of November 02, 2009, an application number of 200980144059.5, and a title of "communication system".

Technical field

[0002] The present invention relates to mobile communication networks, specifically but not exclusively to networks operating in accordance with 3GPP standards or their equivalents or derivatives. The present invention is specifically but not exclusively related to the interface between the home base station and the home base station gateway device.

Background technique

[0003] Under the 3GPP standard, NodeB (or eNB in LTE) is a base station through which mobile devices connect to the core network. In recent years, the 3GPP standards body has adopted the office system architecture and started to develop new standards for home base stations (HNB). In the case where the home base station operates according to the LTE standard, HNB is sometimes referred to as HeNB. However, for simplicity, in the following description, only the term HNBoHNB will be used to provide radio coverage (3G/4G) within the home, and will be via a suitable public network (e.g. via an ADSL link to the Internet) and HNB gateway (HNB- GW) Connect to the mobile network. As part of the standard setting process, the registration process between HNB and HNB-GW has been agreed.

[0004] It was also agreed that the access control mechanism is mandatory at the HNB-GW, and is optionally provided to the pre-release 8 user equipment (UE) at the HNB. In addition, for different evolution scenarios of HNB deployment, it is recognized that HNB can utilize different access control mechanisms (ie, "open", "closed", and "hybrid") to operate. Those skilled in the art should understand that if the HNB is open, for pre-release 8UE, mandatory access control at the HNB-GW is not required. If the HNB is hybrid, for pre-release 8UE, mandatory access control at the HNB-GW may not be required.

[0005] Although for efficiency understood by those skilled in the art, the present invention will be described in detail in the context of a 3G system, but the principle of the present invention can be applied to the case where the corresponding elements of the system are changed as required Other systems where a mobile device or user equipment (UE) communicates with one of several base stations.

Summary of the invention

[0006] The embodiments of the present invention aim to solve one or more of the above problems by enabling the HNB to provide capability information to the HNB-GW.

[0007] According to one aspect, the present invention provides a method executed by a gateway device, the method comprising: receiving a request to register a mobile communication device from a home base station; judging whether the home base station is an open access mode home base station or a closed access mode Into the mode home base station; if the determining step determines that the home base station is a closed mode home base station, access control is performed for the mobile communication device, and if the access control is successful, the mobile phone is registered with the gateway device; if The determining step determines that the home base station is an open-mode home base station, and the mobile phone is registered with the gateway device without performing access control; and if the registration of the mobile communication device is accepted, it is registered with the mobile communication device. The home base station sends a registration acceptance message.

[0008] In one embodiment, the gateway determines whether the home base station is an open access mode home base station or a closed access mode home base station based on, for example, information received from the home base station in the registration request. The information can be defined by the presence or absence of optional elements in the home base station registration request. For example, through the registration request of the home base station

The presence or absence of the access control list is defined so that if the access control list exists, the gateway device determines that the home base station is a closed access home base station, and if the access control list does not exist, the gateway device The device determines that the home base station is an open access home base station.

[0009] Alternatively, the information may be defined by the content of the mandatory element in the home base station registration request. For example, it is defined by the presence or absence of an entry in the mandatory element. In one embodiment, the data is defined by the presence or absence of entries in the mandatory access control list in the home base station registration request, so that if the access control list includes one or more entries, the The gateway device determines that the home base station is a closed access home base station, and if the access control list is empty, the gateway device determines that the home base station is an open access home base station.

[0010] The access mode of the Femtocell can be open, closed, or hybrid, and the gateway device can regard the Femtocell in the hybrid access mode as an open access mode Femtocell, or as a closed access mode. The in-mode home base station may be regarded as both an open-access mode home base station and a closed-access mode home base station. In one embodiment, the mandatory element defines whether the home base station is an open access home base station, a closed access home base station, or a hybrid access home base station.

[0011] If the home base station is a hybrid access home base station, the method may include performing access control for the mobile communication device, and if it succeeds, registering the mobile phone with the gateway device and generating an identification of the mobile communication The device is data that is part of the closed subscriber group associated with the home base station; and if the access control is not successful, the mobile phone is registered with the gateway device and generates identification that the mobile communication device is not associated with the home base station Data that is part of a closed subscriber group.

[0012] In another embodiment, the gateway determines whether the home base station is an open access mode home base station or a closed access mode home base station based on data stored in a central database such as an operation and management database.

[0013] The present invention also provides a method executed by a home base station, the method comprising: sending to the gateway device data identifying whether the home base station is an open access mode home base station or a closed access mode home base station; from the mobile The communication device receives the request; sends a registration request for the mobile communication device to the gateway device; and if the registration of the mobile communication device is accepted, receives a registration acceptance message from the gateway device.

[0014] The home base station may include data in the home base station registration request message sent by the home base station.

[0015] In one embodiment, the data is defined by the presence or absence of optional elements in the home base station registration request. For example, the data may be defined by the presence or absence of the access control list in the home base station registration request, so that if the home base station is a closed access home base station, the home access base station is registered with the home base station The request includes the access control list, and if the home base station is an open access home base station, the home access base station does not include the access control list in the home base station registration request.

[0016] In another embodiment, the data may be defined by the content of the mandatory element in the home base station registration request. For example, the data may be defined by the presence or absence of entries within the mandatory element. For example, the data can be defined by the presence or absence of an entry in the mandatory access control list in the home base station registration request, so that if the home base station is a closed access home base station, the home access base station is The home base station registration request includes the entry in the access control list, and if the home base station is an open access home base station, the home access base station does not include the entry in the access control list in the home base station registration request entry.

[0017] In another embodiment, the mandatory element may define whether the home base station is an open access home base station, a closed access home base station, or a hybrid access home base station.

[0018] The present invention also provides corresponding gateway equipment and home base stations. The present invention also provides a message, which includes identifying the family

Whether the base station is the data of the open access mode home base station or the closed access mode home base station.

[0019] The present invention provides a corresponding computer program or computer program product for executing on the corresponding device, the device itself (user equipment, node or its component), and a method for updating the device for all the methods disclosed.

Description of the drawings

[0020] The embodiments of the present invention will now be described by way of example with reference to the accompanying drawings, in which:

[0021] FIG. 1 schematically shows a mobile telecommunication system of the type to which this embodiment can be applied;

[0022] FIG. 2 is a block diagram of a mobile phone forming part of the system shown in FIG. 1;

[0023] FIG. 3 is a block diagram of a home base station forming part of the system shown in FIG. 1;

[0024] FIG. 4 is a block diagram of a home base station gateway forming part of the system shown in FIG. 1;

[0025] FIG. 5 is a sequence diagram illustrating a registration process for registering a home base station with a home base station gateway; and

[0026] FIG. 6 is a sequence diagram illustrating the registration process performed when the mobile phone registers with the home base station gateway.

[0027] The best mode of the present invention

[0028] Overview

[0029] FIG. 1 schematically illustrates a mobile (cellular) telecommunication system 1, in which, when a user of a mobile phone (MT) 3 leaves home 9, the user can access a 3G radio access network (RAN) base station 5, radio The network controller 7 and the core telephone network 8 communicate with other users (not shown); and when the user is at home 9, it can pass through the home base station (HNB) 11, the Internet 13, and the home base station gateway (HNB-GW) 15 and the core telephone network 8 to communicate with other users (not shown). HNB 11 will generally be connected to HNB-GW 15 via a suitable residential Internet connection such as ADSL or wired connection.

[0030] mobile phone

[0031] FIG. 2 schematically illustrates the main components of the mobile phone 3 shown in FIG. As shown in the figure, the mobile phone 3 includes a transceiver circuit 23 that is operable to transmit and receive signals to and from the RAN base station 5 or HNB 11 via one or more antennas 25. As shown in the figure, the mobile phone 3 further includes a controller 27 that controls the operation of the mobile phone 3 and is connected to the transceiver circuit 23, the speaker 29, the microphone 31, the display 33, and the keyboard 35. The controller 27 operates according to software instructions stored in the memory 37. As shown in the figure, these software instructions include an operating system 39 and a mobile phone registration module 41. In this embodiment, when the user is at home or when they are within the range of their HNB 11, the mobile phone registration module 41 allows the user to select the home base station 11 to which the mobile phone 3 will be registered. The selection can be automatic or manually controlled by the user.

[0032] Home base station

[0033] FIG. 3 is a block diagram illustrating main components of a home base station (HNB) 11 shown in FIG. 1. As shown in the figure, the HNB 11 includes a transceiver circuit 51 that is operable to transmit signals to and receive signals from the mobile phone 3 via one or more antennas 53 and is operable to transmit signals via the HNB- The GW interface 55 is used to send and receive signals to and from HNB-GW 15. The operation of the transceiver circuit 51 is controlled by the controller 57 according to software stored in the memory 59. The software stored in the memory 59 includes an operating system 61, a base station registration module 63, a telephone registration module 65, and so on. The base station registration module 63 is operable to register the HNB with the HNB-GW 15 and the mobile phone registration module 65 is operable to register the mobile phone 3 with itself and the HNB-GW 15.

[0034] HNB Gateway

4 is a block diagram illustrating the main components of the HNB gateway (HNB-GW) 15 shown in FIG. 1. As shown in the figure, HNBGW 15 includes a transceiver circuit 101, which is operable to transmit signals to and from HNB 11 via HNB interface 103.

It receives signals and is operable to send and receive signals to and from the core network 8 via the core network interface 105. The operation of the transceiver circuit 101 is controlled by the controller 107 according to software stored in the memory 109. The software stored in the memory 109 includes an operating system 11KHNB registration module 113, a mobile phone registration module 115, and so on. The HNB registration module 113 is operable to control the registration of the HNB 11 and the mobile phone registration module is operable to control the registration of the mobile phone 3 and to perform access control as needed.

[0036] In the above description, the mobile phone 3, the base station 5, and the HNB gateway 15 are described as having many separate modules (such as registration modules) for ease of understanding. Although for some applications, such as when existing systems are modified to implement the present invention, these modules can be provided in this way, but in other applications, for example, in systems designed with the inventive features from the beginning , These modules can be built into the entire operating system or code so that these modules cannot be identified as separate entities.

[0037] Access Control

[0038] As shown above, three different access mode types are defined for HNB 11:

[0039] Open access mode: HNB operates as a normal cell through which any mobile phone 3 can make and receive calls;

Closed access mode: HNB operates as a closed subscriber group (CSG) cell, where only CSG members are allowed to access (this is the mode defined in pre-release 8); and

[0041] Hybrid access mode: CSG cell, in which at the same time, non-CSG members are allowed to access.

[0042] Although the hybrid access mode is designed for release 9, if the timescale of release 8 is not affected, operators will be happy to recommend the implementation of the hybrid access mode in release 8.

[0043] It will be understood that for HNB 11 operating in closed access mode, HNB-GW 15 must perform access control to restrict access to core network 8 to only those mobile phones 3 belonging to their respective subscriber groups For the HNB 11 operating in the open mode, the HNB-GW 15 does not need to perform access control; and for the HNB 11 operating in the hybrid mode, the HNB-GW 15 may not need to perform access control. Therefore, in this embodiment, the HNB 11 notifies the HNB-GW 15 of its access mode capabilities so that the HNB-GW 15 can determine whether to perform access control for the mobile phone 3 seeking to register with that HNB 11.

[0044] Many techniques for HNB 11 to signal its access mode capabilities to HNB-GW 15 will now be described.

[0045] HNB registration process

[0046] The purpose of the HNB registration process is to register HNB 11 with HNB-GW 15 so that HNB-GW can provide HNB 11 with services and core network connectivity. The general processing is shown in FIG. 5. As shown in the figure, this process involves HNB 11 sending an HNB REGISTER REQUEST message to HNB-GW and HNB-GW 15 sending an HNB REGISTER ACCEPT message in response. There are many different options for signaling the access mode capability of HNB 11 to HNB-GW 15.

[0047] Option 1: HNB-GW 15 may infer the access mode of HNB 11 based on the access control list information element (IE). Therefore, it is proposed to include the optional access control list IE in the HNBAP HNB REGISTER REQUEST message sent from HNB 11 to HNB-GW 15. If HNB 11 is in closed access mode, it will include the optional access control list IE in the HNBAP registration request message; otherwise, if HNB is in open or hybrid access mode, it will not be in HNBAP HNB registration request The message includes an optional access control list IE. Therefore, the new access control list IE needs to be included in the HNBAP HNB registration request message.

[0048] HNB registration request

[0049]

<td>parameter</td><td>Existence</td><td>range</td><td>IE type and reference</td><td>Semantic description</td><td>Criticality</td><td>Is assigned. The criticality of</td>

<td>Message type</td><td>M'</td><td></td><td>9.2,1</td><td></td><td>Yes</td><td>Refuse</td>

<td>HNB identity</td><td>Μ</td><td></td><td>922</td><td></td><td>Yes</td><td>Refuse</td>

[0050]

<td>HNB location information</td><td>Μ'</td><td></td><td>9.2.3</td><td></td><td>Yes</td><td>Refuse</td>

<td>Access control list</td><td>()</td><td></td><td>9.2.x</td><td>If the IE. is included, the HNB access mode is considered to be reclosed." 111· ^11 Wu T Note Q</td><td>Yes</td><td>ignore</td>

<td>PLMN-ID</td><td>Μ</td><td></td><td>9214</td><td></td><td>Η </td><td>Refuse</td>

<td>Cell-ID</td><td>Μ</td><td></td><td></td><td></td><td>Yes</td><td>Refuse;</td>

<td>LAC</td><td>Μ</td><td></td><td>9.2.11</td><td></td><td>Yes</td><td>:Refuse</td>

<td>RAC</td><td>Μ</td><td></td><td>9212</td><td></td><td>Yes</td><td>Refuse;</td>

<td>SAC</td><td>:Μ</td><td></td><td>9213</td><td></td><td>Yes</td><td>Refuse</td>

[0051] This message is sent by HNB 11 to HNB-GW 15 to register HNB 11 at HNB-GW 15._o[0052] Direction: HNB^HNB-GW

[0053] 9.2.x Access Control List

[0054]

<td>IE/group name</td><td>Save</td><td>Range i</td><td>IE type and reference</td><td>Semantic description'</td>

<td>Receiving and holding list</td><td></td><td>O..maxUEs</td><td></td><td>If the list is empty, the ACL is considered empty,</td>

<td>HMSi</td><td>Μ</td><td></td><td>IMSI9210</td><td></td>

[0055] Note 1: The above option assumes that the HNB-GW 15 treats the open access HNB and the hybrid access HNB as the same and therefore, the hybrid HNB does not need to notify the HNB-GW 15 of its access control list. It is unclear whether this assumption is valid in the standard. Therefore, if the HNB-GW 15 does need to have a hybrid HNB access control list, this option will not work.

[0056] Note 2: It is still unclear whether it is possible to have a closed mode HNB without IMSI (International Mobile Subscriber Identity) (ie, an empty access control list) in the access control list in the current standard document. Assuming that the closed HNB cannot have an empty access control list, the existence of the access control list should be made mandatory in the HNBAP HNB registration request message

(Rather than optional as suggested above). In this way, if HNB-GW 15 receives an empty access control list in the HNBAP HNB registration request, HNB-GW 15 can infer that HNB 11 is in open access mode; otherwise, if there is at least one access control list in the access control list IE One entry, the HNB-GW can determine that HNB 11 is a closed mode HNB.

[0057] Option 2: HNB 11 can indicate its capabilities to HNB-GW 15 (open, closed, or hybrid) in the HNBAP HNB registration request message during the HNB registration process by using the new HNB capability information IE shown in the table below. formula).

[0058] HNB registration request

[0059]

<td>parameter</td><td>In sex</td><td>range</td><td>ΙΕ type and reference</td><td>Semantic description</td><td>Criticality</td><td>Assigned criticality</td>

<td>Message type</td><td>Μ</td><td></td><td>9.2.1</td><td></td><td>Yes</td><td>Refuse ]</td>

<td>HNB identity</td><td>Μ;</td><td></td><td>9.2.2</td><td></td><td>Yes</td><td>Refuse</td>

<td>HNB location information</td><td>Μ</td><td></td><td>9.2.3</td><td></td><td>Yes</td><td>:Reject; reject 1</td>

<td>HNB capability information</td><td>Μ</td><td></td><td>92y</td><td></td><td>Yes</td><td>Refuse :</td>

<td>PLK4N-ID Small|χ-π)</td><td>; Μ.: Μ</td><td>—</td><td>92149.2.25</td><td>...........................,</td><td>Yes......................</td><td>Reject Ί-reject</td>

<td>LAC</td><td>Μ</td><td></td><td>9.2.11</td><td></td><td>Yes</td><td>Reject |</td>

<td>RAC</td><td>Μ</td><td></td><td>9.2.12</td><td></td><td>Yes</td><td>Reject |</td>

<td>SAC</td><td></td><td></td><td>9213</td><td></td><td>Yes</td><td>Reject |</td>

[0060] 9.2. HNB capability information

[0061] The HNB Capability Information IE is sent from the HNB to the HNB-GW to provide information about the capabilities of the HNB.

[0062]

<td>IE/group name</td><td>Save</td><td>range</td><td>1E rate and public examination</td><td>Linguistic description</td>

<td>HNB can.</td><td></td><td></td><td></td><td></td>

<td>&gt;Access control type</td><td>Μ</td><td>(Kai Fang Wu "Closed, Taki Take Wu"</td><td></td><td></td>

[0063] Option 3: The OAM (Operation and Maintenance) function for HNB-GW 15 stores the HNB access mode of each HNB 11. After successful HNB registration at the HNB-GW 15, the HNB-GW 15 acquires the HNB access mode from the OAM database (not shown) and performs access control accordingly.

[0064] UE registration process

[0065] Based on the above possible options, HNB-GW 15 will know the HNB access control mode during the HNB registration process.

HNB-GW 15 will store this information for future use until either HNB 11 updates this information via another HNBAP process or deregisters itself. In one embodiment, mobile phone registration (shown in Figure 6) will be performed using the following steps:

[0066] 1. After camping on the HNB 11, the mobile phone (MT) 3 initiates an initial NAS procedure (for example, an LU procedure) by establishing an RRC connection with the HNB 11.

[0067] 2. MT 3 then sends an RRC initial direct transfer message, which carries an initial NAS message (for example, a location update request message) with a NAS-level identity (IMSI or TMSI, P-TMSI, etc.).

[0068] 3. HNB 11 initiates MTS registration to HNB-GW 15. If the HNB 11 is in a closed or hybrid access mode, before starting the mobile phone registration process, the HNB executes the NAS COMMON ID process in order to obtain the IMSI of the mobile phone 3, if the RRC connection is established or the initial direct transfer No words of that identity were received in the message.

[0069] 4. HNB 11 may optionally perform access control based on IMSI and an access control list.

[0070] The 5.3G HNB 11 tries to send an HNBAP UE registration request (HNBAP UE REGISTER REQUEST) to register the mobile phone 3 on the HNB-GW 15.

[0071] 6. If the HNB 11 is in an open access mode, the HNB-GW 15 will accept the registration of the mobile phone 3 and assign the mobile phone 3 a context id (context-id).

[0072] 7. If the HNB 11 is in a closed access mode, the HNB-GW 15 will perform access control for the specific mobile phone 3 trying to utilize the specific 3G HNB.

[0073] 8. If the HNB 11 is in the hybrid access mode, the HNB-GW 15 will perform access control for the specific mobile phone 3 trying to utilize the specific 3G HNB. If the access control is successful, the HNB-GW 15 accepts the registration of the mobile phone 3 and allocates a context id to the mobile phone 3. In this case, the mobile phone 3 is considered to be a CSG mobile phone. This information is stored and can be used for purposes such as service differentiation. On the other hand, if the access control fails, the HNB-GW 15 still accepts the registration of the mobile phone 3 and allocates a context id to the mobile phone 3. However, in this case, the mobile phone is considered to be a non-CSG mobile phone (this information is stored and can be used for purposes such as service differentiation).

[0074] 9. If the HNB-GW accepts the mobile phone registration request, the HNB-GW will send a UE registration acceptance message including a unique context id to the HNB.

[0075] 10. After the successful completion of the mobile phone registration request message, the HNB 11 sends a CONNECT message containing the RANAP initial UE message.

[0076] 11. After receiving the RUA connection (RUA CONNECT) message, the HNB-GW 15 performs SCCP connection establishment towards the core network 8. The HNB-GW 15 may include the initial UE message in the SCCP CR message. Alternatively, the HNB-GW 15 sends the initial UE message after the successful establishment of the SCCP connection establishment.

[0077] Modifications and Alternatives

[0078] The detailed embodiments have been described above. Those skilled in the art will understand that many modifications and substitutions can be made to the above embodiments while benefiting from the invention contained herein.

[0079] In the above embodiments, a mobile phone-based telecommunications system has been described. Those skilled in the art will understand that the signaling technology described in this application can also be used in other communication systems. Other communication nodes or devices may include user equipment, such as personal digital assistants, laptop computers, web browsers, and so on.

[0080] In the above embodiments, many software modules are described. Those skilled in the art will understand that these software modules can be provided in compiled or uncompiled form and can be picked up as a signal on a computer network or on a recording medium.

Supplied to base stations or to mobile phones. In addition, the functions performed by part or all of the software can be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred because it helps to update the base station 5 and the mobile phone 3 in order to update their functions.

[0081] Various other modifications are obvious to those skilled in the art, and therefore will not be described in further detail here.

[0082] The following is a detailed description of the manner in which the present invention can be implemented in the currently proposed 3GPP standard. Although the different features are described as being substantial or necessary, this may only be the case for the proposed 3GPP standard due to other requirements imposed by that standard, for example. Therefore, these statements should not be construed as limiting the present invention in any way.

[0083] 1 Introduction

[0084] In the recent RAN#3 meeting, the HNB registration process has been agreed and recorded in the Phase-2 document. The list of IEs sent from HNB to HNB-GW in the HNB registration request message is currently being discussed and some IE[2] have been agreed. This article discusses the HNB capability information to be included in the HNB registration request message.

[0085] It is assumed that the pre-release 8UE will still exist in the actual field for a long time. Therefore, the network must support both pre-release 8 and CSG UEs. Moreover, it has been agreed that the access control mechanism is mandatory at the HNB-GW and for pre-release 8 users, it is optional at the HNB. In addition, with the evolution of HNB deployment scenarios, it is recognized that HNB can utilize different access controls (ie, "open", "closed", and "hybrid") to operate. Such an agreement has already been made in SA1[1]. It is clear that if the HNB is open or hybrid access, for pre-release 8UE, mandatory access control at the HNB-GW is not required. Therefore, for the effectiveness of the extended work, the HNB-GW should know that the HNB access mode capability is necessary.

[0086] 2 Discussion

[0087] 4.1.2.1 Background

[0088] As mentioned in [1], three different access mode types are defined for HNB/HeNB.

[0089] Open access mode: HNB/HeNB operates as a normal cell (ie, a non-CSG cell).

[0090] Closed access mode: HNB/HeNB operates as a CSG cell. This is the mode defined in pre-release 8, which is a CSG cell in which only CSG members are allowed to access.

[0091] Hybrid access mode: CSG cells, where at the same time, non-CSG cells are allowed to access.

[0092] Although the LS reply [1] involves release 9, it specifically mentioned that if the timetable for pre-release 8 is not affected, operators will be happy to recommend the implementation of a hybrid access mode in release 8.

[0093] In order to avoid unnecessary access control at the HNB-GW when the HNB is open access or hybrid access, the HNBGW must know the access mode capabilities of the HNB.

[0094] This article discusses some possible solutions in the following sections.

[0095] 2.2 HNB registration process

[0096] The purpose of the HNB registration process is to register the HNB with the HNB-GW so that the HNB-GW can provide services and core network connectivity for the HNB.

[0097] Option 1: The HNB-GW may infer the access mode of the HNB based on the access control list IE received from the HNB. Therefore, it is proposed to include the optional access control list IE in the HNBAP HNB registration request message. If the HNB is in the closed access mode, it will include the optional access control list IE in the HNBAP registration request message; otherwise, if the HNB is in the open access mode, it will not include the optional access control list in the HNBAP HNB registration request message. Selected access control list IE. Therefore, the new access control list IE needs to be included in the HNBAP HNB registration request message.

[0098] 4.2 HNB Registration Request

[0099] The message is sent by the HNB to the HNB-GW to register the HNB at the HNB-GW.

[0100] Direction: HNBHNB-GW

[0101] The parameters are stored in I, I, IE type and semantic description || Factory [assigned

[0102]

<td></td><td>In sex</td><td>Encircle</td><td>reference</td><td></td><td>Boundary</td><td>Criticality</td>

<td>Message type</td><td></td><td></td><td>921</td><td></td><td>; Hanging</td><td>Refuse;</td>

<td>HNB identity li\B ί; 71</td><td>ΜΜ</td><td></td><td>9.2.20.2.3</td><td></td><td></td><td>Reject i</td>

<td>Click-in to create a table</td><td>Ο</td><td></td><td>9 2,χ</td><td>If IF., then the access mode of HNB is "closed type, otherwise it is "closed type" 1)</td><td>Yes</td><td>ignore</td>

<td>PLMN-ID</td><td>Μ</td><td></td><td>9.2.U</td><td></td><td></td><td></td>

<td>Cell-ID</td><td>Μ</td><td></td><td>92.25</td><td></td><td>Yes</td><td>Refuse.</td>

<td>LAC</td><td>Μ</td><td></td><td>9.2.1 )</td><td></td><td></td><td>Refuse</td>

<td></td><td>Μ.</td><td></td><td>9.2.12</td><td></td><td>Yes</td><td>Refuse;</td>

<td>SAC</td><td>Μ</td><td></td><td>9.2.13</td><td></td><td>rl</td><td>fit;</td>

[0103] Note 1: It is assumed that the HNB-GW will need to perform the same response for the operation of the "open" and "hybrid" access modes.

[0104] 9.2.x Access Control List

[0105]

<td>IE/group name</td><td>Existence.; Sex;</td><td>range</td><td>IE volume Bi and reference</td><td>Semantic description</td>

<td>Access control list</td><td></td><td>O..maxUEs</td><td></td><td>If the list is empty, consider Λ) ACL is empty.</td>

<td>&gt;IMSI</td><td>Μ</td><td></td><td>MSI9.2.10</td><td></td>

[0106] Note 1: The above option assumes that from the perspective of HNB-GW, open access HNB and hybrid access HNB are the same. Therefore, the hybrid mode HNB does not need to notify the HNB-GW of the ACL. It is unclear whether HNB-GW needs to have ACL for hybrid HNB in the standard. If the HNB-GW does need to have a hybrid HNB ACL, this option will not work.

[0107] Note 2: It is not clear whether it is possible to have a closed mode HNB without IMSI in the ACL in the specification. Assuming that the closed HNB cannot have an empty ACL, the access control list IE should be mandatory in the HNBAP HNB registration request message. In this way, if the HNB-GW receives an empty access control list IE in the HNBAP HNB registration request, the HNB is considered to be an open access mode; otherwise, if there is at least one entry in the access control list IE, the HNB It is considered a closed mode HNB.

[0108] Option 2: The HNB can indicate its capabilities in the HNBAP HNB registration request message during the HNB registration process by using the new HNB capability information IE.

[0109]

<td>parameter</td><td>Existence</td><td>range</td><td>ΙΕ type and reference</td><td>Semantic description</td><td>Criticality</td><td>Assigned criticality</td>

<td>Message type</td><td>Μ</td><td></td><td>9.2.1</td><td></td><td>Yes</td><td>Refuse</td>

<td>unb !'score</td><td>Μ</td><td></td><td>9.2.2</td><td></td><td>F?i </td><td>Refuse</td>

<td>HNB location</td><td>..Μ·</td><td></td><td>9.2.3</td><td></td><td>Yes</td><td>Refuse;</td>

<td>l-ΪΝΒ Capability information</td><td>Μ</td><td></td><td>9.2.x</td><td></td><td>Yes</td><td>Refuse</td>

<td>PLMN-ID</td><td>Ml</td><td></td><td>0214</td><td></td><td>Yes</td><td>Refuse</td>

<td>Community One Blood</td><td>Μ</td><td></td><td>9.2.25</td><td></td><td>Yes</td><td>Refuse</td>

<td>LAC</td><td>Μ</td><td></td><td>9.2.1 1</td><td></td><td>Yes</td><td></td>

<td>RAC:</td><td>Μ</td><td></td><td>9.2.12</td><td></td><td>Yes</td><td>Extinct</td>

<td>SAC</td><td>Μ</td><td></td><td>9.2.13</td><td></td><td>Yes</td><td></td>

[0110] 4.3 9.2. HNB capability information

[0111] The HNB Capability Information IE is sent from the HNB to the HNB-GW to provide information about the capabilities of the HNB.

[0112]

<td>IE/group name</td><td>Save volume</td><td></td><td>1E type and reference semantic description</td>

[0113]

<td></td><td></td><td></td><td></td>

<td>HNB Commitment Information</td><td></td><td></td><td>1</td>

<td>&gt;Access control type</td><td>Μ</td><td>f Open, closed, mixed)</td><td>: 1 :</td>

[0114] Option 3: OAM for HNB-GW stores the HNB access mode of each HNB. After successful HNB registration at the HNB-GW, the HNB-GW obtains the HNB access mode from the OAM database and performs access control accordingly.

[0115] 2.2 UE Registration Process

[0116] Based on the possible solutions mentioned in section 2.1, the HNB-GW will know the HNB access control mode during the HNB registration process. The HNB-GW will store this information for future use until either the HNB updates this information via another HNBAP process or deregisters itself. In Figure 6, the UE is used instead of the mobile phone (TM) 3. The following steps will be used to perform UE registration:

[0117] 12. After camping on the HNB, the UE initiates the initial NAS procedure by establishing an RRC connection with the HNB (for example,

LU process).

[0118] 13. The UE then sends an RRC initial direct transfer message, which carries a NAS-level identity (IMSI or

TMSI, P-TMSI, etc.) initial NAS message (for example, location update request message).

[0119] 14. The HNB initiates UE registration to the HNB-GW. If the HNB is in the closed/hybrid access mode, before starting the UE registration process, the HNB executes the NAS public ID process to obtain the UE IMSI, if the identity is not received in the RRC connection establishment or initial direct transfer message.

[0120] 15. The HNB can optionally perform access control based on the IMSI and the access control list.

[0121] 16.3G HNB attempts to register with the HNBAP UE by sending an HNBAP UE registration request containing the UE identity (IMSI in the case of closed/hybrid access HNB, or TMSI/IMSI in the case of open access mode). Register the UE on the GW.

[0122] 17. If the HNB is open access, the HNB-GW will accept UE registration and assign a context id (context-id) to the UE.

[0123] 18. If the HNB is in the closed access mode, the HNB-GW will perform access control for a specific UE trying to utilize the specific 3G HNB.

[0124] 19. If the HNB is in a hybrid access mode, the HNB-GW will perform access control for a specific UE trying to utilize the specific 3G HNB. If the access control is successful, the HNB-GW accepts the UE registration and assigns a context id to the UE. Think of the UE as a CSG UE, which can be used for purposes such as service differentiation. If the access control fails, the HNB-GW accepts the UE registration and assigns a context id to the UE. However, the UE is considered to be a non-CSG UE, which can be used for purposes such as service differentiation.

[0125] 20. If the HNB-GW accepts the UE registration request, the HNB-GW will send a UE registration acceptance message including a unique context id to the HNB.

[0126] 21. After the successful completion of the UE registration request message, HNB sends a connection message containing the RANAP initial UE message.

[0127] 22. After receiving the RUA connection message, the HNB-GW performs SCCP connection establishment towards the CN. HNB-GW can be

The SCCP CR message includes the initial UE message. Alternatively, the HNB-GW sends the initial UE message after the SCCP connection is successfully established.

[0128] 3 Conclusion

[0129] Introduce new HNB capability information in the HNBAP HNB registration request message.

[0130] This application is based on and claims the priority of British Patent Application No. 0820182.4 filed on November 4, 2008, the disclosure of which is incorporated herein by reference in its entirety.