Communication system, method and apparatus

(Description of related application) The present invention is based on the priority claim of Japanese Patent Application No. 2011-217384 (filed on September 30, 2011), and the entire contents of the application are incorporated in this document by citation. It shall be.

The present invention relates to communication systems, methods and devices.

In the core network of a mobile communication system, in order to provide various services to various terminals (mobile devices), it is necessary for all the nodes in the core network to have the functions required for each service. .. In a large-scale mobile communication network or the like, many nodes are deployed in the core network. The terminals are distributed and connected to the nodes in the core network for each location registration.

Therefore, all the nodes in the core network need to have the necessary functions (service providing functions) for each service. If some of the nodes in the core network do not have the service providing function, the service continuity cannot be guaranteed to the terminal.

As a configuration for optimizing the packet transfer route according to the type of service used by the mobile station, for example, in Patent Document 1, when the mobile station uses the service from the external network, it is specified according to the external network. When the packet transfer path is restricted so as to pass through the packet transfer device and the mobile station uses the service provided by the mobile communication network, a configuration is disclosed in which the packet transfer path is not restricted.

<p num="0006"><patcit num="1"><text>JP-A-2003-338832</text></patcit></p>

<p num="0007"> An analysis of related technologies is given below.</p><p num="0008"> As described above, since each node in the core network has all the service providing functions, high functionality and high performance are required. As a result, each core network node is expensive.</p><p num="0009"> For example, the MBMS (Multimedia Broadcast Multicast Service) service (simultaneous distribution service), which is a bearer service that is standardized by 3GPP (3rd Generation Partnership Project) and realizes broadcast distribution, has mobile devices that support it. Since it is relatively few, there are few opportunities to provide services. However, when trying to provide a service to a small number of MBMS users, the telecommunications carrier will provide the service to that number of MBMS users unless all the nodes in the core network have the MBMS function. You can't.</p><p num="0010"> If the core network nodes can be selected according to the necessity of using the MBMS service of the mobile device, the carrier can use a relatively small number of expensive MBMS-compatible core network nodes and a large number of inexpensive MBMS non-nodes. By deploying a combination of compatible core network nodes, the overall equipment cost can be made more efficient (the first finding of the present inventors).</p><p num="0011"> In addition, the machine communication (MTC: Machine Type Communication) device (M2M device) in 3GPP, which has become popular in recent years, has mobile characteristics different from those of ordinary terminals (handset terminals) such as mobile phone terminals and smartphones used for telephone calls. And the required communication quality are very different. Here, it is known that there are a wide variety of machine communication services, such as remote management of vending machine inventory and billing, remote monitoring control such as sensor system, vehicle monitoring, smart grid, and the like.</p><p num="0012"> Among core network nodes, for example, an MTC-compatible node has a configuration suitable for accommodating a terminal (MTC device) having a large number of control signals and a small amount of user data (for example, a user plane for exchanging user data). The performance of the control signal system is suppressed to reduce the cost, and the control plane of the control signal system is improved accordingly). Therefore, as a telecommunications carrier, if all core network nodes do not have the ability / function to connect both the MTC device and the handset terminal without any problem, the service will be provided to both the MTC device and the handset terminal. Cannot be provided. The same is true for MBMS services.</p><p num="0013"> If the MTC device and the handset terminal can be connected to the appropriate core network node, the carrier can combine the relatively inexpensive core network node for the handset terminal with the relatively inexpensive core network node for the MTC device. Can be deployed (second finding of the present inventors).</p><p num="0014"> In this case, the equipment cost of the entire system can be made more efficient than deploying a relatively expensive core network node that can handle both the handset terminal and the MTC device with one node (the present invention). Third finding of those).</p><p num="0015"> Therefore, the present invention has been devised to solve the above problems, and an object of the present invention is to provide a system, a method, and an apparatus for improving the efficiency of the equipment cost of the entire system and reducing the cost. ..</p>

<p num="0016"> The present invention that solves the above problems has the following configurations (but not limited to the following).</p><p num="0017"> According to one aspect of the invention, a mobile communication system in which a terminal (UE) transmits an Attach Request to a base station (eNodeB). A means by which the base station transfers the Attach Request to the MME (Mobility Management Entity), and The MME is a means for transmitting a request signal including an identifier corresponding to a dedicated MME that specializes in a specific terminal to the base station based on subscriber information from HSS (Home Subscriber Server). The base station has a means for reselecting the dedicated MME based on the identifier, and The base station is provided with a mobile communication system having means for transmitting a NAS (Non-Access Stratum) message to the reselected dedicated MME. Further, according to the present invention, in a mobile communication system, a means by which a terminal (UE) transmits an Attach Request to an SGSN (Serving GPRS (General Packet Radio Service) Support Node) is provided. The SGSN is HLR (Home A means to send a request signal including an identifier corresponding to a dedicated SGSN that specializes in a specific terminal to the RNC (Radio Network Controller) based on the subscriber information from the Location Register). The RNC is a means for reselecting the dedicated SGSN based on the identifier, and The RNC provides a mobile communication system having means for transmitting NAS (Non-Access Stratum) messages to the reselected dedicated SGSN.</p><p num="0018"> According to another aspect of the present invention, it is a communication method of a mobile communication system. The terminal (UE) sends an Attach Request to the base station (eNodeB) and The base station transfers the Attach Request to the MME (Mobility Management Entity), Based on the subscriber information from HSS (Home Subscriber Server), the MME transmits a request signal including an identifier corresponding to a dedicated MME that specializes in a specific terminal to the base station. The base station reselects the dedicated MME based on the identifier and The base station provides a communication method for a mobile communication system that transmits a NAS (Non-Access Stratum) message to the reselected dedicated MME. Further, according to the present invention, it is a communication method of a mobile communication system. The terminal (UE) sends an Attach Request to SGSN (Serving GPRS (General Packet Radio Service) Support Node) and The SGSN is HLR (Home Based on the subscriber information from the Location Register), a request signal including an identifier corresponding to a dedicated SGSN that specializes in a specific terminal is sent to the RNC (Radio Network Controller). The RNC reselects the dedicated SGSN based on the identifier and The RNC provides a communication method for a mobile communication system that transmits a NAS (Non-Access Stratum) message to the reselected dedicated SGSN. According to the present invention, it is a communication method of a terminal (UE) used in a mobile communication system. An Attach Request containing information about the terminal is sent to the base station (eNodeB). The base station transfers the Attach Request to an MME (Mobility Management Entity), and the MME is an HSS (Home Subscriber). A request signal including an identifier corresponding to a dedicated MME that specializes in a specific terminal is transmitted to the base station based on the subscriber information from the server), and the base station reselects the dedicated MME based on the identifier. By doing so, a communication method of a terminal in which the specific terminal connects to the reselected dedicated MME is provided. According to the present invention, it is a communication method of a terminal (UE) used in a mobile communication system. An Attach Request containing information about the terminal is sent to SGSN (Serving GPRS (General Packet Radio Service) Support Node). The SGSN transmits a request signal including an identifier corresponding to a dedicated SGSN that specializes in handling a specific terminal to the RNC (Radio Network Controller) based on the subscriber information from the HLR (Home Location Register), and the RNC transmits the identifier. By reselecting the dedicated SGSN based on the above, a communication method of a terminal in which the specific terminal connects to the reselected dedicated SGSN is provided.</p><p num="0019"> According to another aspect of the present invention, a terminal (UE) used in a mobile communication system. A means for transmitting an Attach Request containing information about the terminal to a base station (eNodeB) is provided. The base station transfers the Attach Request to an MME (Mobility Management Entity), and the MME includes an identifier corresponding to a dedicated MME that specializes in handling a specific terminal based on subscriber information from the HSS (Home Subscriber Server). A terminal is provided in which the specific terminal connects to the reselected dedicated MME by transmitting a request signal to the base station and the base station reselecting the dedicated MME based on the identifier. .. According to the present invention, it is a terminal (UE) used in a mobile communication system. A means for sending an Attach Request containing information about the terminal to an SGSN (Serving GPRS (General Packet Radio Service) Support Node) is provided. The SGSN is HLR (Home Location) Based on the subscriber information from Register), a request signal including an identifier corresponding to a dedicated SGSN that specializes in a specific terminal is transmitted to the RNC (Radio Network Controller), and the RNC sends the dedicated SGSN based on the identifier. Reselection provides a terminal in which the particular terminal connects to the reselected dedicated SGSN.</p>

<p num="0020"> According to the present invention, it is possible to improve the efficiency of the equipment cost of the entire core network system and reduce the cost.</p>

<figref num="1">It is a figure which shows the system structure of the 1st Embodiment of this invention.</figref><figref num="2">It is a figure which shows the system structure of the 2nd Embodiment of this invention.</figref><figref num="3">It is a figure which shows the sequence example of the 1st Example of this invention.</figref><figref num="4">It is a figure which shows the sequence example of the 2nd Example of this invention.</figref><figref num="5">It is a figure which shows the sequence example of the 3rd Example of this invention.</figref><figref num="6">It is a figure which shows the sequence example of the 3rd Example of this invention.</figref><figref num="7">It is a figure which shows the sequence example of the 4th Example of this invention.</figref><figref num="8">It is a figure which shows the sequence example of the 5th Example of this invention.</figref><figref num="9">It is a figure which shows the sequence example of the 5th Example of this invention.</figref><figref num="10">It is a figure which shows the sequence example of the 6th Example of this invention.</figref><figref num="11">It is a figure which shows the sequence example of the 7th Example of this invention.</figref><figref num="12">It is a figure which shows the sequence example of the 8th Example of this invention.</figref><figref num="13">It is a figure which shows the sequence example of the 8th Example of this invention.</figref><figref num="14">It is a figure which shows the sequence example of the 9th Example of this invention.</figref><figref num="15">It is a figure which shows the sequence example of the tenth embodiment of this invention.</figref><figref num="16">It is a figure which shows the sequence example of the tenth embodiment of this invention.</figref>

First, the outline of the present invention will be described with reference to FIGS. 1 and 2. According to the present invention, the core network includes a plurality of nodes (21/22 in FIG. 1 or 121/122 in FIG. 2) having different service functions provided to terminals, and can be used for subscriber information and terminal information. Based on this, the node to be connected to the terminal is selected from the plurality of nodes according to the service characteristics or the terminal type used by the terminal, and is selected as the terminal (1 in FIG. 1 or 101 in FIG. 2). Connects with the node. That is, in the core network, a node having a predetermined specific service providing function (22 in FIG. 1 or 122 in FIG. 2) and a node not having the specific service providing function (21 in FIG. 1 or 21 in FIG. 2). 121) in Fig. 2 is deployed in combination.

As described above, according to the present invention, by separately installing the nodes connected to the terminals as a node optimized for the specific service providing function and a node not having the specific service providing function itself, all of the core network can be installed. Compared to the case of implementing the capabilities and functions corresponding to all services on the node of, it is possible to reduce the cost of the entire system.

According to the present invention, in a mobile communication network, a terminal can be connected to a specific core network node according to conditions such as service characteristics and terminal type.

&lt;Aspect 1&gt; A general MME (Mobility Management Entity) that receives an Attach Request from a UE (User Equipment: also called a user device, terminal, or mobile device) is based on subscriber information and terminal information. When the UE is a type of UE that uses a specific service, an MME reselection request signal (mobility management) is sent to eNodeB (evolved Node B: base station device) in order to connect the UE to a specific MME (Customized MME). Entity reselection request signal) is sent.

The eNodeB connects the UE to the specific MME by retransmitting the attach request (Attach Request) to the specific MME.

&lt;Aspect 2&gt; A general MME that receives an attach request from a UE receives an MME change request signal (mobility management entity change request signal) for the specific MME in order to connect the UE to a specific MME (Customized MME). To send. The specific MME connects the UE to the specific MME by continuing the attach process (Attach Procedure).

&lt;Aspect 3&gt; A general MME that receives an attach request from a UE transmits an attach reject (Attach Reject) with an identifier of the specific MME to the UE in order to connect the UE to a specific MME (Customized MME). To do. The UE connects the UE to the specific MME by assigning an identifier of the specific MME to the Attach Request and retransmitting the request.

&lt;Aspect 4&gt; The UE sends an RRC connection request (RRC (Radio Resource Control) Connection Request) (radio resource connection request) with specific MME (Customized MME / Specific MME) connection request information to eNodeB, and receives the RRC connection request. The eNodeB connects the UE to the specific MME by selecting the specific MME when transmitting an attach request (Attach Request) from the UE that has established an RRC connection (RRC Connection) to the MME. There is.

&lt;Aspect 5&gt; The general MME that has established a session with the UE is the specified MME (Customized MME) the next time the MME is selected at the time of opening the S1 connection (S1 Release) established between the eNodeB and the general MME. By instructing the eNodeB to select, and then when the UE sends a location management area update request (TA (Tracking Area) Update Request), the eNodeB selects the specific MME. , The UE is connected to a specific MME.

&lt;Aspect 6&gt; The General SGSN (Serving GPRS (General Radio Packet Service) Support Node: referred to as "Serving GPRS Support Node" in the scope of billing) that received the Attach Request from the UE is based on the subscriber information and terminal information. When the UE is a type of UE that uses a specific service, an SGSN reselection request signal is transmitted to the RNC (Radio Network Controller) in order to connect the UE to a specific SGSN (Customized SGSN). The RNC connects the UE to the specific SGSN by resending the Attach Request to the specific SGSN.

&lt;Aspect 7&gt; The general SGSN that received the attach request (Attach Request) from the UE transmits an SGSN change request signal to the specific SGSN in order to connect the UE to the specific SGSN (Customized SGSN), and the specific SGSN is attached. By continuing Procedure), the UE is connected to the specific SGSN.

&lt;Aspect 8&gt; Upon receiving the Attach Request from the UE, the general SGSN transmits an Attach Reject with the identifier of the specific SGSN to the UE in order to connect the UE to the specific SGSN (Customized SGSN). , The UE connects the UE to the specific SGSN by adding a specific SGSN identifier to the Attach Request and retransmitting the request.

&lt;Aspect 9&gt; The UE sends a connection request (RRC Connection Request) to the RNC with specific SGSN (Customized SGSN) connection request information, and the RNC that receives the request attaches from the UE that has established the RRC connection (RRC Connection). By selecting the specific SGSN when transmitting the Request to the SGSN, the UE is connected to the specific SGSN.

&lt;Aspect 10&gt; The general SGSN that has established a session with the UE instructs the RNC to select a specific SGSN (Customized SGSN) in the next SGSN selection at the time of Iu release, and then the UE indicates the location management area. When an update request (RA (Routing Area) Update Request) is sent, the RNC selects a specific SGSN to connect the UE to the specific SGSN.

As described in the above aspects 1 to 10, according to the present invention, the core network nodes to be connected to each terminal are selected and connected according to the service characteristics used by the terminals. By doing so, in the core network, a node having a specific service providing function and a node not having a specific service providing function are deployed in combination, and one of the nodes is optimized for the specific service providing function, and the other nodes are concerned. By making a difference such as not having a specific service provision function, the equipment cost of the entire system is reduced. Hereinafter, some embodiments and specific examples will be described with reference to the drawings.

&lt;Embodiment 1&gt; FIG. 1 is a diagram illustrating embodiment 1 of the present invention. As the first embodiment, a configuration in which a UE and a specific MME (Customized MME) are connected at the time of attachment (Attach) in an EPC (Evolved Packet Core) will be described.

In FIG. 1, the UE 1 (user device) may be a terminal that receives a service from a specific MME (Customized MME), for example, the above-mentioned MTC device, an MBMS compatible terminal, or the like. If the UE1 is a normal mobile terminal that uses a normal service such as a mobile phone terminal or a smartphone (for example, a terminal that does not support a specific service such as MTC or MBMS), it is connected to a general MME. In addition, as will be described later, when a specific MME (Customized MME) is selected in response to an Attach request from a normal mobile terminal (for example, a terminal that does not support a specific service such as MTC or MBMS), the MME is reselected. Is done and reconnected to the general MME.

eNodeB11 is an LTE (Long Term Evolution) base station device.

MME21 and MME22 are devices for managing mobility introduced in EPC. The specific MME (Customized MME) 22 is a specific MME to which the UE1 is to be connected, and the general MME (21) is another MME. Although not particularly limited, the specified MME (Customized MME) 22 is configured as, for example, a machine communication (MTC) service and an MME with a customized configuration (for example, reinforcing C-Plane that handles network control) for compatible terminals (M2M devices). Will be done. Alternatively, it may be configured as an MBMS-compatible MME.

HSS (Home Subscriber Server) 31 is a database that holds subscriber information.

The S-GW (Serving Gate Way) 41 and the P-GW (Packet data network Gate Way) 51 are devices that handle the user plane.

The service network 61 indicates an external network.

In FIG. 1, eNodeB corresponds to a radio access network (RAN), MME, S-GW, P-GW, etc. correspond to a core network (CN: Core Network).

Hereinafter, some examples in which the control methods are different from each other will be described with respect to the above-described first embodiment. Examples 1-5 correspond to the above-mentioned aspects 1-5, respectively.

&lt;Example 1&gt; FIG. 3 is a sequence diagram for explaining an operation example of the first embodiment. In Figure 3, UE is UE1 in Figure 1, eNodeB is eNodeB11 in Figure 1, The general MME is the general MME21 in Fig. 1. Customized MME (specific MME) is Customized MME (specific MME) 22 in Fig. 1. Serving GW is S-GW41 in Fig. 1, PDNGW is shown in P-GW51 in Fig. 1. HSS corresponds to HSS31 in Fig. 1, respectively.

PCRF is a policy and billing rules function. In addition, EIR (Equipment Identity Register) holds IMEI (International Mobile Equipment Identity) and is connected to MME by S13 interface.

In FIG. 3, for example, "1. Attach Request" indicates that the transmission of the attach request (Attach Request) from the UE to the eNodeB is the sequence 1. In the following description, this sequence number 1 is written in parentheses, as in "Attach Request (1)", in order to distinguish it from the reference code 1 (reference code of the component) of the UE in the figure. .. The same applies to other sequence numbers. In addition, the same notation is used for the sequence diagrams after FIG. Note that Figure 3 is based on Figure 5.3.2.1-1: Attach procedure of 3GPP TS23.401, and the sequence numbers follow the figure. For details of each sequence, refer to the description of 3GPP TS23.401 5.3.2. Hereinafter, the operation sequence will be described with reference to FIGS. 1 and 3.

Referring to FIG. 3, when UE1 transmits an attach request (Attach Request) (1), the eNodeB 11 first receives it, and the eNodeB 11 relays the attach request (Attach Request) (2) to the MME.

At this time, the eNodeB 11 cannot uniquely determine whether the Attach Request (2) should be forwarded to the general MME21 or the Customized MME22. Therefore, the Attach Request (2) may be transferred from the eNodeB 11 to the general MME21.

In the general MME21, after receiving the attach request (2), the terminal information (ME Identity) is acquired from the UE1 by the Identity Request / Response (4, 5b).

The general MME21 sends an ME Identity Check Request (5b) to the EIR, and the EIR returns the ME Identity Check Ack (not shown) to the general MME. Furthermore, in cooperation with HSS31, authentication and acquisition of subscriber profile will be performed. That is, the general MME21 is used for authentication and acquisition of the subscriber profile.

The general MME21 that has acquired the terminal information and the subscriber profile determines whether the UE1 should be connected to the general MME21 or the customized MME22.

When connecting to the general MME21, the normal attach procedure (Attach Procedure) is continued.

When the UE1 is connected to the Customized MME22, the general MME21 newly indicates the MME selection signal (MME re-selection command): MME re-selection Command (newly in this embodiment) in order to instruct the eNodeB 11 to reselect the MME. The introduced S1AP (S1 application) signal) is transmitted.

At this time, the general MME21 sets the identifier of the Customized MME22 (for example, GUMMEI (Globally Unique MME Identity)) in the MME re-selection Command signal. That is, a reselection request is sent to eNodeB before bearer generation in the core network, and the information (GUMMEI) required for new MME selection is posted. The MME has a function of determining whether or not the UE is a re-selection target.

When the eNodeB 11 receives the MME re-selection Command signal, it selects the Customized MME22 according to the identifier set in this signal, and transfers the Attach Request (2) to the Customized MME22. Since the specific MME22 requires the NAS (Non-Access Stratum) parameter (used for authentication between the UE and MME) of the Attach Request, it is retransmitted by the eNodeB 11. eNodeB11 needs a function to hold NAS messages.

In the new MME (= Customized MME22), the old MME (= general MME) cannot be specified, so the context (Context) cannot be inherited from the old MME (= general MME). Therefore, in the new MME (= Customized MME: MME22), it is necessary to acquire the authentication / subscriber profile again.

After receiving the Attach Request signal, the Customized MME22 acquires the terminal information by Identity Request / Response, and further cooperates with HSS31 to authenticate and acquire the subscriber profile. .. That is, the same processing as general MME21 is performed.

The Customized MME22 that has acquired the terminal information and the subscriber profile determines whether the UE1 should be connected to the general MME21 or the Customized MME22.

Here, since Customized MME22 has been reselected by eNodeB11, normal attach processing (Attach Procedure) is continued without transmitting the MME re-selection Command signal. That is, -Sending an update location request (8) from Customized MME22 to HSS31, · Sending an update location acknowledgment (11) from HSS31 to Customized MME22, -Sending Create Session Request (12) from Customized MME22 to S-GW41, -Sending Create Session Request (12) from S-GW41 to P-GW51, PCEF Initiated IP-CAN Session Establishment / Modification (14) by P-GW41, -Sending Create Session Response (15) from P-GW51 to S-GW41, -Transmission of First Down Link Data from P-GW51 to S-GW41 (if not Handover (HO)), -Sending Create Session Response (16) from S-GW41 to S-GW41, -Sending Initial Context Setup Request / Attach Accept (17) from General MME22 to eNodeB11, · Sending RRC Connection Reconfiguration (18) from eNodeB 11 to UE1, -Sending RRC Connection Reconfiguration Complete (19) from UE1 to eNodeB11, Customized from eNodeB 11 Sending Initial Context Setup Response (20) to MME22, -Direct Transfer from UE1 to eNodeB (21), -Sending Attach Complete (22) from eNodeB 11 to Customized MME22, -Transmission of the first uplink data (First Uplink Data) from UE1 to S-GW41 and P-GW51, -Sending a Modify Bearer Request (23) from Customized MME22 to S-GW41, -Sending a Modify Bearer Request (23a) from S-GW41 to PCEF, -Transmission of Modify Bearer Response (23b) from PCEF to S-GW41, -Sending Modify Bearer Response (24) from S-GW41 to Customized MME22, -The first downlink data (First Downlink data) is transmitted from P-GW51 and S-GW41 to UE1.

In addition, the general MME21 and the customized MME22 have a function of determining which MME the UE1 should be connected to. Information from UE1, for example IMSI (International Mobile Subscriber Identity), IMEI (International Mobile Equipment Identity: International mobile device identification number (terminal identification number)), UE network capability, MS network capability, Mobile station classmark 2, Mobile station classmark 3, -Device properties or -New parameters for Attach Request signals that will be added in the future, or -Partial identifiers that make up these parameters (PLMN (Public land Mobile Network) -id included in the IMSI, etc.), Information from HSS31, for example Feature-List, APN (Access Point Name) or -New parameters for Update Location Answer / Insert Subscriber Data Request signals that will be added in the future, or -Partial identifiers that make up these parameters, Perform after any or a combination of the above.

Further, in the present embodiment, when the Attach Request signal from UE1 to be connected to the general MME21 is transferred to the Customized MME22, the customized MME22 to the eNodeB 11 are generalized by the same means. It is possible to encourage MME reselection of MME21. For example, if the UE1 is a normal mobile terminal (for example, a normal mobile terminal that does not support special services such as MTC and MBMS), once the UE1 is connected to the Customized MME22, the general MME21 is reselected. And the service from general MME21 is provided.

As described above, in the present embodiment, the MME instructs the eNodeB to reselect the MME, and the eNodeB receives the instruction to reselect the MME and then continues the attach procedure (Attach Procedure). , UE can be attached to the appropriate MME.

&lt;Example 2&gt; As the second embodiment, another example of connecting the UE and the Customized MME at the time of Attach in the EPC (Evolved Packet Core) will be described. The system configuration of the second embodiment is the same as that of the first embodiment.

FIG. 4 is a sequence diagram showing an operation example of the second embodiment. Note that Figure 4 is based on Figure 5.3.2.1-1: Attach procedure of 3GPP TS23.401, and the sequence numbers follow the figure. For details of each sequence, refer to the description of 3GPP TS23.401 5.3.2. The operation will be described below with reference to FIGS. 1 and 4.

When UE1 sends an Attach Request (1), the eNodeB 11 receives it and relays the Attach Request (2) to the MME. At this time, the eNodeB 11 cannot uniquely determine whether the Attach Request (2) should be forwarded to the general MME21 or the Customized MME22. Therefore, it may be transferred to the general MME21.

In the general MME21, after receiving the attach request (2), the terminal information (ME Identity) is acquired by the identity request / response (5b), and further, in cooperation with the HSS31. To authenticate and obtain a subscriber profile. That is, authentication and subscriber profile are performed by general MME21.

The general MME21 that has acquired the terminal information and the subscriber profile determines whether the UE1 should be connected to the general MME21 or the customized MME22. When connecting to the general MME21, the normal attach procedure (Attach Procedure) is continued.

When the UE1 is connected to the Customized MME22, the general MME21 uses the MME Change Request signal (MME Change Request) (GTP (GPRS Tunneling) newly introduced in this embodiment to instruct the Customized MME22 to change the MME. Protocol) Send signal).

At this time, the general MME21 sets the context information generated by the terminal authentication or the acquisition of the subscriber profile in the MME change request signal (MME Change Request).

When the Customized MME22 receives the MME change request signal (MME Change Request), it retains the context information set in the MME change request signal, and responds to the general MME21 with the MME change response signal (this implementation). (GTP signal) newly introduced in the example is transmitted.

The Customized MME22 then sends an Update Location Request (8) to the HSS31 to notify the HSS31 that the MME has changed.

Re-execute the Update Location Request with Customized MME22 to notify HSS31 of the MME change MME. Subsequent attachment processing (Attach Procedure) is performed by Customized MME22.

In addition, Customized MME22 can omit re-authentication if the security context information received from general MME21 is valid.

After that, the Customized MME22 continues the attach process (Attach Procedure), and the eNodeB 11 receives the Initial Context Setup Request / Attach Accept (17) from the Customized MME22.

The Initial Context Setup Request / Attach Accept (17) is a response to the Attach Request (2) received by the general MME21. In addition, it is necessary that eNodeB 11 has a function that can receive a response from another MME from the general MME21.

After that, the normal attach procedure (Attach Procedure) is continued.

Further, the general MME21 and the customized MME22 have a function of determining which MME the UE1 should be connected to, and this function is the same as that of the first embodiment.

Further, in the present embodiment, when the Attach Request signal from UE1 to be connected to the general MME21 is transferred to the Customized MME22, it is possible to prompt the general MME21 to change the MME by the same means. Is. For example, if UE1 is a normal mobile terminal (for example, a normal mobile terminal that does not support special services such as MTC and MBMS), once the UE1 is connected to Customized MME22, the MME is changed in Customized MME2. By transmitting a request signal (MME Change Request) to the general MME21, the general MME21 is reselected and the service from the general MME21 is provided.

As described above, in the present embodiment, the general MME instructs the Customized MME to change the MME, and the Customized MME receives the change of the MME and then continues the attach process (Attach Procedure). Allows the UE to attach to the appropriate MME.

&lt;Example 3&gt; As the third embodiment, an example in which the UE and the Customized MME are connected at the time of attaching in the EPC will be described. The system configuration of the third embodiment is the same as that of the first embodiment.

5 and 6 are sequence diagrams illustrating an operation example of the third embodiment. Note that Figures 5 and 6 are based on Figure 5.3.2.1-1: Attach procedure of 3GPP TS23.401, and the sequence numbers follow the figure. For details of each sequence, refer to the description of 3GPP TS23.401 5.3.2. The operation will be described below with reference to FIGS. 1, 5, and 6.

When UE1 sends an Attach Request (1), the eNodeB 11 first receives it, and the eNodeB 11 forwards the Attach Request (2) to the MME. At this time, the eNodeB 11 cannot uniquely determine whether the attach request (2) should be transferred to the general MME21 or the customized MME22. Therefore, it may be transferred to the general MME21.

In the general MME21, after receiving the attach request (2), the terminal information (ME Identity) is acquired by the identity request / response (5b). Furthermore, the general MME21 cooperates with the HSS31 to authenticate and acquire the subscriber profile.

The general MME21 that has acquired the terminal information and the subscriber profile determines whether the UE1 should be connected to the general MME21 or the customized MME22. When connecting to the general MME21, the normal attach procedure (Attach Procedure) is continued.

When the UE1 is connected to the Customized MME22, the general MME21 sends an Attach Reject message to the UE1 without continuing the Attach Procedure. That is, the general MME21 sends an Initial Context Setup Request / Attach Reject (17) to the eNodeB 11.

At this time, the general MME21 receives a parameter (new parameter introduced in this embodiment) for instructing re-attach to the Attach Reject signal, and at the time of re-attach. Customized MME22 is set with GUTI (Globally Unique Temporary Identity (Identifier)) parameters (new parameters introduced in this example) including GUMMEI (Globally Unique MME identifier) so that eNodeB 11 can be selected. The GUTI parameter consists of GUMMEI and M-TMSI (Temporary Mobile Station Identity), and MMEI consists of MCC (Mobile Country Code), MNC (Mobile Network Code) and MME Identifier. These are the new parameters introduced in this example, but since eNodeB11 is transparent, it does not affect eNodeB11.

When the UE1 receives the Attach Reject signal from the eNodeB 11, as shown in FIG. 6, the UE1 has the parameters set in the Attach-Reject signal to indicate the re-attach, and the GUTI. According to the parameters, an Attach Request (1) (Attach by GUTI) with GUTI set is sent to eNodeB 11. At this time, the eNodeB 11 determines an appropriate MME from the GUMMEI included in the GUTI, and forwards the Attach Request (2) to the Customized MME22.

The UE1 accepts the GUTI with the Attach Reject signal, and when the re-attach (Attach Request (1) in FIG. 6) is transmitted, the GUTI instructed by the Attach reject is instructed. The function to use is implemented. MME is equipped with a function to determine whether this UE is a target for re-selection.

After that, Customized MME22 continues the normal Attach Procedure. However, although it is an Attach Request with GUTI set, Customized MME22 itself does not hold context information.

For this reason, the Customized MME22 acquires the terminal information by the Identity Request / Response (4) after receiving the Attach Request signal, and further authenticates in cooperation with the HSS31. And acquire the subscriber profile.

Further, the general MME21 and the customized MME22 have a function of determining which MME the UE1 should be connected to, and this function is the same as that of the first embodiment.

Further, in the present embodiment, even when the Attach Request signal from the UE1 to be connected to the general MME21 is transferred to the Customized MME22, the UE1 is similarly prompted to reselect the MME. It is possible. That is, when the UE1 is a normal mobile terminal (for example, a normal mobile terminal that does not support special services such as MTC and MBMS), once the UE1 is connected to the Customized MME22, the Customized MME22 is By sending an Attach Reject signal to UE1 to prompt UE1 to reselect the general MME21 and UE1 sending a reattach request signal, the general MME21 is reselected and the service from the general MME21 is provided. To.

As described above, in the present embodiment, the general MME instructs the UE to reselect the MME, the UE receives the instruction, specifies the Customized MME, and then continues the attach procedure (Attach Procedure). Allows the UE to attach to the appropriate MME.

&lt;Example 4&gt; As the fourth embodiment, an example in which the UE and the Customized MME are connected at the time of attachment will be described in the EPC. The configuration of Example 4 is the same as that of Example 1. FIG. 7 is a sequence diagram for explaining an operation example of the fourth embodiment. Note that Figure 7 is based on Figure 5.3.2.1-1: Attach procedure of 3GPP TS23.401, and the sequence numbers follow the figure. For details of each sequence, refer to the description of 3GPP TS23.401 5.3.2. The operation will be described below with reference to FIGS. 1 and 7.

In order for UE1 to send an Attach Request (1) to MME, it first establishes an RRC Connection with eNodeB 11. To establish an RRC Connection, UE1 first sends an RRC Connection Request signal to eNodeB 11.

At this time, UE1 indicates that this signal requires a connection to the Customized MME22 (User Identity, a new value of establishment Cause, or a new parameter (a value or parameter newly introduced in this embodiment), or , Set some identifiers (PLMN-id etc. included in IMSI) that make up these parameters.

UE1 informs eNodeB that it is possible to connect to Customized MME by RRC Connection Request, so that the new parameter of RRC Connection Request (new Value or new parameter of establishment Cause) ) Is implemented.

When the eNodeB 11 receives the RRC Connection Request signal, it remembers that UE1 should connect to the Customized MME22, and continues the subsequent RRC connection processing (RRC Connection Procedure).

After establishing the RRC Connection, when UE1 sends an Attach Request (1), eNodeB 11 receives it. At this time, the eNodeB 11 transfers the attach request (Attach Request) (2) to the Customized MME 22 from the information stored when the RRC Connection Request (1) is received.

Customized MME22 continues the normal Attach Procedure after receiving the Attach Request (2).

In addition, UE1 has a function of instructing eNodeB 11 which MME of general MME21 or customized MME22 should be connected to. At this time, UE1 cannot hold all the MME information on the core network, so the instruction to eNodeB 11 uses information such as the MME type or service type instead of the identifier that can uniquely select the MME. ..

In addition, eNodeB 11 has a function to determine which MME the UE1 should be connected to.

In eNodeB11, as described above, the selection of MMM is the user ID (User Identity) in the message of RRC Connection Request, the new value of the communication establishment factor (Establishment Cause), or the new parameter, or these parameters. One or a combination of one or more of the identifiers of a part constituting the above.

As described above, in the present embodiment, the UE instructs the eNodeB to select the MME, the eNodeB receives the instruction to specify the Customized MME, and then continues the attach procedure (Attach Procedure). The UE can be attached to the appropriate MME.

&lt;Example 5&gt; As the fifth embodiment, an example in which the UE and the Customized MME are connected at the time of updating the tracking area (TA Update) in the EPC will be described. The configuration of Example 5 is the same as that of Example 1.

8 and 9 are sequence diagrams for explaining an operation example of the fifth embodiment. Note that Figure 8 is based on Figure 5.3.5-1: S1 Release Procedure of 3GPP TS23.401. See 3GPP TS23.401 5.3.5. Figure 9 is based on Figure 5.3.3.1-1: 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 of FIG. 3).

When UE1 sends an attach request (see 1 in Figure 3), the eNodeB 11 first receives it, and the eNodeB 11 relays the attach request (Attach Request) to the MME (see 2 in Figure 3).

At this time, the eNodeB 11 cannot uniquely determine whether the Attach Request should be forwarded to the general MME21 or the Customized MME22. Therefore, the Attach Request may be transferred to the general MME21.

In general MME21, after receiving an attach request, terminal information is acquired by identity request / response (see 4 and 5b in Fig. 3), and authentication and response are performed in cooperation with HSS31. Obtain a subscriber profile.

The general MME21 that has acquired the terminal information and the subscriber profile determines whether the UE1 should be connected to the general MME21 or the customized MME22. After that, the normal Attach Procedure is continued. When connecting to the general MME21, the process is completed here.

When the UE1 is connected to the Customized MME22, the general MME21 releases the S1 (S1 Release) as shown in FIG. 8 in order to cause the UE1 to perform the tracking area update (TA Update). At this time, the general MME21 sends the S1 UE Context Release Command (4) to the eNodeB 11.

The general MME21 is the S1 UE Context Release Command (4), which indicates the MME to be selected the next time the eNodeB establishes an S1 connection with the MME by using an MME identifier (for example, GUMMEI). At the time of S1 release (S1 Release) for starting Load Balancing TAU (Load Balancing TAU), the parameter for instructing GUMMEI to specify the next MME to eNodeB is a new parameter. At this time, eNodeB 11 keeps holding the MME identifier as the information for the next MME selection while holding the session information for UE1 even after the completion of S1 release (S1 Release).

When the S1 Release is made, UE1 then sends a TAU Request (2), as shown in Figure 9. The TAU Request (2) from UE1 is first received by the eNodeB 11, and the TAU Request (3) is transferred from the eNodeB 11 to the MME. At this time, since eNodeB 11 is in the state where S1 has been released (S1 Release), MME selection is performed and S1 Connection (S1 Connection) is established. At the time of S1 release, eNodeB11 selects Customized MME according to GUMMEI instructed by the old MME (old MME) (= general MME). Here, eNodeB 11 has a function of holding the next GUMMEI for each UE.

In selecting the MME, the eNodeB 11 selects the Customized MME 22 according to the GUMMEI MME Identifier indicated by the S1 UE Context Release Command signal received from the general MME 21. Since GUTI (GUMMEI) on the NAS indicates old MME (= general MME), it is possible to acquire the m context.

After receiving the TAU Request (3), the Customized MME22 continues the normal TA Update Procedure. Customized MME22 sends a context request (Context Request) (4) to general MME21 and receives a context response (Context Response) (5).

When the S-GW relocates, the Customized MME22 sends a Context Acknowledge (7) containing the S-GW change instruction to the general MME, and the Customized MME22 sends a new S-GW41 (new Serving). When GW) is selected, Customized MME22 sends a Create Session Request (8) to the new S-GW41.

In response to this, the new S-GW41 (new Serving GW) sends a Modify Bearer Request (9) to the P-GW51, and when the response is received from the P-GW51, the new S-GW Returns the Create Session Response (11) to Customized MME22.

Customized MME22 sends Update Location (12) to HSS31.

Upon receiving the Cancel Location (13) from the HSS31 to the General MME21, the General MME21 deletes the MM context and sends an Update Location Acck (14) to the HSS31. An update location acknowledgment (Update Location Ack) (17) is sent from HSS31 to Customized MME22 for Update Location (12).

The general MME21 sends a delete session request (18) to the old S-GW41 (old Serving GW), and the response (19) is general from the old S-GW41 (old Serving GW). Sent to MME21.

Customized MME22 sends TAU Accespt (20) to UE1.

If GUTI is included in TAU Accept (20), UE1 returns TAU Complete (21) to Customized MME22 to receive the signal TAU Accept (20). ) Is an acknowledgment.

The general MME 21 and the customized MME 22 have a function of determining which MME the UE1 should be connected to, and this function is the same as that of the first embodiment.

Further, in this embodiment, a TA update request from a UE1 (for example, a normal mobile terminal (for example, a normal mobile terminal that does not support special services such as MTC and MBMS)) that should be connected to the general MME21 by the same means as described above. By selecting the general MME in the eNodeB 11 that has received the (TA Update Request), the UE1 is connected to the general MME21 and the service from the general MME21 is provided.

Further, in this embodiment, the TA update procedure was used in the procedure of FIG. 9, but the feature of this embodiment is that the MME is selected by eNodeB 11. Therefore, other procedures (even Procedures) for reestablishing the S1 Connection, such as a Service Request, can be realized.

As described above, in this embodiment, the general MME instructs eNodeB to reselect the MME, and the eNodeB receives the instruction, specifies the Customized MME at the next MME selection, and then continues the process (Procedure). By doing so, the UE can be connected to the appropriate MME.

&lt;Embodiment 2&gt; As the second embodiment, an example in which a UE and a specific SGSN (Customized SGSN) are connected at the time of attachment in UMTS (Universal Mobile Telecommunications System) will be described. FIG. 2 is a diagram showing a system configuration of the second embodiment.

The UE101 may be a terminal that receives a service from a specific SGSN (Customized SGSN), for example, the above-mentioned MTC device, an MBMS compatible terminal, or the like. If the UE101 is a normal mobile terminal that uses a normal service such as a mobile phone terminal or a smartphone (for example, a terminal that does not support a specific service such as MTC or MBMS), it is connected to a general SGSN. In addition, as will be described later, when a specific SGSN (Customized SGSN) is selected in response to an Attach request from a normal mobile terminal (for example, a terminal that does not support a specific service such as MTC or MBMS), the SGSN is reselected. Is performed and reconnected to the general SGSN.

Node B111 and RNC (Radio Network Controller) 171 represent devices for radio access adopted in UMTS systems.

The general SGSN121 and Customized SGSN122 are in-service devices used for UMTS, and may or may not handle the user plane depending on the connection form. If the SGSN does not handle the user plane, the user plane is set between S-GW and RNC.

HLR (Home Location Register) 131 is a database that holds subscriber information.

GGSN (Gateway GPRS (General Radio Packet Service) Support Node: In the claims, it is referred to as "Gateway GPRS Support Node") 141 is a gateway device that connects to an external network. The service network 161 indicates an external network (data packet network).

In FIG. 2, NodeB111 and RNC171 correspond to the radio access networks RAN, SGSN, GGSN, etc. correspond to the core network.

Hereinafter, the second embodiment will be described with reference to some examples having different control methods. The following Examples 6-10 correspond to the above-mentioned Aspects 6-10, respectively.

&lt;Example 6&gt; FIG. 10 is a sequence diagram for explaining an operation example of the sixth embodiment, and is based on 3GPP TS 23.060 6.5 Fig. 22.

In Figure 10, MS (Mobile Station) is UE101 in Fig. 2. RAN (Radio Access Network) is NodeB1171 and RNC171 in Fig. 2. The general SGSN is the general SGSN121 in Fig. 2. Customized SGSN is the Customized SGSN (Specific SGSN) 122 in Fig. 2. GGSN is GGSN141 in Figure 2, The HLR is HLR131 in FIG.

The VLR of MSC (Mobile Switching Center) / VLR (Visitor Location Register) is a location register for CS services other than HLR. The EIR (Equipment Identifier Register) holds a valid mobile device identifier.

The operation will be described with reference to FIGS. 2 and 10. In the following, the MS in FIG. 10 will be replaced with the UE 101 in FIG.

When UE101 (MS) sends an attach request (Attach Request) (1), NodeB111 first receives it and forwards the attach request (Attach Request) (1) to RNC171. The RNC171 forwards the Attach Request (1) to the SGSN. At this time, the RNC171 cannot uniquely determine whether the Attach Request should be forwarded to the general SGSN121 or the Customized SGSN122. Therefore, it may be transferred to the general SGSN121.

In general SGSN121, after receiving an attach request, terminal information is acquired by identity request / response (3, 4), and in cooperation with HLR131, authentication and subscriber profile. To get. The general SGSN121 will be used for authentication and subscriber profile acquisition.

The general SGSN 121 that has acquired the terminal information and the subscriber profile determines whether the UE 101 should be connected to the general SGSN 121 or the Customized SGSN 122. When connecting to the general SGSN121, the normal attach procedure (Attach Procedure) is continued.

When the UE101 is connected to the Customized SGSN122, the general SGSN121 uses the SGSN re-selection Command (newly introduced in this embodiment, RANAP) to instruct the RNC171 to reselect the SGSN. Signal) is sent. At this time, the general SGSN 121 sets an identifier (for example, RAI (Routing Area Identifier), NRI (Network Resource Identifier), etc.) that identifies the Customized SGSN 122 in the SGSN re-selection Command signal. That is, the general SGSN 121 requests the RNC to reselect the SGSN, and at that time, carries the information (RAI) necessary for selecting the specific SGSN 122. For reselection within the same pool, NRI may be used. The SGSN has a function of determining whether the UE 101 is a target for re-selection.

When the RNC171 receives the SGSN re-selection Command signal, it selects the Customized SGSN122 according to the identifier set in this signal and transfers the Attach Request (1). Since the NAS (Non Access Stratum) parameter of the attach request (Attach Request) is required for the specific SGSN122, the attach request (Attach Request) is resent with the RNC171. RNC171 has a function to hold NAS messages.

Since the old SGSN (= general SGSN) cannot be specified in the new SGSN (= Customized SGSN), the context cannot be inherited. Therefore, it is necessary to acquire the authentication / subscriber profile even for the new SGSN. After receiving the Attach Request (2), the Customized SGSN122 acquires the terminal information by the Identity Request / Response, and further cooperates with the HLR131 to acquire the authentication and the subscriber profile. Do. That is, the same processing as general SGSN121 is performed.

The Customized SGSN122 that has acquired the terminal information and the subscriber profile determines whether the UE101 should be connected to the general SGSN121 or the Customized SGSN (022). Here, since it has been reselected by RNC171, the normal attach procedure (Attach Procedure) is continued without transmitting the SGSN re-selection Command signal.

In addition, the general SGSN121 and the customized SGSN122 have a function of determining which SGSN the UE101 should be connected to, and this determination is based on information from the UE101 (for example, IMSI (International Mobile Subscriber Identity), IMEI, UE network capability, MS network capability, Mobile station classmark 2, Mobile station classmark 3, -Device properties, new parameters of the Attach Request signal that will be added in the future, or identifiers of some of the parameters that make up these parameters (PLMN-id, etc. included in the IMSI), Information from HLR131 (eg Feature-List, APN, -Or a new parameter of the Update Location Answer / Insert Subscriber Data Request signal that will be added in the future, or Partial identifiers that make up these parameters) Either or a combination of the above.

Further, in the present embodiment, even when the Attach Request signal from the UE 101 to be connected to the general SGSN 121 is transferred to the Customized SGSN 122, it is possible to prompt the RNC 171 to reselect the SGSN by the same means. is there. When UE101 is a normal mobile terminal (for example, a terminal that does not support a specific service such as MTC or MBMS), when connected to Customized SGSN122, Customized SGSN122 prompts RNC171 to reselect SGSN, general SGSN121 is reselected, and general Service from SGSN121 is provided.

As described above, in the present embodiment, the SGSN instructs the RNC to reselect the SGSN, the RNC receives the instruction to reselect the SGSN, and then the attach procedure is continued. , The UE can be attached to the appropriate SGSN.

&lt;Example 7&gt; As a seventh embodiment, an example in which a UE and a specific SGSN are connected at the time of attachment in UMTS will be described. The configuration of Example 7 is the same as that of Example 6. FIG. 11 is a sequence diagram for explaining an operation example of the seventh embodiment. The operation will be described with reference to FIGS. 2 and 11.

When UE101 sends an Attach Request (1), NodeB111 first receives it and forwards it to RNC171. RNC171 transfers this to SGSN. At this time, the RNC171 cannot uniquely determine whether the Attach Request should be forwarded to the general SGSN121 or the Customized SGSN122. Therefore, it may be transferred to the general SGSN121.

After receiving the attach request, the general SGSN 121 acquires the terminal information by the identity request / response, and further, authenticates and acquires the subscriber profile in cooperation with the HLR131. The general SGSN121 will be used for authentication and subscriber profile acquisition.

The general SGSN 121 that has acquired the terminal information and the subscriber profile determines whether the UE 101 should be connected to the general SGSN 121 or the Customized SGSN 122. When connecting to the general SGSN121, the normal attach procedure (Attach Procedure) is continued.

When the UE 101 is connected to the Customized SGSN 122, the general SGSN 121 transmits an SGSN Change Request (a GTP signal newly introduced in the present embodiment) in order to instruct the Customized SGSN 122 to change the SGSN.

At this time, the general SGSN 121 sets the context information generated by mobile device authentication or acquisition of the subscriber profile in the SGSN Change Request signal. That is, when requesting an SGSN change from the general SGSN 121 to the Customized SGSN 122, the context is notified to the new SGSN (Customized SGSN 122). SGSN is equipped with a function to determine whether UE101 is a target for re-selection.

When the Customized SGSN122 receives the SGSN Change Request signal, it retains the context information set in the SGSN Change Request signal and responds to the general SGSN121 with an SGSN change response (SGSN). Change Response) signal (GTP signal newly introduced in this embodiment) is transmitted.

The Customized SGSN122 then sends an Update Location signal (8) to the HLR131 to notify the HLR131 that the SGSN has changed.

Further, the Customized SGSN122 can omit the re-authentication if the security context information received from the general SGSN121 is valid.

After that, the Customized SGSN122 continues the Attach Procedure, and the RNC171 receives the Attach Accept signal (9) from the Customized SGSN122. After that, the normal Attach Procedure is continued.

Further, the general SGSN 121 and the customized SGSN 122 have a function of determining which SGSN the UE 101 should be connected to, and this function is the same as that of the sixth embodiment.

Further, in the present embodiment, when the Attach Request signal from the UE 101 to be connected to the general SGSN 121 is transferred to the Customized SGSN 122, it is possible to prompt the general SGSN 121 to change the SGSN by the same means. is there. If the UE101 is a normal mobile terminal (for example, a terminal that does not support a specific service such as MTC or MBMS), when connecting to the Customized SGSN122, the general SGSN121 is reselected in the Customized SGSN122, and the service from the general SGSN121 is provided. ..

As described above, in this embodiment, the general SGSN instructs the specific SGSN to change the SGSN, the specific SGSN receives the change of the SGSN, and then the attach procedure is continued. Allows the UE to attach to the appropriate SGSN.

&lt;Example 8&gt; As Example 8, an example in which a UE and a specific SGSN are connected at the time of Attach in UMTS will be described. The configuration of Example 8 is the same as that of Example 6. 12 and 13 are sequence diagrams for explaining an operation example of the eighth embodiment. The operation will be described with reference to FIGS. 2, 12, and 13.

When the UE101 (MS) sends an Attach Request (1), the NodeB111 first receives it and forwards the attach request to the RNC171. The RNC171 forwards the attach request to the SGSN. At this time, the RNC 171 cannot uniquely determine whether the Attach Request should be forwarded to the general SGSN 121 or the Customized SGSN 122. Therefore, it may be transferred to the general SGSN121.

In the general SGSN121, after receiving the attach request (1), the terminal information is acquired by the identity request / response (3), and further, the authentication and the subscriber in cooperation with the HLR131. Get the profile.

The general SGSN 121 that has acquired the terminal information and the subscriber profile determines whether the UE 101 should be connected to the general SGSN 121 or the Customized SGSN 122. When connecting to the general SGSN121, the normal attach procedure (Attach Procedure) is continued.

When the UE101 is connected to the Customized SGSN122, the general SGSN121 sends an attach rejection (Attach Reject signal) (9) to the UE101 without continuing the attach process (Attach Procedure).

At this time, the general SGSN121 has a parameter for instructing re-attach to the Attach Reject signal, and the RAI (Routing Area) so that the RNC171 can select the Customized SGSN122 at the time of re-attach. Identity) parameter (parameter newly introduced in this embodiment) is set. These are the new parameters introduced in this example, but in RNC171, they are transparent and have no effect.

The UE needs a function to accept RAI by Attach Reject and use RAI specified by Reject when re-attaching. SGSN has the function of determining whether UE101 is a target for re-selection.

When the UE101 receives the Attach Reject signal (9), it follows the parameters indicating re-attach and the RAI parameters set in the Attach Reject signal (9), as shown in FIG. , Send the Attach Request signal (1) with RAI set to RNC171 (reattach by P-TMSI (Packet Temporary Mobile Subscriber Identifier)). At this time, the RNC171 determines an appropriate SGSN from the RAI and forwards the attach request to the Customized SGSN122.

After that, the Customized SGSN122 continues the normal Attach Procedure.

However, although it is an Attach Request for which RAI is set, Customized SGSN122 itself does not hold context information. Therefore, after receiving the Attach Request signal (1), the terminal information is acquired by the Undentity Request / Response (3), and the terminal is further authenticated and subscribed in cooperation with the HLR131. Acquire a person profile.

Further, the general SGSN 121 and the customized SGSN 122 have a function of determining which SGSN the UE 101 should be connected to, and this function is the same as that of the sixth embodiment.

Further, in the present embodiment, when the Attach Request signal from the UE 101 to be connected to the general SGSN (121) is transferred to the Customized SGSN 122, the UE 101 is prompted to reselect the SGSN by the same means. Is possible. If the UE101 is a normal mobile terminal (for example, a terminal that does not support a specific service such as MTC or MBMS), when connected to the Customized SGSN122, the Customized SGSN122 sends an Attach Reject signal to the UE101 to send the UE101. Is prompted to reselect the general SGSN 121, and the UE 101 transmits a reattach request signal, so that the general SGSN 121 is reselected and the service from the general SGSN 121 is provided.

As described above, in the present embodiment, the general SGSN instructs the UE to reselect the SGSN, and the UE receives the instruction to specify the specific SGSN and then continues the attach procedure (Attach Procedure). Allows the UE to attach to the appropriate SGSN.

&lt;Example 9&gt; As the ninth embodiment, an example in which a UE and a specific SGSN are connected at the time of attachment in UMTS will be described. The configuration of Example 9 is the same as that of Example 6. FIG. 14 is a sequence diagram illustrating an operation example of the ninth embodiment. The operation will be described with reference to FIGS. 2 and 14.

In order for UE101 to send an Attach Request to SGSN, it first establishes an RRC Connection with RNC171. To establish an RRC Connection, the UE101 first sends an RRC Connection Request signal to the RNC171.

At this time, the UE 101 has a parameter (User Identity, a new Value of establishment Cause, or a new parameter (introduced in this embodiment) indicating that the RRC Connection Request signal requires a connection to the Customized SGSN 122. Set a new value or parameter) or a partial identifier (PLMN-id, etc. included in the IMSI) that composes these parameters.

When the RNC171 receives the RRC Connection Request signal, it remembers that the UE101 should connect to the Customized SGSN122 and continues the subsequent RRC Connection Procedure.

After the RRC Connection is established, when the UE101 sends an Attach Request (1), the NodeB111 first receives it and forwards the Attach Request to the RNC171.

The RNC171 forwards an Attach Request to the SGSN. At this time, the RNC 171 transfers the Attach Request signal to the Customized SGSN 122 from the information stored when the RRC Connection Request signal is received.

The Customized SGSN122 continues normal attach processing (Attach Procedure) after receiving the Attach Request signal.

In addition, UE101 has a function of instructing RNC171 which SGSN of general SGSN121 or Customized SGSN122 should be connected. At this time, UE101 does not retain all SGSN information on the core network. Since it cannot be done, the instruction to RNC171 is not an identifier that can uniquely select SGSN, but information such as SGSN type or service type.

In addition, the RNC171 has a function of determining which SGSN the UE101 should be connected to, and this determination is based on the new value of the User Identity (establishment Cause) or the new value of the user identity establishment cause as described above. Either or a combination of new parameters (new values or parameters introduced in this embodiment), or a part of the identifiers constituting these parameters.

As described above, in this embodiment, the UE 101 instructs the RNC171 to select the SGSN, and the RNC171 receives this instruction, specifies the specific SGSN, and then continues the attach process (Attach Procedure). To do. With such a configuration, the UE 101 can be attached to an appropriate SGSN.

&lt;Example 10&gt; As the tenth embodiment, an example in which a UE and a specific SGSN are connected at the time of RA update in UMTS will be described. The configuration of Example 10 is the same as that of Example 6. 15 and 16 are sequence diagrams for explaining an operation example of the tenth embodiment. The operation will be described below with reference to a part of FIGS. 2, 15, 16, and 10.

When UE101 sends an Attach Request (see 1. in Figure 10), NodeB111 first receives it and forwards it to RNC171. RNC171 transfers this to SGSN. At this time, the RNC 171 cannot uniquely determine whether the Attach Request should be forwarded to the general SGSN 121 or the Customized SGSN (12). Therefore, it may be transferred to the general SGSN121.

After receiving the attach request, the general SGSN121 acquires the terminal information by the identity request / response (see 3 and 5 in Fig. 10), and further authenticates and authenticates in cooperation with the HLR131. Obtain a subscriber profile.

The general SGSN 121 that has acquired the terminal information and the subscriber profile determines whether the UE 101 should be connected to the general SGSN 121 or the Customized SGSN 122. When connecting to the general SGSN121, the normal attach procedure (Attach Procedure) is continued.

When the UE101 is connected to the Customized SGSN122, the general SGSN121 performs an Iu release (Iu Release) as shown in FIG. 15 in order to cause the UE101 to perform an RA (Routing Area) update.

At this time, the general SGSN121 transmits an Iu Release Command signal (4 in FIG. 15) to the RNC171. The general SGSN 121 uses an Iu Release Command signal to indicate the SGSN to be selected the next time the RNC establishes an Iu Connection with the SGSN by an SGSN identifier (eg RAI, NRI, etc.). To do. If it is in the same pool, it may be NRI.

Even after the completion of Iu release, RNC171 continues to hold the SGSN identifier as information for the next SGSN selection while holding the session information for UE101.

Once an Iu Release has been made (after the IU Release Complete (6) has been sent from the RNC171 to the General SGSN121), the UE101 then makes a RAU request (RA Update), as shown in Figure 16. Request) (2) is sent.

The RAU Request (2) is first received by the NodeB111, which forwards the RAU Request (3) to the RNC171.

RNC171 forwards the RAU request to SGSN. At this time, since RNC171 is in the state where Iu has been released (c), SGSN is selected and Iu connection is established.

In SGSN selection, the RNC171 selects the Customized SGSN122 according to the SGSN identifier indicated by the Iu Release Command signal received from the general SGSN121. RNC selects Customized SGSN according to RAI (or NRI) instructed by old SGSN (= general SGSN) at the time of Iu release. The RNC has a function of holding the next RAI for each UE.

After receiving the RAU request, the Customized SGSN122 continues the normal RA update process (RA Update Procedure). Since P-TMSI (RAI) on NAS indicates the general SGSN which is the old SGSN, get the context.

Further, the general SGSN 121 and the customized SGSN 122 have a function of determining which SGSN the UE 101 should be connected to, and this function is the same as that of the sixth embodiment.

Further, in this embodiment, an RA update request from a UE101 (for example, a normal mobile terminal (for example, a normal mobile terminal that does not support special services such as MTC and MBMS)) that should be connected to the general MME21 by the same means as described above. (RA Update Request)) is received, and by selecting the general SGSN121 in the RNC17, the UE101 is connected to the general SGSN121 and the service from the general SGSN121 is provided.

Further, in this embodiment, the RA update process (RA Update Procedure) was used in the procedure of FIG. 16, but in this embodiment, the SGSN selection is performed by the RNC171. Therefore, for example, PDP Context Activation, etc. It can also be realized by other processes (Procedure) that reestablish the Iu Connection.

As described above, in this embodiment, the general SGSN instructs the RNC to reselect the SGSN, and the RNC receives the instruction, specifies the specific SGSN at the next SGSN selection, and then continues the process (Procedure). By doing so, the UE can be connected to the appropriate SGSN.

The differences between the above-described embodiments will be described below.

&lt;Mobile network&gt; In Examples 1-5, for example, LTE (Long Term Evolution) (radio access network is E-UTRAN (Evolved-Universal Terrestrial Radio Access Network), core network is EPC), Examples 6-10 are, for example, 3G (3rd Generation) (the radio access network is UTRAN (Universal Terrestrial Radio Access Network), and the core network is GPSR).

&lt;Realization method&gt; A) Examples 1 and 6: Attach processing (RAN (Radio Access Network: retry in radio access network)).

B) Examples 2 and 7: Attach processing (core network (CN) interwork).

C) Examples 3 and 7: Retry by terminal.

D) Examples 4 and 8: Core network (CN) selection.

E) Examples 5 and 10: Location management area update (RAU / TAU).

&lt;Scope of influence (targets that need to be modified for implementation)&gt; A) Examples 1 and 6: RAN (Radio Access Network) and CN (Core Network).

B) Examples 2 and 7: CN (RAN).

C) Examples 3 and 8: Terminal and CN.

D) Examples 4 and 9: Terminal and RAN.

E) Examples 5 and 10: RAN and CN.

&lt;Advantages of implementation, etc.&gt; A) Examples 1 and 6: No need to add functions to the terminal. It is necessary to add functions to RAN.

B) Examples 2 and 7: No need to add functions to the terminal. It may not be necessary to add functions to RAN. The amount of signal is the smallest in the examples.

C) Examples 3 and 8: No need to add functions to RAN. It is easy to add functions to terminals and CNs. However, it takes time due to attach rejection.

D) Examples 4 and 9: No need to add functions to CN. There are more function additions in RAN than in other examples. RAN needs to maintain and manage the CN list for CN selection. Since it is before HLR / HSS access, the information used to judge CN selection is limited.

E) Examples 5 and 10: No need to add functions to the terminal. CN can be reselected after attachment due to contract change etc.

&lt;Core network node selection example&gt; Hereinafter, some examples of selecting the core network node will be described in the above-described embodiments and examples.

Connect an MTC (Machine Type Communication) device (M2M device) to a specific CN node (a node streamlined for MTC devices).

Connect MBMS users to a specific CN node (MBMS compatible CN node).

In addition, in order to start a new service on a small scale, the service will be provided only by a specific CN node.

&lt;Case in LTE&gt; Connect a specific UE to a node that has collocated MME and SGW. Although not particularly limited, for example, when a small amount of data traffic is transferred to SMS (Short Message Service) and transmitted to the UE, if MME and SGW are collocated, the implementation of SMS conversion processing becomes easy.

In addition, MME is sorted by terminal type (CSFB (CS Fallback) terminal and VoLTE terminal, etc.). CSFB (CS Fallback) is a function that switches wireless to 3G (or 2G) when there is an incoming / outgoing CS (Circuit Switched) service during LTE connection. VoLTE (Voice over LTE) is a function that provides voice (which was provided by CS) services on LTE. The CSFB terminal requires interwork with the MSC. VoLTE terminals require interwork with IMS (IP Multimedia Subsystem). In CSFB, let the MSC (Mobile Switching Center) that is attached first select the collocated MME.

In addition, each disclosure of the above patent documents shall be incorporated into this document by citation. Within the framework of the entire disclosure (including the scope of claims) of the present invention, it is possible to change or adjust the embodiments or examples based on the basic technical idea thereof. Further, various combinations or selections of various disclosure elements (including each element of each claim, each element of each embodiment, each element of each drawing, etc.) are possible within the scope of the claims of the present invention. .. That is, it goes without saying that the present invention includes all disclosure including claims, and various modifications and modifications that can be made by those skilled in the art in accordance with the technical idea. At least one part of the disclosure of the above embodiments and examples is not particularly limited, but is added as follows. (Appendix 1) The core network of the mobile communication system includes a plurality of nodes having different service functions provided to the terminal as a node for managing the mobility of the terminal, and the plurality of nodes are based on the subscriber information and the terminal information. A communication system in which a node to be connected to the terminal is selected from among them according to the service characteristics or the terminal type used by the terminal, and the terminal is connected to the selected node. (Appendix 2) The first mobility management entity node that receives the attach request from the terminal via the base station apparatus provides the terminal with a service different from the service provided by the first mobility management entity node. A mobility management entity reselection request signal is sent to the base station device to connect to the mobility management entity node of 2. The communication system according to Appendix 1, wherein the base station apparatus connects the terminal to the second mobility management entity node by retransmitting an attach request to the second mobility management entity node. (Appendix 3) The first mobility management entity node that receives the attach request from the terminal via the base station apparatus provides the terminal with a service different from the service provided by the first mobility management entity node. In order to connect to the second mobility management entity node, a mobility management entity change request signal is sent to the second mobility management entity node to connect to the second mobility management entity node. The communication system according to Appendix 1, wherein the second mobility management entity node connects the terminal to the second mobility management entity node by continuing the attach processing procedure for the attach request. (Appendix 4) The first mobility management entity node that received the attach request from the terminal via the base station device An identifier of the second mobility management entity node is assigned to connect the terminal to a second mobility management entity node that provides a service different from the service provided by the first mobility management entity node. Send the attached reject to the terminal, The communication system according to Appendix 1, wherein the terminal assigns an identifier of the second mobility management entity node to the attach request, retransmits the request, and connects to the second mobility management entity node. (Appendix 5) The terminal is an RRC connection (RRC) to which connection request information is given to a second mobility management entity node that provides a service different from the service provided by the first mobility management entity node. Connection) Send the request to the base station equipment and Upon receiving the RRC connection request, the base station apparatus selects the second mobility management entity node when transmitting the attach request from the terminal that has established the RRC connection to the mobility management entity, and selects the terminal. The communication system according to Appendix 1, which connects to the second mobility management entity node. (Appendix 6) The first mobility management entity node that establishes a session with the terminal will be the next mobility management entity when the connection established between the base station device and the first mobility management entity node is opened. Instructs the base station apparatus to select a second mobility management entity node that provides a service different from the service provided by the first mobility management entity node. When the terminal sends a location management area update request to the base station apparatus, the base station apparatus selects the second mobility management entity node and transfers the terminal to the second mobility management entity node. The communication system described in Appendix 1 that connects to. (Appendix 7) The first serving GPRS (General Packet Radio Service) support node that receives the attach request from the terminal via the wireless network controller provides the terminal with a service different from the service provided by the first serving GPRS support node. Send a serving GPRS support node reselection request signal to the wireless network controller to connect to a second serving GPRS support node that provides The communication system according to Appendix 1, wherein the wireless network controller connects the terminal to the second serving GPRS support node by resending the attach request to the second serving GPRS support node. (Appendix 8) The first serving GPRS (General Packet Radio Service) support node (SGSN) that receives the attach request from the terminal via the wireless network controller provides the terminal with a service provided by the first serving GPRS support node. In order to connect to the second serving GPRS support node that provides a different service from the above, the serving GPRS support node change request signal is transmitted to the second serving GPRS support node. The communication system according to Appendix 1, wherein the second serving GPRS support node connects the terminal to the second serving GPRS support node by continuing the attach process for the attach request. (Appendix 9) The first serving GPRS (General Packet Radio) that received the attach request from the terminal via the wireless network controller. The Service) support node (SGSN) connects the terminal to a second serving GPRS support node that provides a different service than the service provided by the first serving GPRS support node. An attach reject with a support node identifier is sent to the terminal, The communication system according to Appendix 1, wherein the terminal assigns an identifier of the second serving GPRS support node to an attach request and retransmits it to connect the terminal to the second serving GPRS support node. (Appendix 10) The terminal is an RRC (Radio Resource Control) connection request to which connection request information is given to a second serving GPRS support node that provides a service different from the service provided by the first serving GPRS (General Packet Radio Service) support node. To the wireless network controller, Upon receiving the RRC connection request, the wireless network controller selects the second serving GPRS support node when transmitting the attach request from the terminal that has established the RRC connection to the serving GPRS support node, and selects the terminal. The communication system according to Appendix 1, which connects to the second serving GPRS support node. (Appendix 11) The first serving GPRS (General Packet Radio Service) support node that establishes a session with the terminal is the connection established between the first serving GPRS (General Packet Radio Service) support node and the wireless network controller. At the time of opening, the wireless network controller is instructed to select a second serving GPRS support node that provides a service different from the service provided by the first serving GPRS support node in the next selection of the serving GPRS support node. , When the terminal sends a location management area update request to the wireless network controller, the wireless network controller selects the second serving GPRS support node and connects the terminal to the second serving GPRS support node. , The communication system described in Appendix 1. (Appendix 12) In the core network of the mobile communication system, a plurality of nodes having different service functions provided to the terminal are arranged as nodes for managing the mobility of the terminal. Based on the subscriber information and the terminal information, the node to be connected to the terminal is selected from the plurality of nodes according to the service characteristics or the terminal type used by the terminal. A communication method for connecting the terminal to the selected node. (Appendix 13) The first mobility management entity node that receives the attach request from the terminal via the base station apparatus provides the terminal with a service different from the service provided by the first mobility management entity node. A mobility management entity reselection request signal is transmitted to the base station device to connect to the mobility management entity node of 2, and the base station device requests an attach to the second mobility management entity node. 12. The communication method according to Appendix 12, wherein the terminal is connected to the second mobility management entity node by retransmitting. (Appendix 14) The first mobility management entity node that receives the attach request from the terminal via the base station apparatus provides the terminal with a service different from the service provided by the first mobility management entity node. In order to connect to the second mobility management entity node, a mobility management entity change request signal is sent to the second mobility management entity node to connect to the second mobility management entity node. The communication method according to Appendix 12, wherein the second mobility management entity node connects the terminal to the second mobility management entity node by continuing the processing procedure for the attach request. (Appendix 15) The first mobility management entity node that received the attach request from the terminal via the base station device An identifier of the second mobility management entity node is assigned to connect the terminal to a second mobility management entity node that provides a service different from the service provided by the first mobility management entity node. Send the attached reject to the terminal, The communication method according to Appendix 12, wherein the terminal assigns an identifier of the second mobility management entity node to the attach request, retransmits the request, and connects to the second mobility management entity node. (Appendix 16) The terminal gives an RRC connection request (RRC (Radio)) to which connection request information is given to the second mobility management entity node that provides a service different from the service provided by the first mobility management entity node. Resource Control) Connection Request) is sent to the base station equipment, Upon receiving the RRC connection request, the base station apparatus selects the second mobility management entity node when transmitting the attach request from the terminal that has established the RRC connection to the mobility management entity, and selects the terminal. The communication method according to Appendix 12, which connects to the second mobility management entity node. (Appendix 17) The first mobility management entity node that establishes a session with the terminal will be the next mobility management entity when the connection established between the base station device and the first mobility management entity node is opened. Instructs the base station apparatus to select a second mobility management entity node that provides a service different from the service provided by the first mobility management entity node. When the terminal sends a location management area update request to the base station apparatus, the base station apparatus selects the second mobility management entity node and transfers the terminal to the second mobility management entity node. The communication method described in Appendix 12 for connecting to. (Appendix 18) The first serving GPRS (General Packet Radio Service) support node (SGSN) that receives the attach request from the terminal via the wireless network controller provides the terminal with a service provided by the first serving GPRS support node. Sends a serving GPRS support node reselection request signal to the wireless network controller to connect to a second serving GPRS support node that offers a different service than The communication method according to Appendix 12, wherein the wireless network controller retransmits the attach request to the second serving GPRS support node and connects the terminal to the second serving GPRS support node. (Appendix 19) The first serving GPRS (General Packet Radio Service) support node (SGSN) that receives the attach request from the terminal via the wireless network controller provides the terminal with a service provided by the first serving GPRS support node. In order to connect to the second serving GPRS support node that provides a different service from the above, the serving GPRS support node change request signal is transmitted to the second serving GPRS support node. The communication method according to Appendix 12, wherein the second serving GPRS support node connects the terminal to the second serving GPRS support node by continuing the attach process. (Appendix 20) The first serving GPRS (General Packet Radio) that received the attach request from the terminal via the wireless network controller. The Service) support node (SGSN) connects the terminal to a second serving GPRS support node that provides a different service than the service provided by the first serving GPRS support node. An attach reject with a support node identifier is sent to the terminal, The communication method according to Appendix 12, wherein the terminal assigns an identifier of the second serving GPRS support node to the attach request and retransmits the request, and connects the terminal to the second serving GPRS support node. (Appendix 21) The terminal makes an RRC connection request (RRC (Radio Resource Control) Connection Request) to which connection request information is given to the second serving GPRS support node that provides a service different from the service provided by the first serving GPRS support node. Send to wireless network controller Upon receiving the RRC connection request, the wireless network controller selects the second serving GPRS support node when transmitting the attach request from the terminal that has established the RRC connection to the serving GPRS support node (SGSN). The communication method according to Appendix 12, wherein the terminal is connected to the second serving GPRS support node. (Appendix 22) The first serving GPRS (General Packet Radio Service) support node that establishes a session with the terminal is established between the first serving GPRS (General Packet Radio Service) support node and the wireless network controller. When the connection is opened, the wireless network controller is asked to select a second serving GPRS support node that provides a service different from the service provided by the first serving GPRS support node at the next selection of the serving GPRS support node. Give instructions, When the terminal sends a routing area update request to the wireless network controller, the wireless network controller selects the second serving GPRS support node and connects the terminal to the second serving GPRS support node. The communication method described in Appendix 12. (Appendix 23) For one mobility management node device that manages terminal mobility Based on the subscriber information and the terminal information, another mobility management node device corresponding to the service characteristics or the terminal type used by the terminal is selected. A node device that controls to connect the terminal to another selected mobility management node device. (Appendix 24) A node device in which the node device of Appendix 23 is a node device on a radio access network or a core network of a mobile communication system. (Appendix 25) As a core network node that manages the mobility of terminals, in addition to general MME (Mobility Management Entity) or general SGSN (Serving GPRS Support Node) for general terminals other than predetermined specific terminals, It has a function to provide a predetermined service to the specific terminal, or a specific MME (Customized MME) or a specific SGSN (Customized SGSN) specialized for supporting the specific terminal of a predetermined model. ) A communication system in which the general MME or the general SGSN, or the specific terminal, selects the specific MME or the specific SGSN as a node to which the specific terminal is connected.

1 UE 11 eNodeB 21 General MME 22 Customized MME 31 HSS 41 S-GW (Serving GW) 51 P-GW (PDN GW) 61 Service network 101 UE (MS) 111 NodeB 121 General SGSN 122 Customized SGSN 131 HLR 141 GGSN 161 Service network 171 RNC