1. A mobile communication system, wherein a terminal (UE) includes means configured to transmit a TAU(Tracking Area Update) Request to a base station (eNodeB); the base station includes means configured to forward the TAU Request to an MME (Mobility Management Entity); the MME includes means configured to transmit to the base station a request signal including an identifier corresponding to a dedicated MME that is dedicated to serve a specific terminal based on subscriber information obtained from an HSS (Home Subscriber Server); the base station includes means configured to re-select the dedicated MME based on the identifier; and the base station further includes means configured to transmit a NAS (Non-Access Stratum) message to the dedicated MME re-selected.

2. A mobile communication system, wherein a terminal (UE) includes means configured to transmit an RAU (Routing Area Update) Request to an SGSN (Serving GPRS(General Packet Radio Service) Support Node); the SGSN includes means configured to transmit to an RNC (Radio Network Controller) a request signal including an identifier corresponding to a dedicated SGSN that is dedicated to serve a specific terminal based on subscriber information obtained from an HLR (Home Location Register); the RNC includes means configured to re-select the dedicated SGSN based on the identifier; and the RNC further includes means configured to transmit a NAS (Non-Access Stratum) message to the dedicated SGSN re-selected.

3. A communication method in a mobile communication system, the method comprising: transmitting, by a terminal (UE), a TAU (Tracking Area Update) Request to a base station (eNodeB); forwarding, by the base station, the TAU Request to an MME (Mobility Management Entity); transmitting, by the MME, to the base station a request signal including an identifier corresponding to a dedicated MME that 60 is dedicated to serve a specific terminal based on subscriber information obtained from an HSS (Home Subscriber Server); re-selecting, by the base station, the dedicated MME based on the identifier; and transmitting, by the base station, a NAS (Non-Access Stratum) message to the dedicated MME re-selected.

4. A communication method in a mobile communication system, the method comprising: transmitting, by a terminal (UE), an RAU (Routing Area Update) Request to an SGSN (Serving GPRS(General Packet Radio Service) Support Node); transmitting, by the SGSN, to an RNC (Radio Network Controller) a request signal including an identifier corresponding to a dedicated SGSN that is dedicated to serve a specific terminal based on subscriber information obtained from an HLR (Home Location Register); re-selecting, by the RNC, the dedicated SGSN based on the identifier; and transmitting, by the RNC, a NAS (Non-Access Stratum) message to the dedicated SGSN re-selected.

5. A terminal (UE) for a mobile communication system, the terminal comprising: means configured to transmit a TAU (Tracking Area Update) Request including information on the terminal to a base station (eNodeB), wherein the base station forwards the TAU Request to an MME (Mobility Management Entity), the MME transmits to the base station a request signal including an identifier corresponding to a dedicated MME that is dedicated to serve a specific terminal based on subscriber information obtained from an HSS (Home Subscriber Server), and the base station re-selects the dedicated MME based on the identifier, thereby the specific terminal connecting to the dedicated MME re-selected.

6. A terminal (UE) for a mobile communication system, the terminal comprising: 61 means configured to transmit an RAU (Routing Area Update) Request including information on the terminal to an SGSN (Serving GPRS(General Packet Radio Service) Support Node), wherein the SGSN transmits to an RNC (Radio Network Controller) a request signal including an identifier corresponding to a dedicated SGSN that is dedicated to serve a specific terminal based on subscriber information obtained from an HLR (Home Location Register), and the RNC re-selects the dedicated SGSN based on the identifier, thereby the specific terminal connecting to the dedicated SGSN re-selected.

7. A communication method of a terminal (UE) for a mobile communication system, the method comprising: transmitting a TAU (Tracking Area Update) Request including information on the terminal to a base station (eNodeB), wherein the base station forwards the TAU Request to an MME (Mobility Management Entity), the MME transmits to the base station a request signal including an identifier corresponding to a dedicated MME that is dedicated to serve a specific terminal based on subscriber information obtained from an HSS (Home Subscriber Server), and the base station re-selects the dedicated MME based on the identifier, thereby the specific terminal connecting to the dedicated MME re-selected.

8. A communication method of a terminal (UE) for a mobile communication system, the method comprising: transmitting an RAU (Routing Area Update) Request including information on the terminal to an SGSN (Serving GPRS(General Packet Radio Service) Support Node), wherein the SGSN transmits to an RNC (Radio Network Controller) a request signal including an identifier corresponding to a dedicated SGSN that is dedicated to serve a specific terminal based on subscriber information obtained from an HLR (Home Location Register), and the RNC re-selects the dedicated SGSN based on the identifier, thereby the specific terminal connecting to the dedicated SGSN re-selected.

COMMUNICATION SYSTEM, METHOD, AND APPRATUS
TECHNICAL FIELD
[000r]
(REFERENCE TO RELATED APPLICATION)
The present invention is based upon and claims the benefit of the
priority of Japanese patent application No. 2011-217384, filed on
September 30, 2011, the disclosure of which is incorporated herein in
its entirety by reference thereto.
[0002]
The present invention relates to a communication system, a
method, and an apparatus.
B A C KGROUND
[0003]
In a core network of a mobile communication system, in order to
provide various services to various kind of terminals (mobile stations),
it is necessary that all of the nodes in the core network are provided
with functions required for each service. In large-scale mobile
communication network and the like, many nodes are arrhnged in the
core network. A terminal, on every location registration, is connected
in a distributed manner to nodes in the core network.
[0004]
Thus, all the nodes in the core network need to have necessary
functions for each service (service providing functions). When even a
part of the nodes in the core network do not have the necessary service
providing functions for each service, service continuitry for a terminal
cannot be ensured.
[000s]
For example, Patent Literature I discloses an arrangement for
optimizing a packet forwarding path based on a type of a service
utilizedby a mobile station, wherein, when the mobile station utilizes a
service from an external network, a constraint is given to a packet
forwarding path so that packet flow through a specific packet
forwarding apparatus based on the external network. When the mobile
l0
tn$.
station utilized a service provided by a mobile communication network,
no constraint is given to a packet forwarding path.
[0006]
IPatent Literature I ]
Japanese Patent Kokai Publication No. 2003-338832A
SUMMARY
[0007]
The following describes some analysis,of the related technique.
[0008] , ,
As described above, since each node in a core network has all
service providing functions, each node is required to have high
functionality and high performance. Consequently, each core network
node becomes expensive.
[000e]
For example, since a relatively small number of mob,ile terminals
are compatible with an MBMS (Multimedia Broadcast Multicast
Service) service (a simultaneous delivery service), which is a bearer
service that is standardized by 3 GPP (3rd Generation Partnership
Project) and that implements broadcast type delivery, there is not much
opportunity to provide the MBMS service. However, to provide the
service to a small number of MBMS users, it is necessary for a
communication operator to have all the nodes in the core network
equipped with the MBMS functions. Otherwise, the communication
operator cannot provide the service to the small number of MBMS users.
[0010]
If a node in the core network can be selected baspd on whether or
not a mobile terminal needs to use the MBMS service, the
communication operator can install a relatively small number of
expensive core network nodes that are compatible with the MBMS and
many inexpensive core network nodes that are not compatible with the
MBMS in combination. In this way, the equipment cost as a whole can
be reducbd more efficiently (first knowledge of the prese'nt inventors).
[0011]
ln addition, 3 GPP machine communication (MTC: Machine Type
l5
20
25
30
.l ,I
Communication) devices (M2M devices), which have been in widespread
use in recent years, greatly differ from normal terminals used for
phone calls (handset terminals) such as mobile phone terminals and
smart-phones or the like, in terms of a t'nobility.charaoteristic, a
5 required communication quality, and so forth. It is known that there
are various types of machine communication services, such as for
remote management of stocks and charging of automatic vending
machines, remote monitoring control in a sensor system, vehicle
monitoring, and smart grid.
10 [0012]
In core network nodes, for example, MTC-compatible nodes are
customized to be suitable for accommodating a terminal (MTC device)
that exchanges more control signals and less user data than normal
nodes (for example, these MTC-compatible nodes are custo mized so that,
l5 while a performance of a user plane in which user data is exchanged is
reduced for cost reduction, a performance of a control plane of a control
signal system is improved). Thus, unless the communication operator
makes all the core network nodes equipped with necessary capabilities
and functions to successfully connect to an MTC devices and a handset
20 terminal, the communication operator cannot provide the service to both
of the MTC device and the handset terminal. The same applies to the
MBMS service.
[0013]
If an MTC device and a handset terminal could respectively be
25 connected to appropriate core network nodes, the communication
operator is allowed to arrange relatively inexpensiv;e core network
nodes fo,r a handset terminal and relatively inexpensive. core network
nodes for a MTC device in combination (second knowledge of the
present inventors).
3 0 [00 l4]
If this is the case, compared with installing relatively expensive
core network nodes, each of which is compatible with both of a handset
terminal and a MTC device, an equipment cost in a whole system can be
reduced more efficiently (third knowledge of the present inventors).
l.i
t0
[0015]
Thus, the present invention has been'made to solvq the above
issues, and an object of the present invention is to prorii" a systeh, &
method, and a device for reducing an equipment cost in an entirety of a
system more efficiently and achieving cost reduction.
[0016]
The present invention that solves the above issues generally has
the following configuration (but not limited thereto).
[0017] .,
According to an aspect of the present invention, there is provided
a communication system including a core network for a mobile
communication system, wherein the core network comprises a plurality
of nodes, each node serving as a node to manage mobility of a terminal,
the plurality of nodes being different to each other witli regard to
service functions that the nodes provide to a terminal, and
wherein based on subscriber information and terminal
information, a node to be connected to the terminal is selected from
among the plurality of nodes, d"pending on a service characteristic
utilized by the terminal or on a type of the terminal, and the terminal is
connected to the selected node. There is also provided a mobile
communication system, comprising:
a terminal (uE(user Equipment) MS (Mobile Station))
supporting a function associated with MTC (Machine Type
C ommuni cation);
a base station; and
a specific MME (Mobility Mana!ement Entit,y) or SGSN (a
serving GPRS (General Packet Radio Service) support Node),
wherein the terminal supporting the function associated with
MTC is c0nfigured to provide the base station with information
indicating that an RRC (Radio Resource Control) connection request
includes the function, and
wherein the base station is configured to use the indication
information provided by the terminal supporting the function to steer
the terminal supporting the function to the specific MME or SGSN, or to
l5
20
25
30
10
/r
select the specific MME or SGSN.
[0018] 'l
According to another aspect of the present invention, there is
provided a communication method, comprising:
arranging a plurality of nodes for the terminal in a mobile
communication system core network, the nodes serving as nodes for
managing mobility of a terminal, and being different to each other with
regard to service functions that the nodes provide to a terminal;
selecting, based on subscriber information u'rrd terminal
information, a node to be connected to the terminal from among the
plurality of nodes, depending on characteristics of a service used by the
terminal or on a type of the terminal; and
connecting the terminal to the selected node. There is also
provided a communication method for a mobile communication system
comprising at least a terminal (UE (User Equipment) or an MS (Mobile
Station)) supporting a function relating to MTC (Machine Type
communication), a base station, and a specific MME (Mobility
Management Entity) or SGSN (Serving GPRS (General Packet Radio
Service) Support Node), the method comprising:
the terminal supporting the function providing the base station
with information indicating that an RRC (Radio Resource Control)
connection request includes the function; and
the base station using the indication information provided by the
terminal to steer the terminal supporting the function to the specific
MME or'SGSN, or to select the specific MME or SGSN.
[0019] ,_
According to another aspect of the present invention, there is
provided a node apparatus that performs control to select, as a mobility
management node apparatus to manage mobility of a terminal, another
mobility management node apparatus compatible with a service
characteristic utilized by the terminal or a type of the terminal, based
on subscriber information and terminal information to connect the
terminal to the selected another mobility management node apparatus.
There is also provided a base station in a mobile communication system
15
20
25
30
10
arArr.re,
comprising at least a terminal (UE (User Equipment) or an MS (Mobile
Station)) supporting a function relating to MTC (Machine Type
Communication) and a specific MME (Mobility Management Entity) or
SGSN (Serving GPRS (General Packet Radio Service) Support Node),
wherein the base station comprises '1
a unit configured to receive information indicating that an RRC
(Radio Resource Control) connection request includes the function from
the terminal supporting the function, and
a unit configured to use the indication information provided by the
terminal supporting the function to steer the terminal supporti.ng the
function to the specific MME or SGSN, or to select the specific MME or
SGSN. There is also provided a terminal in a mobile communication
system comprising at least a base station and a specific MME (Mobility
Management Entity) or SGSN (Serving GPRS (General Packet Radio
Service) Support Node), and that is a terminal (UE (User Equipment) or
an MS (Mobile Station)) supporting a function relating to MTC
(Machine Type Communication), the terminal comprising
a unit configured to provide the base station with information
indicating that an RRC (Radio Resource Control) connection request
includes the function and
a,unit configured to cause the base station to use.the indication
information provided by the terminal to steer the terminal supporting
the function to the specific MME or SGSN, or to select the specific
MME or SGSN.
[0020]
According to the present invention, cost
achieved by reducing the equipment cost in the
system more efficiently.
BRIEF DESCRIPTION OF THE DRAWINGS
reduction can be
whole core network
[002 r ]
Fig. l is a diagram illustrating a system configuration according to a
first exemplary embodiment of the present invention.
Fig. 2 is a diagram illustrating a system configuration according to a
second exemplary embodiment of the present invention.
t5
20
25
30
)-Lt I
Fig.3 is a diagram illustrating a sequence according to a first example
of the present invention.
Fig. 4 is a diagram illustrating a sequence according to a second
example of the present invention.
5 Fig.5 is a diagram illustrating a sequence according to a ihira example
of the present invention.
Fig. 6 is a diagram illustrating a sequence according to the third
example of the present invention.
Fig.7 is a diagram illustrating a sequence according to a fourth example
10 of the present invention.
Fig.8 is a diagram illustrating a sequence according to a fifth example
of the present invention.
Fig. 9 is a diagram illustrating a sequence according to the fifth
example of the present invention.
15 Fig. l0 is a diagram illustrating a sequence according to a sixth example
of the present invention.
Fig. 11 is a diagram illustrating a sequence according to a seventh
e.xample of the present invention.
Fig. l2 is a diagram illustrating a sequence according to an eighth
20 example of the present invention.
Fig. 13 'is a diagram illustrating a sequ€nce according to the eighth
example of the present invention.
Fig. 14 is a diagram illustrating a sequence according to a ninth
example of the present invention.
25 Fig. 15 is a diagram illustrating a sequenc e according to a tenth
example of the present invention. i
Fig. l6 is a diagram illustrating a sequence according to the tenth
example of the present invention.
PREFERRED MQDES 100221
30 First, an outline of the present invention will be described with
reference to Figs..l and 2. According to the present invention, a corenetwork
includes a plurality of nodes (21122 in Fig. I or l2lll22 in Fig.
2) that are different to each other with respect to service functions'
provided for a terminal. Based on subscriber information and terminal
10
tl trl
information, a node to be connected to the terminal is selected from the
plurality of nodes, in accordance with a service characteristic utilized
by the terminal or on a type of the terminal. The terminal (1 in Fig. 1
or 101 in Fig.2) is connected to the selected node. Namely, in the core
network, a node with a predetermined specific service providing
function (22 in Fig. 1 or 122 in Fig. 2) and a node without the specific
service providing function (21 in Fig. I or 121 in Fig. 2) are installed in
combinati on.
[0023 ]
Thus, according to the present invention, by installing both types,
namely, a node optimized with the specific service providing function
and a node without the specific service providing function as the nodes
that can be connected to the terminal(s), the cost in the whole system
can be reduced further, as compared with cases in which all the nodes in
the core network are provided with capabilities and functions for all
servlces.
10024)
According to the present invention, in a mobile terminal
communication network, a terminal can be connected to a specific core
network node, depending on a condition such as a service characteristic
or a terminal type.
[002 s ]

A General MME'(a mobility management entity), upon reception of an
Attach Request from a UE (User Equipment, also termed as a user
device, a terminal, or a mobile station) determines wheJher the UE is of
a type that uses a speci.fic service, based on subscriber information and
terminal information. When the UE is this type, in order.to connect
the UE to a Customized MME, the General MME. transmits an MME
re-selection request signal (a mobility management entity re-selection
request signal) to an eNodeB (evolved NodeB: a base station apparatus).
[0026]
By re-transmitting, by the eNodeB, an Attach Request to the
Customized MME, the UE is connected to the Customized MME.
l5
20
25
30
l,l
10
[0027 )

A General MME, upon reception of an Attach Request from a UE,
transmits an MME change request signal (a mobility management entity
change request signal) to the Customized MME, in order to connect the
UE to a Customized MME. By continuing an Attach Procedure by the
Customized MME, the UE is connected to the Customized MME.
[0028]

A General MME, upon reception of an Attach Request from a UE,
transmits, to the UE, an Attach Reject, to which is added an identifier
of the Customized MME, in order to connect the UE to a Customized
MME. The UE, by re-transmitting an Attach Request, to which is
added the identifier of the Customized MME to an Attach Request by the
UE, is connected to the Customized MME.
[002e]

A UE transmits, to an eNodeB, an RRC (Radio Resource Control)
Connection Request (radio resource connection request), to which is
added connection request information requesting connection to a
Customized MME (specific MME). The eNodeB, which has received
the RRC connection request, when transmitting, to an MME, an Attach
Request from the UE with RRC Connection established, selects the
Customized MME to make the UE connected to the Customized MME.
[003 0]

When a General MME with a session with a UE being established,
performs release (S1 Release) of Sl connection established between an
eNodeB and the General MME, the General MME instructs the eNodeB
to select a Customized MME, in next selection of an MME. Then after,
when the UE transmits a location management area update request (a TA
(Tracking Area) Update Request), the eNodeB selects the Customized
MME to make the UE connected to the Customized MME.
[0031]
15
20
25
30
10
lJr.u

A General SGSN (Serving GPRS (General Radio Packet Service)
Support Node: which is described as "serving GPRS support node" in
the claims), upon reception of an Attach Request from a UE, determines
whether the UE is of a type that uses a specific service based on
subscriber information and terminal information. If the UE is this
type, in order to connect the UE to a Customized SGSN, the General
SGSN transmits an SGSN re-selection request signal to an RNC (a Radio
Network controller). By transmitting an Attach Request to the
Customized SGSN, the RNC make the UE connected to the Customized
S GSN.
[0032]

A General SGSN, upon reception of an Attach Request from a UE,
transmits an SGSN change request signal to the Customized SGSN', in
order to connect the UE to a Customized SGSN. By continuing an
Attach Procedure by the Customized SGSN, the UE is connected to the
Custo mized S GSN.
[0033]

A General SGSN, upon reception of an Attach Request from a UE,
transmits, the UE,. an Attach Reject, to which is added an identifier of
the Customized SGSN,in order to connect the UE to a Customized SGSN.
The UE, by re-transmitting an Attach Request, to which is added the
identifier of the Customized SGSN to an Attach Request, is connected to
the Customized SGSN.
[003 4]

A UE transmits, to an RNC, d connection request (an RRC Connection
Request), to which is added connection request information requesting
connection to a Customized SGSN. The RNC, which has reQeived the
RRC connection request, when transmitting, to an SGSN, &fr Attach
Request from the UE with RRC Connection established, selects the
Custo mized SGSN to make the UE connected to the Customized SGSN.
15
20
25
30
10
10
ll
[003 5 ]

When a General SGSN with a session with a UE being established,
performs. Iu Release, the General SGSN instructs an RNC to select a
Customized SGSN, in next selection of an SGSN. Then after, when the
UE transmits a location management area update request (an RA
(Routing Area) Update Request), the RNC selects the Customized SGSN
to make the UE connected to the Customized SGSN.
[003 6]
As described in the above Modes 1 to 10, according to the present
invention, a core network node is selected and connected to a terminal,
based on characteristics of a service used by the terminal. In this way,
in the core network, nodes with specific service providing functions and
nodes without such functions can be arranged in combination. Namely,
the nodes can be distinguished, by optimizing specific nodes to have
specific service providing functions and by configuring other nodes
without such specific service providing functions. As a result, the
equipment cost in the whole system can be reduced. The following
describes exemplary embodiments and specific examples with reference
to the drawings.
,
[003 7]

Fig. I illustrates exemplary embodiment I of the present invention. As
exemplary embodiment 1, a configuration with EPC (Evolved Packet
Core) will be described. In this configuration, a UE transmits an
Attach Request and the UE is connected to a Customized MME.
[0038]
In Fig. 1, a UE I (user equipment) is a terminal that receives a
service from a Customized MME. For example, the UE l may be the
above described MTC device, MBMS-compatible terminal or the like.
In the case wherein the UE I is a normal mobile station that utilizes a
normal service, such as a mobile phone terminal or a smartphone (a
terminal that is not compatible with a specific service such as MTC or
MBMS), the UE 1 is connected to a General MME. In addition, as will
15
20
25
tl
30
l0
l ,r,
be described below, when the Customized MME is selected in response
to an Attach Request from a normal mobile station (for example, from a
terminal that is not compatible with a specific service such as MTC or
MBMS), re-selection of an MME is performed and UE I is re-connected
to the General MME
[003e]
An eNodeB 11 is a base station apparatus in LTE (Long Term
Evo lution)
[0040]
An MME 21 and an MME 22 are mobility management devices
introduced in EPC. The Customized MME 22 is a Customized MME to
which the UE l needs to be connected and the General MME (21) is an
MME other than such Customized MME. Though not limited thereto,
the Customized MME 22, for example, may be configured, as an MME
customized for a machine communication (MTC) service and for
terminals comp.atible therewith (M2M devices) (for example, the
C-Plane handling network control is reinforced). Or, the Customized
MME 22 may be c.onfigured as an MBMS-compatible MME.
[0041]
An HSS (Home Subscriber Server) 31 is a database storing
subscriber information.
loo 42)
An S-GW (Serving GateWay) 41 and a P-GW (Packet data network
GateWay) 5l are apparatuses handling the user plane.
[0043 ]
A service network 61 is an external network. I
[0044]
In Fig. 1, the eNodeB corresponds to an apparatus in a radio
access network (RAN) and the MMEs, the S-GW, the P-GW, and so forth
correspond to apparatuses in a core network (CN). . '|
[004s]
Next, the above exemplary embodiment I will be described based
on several examples. Different control schemes are described in the
respective examples. Examples 1 to 5 correspond to the above Modes 1
l5
20
25
30
t2
l0
lf llrt
to 5, respectivelY.
[0046]

Fig. 3 is a sequence diagram illustrating an operation according to
example l.
In Fi g. 3,
UE corresponds to the UE 1 in Fig. 1,
eNodeB corresponds to eNodeB 1 I in Fig. l,
General MME" corresponds to the General MME 2l in Fig. 1,
Customized MME corresponds to the Customized MME 22 in Fig. 1,
Serving GW corresponds to the S-GW 4 t in Fig. 1,
PDN GW corresponds to the P-GW 51 in Fig. l, and'
HSS corresponds to the HSS 31 in Fig. 1.
[0047]
"PCRF" is a Policy and Charging Rules Function. In addition,
an EIR (Equipment Identity Register) stores IMEI (International Mobile
Equipment Identity) and the like and is connected to an MME via an S13
interface.
[004 8]
In Fig. 3, for example, "1. Attach Request", raprdsents that
transmission of an Attach Request from the UE to the eNodeB is
sequence 1. To distinguish the reference character of this sequence
from reference character 1 of the UE in Fig. 1 (from the reference
characters of the components), this sequence number I will be
represented in parentheses as "Attach Request (1)" in the following
description. The other sequence numbers are also rqpresented in the
same way. In addition, the sequence numbers in Fig.'4 and in the
subsequent sequence diagrams will also be represented in the same way.
Fig.3 is based on Figure 5.3.2. l-1: Attach Procedure in 3GPP TS23.401
and the sequence numbers are in accordance with this figure. Details
of each sequence are described in 3GPP TS23.401 5.3.2. Hereinafter,
the operation sequence will be described with reference to Figs. 1 and 3.
[004e]
As illustrated in Fig. 3, when the UE 1 transmits an Attach
15
20
25
30
13
10
llltllllr
Request.(1), first, the eNodeB i1 receives the Attach Request (1).
Next, the eNodeB 11 relays the Attach Request (2) to an MME.
[005 o]
At this sequence, the eNodeB l1 cannot uniquely determine
whether to forward the Attach Request (2) to the Genoral MME 21 or to
the Customized MME 22. Thus, there are cases where the eNodeB 11
forwards the Attach Request (2) to the General MME 21.
[00s 1]
After receiving the Attach Request (2), the General MME 2l
acquires terminal information (ME Identity) from the UE 1 via an
Identity Request/Response (4, 5b).
l00s2l
It is noted that the General MME 2l transmits an ME Identity
Check Request (5b) to an EIR, and the EIR retunes an ME Identity
Check Ack (not illustrated) to the General MME. In addition, in
coordination with the HSS 31, the General MME 2l performs
authentication and acquires a subscriber profile. Namely, in this case,
at least, the General MME 21 performs authentication and acquires a
subscriber profile.
[00s3]
The General MME 21, on acquisition of the terminal information
and the subscriber profile, determines whether to connect the UE I to
the General MME 2l or to the Customized MME 22. .
[00s4]
When the General MME 2l determines that the UE l needs to be
connected to the General MME 21, the General MME 21 continues a
normal Attach Procedure.
[00ss]
When the General MME,2l determines that the UE 1 needs to be
connected to the Customized M}y'rB 22, the General MME'21 transmits,
to the eNodeB I l, an MME selection signal (an MME re-selection
command) (S I AP (S I application) signal newly introduced in the
present exempl ary embodiment), in order to instruct re-selection of an
MME.
l5
20
25
30
t4
10
I' !i'
[00s6]
In this sequence, the General MME 21 sets an identifier of'th'e
Customized MME 22 (for example, a GUMMEI (Globally Unique MME
ldentity)) in the MME re-selection Command signal. Namely, before
creation of a bearer in the core network, the General MME 2l transmits,
to the eNodeB, a re-selection request, in which the necessary
information (GUMMEI) for selecting a new MME is included. The
MMEs is equipped with a function of determining whether the UE is a
re - sel ection target,..
[00s 7]
When the eNodeB I I receives the MME re-selection Command'
signal, in accordance with the identifier set in this signal, the eNodeB
I I selects the Customized MME 22 and forwards the Attach Request (2)
to the Customized MllE 22. Since the Customized MME 22 needs an
NAS (Non-Access Stratum) parameter of the Attach Request (used in
authentication between the UE and the MME), the eNodeB 11
re-transmits the Attach Request. The eNodeB 11 .needs to be equipped
with a function of storing such NAS message.
[00s8]
Since the new MME (: the Customized MME 22) cannot
determine the old MME (= the General MME), the new IvIME iannot take
over Context from the old MME (= the General MME). Thus, the new
MME (: the Customized MME: MME 22) also needs to perform
authentication and acquire the subscriber profile.
Io0se]
After receiving the Attach Request signal, the Qustomized MME
22 acquires the terminal information via an Identity Request/Response.
In addition, the Customized MME 22 performs authentication and
acquires a subscriber profile in coordination with the HSS 31. Namely,
the Customized MME 22 performs the same processing as that performed
by the General MME 21.
[0060]
After acquiring the terminal information and the subscriber
profile, the Customized MME 22 determines whether to connect the UE
l5
20
25
30
15
Ir ltrllll,
I to the General M}l4E 21 or to the Customized M}lE 22.
[0061]
In this case., since the Customized MME 22 has been selected
after re-selection by the eNodeB 11, the Customized MME 22 continues
5 a normal Attach Procedure without transmitting an MME re-selection
Command signal. Namely, the following sequences are performed:
- transmission of an Update Location Request (8) fiom the Customized
MME 22 tO thc HSS 31,
- transmission of an Update Location Ack (11) from the HSS 3l to the
I 0 Custo mized MME 22,
- transmission of a Create Session Request (12) from the Customized
MME 22 to the S-GW 4l ,
: - transmission of a Create Session Request (13) from the S-GW 41 to the
P-GW 51,
l5 - PCEF Initiated IP-CAN Session Establishment/ModificatiOn ( l4) by
the P-GW 51,
- transmission of a Create Session Response (15) from the P-GW 51 to
the S-GW 41,
- transmission of First Down Link Data from the P-GW 51 to the S-GW
20 4l (if not handover (HO)),
- transmission of a Create Session Response (16) from the S-GW 41 to
the customized MME22 ,
II - transmission of an Initial Context Setup Request/Attach Accept) (17)
from the customized M}lE 22 to the eNodeB 11,
25 - transmission of an RRC Connection Reconfiguration (18) from the
eNodeB 11 to the UE 1, i
- transmission of an RRC Connection Reconfiguration Complete (19)
from the UE I to the eNodeB 11,
- transmission of an Initial Context Setup Response (20) from the
30 eNodeB 1l to the Customized MME 22,
- Direct Transfer (21) from the UE 1to the eNodeB,
- transmission of an Attach Complete (22) from the eNodeB 11 to the
Customized MME 22,
- transmission of First Uplink Data from the UE I to the S-GW 41 and
t6
lr ll'Lttrl
the P-GW 51,
- transmission o.f a Modify Bearer Request (23) from the Custo mized
MME 22 to the S-GW 41 ,
- transmission of l Modify Bearer Request (23a) from the S-GW 41 to
5 the PDN,
- transmission of a Modify Bearer Response (23b) from the PDN to the
s-Gw 41,
- transmission of a Modify Bearer Response (24) from the S-GW 41 to
the Customized MME 22, and
10 - transmission of First Downlink data from the P-GW 51 and the S-GW
41 to the UE 1.
[0062]
In addition, the General MME 2l and the Customized MME 22 are
equipped with a function of determining which MME needs to be
l5 connected to the UE 1. This determination is made based on
information transmitted from the UE 1. The'information.may be:
- tMSI (International Mobile Subscriber Identity),
- IMEI (International Mobile Equipment Identity: (terminal Identity)),
- UE network capability,
20 - MS network capability,
- Mobile station classmark 2,
- Mobile station classmark 3,
Device properties,
- a new parameter of an Attach Request signal which will be added in
25 the future, or
- an identifier of a part of these parameters (for e4ample, a PLMN
(Public land Mobile Network)-id included in the IMSI).
Alternatively, the above determination may be made based on
information transmitted from the HSS 31. The information may be:
30 - Feature-List,
- APN (Access Point Name),
- a new parameter of an Update Location Answer/Insert Subscriber Data
Request signal which will be added in the future, or
- an identifier of a part of these parameters.
t7
l0
llJht
Any one of or a combin.ation of these items of information may be used.
for the above determination.
[0063 ]
In addition, in the present example, even when an Attach Request
signal is forwarded from the UE I that needs to be connected to the
General MME 21 to the Customized MME 22, the Customized MME 22
can request the eNodeB 11 to select the General MME 2l in a like
manner. For example, if the UE 1 is a normal mobile station (for
example, a normal mobile station that is not compatible with a special
service such as MTC or MBMS) and if the UE 1 is first connected to the
Customized MME 22, the General MME 21 is' selected and a. service is
provided from the General MME 21.
[0064]
As described above, in the present exemplary embodiment, an
MME instructs the eNodeB to perform re-selection of an MME. In
response to the instruction, the eNodeB performs re-selection of an
MME and the Attach Procedure is continued. In this way, the UE can
be attached to an approPriate MME
[006s]

As example 2, another example with EPC (Evolved Packet Core) will be
described. In this example, the UE transmits an Attach Request and
the UE is connected to the Customized MME. In example 2, the same
system configuration as that in example l will be used.
[0066]
Fig.4 is a sequence diagram illustrating an ope,ration according
to example 2. Fig. 4 is based on Figure 5.3.2. 1-1: Attach Procedure in
3GPP TS23.401 and the sequence numbers are in accordance with this
figure. Details of each sequence are described in 3GPP TS23.401 5.3.2.
Hereinafter, the operation will be described with reference to Figs' 1
and 4.
[0067]
When the UE l transmits an Attach Request (l), the eNodeB 11
receives, the Attach Re.quest (1). Next, the eNodeB.ll relays the
t5
20
25
30
l8
l0
]LIL
Attach Request (2) to an MME. At this sequence, the eNodeB 11
cannot uniquely determine whether to forward the Attach Request (2) to
the General MME 2l or to the Customized MME 22. Thus, there are
cases where the eNodeB 11 forwards the Attach Request (2) to the
General MME 21.
[0068]
After receiving the Attach Request (2), the General MME 2l
acquires terminal information (ME Identity) via an Identity
Request/Response (5b). In addition, in coordination with the HSS 31,
the General MME 21 performs authentication.and acquires a subscriber
profile. Namely, in this case, at least, the General fr{VfE Zf performs
authentication and acquires a subscriber profile.
[006e]
After acquiring the terminal information and the subscriber
profile, the General MME 21 determines whether to connect the UE 1to
the General MME 2l or to the Customized MME 22. If the General
MME 21 determines that the UE l needs to be connected to the General
MME 21 , the General MME 21 continues a normal Attach procedure.
[0070]
If the General MME 2l determines that the UE I needs to be
connected to the Customized MME 22, to instruct change of an MME,
the General MME 2l transmits an MME change request signal (MME
Change Request) (a GTP (GPRS Tunneling Protocol) signal newly
introduced in the present example) to the Customized MME 22.
[0071]
In this sequence, the General MME 2l sets conJext information
generated by authentication of the terminal and acqu'isition of the
subscriber profile in the MME change request signal (MME Change
Reque st).
Ioot z)
The Customized MME 22, upon rec'eption of the MME change
request signal (MME Change Request), holds the context information
set in the MME change request signal and transmits an MME Change
Response signal (a GTP signal newly introduced in the present example)
15
20
25
30
l9
1t Ir
l0
the MME.
1007 4l
In order to notify the HSS 31 of the changed MME, the
Customized MME 22 transmits an Update.Location Request. The
subsequent Attach Procedure is performed by the Customi2ed M}y'-E 22.
[007s]
to the General MME 21.
[0073]
Subsequently, the Customized
Location Request (8) to the HSS 31 to
MME 22 transmits an Update
notify the HSS 31 of change of
MME 22 are equipped
to be connected to the
15
The Customized MME 22,
information received from the
performing re-authentication.
[0076]
Subsequently, the Custo mized MME 22 continues the Attach
Procedure and the eNodeB l1 receives an Initial Context Setup
Request/Attach Accept) ( 17) from the Customized MME 22.
[0077]
The Initial Context Setup Request/Attach Accept ( 17) is a
response to the Attach Request (2) received by the General MME 21 .
The eNodeB 11 needs to include a function of receiving a Response from
another MME different from the General MME 21.
[0078]
Subsequently, the Customized MME 22 continues a normal Attach
in the case wherein security context
General MME 2l is valid, can omit
Procedure.
[007e]
The General MME 21 and the Customized
with a function of determining which MME needs
UE 1, as is the case with example 1.
[0080]
In addition, in the present example, even when an Attach Request
signal ii forwarded from the UE l that needs to be cohnected to the
General MME 21 to the Customized MME 22, the Customized MI|lE 22
can request the General MME 21 for change of an MME in a like manner.
20
25
30
20
10
tl
For example, in the case wherein the UE 1is a normal mobile station
(for example, a normal mobile station that is not compatible with a
special service such as MTC or MBMS), when the UE l is once
connected to the Customized MME 22, the Customized MME 22
transmits an MME change request signal (MME Change Request) to the
General MME 21. In this way, the General MME 2l 1.
t:le.cted and a
service is provided from the General MME 21.
[0081]
As described above, in the present example, the General MME
instructs the Customized MME about change of an MME. In response
to the instruction, the Customized MME accepts the change and
continues the Attach Procedure. In this way, the UE can be attached to
an appropriate MME. ,,
[0082]

As example 3, another example with EPC will be described. In this
example, the UE transmits an Attach Request and the UE is connected to
the Customized MME. In example 3, the same system configuration as
that in example 1 will be used.
[0083]
Figs.5 and 6 are sequence diagrams illustrating an operation
according to example 3. Figs. 5 and 6 are based on Figure 5.3.2. 1-1:
Attach Procedure in 3GPP TS23.401 and the sequence numbers are in
accordance with these figures. Details of each sequence are described
in 3GPP TS23.401 5.3.2. Hereinafter, the operation will be described
with referencp to Figs. 1, 5, and 6. i
[0084]
When the UE I transmits an Attach Request (1), first, the eNodeB
1l receives the Attach Request (l). Next, the eNodeB l1 forwards the
Attach Request (2) to an MME. However, the eNodeB 11 cannot
uniquely determine whether to forward the Attach Request (2) to the
General M}y4E 21 or to the Customized MME 22. Thus, there are cases
where the eNodeB 11 forwards the Attach Request (2) to the General
MME 2 1.
l5
20
25
30
2l
10
IUTU
[008s]
After receiving the Attach Request (2), the General MME 2l
acquires terminal information (ME Identity) via an Identity
Request/Response (5b). In addition, in coordination with the HSS 31,
the General MME 21 performs authentication and acquires a subscriber
profile.
[0086]
The General MME 21, on acquisition oi tt. terminaJ information
and the subscriber profile, determines whether to connect the UE 1 to
the General M}l4E 21 or to the Customized MII4E 22. If the UE 1 is to
be connected to the General MME 27, the General MME 2l continues a
normal Attach Procedure.
[0087]
If the UE 1 needs to be connected to the Customized MME 22, the
General MME 2l transmits an Attach Reject message t'b the UE 1,
instead of continuing the Attach Procedure. Namely, the General MME
2l transmits an Initial Context Setup Request/Attach Reject (17) to the
eNodeB 11.
[0088]
In this sequence, the General MME 2I sets a parameter for
instructing re-Attach (a new parameter introduced in the present
example) and a GUTI (Globally Unique Temporary Identity (Identifier))
parameter including a GUMMEI (Globally Unique MME identifier) (a
new parameter introduced in the present example) in the Attach Reject
signal, so that the eNodeB 1l can select the Customized MI|u4E 22 when
performing re-Attach. The GUTI parameter is formed by a GUMMEI
and an M-TMSI (Temporary Mobile Station Identity). An MMEI is
formed by an MCC (Mobile Country Code), an MNC (Mobile Network
Code), and an MME Identifier. While these parameters are parameters
that are newly introduced in the present example, since the eNodeB l1
is transparent, the eNodeB 11 is not affec.ted.
[008e]
The UE 1, upon reception of the Attach t
eNodeB I 1, as illustrated in Fig. 6, transmits,
Reject signal from the
to the eNodeB I I ,' the
15
20
25
30
22
10
ll
Attach Request (l) in which the GUTI is set (Attach by the GUTI), in
accordance with the parameter for instructing re-Attach set in the
Attach-Reject signal and the GUTI parameter. The eNodeB 11 decides
an appropriate MME from the GUMMEI included in the GUTI and
forwards the Attach Request (2) to the Customized MME 22.
[00e0]
The UE 1 is eqyipped with a function ofreceiving a GUTI in an
Attach Reject signal and using the GUTI specified in the Attach Reject
when transmitting a re-Attach (Attach Request (l) in Fig. 6). The
MMEs are equipped with a function of determining whether this UE is a
re-selection target.
[00e i ]
Subsequently, the Customized MME 22 continues a normal Attach
Procedure. While the GUTI is set in the Attach Request, the'
Customized MME 22 does not hold context information.
[00e2]
Thus, upon reception of the Attach Request signal, the
Customized MME 22 acquires terminal information via an Identity
Request/Response (4). In addition, the Customized MME 22 performs
authentication and acquires a subscriber profile in coordination with
the HSS 31.
[00e3 ]
In addition, the General MME 2l and the Customized MME 22 are
equipped with a function of determining which MME needs to be
connected to the UE 1, as is the case with example 1.
[0094] !
In addition," in the present example, even when an Attach Request
signal is forwarded from the UE I that needs to be.connected to the
General MME 21 to the Customized MME 22, the Customized MME 22
can urge the UE 1 to re-select an MME in the same manner. Namely, in
the case wherein the UE 1is a normal mobile station (for example, a.
normal mobile station that is not compatible with a special service such
as MTC or MBMS), when the UE 1is once connected to the Customized
MME 22, the Customized MME 22 transmits an Attach Reject signal to
15
20
25
30
23
10
1illn'
the UE 1 and urges the UE 1 to re-select the General MME 21. In this
w&y, since the UE I transmits a re-Attach Request signal, the General
MME 21 is selected and a service is provided from the General MME 21.
[00es]
As described above, in the present example, the General MME
instructs the UE to perform re-selection of an MME. In response to the
instruction, the UE specifies the Custo mized MME and an Attach
Procedure is continued. In this w&Y, the UE can be attached to an
appropriate MME.
[00e6]

As example 4, another example with EPC will be described. In this
example, the UE transmits an Attach Request and the UE is connected to
the Customized MME. In example 4, the same system configuration as
that in example I will be used. Fig.7 is a sequence diagram
illustrating an operation according to example 4. Fig.7 is based on
Figure 5.3.2.1-1: Attach Procedure in 3GPP TS23.401 and the sequence
numbers are in accordance with the figure. Details of each sequence
are described in 3GPP TS23.401 5.3.2. Hereinafter, the operation will
be described with reference to Figs. I and 7.
[009"ro
order to transmit an Attach Request (l) to an MME, the UE I
first, establishes RRC Connection with the eNodeB 11. In order to
establish RRC Connection, first, the UE l transmits an RRC Connection
Request signal to the eNodeB 11.
[0098] I
In this seauence, the UE 1 Sets a parameter indicating that the UE
1 needs to be connected to the Customized MME 22 (a User Identity, a
new Value or a. new parameter of establishment Cause (a value or a
parameter newly introduced in the present example), or an identifier of
a part of such parameters (a PLMN-id included in the IMSI, for
examp 1e) ).
[00ee]
A new parameter of the RRC Connection Request (a new value or
15
20
25
30
24
10
JIf,!trII,
a new parameter of establishment Cause) is implemented, so that the UE
I can notify the eNodeB that the UE 1 can be connected to the
Custo mized MME by using the RRC Connection Request. 'r
[0100]
The eNodeB I 1, upon
signal, stores information
connected to the Customized
Connection Procedure.
[0101]
After establishing RRC Connection, when the UE 1 transmits an
Attach Request (1), the eNodeB ll receives the Attach Request (1). In
this sequence, the eNodeB 11, from the information stored upon
reception of the RRC Connection Request (1), forwards an Attach
Request (2) to the Customized MME 22.
[0102]
After receiving the Attach Request (2), the Customized MME 22
continues a normal Attach Procedure.
[01 03 ]
In'addition, the UE I is equipped with a function'of instructing
the eNodeB 11 about which one of the General MME 2l and the
Customized MME 22 needs to be connected to the UE 1. Since the UE
l cannot store information about all the MMEs in the core netwbrk,
information indicating an MME type, a service type, or the like is used
for the instruction given to the eNodeB 11, instead of an identifier by
which a unique MME can be selected.
[0 r 04]
In addition, the eNodeB 1l is equipped
determining which MME needs to be connected to
[0r0s]
As described above, one of or a combination of a User Identity, a
new Value or a new parameter of Establishment Cause, and an identifier
of a part of such parameters in the RRC Connection.Request message is
used for selection of an MME by the eNodeB 11.
[0106]
reception of the RRC Connection Request
indicating that the UE l needs to be
MME 22 and continues the subsequent RRC
with a function of
the UE l.
15
20
25
30
25
10
l' ,i,
As described above, in the present example, the UE instructs the
eNodeB to select an MME. In response to the instruction, the eNodeB
specifies the Customized MME and an Attach Procedure is continued.
In this way, the UE can be attached to an appropriate MME.
[0107]

As example 5, another example with EPC will be described. In itit
example, the UE and the Customized MME are connected when Tracking
Area Update is performed. In example 5, the same system
configuration as that in example I will be used.
[0108]
Figs.8 arld 9 are sequence diagrams illustrating an operation
according to example 5. Fig. 8 is based on Figure 5.3.5-1: Sl Release
Procedure in 3GPP TS23.401 (see 3GPP TS23.401 5.3.5). Fig. 9 is
based on Figure 5.3.J.1- l: Tracking Area update procedure with
Serving GW change (see 3GPP TS23.401 5.3.3). The operation will be
described with reference to Figs. 1,8, and 9 (and a part in Fig.3).
[01 0e]
When the UE l transmits an Attach Request (see I in Fig.3), first,
the eNodeB I I receives the Attach Request. The eNodeB 1l relays the
Attach Request to an MME (see 2 in Fig.3).
[0rr0]
The eNodeB 11 cannot uniquely determine whether to forward the
Attach Request to the General MME 21 or to the Customized MME 22.
Thus, there are cases where the eNodeB l1 for,wards the Attach Request
to the General MME 2l . ', '
[0 ] 11]
After receiving the Attach Request, the General MME 21 acquires
terminal information (ME Identity) via an Identity Request/Response
(see 4,5b in Fig.3). In addition, the General MME 2L performs
authentication and acquires a subscriber profile in coordination with
the HSS 31.
[01 l2]
The General MME 21, on acquisition of the terminal information
l5
20
25
30
26
1[Ir"
t0
and the subscriber profile, determines whether to connect the UE I to
the General MME'21 or to the Customized MME 22. Subsequently, a
normal Attach Procedu(e is continued. If the UE 1 is to be connected
to the General MME 2l , processing completes at this point.
[0113]
If the UE I needs to be connected to the Customized MME 22, the
General MME 2l performs Sl Release to cause the UE I to perform
Tracking Area Update (TA Update), as illustrated in Fig. 8. The
General MME 21 transmits an S1 UE Context Release Command (4) to
the eNodeB 11.
[01 14]
The General MME 21 gives an instruction about an MME that the
eNodeB needs to select when establishing S l .Connection with an MME
next time, by using an MME identifier (for example, a CUfrrffr{pl) in the
Sl UE Context Release Command (4). A parameter, for example, the
GUMMEI specifying the next MME to be selected by the eNodeB when
S1 Release for activation of Load Balancing TAU is performed, is a new
parameter. Even after S1 Release is completed, while the eNodeB 11 is
holding session information for the UE 1, the eNodeB 1l continues to
hold the MME identifier as information for selection of th.e next MME.
[011s]
After S I Release being performed, next, the UE I transmits a
TAU Request (2), as illustrated in Fig. 9. First, the eNodeB 11
receives the TAU Request (2) from the UE I and forwards the TAU
Request (3) to an MME. The eNodeB 11, as in a state of Sl Release
being completed, performs re-selection of an MME and establishes S 1
C onnecti on. The eNodeB l1 selects the Customized MME, in
accordance with the GUMMEI indicated by the old MME (= the General
MME) at the time of Sl Release. The eNodeB 1l is equipped with a
function of holding the next GUMMEI per UE.
[0116]
When selecting an MME, the eNodeB 1l selects the Customized
MME 22 in accordance with the MME ldentifier of the GUMMEI
indicated in the Sl UE Context Release Command signal received from
l5
20
25
30
27
l0
till
the General MME 21 . Since the GUTI (GUMMEI) on NAS. indicates the
old MME (: General MME), m contexts can be acquired.
[0117]
After receiving the TAU Request (3), the Customized MME 22
continues a normal TA Update Procedure. The Customized MME 22
transmits a Context Request (4) to the General MME 2l and receives a
Context Response (5).
[0118] ,,
The Customized MME 22, in the case wherein the S-GW is
relocated, transmits a Context Acknowledge (7) including an instruction
for changing the S-GW to the General MME. When the Customized
MME 22 selects a new S-GW 4l (new Serving GW), the Customized
MME 22 transmits a Create Session Request (8) to the new S-GW 41.
[01 l e]
The new S-GW 41 (new Serving GW), responsive to this Create
Session Request (8), transmits a Modify Bearer Request (9) to the P-GW
51. After receiving a response to the Modify Bearer Request (9) from
the P-GW 51, the new S'GW returns a Create Session Response (11) to
the Customized MME 22.
[0120]
The Customized MME 22 transmits an Update Location (12) to the
HSS 31.
[012 r ]
The General MME 21, upon reception of a Cancel Location (13)
from the HSS 31, deletes MM contexts and transmits a Cancel Location
Ack (14) to the HSS 31. The HSS 3l transmits an Update Location Ack
(17) in response to the Update Location (12) to the Customized MME
22.
[0 r22)
The General MME 2l transmits a Delete Session Request (18) to
the old S-GW 4'1 (old Serving GW), and the old S-GW 41 (old Serving-
GW) transmits a response (19) to the Delete Session Request (18) to the
General MME 2i.
[0123]
15
20
25
30
28
tl
The Customized M};4E 22 transmits a TAU Accept (20) to the UE0
l.
t0 t24l
t0
If a GUTI is included in the TAU Accept (20), the UE I returns a
TAU Complete (21) to the Customized MME 22. The UE l uses this
TAU Complete (21) as an acknowledge response to the received signal
TAU Accept (20).
[01 2s ]
The General MME 2l and the Customized MME 22 are equipped
with a function of determining which MME needs to be connected to the
UE 1. This function is the same as that in example 1.
[0r26]
In the present example, in the same manner as described above,
when the eNodeB ll receives a TA Update Request from the UE 1 that
needs to be connected to the General MME 2I (for example, from a
normal mobile station (a normal mobile station that is not compatible
with a special service such as MTC or MBMS), by selecting the General
MME, the UE 1 is connected to the General MME 21 and a service is
Update Procedure has been
9. However, a feature in the
selects an MME. Thus, the
for example, other Procedures,
as a Service Request.
1
As described above, according to the present 'example, the
General MME instructs the eNodeB to perform re-selection of an MME.
In response to the instruction, the eNodeB specifies the Customized
30 MME when selecting the next MME, and the Procedure is continued.
In this way, the UE can be connected to an appropriate Uf,Ae.
l012el

As exemplary embodiment 2, a configuratio'n with UMTS (Universal
29
15
20
25
provided from the General MME 21.
l0 1271
In the present example, the TA
performed based on the sequence in Fig.
present example i'r that the eNodeB l1
present example can also be realized by,
for re-establishing S 1 Connection, such
[0128]
10
Mobile Telecommunications System) *itt be described. In this
configuration, a UE transmits an Attach Request and the UE is
connected to a Customized SGSN. Fig.2 illustrates a system
configuration according to exemplary embodiment 2.
[013 0]
A UE 101 is a terminal that receives a service from a Customized
SGSN. For example, the UE 101 may be the above MTC device or
MBMS-compatible terminal. In the case wherein the UE 101 is a
normal mobile station that utilizes normal services such as a mobile
phone terminal or a smartphone (a terminal that is not compatible with a
specific service such as MTC or MBMS), the UE 101 is connected to a
General SGSN. In addition, as will be described below, when the.
Customized SGSN is selected in response to an Attach Request from a
normal mobile station (for example, from a tefminal that is not
compatible with a specific service such as MTC or MBMS), re-selection
of an SGSN is performed. As a result, the UE I is connected to the
General SGSN.
[0131]
A NodeB 111 and an RNC (a radio network controller) 17l are
devices for Radio access adopted for the UMTS system.
[0132]
A General SGSN 121 and a Customized SGSN ,122, ar,e devices,
each of which covers an area and is used in the UMTS. Depending on
the connection mode, the General SGSN 121 and the Customized SGSN
122 handle the user plane. If the SGSNs do not handle the user plane,
the user plane is set between an S-GW and an RNC. i
[0r33]
An HLR (Home Location Register) 131 is a database storing
subscriber information.
[0134]
A GGSN 141. (Gateway GPRS (General Radio Packet Service)
Support Node: which is described as "gateway GPRS support node" in
the claims) is a gateway device connected to an external network. A
service network I 61 is an external network (data packet network).
l5
20
25
30
30
[013s]
In Fig. 2, the NodeB I I I and the RNC 171 are devices in a radio
access network RAN. The SGSN, the GGSN, and so forth are devices
in a core network.
5 [0136]
Next, exemplary embodiment 2 will be described based on several
examples. Different control methods are described in the respective
examples. The following examples 6 to 10 correspond to the above
Modes 6 to 10, respectively.
10 [013 7]

Fig. 10 is a sequence diagram illustrating an operation according to
example 6 and is based on 3GPP TS 23.060 6.5 Fig.22.
[0r38]
15 In Fig. 10,
"MS (Mobile Station)" corresponds to the UE l0l in Fig.2,
"RAN (Radio Access Network)" corresponds to the NodeB'1ll and the
RNC 171 in Fig.2,
"General SGSN" corresponds to the General SGSN 121 in Fig.2,
20 "Customized SGSN" corresponds to Customized SGSN 122 in Fig.2,
"GGSN" corresponds to the GGSN 141 in Fig. 2, and
"HLR" corresponds to the HLR 131 in Fi g. 2.
[01 3 e]
A VLR of an MSC (Mobile Switching Center)/VLR (Visitor
25 Location Register) is a location register for CS services other than the
HLR. An EIR (Equipment Identifier Register) store-s identifiers of
valid mobile devices.
[0140]
An operation will be described with reference to Figs. 2 and,10.
30 Hereinafter, the UE 101 in Fig.2 will be used as the MS in Fig. 10.
[0141]
When the UE 101 (MS) transmits an Attach Request (1), first, the
NodeB lll receives the Attach Request (1) and forwards the Attach
Request (1) to the RNC l7l. The RNC l7l forwards the Attach
31
l0
Request ( I ) to an S GSN. However, the RNC 171 cannot uniquely
determine whether to forward the Attach Request to the General SGSN
12l or to the Customized SGSN 122. Thus, there are cases where the
RNC lll forwards the Attach Request to the General SGSN 121.
l0 1 421
After receiving the Attach Request, the General SGSN iZt
acquires terminal information via an Identity Request/Response (3, 4).
In addition, the General SGSN 121 performs authentication and acquires
a subscriber profile, in coordination with the HLR 131. Namely, in
this case, the General SGSN l2l performs authentication and acquires a
subscriber profile.
[0143]
The General SGSN 121, on acquisition of the
information and the subscriber profile, determines whether to connect
the UE 101 to the General SGSN Lzl or to the Customized SGSN 122.
In the case wherein the UE 101 needs to be connected to the General
SGSN l2l, the General SGSN l2l continues a normal Attach Procedure.
[0144]
In the case wherein the UE l0l needs to be connected to the
Customized SGSN 122, to instruct re-selection of an SGSN, the General
SGSN l2l transmits an SGSN re-selection Command (an'RANAP signal
newly introduced in the present example) to the RNC 17l. In this
sequence, the General SGSN l2l sets an identifier identifying the
Customized SGSN 122 in the SGSN re-selection..Command signal (for
example, an RAI (Routing Area Identifier) or an NRI (Network
Resource Identifier)). Namely, the General SGSN l2l ,transmits, to the
RNC l7l, an SGSN re-selection request in which necessary information
(RAI) for selecting the customized SGSN 122 is included. In the case
of re-selection being performed within a single pool, only the NRI may
be used. The SGSNs are equipped with a function of determining
whether the UE 10,1 is a re-selection target.
t014sl
When the RNC l7l receives the SGSN re-selection Command
signal, in accordance with the identifier set in this signal, the RNC 171
terminal
15
20
25
30
),L
10
selects the Customized SGSN 122 and forwards the Attach Request (1).
Since the customized SGSN 122 needs an NAS (Non Access Stratum)
parameter of the Attach Request, the RNC 17l transmits the Attach
Request. The RNC l7 | is equipped with a function of storing such
NAS message.
[0 r 46]
Since the new SGSN (: the Customized SGSN) cannot determine
the old SGSN (: the General SGSN), the new SGSN cannot take over
context. Thus, the new SGSN also needs to perform authentication and
acquire the subscriber profile. After receiving the Attach Request (2),
the Customized SGSN 122 acquires terminal information via an Identity
Request/Response. In addition, the Customized SGSN 12.2 performs
authentication and acquires a subscriber profile, in coordination with
the HLR 131. Namely, the Customized SGSN 122 performs the same
processing as that performed by the General SGSN l2l.
[01 4 7]
The Cust'omized SG.SN 122, on acquisition of the terminal
information and the subscriber profile, determines whether to bonnect
the UE 101 to the General SGSN 127 or to the Customized SGSN (022).
In this case, since the Customized SGSN 122 has been selected after
re-selection by the RNC l7l, the Customized SGSN 122 continues a
normal Attach Procedure, without transmitting an. SGSN re-selection
Command signal.
[0148]
In addition, the General SGSN l2l and the Customized SGSN 122
are equipped with a function of determining which SFSN needs to be
connected to the UE 101. This determination is made based on
information transmitted from the UE 101. The information may be:
- IMSI (International Mobile Subscriber Identity),
- IMEI,
- UE network capability, i
-MS network capability,
- Mobile station classmark 2,
-Mobile station classmark 3,
l5
20
25
30
33
10
- Device properties,
- a new parameter of an Attach Request signal which will be added in
the future, or
- an identifier of a part of these parameters (for example, a PLMN-id
included in the iMSI).
Alternatively, the above determination may be made based on
information transmitted from the HLR 131. The information may be:
- Feature-List,
- APN,
- a n,ew parameter of an Update Location Answer/Insert Subscriber Data
Request signal which will be added in the future, or
- an identifier of a part of these parameters.
Any one of or a combination of these items of information may be used
for the above determination.
[014e]
In addition, in the present example, even when an Attach Request
signal is forwarded from the UE 101 that needs to be connected to the
General SGSN l2l to the Customized SGSN l'22, the Customized SGSN
122 can request the RNC 171to perform re-selection of an SGSN in a
like manner. If the UE 101 is a normal mobile station (for example, a
normal mobile station that is not compatible with a special service such
as MTC or MBMS) and if the UE 101 is first connected to the
Customized SGSN 122, the General SGSN 121 requests the RNC I7l to
perform re-selection of an SGSN. As a result, the General SGSN l2l
is selected and a service is provided from the General SGSN 121.
[0150] i
As described above, in the present example, an SGSN instructs
the RNC to perform re-selection of an SGSN. In response to the
instruction, the RNC performs re-selection of an SGSN and the Attach
Procedure is continued. In this w&y, the UE can be attached to an
appropriate SGSN.
[01s1]

As example 7, another example with UMTS will be described.
15
20
25
30
34
In this
l0
example, the UE transmits an Attach Request and the UE is connected to
the Customized SGSN. In example 7, the same system configuration as
that in example 6 will be used. Fig. 11 is a sequence diagram
illustrating an operation according to example 7. Hereinafter, the
operation will be described with reference to Figs. 2 and 1l.
[01s2]
When .the UE 101 transmits an Attach Request (i), first, the
NodeB 111 receives the Attach Request ( I ). Next, the NodeB I I I
forwards the Attach Request to the RNC 171, and the RNC 171 forwards
the Attach Request to an SGSN. However, the RNC l7l cannot
uniquely determine whether to forward the Attach Request to the
General SGSN 121 or to the Customized SGSN 122. Thus, there are
cases where the RNC l7l forwards the Attach Request to' the General
SGSN 121.
[01s3]
The General SGSN 12l, upon reception of the Attach Request,
acquires terminal information via an Identity Request/Response. In
addition, in coordination with the HLR 131, the General SGSN l2l
performs authentication and acquires a subscriber profile. Namely, in
this case, at least, the General SGSN l2l performs authentication and
acquires a subscriber profile.
[01s4]
The General SGSN 12l, upon acquisition of the terminal
information and the subscriber profile, determines whether to connect
the UE 101 to the General SGSN l2l or to the Customized SGSN 122.
If the General SGSN l2l determines that the UE lr01 needs to be
connected to the General SGSN 127, the General SGSN 121 continues a
normal Attach procedure.
[0lss]
In the case wherein the UE 101 needs to be connected to the
Customized SGSN 122, in order to instruct change of an SGSN, the
General SGSN l2l transmits an SGSN Change Request (a GTP signal
newly introduced in the present exemplary embodiment) to the
Customized SGSN 122.
l5
20
25
30
35
10
[01s6] ,,
In this sequence, the General SGSN 121 sets context information
generated by authentication of the mobile station and acquisition of the
subscriber profile in the SGSN Change Request signal. Namely, when
the General SGSN 121 requests the Customized SGSN 122 for change of
an SGSN (SGSN Change), the General SGSN l2l notifies a new SGSN
(the Customized SGSN 122) of context. The SGSNs are equipped with
a function of determining whether the UE 101 is a re-selection target.
[01s7]
The Customized SGSN 122, upon reception of the SGSN Change
Request signal, holds the context information set in the SGSN Change
Request signal and transmits an SGSN Change Response signal (a GTP
signal newly introduced in the present exemplary embodiment) to the
General SGSN l2l.
[01s8]
Subsequently, the Customized S GSN I22 transmits an Update
Location signal (8) to the HLR 131 to notify the HLR 131 of change of
the S GSN.
[01se]
When security context information transmitted from the General
SGSN l2l is valid, the Customized SGSN 122 can omit performing
re-authentication.
[0160]
Subsequently, the Customized SGSN 122 continues the Attach
Procedure and the RNC l7l receives an Attach Accept signal (9) from
the Customized
'SGSN 122. Subsequently, u normal Attach Procedure
is continued.
t0 r 61l
The General SGSN l2l and the Customized SGSN 122 are
equipped with a function of determining which SGSN needs to be
connected to the UE 101, as is the case with example 6.
l0t 621
In the present example, even when an Attach Request signal is
forwarded from the UE 101 that needs to be connected to the General
15
20
25
30
36
l0
SGSN l2l to the Customized SGSN 122, the Customized SGSN 122 can
request the General SGSN l2l for changg of an SGSN in the same
manner. In the case wherein the UE 101 is a normal mobile station (for
example, a terminal that is not compatible with a special service such as
MTC or MBMS) and if the UE 101 is connected to the Customized SGSN
122, the Customized SGSN 122 selects the General SGSN 12l and a
service is provided from the General SGSN 121.
[0163]
As described above, in the present example, the General SGSN
instructs the Customized SGSN about change of an SGSN. In response
to the instruction, the Customized SGSN accepts the change and
continues the Attach Procedure. In this way, the UE can be attached to
an appropriate SGSN.
[0164]

As example 8, another example with UMTS will be described. In this
example, the UE transmits an Attach Request and the UE is connected to.
the Customized SGSN. In example 8, the same configuration as that in
example 6 will be used. Figs. l2 and 13 are'sequence diagrams
illustrating an operation according to example 8. Hereinafter, the
operation will be described with reference to Figs.2, 12, and 13.
[0]6s]
When the UE 101(MS) transmits an Attach Request (1), first, the
NodeB I I I receives the Attach Request (1). Next, the NodeB I 1l
forwards the Attach Request to the RNC l7l, and the RNC l7l forwards
the Attach Request to an SGSN. However, the &NC 17 | cannot
uniquely determine whether to forward thb Attach Rqquest to the
General SGSN 12l or to the Customized SGSN 122. Thus, there are
cases where the RNC 17l forwards the Attach Request to the General
SGSN 12I.
[0166]
After receiving the Attach Request (1), the General SGSN l2l
acquires terminal information via an Identity Request/Response (3).
In addition, in coordination with the HLR 131, the Gener'al SGSN 1,21
15
20
25
30
)t
l0
performs authentication and acquires a subscriber profile.
[0167]
The General SGSN l2l, on acquisition of the terminal
information and the subscriber profile, determines whether to connect
the UE 101 to the General SGSN l2l or to the Customized SGSN I22.
In the case wherein the UE l0l needs to be connected to the General
SGSN 121, the General SGSN l2l continues a norm'dl Attach Procedure.
[0168]
In the case wherein the UE 101 needs to be connected to the
Customized SGSN 122, the General SGSN L2l transmits an Attach
Reject signal (9) to the UE i01, instead of continuing the Attach
Procedure
[016e]
In this case, the General SGSN l2l sets a parameter for
instructing re-Attach and an RAI (Routing Aiea Identity).parameter (a
parameter newly introduced in the present exemplary embodiment) in
the Attach Reject signal, so that the RNC 17l can select the Customized
SGSN 122 when performing re-Attach. While these parameters are
parameters that are newly introduced in the present example, since the
RNC 171 is transparent, the RNC 171 is not affected.
[0170]
The UE 101 needs to are equipped with a function of'receiving an
RAI via an Attach Reject and using the RAI specified in the Attach
Reject when transmitting a Re-Attach. The SGSNs are equipped with a
function of determining whether the UE l0l is a re-selection target.
[0 r 71]
. The UE 101, upon reception of the Attach Reject signal (9),
transmits, to the RNC 171, the Attach Request signal (1) in which the
RAI has been set, in accordance with the parameter for instructing
re-Attach set in the Attach-Reject signal (9) and the RAI parameter
(re-Attach by a P-TMSI (Packet Temporary Mobile Subscriber
Identifier)), as illustrated in Fig. 13. The RNC 171 decides an
appropriate SGSN from the RAI and forwards the Attach Request to the
Customized SGSN 122.
15
20
25
30
38
10
[017 2]
Subsequently, the Customized SGSN 122 continues a normal
Attach Procedure
[0173]
While the RAI is set in the Attach Request, the Customized SGSN
122 does not hold context information. Thus, upon reception of the
Attach Request signal (l), the Customized SGSN 122 acquires terminal
information via an Identity Request/Response (3). In addition, the
Customized SGSN 122 performs authentication and acquires a
subscriber profile in coordination with the HLR l3l.
1017 4)
The General SGSN l2l and the Customized SGSN 122 are
equipped with a function of determining which SGSN needs to be
connected to the UE 101, as is the case with example 6.
[017s]
In the present example, even when an Attach Request signal is
forwarded from the UE 101 that needs to be connected to the General
SGSN (l2l) to the Customized SGSN 122, the Customized SGSN 122
can request the UE 101 for re-selection of an SGSN in a like manner.
If the UE l0l is a normal mobile station (for example, a terminal that is
not compatible with a special service such as MTC or MBMS) and if the
UE 101 is connected to the Customized SGSN 122, the Customized
SGSN 122 transmits an Attach Reject signal to the UE 101 and requests.
the UE l0l to'select the General SGSN 121. In this way, since the UE
101 transmits a re-Attach Request (Attach Request) signal, the General
SGSN 121 is selected and a service is provided from the.General SGSN
r21 .
[0 r 76]
As described above, in the present example, the General SGSN
instructs the UE to perform re-selection of an SGSN. In response to
the instruction, the UE specifies the Customized SGSN and an Attach_
Procedure is continued. In this w&y, the UE can be attached to an
appropriate SGSN.
[0177]
l5
20
25
30
39
t0

As example 9, another example with UMTS will be described. In this
example, the UE transmits an Attach Request and the UE is connected to
the Customized SGSN. In example 6, the same system configuration as
that in example 6 will be used. Fig. 1,4 is a sequence diagram
illustrating an operation according to example g. Hereinafter, the
operation will be described with reference to Figs.2 and 14.
[0178]
To transmit an Attach Request to an SGSN, first, the UE 101
establishes RRC Connection with the RNC 171,. To establish RRC
Connection, first, the UE 101 transmits an RRC Connection Request
signal to the RNC 17I.
[0 r 7e]
In, this signal, the UE l0l sets a par.ameter indicati,ng that the UE
101 needs to be connected to the Customized SGSN 122 (a User Identity,
a new Value or a new parameter of establishment Cause (a value or a
parameter newly introduced in the present example), or an identifier of
a part of such parameters (a PLMN-id included in the IMSI, for
examp I e )).
[0180]
When receiving the RRC Connection Request signal, the RNC 171
stores information indicating that the UE 101 needs to be connected to
the Customized SGSN 122 and continues the subsequent RRC
Connection Procedure.
[0181]
After establishing RRC Connection, the UE 101 transmits an
Attach Request (1) and the NodeB 111 receives the Attach Request (1).
Next, the NodeB 111 forwards the Attach Request to the RNC t7l.
[0182]
The RNC 171 forwards the Attach Request to an SGSN. From
the information stored when the RNC l7l has received the RRC
Connection Request signal, the RNC 171 forwards the Attach Request
signal to the Customized S GSN 122:
[0183]
t5
20
25
30
40
10
After receiving the Attach Request signal, the Customized SGSN
122 continues a normal Attach Procedure
[0 r 84]
In addition, the UE 101 is equipped with a function of instructing
the RNC 17 | about which one of the General SGSN 12l and ,the
Custo mized SGSN 722 needs to be connected to the UE 101. The UE
101 cannot store information about all the SGSNs in the core network,
information indicating an SGSN type, a service type, or the like is used
for the instruction given to the RNC 17L, instead of an identifier by
which a unique SGSN can be selected
[018s]
The RNC 17..1 is equipped with a function of determining which
SGSN needs to be connected to the UE 101. For this determination, as
described above, one of'or a combination of a User Identity, a new value
or a new parameter of Establishment Cause (a value or a parameter
newly introduced in the present example), and an identifier of a part of
such parameters is used.
[0186]
As described above, in the present example, the UE 101 instructs
the RNC 17l to select an SGSN. In response to the instruction, the
RNC 171 specifies the Customized SGSN and an Attach Procedure is
continued. In this way, the UE 101 can be attached to an appropriate
SGSN.
t0l87l

As example 10, another example with UMTS will be described. In this
example, the UE and the Customized SGSN are connected when RA
Update is performed. In example 10, the same system configuration as
that in example 6 will be used. Figs. 15 and l6 are sequence diagrams
illustrating an operation according to example 10. Hereinafter, the
operation will be described with reference to Figs. 2, 15, 1'6, and a part
of Fig. 10.
[0188]
When the UE 101 transmits an Attach Request (see 1 in Fig. 10),
15
2.0
25
30
41
l0
first, the NodeB 1l I receives the Attach Request. The NodeB 111
forwards the Attach Request to the RNC 171, and the RNC 171 forwards
the Attach Request to an SGSN. The RNC l7'L cannot uniquely
determine whether to forward the Attach Request to the General SGSN
l2l or to the Customized SGSN (12). Thus, there are cases where the
RNC l7l forwards the Attach Request to the General SGSN 121.
[01 8 e]
After receiving the Attach Request, the General SGSN l2l
acquires terminal information via an Identity Request/Response (see 3,
5 in Fig. 10). In addition, the General SGSN l2l performs
authentication and acquires a subscriber pro'file in coordination with
the HLR 131.
[01e0]
The General SGSN 121, on acquisition of the terminal
information and the subscriber profile, determines whether to connect
the UE 101 to the General SGSN 121 or to the Customized SGSN 122.
In the case wherein the UE 101 needs to be connected to the General
SGSN 121, the General SGSN 121 continues a normal Attadh Procedure.
[01e 1]
In the case wherein the UE l0l needs to be connected to the
Customized SGSN 122, the General SGSN l2l performs Iu Release to
cause the UE 101 to perform RA (Routing Area) update, as illustrated in
Fig. 15.
[01e2]
The General SGSN l2l transmits an Iu Release Command signal
(4 in Fig. 15) to the RNC 17l. The General SGSN l2l gives an
instruction about an SGSN to be selected by the RNC when establishing
Iu Connection with an SGSN next time, by using an SGSN identifier (for
example, an RAI or an NRI) in the Iu Release Command signal. In the
case of a single pool, the NRI may be used.
[01e3]
Even after Iu Release is completed, while the RNC l7l is holding
session information for the UE l0l, the RNC L7l continues to hold the
SGSN identifier as information for selection of the next SGSN.
l5
20
25
30
42
10
[01e4]
After Iu Release is performed (after the RNC 17 |
Release Complete (6) to the General SGSN l2l), next, as
Fig. l6,.the UE 101 transmits an RAU request (RA Updatg
[01es]
transmits IU
illustrated in
Request) (2).
First, the NodeB i11 receives the RAU Request (2), and the
NodeB lll forwards the RAU Request (3) to the RNC 171.
[01e6]
Next, the RNC 171 forwards the RAU request to an SGSN. Since
Iu Release (c) has already been performed, the RNC l7 | performs
selection of an SGSN and establishes Iu Connection.
[01e7]
In selection of an SGSN, the RNC 171 selects the Customized
SGSN 122 in accordance with the SGSN Identifier specified in the Iu
Release Command, signal received from the General SGSN l2l. The
RNC selects the Customized SGSN in accordance with the RAI (or the
NRI) instructed by the old SGSN (= the General SGSN) when Iu Release
is performed. The RNC is equipped with a function of holding the next
RAI per UE.
[01e8]
After receiving the RAU request, the Customized SGSN 1,22
continues a normal RA Update Procedure. Since the P-TMSI (RAI) on
the NAS indicates the General SGSN, which is the old SGSN, the
Customized SGSN 122 acquires context.
[0 r ee]
The General SGSN 121 and the Custo mized. SGSN 122 are
equipped with a function of determining which SGSN needs to be
connected to the UE 101. This function is the same as that in example
6.
[0200]
In the present example, in the same means as described above,
when the RNC 17 receives an RA Update Request from the UE 101 that
needs to be connected to the General SGSN l2l (for exa'mple, from a
normal mobile station (a normal mobile station that is not compatible
15
20
25
30
43
l0
with a special service such as MTC or MBMS)), by selecting the General
SGSN 121, the UE 101 is connected to the General SGSN 121 and a
service i.s provided from the General SGSN 121.
[0201]
In addition, in the present example, the RA Update Procedure has
been performed based on the sequence in Fig. 16. However, a feature
in the present example is that the RNC 171 selects an SGSN. Thus, the
present example can also be realized by, for example, other procedures
for re-establishing Iu Connection, such as PDP Context Activation.
10202)
As described above, according to the present example, the
General SGSN instructs the RNC to perform re-selection of an SGSN.
In response to the.instruction, the RNC specifies the Customized SGSN
in the next selection of an SGSN, and the other procedure is continued.
In this way, the UE can be connected to an appropriate SGSN
[0203 ]
Hereinafter, differences among the above'examples will be
described.
10204)

Examples 1-5 are, for example, based on LTE (Long Term Evolution)
(the radio access network is E-UTRAN (Evolved-Universal Terrestrial
Radio Access Network) and the core network is EPC). Examples 6-10
are, for example, based on 3G (3rd Generation) (the radio access
network is UTRAN (Universal Terrestrial Radio Access Network) and
the core network is GPSR).
[020s]

A) Examples 1 and 6: attach procedure (retry in the
Network))
[0206]
RAN (Radio Access
15
20
25
30
B) Examples 2 and 7: attach
network (CN))
[0207]
procedure (interworking''in the core
44
C) Examples 3 and 7: retry by the terminal
[0208]
D) Examples 4 and 8: selection in the core network (CN)
[02 0e]
5 E) Examples 5 and l0: update of the location management area
(RAU/TAU)
[0210]

l0 A) Examples I and 6: the RAN (radio access network) and the CN (core
network)
[02 ] 1]
B) Examples 2 and 7: the CN (RAN)
102121
l5 C) Examples 3 and 8: the terminal and the CN
[0213]
D) Examples 4 and 9: the terminal and the RAN
102141
E) Examples 5 and l0: the RAN and the CN
20 [021s]

A) Examples I and 6: while no functions 'need to be added to the
terminal, functions need to be added to the RAN.
[02161
25 B) Examples 2 and 7: no functions need to be added to the terminal, and
in some cases, no functions need to be added to the RAN. In addition,
among the examples, the least signal amount is required.
102171
C) Examples 3 and 8: no functions need to be added to fhe RAN, and
30 functions can easily be added to the terminal and the CN. However,
Attach Reject requires time.
[0218]
D) Examples 4 and 9: while no functions need to be added to the CN,
more functions need to be added to the RAN than the other examples.
45
10
In addition, the RAN needs to store and manage a CN list for selecting a
CN. Before accessing the HLR/HSS, information used for selecting a
CN is limited.
[02 r e]
E) Examples 5 and 10: no functions need to be added to the terminal.
Re-selection of a CN is possible after Attach by change of a contract or
the like.
10220)

Hereinafter, several cases where a core network node is selected based
on the above exemplary embodiments and examples.will be described.
102211
An MTC (Machine Type Communication) device (an M2M device)
is connected to a customized CN node (a node optimized for MTC
devices).
[0222)
A user using MBMS is connected to a customized CN node (an
MBMS-compatible CN node).
102231
In another case, a service is provided only by a customized CN
node so that a new service is started in a small scale.
[0224]

A specific UE is connected to a node in which an MME and an SGW are
collocated. While not particularly limited,.for example, there are
cases where a small amount of data traffic is transmitte.d ts a UE via an
SMS (Short Message Service). In such cases, if an MME and an SGW
are collocated, implementation of SMS conversion processing can be
achieved more easily.
[022s]
In addition, MMEs are switched, depending on a terminal type
(CSFB (CS Fallback) terminal and a VoLTE terminal, for example).
CSFB (CS Fallback) is a function of switching radio to 3G (or 2G) when
a CS (Circuit Switched) service is transmitted or received during LTE
l5
20
25
30
46
l0
connection. VoLTE (Voice over LTE) is a function of providing a voice
(which have been provided via CS) service on LTE. The CSFB terminal
needs to interwork with an MSC. The VoLTE terminal needs to
interwork with bn IMS (IP Multimedia Subsystem). When CSFB is
performed, dn MSC (Mobile Switching Center) that is in advance
attached is caused'to select a collocated MME.
lo226l
The disclosure of the above Patent Literature incorporated herein
by reference thereto. Modifications and adjustmenJs of the exemplary
embodiments and examples are possible within the scope of the overall
disclosure (including the claims) of the present invention and based on
the basic technical concept of the present invention. Various
combinations and selections of various disclosed elements (including
the elements in each of the claims, examples, drawings, etc.) are
possible within the scope of the claims of the present invention. That
is, the present invention of course includes various variations and
modifications that could be made by those skil,led in the art according to
the overall disclosure including the claims and the te'chnical concept.
At least part of the above-disclosed exemplary embodiments and
examples can be described as the following Supplementary Notes,
though not limited thereto.
(Supplementary Note 1)
A communication system including a core network for a mobile
communication system, wherein the core network comprisqs a plurality
of nodes, each node serving as a node to manage mobility of a terminal,
the plurality of nodes being different to each other;.with regard to
service functions that the nodes provide to a terminal, and
wherein based on subscriber information and terminal
information, a node to be connected to the terminal is selected from
among the plurality of nodes, depending on a service characteristic
utilized by the terminal or on a type of the terminal, and the terminal is
connected to the selected node.
(Supplementary Note 2)
The communication system according to Supplementary Note 1,
15
20
25
47
30
10
wherein a first mobility rnanagement entity node, uPon reception of an
Attach Request from the terminal via a base station apparatut, ttunsmits
a mobility management entity re-selection request signal to the base
station apparatus, in order to connect the terminal to a second mobility
management entity node that provides a service different from a service
provided by the first mobility management entity node, and
wherein the base station apparatus transm its an Attach Request to
the second mobility management entity node to connect th,e terminal to
the second mobility management entity node.
(Supplementary Note 3 )
The communication system according to Supplementary Note 1,
wherein a first mobility management entity node, upon reception of an
Attach Request from the terminal via a base station apparatus, transmits
a mobility management entity change request signal to a second
mobility management entity node that provides a service different from
a service provided by the first mobility management entity node, in
order to connect the terminal to the second mobility management entity
node, and
wherein the second mobility management entity node continues
an Attach procedure for the Attach Request to connect the terminal to
the second mobility management entity node.
(Supplementary Note 4)
The communication system according to Supplementary Note 1,
wherein a first mobility management entity node, upon reception of an
Attach Request from the terminal via a base station apparatus, transmits
an Attach Reject, to which an identifier of a Second mobility
management entity node that provides a service different from a service
provided by the first mobility management entity node is added, tci the
terminal, in order to connect the terminal to the second mobility
management entitY node, and
wherein the terminal adds the identifier of the second mobility
management entity node to an Attach Request and re-transmit the Attach
Request to connect to the second mobility management entity node.
(Supplementary Note 5)
15
20
25
48
30
The communication system according to Supplementary Note 1,
wherein the terminal transmits an RRC Connection Request, to which is
added connection request information requesting connection to a second
mobility management entity node that provides a service different from
5 a service provided by a first mobility management entity node, to a base
station apparatus, and
wherein at a time when the base station apparatus, upon reception
of the RRC Connection Request, transmits an Attach Request received
from the terminal with RRC connection to a mobility management entity
10 being established, the base station apparatus selects the second mobility
management entity node to connect the terminal to the second mobility
management entity node.
(Supplementary Note 6)
The communication system according to Supplementary Note 1,
15 wherein, when a first mobility management entity node with a session
with the terminal being established releases connection established
between the base station apparatus and the first mobility management
entity node, the first mobility management entity node instructs the
base station apparatus to select a second mobility management entity
20 node that provides a service different from a service provided by the
first mobility m.anagement entity node in next selection of a mobility
management entity by the base station apparatus, and
wherein upon transmission of a location management area update
request by the ter'minal to the base station Apparatus, the base station
25 apparatus selects the second mobility management entity node to
connect the terminal to the second mobility management entity node.
(Supplementary Note 7)
The communication system according to Supplementary Note l,
wherein a first serving GPRS (General Packet Radio Service) support
30 node, upon reception of an Attach Request from the terminal via a radio
network controller, transmits a serving GPRS support node re-selection
request signal to the radio network controller, in order to connect the
terminal to a second serving GPRS support node that provides a service
different from a service provided by the first serving GPRS support
49
t0
I"I.I
node, an'd
wherein the radio network controller re-transmits an Attach
Request to the second serving GPRS support node to connect the
terminal to the second serving GPRS support node.
(Supplementary Note 8)
The communication system according to Supplementary Note 1,
wherein a first serving GPRS (General Packet Radio Service) support
node (SGSN), upon reception of an Attach Request from the terminal via
a radio network controller, transmits a serving GPRS support node
change request signal to a second serving GPRS support node that
provides a service.different from a service provided by the first serving
GPRS support node, in order to connect the terminal to the second
serving GPRS support node, and
wherein the second serving GPRS support.node continues an
Attach procedure for the Attach Request to connect the terminal to the
second serving GPRS support node.
(Supplementary Note 9)
The communication system according to Supplementary Note 1,
wherein a first serving GPRS (General Packet Radio Service) support
node (SGSN), upon reception of an Attach Request from the terminal via
a radio network controller, transmits an Attach Reject, to which is
added an identifier of a second serving GPRS gupport node that provides
a service different from a service provided by the first derving GPRS
support node is added, to the terminal to connect the terminal to the
second serving GPRS support node, and
wherein the terminal adds the identifier of the- second serving
GPRS support node to an Attach Request and re-transmits the Attach
Request to connect to the second serving GPRS support node.
(Supplementary Note 10)
The communication system according to Suppl.*.ntury Note l,
wherein the terminal transmits an RRC (Radio Resource Control)
Connection Request, to which is added connection request information
requesting connection to a second serving GPRS support node that
provides a service different from a service provided by a first serving
l5
20
25
30
50
10
GPRS (General Packet Radio Service) support node, to a radio network
controller, and
wherein at a time when the radio network controller, upon
reception of the RRC connection Request, transmits an Attach Request
from the terminal with RRC connection to a serving GPRS support node
being established, the radio network controller selects the second
serving GPRS support node to connect the terminal to the second
serving GPRS support node.
(Supplementary Note I 1)
The communication system according to Supplementary Note 1,
wherein, when a first serving GPRS (General Packet Radio Service)
support node with a session with the terminal being established releases
connection established between the first serving GPRS (General Packet
Radio Service) support node and the radio network controller, the first
serving GPRS support node instructs the radio network controller to
select a second serving GPRS support node that provides a service
different from a service provided by the first serving G'PRS support
node in next selection of a serving GPRS support node by the radio
network controller, and
wherein upon transmission of a location management area update
request by the terminal to the radio network controller, the radio
network controller selects the second serving GPRS support node to
connect the terminal to the second serving GPRS support node.
(Supplementary Note l2)
. A communication method, comprising:
arranging a plurality of nodes for the termirial in a mobile
communication system core network, the nodes serving as nodes for
managing mobility of a terminal, and being different to each other with
regard to service functions that the nodes provide to a terminal;
selecting, based on subscriber information and terminal
information, a node to be connected to the terminal from among the
plurality of nodes, depending on characteristics of a service used by the
terminal .or on a type of the terminal; and
connecting the terminal to the selected node.
l5
20
25
30
51
l0
(Supplementary Note 1 3)
The communication method according to Supplementary Note 12,
comprising:
a first mobility management entity node, upon reception of an
Attach Request from the terminal via a base statio'n apparatus,
transmitting a mobility management entity re-selection request signal to
the base station apparatus, in order to connect the terminal to a second
mobility management entity node that provides a service different from
a service provided by the first mobility management entity node; and
the base station apparatus transmitting an Attach Request to the
second mobility management entity node to connect the terminal to the
second mobility management entity node.
(Supplementary Note 14)
The communigation method according to Supplementary Note 12,
comprising:
a first mobility management entity node, upon receplion of an
Attach Request from the terminal via a base station apparatus,
transmitting a mobility management entity, change request signal to a
second mobility management entity node that provides a service
different from a service provided by the first mobility management
entity node, in order to connect the terminal to the second mobility
management entity node; and
the second mobility management entity node continuin.g a
procedure for the Attach Request to connect the terminal to the sec.ond
mobility management entity node.
(Supplementary Note 15) I
The communication method according to Supplementary Note 12,
comprising:
a first mo.bility management entity node, upon reception of an
30 Attach Request from the terminal via a base station apparatus,
transmitting an Attach Reject, to which is added an identifier of a
second mobility manqgement entity node that provides a service
different from a service provided by the first mobility management
entity node, to the terminal, in order to connect the terminal to the
l5
20
25
52
10
second mobility management entity node; and
the terminal adding the identifier of the second mobility
management entity node to an Attach Request and re-transmitting the
Attach Request to connect to the second mobility management entity
node.
(Supplementary Note 16)
The communication method according to Supplementary Note 12,
comprising:
th,e terminal transmitting an RRC (Radio Resource Control)
Connection Request, to which is added connection request information
requesting connection to a second mobility management entity node that
provides a service different from a service provided by a first mobility
management entity node, to a base station apparatus; and
the base station apparatus selecting the second mobility
management entity node, at a time when the base station apparatus,
upon reception of the RRC Connection Request, transmits an Attach
Request from lhe terminal with RRC connection to a mobility
management entity being established, to connect the terminal to the
second mobility m.anagement entity node
(Supplementary Note 17)
The communicati'on method according to Supplementary Note 12,'
comprising:
when a first mobility management entity node with a session with
the terminal being established releases connection established between
the base station apparatus and the first mobility management entity
node, the first mobility management entity node instiucting the base
station apparatus to select a second mobility management entity node
that provides a service different from a service provided by the first
mobility management entity node in next selection of a mobility
management entity by the base station apparatus; and
upon transmission of a location management are.a upddte request
by the terminal to the base station apparatus, the base station apparatus
selecting the second mobility management entity node to connect the
terminal to the second mobility management entity node.
l5
20
25
30
53
10
(Supplementary Note 18)
The communication method according to Supplementary Note 12,
comprising:
a first serving GPRS (General Packet Radio Service) support node
(SGSN), upon reception of an Attach Request from the terminal via a
radio network controller, transmitting a serving GPRS support node
re-selection request signal to the radio network controller, in order to
connect the terminal to a second serving GPRS support node that
provides a service different from a service provided by the first serving'
GPRS support node; and
the radio network controller transmitting an Attach Request to
the second serv.ing GPRS support node to connect the terminal to the
second serving GPRS support node.
(Supplementary Note l9)
The communication method according to Supplementary Note 12,
comprising:
a first serving GPRS (General Packet Radio Service) support node
(SGSN), upon reception of an Attach Request from the terminal via a
radio network controller, transmitting a serving GPRS sufport node
change request signal to a second serving GPRS support node that
provides a service different from a service provided by the first serving
GPRS support node, in order to connect the terminal to the second
serving GPRS support node; and
the second serving GPRS support node continuing an Attach
procedure to connect the terminal to the second serving GPRS support
node
(Supplementary Note 20)
The communication method according to Supplementary Note 12,
comprising:
a first serving GPRS (General Packet Radio Service) support node
(SGSN), upon reception of an Attach Request from the terminal via a
radio network controller, transmitting an Attach Reject, to which is
added an identifier of a second serving GPRS support node that provides
a service different from a service provided by the first serving GPRS
15
20
25
30
54
10
support node, to the terminal. in order to connect the terminal to the
second serving GPRS support node; and
the terminal adding the identifier of the second serving GPRS
support node to an Attach Request and re-transmitting the Attach
Rbquest to connect to the second serving GPRS support node.
(Supplementary Note 2l)
The communication method according to Supplementary Note 12,
comprising:
the terminal transmitting an RRC (Radio Resource Control)
ConnEction Request, to which is added connection request information
requesting connection to a second serving GPRS support node that
provides a service different from a service provided by a first serving
GPRS support node, to a radio network controller; and
,r
at a time when the radio network controller, upon reception of the
RRC Connection Request, transmits an Attach Request from the
terminal with RRC connection to a serving GPRS support node (SGSN)
being established, the radio network controller selecting the second
serving GPRS support node to connect the terminal to the second
serving GPRS support node.
(Supplementary Note 22)
The communication method according to Supplementary Note 12,
comprising:
when a first serving GPRS (General Packet Radio Service)
support node with a session with the terminal being established releases
connection established between the first serving GPRS (General Packet
Radio Service) support node and the radio network coritroller, the first
serving GPRS.support node instructing the radio network controller to
select a second serving GPRS support node that provides a service
different from a service provided by the first serving GPRS support
node, in'next selection of a serving GPRS support node by the radio
network controller; and
upon transmission of a Routing Area Update Request by the
terminal to the radio network controller, the radio network controller
selecting the second serving GPRS support node to connect the terminal
l5
20
25
30
55
10
l5
to the second serving GPRS support node.
(Supplementary Note 23)
A node apparatus that performs control to select, as a mobility
management node apparatus to manage mobility of a terminal, another
mobility management node apparatus compatible with a service
characteristic utilized by the terminal or a type of the terminal, based
on subscriber information and terminal information to connect the
terminal to the selected another mobility management node apparatus.
(Supplementary Note 24)
The node apparatus according to Supplementary Note 23, wherein
the node apparatus is a node apparatus on a radio access network or a
core network in a mobile communication system.
(Supplementary Note 25)
A communication system, comprising:
a general MME (Mobility Management Entity) or a general SGSN
(Serving GPRS Support Node) for a general terminal other than a
predetermined specific terminal, as a core network node managing
mobility'of a terminal; and
a customized MME or a customized SGSN that includes a function
to provide a predetermined specific service to the specific terminal or
that is customized to be compatible with the specific terminal of a
predetermined type,
wherein the general MME, the general SGSN, or the specific
terminal selects the customized MME or the customized SGSN as a node
to which the specific terminal is connected.
REFERENCE SIGNS LIST
10227)
20
25
I
1t
21
22
3l
41
51
UE
eNodeB
General MME
Custo mized MME
HSS
S -GW (Serving GW)
P-GW (PDN GW)
56
30
6l service network
101 uE (MS)
l l l NodeB
121 General SGSN
5 122 CustomizedSGSN
131 HLR
I4I GGSN
161 service network
17I RNC

We Claim:
1. A mobile communication system, wherein
a terminal (UE) includes means configured to transmit a
TAU(Tracking Area Update) Request to a base station (eNodeB);
the base station includes means configured to forward the
TAU Request to an MME (Mobility Management Entity);
the MME includes means configured to transmit to the base
station a request signal including an identifier corresponding to
a dedicated MME that is dedicated to serve a specific terminal based
on subscriber information obtained from an HSS (Home Subscriber
Server);
the base station includes means configured to re-select the
dedicated MME based on the identifier; and
the base station further includes means configured to
transmit a NAS (Non-Access Stratum) message to the dedicated MME
re-selected.
2. A mobile communication system, wherein
a terminal (UE) includes means configured to transmit an RAU
(Routing Area Update) Request to an SGSN (Serving GPRS(General
Packet Radio Service) Support Node);
the SGSN includes means configured to transmit to an RNC
(Radio Network Controller) a request signal including an identifier
corresponding to a dedicated SGSN that is dedicated to serve a
specific terminal based on subscriber information obtained from an
HLR (Home Location Register);
the RNC includes means configured to re-select the dedicated
SGSN based on the identifier; and
the RNC further includes means configured to transmit a NAS
(Non-Access Stratum) message to the dedicated SGSN re-selected.
3. A communication method in a mobile communication system, the
method comprising:
transmitting, by a terminal (UE), a TAU (Tracking Area
Update) Request to a base station (eNodeB);
forwarding, by the base station, the TAU Request to an MME
(Mobility Management Entity);
transmitting, by the MME, to the base station a request
signal including an identifier corresponding to a dedicated MME that
60
is dedicated to serve a specific terminal based on subscriber
information obtained from an HSS (Home Subscriber Server);
re-selecting, by the base station, the dedicated MME based
on the identifier; and
transmitting, by the base station, a NAS (Non-Access
Stratum) message to the dedicated MME re-selected.
4. A communication method in a mobile communication system, the
method comprising:
transmitting, by a terminal (UE), an RAU (Routing Area
Update) Request to an SGSN (Serving GPRS(General Packet Radio
Service) Support Node);
transmitting, by the SGSN, to an RNC (Radio Network
Controller) a request signal including an identifier corresponding
to a dedicated SGSN that is dedicated to serve a specific terminal
based on subscriber information obtained from an HLR (Home Location
Register);
re-selecting, by the RNC, the dedicated SGSN based on the
identifier; and
transmitting, by the RNC, a NAS (Non-Access Stratum) message
to the dedicated SGSN re-selected.
5. A terminal (UE) for a mobile communication system, the terminal
comprising:
means configured to transmit a TAU (Tracking Area Update)
Request including information on the terminal to a base station
(eNodeB), wherein
the base station forwards the TAU Request to an MME (Mobility
Management Entity), the MME transmits to the base station a request
signal including an identifier corresponding to a dedicated MME that
is dedicated to serve a specific terminal based on subscriber
information obtained from an HSS (Home Subscriber Server), and
the base station re-selects the dedicated MME based on the
identifier, thereby the specific terminal connecting to the
dedicated MME re-selected.
6. A terminal (UE) for a mobile communication system, the terminal
comprising:
61
means configured to transmit an RAU (Routing Area Update)
Request including information on the terminal to an SGSN (Serving
GPRS(General Packet Radio Service) Support Node), wherein
the SGSN transmits to an RNC (Radio Network Controller) a
request signal including an identifier corresponding to a dedicated
SGSN that is dedicated to serve a specific terminal based on
subscriber information obtained from an HLR (Home Location
Register), and the RNC re-selects the dedicated SGSN based on the
identifier, thereby the specific terminal connecting to the
dedicated SGSN re-selected.
7. A communication method of a terminal (UE) for a mobile
communication system, the method comprising:
transmitting a TAU (Tracking Area Update) Request including
information on the terminal to a base station (eNodeB), wherein
the base station forwards the TAU Request to an MME (Mobility
Management Entity), the MME transmits to the base station a request
signal including an identifier corresponding to a dedicated MME that
is dedicated to serve a specific terminal based on subscriber
information obtained from an HSS (Home Subscriber Server), and the
base station re-selects the dedicated MME based on the identifier,
thereby the specific terminal connecting to the dedicated MME
re-selected.
8. A communication method of a terminal (UE) for a mobile
communication system, the method comprising:
transmitting an RAU (Routing Area Update) Request including
information on the terminal to an SGSN (Serving GPRS(General Packet
Radio Service) Support Node), wherein
the SGSN transmits to an RNC (Radio Network Controller) a
request signal including an identifier corresponding to a dedicated
SGSN that is dedicated to serve a specific terminal based on
subscriber information obtained from an HLR (Home Location Register), and the RNC re-selects the dedicated SGSN based on the identifier, thereby the specific terminal connecting to the dedicated SGSN re-selected.