0001]
　The present invention relates to communication systems, and more particularly to a communication system for selecting a communication control device from among a plurality of communication control device.
Background technique
[0002]
　With the spread of smartphones and tablet devices, MME that is disposed in the core network (Mobile Management Entity) is of the device application must handle a wide variety of signaling is generated. Further, MTC (Machine Type Communication) providing services, implementation of the event a person are concentrated, or, occurrence of a disaster, characteristic greatly changes depending on time or location communication occurs, difficult signaling increases foreseen ing. In this environment, mobile communication operators, reduce the excessive investment, while reducing the TCO (Total Cost Ownership), must maintain the quality of service.
[0003]
　Accordingly, the MME, the performance of the device, in accordance with the held resource or load status, etc., dynamically mechanism to load balance signaling is required. For example, Non-Patent Document 1, the mechanism of signaling control is disclosed in MME. Further, Patent Document 1, be load balanced perform replacement housing to another MME to eNB (evolved NodeB) units for congestion avoidance MME are described.
CITATION
Patent Literature
[0004]
Patent Document 1: JP-T 2014-533011 Patent Publication
Non-Patent Document
[0005]
Non-Patent Document 1: 3GPP TS 23.401 V13.1.0 (2014-12) 5.3.2 Attach procedure
Summary of the Invention
Problems that the Invention is to Solve
[0006]
　However, Non-Patent Document 1, the information necessary for call processing, including the communication terminal about the MM Context (subscriber data) is generated once a particular MME, when performing call processing related to the communication terminal , it is described to continue to use the MME of information required for call processing has been generated. Therefore, in the call processing, in accordance with the load status of MME, it is impossible to dynamically change the MME to use. In Patent Document 1, since that accommodates replacement to the eNB the unit, or load balancing could not be performed sufficiently in the MME, there is a problem that sometimes may not be appropriately performed.
[0007]
　An object of the present invention is to solve the above problems, a communication system capable of distributing the load of the MME more effectively, the communication control device is to provide a node device and a communication method.
Means for Solving the Problems
[0008]
　Communication system according to a first aspect of the present invention is a communication system comprising a plurality of communication control device, a node device that performs a control process including a call processing related to the communication terminal and the plurality of communication control device, wherein the plurality of communication control device, the form of the shared context groups that share subscriber data of the communication terminal, the node device selects the first communication control unit in the shared context group, the first sends a call processing message to the communication control device, the first communication controller is to perform call processing by using the subscriber data to be shared in the context sharing group.
[0009]
　Communication control apparatus according to the second aspect of the present invention includes a shared context portion to share subscriber data of the communication terminal and another communication control apparatus belonging to the shared context group receives a call processing message from the node device, wherein and it executes the call processing by using the subscriber data that is shared in the context sharing group.
[0010]
　Third node device according to an aspect of the present invention, there is provided a node apparatus for executing control processing including call processing related to the communication terminal and the communication control device, each time to send a call processing message, the communication terminal subscriber data selecting one of the communication control device from among a plurality of communication control devices belonging to the shared context groups that share, and transmits a control processing message including the call processing message to the selected communication control device.
[0011]
　Communication method according to the fourth aspect of the present invention is implemented in a communication system comprising a plurality of communication control device, a node device that performs a control process including a call processing related to the communication terminal and the plurality of communication control device a communication method, the plurality of communication control device forms a shared context groups that share subscriber data of said communication terminal, the node device, selects the first communication control unit in the shared context group and transmits a call processing message to the selected first communication control device, the first communication controller is for executing a call processing by using the subscriber data to be shared in the context sharing group is there.
Effect of the invention
[0012]
　The present invention, in accordance with the load status of MME, the communication system capable of distributing the load of the MME more effectively, the communication control device, it is possible to provide a node device and a communication method.
BRIEF DESCRIPTION OF THE DRAWINGS
[0013]
FIG. 1 is a configuration diagram of a communication system in the first embodiment.
FIG. 2 is a configuration diagram of a communication system according to the second embodiment.
3 is a configuration diagram of a MME according to the second embodiment.
4 is a block diagram of an eNB according to the second embodiment.
5 is a configuration diagram of a S-GW according to the second embodiment.
6 is a configuration diagram of HSS according to the second embodiment.
7 is a diagram showing a flow of notification processing of information about the context sharing group for eNB from the MME according to the second embodiment.
8 is a diagram showing a flow of notification processing of information about the context sharing group for eNB from the MME according to the second embodiment.
9 is a diagram showing a flow of notification processing of information about the context sharing group for eNB from the MME according to the second embodiment.
10 is a diagram showing a flow of notification processing of information about the context sharing group for S-GW from the MME according to the second embodiment.
11 is a diagram showing a flow of notification processing of information about the context sharing group for S-GW from the MME according to the second embodiment.
12 is a diagram showing a flow of notification processing of information about the context sharing group for S-GW from the MME according to the second embodiment.
13 is a diagram showing a flow of notification processing of information about the context sharing group for S-GW from the MME according to the second embodiment.
14 is a diagram showing a flow of notification processing of information about the context sharing group for S-GW from the MME according to the second embodiment.
15 is a diagram showing a flow of notification processing of information about the context sharing group for HSS from MME according to the second embodiment.
16 is a diagram showing a flow of notification processing of information about the context sharing group for HSS from MME according to the second embodiment.
17 is a diagram showing a flow of notification processing of information about the context sharing group for HSS from MME according to the second embodiment.
[Figure 18] eNB according to the second embodiment, a diagram showing a management information S-GW and HSS manages.
19 is a diagram showing a call processing according to the second embodiment.
FIG. 20 is a diagram showing a call processing according to the second embodiment.
[21] When installing additional MME according to the third embodiment, a diagram showing a flow of notification processing of information relating to the shared context group for eNB.
When installing additional MME according to [22] Embodiment 3 is a diagram showing a flow of notification processing of information about the context sharing group for S-GW.
When installing additional MME according to [23] Embodiment 3 is a diagram showing a flow of notification processing of information about the context sharing group for S-GW.
When installing additional MME according to [24] Embodiment 3 is a diagram showing a flow of notification processing of information about the context sharing group for S-GW.
When the removed and reinstalled such MME in FIG. 25 embodiment 3 is a diagram showing a flow of notification processing of information relating to the shared context group for eNB.
[Figure 26] when the removed and reinstalled such MME to the fourth embodiment, a diagram showing a flow of notification processing of information relating to the shared context group for eNB.
In FIG. 27 when removed and reinstalled such MME to the fourth embodiment, a diagram showing a flow of notification processing of information about the context sharing group for S-GW.
[Figure 28] when the removed and reinstalled such MME to the fourth embodiment, a diagram showing a flow of notification processing of information about the context sharing group for S-GW.
[Figure 29] when the removed and reinstalled such MME to the fourth embodiment, a diagram showing a flow of notification processing of information about the context sharing group for S-GW.
[Figure 30] when the removed and reinstalled such MME to the fourth embodiment, a diagram showing a flow of notification processing of information relating to the shared context group for HSS.
[Figure 31] when the removed and reinstalled such MME to the fourth embodiment, a diagram showing a flow of notification processing of information relating to the shared context group for HSS.
[Figure 32] when changing the WF of MME according to the fifth embodiment, a diagram showing a flow of notification processing of information relating to the shared context group for eNB.
[33] is a diagram for explaining an interface relating HSS according to the sixth embodiment.
FIG. 34 is a diagram for explaining an interface relating HSS according to the sixth embodiment.
[FIG. 35] is a diagram showing the flow of storage processing according Context information to the sixth embodiment.
[FIG. 36] is a diagram showing the flow of storage processing according Context information to the sixth embodiment.
[FIG. 37] is a configuration diagram of a communication system according to the seventh embodiment.
DESCRIPTION OF THE INVENTION
[0014]
　(Embodiment 1)
　Hereinafter, with reference to the drawings will be described embodiments of the present invention. First, a configuration example of a communication system according to a first embodiment of the present invention will be described with reference to FIG. Communication system of FIG. 1 includes a communication control device 10 to 12 and node 20. In this figure, the node device 20 indicates that it is connected to the communication control device 10-12, the node device 20 may be connected two or a three or more communication control device.
[0015]
　Communication control devices 10 to 12 may be a computer system that operates by a CPU (Central Processing Unit) executes a program stored in the memory. The communication control devices 10 to 12 may be 3GPP (3rd Generation Partnership Project) are defined in the MME or SGSN (Serving GPRS Support Node).
[0016]
　Node device 20 executes a control processing including call processing related to the communication terminal in the communication control unit 10-12. The call processing, for example, the communication terminal is executed to perform voice communication or data communication, etc., it corresponds to a control processing such as routing in the core network. Node device 20 may be a computer system that operates by a CPU (Central Processing Unit) executes a program stored in the memory. Also, the node device 20, eNB as defined in 3GPP (evolved Node B), RNC (Radio Network Controller), may be a S-GW (Serving Gateway) or HSS (Home Subscriber Server) or the like.
[0017]
　Communication terminal, for example, a cellular phone, may be a tablet terminal or the like having a smartphone or communication function. The communication terminal may be a computer device such as a personal computer.
[0018]
　Communication control devices 10 to 12 form a shared context groups that share subscriber data of the communication terminal. And to share the subscriber data, the subscriber data communication control device 10 can be utilized, also the communication control apparatus 11 and 12 is that it can be utilized. For example, if there is a server apparatus that manages subscriber data, the communication control devices 10 to 12 may acquire the appropriate subscriber data from the server device. Or, between each of the communication control apparatus by sending and receiving subscriber data may obtain subscriber data held in the other communication control device.
[0019]
　Node device 20, to perform call processing or control processing regarding the communication terminal, selects one of the communication control device in the shared context group. Furthermore, the node device 20 to the selected communication control unit transmits a call processing message or a control message. Call processing message may for example be a control message defined in 3GPP. In 3GPP, for example, Attach Request message or the like transmitted when the power of the communication terminal is transitioned to the ON state, a variety of control messages are defined. Node apparatus, the information notified from the communication control device (e.g., a congestion situation and, capacity, subscriber data (shared context groups sharing between the communication control apparatus of the communication control device of each communication control device) based on the information, etc.), it selects the communication control device.
[0020]
　Communication control device selected in the node device 20, that is, a communication control device which receives the transmitted call processing message or a control message, from the node device 20, the call processing by using the subscriber data to be shared in the context sharing group or it executes a control process. For example, communication control unit selects the node device 20, when holding the subscriber data of the communication terminal to be call processing in the own device, the call processing by using the subscriber data held, or executes a control process. Node communication control apparatus selects the device 20, when not hold the subscriber data of the communication terminal to be call processing in the own device, retrieving subscriber data managed by the server device well, it may acquire the subscriber data from another communication control device.
[0021]
　As described above, by using the communication system of FIG. 1, a communication control device which belongs to the shared context group can share the subscriber data of the communication terminal. Therefore, the node device, selecting one of the communication control device belonging to the shared context group, it is possible to perform call processing or control processing in the communication terminal.
[0022]
　From this, the node device 20 can dynamically change the communication control apparatus for performing communication in performing the call processing or control processing. Therefore, the node device 20, for example, depending on the load status of the communication control device, it is also possible to change the communication control device. As a result, the node device 20 can control the load sharing in a plurality of communication control device. Also, the node device, the communication control device to share subscriber data, it is possible to distribute the call processing message or a control message, the subscriber unit. Therefore, as compared with the case of dispersing a message to the node device unit, the node device can be made to the communication control device, a better dispersion of the messages in a minute unit.
[0023]
　(Second Embodiment)
　Subsequently, a configuration example of a communication system according to Embodiment 2 of the present invention will be described with reference to FIG. Communication system of FIG. 2 is constituted by a device as defined in 3GPP. Communication system of FIG. 2 includes a MME30 ~ 60, eNB70, HSS80, S-GW90, P-GW (Packet Data Network-Gateway) 100 and UE (User Equipment) 110. MME 30 ~ 60 correspond to the communication control device in FIG. eNB 70, HSS80 and S-GW90 corresponds to the node device of FIG. UE110 corresponds to the communication terminal.
[0024]
　Further, MME may be replaced by the SGSN are defined in the 3GPP, eNB may be replaced by RNC as specified in 3GPP.
[0025]
　In this figure, MME 30 and MME40 is, belongs to the shared context group A, MME50 and MME60 have shown to belong to the shared context group B. Furthermore, MME 30 ~ 60 may belong to MME group is a different group from the shared context group. MME Group is a group of MME belongs candidate to generate a Context information at the beginning is eNB70. Context information corresponds to the subscriber data described in FIG. That, MME group may include a plurality of contexts share group. Or, and the MME which belong to the MME group, the MME which belong to the shared context group may be the same.
[0026]
　Generally, eNB 70, when you decide to generate a Context information about the UE110 in First MME 30, select all MME 30 in call processing later. In contrast, in each embodiment of the present invention, eNB 70, even if it is generating the Context information in First MME 30, the call processing after it is possible to select the MME 30 or MME 40. Further, HSS80 and S-GW90 also may perform call processing by selecting different MME is the first Context information is generated MME.
[0027]
　Next, an example of the configuration of the MME30 according to a second embodiment of the present invention will be described with reference to FIG. MME 40 ~ 60 are substantially the same configuration as the MME 30, a detailed description thereof will be omitted.
[0028]
　MME30 ha, Diameter communication unit 31, S1AP (S1 Application) communication portion 32, GTP (General packet radio service Tunneling Protocol) -C communication unit 33, Context total of portion 34, Context Memory portion 35 and び MME call processing section 36 wo have shi te IRU. Diameter wa communication unit 31, HSS80 と の の イ nn between TAFMER S Factory ー と shi te ru su ra me cry with い. S1AP wa communication unit 32, eNB70 と の の イ nn between TAFMER S Factory ー と shi te ru su ra me cry with い. GTP-C ha communication unit 33, S-GW90 と の の イ nn between TAFMER S Factory ー と shi te ru su ra me cry with い.
[0029]
　Context sharing unit 34 acquires Context information UE110 to be call processing. For example, in the server device or the like, if the Context information generated in MME context shared group A is managed, Context sharing unit 34 also acquires the Context information UE110 to be the call processing from the server device good. Or, Context sharing unit 34, may be obtained from MME40 belonging to Context information UE110 to be call processing context 拒有 group A.
[0030]
　Context storage unit 35 stores a Context information generated in Context information and MME30 the Context sharing unit 34 has been acquired. Context storage unit 35 is, for example, may be a memory in the MME 30, may be an external memory device or the like which is attached to the MME 30. Or, HSS80 the Context information by accessing optionally multiple MME holds Context information may be shared among multiple MME.
[0031]
　Furthermore, Context storage unit 35 stores information about the context sharing group which MME30 belongs. Here, Context storage unit 35 holds information indicating the context sharing group A. Context storage unit 35 is, for example, may be a memory in the MME 30, may be an external memory device or the like which is attached to the MME 30. Or, HSS80 information that Context storage unit 35 holds by accessing optionally multiple MME holds the Context storage unit 35 may be shared between multiple MME.
[0032]
　MME call processing unit 36 ​​uses the information indicating the Context information and context sharing group A is stored in the Context storage unit 35, performs call processing. MME call processing unit 36 ​​via the Diameter communication unit 31, S1AP communication unit 32 or GTP-C communication unit 33 transmits and receives during a message about the call processing with the eNB 70, HSS80 or S-GW90.
[0033]
　Next, an example of the configuration of the eNB70 according to a second embodiment of the present invention will be described with reference to FIG. eNB70 has S1AP communication unit 71, S1AP call processing section 72, RRC (Radio Resource Control) processing section 73, a radio processing section 74, GTP-U communication unit 75, GTP-U processing unit 76 and the Context storage unit 77 ing.
[0034]
　S1AP communication unit 71 is used as an interface when communicating with MME 30 ~ 60. S1AP call processing unit 72 uses the information stored in the Context storage unit 77, executes a call process between the MME 30 ~ 60.
[0035]
　S1AP call processing section 72 transmits and receives messages about call process between the MME 30 ~ 60 through the S1AP communication unit 71. Further, S1AP call processing unit 72 uses the information stored in the Context storage unit 77, selects the MME to perform the call processing.
[0036]
　RRC (Radio Resource Control) processing section 73 performs processing related to the RRC protocol used between the UE 110. For example, RRC processing unit 73 may perform a process of managing the connection state between the UE 110. The radio processing section 74 is used as an interface when the UE110 and wireless communications.
[0037]
　GTP-U communication unit 75 is used as an interface when communicating with S-GW90. GTP-U processing unit 76 via the GTP-U communication unit 75 performs transmission and reception of user data between the S-GW90.
[0038]
　Context storage unit 77 stores information about the context sharing group transmitted from MME 30 ~ 60. For example, Context storage unit 77, and context sharing group are stored in association with MME belonging to the group. Furthermore, Context storage unit 77, WF to be referred to when selecting the respective MME a (Weight Factor) may be stored in association with the MME.
[0039]
　Next, an example of the configuration of the S-GW90 according to the second embodiment of the present invention will be described with reference to FIG. S-GW90 has a GTP-C communication unit 91, GTP-U communication unit 92, GTP-C processing unit 93, Context storage unit 94 and the GTP-U processing unit 95.
[0040]
　GTP-C communication unit 91 is used as an interface when communicating with MME 30 ~ 60. GTP-U communication unit 92 is used as an interface when communicating with eNB 70.
[0041]
　GTP-C processing unit 93 sends and receives a message about the call process between the MME 30 ~ 60 via the GTP-C communication unit 91. Moreover, GTP-C processing unit 93 uses the information stored in the Context storage unit 94, selects the MME to perform the call processing. GTP-U processing unit 95 transmits and receives user data between the eNB70 via GTP-U communication unit 92.
[0042]
　Context storage unit 94 stores information about the context sharing group transmitted from MME 30 ~ 60. For example, Context storage unit 77, and context sharing group are stored in association with MME belonging to the group. Furthermore, the WF reference in selecting the respective MME may be stored in association with the MME.
[0043]
　Next, an example of the configuration of the HSS80 according to a second embodiment of the present invention will be described with reference to FIG. HSS80 is, the Diameter communication unit 81, and a subscriber information processing unit 82 and the subscriber information storage unit 83. Diameter communication unit 81 is used as an interface to communicate with the MME 30 ~ 60.
[0044]
　Subscriber information storage unit 83 stores information about the context sharing group transmitted from MME 30 ~ 60. For example, subscriber information storage unit 83, and context sharing group are stored in association with MME belonging to the group. Further subscriber information storage unit 83, a WF referred to when selecting the respective MME may be stored in association with the MME.
[0045]
　Subscriber information processing unit 82 transmits and receives a message about the call process between the MME 30 ~ 60 via the Diameter communication unit 81. Also, the subscriber information processing unit 82 uses the information stored in the subscriber information storage unit 83, selects the MME to perform the call processing.
[0046]
　Subsequently, the flow of notification processing of information about the context sharing group for eNB from such MME to a second embodiment of the present invention will be described with reference to FIG. First, eNB 70, in order to establish the S1 connection for all MME in MME group, transmits the S1 SETUP REQUEST message (S11).
[0047]
　Next, each of the MME, as a response to S1 SETUP REQUEST message, sends the S1 SETUP RESPONSE message to the eNB 70 (S12). Each MME is the S1 SETUP RESPONSE message, the shared context group to which the self apparatus belongs, sets the GUMMEI (Globally Unique MME Identifier) ​​and WF (Weight Factor). GUMMEI is identification information for uniquely identifying the MME. WF is priority information for use in selecting an MME for eNB70 performs call processing. For example, eNB 70 is to increase the number of times the value of WF selects a high MME, may reduce the number of times the value of WF selects a low MME. eNB70 holds information set in the S1 SETUP RESPONSE message.
[0048]
　Then, the notification process information about the context sharing group according to a second embodiment of the present invention, a description is given of the flow of different notification processing of FIG. 7 with reference to FIG. First, MME 30 and MME40 are both to practice the representative selection process of determining whether a representative MME (S20). Representative selection process is executed between a plurality of MME belonging to the same context sharing group. For example, representative MME, may be selected MME identification information young number is set, the other criteria representative MME may be selected. Here, the MME30 has been selected as the representative MME. Further, in a representative selection process, the MME40 like not representative MME, to the representative MME, may transmit information such as GUMMEI and WF of the device itself.
[0049]
　Then, eNB 70 in order to establish the S1 connection for all MME in MME group, transmits the S1 SETUP REQUEST message (S21). In FIG. 8, eNB 70 is is shown that is sending the S1 SETUP REQUEST message to MME30 and MME 40, when the S1 SETUP REQUEST message to all MME in MME group is transmitted to.
[0050]
　Next, a representative MME MME 30, to the eNB 70, the shared context group, GUMMEI all MME which belong to the shared context group, and transmits the S1 SETUP RESPONSE message set the WF of all MME (S22) . MME40 not representative MME, for the establishment of the S1 connection, sends the S1 SETUP RESPONSE message to the eNB 70. The S1 SETUP RESPONSE message MME40 sends information about the shared context group may not be set.
[0051]
　Subsequently, with reference to FIG. 9, the notification processing of information about the context sharing group according to a second embodiment of the present invention, a description is given of the flow of different notification process and FIGS. In this figure, EMS (Element Management System) device, with respect to eNB 70, the shared context group, GUMMEI all MME which belong to the shared context group, and registers the information about the WF for all MME (S31).
[0052]
　Subsequently, with reference to FIG. 10, description will be given of a flow of notification processing of information about the context sharing group for S-GW from the MME according to the second embodiment of the present invention. First, each of the MME, the GTP Echo REQUEST message set for the shared context group and WF own device belongs sends to the S-GW90 (S41). S-GW90, using the source IP address of the GTP Echo REQUEST message, identifies the MME. S-GW90 holds information set in the GTP Echo REQUEST message.
[0053]
　Next, S-GW90 transmits a GTP Echo RESPONSE message to each of the MME (S42). Generally, GTP Echo REQUEST message and GTP Echo RESPONSE message is used to confirm whether or not a failure has occurred between the MME and the S-GW.
[0054]
　Subsequently, with reference to FIG. 11, the notification processing of information about the context sharing group according to a second embodiment of the present invention, a description is given of the flow of different notification process and FIG. In this figure, S-GW90 transmits a GTP Echo REQUEST message to each MME (S51). Next, each of the MME, the GTP Echo RESPONSE message set for the shared context group and WF own device belongs sends to the S-GW90 (S52).
[0055]
　Subsequently, with reference to FIG. 12, the notification process of the shared context group information according to the second embodiment of the present invention, a description is given of the flow of different notification process and FIGS.
[0056]
　First, MME 30 and MME40 are both to practice the representative selection process of determining whether a representative MME (S60). Representative selection process is executed between a plurality of MME belonging to the same context sharing group. Here, the MME30 has been selected as the representative MME.
[0057]
　Next, a representative MME MME 30 transmits, to the S-GW90, the GTP Echo REQUEST message set the WF of all MME which belong to the shared context groups and context sharing group (S61). MME30 may set in association with the IP address and the WF is identification information MME belonging to the shared context group. MME40 not representative MME transmits a normal GTP Echo REQUEST message to the S-GW90 (S62).
[0058]
　Next, S-GW90 as a response message to the GTP Echo REQUEST message, transmits a GTP Echo RESPONSE message to each of the MME (S63).
[0059]
　Subsequently, with reference to FIG. 13, the notification process of the shared context group information according to the second embodiment of the present invention, a description is given of the flow of different notification process and FIGS. 10 to 12. First, MME 30 and MME40 as in step S60 in FIG. 12, implementing a representative selection process (S70). Next, S-GW90 transmits a GTP Echo REQUEST message to all MME in MME group (S71).
[0060]
　Next, a representative MME MME 30 may, GTP Echo response message to REQUEST message, a GTP Echo REQUEST message set the WF of all MME which belong to the shared context groups and context sharing group transmits to the S-GW90 (S72) .
[0061]
　MME40 not representative MME, as a response message to the GTP Echo REQUEST message, transmits a normal GTP Echo RESPONSE message to the S-GW90 (S73).
[0062]
　Subsequently, with reference to FIG. 14, the notification process of the shared context group information according to the second embodiment of the present invention, a description is given of the flow of different notification process and FIGS. 10 to 13. In this figure, EMS (Element Management System) device, with respect to S-GW90, shared context group, registers the information about the WF of all MME which belong to the shared context group (S81).
[0063]
　Subsequently, the flow of notification processing the shared context group information for HSS80 from the MME according to the second embodiment of the present invention will be described with reference to FIG. 15. First, each of the MME establishes an SCTP (Stream Control Transmission Protocol) Connection between the HSS80 (S90).
[0064]
　Next, each of the MME sends the shared context group to which the self apparatus belongs, the Update Context Shared Group REQUEST message set the Origin-Host and WF to HSS80 (S91). Origin-Host is information for identifying the MME. HSS80 holds information set in the Update Context Shared Group REQUEST message.
[0065]
　Then, HSS80 as a response to the Update Context Shared Group REQUEST message, sends the Update Context Shared Group ANSWER message to each of the MME (S92).
[0066]
　Subsequently, with reference to FIG. 16, the notification process of the shared context group information according to the second embodiment of the present invention, a description is given of the flow of different notification process and Figure 15. First, MME 30 and MME40 as in step S90 of FIG. 15, to establish the SCTP Connection (S100). Next, MME 30 and MME40 are both to practice the representative selection process of determining whether a representative MME (S101). Representative selection process is executed between a plurality of MME belonging to the same context sharing group. Here, the MME30 has been selected as the representative MME.
[0067]
　Next, a representative MME MME 30 may transmit the shared context group, the Update Context Shared Group REQUEST message set the WF of all MME belonging to Origin-Host and shared context group of all MME which belong to the shared context group to HSS80 to (S102). Then, HSS80 as a response to the Update Context Shared Group REQUEST message, sends the Update Context Shared Group ANSWER message to MME 30 (S103).
[0068]
　Subsequently, with reference to FIG. 17, the notification process of the shared context group information according to the second embodiment of the present invention, a description is given of the flow of different notification processing as in FIG. 15 and FIG. 16. In this figure, EMS (Element Management System) device, relative HSS80, shared context group, registers the information about the WF of all MME which belong to the shared context group (S 111).
[0069]
　In FIGS. 7 to 17, eNB 70 receives the information about the context sharing group, S-GW90 and HSS80 manages information about the context sharing group as shown in Figure 18. Management information shown in FIG. 18 is managed in association with the shared context group, the MME which belong to the shared context group. Moreover, it is managed in association with each MME also the value of WF was set to MME. The context sharing group A, belong MME30 ~ MME # N, the shared context group B, MME50 and MME60 belongs. Further, for example, MME 30 belongs to the shared context group A, the value of WF is shown to be 50.
[0070]
　Also, information identifying the MME may be different depending on the type of node. For example, eNB uses the GUMMEI as the identification information of the MME, SGW uses the IP address as the identification information of the MME, HSS may use Origin-Host.
[0071]
　Subsequently, with reference to FIGS. 19 and 20, a description is given of the flow of call processing according to the second embodiment of the present invention. First, UE 110 includes a power button is pressed by the user, when the device is activated, NAS (Non-Access Stratum): the Attach REQUEST message transmitted to the eNB 70 (S121). UE110 is, NAS: to Attach REQUEST message, to set the GUTI (Globally Unique Temporary Identifier). GUTI is information composed of GUMMEI and M-TMSI (Temporary Mobile Subscriber Identity). GUTI is a temporary identification information used to uniquely identify the UE.
[0072]
　Then, eNB 70 may, NAS: Attach performs processing for selecting a MME to send the REQUEST message (S122). eNB70, in the processing of selecting the MME, NAS: Attach the GUTI set in the REQUEST message, identifies the GUMMEI. GUMMEI identified from GUTI, in previous Attach process, MME to produce a Context information about the UE110 or shows eNB selects MME. eNB70 may be from the management information shown in FIG. 18, it identifies the shared context group the MME belongs identified by GUMMEI. eNB70, from the MME belonging to the specified context sharing group, to select the MME according to the WF. In this figure, eNB 70 is to have selected the MME 30.
[0073]
　Then, eNB 70 is to the selected MME, NAS: Attach REQUEST / S1AP: Initial transmits a UE message (S123). Next, MME 30 an authentication vector for UE110 (Authentication Vector: AV) in order to get the, selects the Authentication Information REQUEST message to HSS80 (S124). Then, HSS80 performs processing of selecting the MME to send the Authentication Information ANSWER message set the AV (S125). HSS80, using the management information shown in FIG. 18, identifies the shared context group including MME30 which has transmitted the Authentication Information REQUEST message. HSS80, from the MME belonging to the specified context sharing group, to select the MME according to the WF. In this figure, HSS80 shall be selected the MME # N. MME # N shall be included in the same context sharing group A and MME 30.
[0074]
　Then, HSS80 is, Authentication and Information ANSWER message to the selected MME # N (S126). Thus, HSS80 is, Authentication Information to REQUEST message and MME30 which has transmitted the different MME # N, it is possible to transmit the Authentication Information ANSWER message. Next, MME # N is the eNB 70, sends the Authentication REQUEST message (S127).
[0075]
　Turning to FIG. 20, MME 30, to generate a session between the S-GW90, a the Create Session REQUEST message transmitted to the S-GW90 (S128). Next, S-GW90 performs processing of selecting the MME to send the the Create Session RESPONSE message (S129). S-GW90, using the management information of FIG. 18, identifies the shared context group including MME30 that transmitted the the Create Session REQUEST message. S-GW90, from the MME belonging to the specified shared context group, selects the MME according WF. In this figure, S-GW90 shall be selected the MME # N.
[0076]
　Next, S-GW90 is a the Create Session RESPONSE message to the selected MME # N (S130). Thus, S-GW90 is, the Create the Session REQUEST message differs from MME30 which has transmitted the MME # N, can transmit the Create Session RESPONSE message.
[0077]
　Then, MME # N is, NAS: Attach Accept / S1AP: the Initial Context Setup Request message to send to the eNB70 (S131). In step S131, eNB 70 may, NAS: Attach Request NAS message from MME30 different MME # N that transmitted: Attach can receive Accept message.
[0078]
　Then, eNB 70 may, NAS: the Attach Accept message and transmits to the UE 110 (S132). Then, eNB 70, at step S131, S1AP: Initial Context Setup receives the REQUEST message, S1AP: Initial Context Setup RESPONSE performs processing for selecting a destination to become MME message (S133). Here, eNB 70 is to have selected the MME # N from among the shared context group A. Then, eNB 70 may, S1AP: the Initial Context Setup RESPONSE message to the selected MME # N. Thus, eNB 70 may, NAS transmitted in step S123: Attach S1AP to MME30 different MME # N which is the destination of the REQUEST message: Initial Context Setup RESPONSE message can be transmitted.
[0079]
　Next, MME # N is a Modify Bearer REQUEST message transmitted to the S-GW90 (S135). Next, S-GW90 in order to select the MME to send a Modify Bearer RESPONSE message, performs the same process as in step S129 (S136). Here, S-GW90 is that selects the MME 30. Next, S-GW90 is a Modify Bearer RESPONSE message to the MME30 selected.
[0080]
　As described above, MME can share with other MME in the same context sharing group, the Context information about the UE. Therefore, eNB, the S-GW and HSS, as call processing message has been transmitted to any MME in a context share group can continue call processing for the UE.
[0081]
　Further, eNB is a node device near the MME, S-GW and HSS may be in performing call processing UE, and transmits a call processing message to any MME in a context share group. Therefore, eNB, S-GW and HSS can distribute the load of call processing to be executed in the MME.
[0082]
　(Third Embodiment)
　Subsequently, with reference to FIG. 21, description will be given of a flow of notification processing the shared context group information for eNB from the MME in case of installing additional MME according to the third embodiment of the present invention.
[0083]
　First, after increasing MME, other MME context shared group extension MME belongs transmits an S1 SETUP request message for requesting the start of the S1 SETUP message to the eNB 70 (S151). In this view, additional MME is, belongs to the shared context group A, MME 30 in the shared context group A is sending S1 SETUP request message to the eNB 70.
[0084]
　Thereafter executes the processing of FIG. 7 or FIG. 8, eNB 70 receives information about the shared context group set to S1 SETUP RESPONSE message.
[0085]
　S1 MME to send a SETUP request message may be, for example, a MME of extension MME is selected as a representative before belonging to the shared context group, an MME information about additional MME is input from the administrator or the like it may be. Further, the expansion MME, representative selection process between the existing MME is executed, if the extension MME is selected as the representative MME, expansion MME may send the S1 SETUP request message.
[0086]
　Further, instead of MME sends S1 SETUP request message, as shown in FIG. 9, EMS devices may register information on the extension MME to eNB 70. eNB70, when information about the extension MME is registered, as shown in FIGS. 7 and 8 may transmit the S1 SETUP REQUEST message to only any MME or expansion MME.
[0087]
　Subsequently, with reference to FIG. 22, description will be given of a flow of notification processing the shared context group information for S-GW from the MME in case of installing additional MME according to the third embodiment of the present invention. First, expansion the MME, a GTP Echo REQUEST message set for the shared context group and WF own device belongs sends to the S-GW90 (S161).
[0088]
　S-GW90 manages the information shown in FIG. 18, by receiving the GTP Echo REQUEST message, updates the management information by adding information about the extension MME to the information shown in FIG. 18 (S162). Next, S-GW90 is to expansion MME, transmits the GTP Echo RESPONSE message (S163).
[0089]
　Subsequently, with reference to FIG. 23, the flow of notification processing the shared context group information for S-GW from the MME in case of installing additional MME according to the third embodiment of the present invention, the flow of process different from that of FIG. 22 explain.
[0090]
　First, the MME is added, in the context shared in a group expansion MME belongs, selection processing of the representative MME is executed (S171). Here, the MME # N is selected as the representative MME. Next, the representative MME transmits, to the S-GW90, the GTP Echo REQUEST message set the WF of all MME which belong to the shared context groups and context sharing group (S172).
[0091]
　Step S173 and S174 are omitted detailed to those at steps S162 and S163 in FIG. 22. However, in step S174, S-GW90 is to the representative MME, transmits the GTP Echo REQUEST message.
[0092]
　Subsequently, with reference to FIG. 24, the flow of notification processing the shared context group information for S-GW from the MME in case of installing additional MME according to the third embodiment of the present invention, different processing from that in FIG. 22 and FIG. 23 description will be given of the flow.
[0093]
　Step S181 is a detailed description thereof will be omitted because it is similar to step S171 of FIG. 23. Next, S-GW90 transmits a GTP Echo REQUEST message to all MME in MME group (S182). Next, the representative MME transmits, to the S-GW90, the GTP Echo RESPONSE message set the WF of all MME which belong to the shared context groups and context sharing group (S183). Here, for the MME other than the representative MME, a GTP Echo RESPONSE message is not set information such as the shared context group may be transmitted to the S-GW90. Step S184 is a detailed description thereof will be omitted because it is similar to step S173 of FIG. 23.
[0094]
　Also, instead of using the GTP Echo REQUEST message and GTP Echo RESPONSE message as shown in FIGS. 22 to 24, EMS device as in FIG. 14 may register information on the extension MME to S-GW90. Also, instead of using the GTP Echo REQUEST message and GTP Echo RESPONSE message as shown in FIGS. 22 to 24, now with a new message that is not defined in 3GPP, information about the expansion MME it is transmitted to the S-GW90 it may be.
[0095]
　Next, a description will be given notification processing flow of the shared context group information for HSS from expansion MME according to the third embodiment of the present invention. If the MME is added, as in FIGS. 15 and 16, SCTP Connection is established between the expansion MME and HSS80. After the SCTP Connection is established, similar to FIGS. 15 and 16, using the Update Context Shared Group REQUEST message, the HSS, notifying information such as the shared context Group on expansion have been MME.
[0096]
　As described above, when installing additional MME, eNB70, S-GW90 and HSS80 grasps that the MME has been added, it is possible to update the management information. eNB70, S-GW90 and HSS80 by selecting the MME which is added in accordance with the value of WF, it is possible to perform call processing by using the expansion has been MME. That, eNB70, S-GW90 and HSS80 can dynamically transmits a call processing message to the additional been MME.
[0097]
　(Embodiment 4)
　Subsequently, when the MME according to a fourth embodiment of the present invention was removed and reinstalled in the flow will be described information update processing eNB70 with reference to FIG. First, MME as a degrowth target, to start the degrowth processing (S191). Degrowth process the MME, for example, may be possible such that the or MME to the power of the MME in the OFF state to the shutdown state.
[0098]
　When MME performs degrowth process, S1AP connection between the degrowth MME and eNB70 are disconnected. In this case, eNB 70 detects that the connection S1AP is disconnected (S192). Then, eNB 70 from the management information described in FIG. 18, so as to remove information about degrowth MME, updates the management information (S193). At this time, if MME belonging to the shared context group was only MME that is degrowth, eNB 70 may also cut the RRC connection.
[0099]
　In this view, there has been described a case where degrowth the MME, the process of the figure, may also be applied in the event of a failure the MME.
[0100]
　Subsequently, with reference to FIG. 26, in the case where removed and reinstalled the MME according to a fourth embodiment of the present invention, the flow of information update process eNB 70, a description is given of the flow of different information update processing as in FIG 25. MME to be degrowth subject before starting the degrowth process, it sends the MME Shutdown Indication message to the eNB 70 (S201). MME to be degrowth subject to signal to initiate a degrowth process, sends the MME Shutdown Indication message to the eNB 70. Further, MME Shutdown Indication message may be a message of different names.
[0101]
　MME as a degrowth subject to MME Shutdown Indication message, the shared context group, may be set GUMMEI and shutdown time. shutdown time, for example, time MME as a degrowth subject starts degrowth process, or, MME after what seconds is information indicating whether such starts degrowth process. Thus, MME to be degrowth target, by sending a shutdown time to eNB 70, for example, it is possible to prevent call loss caused by the MME to set reduced suddenly. For example, eNB 70 that has received the MME Shutdown Indication message, call processing between the MME to be degrowth target priority may be given.
[0102]
　Subsequently, with reference to FIG. 27, in the case where the MME according to a fourth embodiment of the present invention were removed and reinstalled, a description is given of the flow of information update processing of S-GW90. S-GW90, to check that you are connected correctly with MME, periodically sends a GTP Echo REQUEST message to the MME (S211). However, if the MME is degrowth, S-GW90 will not receive a response signal to the transmitted GTP Echo REQUEST message. Therefore, S-GW90 repeats the transmission of GTP Echo REQUEST message (S212).
[0103]
　Next, S-GW90 determines, if it does not receive the GTP Echo be repeated the number of times the predetermined sending the REQUEST message response message, the MME is degrowth, or that a failure has occurred in the MME. In this case, S-GW90 updates the management information in FIG. 18, degrowth been or disorder deletes the entry of MME it is judged to have occurred (S213).
[0104]
　Subsequently, with reference to FIG. 28, in the case where removed and reinstalled the MME according to a fourth embodiment of the present invention, the flow of information update processing of S-GW90, a description is given of the flow of processing that is different from that in FIG 27. MME of degrowth subject before starting the degrowth, a GTP Echo REQUEST message set to degrowth transmits to S-GW90 (S221). MME of degrowth subject, GTP in Echo REQUEST message, for example, may be set degrowth flags indicating that degrowth target MME is set shared context group and reduced belong as a new IE (Information Element) .
[0105]
　Next, S-GW90 receives the GTP Echo REQUEST message in step S221, updates the management information in FIG. 18, deletes the entry of the MME is degrowth (S222). Next, S-GW90 is to the MME of degrowth target transmits a GTP Echo RESPONSE message (S223).
[0106]
　Subsequently, with reference to FIG. 29, in the case where the MME according to a fourth embodiment of the present invention were removed and reinstalled, the flow of information update processing of S-GW90, a description is given of the flow of processing that is different from that in FIG. 27 and FIG. 28 . In Figure 28, the MME of degrowth subject to S-GW90, had told to set reduced by transmitting the GTP Echo REQUEST message, in FIG. 29, the MME Shutdown Indication message to the S-GW90 tell that to set reduction by sending. MME of degrowth subject to MME Shutdown Indication message, may be set a context shared group and shutdown time. shutdown time, for example, time MME as a degrowth subject starts degrowth process, or, MME after what seconds is information indicating whether such starts degrowth process.
[0107]
　Next, S-GW90 receives the MME Shutdown Indication message in step S221, updates the management information in FIG. 18, deletes the entry of the MME is degrowth (S232). Here, S-GW90 ends the processing without transmitting a response message to MME Shutdown Indication message.
[0108]
　Also, instead of using the GTP Echo REQUEST message and MME Shutdown Indication message as in FIGS. 27 to 29, EMS device as in FIG. 14 may register information on degrowth MME to S-GW90. Also, instead of using the GTP Echo REQUEST message and MME Shutdown Indication message as in FIGS. 27 to 29, now with a new message that is not defined in 3GPP, information about degrowth MME is sent to the S-GW90 it may be.
[0109]
　Subsequently, with reference to FIG. 30, in the case where the MME according to a fourth embodiment of the present invention were removed and reinstalled, a description is given of the flow of information update process HSS80. First, MME as a degrowth target, to start the degrowth processing (S241). Degrowth process the MME, for example, may be possible such that the or MME to the power of the MME in the OFF state to the shutdown state.
[0110]
　When MME performs degrowth process, SCTP connection between the degrowth MME and HSS80 are disconnected. At this time, HSS80 detects that the SCTP connection is disconnected (S242). Then, HSS80 from the management information described in FIG. 18, by deleting the information about degrowth MME, updates the management information (S243).
[0111]
　Subsequently, with reference to FIG. 31, in the case where removed and reinstalled the MME according to a fourth embodiment of the present invention, the flow of information update process HSS80, a description is given of the flow of different information update processing as in FIG 30. MME to be degrowth subject before starting the degrowth process, it sends the MME Shutdown Indication message to HSS80 (S252). MME to be degrowth subject to signal to initiate a degrowth process, sends the MME Shutdown Indication message to HSS80. Further, MME Shutdown Indication message may be a message of different names.
[0112]
　MME as a degrowth subject to MME Shutdown Indication message, the shared context group, may set the Origin-Host and shutdown time. shutdown time, for example, time MME as a degrowth subject starts degrowth process, or, MME after what seconds is information indicating whether such starts degrowth process. Thus, MME to be degrowth target, by sending a shutdown time to eNB 70, for example, it is possible to prevent call loss caused by the MME to set reduced suddenly. For example, HSS80 having received the MME Shutdown Indication message, call processing between the MME to be degrowth target priority may be given.
[0113]
　Next, MME of degrowth subject starts Gen設 processed at the timings shown in shutdown time (S252). Further, HSS80 updates the management information so as to remove the MME of degrowth subject from the entry of the management information shown in FIG. 18.
[0114]
　As described above, when removed and reinstalled the MME, eNB70, S-GW90 and HSS80 grasps that the MME has been reduced set, it is possible to update the management information. eNB70, S-GW90 and HSS80 is, after updating the management information, is no longer able to send the call processing message to degrowth been MME.
[0115]
　Usually, when degrowth the MME, the MME of degrowth target, it is necessary to transfer the Context information for each UE the MME holds to another MME. In such a case, in general, MME is allowed to Detach the UE, UE to be executed again Attach process to produce a Context information of the UE in the new MME. Here, if allowed to Detach the communicating UE, there is a problem that UE communication during communication from being temporarily interrupted.
[0116]
　In contrast, the communication system in the fourth embodiment, each MME can share the Context information stored in an external server device or the like. Therefore, in the case of degrowth the MME also not necessary to Detach the UE. From this, by using a communication system in the fourth embodiment, without interrupting the communication of the UE, it is possible to degrowth the MME.
[0117]
　Also, if the Context information is stored in the server apparatus or the like, when the MME is degrowth also, Context information will not disappear. Therefore, MME the remaining can continue the call processing by using the Context information stored in the server apparatus or the like instead of degrowth been MME.
[0118]
　(Embodiment 5)
　Subsequently, MME according to the fifth embodiment of the present invention will be described flow of information update processing HSS80 in case of scale-up or scale-down with reference to Figure 32. The MME scale-up, is to improve the performance of MME, and the scaling down of the MME, is to reduce the performance of the MME. If the MME is scaled up, it is possible to increase the call throughput of MME obtained by scale-up. In this case, MME a scaled-up by increasing the value of WF, increasing the chance of the own device is selected in the vicinity of the node device. If the MME is scaled down, MME a scaled down, to lower the value of WF, reduces the chance that the device itself is selected in the vicinity of the node device. In FIG. 32, a description is given of the flow of processing for notifying the WF has been changed by scaling up or scaling down the eNB 70.
[0119]
　First, MME # N belonging to the context sharing group A it is assumed that the scale up or scale down (S261). Next, MME # N is the eNB 70, sends the MME Configuration Update message (S262). MME # N is the MME Configuration Update message, the shared context group, setting the value of GUMMEI and updated WF.
[0120]
　Then, eNB 70, among the management information shown in FIG. 18, updates the value of WF of MME # N (S263). Then, eNB 70 transmits an MME Configuration Update Acknowledge message to the MME # N.
[0121]
　Further, in this figure, the MME # N changing the WF has been described to transmit the MME Configuration Update message to the eNB 70, the representative MME in a context shared group A sends a MME Configuration Update message to the eNB 70 it may be. In this case, the representative MME includes a shared context group, of all the shared context group GUMMEI and WF of MME may set the MME Configuration Update message. Or, representative MME includes a shared context group, the GUMMEI and WF after updating the MME updating the WF may be set to MME Configuration Update message.
[0122]
　Further, as shown in FIG. 9, EMS devices may register information on WF after updating MME # N to eNB 70.
[0123]
　Subsequently, MME will be described flow of information update processing of S-GW90 when a scaled up or scaled down. If the MME has scaled up or scaled down, similar to the process in FIGS. 10 to 13, it sets the WF updated to GTP Echo REQUEST messages or GTP Echo RESPONSE message. Or, as in the processing in FIG. 14, EMS devices may register information on WF after updating the MME which was scaled up or scaled down to S-GW90.
[0124]
　Subsequently, MME will be described flow of information update processing HSS80 in case of scale-up or scale-down. If the MME has scaled up or scaled down, similar to the process in FIGS. 15 and 16, MME sets the WF updated to Update Context Shared Group REQUEST message. Or, as in the processing in FIG. 17, EMS devices may register information on WF after updating the MME which was scaled up or scaled down to HSS80.
[0125]
　As described above, by using the communication system according to a fifth embodiment of the present invention, in accordance with a change in performance of the MME, there can control the load sharing dynamically MME.
[0126]
　In addition, change of WF may be performed when the congestion occurs in the MME. For example, if congestion occurs in MME, it may change the WF of MME congestion occurs to a lower value. By this way, the periphery of the node device will be the opportunity to select the MME is reduced, it is possible to avoid congestion.
[0127]
　(Embodiment 6)
　Next, with reference to FIGS. 33 and 34, MME in a context shared group in order to share the Context information, explaining a configuration of the case of using HSS80 as a device for storing Context Information .
[0128]
　Figure 33, MME 30 have shown that it is connected through a HSS80 and S6a interface. In this figure, the HSS80, while indicating that the MME30 is connected, the HSS80, a plurality of MME are connected via the S6a interface.
[0129]
　Figure 34 is, MME 30 have shown that the HSS-FE (Front End) through 85 and S6a interface connected, are connected via a UDR (User Data Repository) 86 and Ud interface. Also, HSS-FE85 is connected via a UDR86 and Ud interface.
[0130]
　UDR86 holds subscriber data of the UE. Also, HSS-FE85 is disposed between the MME30 and UDR86, relays communications between the MME30 and UDR86. Thus, construction of HSS80 includes a storage unit of the data UDR86, it may be separated into the HSS-FE85 which acts as an interface when communicating with MME 30.
[0131]
　Subsequently, with reference to FIGS. 35 and 36, a description is given of the flow of processing for storing the Context information created in MME to HSS80 or UDR86.
[0132]
　First, eNB 70, as in the step S122 and the like in FIG. 19, NAS: Attach to select the destination to become the MME REQUEST message (S271). Here, eNB70 is, and selects the MME30. Then, eNB 70 is to MME30 selected, NAS: Attach to send a REQUEST message (S272).
[0133]
　Next, MME 30 is, NAS: Attach to generate a Context information about the UE that sent the REQUEST message (S273). For example, MME 30 is a HSS80 NAS: generating a Context information, etc. If the Attach Context information about the UE that sent the REQUEST message is not stored.
[0134]
　Next, MME 30 is generated Context information HSS80 or UDR86 (hereinafter referred to as HSS80 etc.) to store the sends a Context Put REQUEST message (S275). Then, like HSS80 stores Context information set in Context Put REQUEST message to the memory of the self apparatus (S275). Then, the like HSS80, sends a Context Put ANSWER message to MME 30. Here, like HSS80, without executing the process of selecting any MME in a context share group, Context Put to the MME which sent the REQUEST message, it transmits a Context Put ANSWER message.
[0135]
　Next, MME 30 in order to acquire an authentication vector (AV) required for authenticating the UE, to HSS80 like, and transmits the Authentication Information REQUEST message (S277). Next, HSS80 etc., transmits the set of authentication vectors for the given UE Authentication Information Answer message to the MME 30 (S278).
[0136]
　Next, MME 30 transmits a Context Put REQUEST message to send the authentication vector transmitted from like HSS80 to HSS80 like to HSS80 like. It is such HSS80, updates Context information reflecting the authentication vector of the UE Context information stored at step S275 (S280). Then, HSS80 transmits a Context Put ANSWER message to MME 30 (S281).
[0137]
　Next, MME 30 transmits an Authentication REQUEST message to the UE via the eNB70 to implement the authentication of UE (S282). Then, eNB 70 may, Authentication RESPONSE to send a message, to select the MME destination as in step S271 (S283). Here, eNB 70 is to have selected the MME # N belonging to the shared context group A.
[0138]
　Then, eNB 70 transmits an Authentication RESPONSE message to the selected MME # N (S284).
[0139]
　Proceeds to FIG. 36, then, MME # N in order to obtain a Context information about the UE, and sends a Context The Get REQUEST message to HSS80 etc. (S285). Next, HSS80 etc., transmits the set of Context information of the designated UE Context The Get ANSWER message to the MME # N (S286).
[0140]
　Next, MME # N executes an authentication process about the UE (S287). Next, MME # N, in order to store Context information reflecting the authentication process to HSS80 like, sends a Context Put REQUEST message set the Context information to HSS80 (S288). Then, the like HSS80, using the Context information set in Context Put REQUEST message, and updates the current Context information (S289). Then, like HSS80 is to MME # N, and transmits a Context Put ANSWER message (S290).
[0141]
　Here, steps S277 ~ S281 in FIG. 35 obtains the authentication vector which is required for authenticating the UE from HSS, further comprising a motion for saving the Context stored authentication vectors to HSS80. Therefore, like HSS80 is, to perform operations for storing the authentication vector to Contex information stored, it is possible to omit the steps S277 ~ S281.
[0142]
　As described above, by using the communication system according to a sixth embodiment of the present invention, HSS may store the Context information generated in MME. Thus, the plurality of MME which belong to the shared context group, by obtaining Context information from the HSS, it is possible to use the Context information generated in other MME.
[0143]
　(Embodiment 7)
　Subsequently, a configuration example of a communication system according to Embodiment 7 of the present invention will be described with reference to FIG. 37. Communication system of FIG. 37, the communication system of FIG. 2, the MME which belong to the shared context group different. In the figure, will mainly communication system differs from the FIG.
[0144]
　Communication system of the figure, MME 30 and MME40 belong to the shared context group C. Further, MME40, MME50 and MME60 belong to the shared context group D. That, MME 40 belongs to the shared context group C, and the shared context group D. Thus, MME may belong to multiple contexts sharing group.
[0145]
　In the configuration of such context sharing group as in FIG. 37, when executing a call process of FIG. 19, eNB 70 may, NAS: Attach if GUMMEI identified from GUTI set in the REQUEST message indicates MME 40, the MME 40, which context can not be identified belongs to a shared group.
[0146]
　Therefore, in such a case, the GUMMEI, may set the information capable of specifying the context sharing group. For example, the MMEC region of GUMMEI, may be subdivided into MMEC + shared context group ID. Or, eNB 70 is to NAS MME 40: after sending the Attach REQUEST message, the shared context group may be specified in the message sent from the MME.
[0147]
　As described above, as in the communication system according to a seventh embodiment of the present invention, by the MME to be able to belong to multiple contexts sharing group, the MME which belong to multiple contexts sharing groups, respectively It can also be used as a replacement device in the context sharing groups.
[0148]
　The present invention is not limited to the above embodiments, but can be appropriately changed without departing from the spirit.
[0149]
　Although the present invention has been described with reference to the embodiments, the present invention is not limited by the foregoing. Configuration and details of the present invention, it is possible to make various modifications that those skilled in the art can understand within the scope of the invention.
[0150]
　This application claims priority based on Japanese Patent Application No. 2015-049573 filed on March 12, 2015, the entire disclosure of which is incorporated herein.
DESCRIPTION OF SYMBOLS
[0151]
　10 communication control unit
　11 communication control unit
　12 communication control device
　20 Node device
　30 MME
　31 the Diameter communication unit
　32 S1AP communication unit
　33 GTP-C communication unit
　34 Context sharing unit
　35 Context storage unit
　36 MME call processing unit
　40 MME
　50 MME
　60 MME
　70 eNB
　71 S1AP communication unit
　72 S1AP call processing section
　73 RRC processing section
　74 wireless processing section
　75 GTP-U communication unit
　76 GTP-U processing unit
　77 Context storage unit
　80 HSS
　81 the Diameter communication unit
　82 the subscriber information processing unit
　83 the subscriber information storage unit
　85
　HSS-FE
　86 UDR
　90 S-GW 91 GTP-C communication unit
　92 GTP-U communication unit
　93 GTP-C processing unit
　94 Context storage unit
　95 GTP-U processing unit
　100
　P-GW 110 UE

[Claim 1]
　A communication system comprising a plurality of communication control device, a node device for performing the call processing related to the communication terminal and the plurality of communication control device,
　the plurality of communication control devices share the subscriber data of said communication terminal to form a shared context group,
　the node device,
　selects the first communication control device in the context sharing group, it sends a call processing message to the first communication control device,
　the first communication control apparatus,
　executes the call processing by using the subscriber data to be shared in the context sharing group communication system.
[Claim 2]
　Wherein each of the communication control apparatus belonging to the shared context group,
　and transmits the identifier of the identifier and the device itself the shared context group to which the own device belongs to the node device, the communication system according to claim 1.
[Claim 3]
　Wherein each of the communication control device belonging to the shared context group,
　further transmitted to the node device weight information indicating the priority of selecting the own device, a communication system according to claim 2.
[Claim 4]
　The representative communication control unit belonging to the shared context group,
　and transmits the identifiers of all of the communication control device belonging to the identifier and the context shared group of shared context group to which the own device belongs to the node device, the communication of claim 1 system.
[Claim 5]
　The representative communication control unit belonging to the context sharing group,
　for all of the communication control device belonging to the shared context group, and further transmitted to the node device weight information indicating the priority of selecting a respective call control apparatus, according to claim the communication system according to 4.
[Claim 6]
　It said node device,
　receives the identifiers of all of the communication control device belonging to the identifier and the context shared group of the shared context group transmitted from the management apparatus to perform network management, communication system according to claim 1.
[Claim 7]
　The management apparatus
　for all of the communication control device belonging to the shared context group, further transmitted to the node device weight information indicating the priority of selecting a respective call control apparatus, a communication system according to claim 6.
[8.]
　The communication terminal
　transmits an identifier of a communication control apparatus that has performed the previous communication to the node device,
　the node device,
　wherein the communication terminal identifies the shared context group including call control apparatus executed the previous communication, the specific wherein transmitting the call processing message selected to the communication control device from the shared context of multiple belonging to the group communication control device, a communication system according to any one of claims 2 to 7 were.
[Claim 9]
　The communication terminal
　transmits an identifier of the shared context group communication control apparatus belongs executed the previous communication to the node device,
　the node device,
　a communication selected from a plurality of communication control device belonging to the shared context group transmitting the call processing message to the control device, a communication system according to any one of claims 2 to 7.
[Claim 10]
　The node device,
　identifies a context shared group call control apparatus that has transmitted the call processing message belongs, the call processing message to the selected communication control apparatus from among a plurality of communication control device belonging to the context sharing group identified sending a response message to the communication system according to any one of claims 2 to 7.
[Claim 11]
　The node device
　detects that the connection with the second communication control unit belonging to the shared context group is disconnected, the second communication control unit, to remove from the shared context group, claim 1 or the communication system according to any one of 10.
[Claim 12]
　The node device
　each time it sends a call proceeding message, select one of the communication control device from among a plurality of communication control device belonging to the shared context group, send the call processing message to the selected communication control device to, the communication system according to any one of claims 1 to 11.
[Claim 13]
　Third communication control device that will stop the operation,
　sends a message indicating that the device itself stops its operation to the node device,
　the node device,
　the third communication control unit, said shared context to remove from the group, the communication system according to any one of claims 1 to 12.
[Claim 14]
　Said third communication control apparatus
　sets the information indicating the timing for stopping the operation message indicating that stopping the own device operation, the communication system according to claim 13.
[Claim 15]
　A shared context means to share subscriber data of the communication terminal and another communication control apparatus belonging to the shared context group,
　when receiving the call processing message from the node device, using the subscriber data shared in the context sharing group a communication control unit for performing call processing Te.
[Claim 16]
　A node apparatus for performing call processing related to the communication terminal and the communication control apparatus,
　one each time to send a call processing message from a plurality of communication control devices belonging to the shared context groups that share subscriber data of the communication terminal select the communication control unit transmits a call processing message to the selected communication control device, the node device.
[Claim 17]
　A plurality of communication control device, a communication method executed in a communication system comprising a node apparatus for performing call processing related to the communication terminal and the plurality of communication control device,
　the plurality of communication control device, the communication terminal subscriber data to form a shared context groups that share of
　the node device selects the first communication control device in the context share group,
　sends a call processing message to the selected said first communication control unit and,
　the first communication control unit executes the call processing by using the subscriber data to be shared in the context sharing group, the communication method.