Communications system

0001The present invention relates to mobile communication networks, but not exclusively, to networks operating in accordance with the 3GPP standard or its equivalents or derivatives. The present invention relates, but not exclusively, to interfaces between home base stations and home base station gateway devices.

0002This application is based on UK Patent Application No. 0820182.4 filed on November 4, 2008 and claims the benefit or priority from that patent application, the disclosure of which patent application is hereby incorporated by reference in its entirety. It is used for.

0003Under the 3GPP standard, NodeB (or eNB in LTE) is a base station where mobile devices connect to the core network via the base station. More recently, the 3GPP standards body has adopted an official architecture and has begun working on new standards for home base stations (HNB). HNB is sometimes referred to as HeNB when the home base station operates according to the LTE standard. However, for simplicity, the following description uses only HNB terminology. HNB provides in-home wireless coverage (3G / 4G) and connects to mobile networks via the HNB gateway (HNB-GW) over the appropriate public network (eg via an ADSL link to the Internet). To do. As part of this standard-setting process, a registration procedure has been agreed between HNB and HNB-GW.

0004It has also been agreed that an access control mechanism is mandatory for HNB-GW, while it is available as an option for pre-release 8 user equipment (UE) at HNB. In addition, it has been recognized that HNB can operate with different access control mechanisms: "open," "closed," and "hybrid," for different evolution scenarios of HNB deployment. As will be appreciated by those skilled in the art, mandatory access control in HNB-GW is not required for pre-release 8UE if the HNB is open. If the HNB is a hybrid, mandatory access control on the HNB-GW may not be required for the pre-release 8UE.

0005For the sake of efficiency of those skilled in the art, the invention is described in detail in the context of 3G systems, but the principle of the invention is that the mobile device or user equipment (UE) is one of several base stations. It can be applied to other systems that communicate. Corresponding elements of the system have been modified as needed.

<p num="0006"> Embodiments of the present invention aim to address one or more of the above problems by having HNB provide HNB-GW with capability information.</p>

<p num="0007"> According to one aspect, the invention is a method performed by a gateway device.<u style="single">Home base station</u>To receive a home base station registration request message containing data identifying whether the is operating in open access mode, closed access mode, or hybrid access mode, and<u style="single">Mobile communication device</u>The registration acceptance message includes a step of transmitting a registration acceptance message to the home base station when the registration is accepted, and the registration acceptance message provides a method including a context ID of the mobile communication device.</p><p num="0008"> The present invention also provides a corresponding gateway device. That is, according to another aspect, the present invention is a gateway device.<u style="single">Home base station</u>A means of receiving a home base station registration request message containing data identifying whether the is operating in open access mode, closed access mode, or hybrid access mode.<u style="single">Mobile communication device</u>If the registration is accepted, the registration acceptance message is provided with a means for transmitting the registration acceptance message to the home base station, and the registration acceptance message provides a gateway device including a context ID of the mobile communication device.</p><p num="0009"> Hereinafter, embodiments of the present invention will be described as examples with reference to the accompanying drawings.</p>

0010<figref num="1">It is a figure which shows typically the type of mobile communication system to which an embodiment is applicable.</figref><figref num="2">It is a block diagram of the mobile phone which forms the part of the system shown in FIG.</figref><figref num="3">It is a block diagram of a home base station which forms a part of the system shown in FIG.</figref><figref num="4">It is a block diagram of the home base station gateway which forms the part of the system shown in FIG.</figref><figref num="5">It is a timing diagram which shows the registration procedure for registering a home base station in a home base station gateway.</figref><figref num="6">It is a timing diagram which shows the registration procedure which is executed when a mobile phone registers with a home base station gateway.</figref>

0011Overview Figure 1 shows a mobile phone (MT) 3 user via a 3G wireless access network (RAN) base station 5, a wireless network controller 7, and a core telephone network 8 when the user is away from home 9. Can communicate with users (not shown), and when the user is at home, home base station (HNB) 11, Internet 13, home base station gateway (HNB-GW) 15, and core telephone network 8 A mobile (cellular) communication system 1 capable of communicating with another user (not shown) via the mobile (cellular) communication system 1 is shown schematically. The HNB 11 typically connects to the HNB-GW 15 via a suitable residential internet connection such as ADSL or cable connection.

0012Mobile phone FIG. 2 schematically shows the main components of the mobile phone 3 shown in FIG. As shown, the mobile phone 3 comprises a transmitter / receiver circuit 23 capable of operating to send and receive signals to and from the RAN base station 5 or HNB 11 via one or more antennas 25. As shown, the mobile phone 3 also includes a controller 27 that controls the operation of the mobile phone 3, which is connected to a transmitter / receiver circuit 23 and a speaker 29, a microphone 31, a display 33, and a keypad 35. Will be done. The controller 27 operates according to the software instruction stored in the memory 37. As illustrated, these software instructions include, among other things, the operating system 39 and the mobile phone registration module 41. In this embodiment, the mobile phone registration module 41 allows the user to select a home base station 11 to be registered by the mobile phone 3 when the user is at home or within the range of his HNB 11. It will be possible. This selection may be automatic or manually controlled by the user.

0013Home base station FIG. 3 is a block diagram showing the main components of the home base station (HNB) 11 shown in FIG. As illustrated, the HNB 11 is capable of operating to send and receive signals to and from the mobile phone 3 via one or more antennas 53 and signals to the HNB-GW 15 via the HNB-GW interface 55. It includes a transmitter / receiver circuit 51 that can operate to transmit and receive. The operation of the transmitter / receiver circuit 51 is controlled by the controller 57 according to the software stored in the memory 59. The software stored in the memory 59 includes, among others, the operating system 61, the base station registration module 63, and the telephone registration module 65. The base station registration module 63 can operate to register the HNB with the HNB-GW15, and the mobile phone registration module 65 can operate to register the mobile phone 3 with the mobile phone itself and with the HNB-GW15. ..

0014HNB gateway FIG. 4 is a block diagram showing the main components of the HNB gateway (HNB-GW) 15 shown in FIG. As shown, the HNB-GW 15 can operate to send and receive signals to and from HNB 11 via HNB interface 103 and to send and receive signals to and from core network 8 via core network interface 105. It is equipped with a transmitter / receiver circuit 101. The operation of the transmitter / receiver circuit 101 is controlled by the controller 107 according to the software stored in the memory 109. The software stored in memory 109 includes, among other things, the operating system 111, the HNB registration module 113, and the mobile phone registration module 115. The HNB registration module 113 can operate to control the registration of the HNB 11, and the mobile phone registration module can operate to control the registration of the mobile phone 3 and execute access control as needed.

0015In the above description, the mobile phone 3, the base station 5, and the HNB gateway 15 are described as having a plurality of separate modules (registration modules, etc.) for ease of understanding. These modules can be provided in this way, for example, for specific applications where existing systems must be modified to implement the invention, but other applications, such as features of the invention from the beginning. In systems designed with this in mind, these modules may not be identifiable as separate entities because they can be incorporated into the operating system or the entire code.

0016Access control As mentioned above, three different types of access modes are defined for HNB 11. Open access mode: The HNB operates as the normal cell, which allows any mobile phone 3 to make and receive calls through the normal cell. · Closed access mode: HNB operates as a Closed Subscriber Group (CSG) cell that only CSG members are allowed access to (this is the mode specified in Rel-8), and -Hybrid access mode: CSG cells that non-CSG members are allowed access to at the same time.

0017Although the hybrid access mode was designed for release 9, the operator would recommend that the hybrid access mode be implemented in release 8 if it does not affect the release 8 timescale.

0018As you can see, for HNB 11 operating in closed access mode, HNB-GW15 performs access control to limit access to core network 8 to mobile phones 3 belonging to their respective subscriber groups. On the other hand, in the case of HNB11 operating in open mode, it is not necessary for HNB-GW15 to execute access control, and in the case of HNB11 operating in hybrid mode, HNB-GW15 is access control. May not need to be executed. Therefore, in this embodiment, the HNB 11 notifies the HNB-GW 15 of the access mode capability of the HNB 11, thereby determining whether the HNB-GW 15 implements access control for the mobile phone 3 seeking registration through the HNB 11. can do.

0019This describes a plurality of techniques for the HNB 11 to signal the access mode capability of the HNB to the HNB-GW15.

0020HNB registration procedure The purpose of the HNB registration procedure is to register the HNB 11 with the HNB-GW 15 so that the HNB-GW can provide services and core network connectivity for the HNB 11. The overall process is shown in Figure 5. As shown, the process involves HNB 11 sending an HNB registration request message to HNB-GW and, in response, HNB-GW 15 sending an HNB registration acceptance message. There are many different options for signaling the access mode capability of HNB11 to HNB-GW15.

0021Option 1: HNB-GW15 can 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 registration request message sent from HNB11 to HNB-GW15. When the HNB 11 is in closed access mode, the HNB includes an optional access control list IE in the HNB AP registration request message. Otherwise, if the HNB is in open access mode or hybrid access mode, the HNB does not include the optional access control list IE in the HNBAP HNB registration request message. Therefore, the new access control list IE must be included in the HNBAP HNB registration request message.

0022<tables num="1"><img id="000002" he="88" wi="158" file="JP5892353B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>

0023This message is transmitted by the HNB 11 to the HNB-GW 15 in order to register the HNB 11 in the HNB-GW 15.

0024Direction: HNB HNB-GW

0025<tables num="2"><img id="000003" he="40" wi="159" file="JP5892353B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>

0026Note 1: The above options assume that the HNB-GW15 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-GW15 about the access control list of the hybrid HNB. doing. At present, it is not clear whether this assumption is valid in the standard. As a result, if the HNB-GW15 does not have a hybrid HNB access control list, the option will not work.

0027Note 2: In the current standards document, it is not clear whether it is possible to have a closed mode HNB that does not have an IMSI (International Mobile Subscriber Identity) in the access control list (ie empty access control list). If it is assumed that a closed HNB cannot have an empty access control list, the presence of an access control list IE (rather than an option as suggested above) must be required in the HNBAP HNB registration request message. .. Thus, if the HNB-GW15 receives an empty access control list IE in the HNBAP HNB registration request, the HNB-GW15 can infer that the HNB11 is in open access mode, otherwise at least one. If the entry is in the access control list IE, HNB-GW can determine that HNB 11 is in closed mode HNB.

0028Option 2: HNB11 can use the new HNB Capability Information IE to use the new HNB Capability Information IE in the HNBAP HNB registration request message during the HNB registration procedure, the HNB capability (open, closed, or (Hybrid) can be shown in HNB-GW15.

0029<tables num="3"><img id="000004" he="70" wi="159" file="JP5892353B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>

00309.2.y HNB capability information The HNB capability information IE is transmitted from the HNB to the HNB-GW to provide information on the capability of the HNB.

0031<tables num="4"><img id="000005" he="26" wi="158" file="JP5892353B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>

0032Option 3: The OAM (Operation and Maintenance) function of HNB-GW15 remembers the HNB access mode for each HNB 11. If the HNB registration is successful in the HNB-GW15, the HNB-GW15 retrieves the HNB access mode from the OAM database (not shown) and executes access control accordingly.

0033UE registration procedure Based on the possible options described above, the HNB-GW15 knows the HNB access control mode during the HNB registration procedure. HNB-GW15 stores this information for further use until HNB11 cancels its registration or updates this information via another HNBAP procedure. In one embodiment, mobile phone registration (shown in FIG. 6) is performed using the following steps. 1. When the mobile phone (MT) 3 camps on HNB11, it initiates an initial NAS procedure (eg LU procedure) by establishing an RRC connection with the HNB11. 2. The MT3 then sends an RRC initial direct forwarding message carrying an initial NAS message (eg, location update request message) with a NAS level identity (IMSI or TMSI, P-TMSI, etc.). 3. HNB11 starts the registration of MT3 with HNB-GW15. When the HNB 11 is in closed access mode or hybrid access mode, the HNB is a mobile phone to obtain such an identity if the mobile phone 3's IMSI is not received in the RRC connection establishment message or initial direct transfer message. Perform the NAS common ID procedure before starting the registration procedure. 4. HNB11 can optionally perform access control based on the IMSI and access control list. 5.3G HNB11 attaches mobile phone 3 to HNB-GW15 by sending an HNBAP UE registration request containing the mobile phone identity (IMSI for closed / hybrid access HNB or TMSI / IMSI for open access HNB). Attempt to register with. 6. When HNB11 is in open access mode, HNB-GW15 accepts mobile phone 3 registration and assigns a context ID to mobile phone 3. 7. If HNB11 is in closed access mode, HNB-GW15 will be in that particular 3G Perform access control for a particular mobile phone 3 attempting to use HNB. 8. When the HNB 11 is in hybrid access mode, the HNB-GW15 performs access control for a particular mobile phone 3 that attempts to utilize that particular 3G HNB. If the access control is successful, the HNB-GW15 accepts the registration of the mobile phone 3 and assigns the context ID to the mobile phone 3. In this case, mobile phone 3 is considered a CSG mobile phone. This information is stored and can be used for purposes such as service differentiation. On the other hand, even if the access control fails, the HNB-GW15 accepts the registration of the mobile phone 3 and assigns the context ID to the mobile phone 3. However, in this case, mobile phone 3 is considered a non-CSG mobile phone (the information is stored and can be used for purposes such as service differentiation). 9. When HNB-GW accepts the mobile phone registration request, it sends a UE registration acceptance message containing a unique context ID to HNB. 10. When HNB11 succeeds in completing the mobile phone registration request message, it sends a connection message including the RANAP initial UE message. 11. When HNB-GW15 receives the RUA connection message, it executes SCCP connection establishment to core network 8. HNB-GW15 can include the initial UE message in the SCCP CR message. Alternatively, HNB-GW15 sends an initial UE message when it succeeds in establishing an SCCP connection.

0034Modified and alternative forms A detailed embodiment has been described above. As one of ordinary skill in the art will understand, multiple modifications and substitutions can be made to the above embodiments, still benefiting from the invention embodied in the embodiments.

0035In the above embodiments, mobile phone based communication systems have been described. The signaling techniques described in this application can be used for other communication systems, as will be appreciated by those skilled in the art. Other communication nodes or communication devices can include, for example, user devices such as personal digital assistants, laptop computers, web browsers and the like.

0036In the above embodiments, a plurality of software modules have been described. As those skilled in the art will understand, those software modules can be provided in both compiled and uncompiled formats, base stations or mobiles as signals over a computer network or on recording media. Can be supplied to the telephone. In addition, the functions performed by parts or all of this software may be performed using one or more dedicated hardware circuits. However, the use of the software module is preferred because it facilitates updating the base station 5 and the mobile phone to update the functions of the base station 5 and the mobile phone 3.

0037Various other modifications are apparent to those skilled in the art and will not be described in further detail here.

0038The following is a detailed description of how the invention can be practiced in the currently proposed 3GPP standard. Although various features have been described as important or essential, this may only apply to the proposed 3GPP standard, for example due to other requirements imposed by the standard. Therefore, these expressions should not be construed as limiting the invention in any way.

00391 Introduction During the recent RAN # 3 meeting, the HNB registration procedure was agreed and incorporated into the Stage 2 document. The list of IEs sent by HNB to HNB-GW in the HNB registration request message is currently under discussion and some IE [2] have already been agreed. This contribution considers the HNB capability information contained in the HNB registration request message.

0040Pre-release 8UE is expected to remain in the field for quite some time. Therefore, the network must support Prerelease 8 and CSG UE at the same time. It has already been agreed that the access control mechanism is mandatory for HNB-GW, whereas it is optional for pre-release 8UE HNB. In addition, in the evolutionary scenarios of HNB deployments, it is recognized that HNB can operate with a variety of access control mechanisms: "open," "closed," and "hybrid." Such an agreement has already been made in SA1 [1]. As is clear, mandatory access control in HNB-GW is not required for pre-release 8UE if the HNB is open access or hybrid access. Therefore, it is already necessary that the HNB access mode capability must be known to the HNB-GW in order to function efficiently.

00412 Consideration 4.1.2.1 Background As mentioned in [1], three types of access modes are specified for HNB / HeNB. -Open access mode: HNB / HeNB operates as a normal cell, that is, a non-CSG cell. -Closed access mode: HNB / HeNB operates as a CSG cell. This is the mode specified in REl-8. This is a CSG cell that only CSG members are allowed access to. -Hybrid access mode: CSG cells that are allowed access to non-CSG cells at the same time.

0042LS Answer [1] mentions Release 9, but clearly states that the operator wants to recommend that hybrid access mode be implemented in Release 8 as long as it does not affect the time scale of Release 8. Has been done.

0043To avoid unnecessary access control in the HNB-GW when the HNB is open access or hybrid access, the HNB-GW must know the access mode capability of the HNB.

0044This paper considers some of the possible solutions in the sections below.

00452.2 HNB registration procedure The purpose of the HNB registration procedure is to register the HNB with the HNB-GW and allow the HNB-GW to provide services and core network connectivity to the HNB.

0046Option 1: The HNB-GW can infer the access mode of the HNB based on the access control list IE received from the HNB. Therefore, it is suggested to include the optional access control list IE in the HNBAP HNB registration request message. When the HNB is in closed access mode, the HNB includes an optional access control list IE in the HNB AP registration request message. Otherwise, if the HNB is in open access mode, the HNB does not include the optional access control list IE in the HNBAP HNB registration request message. Therefore, the new access control list IE must be included in the HNBAP HNB registration request message.

00474.2. HNB registration request This message is transmitted by the HNB to the HNB-GW in order to register the HNB in the HNB-GW.

0048Direction: HNB HNB-GW

0049<tables num="5"><img id="000006" he="88" wi="159" file="JP5892353B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>

0050Note 1: HNB-GW is expected to require the same processing for the "open" and "hybrid" access modes of operation.

0051<tables num="6"><img id="000007" he="37" wi="159" file="JP5892353B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>

0052Note 1: The above options assume that the open access HNB and the hybrid access HNB are the same from the perspective of HNB-GW. Therefore, it is assumed that the hybrid mode HNB does not need to notify the HNB-GW about the ACL. At present, it is not clear whether HNB-GW needs to have a hybrid HNB ACL in the standard. This option does not work if the HNB-GW needs to have a hybrid HNB ACL.

0053Note 2: It is not clear in the specification whether it is possible to have a closed mode HNB in the ACL that does not have an IMSI. If it is assumed that a closed HNB cannot have an empty ACL, the access control list IE must be present in the HNBAP HNB registration request message. Therefore, when the HNB-GW receives the empty access control list IE in the HNBAP HNB registration request, the HNB is regarded as the open access mode. Otherwise, an HNB is considered to be a closed mode HNB if at least one entry is in the access control list IE.

0054Option 2: HNB can indicate the capabilities of the HNB in the HNBAP HNB registration request message during the HNB registration procedure by using the new HNB capability information IE.

0055<tables num="7"><img id="000008" he="51" wi="158" file="JP5892353B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>

00564.3 9.2.y HNB capability information The HNB capability information IE is transmitted from the HNB to the HNB-GW to provide information on the capability of the HNB.

0057<tables num="8"><img id="000009" he="28" wi="159" file="JP5892353B2_D0001.tif" img-format="tif" img-content="drawing" /></tables>

0058Option 3: HNB-GW OAM remembers HNB access mode for each HNB. If the HNB registration is successful in the HNB-GW, the HNB-GW retrieves the HNB access mode from the OAM database and executes access control accordingly.

00592.2 UE registration procedure Based on the possible solutions described in Section 2.1, HNB-GW knows the HNB access control mode during the HNB registration procedure. HNB-GW stores this information for further use until HNB cancels its registration or updates this information via another HNBAP procedure. In FIG. 6, UE is used instead of mobile phone (TE) 3. UE registration is performed using the following steps. 12. When the UE camps on the HNB, it initiates the initial NAS procedure (eg LU procedure) by establishing an RRC connection with the HNB. 13. The UE then sends an RRC initial direct forwarding message carrying an initial NAS message (eg, location update request message) with a NAS level identity (IMSI or RMSI, P-TMSI, etc.). 14. HNB initiates UE registration with HNB-GW. When the HNB is in closed / hybrid access mode, the HNB is UE if the IMSI is not received in the RRC connection establishment message or the initial direct transfer message. To obtain the IMSI, perform the NAS common ID procedure before starting the UE registration procedure. 15. HNB can optionally perform access control based on the IMSI and access control list. 16.3G HNB registers the UE with the HNB-GW by sending an HNBAP UE registration request containing the UE identity (IMSI for closed / hybrid access HNB or TMSI / IMSI for open access HNB). Try to do that. 17. If HNB is in open access mode, HNB-GW accepts UE registration and assigns a context ID to the UE. 18. When the HNB is in closed access mode, the HNB-GW enforces access control for the particular UE that attempts to utilize that particular 3G HNB. 19. If the HNB is in hybrid access mode, the HNB-GW will be in that particular 3G Perform access control on specific UEs that attempt to utilize HNB. If access control is successful, HNB-GW accepts the UE registration and assigns a context ID to the UE. UEs are considered CSG UEs. It can be used for purposes such as service differentiation. Even if access control fails, HNB-GW accepts UE registration and assigns a context ID to the UE. However, UEs are considered non-CSG UEs, which can be used for purposes such as service differentiation. 20. When HNB-GW accepts a UE registration request, it sends a UE registration acceptance message containing a unique context ID to HNB. 21. When HNB succeeds in completing the UE registration request message, it sends a connection message containing the RANAP initial UE message. 22. When HNB-GW receives the RUA connection message, it executes SCCP connection establishment to CN. HNB-GW is SCCP The initial UE message can be included in the CR message. Alternatively, HNB-GW sends an initial UE message when it succeeds in establishing an SCCP connection.

00603 Conclusion HNBAP Introduce new HNB capability information IE to HNB registration request message.

0061Hereinafter, aspects of this embodiment will be described.

0062According to one aspect, the invention is a method performed by a gateway device, in which a step of receiving a request to register a mobile communication device from a home base station and said home base station is in open access mode home. When the step of determining whether the home base station is a base station or the closed access mode home base station and the determination step determine that the home base station is a closed mode home base station, the access of the mobile communication device When the control is executed and the access control is successful, the step of registering the mobile communication device in the gateway device and the step of determining the determination indicate that the home base station is an open mode home base station. A step of registering the mobile communication device in the gateway device without executing the access control, and a step of transmitting a registration acceptance message to the home base station when the registration of the mobile communication device is accepted. Provide methods, including.

0063In one embodiment, the gateway is either an open access mode home base station or a closed access mode home base station, based on information received from the home base station, eg, in the registration request. Determine if it is a station. The information can be specified by the presence or absence of optional elements in the home base station registration request. For example, if the access control list exists depending on the presence or absence of the access control list in the home base station registration request, the gateway device determines that the home base station is a closed access home base station, and the access control list. If does not exist, the gateway device determines that the home base station is an open access home base station.

0064Alternatively, the information can be specified by the content of the essential elements in the home base station registration request. For example, it may be specified by the presence or absence of an entry in the required element. In one embodiment, the information is defined by the presence or absence of an entry in the required access control list in the home base station registration request, and if the access control list contains one or more entries, 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.

0065The access mode of the home base station can be open, closed, or hybrid, and the gateway makes the hybrid access mode home base station an open access mode home base station or a closed access mode home base station, or open. It can be treated as a home base station in both access mode and closed access mode. In one embodiment, the essential 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.

0066When the home base station is a hybrid access home base station, the method executes access control of the mobile communication device, and when the access control is successful, the mobile communication device is registered in the gateway device and the mobile communication device is registered. The step of generating data identifying that the communication device is part of a closed subscriber group associated with the home base station and, if the access control is unsuccessful, register the mobile communication device with the gateway device. And can include the step of generating data identifying that the mobile communication device is not part of a closed subscriber group associated with the home base station.

0067In another embodiment, the gateway is either 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 operations and management database. Judge whether it is.

0068The present invention is a method performed by a home base station, in which the gateway device is provided with data that identifies whether the home base station is an open access mode home base station or a closed access mode home base station. A step of transmitting, a step of receiving a request from the mobile communication device, a step of transmitting a registration request of the mobile communication device to the gateway device, and a step of transmitting the registration of the mobile communication device to the gateway device, and registration from the gateway device when the registration of the mobile communication device is accepted. It also provides a method, including, and a step of receiving an acceptance message.

0069The home base station may include the data in a home base station registration request message transmitted by the home base station.

0070In 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 can be defined by the presence or absence of an access control list in the home base station registration request, and when the home base station is a closed access home base station, the home access base station is the home base station. When the access control list is included in the registration request and 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.

0071In another embodiment, the data can be defined by the content of the essential elements in the home base station registration request. For example, the data can be defined by the presence or absence of an entry within the required 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, and if the home base station is a closed access home base station, the home access base station is said to be said. If the home base station contains an entry in the access control list in the home base station registration request and the home base station is an open access home base station, the home access base station is in the access control list in the home base station registration request. Does not contain an entry in.

0072In a further embodiment, the essential element can specify 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.

0073The present invention also provides corresponding gateway devices and home base stations. The present invention also provides a message containing data identifying whether the home base station is an open access mode or closed access mode home base station.

0074The present invention relates to the corresponding computer program or computer program product for execution on the corresponding device, the device itself (user device, node, or component thereof), and the device for all disclosed methods. Provide a way to update.