Description
Title of Invention: GATEWAY, COMMUNICATION SYSTEM,
METHOD OF CONTROLLING GATEWAY, AND COMPUTER
READABLE MEDIUM THEREFOR
Technical Field
LOO011 Exemplary embodiments of the present inventioil relate to a gateway, a base station,
a communication node, a co~nmunication system, and inethods of controlling the
gateway, the base station and the communication node. In particular, exemplary einbodi~
nentsr elate to a technique to use a feinto system defined by 3GPP (3rd
Generation Pai-tnership Project) so as to realize remote IP (Internet Protocol) access
from a macro network.
Background Art
[0002] The above-mentioned felnto systeln is the genelic term for access systems which
include a Hoine Node B (HNB), a Home evolved Node B (HeNB), and a Gateway
(HNB-GW andlor HeNB-GW).
[0003] The HNB is a small-sized radio base station which can be installed within end-user's
premises or the like, and connects a mobile station (also referred to as User Equipment,
or UE) compatible with a Universal Mobile Telecommunications System (UMTS)
radio system in the 3GPP to a core network of a mobile operator through a public
network such as a broadband IP backhaul. Fig. 1 shows a configuratioil of a cominunication
systeln where four units of HNBs 20-1 to 20-4 (hereinafter collectively
referred to using just reference numeral "20") are incoiporated into a core netwo1.k
through a broadband IP backhaul 50, so that a UE 10 is connected to the core network.
[0004] The HNB-GW accommodates a plurality of HNBs connected through the public
network, and relays traffic between each HNB and communication 11odes such as a
Mobile Switching Centre (MSC), a Serving GPRS (General Packet Radio Service)
Support Node (SGSN), a Media Gateway (MGW), and a Gateway GPRS Support
Node (GGSN), which form the core network. In the example of Fig. I, a HNB-GW 60
relays traffic between each of the HNBs 20-1 to 20-4 and an SGSN 70, so that the UE
10 is connected to a Packet Data Network (PDN) 90 through a GGSN 80.
LO005 1 The HeNB is a small-sized radio base station which can be installed within end-user's
premises or the like as with the HNB, and coni~ectsa UE compatible with a Long Teiln
Evolutioil (LTE) radio system in the 3GPP to the core network of the mobile operator
through the public network such as the broadband IP backhaul. Fig. 8 shows a configuration
of a communication system where four units of HeNBs 120-1 to 120-4
(hereinafter, also collectively referred to by using a reference numeral "120") are incoiporated
into a core network through a broadband IP backhaul 150, so that a UE 110
is connected to the core network.
100061 The HeNB-GW accolninodates a plurality of HeNBs connected through the public
network, and relays traffic between each HeNB and comm~~nicationno des such as a
Mobility Management Entity (MME). a Serving Gateway (S-GW) and a PDN Gateway
(P-GW), which form the core network. In the example of Fig. 8, a HeNB-GW 160
relays traffic between each of the HeNBs 120-1 to 120-4 and each of an MME 170
and an S-GW 171, so that the UE 110 is connected to a PDN 190 through a P-GW 180.
[0007] Note that details of the HNB, the HeNB, the HNB-GW, the HeNB-GW, the UE, the
MSC, the MGW, the SGSN, the MME, the S-GW, the P-GW and the PDN are defined
in various portions of 3GPP specifications including the following which are incorporated
herein by the following specific references: Non-patent literature 1, TS
22.220, TS 25.467, TS 23.002, TS 23.060, and TS 36.300.
[0008] Ful-ther, Non-patent literature 1 standardizes a Local IP Access (LIPA) function. This
is a function for enabling a UE which camps on an HeNB to access a local network in
which the HeNB is installed. Specifically, a Local Gateway (L-GW) which has the
function equivalent to the P-GW is built in the HeNB. On demand from the UE,
packets oi-iginated from the UE are directly muted within a local IP network to which
the HeNB belongs through the L-GW functioll in the HeNB. I11 an example shown in
Fig. 15, L-GWs 330-1 and 330-2 (hereinafter, also collectively referred to by using a
reference numeral "330") are built in HeNBs 120-1 and 120-2 among HeNBs 120-1
to 120-3 which belong to a local IP network 130.
[0009] Similarly, in the communication system employing the UMTS radio system, the
HNB illcludes an L-GW function which has the finnction equivalent to the GGSN, so
that the LIPA function can be realized. 111 an example shown in Fig. 16, L-GWs 230-1
and 230-2 (hereinafter, also collectively referred to by using a reference numeral
"230") are built in HeNBs 20-1 and 20-2 among HNBs 20-1 to 20-3 which belong to
a local IP network 30.
[0010] On the other hand, the above-inentioned macro network is typically the generic term
for access systems which include a RAN (Radio Access Network).
[001 11 Fig. 17 shows a network configuration for access from the inacro network to the
PDN in the communication system einploying the UM'TS radio system. The UE 10
wirelessly connects to a Node B (NB) 420, and thus is connected to the PDN 90
through a Radio Network Controller (RNC) 430, the SGSN 70 and the CCSN 80. The
RAN is foi~nedb y the NB and the RNC. The NB is a radio base station which is
installed outdoo~.so r the like by the mobile operator, and connects the UE compatible
with the UMTS radio system to the core network. The RNC is a control device which
accommodates a plurality of NBs and controls radio resources between each NB and
the UE.
LO01 21 Ful-ther, Fig. 18 shows a network configuration for access from the macro network to
the PDN in the communication systein elnployiilg the LTE radio system. The UE 110
wirelessly collilects to an evolved Node B (eNB) 520, and thus is connected to the
PDN 190 through the S-GW 17 1 and the P-GW 180. The RAN is foilned by the eNB.
The eNB is a radio base station which is installed outdoors or the like by the mobile
opesator as with the NB, and connects the UE compatible with the LTE radio system to
the core network.
[0013] Note that the coverage of a cell (generally, refessed to as "macro cell") foimed by
each of the NB and the eNB is large, so that the number of UEs which can be accoimodated
in the cell is large. On the other hand, the coverage of a cell formed by
each of the above-mentioned HNB and HeNB is quite smaller than that formed by each
of the NB and the eNB. Therefore, this cell is generally refemed to as "fernto cell".
[0014] Incidentally, in Non-patent literature 2, it has been proposed that the LIPA fuilctioll
be used for remotely accessing, fsom the macro network, a local 1P network to which
the HeNBIHNB is connected. In the following explanation, this access is sefersed to as
"remote IP access". The L-GW has the function equivalent to the P-GW and the
GGSN. Therefore, the remote IP access can be realized in a case where when a UE
attaching to the macro network requests access to the local 1P network, the UE can
connect to the L-GW having the function equivalent to the GGSN and the P-GW
through the SGSN or the MMEIS-GW, as in the case of noimal packet communication.
Fig. 19 shows a network configuration in a case of realizing the remote IP access in the
commui~ications ystein employing the UMTS radio system. Fig. 20 shows a network
configuration in a case of realizing the remote IP access in the communication systein
employing the LTE radio system.
Citation List
Non Patent Literature
[0015] NPL 1: 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhailcelnents for
Evolved Universal Tessestrial Radio Access Network (E-UTRAN) access (Release
lo)", V10.3.0,2011-03, Clause 4.3.16, pp. 39 to 40
NPL 2: 3GPP TSG-SA WG1 Meeting #51, S1-102154, "Remote Local IP access"
Summary of Invention
Technical Problem
[0016] However, there is a problem that it is difficult to realize the remote IP access.
[0017] Specifically, in order to connect a comlnunication pass from the SGSN or the S-GW
to the L-GW, it is necessary to transinit a control message for establishing the coinmunication
path. Typically, in order to establish a coinmunicatioi~p ath to the GGSN or
the P-GW, the SGSN or the S-GW delives an IP address of a desti~lationG GSN or PGW
by using an Access Point Name (APN) designated as the destinatioil by a UE, and
trails~nitsa control message to the derived IP address. However, there are many cases
where the HNB or the HeNB itself is co~lnectedto the local 1P network and thus a
private IP address is assigned to the HNB or the HeNB. Therefore, it is not possible to
directly transmit the coiltrol message from the SGSN or the S-GW to the HNB or the
HeNB. Even uilder circu~nstancesw here a public IP address is assigned to the HNB or
the HeNB, there is a high possibility that the 1P address is vaiiable. Therefore, it is
difficult for the SGSN or the S-GW to constantly derive the IP address of the HNB or
the HeNB.
[OO18] Accordingly, an object of certain exemplary embodiments is to more easily realize
remote IP access.
Solution to Problem
[OOI 91 In order to achieve the above-mentioned object, a first exemplary aspect of certain
exemplaiy embodiments is a gateway that establishes a secure tunnel between the
gateway and each of a plurality of base stations through a public network. This
gateway includes: a first comnuilicator that com~nu~licatewsi th each of the base
stations through the secure tunnel; a second comlnu~licatorth at com~nu~licatewsi th a
core network; and a co~ltrolletrh at coiltrols the first and second co~mn~~nicatto rs
relay traffic between the core network and each of the base stations. The controller is
coilfigured to: store an APN supported by each of the base stations, when each of the
base stations includes a function of routing traffic received through the secure tunnel
into a local network to which each of the base stations belongs; and transfer, when
receiving from the core network a first inessage for establishing a coinm~u~icatiopnat h
to any one of the plurality of base statioils from a mobile station attaching to a RAN
co~lnectedto the core network, the first message to a base station corresponding to a
first APN included in the first message.
[0020] Further, a second exeinplaly aspect of certain exemplaiy e~nbodi~ne~isl tas b ase
station that is incorporated illto a core network through a public network. This base
station includes: a communicator that establishes a secure tunnel between the base
station and a gateway through the public network to communicate with the gateway; a
muter that routes traffic received through the secure tunnel into a local network to
which the base station belongs; and a controller that coi~trolsth e coinmuilicator and the
router. The communicator is configured to receive, from the gateway, a first lnessage
for establishing a communication path to the base station from a mobile station
attaching to a RAN connected to the core network. The controller is configured to
cause, when the first message is received, the router to route traffic origi~latedf rom the
inobile station into the local network.
[0021] F~u-thera, third exemplary aspect of certain exemplary embodiments is a commullicatioll
node that is installed in a core network. This colmnullicatioll node includes: a
first coinmunicator that communicates with a gateway establishi~~ag s ecure tullllel
between the gateway and each of a plurality of base stations through a public network;
a second comlnunicator that commn~lllicatest.h rough a RAN connected to the core
network, with a mobile station attaching to the RAN; and a controller that controls the
first and second communicators. The secolld communicator is configured to receive,
froin the inobile station, a first message for requesting access to one base station
among the plurality of base stations. The controller is configured to: generate a second
message for establishing a communication path from the mobile station to the one base
station, and set in the second message an APN included in the first message; and
transinit the second message to the gateway.
[0022] Fui-ther, a fourth exemplary aspect of cel-tain exemplary ernbodilnellts is a communication
system including: a cominullication node that is installed in a core network;
and a gateway that establishes a secure tunnel between the gateway and each of a
plurality of base stations through a public network. The commullication node is
collfigured to: receive, through a RAN conllected to the core network, from a inobile
station attaching to the RAN, a first message for requesting access to one base station
among the plurality of base stations; generate a second message for establishing a coinlnunication
path from the mobile station to the one base station, and set in the second
message an APN included in the first message; and transmit the second message to the
gateway. The gateway is configured to: store an APN supported by each of the base
stations, when each of the base stations includes a function of routing traffic received
thmugh the secure tuilnel into a local network to which each of the base stations
belongs; and transfer, when the second message is received from the colmnunicatioll
node, the second message to a base station coil-esponding to a first APN included in the
secoild inessage.
[0023] F-c~i-thear, fifth exemplary aspect of cel-tain exemplary embodiments is a inethod of
controlling a gateway that establishes a secure tunnel between the gateway and each of
a plurality of base stations through a public network. This inethod includes: storing an
APN supported by each of the base stations, when each of the base stations iilcludes a
function of routing traffic received through the secure hlnnel into a local network to
which each of the base stations belongs; and transferring, when receiving from the core
network a first message for establishing a corninul~icatiolpl ath to any one of the
plurality of base stations from a mobile station attaching to a RAN connected to the
core network, the fist message to a base station corresponding to a first APN included
in the first message.
[0024] Further, a sixth exemplary aspect of eel-tain exemplary embodiments is a inethod of
controlling a base station that is i~lcorporatedin to a core network through a public
network. This inethod includes: establishing a secure tunnel between the base station
and a gateway through the public network to colnmullicate with the gateway;
receiving. from the gateway, a first message for establishing a communicatioi~p ath to
the base station from a inobile station attaching to a RAN connected to the core
network: and routing, when the first message is received, traffic received from the
inobile station through the secure tunnel into a local network to which the radio base
station belongs.
[0025] Fu~.thermore, a seventh exemplary aspect of certain exemplary embodiments is a
method of controlling a communication node that is installed in a core network. This
inethod includes: receiving, through a RAN connected to the core network, from a
mobile station attaching to the RAN, a first message for requesting access to one base
station among a plurality of base statioils that are incol-porated into the core network
through a public network; generating a second message for establishing a communication
path from the inobile station to the one base station, and setting in the second
message an APN included in the first message; and transmitting the second message to
a gateway that establishes a secure tunnel between the gateway and each of the base
stations through the public network.
Advantageous Effects of Invention
[0026] According to cei-tain exelnplaiy embodiments, it is possible to more easily realize
remote TP access.
Brief Description of Drawings
[0027] [fig. l]Fig. 1 is a block diagram showing a configuration example of a communication
system to which a gateway, a base station and a communication node accordiilg to a
first exemplary embodiment are applied.
Ifig.21Fig. 2 is a block diagrain showing an example of a network configuratioil in a
case of realizing remote IP access in the communication system according to the first
exelnplaiy embodiment.
Lfig.31Fig. 3 is a block diagrain showing a coilfiguration example of the gateway
according to the first exempla~ye mbodiinent.
Cfig.4lFig. 4 is a block diagram showing a coilfiguration example of the base station
according to the first exeinplary embodiment.
[fig.S]Fig. 5 is a block diagram showing a configuration example of the communication
node according to the first exemplary embodiinent.
[fig.h]Fig. 6 is a sequence diagram showing an example of procedures to register a
base station in the gateway according to the first exemplary embodiment.
[fig.7]Fig. 7 is a sequence diagram showiilg an exainple of procedures to establish a
co~mnui~icatiopnat h in the gateway, the base station and the colnlnunicatioll node
according to the first exeinplaiy embodiment.
Lfig.8JFig. 8 is a block diagrain showing a configuration example of a communication
systeln to which a gateway, a base station and a coinmunication node according to a
fifth exelnplary embodiment of the invention are applied.
[fig.9]Fig. 9 is a block diagram showing an exainple of a network configuration in a
case of realizing reinote IP access in the communication system according to the fifth
exemnpla~ye rnbodimnent.
[fig. 1OlFig. 10 is a block diagram showing a configuration example of the gateway
according to the fifth exemplary embodiment.
[fig. 111Fig. 11 is a block diagram showing a configuration exainple of the base station
according to the fifth exemplary embodiment.
[fig. 12lFig. 12 is a block diagram showing a configuration example of the communication
node according to the fifth exemplary embodiment.
[fig. 13lFig. 13 is a sequence diagram showing an example of procedures to register a
base station in the gateway according to the fifth exemplaly embodiment.
[fig. 141Fig. 14 is a sequence diagrain showing an example of procedures to establish a
communicatioi~p ath in the gateway, the base station and the communication node
according to the fifth exemplary embodiment.
[fig. 151Fig. 15 is a block diagram showing an example of realizing a LIPA function in
a typical co~nrnunications ystem employing an LTE radio system.
[fig. 16lFig. 16 is a block diagram showing an exalnple of realizing a LIPA function in
a typical colmnunication system elnploying a UMTS radio system.
[fig. 17lFig. 17 is a block diagram showing an exainple of a network configuration for
access from a macro network to a PDN in the typical coimnunication systeln
employing the UMTS radio system.
[fig. 18lFig. 18 is a block diagram showing an exainple of a network configuration for
access from a macro network to a PDN in the typical cominunication system
employing the LTE radio system.
[fig.l9]Fig. 19 is a block diagram showing an exainple of a network coilfiguration in a
case of realizing reinote IP access in the typical co~ninunications ysteln elnploying the
UMTS radio system.
[fig.20]Fig. 20 is a block diagram showing an example of a network configuration in a
case of realizing remote IP access in the typical cominunication systeln employing the
LTE radio system.
Description of Embodiments
[0028] Hereinafter, first to eighth exeinplaly elnbodiinents of a gateway and a communication
node according to certain exemplary embodiments, and a co~n~nunication
system to which these gateway and coln~nunication~ol de are applied will be described
with reference to Figs. 1 to 14. Note that in the drawings, the same colnponents are
denoted by the same reference nulnerals and duplicated explaiiation is omitted as
necessary for clarity of explanation. The word "exemplary" is used herein to mean
"serving as an example, instance, or illustration". Any embodiment described herein as
"exemplary" is not llecessakly to be construed as prefell-ed or advantageous over other
einbodi~nents.
LO0291
As shown in Fig. 1, a communication system according to this exelnplary embodiment
includes an HNB-GW 60 and an SGSN 70.
[0030] Among them, the HNB-GW 60 relays traffic between a core network including the
SGSN 70 and a GGSN 80, and HNBs 20-1 to 20-4 incorporated into the core network
through a broadband 1P backhaul 50 which is one of public networks. The L-GW
having the function equivalent to the GGSN 80 is built in each of the HNBs 20-1 to
20-4, so that each of the HNBs 20-1 to 20-4 has the LIPA function.
[0031] On the other hand, when a macro network (a UE 10 which attaches to a RAN
including an NB 420 and an RNC 430 as shown in Fig. 2) requests remote 1P access,
the SGSN 70 cooperates with the HNB-GW 60 to establish a comin~inication path
from the UE 10 to the HNB 20.
[0032] In operations, as shown in Fig. 1, the HNB-GW 60 firstly establishes Psec tunnels
40-1 to 40-4 (hereinafter, also collectively refened to by using a reference numeral
"40") between the HNB-GW 60 and the HNBs 20-1 to 20-4. Next, the HNB 20
translnits an HNB Register Request inessage to the HNB-GW 60 through the IPsec
tunnel 40. The HNB-GW 60 receives the HNB Register Request message, and then authenticates
whether or not the HNB 20 is an allowable device which can be incorporated
into the core network. As a result, in a case of succeeding in the authentication
of the HNB 20, the HNB-GW 60 telininates the registration of the HNB 20,
and sends an HNB Register Accept inessage back to the HNB 20.
[0033] A series of processes mentioned above are operations defined in the 3GPP specification.
Meanwhile, the following processes will be executed as characteristic operations
in this exelnplary embodiment.
100341 If the HNB 20 has the LIPA function, the EINB 20 includes an APN supported by the
HNB 20 itself in the HNB Register Request message. The HNB-GW 60 stores this
APN in association with an 1 P address of' the HNB 20. The HNB-GW 60 sets, as the IP
address of the HNB 20, e.g., a source 1P address of the HNB Register Request
message.
LO0351 After that, if the UE 10 desires access to a local 1P network, the UE 10 trans~nitsa
PDP (Packet Data Protocol) Activation Request message to the SGSN 70 through the
RAN (the NB 420 and the RNC 430 shown in Fig. 2). At this time, the UE 10 includes
the APN in the PDP Activation Request message.
LO0361 The SGSN 70 receives the PDP Activation Request inessage, and then generates a
PDP Create Request message. At this time, the SGSN 70 sets, in the PDP Activation
Request message, the APN included in the PDP Activation Request message. Fui-ther,
the SGSN 70 derives an IP address of the HNB-GW 60 by using the APN included in
the PDP Activation Request inessage. Note that this derivation is perfo~lneda s in the
case where the SGSN derives an IP address of the GGSN. Therefore, the specific explanation
thereof is omitted. Then, the SGSN 70 transmits the PDP Create Request
message to the IP address of the HNB-GW 60.
[0037] When the HNB-GW 60 receives the PDP Create Request message, the HNB-GW 60
determines which L-GW (HNB) a coininu~licatiop~al th should be established to among
the HNBs 20-1 to 20-4 by using the APN included in this message, and transfers the
PDP Create Request inessage to an appropriate L-GW (HNB). Taking as an example a
case where an APN supported by an L-GW 230-1 (HNB 20-1) is set as the APN
included in the PDP Create Request message, the HNB-GW 60 identifies an IP address
coil-esponding to this APN (IP address of the HNB 20-1) as shown in Fig. 2. Then, the
HNB-GW 60 transfers the PDP Create Request inessage to the identified P address.
100381 According to a series of processes mentioned above, com~nunicationp aths between
elements from the local IP network to the UE are established.
[0039] Hereinafter, with reference to Figs. 3 to 7. there will be described in detail specific
configuration examples and operation examples of the HNB-GW 60, the HNB 20 and
the SGSN 70 for materializing the above-mentioned operations.
[0040] As shown in Fig. 3, the HNB-GW 60 according to this exemplary embodilneilt
includes an HNB I/F 61, a CN (Core Network) IIF 62, and a controller 63. The HNB I/
F 61 colntn~~nicatewsi th the HNB 20 through the broadband 1P backhaul 50. The CN
I/G 62 coin~nunicatesw ith the SGSN 70. The controller 63 controls the HNB I/F 61
and the CN I/F 62 to relay traffic between the HNB 20 and the SGSN 70. In other
words, the controller 63 cooperates with the HNB I/F 6 1 and the CN I/F 62 to make the
HNB-GW 60 f~~nctioasn with the typical HNB-GW. In addition, the controller 63
executes the process to store the APN supposted by the HNB 20 in association with the
IP address of the I-INB 20, the process to identify the L-GW (HNB) to which the corninunication
path should be established by using the APN included in the PDP Create
Request message, the process to transfer the PDP Create Request lnessage to the
identified L-GW (HNB), and the like.
(00411 Fui-ther, as shown in Fig. 4, the IINB 20 according to this exemplary embodiment
includes an HNB-GW VF 21, an L-GW 230, and a controller 22. The HNB-GW I/F 21
cornlnunicates with the HNB-GW 60 through the bn~adbandT P backhaul 50. The
controller 22 controls the HNB-GW I F 21 and the L-GW 230 to route packets
originated from the UE 10 upoll the remote JP access into the local IP network to
which the HNB 20 belongs. Note that although the illustration is omitted, the HNB 20
also has the f~inctiono f for~ninga femto cell to wirelessly communicate with the UE as
with the typical HNB.
[0042] Fu~-the~moraes, shown in Fig. 5, the SGSN 70 according to this exeinplaly einbodiinent
includes an HNB-GW I/F 71, a RAN I/F 72, and a controller 73. The HNBGW
I/F 7 1 communicates with the HNB-GW 60. The RAN T/F 72 serves as the
interface to the RNC 430 shown in Fig. 2, and thus communicates with the UE 10
through the RNC 430 and the NB 420 (i.e., the RAN). The controller 73 controls the
HNB-GW I/F 71 and the RAN I/F 72, thereby making the SGSN 70 f~inctiona s with
the typical SGSN. In addition, the controller 73 executes the process to extract the
APN from the PDP Activation Request message, the process to generate the PDP
Create Request lnessage and to set the extracted APN in this message, the process to
deiive the TP address of the HNB-GW 60 by using the extracted APN, the process to
transinit the PDP Create Request message to the derived IP address, and the like.
[0043] Next, operation examples of the HNB-GW 60, the HNB 20 and the SGSN 70 will be
described with reference to Figs. 6 and 7.
[0044] As shown in Fig. 6, the HNB 20 transmits to the HNB-GW 60 the HNB Register
Request inessage which includes the APN supported by the HNB 20 itself ptior to
stat-ting commn~~nicatiowni th the HNB-GW 60 (Step S11).
[0045] The HNB 1/F 61 in the HNB-GW 60 transfers the HNB Register Request lnessage
received from the HNB 20 to the controller 63. At this time, the controller 63 perforins
authentication for the HNB 20. As a result, upon succeeding in the authenticatioil of
the HNB 20, the controller 63 extracts the APN from the HNB Register Request
message, and stores the extracted APN in association with the 1P address of the HNB
20 (Step S 12).
[0046] Note that in the following explanation, infotination 011 the associated APN and IP
address is also referred to as "APN information".
[0047J Then, the contwller 63 in the HNB-GW 60 tetlninates the registration of the HNB
20. and generates the HNB Register Accept message. FUI-ther,t he controller 63 causes
the HNB I/F 61 to transmit the generated HNB Register Accept lnessage to the HNB
20 (Step S 13).
100481 As shown in Fig. 7, if the UE 10 desires access to the local IP network, the UE 10
translnits to the SGSN 70 the PDP Activatio~R~e quest inessage which includes an
APN supported by a certain HNB. Assume that the UE 10 desires access to the L-GW
230-1 (HNB 20-1) within the local IP network 30. In this case, the UE 10 includes the
APN supported by the HNB 20-1 in the PDP Activation Request message (Step S21).
[0049] The RAN I F 72 in the SGSN 70 transfers the PDP Activation Request message
received from the UE 10 to the controller 73. The controller 73 generates the PDP
Create Request message, and sets the APN extracted from the PDP Activation Request
message in this PDP Create Request message. Further, the controller 73 derives the IF
address of the HNB-GW 60 by using the extracted APN. Then, the controller 73 causes
the HNB-GW VF 71 to transmit the PDP Create Request message to the derived IP
address (Step S22).
[0050] The CN VF 62 in the HNB-GW 60 transfers the PDP Create Request message
received from the SGSN 70 to the controller 63. The controller 63 selects an appropriate
L-GW (HNB) by using the APN included in the PDP Create Request
message and the APN information. Now, the PDP Create Request message includes
the APN supported by the HNB 20-1. Therefore, the controller 63 selects the IP
address of the L-GW 230-1 (HNB 20-1) corresponding to this APN (Step S23).
[0051] Then, the controller 63 causes the HNB IIF 61 to transmit the PDP Create Request
message to the selected IP address (Step S24).
[0052] The L-GW 230-1 (HNB 20-1) receives the PDP Create Request message, and then
sends a PDP Create Response lnessage back to the HNB-GW 60 (Step S25).
[0053] Thus, a communication path is established between the HNB-GW 60 and the L-GW
230-1.
[0054] Next, the HNB-GW 60 translnits the PDP Create Response message to the SGSN 70
(Step S26).
[0055] Thus, a communication path is established between the SGSN 70 and the HNB-GW
60.
[0056] Finally, the SGSN 70 transmits a PDP Activation Response message to the UE 10
(Step S27).
LO0571 Thus, a communication path is established between the UE 10 and the SGSN 70.
LO0581 According to the above-mentioned processes, the communication paths between
elements from the local IP network to the UE are established, so that the remote IP
access can be realized.
LO0591 As mentioned above, according to this exemplary embodiment, the following first to
fourth effects can be achieved.
[0060] It is difficult for the typical SGSN to directly transmit the control message for establishing
the communication path to the HNB. due to the assignment of the private IP
address or the variable public I P address to the HNB. However, in this exemplary embodiment,
it is possible to establish the communication path to the HNB by the simple
mechanism to include the APN supported by the HNB in the control message, so that it
is possible to achieve the first effect that the remote IP access call be easily realized.
[0061] Further, in this exe~nplalye mbodiment, the control message and the communication
path are transmitted and established within the IPsec tunnel between the HNB-GW and
the HNB. Therefore, it is possible to achieve the second effect to avoid the risk of communication
contents being intercepted by third persons.
COO621 Further, the HNB is the device installed within end-user's premises or the like. In
some cases, there may exist a maliciously modified device. The typical SGSN does not
have the f~lnctiono f authenticating the destination device, and therefore may establish
a communication path to such a malicious HNB. However, in this exemplaiy embodiment,
at the time when the SGSN transmits the PDP Create Request message to
the HNB-GW, the HNB-GW has already authenticated the HNB. Therefore, it is
possible to achieve the third effect that a cominunication path to an allowable L-GW
(HNB) can be established without implementing the function of authenticating the
HNB in the SGSN.
100631 Ful-theiinore, upon establishing the communication path between the HNB and the
SGSN, the typical SGSN needs to notify its IP address to the HNB. The SGSN is a
coimnunicatiol~n ode which accommodates comin~~nicatiopnat hs for a large number of
users. Therefore, there is a ciitical security problem in notifying the IP address of such
a communication node to the HNB installed within end-user's premises. However, in
this exemplary embodiment, it is not necessaly to notify the IP address of the SGSN to
the HNB. Therefore, it is possible to achieve the fourth effect to improve security as
compared with the case of notifying the IP address of the SGSN to the HNB.
[0064]
A colmnunicatioi~s ystem, an HNB-GW, an HNB and an SGSN according to this
exemplary ernbodirnent can be configured as with the above-mentioned first exelnplary
embodiment. Meanwhile, this exemplary embodiment is different from the abovementioned
first exemplary embodiment, in that the controller in the HNB-GW preliminarily
stores the APN suppoi-ted by each HNB in association with the IP address of
each HNB prior to stai-ting communication with each HNB.
[0065] Specifically, the HNB 20 does not notify the HNB-GW 60 of the APN supported by
the HNB 20 itself, unlike the example shown in Fig. 6 in the registration procedures
for the HNB 20. Alternatively, in the HNB-GW 60, the APN infolination is preliminarily
stored as a database by e.g., an operator.
[0066] The HNB-GW 60 receives the PDP Create Request message from the SGSN 70 as in
the case shown in Fig. 7, and then refers to the database by using the APN included in
the PDP Create Request message, thereby selecting the appropriate L-GW (HNR).
[0067] Thus, in this exemplary embodiment, it is not necessary to notify the APN from the
HNB to the HNB-GW. Therefore, it is possible to achieve the effect that the remote 1P
access call be realized without modifying the existing HNB registration procedure. It is
also possible to achieve the effect to reduce the amount of traffic between the HNB
and the HNB-GW as compared with the above-mentioned first exemplary embodimen
t.
[0068]
A communication system, an HNB-GW, an HNB and a11 SGSN according to this
exemplary embodiment can be configured as with the above-mentioned first exemplary
emnbodiment. Meanwhile, this exemplary embodiment is different from the abovementioned
first exemplaly embodiment, in that the PDP Create Request lnessage
i~lcludesa CSG (Closed Subscriber Group)-ID, and that the controller in the HNB-GW
stores the APN supported by each HNB further in association with a CSG-ID and
transfers the PDP Create Request message to the HNB when the CSG-ID i~icludedin
the PDP Create Request message coincides with the stored CSG-ID. Note that the term
CSG indicates that only a specific group of users (group of UEs) is allowed to access a
specific HNB installed within a certain local IP network. The UE call access the
specific HNB by using a CSG-ID prelimina~ilya ssigned thereto.
[0069] Specifically, in the registration procedure shown in Fig. 6, the HNB 20 further
iilcludes the CSG-ID in the HNB Register Request message.
[0070] The HNB-GW 60 receives the HNB Register Request lnessage from the HNB 20,
and then stores, as an i~lfor~natioeille ment of the APN information, the CSG-ID
included in this message.
[0071] On the other hand, upoil trallsmittiiig the PDP Activation Request lnessage shown in
Fig. 7, the UE 10 includes the CSG-ID in the PDP Activation Request message.
[0072] The SGSN 70 extracts the APN aiid the CSG-ID from the PDP Activation Request
message received from the UE 10. Then, the SGSN 70 sets the extracted APN and
CSG-ID in the PDP Create Request lnessage to be transmitted to the I-INB-GW 60.
[0073] The HNB-GW 60 selects the appropriate L-GW (HNB) by using the APN included
in the PDP Create Request message as in the case shown in Fig. 7. Meanwhile, when a
CSG-ID stored in association with this APN coincides with the CSG-ID included in
the PDP Create Request lnessage (in other words, when the UE 10 is allowed to access
the selected L-GW (HNB)), the HNB-GW 60 trailsfers the PDP Create Request
message to the selected L-GW (HNB). On the other hand, when both CSG-IDS do not
coincide with each other (in other words, when the UE 10 is not allowed to access the
selected L-GW (HNB)), the HNB-GW 60 does not transfer the PDP Create Request
message.
LO0741 Thus, in this exemplary embodiment, it is possible to achieve the effect that the
reinote IP access can be pel-formed oilly for an allowable UE which is allowed to
access the HNB.
[0075] Note that it is not essential to notify the CSG-ID from the HNB to the HNB-GW.
The CSG-ID may be preliminarily stored in the database as with the above-mentioned
second exemplaiy embodiment. 111 this case, the above-mentioned effect call be
similarly achieved. In addition, it is also possible to achieve the effect that it is not
necessaiy to modify the existing HNB registration procedure and that the amount of
traffic between the HNB and the HNB-GW can be reduced.
[0076]
A coinmullicatio~ls ystem, an HNB-GW, an HNB and a11 SGSN according to this
exeinplaly einbodirnent can be coilfigured as with the above-mentioned first exemplary
embodiment. Meanwhile, this exemplary embodilnent is different from the abovementioned
first exemplary embodiment, in that the controller in the HNB-GW further
stores information indicating whether or not each HNB has the LIPA function
(hereinafter, this inforination will be referred to as "function information"), and
trallsfers the PDP Create Request message only to the HNB whose corresponding
functioil info~lnationin dicates "preseace of LIPA function".
[0077] According to this exelnplary embodiment, even under circumstances where an HNB
which has the LIPA fuilction and an HNB which does not have the LIPA function are
mixed, it is possible to achieve the effect to appropriately select the HNB having the
LIPA function upon the remote 1P access.
[0078] Note that the function information may be notified from the HNB to the HNB-GW in
the HNB registration procedure, or may be preliminarily set in the database. In both
cases, the above-mentioned effect call be similarly achieved. In the latter case, it is also
possible to achieve the effect that it is not necessary to modify the existing HNB registration
procedure and that the amount of traffic between the HNB and the HNB-GW
can be reduced.
LO0791
Each of the above-mentioned first to foui-th exemplaiy embodiments deals with the
coinrnuilication system employing the UMTS radio system. However, the gateway, the
base station and the co~mnunicatioln~o de according to exeinplary embodiment can also
be applied to a communication system employing the LTE radio system.
[0080] As shown in Fig. 8, a communication system according to this exemplary embodiinent
includes an HeNB-GW 160 and an S-GW 171.
[008 11 Among them, the HeNB-GW I60 relays traffic between a core network i~lcludinga n
MME 170. the S-GW 17 1 and a P-GW 180, and I-IeNBs 120-1 to 120-4 incorporated
into the core network through a broadba~ld1 P backhaul 150. The L-GW having the
f~~nctioenqu ivalent to the P-GW I80 is built in each of the HeNBs 120-1 to 120-4, so
that each of the HcNBs 120-1 to 120-4 has the LIPA f~inctioi~.
LO0821 On the other hand, when a macro network (a UE 110 which attaches to a RAN
includii~ga n eNB 520 as shown in Fig. 9) requests remote IP access, the S-GW 170 cooperates
with the HeNB-GW 160 to establish a communication path from the UE 1 10
to the HeNB 120.
100831 I11 operatioi~sa, s shown in Fig. 8, the HeNB-GW 160 firstly establishes lPsec h~nnels
140-1 to 140-4 (hereinafter, also collectively referred to by using a reference nulneral
" 140") between the HeNB-GW 160 and the HeNBs 120-1 to 120-4. Next, the HeNB
120 transmits an S1 Establishinellt Request message to the HeNB-GW 160 through the
IPsec tuilllel 140. The HeNB-GW 160 receives the Sl Establishinent Request message,
and then authenticates whether or not the HeNB 120 is an allowable device which can
be incorporated into the core network. As a result, in a case of succeedi~lgin the authentication
of the HeNB 120, the HeNB-GW 160 transfers the S1 Establishment
Request message to the MME 170. The HeNB-GW 160 receives an S 1 Establishinent
Response inessage from the MME 170, and then transfers this S 1 Establishinent
Respollse inessage to the HeNB 120.
100841 A series of processes mentioned above are operations defined in the 3GPP specification.
Meanwhile, the following processes will be executed as characteristic operations
in this exemplary embodiment.
[0085] If the HeNB 120 has the LIPA function, the HeNB 120 includes an APN supported
by the HeNB 120 itself in the Sl Establishment Request message. The HeNB-GW 160
stores this APN in associatioil with an IP address of the HeNB 120. The HeNB-GW
160 sets, as the IP address of the HeNB 120, e.g., a source IF' address of the Sl Establishment
Request message.
100861 After that, if the UE 1 10 desires access to a local IP network, the UE 1 10 transmits a
PDN Connectivity Request message to the MME 170 through the RAN (the eNB 520
shown in Fig. 9). At this time, the UE 110 iilcludes the APN in the PDN Connectivity
Request message. The MME 170 receives the PDN Connectivity Request message,
and then trallsinits a Create Session Request message to the S-GW 171. At this time,
the MME 170 sets, in the Create Session Request message, the APN included in the
PDN Connectivity Request message.
[0087] The S-GW 171 receives the Create Session Request message, and then derives an IP
address of the HeNB-GW 160 by using the APN included in the Create Session
Request message. Note that this derivation is performed as in the case where the S-GW
derives an TP address of the P-GW. Therefore, the specific explanation thereof is
omitted. Then, the S-GW 171 transfers the Create Session Request inessage to the IP
address of the HeNB-GW 160.
100138 1 When the HeNB-GW 160 receives the Create Session Request message, the HeNBGW
160 deterlnines which L-GW (HeNB) a cominunication path should be established
to ainong the HeNBs 120- 1 to 120-4 by using the APN included in this
message, and transfers the Create Session Request message to an appropriate L-GW
(HeNB). Taking as an example a case where an APN supported by an L-GW 330-1
(HeNB 120-1) is set as the APN included in the Create Session Request message, the
HeNB-GW 160 identifies an IP address col-sesponding to this APN (IP address of the
HeNB 120-1) as shown in Fig. 9. Then, the HeNB-GW 160 transfers the Create
Session Request message to the identified IP address.
100891 According to a series of processes mentioned above, communication paths between
elements from the local IP network to the UE are established.
[0090] Hereinafter, with reference to Figs. 10 to 14, there will be described in detail specific
configuration examples and operation examples of the HeNB-GW 160, the HeNB 120
and the S-GW 171 for matelializing the above-mentioned operations.
[0091] As shown in Fig. 10, the HeNB-GW 160 according to this exelnplary embodiment
includes an HeNB I/F 16 1, a CN (Core Network) I/F 162, and a controller 163. The
HeNB I/F 161 co~nmunicatesw ith the HeNB 120 through the broadband IP backhaul
150. The CN I/G 162 cominui.~icatews ith the S-GW 17 1. The contmller 163 controls
the HeNB I/F 161 and the CN I/F 162 to relay traffic between the HeNB 20 and the SGW
17 1. In other words, the controller 163 cooperates with the HeNB I/F 16 1 and the
CN I/F 162 to make the HeNB-GW 160 function as with the typical HeNB-GW. In
addition, the controller 163 executes the process to store the APN supposted by the
HeNB 120 in association with the IP address of the HeNB 120, the process to identify
the L-GW (HeNB) to which the cormnunication path should be established by using
the APN included in the Create Session Request message, the process to transfer the
Create Session Request inessage to the identified L-GW (HeNB), and the like.
100921 Further, as shown in Fig. I I, the HeNB 120 according to this exemplary embodiment
includes an HeNB-GW VF 121, an L-GW 330, and a controller 122. The HeNB-GW I/
F 121 cominunicates with the HeNB-GW 160 through the broadband IP backhaul 150.
The controller 122 controls the HeNB-GW I/F 121 and the L-GW 330 to route packets
originated from the UE 110 upon the remote 1P access into the local 1P network to
which the HeNB 120 belongs. Note that although the illustration is omitted, the HeNB
120 also has the f~~nctioofn forlning a femto cell to wirelessly colninunicate with the
UE as with the typical HeNB.
100931 Ful-theiinore, as shown in Fig. 12, the S-GW 17 1 according to this exeinplaiy embodiment
includes an HeNB-GW IIF 171-1, a RAN I/F 171-2, and a controller 171-3.
The HeNB-GW I/F 171-1 communicates with the HeNB-GW 160. The RAN 1/F
17 1-2 serves as the interface to the eNB 520 shown in Fig. 8. and thus co~nlnunicates
with the UE 1 10 through the eNB 520 (i.e.. the RAN). The controller 171-3 controls
the HeNB-GW I/F 171-1 and the RAN IF 171-2, thereby making the S-GW 171
function as with the typical S-GW. 111 addition, the controller 171-3 executes the
process to extract the APN from the Create Session Request message, the process to
derive the IP address of the HeNB-GW 160 by using the extracted APN, the process to
transfer the Create Session Request message to the derived IP address, and the like.
Next, operation examples of the HeNB-GW 160, the HeNB 120 and the S-GW 171
will be described with reference to Figs. 13 and 14.
As shown in Fig. 13, the HeNB 120 transmits to the HeNB-GW 160 the S 1 Establishment
Request message which includes the APN supported by the HeNB 120 itself
prior to starting comin~~nicatiowni th the HeNB-GW 160 (Step S31).
The HeNB I/F 161 in the HeNB-GW 160 transfers the S1 Establishment Request
message received from the HeNB 120 to the controller 163. At this time, the controller
163 pelforms authentication for the HeNB 120. As a result, upon succeeding in the authentication
of the HeNB 120, the controller 163 extracts the APN from the S 1 Establishment
Request message, and stores, as the APN infolmation, the extracted APN in
association with the IP address of the HeNB 120 (Step S32).
Then, the controller 163 in the HeNB-GW 160 transfers the S 1 Establishment
Request message to the MME 170 (Step S33).
The CN I/F 162 in the HeNB-GW 160 receives the SI Establishment Response
message from the MME 170, and then transfers the S1 Establishment Response
message to the controller 163 (Step S34).
At this time, the controller 163 in the HeNB-GW 160 causes the HeNB I/F 161 to
trailsfer the S1 Establishment Response lnessage to the HeNB 120 (Step S3.5).
As shown in Fig. 14, if the UE 110 desires access to the local IP network, the UE 110
trans~nitsto the MME 170 the PDN Connectivity Request lnessage which includes an
APN supported by a certain HeNB. Assume that the UE 110 desires access to the LGW
330-1 (HeNB 120-1) within the local IP network 130. In this case, the UE 110
includes the APN supported by the HeNB 120-1 in the PDN Connectivity Request
message (Step S41).
The MME 170 receives the PDN Connectivity Request message, and then transmits a
Location Updating Request message to an HSS (Home Subscriber Selves) 173. When
the MME 170 receives a Location Updating Response lnessage from the HSS 173, the
MME 170 generates the Create Session Request message, and sets, in this Create
Session Request message, the APN extracted from the PDN Connectivity Request
message, an APN received from the HSS 173, or an APN included in another message
received from the UE 1 10.
Then, the MME 170 transmits the Create Session Request message to the S-GW 171
(Step S42).
The RAN I/F 17 1-2 in the S-GW 17 1 transfers the Create Session Request message
received from the MME 170 to the controller 171-3. The controller 171-3 derives the
IP address of the HeNB-GW 160 by using the APN extracted froin the Create Session
Request message. Then, the controller 171-3 causes the HeNB-GW T/F 17 1-1 to
transfer the Create Session Request message to the derived IP address (Step S43).
The CN YF 162 in the HeNB-GW 160 transfers the Create Session Request inessage
from the S-GW 171 to the controller 163. The controller 163 selects an appropriate LGW
(HeNB) by using the APN included in the Create Session Request message and
the APN infoilnation. Now, the Create Session Request message includes the APN
supported by the HeNB 120-1. Therefore, the controller 163 selects the IP address of
the L-GW 330-1 (I-IeNB 120-1) corresponding to this APN (Step S44).
Then, the controller 163 causes the HeNB I/F 161 to transfer the Create Session
Request message to the selected IP address (Step S45).
The L-GW 330-1 (HeNB 120-1) receives the Create Session Request message, and
then sends a Create Sessioil Response message back to the HeNB-GW 160 (Step S46).
Thus, a co~mnu~licatiopna th is established between the HeNB-GW 160 and the LGW
330-1.
Next, the HeNB-GW 160 transmits the Create Session Response message to the SGW
171 (Step S47).
Thus, a coimn~1ilicationp ath is established between the S-GW 171 and the HeNBGW
160.
Next, the S-GW 171 transmits the Create Session Response message to the MME
170 (Step S48).
Thus, a coimnuilication path is established between the MME 170 and the S-GW
171.
Finally, the MME 170 transmits a Create Default Bearer Request inessage to the UE
1 10 (Step S49), and receives, as a response thereto, a Create Default Bearer Response
message from the UE 110 (Step S50).
Thus, a colnmunication path is established between the UE 110 and the MME 170.
According to the above-mentioned processes, the communication paths between
elements from the local IP network to the UE are established, so that the remote IP
access can be realized.
As mentioiled above, according to this exemplary embodiment, the following fifth to
eighth effects can be achieved.
It is difficult for the typical S-GW to directly transmit the control inessage for establishing
the communication path to the HeNB, due to the assignment of the private
1P address or the variable public IP address to the HeNB. However, in this exemplary
embodiment, it is possible to establish the communication path to the HeNB by the
simple mechanism to i~lcludeth e APN supported by the HeNB in the control message.
so that it is possible to achieve the fifth effect that the remote IP access can be easily
realized.
[0116] Further, in this exempla~ye mbodiment, the control message and the comtnunication
path are transmitted and established within the IPsec tunnel between the HeNB-GW
and the HeNB. Therefore, it is possible to achieve the sixth effect to avoid the risk of
collmnication contents being intercepted by thisd persons.
[0117] Ful-ther, the HeNB is the device installed within end-user's premises or the like. In
some cases, there may exist a maliciously modified device. The typical S-GW does not
have the f~~nctioonf authenticating the destination device, and therefore may establish
a comlnunication path to such a malicious HeNB. However, in this exeinplary einbodiment,
at the time when the S-GW transmits the Create Session Request message to
the HeNB-GW, the HeNB-GW has already authenticated the HeNB. Therefore, it is
possible to achieve the seventh effect that a colmnunication path to an allowable LGW
(HeNB) can be established without implementing the function of authenticating
the HeNB in the S-GW.
[0 11 81 Ful-thes~noreu, pon establishing the communication path between the HeNB and the
S-GW, the typical S-GW needs to notify its IP address to the HeNB. The S-GW is a
communication node which accolnmodates communication paths for a large number of
users. Therefore, there is a critical security problem in notifying the 1P address of such
a communication node to the HeNB installed within end-user's premises. However, in
this exemplary embodiment, it is not necessaly to notify the IP address of the S-GW to
the HeNB. Therefore, it is possible to achieve the eighth effect to improve security as
compared with the case of ~~otifyinthge IP address of the S-GW to the HeNB.
10 1 191
A communication system, a11 HeNB-GW, an HeNB and an S-GW according to this
exemplary embodiment can be configured as with the above-mentioned fifth
exeinplaly embodiment. Meanwhile, this exemplary embodiment is different from the
above-mentioned fifth exemplary embodiment, in that the controller in the HeNB-GW
preliminarily stores the APN supported by each HeNB in association with the 1P
address of each HeNB psior to starting commn~~nicatiowni th each HeNB.
[0120] Specifically, the HeNB 120 does not notify the HeNB-GW 160 of the APN
supported by the HeNB 120 itself, unlike the example shown in Fig. 13 in the S1 establishment
procedures for the HeNB 120. Alternatively, in the HeNB-GW 160, the APN
information is preliminarily stored as a database by e.g., an operator.
[0121] The HeNB-GW 160 receives the Create Session Request message from the S-GW
17 1 as in the case shown in Fig. 14, and then refers to the database by using the APN
included in the Create Session Request message, thereby selecting the appropriate LGW
(HeNB).
[0122] Thus, in this exemplary embodiment, it is not necessary to notify the APN from the
HeNB to the HeNB-GW. Therefore, it is possible to achiel~eth e effect that the remote
IP access can be realized without modifying the existing SI establish~nenpt rocedure. It
is also possible to achieve the effect to reduce the amount of traffic between the HeNB
and the HeNB-GW as comnpared with the above-mentioned fifth exelnplary embodiment.
[O 1231
A co~mnunication system, an HeNB-GW, an HeNB and an S-GW according to this
exemplary embodiment can be configured as with the above-mentioned fifth
exemplary embodiment. Meanwhile, this exeinplary embodiment is different from the
above-mentioned fifth exemplary embodiment, in that the Create Session Request
lnessage includes a CSG-ID, and that the controller in the HeNB-GW stores the APN
supported by each HeNB flirther in association with a CSG-ID and transfers the Create
Session Request message to the HeNB when the CSG-ID included in the Create
Session Request lnessage coincides with the stored CSG-ID. Note that the term CSG in
this exemplary embodiment indicates that only a specific group of users (group of
UEs) is allowed to access a specific HeNB installed within a certain local IP network.
The UE call access the specific HeNB by using a CSG-ID pl*eliminaiily assigned
thereto.
[0124] Specifically, in the Sl establishment procedure shown in Fig. 13, the HeNB 120
further includes the CSG-ID in the S 1 Establishinent Request message.
[0125] The HeNB-GW 160 receives the S 1 Establishinent Request message from the HeNB
120, and then stores, as an infomation element of the APN infor~nation,t he CSG-ID
included in this message.
101261 On the other hand, upon transmitting the PDN Coiinectivity Request message shown
in Fig. 14, the UE 110 includes the CSG-ID in the PDN Connectivity Request
message. Further, the MME 170 includes this CSG-ID in the Create Session Request
lnessage to be transinitted to the S-GW 17 1.
[0127] The S-GW 171 transfers the Create Session Request message received from the
MME 170 to the HeNB-GW 160.
[0128] The HeNB-GW 160 selects the appropriate L-GW (HNB) by using the APN included
in the Create Session Request message as in the case show11 in Fig. 14. Meanwhile,
when a CSG-ID stored in association with this APN coincides with the CSG-ID
included in the Create Session Request lnessage (in other words, when the UE 110 is
allowed to access the selected L-GW (HeNB)), the HeNB-GW 160 transfers the Create
Session Request lnessage to the selected L-GW (HeNB). On the other hand, when both
CSG-IDS do not coincide with each other (in other wol-ds, when the UE 110 is not
allowed to access the selected L-GW (HeNB)), the HeNB-GW 160 does not transfer
the Create Session Request message.
Thus, in this exemplaly embodiment, it is possible to achieve the effect that the
remote IP access can be performed only for an allowable UE which is allowed to
access the HeNB.
Note that it is not essential to notify the CSG-ID from the HeNB to the HeNB-GW.
The CSG-ID may be prelirnina~ilys tored in the database as with the above-mentioned
sixth exe~nplarye mbodiment. In this case, the above-mentioned effect call be similarly
achieved. In addition, it is also possible to achieve the effect that it is not necessary to
modify the existing S 1 establishment procedure and that the amount of traffic between
the HeNB and the I-leNB-GW can be reduced.

A communication system, an HeNB-GW, an HeNB and an S-GW according to this
exempla~ye mbodiment can be configured as with the above-mentioned fifth
exempla~ye mbodiment. Meanwhile, this exempla~ye mbodiment is different from the
above-mentioned fifth exemplary embodiment, in that the controller in the HeNB-GW
further stores fuilction information indicating whether or not each HeNB has the LIPA
function, and transfers the Create Session Request message only to the HeNB whose
correspondi~lgf unction infor~nationin dicates "presence of LIPA function".
According to this exemplary embodiment, even under circulnstances where an HeNB
which has the LIPA ful~ctiona nd an HeNB which does not have the LlPA f~lnctiona re
mixed, it is possible to achieve the effect that the HeNB-GW can appropriately select
the HeNB having the LIPA function upon the remote IP access.
Note that the f~lnctionin formation may be notified from the HeNB to the HeNB-GW
in the S 1 establish~nent procedure, or may be preliminarily set in the database. In both
cases, the above-mentioned effect call be similarly achieved. In the latter case, it is also
possible to achieve the effect that it is not necessary to modify the existing S1 establishment
procedure and that the amount of traffic between the HeNB and the HeNBGW
can be reduced.
It should be noted that the present inventive concept is not limited to the above
exemplaly embodiments but modification can be made as needed without deviating
from the spirit and scope as defined by the claims.
This application is based upon and claims the benefit of priority from Japanese patent
application No. 2012- 1 1740 1, filed on May 23,201 2, the disclosure of which is incolporated
herein in its entisety by this reference.
The whole or part of the exemplary embodiments disclosed above can be described
as, but not limited to, the following supplemelltary notes.
(Supp1ementai.y note 1 )
A gateway that establishes a secure tunnel between the gateway and each of a
plurality of base stations through a public network, the gateway comprising:
a first communicator that communicates with each of the base stations through the
secure tunnel;
a second communicator that comin~inicatesw ith a core network; and
a controller that controls the first and second colmnunicators to relay traffic between
the core network and each of the base stations,
wherein the controller is configured to:
store an APN (Access Point Name) supported by each of the base stations, when each
of the base stations includes a f~~nctioofn r outing traffic received through the secure
tunnel into a local network to which each of the base stations belongs; and
transfer, when receiving from the core network a first message for establishing a commu~
licationp ath to any one of the plurality of base stations from a mobile station
attaching to a RAN (Radio Access Network) connected to the core network, the first
message to a base station col-responding to a first APN included in the first message.
[O 1381 (Supplementary note 2)
The gateway according to Supplementary note 1, wherein the controller is configured
to preliminarily store the APN supported by each of the base stations prior to starting
communication with each of the base stations.
10 1391 (Suppleinentary note 3)
The gateway according to Supplementary note 1,
wherein the first colmnunicator is configured to receive, upon starting commnunication
with each of the base stations, from each of the base stations a second message
including the APN suppoi-ted by each of the base stations, and
wherein the controller is configured to store the APN included in the second
message.
[0 1401 (Supplementary note 4)
The gateway according to any one of Supplementa~yn otes 1 to 3, wherein the
controller is configured to:
hold, in a database, information on a mobile station that can connect to each of the
base stations;
refer to the database to determine whether or not a mobile station corresponding to
the first message can connect to the base station corresponding to the first APN; and
transfer the first message to the base station corresponding to the first APN, only
when it is determined that the mobile station can connect to the base station corresponding
to the first APN.
[O 14 1 1 (Supplementary note 5)
The gateway according to Supplementary note 4, wherein the database is preliminarily
created prior to stal-ting communication with each of the base stations.
[0 1421 (Supplementary note 6)
The gateway according to any one of Suppleinelltary notes 1 to 5, wherein the
controller is configured to:
select one base station when there are a plurality of base stations that correspond to the
first APN; and
trallsfer the first message to the selected base station.
[0143] (Supplementary note 7)
A base station that is incorporated illto a core network through a public network, the
base station comnprising:
a colnlnullicator that establishes a secure tunnel between the base station and a
gateway through the public network to communicate with the gateway;
a router that mutes traffic received through the secure tunnel into a local network to
which the base station belongs; and
a controller that controls the communicator and the router,
wherein the colninunicator is configured to receive, from the gateway, a first
message for establishing a coinrnullication path to the base station from a mobile
station attaching to a RAN connected to the core network, and
wherein the controller is configured to cause, when the first message is received, the
router to route traffic originated from the mobile station into the local network.
101 441 (Supplementary note 8)
A co~mnunicationn ode that is installed in a core network, the co~nmunicationn ode
comprising:
a first commullicator that coinlnunicates with a gateway establishing a secure tunllel
between the gateway and each of a plurality of base stations through a public network;
a second comnunicator that communicates, through a RAN co~lnectedt o the core
network, with a mobile station attaching to the RAN; and
a controller that controls the first and second communicators.
wherein the second co~n~nunicatiosr c onfigured to receive, from the mobile station, a
first message for requesting access to one base station among the plurality of base
stations, and
wherein the controller is configured to:
generate a second message for establishing a communication path from the mobile
station to the one base station, and set in the second message an APN included in the
first message; and
transmit the second inessage to the gateway.
[O 1451 (Supplementary note 9)
The communication node according to Supplementary note 8.
wherein the first colnlnunicator is configured to coinmunicate with a plurality of
gateways. and L
wherein the controller is configured to derive, by using the APN, an IP address of one
gateway to be a transmission destination of the second message.
10 1461 (Supplementary note 10)
The coinmunicatiol~n ode according to Supplementary note 8 or 9,
wherein the first message further includes infolinatioll for causing the gateway to
determine whether or not the mobile station call connect to the one base station, and
wherein the controller is configured to further set the information in the second
message.
[0147] (Supplementary note 1 1)
A cormnunication system comprising:
a communication node that is installed in a core network; and
a gateway that establishes a secure tunnel between the gateway and each of a
plurality of base stations through a public network,
wherein the coininunicatioil node is configured to:
receive, through a RAN connected to the core network, from a mobile station
attaching to the RAN, a first message for requesting access to one base station among
the plurality of base stations;
generate a second inessage for establishing a communication path from the mobile
station to the one base station, and set in the second message an APN included in the
first message; and
transmit the second inessage to the gateway, and
wherein the gateway is configured to:
store an APN supposted by each of the base stations, when each of the base stations
includes a function of routing traffic received through the secure tunnel into a local
network to which each of the base stations belongs; and
transfer, when the second inessage is received from the communication node, the
second rnessage to a base station corsesponding to a first APN incl~~deind the second
message.
[0148] (Supplementary note 12)
The colnmullicatioll system according to Supplelnentaly note 11,
wherein the mobile station is configured to further include, in the first inessage, information
for causing the gateway to determine whether or not the mobile station can
connect to the one base station,
wherein the coln~nunicationn ode is configured to further set the info~mationin the
second inessage, and
wherein the gateway is configured to:
hold, in a database, information on a mobile station that can connect to each of the
base stations;
refer to the database to deteiinine whether or not the inobile station can connect to the
base station corresponding to the first APN; and
transfer the second message to the base station corresponding to the first APN, only
when it is determined that the inobile station can connect to the base station corresponding
to the first APN.
[O 1491 (Supplementary note 13)
The communication system accolding to Supplementary note 12, wherein the
database is preliininarily created prior to starting communication with each of the base
stations.
[0150] (Supplementary note 14)
The communication system according to any one of Supplementary notes 11 to 13,
wherein the gateway is configured to preliminarily store the APN supposted by each of
the base stations prior to starting colnmunication with each of the base stations.
[O 15 11 (Supplementary note 15)
The coinmunicatiol~s ystem according to any one of Supplementary notes 11 to 13,
wherein each of the base stations is configured to transmit, upon starting cornintinication
with the gateway, to the gateway a third message including the APN
suppoi-ted by each of the base stations, and
wherein the gateway is configured to store the APN included in the thisd message.
[O 1521 (Supplementary note 16)
A method of controlling a gateway that establishes a secure tunnel between the
gateway and each of a plurality of base stations through a public network, the method L
comprising:
storing an APN supported by each of the base stations, when each of the base stations
includes a f~~nctioofn r outing traffic received through the secure tunnel into a local
network to which each of the base stations belongs; and
transferring. when receiving from the core network a first message for establishing a
corninunication path to any one of the plurality of base stations from a mobile station
attaching to a RAN connected to the core network, the first message to a base station
corresponding to a first APN included in the first message.
[O 1531 (Supplementary note 17)
A method of controlling a base station that is incorporated into a core network
through a public network, the method comprising:
establishing a secure tunnel between the base station and a gateway through the
public network to coinrnunicate with the gateway;
receiving, fi-om the gateway, a first message for establishing a communication path to
the base station from a mobile station attaching to a RAN connected to the core
network: and
routing, when the first message is received, traffic received from the mobile station
through the secure tunnel into a local network to which the radio base station belongs.
[0154] (Supplementary note 18)
A method of controlling a coin~nunicationn ode that is installed in a core network,
the method comprising:
receiving, through a RAN connected to the core network, from a mobile station
attaching to the RAN, a first message for requesting access to one base station ainong a
plurality of base stations that are incorporated illto the core netwol-k through a public
network;
generating a second message for establishing a corninunication path from the inobile
station to the one base station, and setting in the second message an APN included in
the first message; and
transmitting the second message to a gateway that establishes a secure tunnel
between the gateway and each of the base stations through the public network.
Reference Signs List
[0155] 10, 11 UE
20,20- 1 -20-4 HNB
30,3 1, 130, 13 1 LOCAL IF NETWORK
40,40-1-40-4, 140, 140- 1 - 140-4 IPsec TUNNEL
50,150 BROADBAND IP BACKHAUL
60 HNB-GW
6 1 HNB I/F
62, 162 CN I/F
22,63,73,122,163,17 1-3 CONTROLLER
70 SGSN
2 1,7 1 HNB-GW I/F
72, 17 1-2 RAN 1/F
80 GGSN
90,190 PDN
120, 120- 1 - 120-4 HeNB
160 HeNB-GW
161 HeNB I/F
170 MME
171 S-GW
121, 171-1 HeNB-GW 1/F
173 HSS
180 P-GW
230,230~1,230~2,330,330~1,33L0-G~W2
420 NB
430 RNC
520 eNB
Claims
[Claim I]
[Claim 21
[Claim 31
[Claim 41
[Claim 51
[Claim 61
A gateway conilected to a plurality of base stations and a core letw work,
the gateway comprising:
a receiver adapted to receive, from the core network, a message establishing
tablishing a coinin~u~icatiopna th to ally one of the plurality of base
stations, wherein the message includes a received Access Point Naine
(APN); and
a controller adapted to determine, in response to the APN included in
the message, a destination of the message using infoilnation indicating
a destination base station corresponding to the received APN.
The gateway according to claiin 1, further comprisiilg a transmitter
adapted to transmit the message with the destination base station as the
destination of the transmission.
The gateway according to claim 1 or 2, further compiising a memory
adapted to store:
the APN as a stored APN; and
information including an indication of the destillatioil base station corresponding
to the stored APN.
The gateway according to claim 3, wherein the memory stores the
stored APN before the gateway starts sending comnm~inication
messages, for a mobile station, using the indicated destinatioil base
station information.
The gateway according to claim 2, further comprisiilg a database that
stores iilforinatio~iln dicating one or more mobile stations permitted to
coilnect to the destination base station, wherein:
the message includes an illdicator of a requesting mobile station;
the coiltroller responds to the message by using the database to
dete~~ninweh ether the indicated requesting mobile station is one of the
peimitted mobile stations; and
when the indicated requesting mobile station is one of the permitted
mobile stations, the transmitter trailsmits the message with the destination
base station as the destination of the transmission.
A mobile com~nuilicatioisly stem comprising:
a plurality of base stations;
a core network; and
a gateway configured to communicate with the plurality of base
stations and the core network, and comprising:
[Claiin 71
[Claiin 81
[Claim 91
[Claiin 101
a receiver adapted to receive, froin the core network, a inessage establishing
a communication path to ally one of the plurality of base
stations, wherein the message il~cludesa received Access Point Name
(APN); and
a controller adapted to determine, in response to the APN illcluded in
the massage, a destination of the message using inforination indicating
a destillatioll base station col~espondingto the received APN.
The system according to claiin 6, wherein the gateway comprises a
transmitter adapted to transinit the message with the destination base
station as the destination of the transmission.
A inethod of controlling a gateway connected to a plurality of base
stations and a core inetwork, the inethod comprising:
receiving, from the core network, a inessage establishing a communication
path to ally one of the plurality of base stations, wherein the
message includes a received Access Point Name (APN); and
detei~niningi,n response to the APN included in the massage, a destination
of the message using information indicating a destination base
station corresponding to the received APN.
The method according to claim 8, ful-ther coinprisi~lgt ra~~sinittinthge
inessage with the destination base station as the destiilation of the
transmission.
A non-transitory coinpiiter readable medium i~lcludillgil lstluctioils for
contl-olling a pmcessor to impleinent a method for a gateway coi~nected
to a plurality of base stations and a core network, the inethod
comprising:
receiving, froin the core network, a inessage establishil~ga coinmullicatioll
path to any one of the plurality of base stations, wherein the
inessage includes a received Access Point Naine (APN); and
detelmining, in response to the APN included in the massage, a destinatioil
of the message using information indicatiilg a destinatioll base
station corresponding to the received APN.