US20160219476A1 - Communication system, base station, communication method, and non-transitory computer readable medium storing program - Google Patents
Communication system, base station, communication method, and non-transitory computer readable medium storing program Download PDFInfo
- Publication number
- US20160219476A1 US20160219476A1 US15/023,784 US201415023784A US2016219476A1 US 20160219476 A1 US20160219476 A1 US 20160219476A1 US 201415023784 A US201415023784 A US 201415023784A US 2016219476 A1 US2016219476 A1 US 2016219476A1
- Authority
- US
- United States
- Prior art keywords
- mme
- core network
- handover
- base station
- sgsn
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000004891 communication Methods 0.000 title claims abstract description 194
- 238000000034 method Methods 0.000 title claims abstract description 24
- 238000010295 mobile communication Methods 0.000 claims description 17
- 230000000694 effects Effects 0.000 abstract description 6
- 230000008569 process Effects 0.000 description 13
- 230000004044 response Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 5
- 239000000284 extract Substances 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 238000012546 transfer Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000013461 design Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000002411 adverse Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 230000001174 ascending effect Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000002542 deteriorative effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 231100000989 no adverse effect Toxicity 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000003014 reinforcing effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/12—Reselecting a serving backbone network switching or routing node
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- H04L61/1511—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/08—Load balancing or load distribution
- H04W28/0827—Triggering entity
- H04W28/0835—Access entity, e.g. eNB
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/08—Load balancing or load distribution
- H04W28/088—Load balancing or load distribution among core entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/08—Load balancing or load distribution
- H04W28/09—Management thereof
- H04W28/0925—Management thereof using policies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/08—Load balancing or load distribution
- H04W28/09—Management thereof
- H04W28/0925—Management thereof using policies
- H04W28/0942—Management thereof using policies based on measured or predicted load of entities- or links
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0066—Transmission or use of information for re-establishing the radio link of control information between different types of networks in order to establish a new radio link in the target network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/16—Performing reselection for specific purposes
- H04W36/22—Performing reselection for specific purposes for handling the traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/34—Reselection control
- H04W36/38—Reselection control by fixed network equipment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/34—Reselection control
- H04W36/38—Reselection control by fixed network equipment
- H04W36/385—Reselection control by fixed network equipment of the core network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0284—Traffic management, e.g. flow control or congestion control detecting congestion or overload during communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/16—Gateway arrangements
Definitions
- the present invention relates to a communication system, in particular, a communication system including a plurality of core network systems.
- a communication system managed by a telecommunications carrier manages the movements of communication terminals and includes a core network(s) that includes data relay devices and the like. Further, the communication system managed by a telecommunications carrier prepares a gateway device for each company (i.e., each corporate client) as a corporate service and thereby connects to a network managed by each company through the gateway device. The gateway devices are disposed inside the core network. A communication terminal can connect to the network of the company to which that communication terminal belongs through the gateway device disposed inside the communication system managed by the telecommunications carrier.
- the MTC terminal is a terminal that transmits/receives sensor information, commodity management information and so on, and the amount of communication per terminal is small.
- a company or the like that introduces MTC terminals collects information pieces transmitted from a plurality of MTC terminals and analyzes the collected information.
- the company or the like that introduces MTC terminals expands their services by using the analysis result. In such cases, each company connects a number of MTC terminals to a communication system in order to collect a large amount of information.
- Patent Literature 1 discloses a system in which a sensor(s), a mobile information terminal(s), and an application server cooperate with each other so that a service is provided to the mobile information terminal(s). Specifically, the mobile information terminal acquires a plurality of sensor information pieces. Further, the mobile information terminal transmits the acquired sensor information pieces to the application server. Then, the application server creates advice information based on the sensor information transmitted from the mobile information terminal and transmits the created advice information to the mobile information terminal. In this way, the mobile information terminal can receive an advice service based on the sensor information.
- An object of the present invention is to provide a communication system, a base station, a communication method, and a program capable of eliminating an effect caused by a sharp increase in the amount of traffic by a specific group of communication terminals on the quality of the other communication terminals.
- a communication system includes: a communication terminal; a node device that selects a gateway device that performs data communication with the communication terminal; and a base station that selects the node device based on an identifier included in a connection request message transmitted from the communication terminal.
- a base station includes: a communication unit that receives a connection request message transmitted from a communication terminal; and a determination unit that selects a node device from among a plurality of node devices based on an identifier included in the connection request message, the selected node device being to select a gateway device to which the communication terminal connects.
- a communication method includes: receiving a connection request message transmitted from a communication terminal; and selecting a node device from among a plurality of node devices based on an identifier included in the connection request message, the selected node device being to select a gateway device to which the communication terminal connects.
- a program causes a computer to execute: receiving a connection request message transmitted from a communication terminal; and selecting a node device from among a plurality of node devices based on an identifier included in the connection request message, the selected node device being to select a gateway device to which the communication terminal connects.
- the present invention it is possible to provide a communication system, a base station, a communication method, and a program capable of eliminating an effect caused by a sharp increase in the amount of traffic by a specific group of communication terminals on the quality of the other communication terminals.
- FIG. 1 is a configuration diagram of a communication system according to a first exemplary embodiment
- FIG. 2 is a configuration diagram of a base station according to a second exemplary embodiment
- FIG. 3 is a configuration diagram of a core network system according to the second exemplary embodiment
- FIG. 4 shows a service identifier according to the second exemplary embodiment
- FIG. 5 shows an outline of a selection process performed by an MME according to the second exemplary embodiment
- FIG. 6 shows a flow of a service identifier transmission process according to the second exemplary embodiment
- FIG. 7 shows a flow of a service identifier acquisition process according to the second exemplary embodiment
- FIG. 8 shows a flow of a connection request message transfer process according to the second exemplary embodiment
- FIG. 9 shows a specific example of a connection request message according to the second exemplary embodiment
- FIG. 10 is a configuration diagram of a communication system according to a third exemplary embodiment.
- FIG. 11 shows a flow of an MME selection process according to the third exemplary embodiment.
- FIG. 12 is a configuration diagram of a core network system according to a fourth exemplary embodiment.
- FIG. 1 A configuration example of a communication system according to a first exemplary embodiment of the present invention is explained with reference to FIG. 1 .
- a communication system shown in FIG. 1 includes a core network system 10 , a core network system 20 , a base station 30 , and a communication terminal 40 .
- Each of the core network systems 10 and 20 is a core network system for which communication terminals 40 allowed to connect thereto are restricted.
- the communication terminals 40 allowed to connect to that core network may be communication terminals owned by users belonging to that company. That is, the communication terminal 40 may be configured so that a communication terminal 40 can connect only to a core network system assigning to a company to which its user belong and cannot connect to core network systems assigned to the other companies.
- the core network system 10 or 20 may be assigned to one company or a plurality of companies. That is, a plurality of companies may share one core network system. Further, for example, one core network system may be assigned to each service to be provided. When a service using MTC terminals is provided, a core network system may be used for connection with specific MTC terminals. Further, for example, in a region in which traffic is small or the like, a plurality of companies may share one core network system.
- the core network systems 10 and 20 include a plurality of node devices.
- the plurality of node devices are used to manage the communication terminal 40 or to relay data.
- Each of the core network systems 10 and 20 is assigned a service identifier indicating a corporate service that can be accommodated in that core network system.
- the corporate service is a service that is provided inside the core network system by an ordinary company or a telecommunications carrier, and in the core network system, the corporate service is identified by using a service identifier.
- the corporate service may be a service that is provided in an external network connected to the core network system.
- Service identifiers assigned to their respective core network systems are different from one core network system to another.
- Each of the core network systems 10 and 20 transmits the service identifier assigned to the own system to the base station 30 .
- the communication terminal 40 may be a mobile phone terminal, a smart phone terminal, a tablet communication terminal, a personal computer having a communication function, or the like.
- the communication terminal 40 may be an MTC terminal, a compact device having a communication function, or the like.
- the base station 30 is shared by the core network systems 10 and 20 .
- the base station 30 is disposed inside a mobile communication network and communicates with the communication terminal 40 through a wireless line. Further, the base station 30 communicates with a node device included in the core network system 10 or 20 through a wired line or a wireless line.
- the mobile communication network is a network that includes the core network systems 10 and 20 and the base station 30 and is managed by one telecommunications carrier.
- the base station 30 receives a connection request message for the core network system 10 or 20 transmitted from the communication terminal 40 .
- a core network system to which it can connect is determined in advance. Assume that, for example, the core network system to which the communication terminal 40 can connect is the core network system 10 . In such a case, the communication terminal 40 transmits a connection request message including information for identifying the core network system 10 .
- the identification information included in the connection request message may be a service identifier indicating a cooperate service or may be other identifiers.
- the base station 30 When the base station 30 is requested to connect to the core network system 10 by the communication terminal 40 , the base station 30 transmits the connection request message transmitted from the communication terminal 40 to the core network system 10 by using the service identifier transmitted from the core network system 10 .
- the “using the service identifier” means that the base station 30 selects a destination core network system to which the connection request message should be transmitted by specifying the service identifier.
- the base station 30 may transmit the connection request message to a core network system to which that service identifier is assigned.
- the base station 30 may extract a service identifier associated with that identifier and transmit the connection request message to a core network system to which the extracted service identifier is assigned.
- the base station 30 can identify a core network system to which the base station 30 should connect from among a plurality of core network systems by using a service identifier assigned to a respective one of the core network systems.
- the base station 30 can select a core network system to which the communication terminal 40 can connect by using a service identifier and transmit a connection request message transmitted from the communication terminal 40 to the selected core network system.
- the base station 30 can also transmit/receive data relating to the communication terminal 40 that is generated after the above-described connection process through the selected core network system.
- each of a plurality of core network systems disposed inside the mobile communication system is assigned a service identifier indicating a corporate service that can be accommodated in that core network system.
- the base station 30 can determine, for each communication terminal 40 , the destination of a connection request message transmitted from that communication terminal 40 . Since the base station 30 can transfer communication data relating to a specific group of communication terminals to a specific core network system, the base station 30 can prevent the transfer of communication data from having an adverse effect on the other core network systems and thereby deteriorating their communication quality even when the amount of communication data relating to the specific group of communication terminals sharply increases.
- the base station 30 includes a network (NW) communication unit 31 , a service identifier holding unit 32 , a terminal communication unit 33 , and a determination unit 34 .
- NW network
- the NW communication unit 31 communicates with a node device disposed inside a core network system.
- the NW communication unit 31 may be used as an interface for communicating with the node device.
- the NW communication unit 31 receives a service identifier transmitted from the node device.
- the service identifier is an identifier indicating a corporate service that can be accommodated in the core network system in which the node device is disposed.
- the NW communication unit 31 outputs the received service identifier to the service identifier holding unit 32 .
- the service identifier holding unit 32 associates the service identifier output from the NW communication unit 31 with the core network system and manages (or stores) the service identifier in the associated state.
- the service identifier holding unit 32 may be a memory disposed inside the base station 30 or an external memory connected to the base station 30 .
- the NW communication unit 31 communicates with a plurality of core network systems and thereby receives a plurality of service identifiers
- the service identifier holding unit 32 holds the plurality of service identifiers.
- the terminal communication unit 33 communicates with the communication terminal 40 .
- the terminal communication unit 33 may be used as an interface for communicating with the communication terminal 40 .
- the terminal communication unit 33 performs wireless communication with the communication terminal 40 by using a predetermined wireless communication scheme.
- the predetermined wireless communication scheme may be, for example, LTE (Long Term Evolution) specified in 3GPP (3rd Generation Partnership Project).
- the terminal communication unit 33 receives a connection request message transmitted from the communication terminal 40 .
- the terminal communication unit 33 outputs the received connection request message to the determination unit 34 .
- the communication terminal 40 can transmit/receive user data by connecting to the core network system through the base station 30 . Therefore, the communication terminal 40 transmits a connection request message in order to connect to the core network system.
- the user data examples include voice data, image data, and moving image data. Further, the user data may be referred to as “U-Plane (User-Plane) data”. Meanwhile, the connection request message may be referred to as “control data”. The control data may also be referred to as “C-Plane (Control-Plane) data”. Specifically, the connection request message may be an Attach message or a TAU (Tracking Area Update) message specified in the 3GPP.
- TAU Track Area Update
- the determination unit 34 determines a core network system to which the connection request message output from the terminal communication unit 33 should be transmitted by using a service identifier set in that connection request message and a service identifier(s) held in the service identifier holding unit 32 .
- the CPU or the like of a computer apparatus constituting the base station 30 may be used as the determination unit 34 .
- the determination unit 34 Upon receiving the connection request message from the terminal communication unit 33 , the determination unit 34 extracts a service identifier set in the connection request message.
- the service identifier set in the connection request message is used when the communication terminal 40 selects a core network system to which the communication terminal should connect.
- the determination unit 34 determines whether or not the same service identifier as the extracted service identifier is held in the service identifier holding unit 32 .
- the determination unit 34 may acquire information representing a list of service identifiers held in the service identifier holding unit 32 from the service identifier holding unit 32 and thereby determine whether or not the service identifier set in the connection request message is held in the service identifier holding unit 32 .
- the determination unit 34 determines that the same service identifier as the extracted service identifier is held in the service identifier holding unit 32 , the determination unit 34 transmits the connection request message to a core network system associated with the service identifier through the NW communication unit 31 .
- the fact that the same service identifier as the extracted service identifier is held in the service identifier holding unit 32 indicates that the NW communication unit 31 can communicate with the core network system to which that service identifier is assigned.
- the determination unit 34 may transmits the connection request message to a predetermined core network system through the NW communication unit 31 .
- the core network system 10 B has a similar configuration to that of the core network system 10 A, and therefore its detailed explanation is omitted.
- the core network systems 10 A and 10 B may be operated by one company, or may be shared by a plurality of companies.
- each of the core network systems 10 A and 10 B is an EPC (Evolved Packet Core).
- the core network system 10 A includes an SGW (Serving GW) 11 A, a PGW (Packet Data Network GW) 12 A and an MME (Mobility Management Entity) 13 A. Further, the PGW 12 A is connected to a service server 14 A installed in a dedicated network A.
- the SGW 11 A, the PGW 12 A, and the MME 13 A are node devices specified in the 3GPP. Examples of the dedicated network include: networks operated by companies, organizations and agencies, and municipalities; intra-company LANs; and Ethernets (registered trademark).
- the core network system 10 A includes one SGW 11 A, one PGW 12 A, one MME 13 A, and one service server 14 A. However, the core network system 10 A may include a plurality of SGWs 11 A, a plurality of PGWs 12 A, a plurality of MMEs 13 A, and a plurality of service servers 14 A.
- each node device in the core network system 10 A may be provided as a VNF (Virtualized Network Function) by the telecommunications carrier.
- the VNF is virtualization of a network node in which a CPU(s), a memory(s), and so on of a physical machine(s) are shared by a plurality of companies or the like, and resources such as a virtual CPU and a virtual memory provided to each company can be dynamically changed.
- the SGW 11 A transmits user data transmitted from base stations 30 A and 30 B to the PGW 12 A. Further, the SGW 11 A transmits user data whose destination is a communication terminal 100 to the base station 30 A and transmits user data whose destination is a communication terminal 130 to the base station 30 B.
- FIG. 3 shows that the communication terminals 100 and 130 communicate with the core network system 10 A, and communication terminals 110 and 120 communicate with the core network system 10 B.
- the PGW 12 A transmits or receive user data.
- the PGW 12 A communicates with the service server 14 A disposed in the dedicated network A. That is, the PGW 12 A is a gateway device disposed on the boundary with the dedicated network A.
- the PGW 12 A may connect to a corporate service server or the like.
- the MME 13 A selects the SGW 11 A that transmits/receive user data relating to the communication terminal 100 , which is connected to the MME 13 A through the base station 30 A, and user data relating to the communication terminal 130 , which is connected to the MME 13 A through the base station 30 B.
- the MME 13 A notifies the base stations 30 A and 30 B of information about the selected SGW 11 A.
- the base station 30 A can transmit user data transmitted from the communication terminal 100 to the SGW 11 A.
- the base station 30 A can receive data transmitted from the SGW 11 A and transmit the received data to the communication terminal 100 .
- the MME 13 A selects the PGW 12 A as well as the SGW 11 A.
- the MME 13 A may take account of the load state of each of these SGWs 11 A and thereby select a SGW 11 A having a smaller (or smallest) load. Further, the MME 13 A may select a SGW 11 A according to other selection criteria.
- the MME 13 A holds a service identifier of a service that can be accommodated in the core network system 10 A. Further, the MME 13 A transmits the held service identifier to the base stations 30 A and 30 B. A case where the MME 13 A is shared among a plurality of cooperate services, e.g., shared by a plurality of companies or the like is explained hereinafter.
- the MME 13 A holds a plurality of service identifiers relating to a plurality of cooperate services for which the connection is allowed, and thereby is shared among the plurality of cooperate services and the like. In this case, the MME 13 A notifies the base stations 30 A and 30 B of the plurality of service identifiers.
- FIG. 4 shows an example in which a service identifier is set in a sub-field of an MMEGI (MME Group ID) field included in a GUMMEI (Globally Unique MME Identifier).
- MMEGI MME Group ID
- GUMMEI Globally Unique MME Identifier
- the GUMMEI is identification information for an MME specified in the 3GPP.
- the service identifier may be handled as an independent information element in the mobile communication system.
- the GUMMEI is identification information that the MME 13 transmits to the base station 30 .
- the GUMMEI includes various information fields including fields for an MCC (Mobile Country Code), an MNC (Mobile Network Code), an MMEGI, and an MMEC (MME Code).
- MCC Mobile Country Code
- MNC Mobile Network Code
- MMEGI Mobile Network Code
- MME Code MMEC
- the Pool ID is an identifier that is assigned to a plurality of MMEs in common.
- a common Pool ID may be assigned to a plurality of MMEs disposed in a specific region.
- the plurality of MMEs to which a common Pool ID is assigned may be referred to a MME group. That is, different Pool IDs are assigned to a group of MMEs disposed in different regions, and the same Pool ID is assigned to a group of MMEs disposed in the same region.
- the MMEGI consists of, for example, 16 bits.
- N bits N is an integer no less than zero
- the remaining bits (16-N bits) are assigned to the Pool ID.
- the Service ID is an identifier assigned to each corporate service.
- a core network system used by a corporate service is specified.
- Service IDs each of which is assigned to one of the plurality of corporate services are assigned to that core network system. That is, a core network system holds one or a plurality of Service IDs according to a corporate service(s) to which the connection is allowed.
- the MMEC is an identifier for uniquely identifying each of a plurality of MMEs to which a common Pool ID is assigned.
- the MME 13 transmits a GUMMEI with a Service ID set therein to the base station 30 .
- the base station 30 extracts the Service ID from the GUMMEI transmitted from the MME 13 , associates the extracted GUMMEI with a core network system, and manages (or stores) the GUMMEI in the associated state.
- a core network system 10 includes one MME and a core network system 20 includes three MMEs.
- the core network system 10 includes an MME in which the MMEGI is 10/100 and the MMEC is 1.
- the MMEGI indicates “Service ID/Pool ID”. Therefore, in the MME of the core network system 10 , a value 10 is assigned to the Service ID and a value 100 is assigned to the Pool ID.
- the core network system 20 includes: an MME in which the MMEGI is 20/100 and the MMEC is 1; an MME in which the MMEGI is 20/100 and the MMEC is 2; and an MME in which the MMEGI is 20/100 and the MMEC is 3.
- Each MME notifies the base station 30 of its MMEGI and MMEC.
- the base station 30 manages (or stores) the notified MMEGIs and MMECs.
- the base station 30 when the base station 30 receives a connection request message in which a value 20 is set as a service identifier from the communication terminal 40 , the base station 30 selects one of the three MMEs in which a value 20 is set as the Service ID and transmits the connection request message to the selected MME. In this case, the base station 30 may select one of the three MMEs in which a value 20 is set as the Service ID by using Weight Factors. For example, the base station 30 may selects an MME in the ascending order of the MMECs. Alternatively, the base station 30 may acquire the processing load states of the MMEs in advance and select an MME having a smaller (or smallest) processing load. The base station 30 may select an MME by using other selection processes.
- the communication system may be configured so that an MME is shared among a plurality of corporate services.
- MME accommodates “MMEGI: 10/100, MMEC: 1” and “MMEGI: 20/100, MMEC: 1”.
- the eNB is a base station in conformity with an LTE (Long Term Evolution) wireless scheme.
- the eNB transmits an S1 SETUP REQUEST message to an MME (S 10 ). For example, upon power-on, the eNB transmits an S1 SETUP REQUEST message to an MME connected to that eNB. Note that the eNB may transmit an S1 SETUP REQUEST message to a plurality of MMEs.
- the MME transmits an S1 SETUP RESPONSE message to the eNB (S 11 ).
- the MME sets a GUMMEI in the S1 SETUP RESPONSE message. That is, the MME notifies the eNB of a Service ID by transmitting an S1 SETUP RESPONSE message to the eNB.
- the MME notifies the eNB of the plurality of Service IDs.
- the plurality of Service IDs may be transmitted from the MME to the eNB in the form of a list of Service IDs. Note that the outline of the S1 SETUP REQUEST message and the S1 SETUP RESPONSE message shown in FIG.
- the NW communication unit 31 of the eNB acquires a GUMMEI set in an S1 SETUP RESPONSE message (S 21 ).
- the service identifier holding unit 32 extracts a service identifier (Service ID) set in a sub-field of the MMEGI of the GUMMEI (S 22 ).
- the service identifier holding unit 32 holds the extracted Service ID (S 23 ).
- connection request message transfer process according to the second exemplary embodiment of the present invention is explained with reference to FIG. 8 .
- the determination unit 34 receives a connection request message transmitted from the communication terminal 40 through the terminal communication unit 33 (S 31 ). Next, the determination unit 34 determines whether or not a Service ID is set as a service identifier in the connection request message (S 32 ). Next, when the determination unit 34 determines that a Service ID is set in the connection request message, the determination unit 34 extracts that Service ID (S 33 ). Next, the determination unit 34 determines whether or not the extracted Service ID matches a Service ID held in the service identifier holding unit 32 (S 34 ).
- the determination unit 34 determines that the Service ID included in the connection request message matches a Service ID held in the service identifier holding unit 32 , the determination unit 34 transmits the connection request message to an MME of a core network system associated with the Service ID included in the connection request message (S 36 ).
- the determination unit 34 determines that the Service ID included in the connection request message does not match any Service ID held in the service identifier holding unit 32 or when the determination unit 34 determines that no Service ID is set in the connection request message transmitted from the communication terminal 40 in the step S 32 , the determination unit 34 transmits the connection request message to a predetermined Default MME (S 35 ).
- Information about the Default MME may be stored in advance in a memory or the like disposed inside the base station 30 , or may be set in an S1 SETUP RESPONSE or the like and sent to the base station 30 .
- FIG. 9 shows a state where a Service ID is set in an RRC Connection Request message transmitted from the communication terminal 40 to the eNB. In this way, the communication terminal 40 notifies the eNB of the Service ID.
- FIG. 9 an example case where the Service ID has an 8-bit length is shown.
- the base station can connect a communication terminal for which a specific service identifier is set with a specific core network system.
- a specific core network system As a result, data relating to the specific communication terminal is transmitted through the specific core network system. Therefore, no data relating to the specific communication terminal flows into the other core network systems. Accordingly, even when the amount of data relating to the specific communication terminal increases, the other core network systems receive no adverse effect therefrom.
- the service identifier is set in a sub-field of the MMEGI of the GUMMEI, which has been already specified in the 3GPP, the above-described configuration can be implemented without substantially changing the structure of existing messages.
- a mobile telecommunications carrier can design a network while estimating the amount of traffic only for ordinary users such as users of smart phones and users of mobile phone terminals. That is, a mobile telecommunications carrier can design a mobile communication network without taking account of the amount of traffic relating to communication terminals and the like that connect to core network systems each of which is assigned to a respective one of corporate services.
- each company can design a core network system according to the characteristics of communication terminals that connect to that core network system. For example, when only communication terminals that do not move connect to a core network system, the cost for the core network system can be reduced by constructing a core network system in which the movement management function is omitted. Further, when a number of communication terminals that frequently move connect to a core network system, the company can construct a core network system having high quality by reinforcing the MME, the SGW, and the PGW.
- FIG. 10 a configuration example of a communication system according to a third exemplary embodiment of the present invention is explained with reference to FIG. 10 .
- a case where the communication terminal 40 performs handover involving a change of an MME is explained.
- a communication system shown in FIG. 10 includes a core network system 20 , a core network system 50 , a base station 30 , a base station 35 , and a DNS (Domain Name System) server 60 .
- the core network system 20 includes an MME 21 and an MME 22 .
- the core network system 50 includes an MME 51 .
- FIG. 10 shows a state where the communication terminal 40 moves from a communication area formed by the base station 30 to a communication area formed by the base station 35 .
- the communication terminal 40 moves while communicating with the base station 30 and thus performs handover.
- a Service ID assigned to the MMEs 21 and 22 has a value 20. Further, the Pool ID of the MME 21 has a value 100 and the Pool ID of the MME 22 has a value 200. That is, the MMEs 21 and 22 are disposed in different regions.
- the Service ID of the MME 51 has a value 50 and its Pool ID has a value 100.
- the MME 51 manages a region corresponding to the combined regions of the MMEs 21 and 22 .
- the MME 21 manages the base station 30 . That is, the MME 21 is connected to the base station 30 .
- the MME 22 is connected to the base station 35 . Further, the MME 51 is connected to the base stations 30 and 35 . Further, the MMEs 21 and 22 is connected with the DNS server 60 .
- Each of the base stations 30 and 35 selects the core network system 20 or 50 as the destination of a connection request message according to a Service ID sent from the communication terminal 40 .
- FIG. 10 shows a state where the communication terminal 40 uses a value 20 as its Service ID and connects to the MME 21 through the base station 30 .
- the communication terminal 40 moves to the communication area formed by the base station 35 .
- the MME 22 since the Service ID assigned to the MME 21 connected to the base station 30 has a value 20, the MME 22 , to which the value 20 is assigned as its Service ID, serves as the MME that manages the base station 35 after the communication terminal 40 has moved. Therefore, when the communication terminal 40 is handed over, the MME to which the communication terminal 40 connects also changes from the MME 21 to the MME 22 .
- the MMEs to which the base station 35 connects includes the MME 51 in addition to the MME 22 .
- the MME to which the communication terminal 40 connects is changed to the MME 22 that has a Service ID having the same value as that of the MME 21 .
- the MME 22 which manages the base station 35 to which the communication terminal 40 has been handed over, acquires subscriber information of the communication terminal 40 from the MME 21 . That is, the MME 21 transmits the subscriber information of the communication terminal 40 to the MME 22 , which manages the base station 35 to which the communication terminal 40 has moved.
- the MME 21 receives a handover (HO) request message relating to the communication terminal 40 from the base station 30 (S 41 ).
- the MME 21 transmits a message for inquiring the MME at the HO destination of the communication terminal 40 to the DNS server 60 (S 42 ).
- the MME 21 may transmit a message to the DNS server 60 in order to inquire the MME connected to the base station 35 to which the communication terminal 40 has moved.
- the MME 21 may transmit area information of the base station 35 to the DNS server 60 .
- the DNS server 60 manages (or stores), for example, information of areas and MMEs managing those areas in a state where they are associated with each other. Note that the DNS server 60 manages MMEs by using FQDNs (Fully Qualified Domain Names). The DNS server 60 may also manage (or stores) Service IDs possessed by MMEs by incorporating those Service IDs into FQDNs. For example, since a value 20 is assigned to the MME 22 as a Service ID, the DNS server 60 may define the FQDN of the MME 22 as “sid20mmec1.epc. . . . ” and manages (or stores) the defined FQSN. Further, the DNS server 60 may define the FQDN of the MME 51 as “sid50mmec1.epc. . . . ” and manages (or stores) the defined FQSN.
- the MME 21 receives a response massage including “sid20mmec1.epc. . . . ” and “sid50mmec1.epc. . . . ” from the DNS server 60 (S 43 ).
- the MME 21 determines whether or not there is an FQDN including a Service ID that matches the Service ID assigned to the MME 21 itself (S 44 ).
- the MME 21 transmits subscriber information of the communication terminal 40 to the MME 22 in which an FQDN including the same Service ID as the Service ID assigned to the MME 21 itself is set (S 45 ).
- the MME 21 determines that there is no FQDN including a Service ID that matches the Service ID assigned to the MME 21 itself, the MME 21 selects one of the MMEs in which FQSNs notified from the DNS server 60 are set and transmits subscriber information of the communication terminal 40 to the selected MME (S 46 ).
- the former MME can transmit subscribe information of the communication terminal to the destination MME by using a service identifier.
- the MME 22 which manages the base station 35 to which the communication terminal 40 moves, selects the MME 21 , which manages the base station 30 from which the communication terminal 40 moves, and acquires subscriber information from the MME 21 .
- the MME 22 transmits an inquiring message to the DNS server 60 and acquires information about the MME connected to the base station 30 .
- the MME 22 selects the MME 21 by using a Service ID as in the case of the handover operation.
- the core network system 70 includes an SGSN (Serving GPRS Support Node) 71 and a GGSN (Gateway GPRS Support Node) 72 .
- SGSN Server GPRS Support Node
- GGSN Gateway GPRS Support Node
- Each of the SGSN 71 and the GGSN 72 is a node device specified in the 3GPP.
- Each of the SGSN 71 and the GGSN 72 transmits/receives user data relating to the communication terminal 40 and also transmits/receives control data relating to the communication terminal 40 .
- the SGSN 71 is connected to the base station 30 . That is, in contrast to the above-explained second and third exemplary embodiments in which the base station 30 selects an MME, the base station 30 selects the SGSN 71 in FIG. 12 . Similarly to the first to third exemplary embodiments, the base station 30 selects the SGSN 71 by using a service identifier.
- the base station 30 can select the SGSN 71 by using a service identifier even in the so-called “second generation system” or “third generation system” including the SGSN 71 and the GGSN 72 .
- the present invention is described as a hardware configuration in the above-described exemplary embodiments, the present invention is not limited to the hardware configurations.
- the processes in the base station and the MME can be also implemented by causing a CPU (Central Processing Unit) to execute a computer program.
- a CPU Central Processing Unit
- the program can be stored in various types of non-transitory computer readable media and thereby supplied to computers.
- the non-transitory computer readable media includes various types of tangible storage media. Examples of the non-transitory computer readable media include a magnetic recording medium (such as a flexible disk, a magnetic tape, and a hard disk drive), a magneto-optic recording medium (such as a magneto-optic disk), a CD-ROM (Read Only Memory), a CD-R, and a CD-R/W, and a semiconductor memory (such as a mask ROM, a PROM (Programmable ROM), an EPROM (Erasable PROM), a flash ROM, and a RAM (Random Access Memory)).
- a magnetic recording medium such as a flexible disk, a magnetic tape, and a hard disk drive
- a magneto-optic recording medium such as a magneto-optic disk
- CD-ROM Read Only Memory
- CD-R Compact Only Memory
- CD-R/W and
- the program can be supplied to computers by using various types of transitory computer readable media.
- Examples of the transitory computer readable media include an electrical signal, an optical signal, and an electromagnetic wave.
- the transitory computer readable media can be used to supply programs to computer through a wire communication path such as an electrical wire and an optical fiber, or wireless communication path.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Information Transfer Between Computers (AREA)
- Databases & Information Systems (AREA)
Abstract
An object is to provide a communication system, a base station, a communication method, and a program capable of eliminating an effect caused by a sharp increase in the amount of traffic by a specific group of communication terminals on the quality of the other communication terminals. A communication system according to the present invention includes a communication terminal (40), and a node device (13) that selects a gateway device (11) that performs data communication with the communication terminal (40). Further, the communication system includes a base station (30) that selects the node device (13) based on an identifier included in a connection request message transmitted from the communication terminal (40).
Description
- The present invention relates to a communication system, in particular, a communication system including a plurality of core network systems.
- A communication system managed by a telecommunications carrier manages the movements of communication terminals and includes a core network(s) that includes data relay devices and the like. Further, the communication system managed by a telecommunications carrier prepares a gateway device for each company (i.e., each corporate client) as a corporate service and thereby connects to a network managed by each company through the gateway device. The gateway devices are disposed inside the core network. A communication terminal can connect to the network of the company to which that communication terminal belongs through the gateway device disposed inside the communication system managed by the telecommunications carrier.
- In recent years, a connection(s) of an MTC (Machine Type Communication) terminal(s) to a communication system has been studied. The MTC terminal is a terminal that transmits/receives sensor information, commodity management information and so on, and the amount of communication per terminal is small. A company or the like that introduces MTC terminals collects information pieces transmitted from a plurality of MTC terminals and analyzes the collected information. The company or the like that introduces MTC terminals expands their services by using the analysis result. In such cases, each company connects a number of MTC terminals to a communication system in order to collect a large amount of information.
- Note that
Patent Literature 1 discloses a system in which a sensor(s), a mobile information terminal(s), and an application server cooperate with each other so that a service is provided to the mobile information terminal(s). Specifically, the mobile information terminal acquires a plurality of sensor information pieces. Further, the mobile information terminal transmits the acquired sensor information pieces to the application server. Then, the application server creates advice information based on the sensor information transmitted from the mobile information terminal and transmits the created advice information to the mobile information terminal. In this way, the mobile information terminal can receive an advice service based on the sensor information. -
- [Patent Literature 1] Japanese Unexamined Patent Application Publication No. 2010-165112
-
- [Non-Patent Literature 1] 3GPP Technical Specification, TS 36.413 V11.5.0 (2013-09), clause 8.7.3
- However, when a number of sensors each having a communication function, a number of MTC terminals or the like are connected to a communication system managed by a telecommunications carrier, the following problem occurs. When a number of sensors, a number of MTC terminals or the like update their software all at once, the amount of traffic in the communication system sharply increases. Further, in addition to the software updating, when MTC terminals perform communication all at once, the amount of traffic in the communication system increases with the increase in the number of the MTC terminals performing communication, though the amount of communication per terminal is small. In addition to the MTC terminals and the like, smart phones, mobile phones or the like are also connected to the communication system. Therefore, there is a problem that when the amount of traffic by the MTC terminals and the like sharply increases, it could cause adverse effects such as data delays on communication using smart phones, mobile phones or the like due to the network congestion.
- An object of the present invention is to provide a communication system, a base station, a communication method, and a program capable of eliminating an effect caused by a sharp increase in the amount of traffic by a specific group of communication terminals on the quality of the other communication terminals.
- A communication system according to a first aspect of the present invention includes: a communication terminal; a node device that selects a gateway device that performs data communication with the communication terminal; and a base station that selects the node device based on an identifier included in a connection request message transmitted from the communication terminal.
- A base station according to a second aspect of the present invention includes: a communication unit that receives a connection request message transmitted from a communication terminal; and a determination unit that selects a node device from among a plurality of node devices based on an identifier included in the connection request message, the selected node device being to select a gateway device to which the communication terminal connects.
- A communication method according to a third aspect of the present invention includes: receiving a connection request message transmitted from a communication terminal; and selecting a node device from among a plurality of node devices based on an identifier included in the connection request message, the selected node device being to select a gateway device to which the communication terminal connects.
- A program according to a fourth aspect of the present invention causes a computer to execute: receiving a connection request message transmitted from a communication terminal; and selecting a node device from among a plurality of node devices based on an identifier included in the connection request message, the selected node device being to select a gateway device to which the communication terminal connects.
- According to the present invention, it is possible to provide a communication system, a base station, a communication method, and a program capable of eliminating an effect caused by a sharp increase in the amount of traffic by a specific group of communication terminals on the quality of the other communication terminals.
-
FIG. 1 is a configuration diagram of a communication system according to a first exemplary embodiment; -
FIG. 2 is a configuration diagram of a base station according to a second exemplary embodiment; -
FIG. 3 is a configuration diagram of a core network system according to the second exemplary embodiment; -
FIG. 4 shows a service identifier according to the second exemplary embodiment; -
FIG. 5 shows an outline of a selection process performed by an MME according to the second exemplary embodiment; -
FIG. 6 shows a flow of a service identifier transmission process according to the second exemplary embodiment; -
FIG. 7 shows a flow of a service identifier acquisition process according to the second exemplary embodiment; -
FIG. 8 shows a flow of a connection request message transfer process according to the second exemplary embodiment; -
FIG. 9 shows a specific example of a connection request message according to the second exemplary embodiment; -
FIG. 10 is a configuration diagram of a communication system according to a third exemplary embodiment; -
FIG. 11 shows a flow of an MME selection process according to the third exemplary embodiment; and -
FIG. 12 is a configuration diagram of a core network system according to a fourth exemplary embodiment. - Exemplary embodiments according to the present invention are explained hereinafter with reference to the drawings. A configuration example of a communication system according to a first exemplary embodiment of the present invention is explained with reference to
FIG. 1 . A communication system shown inFIG. 1 includes acore network system 10, acore network system 20, abase station 30, and acommunication terminal 40. - Each of the
core network systems communication terminals 40 allowed to connect thereto are restricted. For example, when each of thecore network systems communication terminals 40 allowed to connect to that core network may be communication terminals owned by users belonging to that company. That is, thecommunication terminal 40 may be configured so that acommunication terminal 40 can connect only to a core network system assigning to a company to which its user belong and cannot connect to core network systems assigned to the other companies. - Further, the
core network system - The
core network systems communication terminal 40 or to relay data. - Each of the
core network systems core network systems base station 30. - The
communication terminal 40 may be a mobile phone terminal, a smart phone terminal, a tablet communication terminal, a personal computer having a communication function, or the like. Alternatively, thecommunication terminal 40 may be an MTC terminal, a compact device having a communication function, or the like. - The
base station 30 is shared by thecore network systems base station 30 is disposed inside a mobile communication network and communicates with thecommunication terminal 40 through a wireless line. Further, thebase station 30 communicates with a node device included in thecore network system core network systems base station 30 and is managed by one telecommunications carrier. - The
base station 30 receives a connection request message for thecore network system communication terminal 40. For thecommunication terminal 40, a core network system to which it can connect is determined in advance. Assume that, for example, the core network system to which thecommunication terminal 40 can connect is thecore network system 10. In such a case, thecommunication terminal 40 transmits a connection request message including information for identifying thecore network system 10. The identification information included in the connection request message may be a service identifier indicating a cooperate service or may be other identifiers. - When the
base station 30 is requested to connect to thecore network system 10 by thecommunication terminal 40, thebase station 30 transmits the connection request message transmitted from thecommunication terminal 40 to thecore network system 10 by using the service identifier transmitted from thecore network system 10. The “using the service identifier” means that thebase station 30 selects a destination core network system to which the connection request message should be transmitted by specifying the service identifier. - When a service identifier is included in the connection request message, the
base station 30 may transmit the connection request message to a core network system to which that service identifier is assigned. When an identifier different from the service identifier is included in the connection request message, thebase station 30 may extract a service identifier associated with that identifier and transmit the connection request message to a core network system to which the extracted service identifier is assigned. - As explained above, by using the communication system shown in
FIG. 1 , thebase station 30 can identify a core network system to which thebase station 30 should connect from among a plurality of core network systems by using a service identifier assigned to a respective one of the core network systems. Thebase station 30 can select a core network system to which thecommunication terminal 40 can connect by using a service identifier and transmit a connection request message transmitted from thecommunication terminal 40 to the selected core network system. Further, thebase station 30 can also transmit/receive data relating to thecommunication terminal 40 that is generated after the above-described connection process through the selected core network system. - As described above, each of a plurality of core network systems disposed inside the mobile communication system is assigned a service identifier indicating a corporate service that can be accommodated in that core network system. As a result, the
base station 30 can determine, for eachcommunication terminal 40, the destination of a connection request message transmitted from thatcommunication terminal 40. Since thebase station 30 can transfer communication data relating to a specific group of communication terminals to a specific core network system, thebase station 30 can prevent the transfer of communication data from having an adverse effect on the other core network systems and thereby deteriorating their communication quality even when the amount of communication data relating to the specific group of communication terminals sharply increases. - Next, a detailed configuration example of a
base station 30 according to a second exemplary embodiment of the present invention is explained with reference toFIG. 2 . Thebase station 30 includes a network (NW)communication unit 31, a serviceidentifier holding unit 32, aterminal communication unit 33, and adetermination unit 34. - The
NW communication unit 31 communicates with a node device disposed inside a core network system. TheNW communication unit 31 may be used as an interface for communicating with the node device. TheNW communication unit 31 receives a service identifier transmitted from the node device. The service identifier is an identifier indicating a corporate service that can be accommodated in the core network system in which the node device is disposed. TheNW communication unit 31 outputs the received service identifier to the serviceidentifier holding unit 32. - The service
identifier holding unit 32 associates the service identifier output from theNW communication unit 31 with the core network system and manages (or stores) the service identifier in the associated state. The serviceidentifier holding unit 32 may be a memory disposed inside thebase station 30 or an external memory connected to thebase station 30. When theNW communication unit 31 communicates with a plurality of core network systems and thereby receives a plurality of service identifiers, the serviceidentifier holding unit 32 holds the plurality of service identifiers. - The
terminal communication unit 33 communicates with thecommunication terminal 40. Theterminal communication unit 33 may be used as an interface for communicating with thecommunication terminal 40. Theterminal communication unit 33 performs wireless communication with thecommunication terminal 40 by using a predetermined wireless communication scheme. The predetermined wireless communication scheme may be, for example, LTE (Long Term Evolution) specified in 3GPP (3rd Generation Partnership Project). Theterminal communication unit 33 receives a connection request message transmitted from thecommunication terminal 40. Theterminal communication unit 33 outputs the received connection request message to thedetermination unit 34. Thecommunication terminal 40 can transmit/receive user data by connecting to the core network system through thebase station 30. Therefore, thecommunication terminal 40 transmits a connection request message in order to connect to the core network system. - Examples of the user data include voice data, image data, and moving image data. Further, the user data may be referred to as “U-Plane (User-Plane) data”. Meanwhile, the connection request message may be referred to as “control data”. The control data may also be referred to as “C-Plane (Control-Plane) data”. Specifically, the connection request message may be an Attach message or a TAU (Tracking Area Update) message specified in the 3GPP.
- The
determination unit 34 determines a core network system to which the connection request message output from theterminal communication unit 33 should be transmitted by using a service identifier set in that connection request message and a service identifier(s) held in the serviceidentifier holding unit 32. The CPU or the like of a computer apparatus constituting thebase station 30, for example, may be used as thedetermination unit 34. - Upon receiving the connection request message from the
terminal communication unit 33, thedetermination unit 34 extracts a service identifier set in the connection request message. The service identifier set in the connection request message is used when thecommunication terminal 40 selects a core network system to which the communication terminal should connect. At this point, thedetermination unit 34 determines whether or not the same service identifier as the extracted service identifier is held in the serviceidentifier holding unit 32. Thedetermination unit 34 may acquire information representing a list of service identifiers held in the serviceidentifier holding unit 32 from the serviceidentifier holding unit 32 and thereby determine whether or not the service identifier set in the connection request message is held in the serviceidentifier holding unit 32. - When the
determination unit 34 determines that the same service identifier as the extracted service identifier is held in the serviceidentifier holding unit 32, thedetermination unit 34 transmits the connection request message to a core network system associated with the service identifier through theNW communication unit 31. The fact that the same service identifier as the extracted service identifier is held in the serviceidentifier holding unit 32 indicates that theNW communication unit 31 can communicate with the core network system to which that service identifier is assigned. On the other hand, when thedetermination unit 34 determines that the same service identifier as the extracted service identifier is not held in the serviceidentifier holding unit 32, thedetermination unit 34 may transmits the connection request message to a predetermined core network system through theNW communication unit 31. - Next, configuration examples of
core network systems FIG. 3 . Thecore network system 10B has a similar configuration to that of thecore network system 10A, and therefore its detailed explanation is omitted. Note that thecore network systems core network systems - The
core network system 10A includes an SGW (Serving GW) 11A, a PGW (Packet Data Network GW) 12A and an MME (Mobility Management Entity) 13A. Further, thePGW 12A is connected to aservice server 14A installed in a dedicated network A. TheSGW 11A, thePGW 12A, and theMME 13A are node devices specified in the 3GPP. Examples of the dedicated network include: networks operated by companies, ministries and agencies, and municipalities; intra-company LANs; and Ethernets (registered trademark). In this figure, thecore network system 10A includes oneSGW 11A, onePGW 12A, oneMME 13A, and oneservice server 14A. However, thecore network system 10A may include a plurality ofSGWs 11A, a plurality ofPGWs 12A, a plurality ofMMEs 13A, and a plurality ofservice servers 14A. - Further, each node device in the
core network system 10A may be provided as a VNF (Virtualized Network Function) by the telecommunications carrier. The VNF is virtualization of a network node in which a CPU(s), a memory(s), and so on of a physical machine(s) are shared by a plurality of companies or the like, and resources such as a virtual CPU and a virtual memory provided to each company can be dynamically changed. - The
SGW 11A transmits user data transmitted frombase stations PGW 12A. Further, theSGW 11A transmits user data whose destination is acommunication terminal 100 to thebase station 30A and transmits user data whose destination is acommunication terminal 130 to thebase station 30B.FIG. 3 shows that thecommunication terminals core network system 10A, andcommunication terminals core network system 10B. - Similarly to the
SGW 11A, thePGW 12A transmits or receive user data. ThePGW 12A communicates with theservice server 14A disposed in the dedicated network A. That is, thePGW 12A is a gateway device disposed on the boundary with the dedicated network A. For example, thePGW 12A may connect to a corporate service server or the like. - The
MME 13A selects theSGW 11A that transmits/receive user data relating to thecommunication terminal 100, which is connected to theMME 13A through thebase station 30A, and user data relating to thecommunication terminal 130, which is connected to theMME 13A through thebase station 30B. TheMME 13A notifies thebase stations SGW 11A. As a result, for example, thebase station 30A can transmit user data transmitted from thecommunication terminal 100 to theSGW 11A. Further, thebase station 30A can receive data transmitted from theSGW 11A and transmit the received data to thecommunication terminal 100. TheMME 13A selects thePGW 12A as well as theSGW 11A. - When there are a plurality of
SGWs 11A in thecore network system 10A, theMME 13A may take account of the load state of each of theseSGWs 11A and thereby select aSGW 11A having a smaller (or smallest) load. Further, theMME 13A may select aSGW 11A according to other selection criteria. - The
MME 13A holds a service identifier of a service that can be accommodated in thecore network system 10A. Further, theMME 13A transmits the held service identifier to thebase stations MME 13A is shared among a plurality of cooperate services, e.g., shared by a plurality of companies or the like is explained hereinafter. - For example, the
MME 13A holds a plurality of service identifiers relating to a plurality of cooperate services for which the connection is allowed, and thereby is shared among the plurality of cooperate services and the like. In this case, theMME 13A notifies thebase stations - Next, a specific structure of a service identifier is explained with reference to
FIG. 4 .FIG. 4 shows an example in which a service identifier is set in a sub-field of an MMEGI (MME Group ID) field included in a GUMMEI (Globally Unique MME Identifier). The GUMMEI is identification information for an MME specified in the 3GPP. Alternatively, the service identifier may be handled as an independent information element in the mobile communication system. - The GUMMEI is identification information that the MME 13 transmits to the
base station 30. The GUMMEI includes various information fields including fields for an MCC (Mobile Country Code), an MNC (Mobile Network Code), an MMEGI, and an MMEC (MME Code). In the MCC, a code for identifying a country is set. In the MNC, a code for identifying a telecommunications carrier is set. The MMEGI includes sub-fields in which a Service ID indicating a service identifier and a Pool ID are set. - The Pool ID is an identifier that is assigned to a plurality of MMEs in common. For example, a common Pool ID may be assigned to a plurality of MMEs disposed in a specific region. The plurality of MMEs to which a common Pool ID is assigned may be referred to a MME group. That is, different Pool IDs are assigned to a group of MMEs disposed in different regions, and the same Pool ID is assigned to a group of MMEs disposed in the same region.
- The MMEGI consists of, for example, 16 bits. When N bits (N is an integer no less than zero) of the 16 bits are used for the Service ID, the remaining bits (16-N bits) are assigned to the Pool ID.
- The Service ID is an identifier assigned to each corporate service. By assigning a Service ID to each core network system, a core network system used by a corporate service is specified. When one core network system is shared among a plurality of corporate services, Service IDs each of which is assigned to one of the plurality of corporate services are assigned to that core network system. That is, a core network system holds one or a plurality of Service IDs according to a corporate service(s) to which the connection is allowed.
- The MMEC is an identifier for uniquely identifying each of a plurality of MMEs to which a common Pool ID is assigned.
- The MME 13 transmits a GUMMEI with a Service ID set therein to the
base station 30. Thebase station 30 extracts the Service ID from the GUMMEI transmitted from the MME 13, associates the extracted GUMMEI with a core network system, and manages (or stores) the GUMMEI in the associated state. - An outline of a process for selecting a core network system, i.e., for selecting an MME performed by the
determination unit 34 of thebase station 30 is explained hereinafter with reference toFIG. 5 . In this figure, acore network system 10 includes one MME and acore network system 20 includes three MMEs. Thecore network system 10 includes an MME in which the MMEGI is 10/100 and the MMEC is 1. The MMEGI indicates “Service ID/Pool ID”. Therefore, in the MME of thecore network system 10, avalue 10 is assigned to the Service ID and avalue 100 is assigned to the Pool ID. - Similarly, the
core network system 20 includes: an MME in which the MMEGI is 20/100 and the MMEC is 1; an MME in which the MMEGI is 20/100 and the MMEC is 2; and an MME in which the MMEGI is 20/100 and the MMEC is 3. - Each MME notifies the
base station 30 of its MMEGI and MMEC. Thebase station 30 manages (or stores) the notified MMEGIs and MMECs. - Note that when the
base station 30 receives a connection request message in which avalue 20 is set as a service identifier from thecommunication terminal 40, thebase station 30 selects one of the three MMEs in which avalue 20 is set as the Service ID and transmits the connection request message to the selected MME. In this case, thebase station 30 may select one of the three MMEs in which avalue 20 is set as the Service ID by using Weight Factors. For example, thebase station 30 may selects an MME in the ascending order of the MMECs. Alternatively, thebase station 30 may acquire the processing load states of the MMEs in advance and select an MME having a smaller (or smallest) processing load. Thebase station 30 may select an MME by using other selection processes. Further, instead of using the configuration shown inFIG. 5 , the communication system may be configured so that an MME is shared among a plurality of corporate services. For example, one MME accommodates “MMEGI: 10/100, MMEC: 1” and “MMEGI: 20/100, MMEC: 1”. - Next, a flow of a service identifier transmission process according to the second exemplary embodiment of the present invention is explained with reference to
FIG. 6 . This example is explained by using an eNB (evolved NodeB) specified in the 3GPP as thebase station 30. The eNB is a base station in conformity with an LTE (Long Term Evolution) wireless scheme. - Firstly, the eNB transmits an S1 SETUP REQUEST message to an MME (S10). For example, upon power-on, the eNB transmits an S1 SETUP REQUEST message to an MME connected to that eNB. Note that the eNB may transmit an S1 SETUP REQUEST message to a plurality of MMEs.
- Next, the MME transmits an S1 SETUP RESPONSE message to the eNB (S11). The MME sets a GUMMEI in the S1 SETUP RESPONSE message. That is, the MME notifies the eNB of a Service ID by transmitting an S1 SETUP RESPONSE message to the eNB. When a plurality of Service IDs are assigned to the MME, the MME notifies the eNB of the plurality of Service IDs. The plurality of Service IDs may be transmitted from the MME to the eNB in the form of a list of Service IDs. Note that the outline of the S1 SETUP REQUEST message and the S1 SETUP RESPONSE message shown in
FIG. 6 is explained in Chapter 8.7.3 of TS36.413 V11.5.0 (2013-09), which is specifications in the 3GPP. In the communication system according to the second exemplary embodiment of the present invention, a Service ID is newly set in the S1 SETUP RESPONSE message specified in Chapter 8.7.3 of TS36.413 V11.5.0 (2013-09). - Next, a flow of a service identifier acquisition process according to the second exemplary embodiment of the present invention is explained with reference to
FIG. 7 . Firstly, theNW communication unit 31 of the eNB acquires a GUMMEI set in an S1 SETUP RESPONSE message (S21). Next, the serviceidentifier holding unit 32 extracts a service identifier (Service ID) set in a sub-field of the MMEGI of the GUMMEI (S22). Next, the serviceidentifier holding unit 32 holds the extracted Service ID (S23). - Next, a flow of a connection request message transfer process according to the second exemplary embodiment of the present invention is explained with reference to
FIG. 8 . - Firstly, the
determination unit 34 receives a connection request message transmitted from thecommunication terminal 40 through the terminal communication unit 33 (S31). Next, thedetermination unit 34 determines whether or not a Service ID is set as a service identifier in the connection request message (S32). Next, when thedetermination unit 34 determines that a Service ID is set in the connection request message, thedetermination unit 34 extracts that Service ID (S33). Next, thedetermination unit 34 determines whether or not the extracted Service ID matches a Service ID held in the service identifier holding unit 32 (S34). - When the
determination unit 34 determines that the Service ID included in the connection request message matches a Service ID held in the serviceidentifier holding unit 32, thedetermination unit 34 transmits the connection request message to an MME of a core network system associated with the Service ID included in the connection request message (S36). When thedetermination unit 34 determines that the Service ID included in the connection request message does not match any Service ID held in the serviceidentifier holding unit 32 or when thedetermination unit 34 determines that no Service ID is set in the connection request message transmitted from thecommunication terminal 40 in the step S32, thedetermination unit 34 transmits the connection request message to a predetermined Default MME (S35). Information about the Default MME may be stored in advance in a memory or the like disposed inside thebase station 30, or may be set in an S1 SETUP RESPONSE or the like and sent to thebase station 30. - A specific example of a connection request message transmitted from the
communication terminal 40 in the step S31 is explained hereinafter with reference toFIG. 9 .FIG. 9 shows a state where a Service ID is set in an RRC Connection Request message transmitted from thecommunication terminal 40 to the eNB. In this way, thecommunication terminal 40 notifies the eNB of the Service ID. InFIG. 9 , an example case where the Service ID has an 8-bit length is shown. - As explained above, by using the communication system according to the second exemplary embodiment of the present invention, the base station (eNB) can connect a communication terminal for which a specific service identifier is set with a specific core network system. As a result, data relating to the specific communication terminal is transmitted through the specific core network system. Therefore, no data relating to the specific communication terminal flows into the other core network systems. Accordingly, even when the amount of data relating to the specific communication terminal increases, the other core network systems receive no adverse effect therefrom.
- Further, since the service identifier is set in a sub-field of the MMEGI of the GUMMEI, which has been already specified in the 3GPP, the above-described configuration can be implemented without substantially changing the structure of existing messages.
- Further, by assigning a core network system to each corporate service, a mobile telecommunications carrier can design a network while estimating the amount of traffic only for ordinary users such as users of smart phones and users of mobile phone terminals. That is, a mobile telecommunications carrier can design a mobile communication network without taking account of the amount of traffic relating to communication terminals and the like that connect to core network systems each of which is assigned to a respective one of corporate services.
- Further, each company can design a core network system according to the characteristics of communication terminals that connect to that core network system. For example, when only communication terminals that do not move connect to a core network system, the cost for the core network system can be reduced by constructing a core network system in which the movement management function is omitted. Further, when a number of communication terminals that frequently move connect to a core network system, the company can construct a core network system having high quality by reinforcing the MME, the SGW, and the PGW.
- Next, a configuration example of a communication system according to a third exemplary embodiment of the present invention is explained with reference to
FIG. 10 . In this figure, a case where thecommunication terminal 40 performs handover involving a change of an MME is explained. - A communication system shown in
FIG. 10 includes acore network system 20, acore network system 50, abase station 30, abase station 35, and a DNS (Domain Name System)server 60. Thecore network system 20 includes anMME 21 and anMME 22. Further, thecore network system 50 includes anMME 51. - Further,
FIG. 10 shows a state where thecommunication terminal 40 moves from a communication area formed by thebase station 30 to a communication area formed by thebase station 35. Thecommunication terminal 40 moves while communicating with thebase station 30 and thus performs handover. - A Service ID assigned to the
MMEs value 20. Further, the Pool ID of theMME 21 has avalue 100 and the Pool ID of theMME 22 has a value 200. That is, theMMEs MME 51 has avalue 50 and its Pool ID has avalue 100. TheMME 51 manages a region corresponding to the combined regions of theMMEs - Next, a connection configuration of the communication system shown in
FIG. 10 is explained. TheMME 21 manages thebase station 30. That is, theMME 21 is connected to thebase station 30. TheMME 22 is connected to thebase station 35. Further, theMME 51 is connected to thebase stations MMEs DNS server 60. - Each of the
base stations core network system communication terminal 40. -
FIG. 10 shows a state where thecommunication terminal 40 uses avalue 20 as its Service ID and connects to theMME 21 through thebase station 30. In the above-described state, thecommunication terminal 40 moves to the communication area formed by thebase station 35. In this case, since the Service ID assigned to theMME 21 connected to thebase station 30 has avalue 20, theMME 22, to which thevalue 20 is assigned as its Service ID, serves as the MME that manages thebase station 35 after thecommunication terminal 40 has moved. Therefore, when thecommunication terminal 40 is handed over, the MME to which thecommunication terminal 40 connects also changes from theMME 21 to theMME 22. Note that the MMEs to which thebase station 35 connects includes theMME 51 in addition to theMME 22. However, since thecommunication terminal 40 had been connected to theMME 21 by using thevalue 20 as its Service ID before the handover, the MME to which thecommunication terminal 40 connects is changed to theMME 22 that has a Service ID having the same value as that of theMME 21. - The
MME 22, which manages thebase station 35 to which thecommunication terminal 40 has been handed over, acquires subscriber information of thecommunication terminal 40 from theMME 21. That is, theMME 21 transmits the subscriber information of thecommunication terminal 40 to theMME 22, which manages thebase station 35 to which thecommunication terminal 40 has moved. - A flow of a process for selecting the
MME 22 as the destination of the subscriber information performed by theMME 21 is explained hereinafter with reference toFIG. 11 . Firstly, theMME 21 receives a handover (HO) request message relating to thecommunication terminal 40 from the base station 30 (S41). Next, theMME 21 transmits a message for inquiring the MME at the HO destination of thecommunication terminal 40 to the DNS server 60 (S42). For example, theMME 21 may transmit a message to theDNS server 60 in order to inquire the MME connected to thebase station 35 to which thecommunication terminal 40 has moved. In this process, for example, theMME 21 may transmit area information of thebase station 35 to theDNS server 60. - The
DNS server 60 manages (or stores), for example, information of areas and MMEs managing those areas in a state where they are associated with each other. Note that theDNS server 60 manages MMEs by using FQDNs (Fully Qualified Domain Names). TheDNS server 60 may also manage (or stores) Service IDs possessed by MMEs by incorporating those Service IDs into FQDNs. For example, since avalue 20 is assigned to theMME 22 as a Service ID, theDNS server 60 may define the FQDN of theMME 22 as “sid20mmec1.epc. . . . ” and manages (or stores) the defined FQSN. Further, theDNS server 60 may define the FQDN of theMME 51 as “sid50mmec1.epc. . . . ” and manages (or stores) the defined FQSN. - In response to the message transmitted by the
MME 21 for inquiring the MME at the HO destination by using theService ID 20 assigned to thecommunication terminal 40 in the step S42, theMME 21 receives a response massage including “sid20mmec1.epc. . . . ” and “sid50mmec1.epc. . . . ” from the DNS server 60 (S43). - Next, the
MME 21 determines whether or not there is an FQDN including a Service ID that matches the Service ID assigned to theMME 21 itself (S44). When theMME 21 determines that there is an FQDN including a Service ID that matches the Service ID assigned to theMME 21 itself, theMME 21 transmits subscriber information of thecommunication terminal 40 to theMME 22 in which an FQDN including the same Service ID as the Service ID assigned to theMME 21 itself is set (S45). When theMME 21 determines that there is no FQDN including a Service ID that matches the Service ID assigned to theMME 21 itself, theMME 21 selects one of the MMEs in which FQSNs notified from theDNS server 60 are set and transmits subscriber information of thecommunication terminal 40 to the selected MME (S46). - As explained above, by using the communication system according to the third exemplary embodiment of the present invention, even when the communication terminal performs handover involving a change of an MME, the former MME can transmit subscribe information of the communication terminal to the destination MME by using a service identifier.
- Further, although an operation of the
communication terminal 40 that is performed when thecommunication terminal 40 is handed over is explained in the third exemplary embodiment of the present invention, it is also possible to take over subscriber information between MMEs in a similar manner at the time of TAU (Tracking Area Update) of thecommunication terminal 40 involving a change of an MME. However, in the case of the TAU, theMME 22, which manages thebase station 35 to which thecommunication terminal 40 moves, selects theMME 21, which manages thebase station 30 from which thecommunication terminal 40 moves, and acquires subscriber information from theMME 21. - In this case, similarly to the processes explained above with reference to
FIGS. 10 and 11 , theMME 22 transmits an inquiring message to theDNS server 60 and acquires information about the MME connected to thebase station 30. TheMME 22 selects theMME 21 by using a Service ID as in the case of the handover operation. - Next, a configuration example of a
core network system 70 according to a fourth exemplary embodiment of the present invention is explained with reference toFIG. 12 . Thecore network system 70 includes an SGSN (Serving GPRS Support Node) 71 and a GGSN (Gateway GPRS Support Node) 72. Each of the SGSN 71 and theGGSN 72 is a node device specified in the 3GPP. Each of the SGSN 71 and theGGSN 72 transmits/receives user data relating to thecommunication terminal 40 and also transmits/receives control data relating to thecommunication terminal 40. - The SGSN 71 is connected to the
base station 30. That is, in contrast to the above-explained second and third exemplary embodiments in which thebase station 30 selects an MME, thebase station 30 selects the SGSN 71 inFIG. 12 . Similarly to the first to third exemplary embodiments, thebase station 30 selects the SGSN 71 by using a service identifier. - As explained above, by using the communication system shown in
FIG. 12 , thebase station 30 can select the SGSN 71 by using a service identifier even in the so-called “second generation system” or “third generation system” including the SGSN 71 and theGGSN 72. - Although the present invention is described as a hardware configuration in the above-described exemplary embodiments, the present invention is not limited to the hardware configurations. In the present invention, the processes in the base station and the MME can be also implemented by causing a CPU (Central Processing Unit) to execute a computer program.
- In the above-described examples, the program can be stored in various types of non-transitory computer readable media and thereby supplied to computers. The non-transitory computer readable media includes various types of tangible storage media. Examples of the non-transitory computer readable media include a magnetic recording medium (such as a flexible disk, a magnetic tape, and a hard disk drive), a magneto-optic recording medium (such as a magneto-optic disk), a CD-ROM (Read Only Memory), a CD-R, and a CD-R/W, and a semiconductor memory (such as a mask ROM, a PROM (Programmable ROM), an EPROM (Erasable PROM), a flash ROM, and a RAM (Random Access Memory)). Further, the program can be supplied to computers by using various types of transitory computer readable media. Examples of the transitory computer readable media include an electrical signal, an optical signal, and an electromagnetic wave. The transitory computer readable media can be used to supply programs to computer through a wire communication path such as an electrical wire and an optical fiber, or wireless communication path.
- Note that the invention is not limited to the above-described exemplary embodiments and various changes may be made therein without departing from the spirit and scope of the present invention.
- Although the present invention is explained above with reference to exemplary embodiments, the present invention is not limited to the above-described exemplary embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the invention.
- This application is based upon and claims the benefit of priority from Japanese patent applications No. 2013-202034, filed on Sep. 27, 2013, the disclosure of which is incorporated herein in its entirety by reference.
-
- 10 CORE NETWORK SYSTEM
- 11 SGW
- 12 PGW
- 13 MME
- 20 CORE NETWORK SYSTEM
- 21 MME
- 22 MME
- 30 BASE STATION
- 31 NW COMMUNICATION UNIT
- 32 SERVICE IDENTIFIER HOLDING UNIT
- 33 TERMINAL COMMUNICATION UNIT
- 34 DETERMINATION UNIT
- 35 BASE STATION
- 40 COMMUNICATION TERMINAL
- 50 CORE NETWORK SYSTEM
- 51 MME
- 60 DNS SERVER
- 70 CORE NETWORK SYSTEM
- 71 SGSN
- 72 GGSN
Claims (13)
1-19. (canceled)
20. A mobile communication system comprising:
a terminal (UE);
a base station (eNB);
a dedicated core network that includes an MME (Mobility Management Entity) and is identified by MMEGI (MME Group ID) which identifies the MME; and
a DNS (Domain Name Server) server;
wherein when the terminal performs a handover, the MME for a handover source in the dedicated core network receives a handover required message from the base station, makes inquires to the DNS server, and selects the MME for a handover target in the dedicated core network.
21. A mobile communication system comprising:
a terminal (UE);
a base station;
a dedicated core network that includes an SGSN (Serving GPRS Support Node) and is identified by an ID which identifies the SGSN; and
a DNS (Domain Name Server) server;
wherein when the terminal performs a handover, the SGSN for a handover source in the dedicated core network receives a handover required message from the base station, makes inquires to the DNS server, and selects the SGSN for a handover target in the dedicated core network.
22. An MME (Mobility Management Entity) in a mobile communication system including a terminal (UE), a base station (eNB) and a DNS (Domain Name Server) server, comprising:
when a terminal (UE) performs a handover, the MME for a handover source in the dedicated core network that is identified by MMEGI (MME Group ID) which identifies the MME comprising:
a unit configured to receive a handover required message from the base station (eNB);
a unit configured to make inquires to the DNS server; and
a unit configured to select the MME for a handover target in the dedicated core network.
23. An SGSN (Serving GPRS Support Node) in a mobile communication system including a terminal (UE), a base station (eNB) and a DNS (Domain Name Server) server, comprising:
when a terminal (UE) performs a handover, the SGSN for a handover source in the dedicated core network that is identified by an ID which identifies the SGSN comprising:
a unit configured to receive a handover required message from the base station;
a unit configured to make inquires to the DNS server; and
a unit configured to select the SGSN for a handover target in the dedicated core network.
24. A terminal (UE) in a mobile communication system comprising:
a unit configured to have an identifier which identifies a core network; and
a unit configured to provide an MME (Mobile Management Entity) with the identifier via an base station (eNB);
wherein when the terminal performs a handover, the MME for a handover source in a dedicated core network that is identified by MMEGI (MME Group ID) which identifies the MME receives a handover required message from a base station and selects the MME for a handover target in the dedicated core network based on the identifier.
25. A terminal (UE) in a mobile communication system comprising:
a unit configured to have an identifier which identifies a core network; and
a unit configured to provide an SGSN (Serving GPRS Support Node) with the identifier via an base station;
wherein when the terminal performs a handover, the SGSN for a handover source in a dedicated core network that is identified by an ID which identifies the SGSN based on the identifier receives a handover required message from a base station and selects the SGSN for a handover target in the dedicated core network based on the identifier.
26. A communication method of a mobile communication system including a terminal (UE), a base station (eNB), a DNS (Domain Name Server) server, and an MME (Mobile Management Entity) comprising:
when the terminal performs a handover,
receiving, by the MME for a handover source in a dedicated core network that is identified by MMEGI (MME Group ID) which identifies the MME a handover required message from said base station;
making inquires, by the MME for the handover source, to the DNS server; and
selecting, by the MME for the handover source, the MME for a handover target in the dedicated core network.
27. A communication method of a mobile communication system including a terminal (UE), a base station (eNB), a DNS (Domain Name Server) server, and an SGSN (Serving GPRS Support Node) comprising:
when the terminal performs a handover,
receiving, by the SGSN for a handover source in a dedicated core network that is identified by an ID which identifies the SGSN a handover required message from said base station;
making inquires, by the SGSN for the handover source, to the DNS server; and
selecting, by the SGSN for the handover source, the SGSN for a handover target in the dedicated core network.
28. A communication method of an MME (Mobility Management Entity) including a terminal (UE), a base station (eNB) and a DNS (Domain Name Server) server in a mobile communication system comprising:
when a terminal (UE) performs a handover,
receiving, by the MME for a handover source in a dedicated core network that is identified by MMEGI (MME Group ID) which identifies the MME a handover required message from the base station;
making inquires, by the MME for the handover source, to the DNS server; and
selecting, by the MME for the handover source, the MME for a handover target in the dedicated core network.
29. A communication method of an SGSN (Serving GPRS Support Node) including a terminal (UE), a base station and a DNS (Domain Name Server) server in a mobile communication system comprising:
when a terminal (UE) performs a handover,
receiving, by the SGSN for a handover source in a dedicated core network that is identified by an ID which identifies the SGSN a handover required message from the base station;
making inquires, by the SGSN for the handover source, to the DNS server; and
selecting, by the SGSN for the handover source, the SGSN for a handover target in the dedicated core network.
30. A communication method of a terminal (UE) in a mobile communication system comprising:
having an identifier which identifies a core network; and
providing an MME (Mobile Management Entity) with the identifier via an base station (eNB);
wherein when the terminal performs a handover, the MME for a handover source in a dedicated core network that is identified by MMEGI (MME Group ID) which identifies the MME receives a handover required message from a base station and selects the MME for a handover target in the dedicated core network based on the identifier.
31. A communication method of a terminal (UE) in a mobile communication system comprising:
having an identifier which identifies a core network; and
providing an SGSN (Serving GPRS Support Node) with the identifier via an base station;
wherein when the terminal performs a handover, the SGSN for a handover source in a dedicated core network that is identified by an ID which identifies the SGSN based on the identifier receives a handover required message from a base station and selects the SGSN for a handover target in the dedicated core network based on the identifier.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013-202034 | 2013-09-27 | ||
JP2013202034 | 2013-09-27 | ||
PCT/JP2014/004628 WO2015045296A2 (en) | 2013-09-27 | 2014-09-09 | Communication system, base station, communication method, and non-transitory computer readable medium storing program |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/004628 A-371-Of-International WO2015045296A2 (en) | 2013-09-27 | 2014-09-09 | Communication system, base station, communication method, and non-transitory computer readable medium storing program |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/529,556 Continuation US20190357104A1 (en) | 2013-09-27 | 2019-08-01 | Communication system, base station, communication method, and non- transitory computer readable medium storing program |
Publications (1)
Publication Number | Publication Date |
---|---|
US20160219476A1 true US20160219476A1 (en) | 2016-07-28 |
Family
ID=51660523
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/023,784 Abandoned US20160219476A1 (en) | 2013-09-27 | 2014-09-09 | Communication system, base station, communication method, and non-transitory computer readable medium storing program |
US16/529,556 Abandoned US20190357104A1 (en) | 2013-09-27 | 2019-08-01 | Communication system, base station, communication method, and non- transitory computer readable medium storing program |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/529,556 Abandoned US20190357104A1 (en) | 2013-09-27 | 2019-08-01 | Communication system, base station, communication method, and non- transitory computer readable medium storing program |
Country Status (13)
Country | Link |
---|---|
US (2) | US20160219476A1 (en) |
EP (2) | EP3050346A2 (en) |
JP (3) | JP6256602B2 (en) |
KR (3) | KR102009614B1 (en) |
CN (3) | CN110267326A (en) |
BR (1) | BR112016006125B1 (en) |
CL (1) | CL2016000697A1 (en) |
MX (1) | MX371339B (en) |
PH (1) | PH12016500479A1 (en) |
RU (3) | RU2671966C1 (en) |
UA (1) | UA114156C2 (en) |
WO (1) | WO2015045296A2 (en) |
ZA (3) | ZA201601730B (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160066230A1 (en) * | 2006-08-15 | 2016-03-03 | Huawei Technologies Co., Ltd. | Method and system for transferring user equipment in mobile communication system |
US20170311245A1 (en) * | 2014-10-06 | 2017-10-26 | Sharp Kabushiki Kaisha | Base station device, terminal device, location management device, and control method |
US20180270745A1 (en) * | 2015-11-19 | 2018-09-20 | Sk Telecom Co., Ltd. | Method and apparatus for selecting core network in mobile communication system |
WO2018217510A1 (en) * | 2017-05-26 | 2018-11-29 | Sprint Communications Company L.P. | Role-based attachment to optimal wireless network cores in a multi-role wireless communication network |
US20180343582A1 (en) * | 2016-01-18 | 2018-11-29 | Huawei Technologies Co., Ltd. | Congestion control method and apparatus |
US20190045409A1 (en) * | 2016-01-27 | 2019-02-07 | Nokia Solutions And Networks Oy | Method and apparatus for implementing mobile edge application session connectivity and mobility |
US20190141583A1 (en) * | 2016-07-01 | 2019-05-09 | Huawei Technologies Co., Ltd. | Handover method and apparatus |
US11197198B2 (en) * | 2019-06-17 | 2021-12-07 | At&T Intellectual Property I, L.P. | Method, system, and computer program for automated offloading of subscribers during mobility management equipment failures |
US11696113B2 (en) | 2015-10-09 | 2023-07-04 | Nec Corporation | Dedicated core networks (DCN) selection |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104780623A (en) * | 2015-04-16 | 2015-07-15 | 中兴通讯股份有限公司 | Connection control method and device |
CN106304246A (en) * | 2015-05-11 | 2017-01-04 | 中兴通讯股份有限公司 | A kind of cut-in method and corresponding access node, terminal and communication network |
US10524171B2 (en) * | 2015-06-16 | 2019-12-31 | Qualcomm Incorporated | Reselection between regular and dedicated core networks |
CN106358270A (en) * | 2015-07-17 | 2017-01-25 | 中兴通讯股份有限公司 | Special core network selection method and device |
CN106488538B (en) * | 2015-08-24 | 2019-12-20 | 电信科学技术研究院 | Special network selection method, terminal, access network node and core network node |
WO2017045189A1 (en) | 2015-09-18 | 2017-03-23 | 华为技术有限公司 | Method, device and system for selecting core network |
US10425887B2 (en) * | 2015-11-10 | 2019-09-24 | Blackberry Limited | Gateway selection controlled by network |
WO2017114800A1 (en) * | 2015-12-30 | 2017-07-06 | Deutsche Telekom Ag | Communication system for the communication in a communication network having sub-networks |
WO2017162295A1 (en) * | 2016-03-24 | 2017-09-28 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and node for handling re-selection of a serving node to serve a ue |
US11039502B1 (en) * | 2020-02-24 | 2021-06-15 | Verizon Patent And Licensing Inc. | Systems and methods for establishing and modifying user plane communications |
US11776270B2 (en) | 2021-01-14 | 2023-10-03 | International Business Machines Corporation | Telecommunication network monitoring |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2010165112A (en) * | 2009-01-14 | 2010-07-29 | National Institute Of Information & Communication Technology | Sensor information system for mobile terminal |
CN102056130A (en) * | 2009-11-02 | 2011-05-11 | 中兴通讯股份有限公司 | Method, system and device for selecting target MME during mobile terminal switching |
US20120164979A1 (en) * | 2009-06-30 | 2012-06-28 | Panasonic Corporation | Inter-vplmn handover via a handover proxy node |
US20120177005A1 (en) * | 2011-01-06 | 2012-07-12 | Samsung Electronics Co., Ltd. | Method and apparatus for supporting user equipment mobility in a wireless communication system |
US20140033438A1 (en) * | 2012-08-03 | 2014-02-06 | Fu-Chieng Chen | Ergonomical pillow for head rest |
US20160057681A1 (en) * | 2013-05-03 | 2016-02-25 | Huawei Technologies Co., Ltd. | Load Balancing Method and Device |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1820361A1 (en) | 2004-12-08 | 2007-08-22 | Telefonaktiebolaget LM Ericsson (publ) | Method and system for improved handover of mobile stations to unlicensed mobile access networks |
WO2007117190A1 (en) | 2006-04-12 | 2007-10-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and arrangements for providing information regarding gan coverage in the cellular radio communication network |
CN101610504B (en) * | 2008-06-18 | 2012-08-08 | 上海华为技术有限公司 | Method and device for accessing and obtaining user equipment context and user equipment identification |
JP4493707B2 (en) * | 2008-08-07 | 2010-06-30 | 株式会社エヌ・ティ・ティ・ドコモ | Mobile communication method, mobile station and exchange |
EP2382826B1 (en) * | 2009-01-23 | 2017-11-29 | Telefonaktiebolaget LM Ericsson (publ) | Method and arrangement in a communication network |
WO2010110711A1 (en) * | 2009-03-27 | 2010-09-30 | Telefonaktiebolaget L M Ericsson (Publ) | Overlaod avoidance with home node b gateway (henb gw) in lte |
EP2309702B1 (en) * | 2009-10-12 | 2019-02-20 | LG Electronics Inc. | Mobile terminated communication method |
CN102045695B (en) * | 2009-10-23 | 2014-03-12 | 中兴通讯股份有限公司 | Method and system for acquiring information on MTC (Microsoft Technology Center) server address |
US8307097B2 (en) * | 2009-12-18 | 2012-11-06 | Tektronix, Inc. | System and method for automatic discovery of topology in an LTE/SAE network |
CN102413450B (en) * | 2010-09-21 | 2014-12-10 | 中兴通讯股份有限公司 | Access control method of machine type communication terminal and system thereof |
EP2668796B1 (en) * | 2011-04-06 | 2015-06-10 | NEC Europe Ltd. | Method and a system for distributing of user equipment context in an evolved packet system |
CN102333294B (en) * | 2011-09-23 | 2014-04-09 | 电信科学技术研究院 | Method and device for renewing terminal reachable state information based on detaching process |
CN108924813A (en) * | 2011-09-30 | 2018-11-30 | 日本电气株式会社 | System, terminal, core network node, radio access network node and method |
JP2013150213A (en) * | 2012-01-20 | 2013-08-01 | Sharp Corp | Communication system, gateway device and communication method |
JP5841877B2 (en) | 2012-03-29 | 2016-01-13 | ヤンマー株式会社 | Combine |
JP6196103B2 (en) * | 2013-09-13 | 2017-09-13 | 株式会社Nttドコモ | Mobile communication system, network node, and mobile communication method |
-
2014
- 2014-09-09 KR KR1020187027427A patent/KR102009614B1/en active IP Right Grant
- 2014-09-09 RU RU2017126049A patent/RU2671966C1/en active
- 2014-09-09 KR KR1020167007992A patent/KR101796405B1/en active IP Right Grant
- 2014-09-09 UA UAA201603057A patent/UA114156C2/en unknown
- 2014-09-09 JP JP2016518222A patent/JP6256602B2/en active Active
- 2014-09-09 KR KR1020177031736A patent/KR101903928B1/en active IP Right Grant
- 2014-09-09 EP EP14780908.1A patent/EP3050346A2/en not_active Withdrawn
- 2014-09-09 RU RU2016111120A patent/RU2016111120A/en not_active Application Discontinuation
- 2014-09-09 CN CN201910275321.5A patent/CN110267326A/en active Pending
- 2014-09-09 BR BR112016006125-0A patent/BR112016006125B1/en active IP Right Grant
- 2014-09-09 WO PCT/JP2014/004628 patent/WO2015045296A2/en active Application Filing
- 2014-09-09 US US15/023,784 patent/US20160219476A1/en not_active Abandoned
- 2014-09-09 MX MX2016003047A patent/MX371339B/en active IP Right Grant
- 2014-09-09 CN CN201910275344.6A patent/CN110225574B/en active Active
- 2014-09-09 CN CN201480053021.8A patent/CN105580444B/en active Active
- 2014-09-09 EP EP19194339.8A patent/EP3598791A1/en not_active Withdrawn
-
2016
- 2016-03-11 PH PH12016500479A patent/PH12016500479A1/en unknown
- 2016-03-14 ZA ZA2016/01730A patent/ZA201601730B/en unknown
- 2016-03-24 CL CL2016000697A patent/CL2016000697A1/en unknown
- 2016-09-06 JP JP2016173372A patent/JP6245327B2/en active Active
-
2017
- 2017-11-07 ZA ZA2017/07519A patent/ZA201707519B/en unknown
- 2017-12-06 JP JP2017234317A patent/JP2018082443A/en active Pending
-
2018
- 2018-04-13 ZA ZA2018/02436A patent/ZA201802436B/en unknown
- 2018-08-07 RU RU2018128788A patent/RU2695990C1/en active
-
2019
- 2019-08-01 US US16/529,556 patent/US20190357104A1/en not_active Abandoned
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2010165112A (en) * | 2009-01-14 | 2010-07-29 | National Institute Of Information & Communication Technology | Sensor information system for mobile terminal |
US20120164979A1 (en) * | 2009-06-30 | 2012-06-28 | Panasonic Corporation | Inter-vplmn handover via a handover proxy node |
CN102056130A (en) * | 2009-11-02 | 2011-05-11 | 中兴通讯股份有限公司 | Method, system and device for selecting target MME during mobile terminal switching |
US20120177005A1 (en) * | 2011-01-06 | 2012-07-12 | Samsung Electronics Co., Ltd. | Method and apparatus for supporting user equipment mobility in a wireless communication system |
US20140033438A1 (en) * | 2012-08-03 | 2014-02-06 | Fu-Chieng Chen | Ergonomical pillow for head rest |
US20160057681A1 (en) * | 2013-05-03 | 2016-02-25 | Huawei Technologies Co., Ltd. | Load Balancing Method and Device |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160066230A1 (en) * | 2006-08-15 | 2016-03-03 | Huawei Technologies Co., Ltd. | Method and system for transferring user equipment in mobile communication system |
US11678240B2 (en) | 2006-08-15 | 2023-06-13 | Huawei Technologies Co., Ltd. | Method and system for transferring user equipment in mobile communication system |
US9894576B2 (en) * | 2006-08-15 | 2018-02-13 | Huawei Technologies Co., Ltd. | Method and system for transferring user equipment in mobile communication system |
US10412646B2 (en) | 2006-08-15 | 2019-09-10 | Huawei Technologies Co., Ltd. | Method and system for transferring user equipment in mobile communication system |
US11012907B2 (en) | 2006-08-15 | 2021-05-18 | Huawei Technologies Co., Ltd. | Method and system for transferring user equipment in mobile communication system |
US20190182761A1 (en) * | 2014-10-06 | 2019-06-13 | Sharp Kabushiki Kaisha | Base station device, terminal device, location management device, and control method |
US11770761B2 (en) * | 2014-10-06 | 2023-09-26 | Sharp Kabushiki Kaisha | Base station device, terminal device, location management device, and control method |
US10231176B2 (en) * | 2014-10-06 | 2019-03-12 | Sharp Kabushiki Kaisha | Base station device, terminal device, location management device, and control method |
US20170311245A1 (en) * | 2014-10-06 | 2017-10-26 | Sharp Kabushiki Kaisha | Base station device, terminal device, location management device, and control method |
US11696113B2 (en) | 2015-10-09 | 2023-07-04 | Nec Corporation | Dedicated core networks (DCN) selection |
US11792728B2 (en) | 2015-11-19 | 2023-10-17 | Sk Telecom Co., Ltd. | Method and apparatus for selecting core network in mobile communication system |
US20180270745A1 (en) * | 2015-11-19 | 2018-09-20 | Sk Telecom Co., Ltd. | Method and apparatus for selecting core network in mobile communication system |
US10609636B2 (en) * | 2015-11-19 | 2020-03-31 | Sk Telecom Co., Ltd. | Method and apparatus for selecting core network in mobile communication system |
US11265809B2 (en) | 2015-11-19 | 2022-03-01 | Sk Telecom Co., Ltd. | Method and apparatus for selecting core network in mobile communication system |
US20180343582A1 (en) * | 2016-01-18 | 2018-11-29 | Huawei Technologies Co., Ltd. | Congestion control method and apparatus |
US20190045409A1 (en) * | 2016-01-27 | 2019-02-07 | Nokia Solutions And Networks Oy | Method and apparatus for implementing mobile edge application session connectivity and mobility |
US10959132B2 (en) * | 2016-07-01 | 2021-03-23 | Huawei Technologies Co., Ltd. | Handover method and apparatus |
US20190141583A1 (en) * | 2016-07-01 | 2019-05-09 | Huawei Technologies Co., Ltd. | Handover method and apparatus |
US10686662B2 (en) | 2017-05-26 | 2020-06-16 | Sprint Communications Company L.P. | Role-based attachment to optimal wireless network cores in a multi-role wireless communication network |
WO2018217510A1 (en) * | 2017-05-26 | 2018-11-29 | Sprint Communications Company L.P. | Role-based attachment to optimal wireless network cores in a multi-role wireless communication network |
US11197198B2 (en) * | 2019-06-17 | 2021-12-07 | At&T Intellectual Property I, L.P. | Method, system, and computer program for automated offloading of subscribers during mobility management equipment failures |
Also Published As
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20190357104A1 (en) | Communication system, base station, communication method, and non- transitory computer readable medium storing program | |
US11838969B2 (en) | Method for accessing local network, and related device | |
CN104768168B (en) | Control method, controller and MME (mobility management entity) of user tracking area | |
JP7145197B2 (en) | Handover method, device and system | |
KR102244539B1 (en) | Method and apparatus for acquiring location information of user equipment based on radio unit | |
US10045199B2 (en) | Mobile communication system, mobile station, switching station, and location registration method for mobile station | |
US11233883B2 (en) | Systems and methods for acquiring an internet protocol network address of a user equipment in networks | |
WO2017169513A1 (en) | Communication control method and communication system | |
US10820357B2 (en) | Connecting to a packet data network (PDN) based on priority | |
JP2017017379A (en) | Communication connection method and communication system | |
JP6603090B2 (en) | Wireless communication system and method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NEC CORPORATION, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ONISHI, KOJI;TAMURA, TOSHIYUKI;REEL/FRAME:038062/0820 Effective date: 20160205 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: ADVISORY ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |