WO2015178032A1 - 通信装置、通信方法、通信システムおよびプログラム - Google Patents
通信装置、通信方法、通信システムおよびプログラム Download PDFInfo
- Publication number
- WO2015178032A1 WO2015178032A1 PCT/JP2015/002586 JP2015002586W WO2015178032A1 WO 2015178032 A1 WO2015178032 A1 WO 2015178032A1 JP 2015002586 W JP2015002586 W JP 2015002586W WO 2015178032 A1 WO2015178032 A1 WO 2015178032A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- virtual
- terminal
- communication
- network node
- Prior art date
Links
- 238000004891 communication Methods 0.000 title claims abstract description 249
- 238000000034 method Methods 0.000 title claims description 55
- 238000012545 processing Methods 0.000 claims abstract description 36
- 230000008569 process Effects 0.000 claims description 7
- 238000005516 engineering process Methods 0.000 abstract description 3
- 238000007726 management method Methods 0.000 description 37
- 238000010586 diagram Methods 0.000 description 31
- 230000004044 response Effects 0.000 description 29
- 238000012546 transfer Methods 0.000 description 17
- 230000005540 biological transmission Effects 0.000 description 7
- 238000004886 process control Methods 0.000 description 4
- 230000011664 signaling Effects 0.000 description 4
- 241001522296 Erithacus rubecula Species 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 3
- 230000010267 cellular communication Effects 0.000 description 3
- 238000013508 migration Methods 0.000 description 3
- 230000005012 migration Effects 0.000 description 3
- 238000010276 construction Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004913 activation Effects 0.000 description 1
- 238000001994 activation Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- 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/084—Load balancing or load distribution among network function virtualisation [NFV] entities; among edge computing entities, e.g. multi-access edge computing
-
- 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
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
Definitions
- the present invention is based on the priority claim of Japanese Patent Application: Japanese Patent Application No. 2014-106616 filed on May 23, 2014, the entire contents of which are incorporated herein by reference. It shall be.
- the present invention relates to a communication device, a communication method, a communication system, and a program used for communication.
- Patent Document 1 discloses a technique for switching between a plurality of types of wireless systems in accordance with network congestion. If the terminal can use both cellular communication and wireless LAN (Local Area Network) as a wireless system, congestion determination can be performed and an optimal wireless system can be selected. For example, by switching cellular communication traffic to a wireless LAN network, congestion of the cellular network can be reduced.
- cellular communication and wireless LAN (Local Area Network) as a wireless system
- congestion determination can be performed and an optimal wireless system can be selected. For example, by switching cellular communication traffic to a wireless LAN network, congestion of the cellular network can be reduced.
- wireless LAN Local Area Network
- Patent Document 1 the network switching technique disclosed in Patent Document 1 is limited to a case where a terminal can use a plurality of different wireless systems. Therefore, for example, when a plurality of types of wireless systems cannot be accessed depending on the stay location of the terminal, it is not possible to perform offloading of communication traffic, and it is not possible to achieve network congestion reduction.
- an object of the present invention is to provide a new traffic offload technology.
- the communication apparatus of the present invention includes a first network node that executes predetermined signal processing in a first network, and a second network node that operates a function of the first network node by a virtual machine in a second network, A first means for selecting the second network node with respect to a terminal capable of autonomous communication with a communication partner device from a plurality of network nodes, and communication data relating to the terminal selected as the second A second means for transmitting to the network node.
- the communication method of the present invention includes a first network node that executes predetermined signal processing in a first network, and a second network node that operates a function of the first network node by a virtual machine in a second network,
- the second network node is selected for a terminal capable of autonomous communication with a communication partner device from a plurality of network nodes, and communication data related to the terminal is transmitted to the selected second network node To do.
- the communication system of the present invention is a communication system including a communication device that processes communication data related to a terminal, and the communication device includes a first network node that executes predetermined signal processing in a first network, and a second network node.
- the program according to the present invention includes a first network node that executes predetermined signal processing in a first network and a second network that operates the function of the first network node in a second network by a virtual machine.
- FIG. 1 is a system configuration diagram showing an example of a communication system according to the first embodiment of the present invention.
- FIG. 2 is a block diagram illustrating an example of a schematic functional configuration of the base station according to the first embodiment.
- FIG. 3 is a block diagram illustrating an example of a schematic functional configuration of the terminal according to the first embodiment.
- FIG. 4 is a sequence diagram illustrating an operation example of the communication system according to the first embodiment.
- FIG. 5 is a system configuration diagram showing an example of a communication system according to the second embodiment of the present invention.
- FIG. 6 is a sequence diagram illustrating a first operation example of the communication system according to the second embodiment.
- FIG. 1 is a system configuration diagram showing an example of a communication system according to the first embodiment of the present invention.
- FIG. 2 is a block diagram illustrating an example of a schematic functional configuration of the base station according to the first embodiment.
- FIG. 3 is a block diagram illustrating an example of a schematic functional configuration of the terminal according to the first embodiment
- FIG. 7 is a sequence diagram illustrating an operation related to a non-MTC device in the second operation example of the communication system according to the second embodiment.
- FIG. 8 is a sequence diagram showing operations related to the MTC device in the second operation example of the communication system according to the second embodiment.
- FIG. 9 is a sequence diagram showing an operation of identifying the MME terminal type in the second operation example of the communication system according to the second embodiment.
- FIG. 10 is a block diagram illustrating an example of a schematic functional configuration of the MME in the second embodiment.
- FIG. 11 is a sequence diagram illustrating a third operation example of the communication system according to the second embodiment.
- FIG. 12 is a system configuration diagram showing an example of a communication system according to the third embodiment of the present invention.
- FIG. 13 is a block diagram illustrating an example of a schematic functional configuration of a base station according to the third embodiment.
- FIG. 14 is a schematic diagram illustrating an example of a data configuration of a policy management database provided in the base station according to the third embodiment.
- FIG. 15 is a block diagram illustrating an example of a schematic functional configuration of a router according to the third embodiment.
- FIG. 16 is a sequence diagram illustrating an operation example of the communication system according to the third embodiment.
- FIG. 17 is a system configuration diagram showing an example of a communication system according to the fourth embodiment of the present invention.
- FIG. 18 is a sequence diagram illustrating an operation example of the communication system according to the fourth embodiment.
- FIG. 19 is a sequence diagram illustrating another operation example of the communication system according to the fourth embodiment.
- FIG. 20 is a system configuration diagram showing an example of a communication system according to the fifth embodiment of the present invention.
- FIG. 21 is a block diagram illustrating an example of a schematic functional configuration of a control device according to the fifth embodiment.
- FIG. 22 is a block diagram illustrating an example of a schematic functional configuration of a base station according to the fifth embodiment.
- FIG. 23 is a system configuration diagram showing an example of a communication system according to the sixth embodiment of the present invention.
- FIG. 24 is a block diagram illustrating an example of a schematic functional configuration of a control device according to the sixth embodiment.
- FIG. 25 is a block diagram illustrating an example of a schematic functional configuration of a communication device according to the sixth embodiment.
- FIG. 21 is a block diagram illustrating an example of a schematic functional configuration of a control device according to the fifth embodiment.
- FIG. 22 is a block diagram illustrating an example of a schematic functional configuration of a base station according to the fifth embodiment.
- FIG. 23 is a system configuration diagram showing
- FIG. 26 is a system configuration diagram showing an example of a communication system according to the seventh embodiment of the present invention.
- FIG. 27 is a schematic system configuration diagram for explaining an example of a charging method in the communication system according to the seventh embodiment.
- FIG. 28 is a sequence diagram illustrating an operation example of the communication system according to the seventh embodiment.
- FIG. 29 is a sequence diagram illustrating another operation example of the communication system according to the seventh embodiment.
- FIG. 30 is a system configuration diagram illustrating another example of the communication system according to the seventh embodiment.
- an example of an LTE communication system will be described as a communication system according to a first embodiment of the present invention.
- the communication system to which the present invention is applied is not limited to LTE.
- the present invention is applicable to GPRS (General Packet Radio Service), UMTS (Universal Mobile Telecommunication System), WiMAX (Worldwide Interoperability for Microwaves, etc.).
- the communication system includes a terminal 1, a legacy network, and a virtual network.
- the terminal 1 is a mobile phone, a PC (Personal Computer), a mobile router, a smart device (a smart meter that monitors household power consumption, a smart TV, a wearable terminal), an M2M (Machine to Machine) device, and the like.
- a PC Personal Computer
- a mobile router a smart device (a smart meter that monitors household power consumption, a smart TV, a wearable terminal), an M2M (Machine to Machine) device, and the like.
- M2M Machine to Machine
- the legacy network and the virtual network are backbone networks such as EPC (Evolved Packet Core), and are used for the terminal 1 to communicate with an external network such as the Internet via the base station 2.
- EPC Evolved Packet Core
- the legacy network includes a plurality of network nodes for providing a communication service to the terminal 1, and each network node is a communication device having a predetermined communication function.
- the network node is a communication device such as a base station (eNB) 2, a SGW (Serving Gateway) 3, a PGW (PDN Gateway) 4, and an MME (Mobility Management Entity) 5.
- the terminal 1 is connected to the base station 2 and can access a network such as the Internet via the SGW 3 and the PGW 4.
- the communication system shown in FIG. 1 may include a network other than the legacy network and the virtual network.
- the legacy network and the virtual network may each include a plurality of types of networks, such as an LTE network, a GPRS network, a UMTS network, and the like.
- Each network node illustrated in FIG. 1 executes predetermined signal processing.
- Each network node includes the following functions related to signal processing, for example.
- SGW3 ⁇ Packet processing function (User-Plane function) ⁇ Function to process control signaling (C-Plane function) -Lawful Interception (LI) function
- PGW4 for intercepting communication ⁇ Packet processing function (User-Plane function) -Function to manage the billing status according to communication (PCEF: Policy and Charging Enforcement Function) ⁇ Function to control policies such as QoS (PCRF: Policy and Charging Rule Function)
- MME5 ⁇ Function to process control signaling (C-Plane function) ⁇ Function to manage subscriber information of communication system in cooperation with HSS (Home Subscriber Server)
- the virtual network In the virtual network, at least a part of the functions of the network node of the legacy network is virtually operated by software. For example, the function of the network node is operated by an application on the virtual machine.
- the virtual network is constructed in a data center composed of, for example, servers and other communication devices (routers and the like).
- the functions (for example, MME functions) of some network nodes of the legacy network can be operated by software such as a virtual machine.
- a virtual network can be constructed by dynamically scaling out / in a virtual machine.
- a network operator can dynamically build a virtual network by starting or stopping a virtual machine according to the state of communication traffic in the network or according to whether or not it is in a predetermined time zone.
- the network operator can also dynamically construct a virtual network by starting or stopping a virtual machine corresponding to predetermined communication traffic, for example, communication traffic of a predetermined terminal 1.
- the network operator can dynamically construct a virtual network by starting or stopping a virtual machine so as to satisfy a request condition (for example, SLA: Service Level Agreement) for processing communication traffic. For example, by stopping some virtual machines in a predetermined time zone with low communication traffic, it is possible to suppress resources allocated to the virtual network and reduce power consumption of the data center.
- a request condition for example, SLA: Service Level Agreement
- the base station 2 can distribute, distribute, distribute or switch communication traffic among a plurality of networks constituting the backbone.
- communication traffic is distributed or switched between a legacy network and a virtual network that form a backbone of a wireless network between the terminal 1 and the base station 2. Therefore, for example, even if the terminal 1 that can be used in a network such as a wireless LAN cannot access the wireless LAN, communication traffic can be offloaded in the backbone network. Therefore, according to the present embodiment, the base station 2 can execute traffic offload that does not depend on the radio environment of the terminal.
- FIG. 2 shows a configuration example of the base station 2 which is an example of the communication device according to the present embodiment.
- the base station 2 includes an identification unit 20 and a network switching unit 21.
- the identification unit 20 identifies the type of communication traffic or the attribute / type of the terminal 1, and selects a network corresponding to the identified communication traffic or the terminal 1 from a plurality of networks including a legacy network and a virtual network. Further, the identification unit 20 may select a network node corresponding to the identified communication traffic or the terminal 1 from a plurality of network nodes including a legacy network node and a virtual network virtual node.
- the identification unit 20 can identify the type of communication traffic, the type of the terminal 1, and the like based on a predetermined identification policy. For example, the identification unit 20 identifies communication traffic to be processed in the virtual network based on the identification policy. For example, the identification unit 20 identifies whether the terminal 1 is a type of terminal 1 to be processed in the virtual network based on the identification policy.
- the identification policy of the identification unit 20 can be dynamically changed, for example, by a network operator.
- the network switching unit 21 transfers the communication traffic to the network selected for the communication traffic. For example, the network switching unit 21 switches the communication traffic transfer path so that the communication traffic related to the terminal 1 passes through a selected network (for example, a legacy network or a virtual network). For example, the network switching unit 21 transfers the specific communication traffic identified by the identification unit 20 to the virtual network.
- a selected network for example, a legacy network or a virtual network.
- the network switching unit 21 can manage the legacy network node and the virtual network node separately from each other.
- the network switching unit 21 manages the identification information (for example, the address of the node) regarding the node of the legacy network and the identification information (for example, the address of the virtual node) regarding the virtual node of the virtual network, separately from each other.
- the network switching unit 21 may manage the identification information of each node in association with a flag indicating whether or not the node is a virtual node. With the above configuration, the network switching unit 21 can transmit communication traffic to be offloaded to the virtual network to the virtual node on the virtual network.
- the identification unit 20 identifies, for example, whether the terminal 1 is an MTC (Machine Type Communication) device. For example, the network switching unit 21 transfers the communication traffic of the terminal 1 identified by the identifying unit 20 as an MTC device to the virtual network. For example, when the terminal 1 is an MTC device, the identification unit 20 may identify the MTC device group to which the terminal belongs. For example, the network switching unit 21 switches a network for transferring communication traffic related to the terminal according to the identified MTC device group.
- MTC Machine Type Communication
- the identification unit 20 can identify communication traffic corresponding to a predetermined application. As an example, when the identification unit 20 identifies communication traffic corresponding to an application related to M2M (Machine-to-Machine), the network switching unit 21 transfers the communication traffic related to M2M to, for example, a virtual network. As another example, the identification unit 20 may identify communication traffic corresponding to an application such as SNS (Social Network Service). Further, the identification unit 20 may identify communication traffic corresponding to an application that operates in the background of the terminal 1 (for example, an application that automatically communicates at a predetermined time interval regardless of a user operation).
- M2M Machine-to-Machine
- SNS Social Network Service
- the identification unit 20 can identify communication traffic corresponding to a predetermined position (for example, a predetermined base station, a predetermined cell, etc.). As an example, the identification unit 20 can identify communication traffic corresponding to a position (event venue, shopping mall, etc.) where many users gather.
- the network switching unit 21 transfers the communication traffic identified by the identification unit 20 to, for example, a virtual network.
- the base station 2 is exemplified as the communication device according to the present embodiment, but the MME 5 may have the functions of the identification unit 20 and the network switching unit 21 described above as the communication device.
- the base station 2 can also select a network based on a predetermined message transmitted from the terminal 1.
- a configuration example of the terminal 1 capable of transmitting a predetermined message to the base station 2 will be shown with reference to FIG.
- the terminal 1 includes a message generation unit 10 and a communication unit 11.
- the message generator 10 generates a message for the base station 2 to select a network. For example, the message generator 10 generates a message including information indicating whether the terminal 1 is an MTC device. Further, for example, the message generation unit 10 generates a message including information indicating an application corresponding to communication traffic.
- the communication unit 11 transmits the generated message to the base station 2. As described above, the base station 2 selects a network based on the message transmitted from the terminal 1.
- the traffic offload according to the present embodiment can be implemented using either one or both of the base station 2 illustrated in FIG. 2 and the terminal 1 illustrated in FIG.
- the communication method according to the present embodiment will be described.
- FIG. 4 is a sequence diagram showing an operation example of the communication system according to the first embodiment of the present invention.
- the terminal 1 notifies the base station 2 of a connection request to the network (operation S1-1). For example, the terminal 1 notifies the base station 2 of a connection request to the network when the power is turned on or the cellular communication function is turned on.
- the base station 2 selects a network to which the terminal 1 is connected in response to a connection request from the terminal 1 (operation S1-2).
- the base station 2 selects either a legacy network or a virtual network.
- the terminal 1 that has notified the connection request is an MTC device
- the base station 2 connects the terminal 1 to the virtual network.
- the base station 2 connects the terminal 1 to the selected network (operation S1-3).
- the base station 2 connects the terminal 1 to either a legacy network or a virtual network.
- the base station 2 can adjust the amount of traffic flowing into the legacy network.
- the base station 2 can select a network node to which the terminal 1 is connected depending on whether or not the terminal 1 is an MTC device.
- the technique of the second embodiment can be applied to both the first embodiment and the later-described embodiments.
- the MTC device includes the M2M device exemplified in the above embodiment.
- the MTC device is, for example, a smart device (a smart meter that monitors household power consumption, a smart TV, a wearable terminal, etc.), an industrial device, a car, a healthcare device, a home appliance, or the like.
- MTC refers to a form of data communication that does not necessarily require human intervention, such as a smart meter. That is, the MTC device can perform autonomous communication with a communication partner device.
- MTC is being standardized by technical standard specifications (3GPP TS22.368 etc.).
- the MTC device is assumed to be used when communicating at a specific time (for example, “every day, PM 12:00”, “every Friday, AM 3:00”, etc.). Therefore, when there are a large number of similar MTC devices (eg, smart meters), it is assumed that a large amount of traffic occurs at a specific time when communication is started at the same time. Such a large amount of traffic is a heavy load on the legacy network.
- the base station 2 can offload the communication traffic of the MTC device to the virtual network.
- the load can be reduced.
- the communication system according to the present embodiment has the same configuration as that of FIG. 1, but the terminal 1 includes a Non-MTC device 1A and an MTC device 1B. . Since the configurations of the Non-MTC device 1A, the MTC device 1B, and the base station 2 are the same as those in the first embodiment, the same reference numerals are assigned and detailed description thereof is omitted. Further, since the functions of the network nodes (SGW3, PGW4, MME5) illustrated in FIG. 5 are the same as those in the first embodiment, detailed description thereof is omitted.
- the base station 2 which is a communication apparatus according to the present embodiment can connect the MTC device 1B to the virtual network and the non-MTC device 1A to the legacy network. Therefore, the base station 2 can offload communication traffic related to the MTC device 1B to the virtual network.
- a virtual network node that constitutes a virtual network is operated by a virtual machine that is dynamically constructed according to a request condition related to processing of communication data of the MTC device 1B.
- the required conditions include, for example, the performance and communication bandwidth required for processing the communication data of the MTC device 1B, the SLA (Service Level Agreement) required for the communication of the MTC device 1B, and the time when the communication by the MTC device 1B occurs Obi etc.
- the base station 2 selects the MME to which the terminal is connected in response to the reception of “RRC Connection Request” (Operation S2-2). For example, the identification unit 20 of the base station 2 identifies whether the terminal is an MTC device based on information included in “RRC Connection Request”. As an example, the identification unit 20 identifies whether the type of the terminal is an MTC device based on whether “LAPI: Low Access Priority Indicator” is included in “RRC Connection Request”. Since “LAPI” is not included in the “RRC Connection Request” transmitted from the non-MTC device 1A, in operation S2-2, the terminal is identified as a non-MTC device and is legacy to the non-MTC device. Select a network.
- the non-MTC device 1A transmits a message (“Attach Request”) requesting connection to the network to the base station 2.
- the network switching unit 21 of the base station 2 transmits the “Attach Request” received from the non-MTC device 1A to the MME 5 of the selected legacy network because the MME 5 of the legacy network is selected in the operation S2-2 ( Operation S2-3).
- the MME 5 of the legacy network starts an EPS bearer establishment procedure (operation S2-4).
- the EPS bearer establishment procedure is started by the MME 5, control signals are exchanged among the SGW 3, the PGW 4, the MME 5, and the base station 2, and the EPS bearer is established.
- the network switching unit 21 of the base station 2 transmits and receives communication data related to the non-MTC device 1A via the EPS bearer, so that the non-MTC device 1A can communicate with the external network via the established EPS bearer.
- the base station 2 selects the MME to which the terminal is connected in response to the reception of “RRC Connection Request” (Operation S2-6). Since “LAPI” is included in the “RRC Connection Request” transmitted from the MTC device 1B, the identification unit 20 of the base station 2 performs “RRC Connection Request” based on the LAPI included in the “RRC Connection Request”.
- the transmitting terminal is identified as an MTC device, and a virtual network is selected for the MTC device.
- the network switching unit 21 of the base station 2 receives the “Attach Request” received from the MTC device 1B. Transmit to the virtual MME 5A of the selected virtual network (operation S2-7).
- the virtual MME 5A In response to the reception of “Attach Request”, the virtual MME 5A starts an EPS bearer establishment procedure (operation S2-8). By starting the EPS bearer establishment procedure by the virtual MME 5A, control signals are exchanged among the virtual SGW 3A, the virtual PGW 4A, the virtual MME 5A, and the base station 2 to establish an EPS bearer.
- the network switching unit 21 of the base station 2 transmits and receives communication data related to the MTC device 1B via the EPS bearer, so that the MTC device 1B communicates via the established EPS bearer.
- FIG. 7 shows an operation example related to the non-MTC device 1A.
- the base station 2 transmits “Attach Request” to the MME 5 of the legacy network.
- the MME 5 executes a terminal authentication procedure in response to the reception of “Attach Request” (operation S3-2).
- the MME 5 executes identification of the terminal type in the authentication procedure (Operation S3-3).
- the MME 5 identifies the type of the terminal based on the IMSI (International Mobile Subscriber Identity) included in the “Attach Request”.
- IMSI International Mobile Subscriber Identity
- the MME 5 determines that the terminal is not an MTC device by the above-described identification procedure, the MME 5 starts an EPS bearer establishment procedure (operation S3-4).
- the EPS bearer establishment procedure is the same as that in the operation example of FIG.
- the MME 5 transmits “Authentication Information Request” to the HSS (Home Subscriber Server) 6 (operation S3-10).
- “Authentication Information Request” includes IMSI.
- the HSS 6 manages “External Identifier” which is identification information for identifying an MTC device by an external AS (Application Server).
- the external AS calls the MTC device based on “External Identifier” (Call procedure triggered by the external AS).
- the M2M service provider uses “External Identifier” to identify the MTC device.
- the HSS 6 manages, for example, IMSI and “External Identifier” in association with each other.
- the HSS 6 searches for “External Identifier” in response to the reception of “Authentication Information Request” (operation S3-11). For example, the HSS 6 searches for “External Identifier” associated with the IMSI included in the “Authentication Information Request”.
- the HSS 6 includes the search result of “External Identifier” in “Authentication Information Answer” and transmits it to the MME 5 (operation S3-12). For example, when information indicating that “External Identifier” is searched for in “Authentication Information Answer”, the MME 5 determines that the terminal is an MTC device. For example, when the information indicating that “External Identifier” has been searched for is not included in “Authentication Information Answer”, the MME 5 determines that the terminal is not an MTC device.
- the MME 5 when the MME 5 identifies that the terminal is an MTC device by the terminal identification procedure (operation S3-7), the MME 5 transmits “MME Reselection Indication” to the base station 2 and transmits the MME to the base station 2. Reselect (operation S3-8).
- the MME 5 includes, for example, information on the MME to be reselected by the base station 2 in “MME Selection Indication” and transmits the information to the base station 2.
- the MME 5 can include the IP address of the MME (virtual MME 5A) of the virtual network in the “MME Reselection Indication”.
- the base station 2 In response to the reception of “MME Selection Indication”, the base station 2 transmits “Attach Request” to the reselected MME (operation S3-9). If the base station 2 reselects the virtual MME 5A, the base station 2 transmits “Attach Request” to the reselected virtual MME 5A.
- the virtual MME 5A In response to the reception of “Attach Request”, the virtual MME 5A starts an EPS bearer construction procedure in the virtual network (operation S3-10).
- the EPS bearer establishment procedure is the same as that in the operation example of FIG.
- the MTC device 1B communicates with the Internet or the like via an EPS bearer constructed in a virtual network.
- the MME 5 has a function of instructing the base station 2 to reselect the MME according to the type of the terminal.
- the MME 5 includes a virtual entity management unit 50 and a control unit 51.
- the virtual entity management unit 50 manages, for example, the address (IP address or the like) of the virtual MME 5A arranged in the virtual network.
- the control unit 51 acquires the address of the virtual MME 5A from the virtual entity management unit 50.
- the control unit 51 transmits the acquired IP address to the base station 2 and instructs reselection of the MME. In this way, as described above, the base station 2 retransmits “Attach Request” to the virtual MME 5A of the IP address notified from the control unit 51.
- the “RRC Connection Request” transmitted to the base station 2 includes the MTC device identifier, so the base station 2 includes the MTC device identifier in the “RRC Connection Request”.
- the MME can be selected depending on whether or not it is selected. For example, if the MTC device identifier is included in “RRC Connection Request”, the base station 2 selects the MME (virtual MME 5A) of the virtual network.
- the base station 2 or the MME 5 selects the network to which the terminal 1 is connected according to the type of the terminal 1 (that is, whether or not it is an MTC device).
- the base station 2 or the MME 5 may select a network to which the terminal 1 is connected based on a policy regarding the type of the terminal 1.
- the base station 2 or the MME 5 is based on the user attributes of the terminal 1 (for example, whether or not it is a premium user), the charging characteristics of the terminal 1 (for example, whether it is pay-as-you-go or flat-rate charging), etc. You can also select a network.
- the base station 2 can select a network node to which the terminal 1 is connected according to the type of communication traffic.
- the third embodiment can be applied to any of the first and second embodiments or the later-described embodiments.
- the base station 2 and the router 7 configure a legacy network and a virtual network as a network through which communication traffic between the terminal 1 and the external network passes according to the communication type. You can choose from. Since the configurations of the legacy network and the virtual network are the same as those in the first and second embodiments, the details are omitted.
- the base station 2 has a switch function capable of switching the transfer destination of communication traffic, and may have the configuration illustrated in FIG. 2 or the configuration illustrated in FIG.
- the base station 2 includes a switch unit 22 and a policy management DB (Data Base) 24, and the switch unit 22 includes a plurality of ports 23.
- the switch unit 22 can switch the transfer destination of communication traffic according to the communication type.
- the switch unit 22 may be a virtual switch (vSwitch) configured by software, for example.
- the policy management DB 24 has the data configuration illustrated in FIG. 14 and includes a rule for identifying communication traffic (“Identification Rule”) and a transfer destination (“Destination”) of communication traffic conforming to the rule. .
- the switch unit 22 refers to the policy management DB 24 and identifies the type of communication traffic input to the port 23. More specifically, the switch unit 22 includes the port number of the input communication traffic (for example, port number “80” for HTTP communication, port number “25” for SMTP communication), and “Identification Rule” in the policy management DB 24. And “Identification Rule” is searched using the port number of the input communication traffic. The switch unit 22 transfers the input communication traffic to “Destination” associated with the searched “Identification Rule”, that is, to the port 23 corresponding to the selected network, and transmits it to the selected network. When the “Identification Rule” corresponding to the communication traffic is not searched in the policy management DB 24, the switch unit 22 selects a default transfer destination (for example, legacy network) and transfers the communication traffic to the corresponding port 23. .
- a default transfer destination for example, legacy network
- the router 7 has the same configuration and function as the base station 2. That is, the router 7 includes a switch unit 70 and a policy management DB 72, and has the same configuration and function as the switch unit 22 and the policy management DB 24 of the base station 2, respectively.
- the MME 5 and the virtual MME 5A each start an EPS bearer establishment procedure (Operation S5-2, Operation S5-3).
- the EPS bearer establishment procedure is started by the MME 5
- control signals are exchanged among the SGW 3, the PGW 4, the MME 5, and the base station 2, and the EPS bearer is established.
- an EPS bearer establishment procedure is started by the virtual MME 5A
- control signals are exchanged among the virtual SGW 3A, the virtual PGW 4A, the virtual MME 5A, and the base station 2, and an EPS bearer is established.
- the base station 2 when the base station 2 receives the “Attach Request” from the terminal 1, it may transmit it only to the MME 5 of the legacy network (operation S5-1).
- the MME 5 In response to the reception of “Attach Request”, the MME 5 starts an EPS bearer establishment procedure in the legacy network and the virtual network (operation S5-2, operation S5-3). For example, MME5 transmits the control signal regarding EPS bearer establishment to SGW3 and virtual SGW3A according to reception of "Attach Request".
- the base station 2 and the router 7 pass the EPS related to the communication traffic related to the terminal 1 according to the communication type. Switch bearers.
- the base station 2 and the router 7 transfer the communication traffic to the EPS bearer established in the legacy network or perform communication. If the type is “Traffic (B)”, the communication traffic is transferred to the EPS bearer established in the virtual network (operation S5-4, operation S5-5).
- a network node to which the terminal 1 is connected is selected based on information related to the position of the terminal 1.
- the fourth embodiment can be applied to both the first to third embodiments and the embodiments described later.
- the communication system illustrated in FIG. 17 includes a plurality of networks (here, a legacy network and a virtual network) and a plurality of base stations, and is connected depending on the geographical location of the terminal 1.
- Network to select Since the configurations of the legacy network and the virtual network have already been described, details are omitted.
- the network to which the terminal 1 can be connected is determined to be either a legacy network or a virtual network depending on the position of the terminal 1.
- the terminal 1 is connected to the legacy network when staying in the cover area of the base station 2 (A), and is connected to the virtual network when staying in the cover area of the base station 2 (B).
- the terminal 1 transmits “Attach Request” to the base station 2 (A), and in response, the base station 2 (A) sets “Attach Request” to the default MME (here, the legacy network). It is assumed that it has been transmitted to the MME 5) (operation S6-1).
- “Attach Request” includes TAI (Tracking Area ID) and ECGI (E-UTRAN Cell Global ID). The TAI is an identifier of an area where the terminal 1 has performed location registration. ECGI is the identifier of the cell of the base station 2 to which the terminal 1 is connected.
- the MME 5 selects a network to which the terminal 1 should be connected based on at least one of the TAI and ECGI included in the “Attach Request” (operation S6-2).
- the MME 5 in this operation example has the configuration and functions illustrated in FIG. 10 described above, for example. That is, the control unit 51 of the MME 5 selects a network to which the terminal 1 is connected based on at least one of TAI and ECGI.
- the control unit 51 has policy information indicating a network associated with the position (TAI or ECGI) of the terminal 1.
- the control unit 51 refers to the policy information and searches for a network corresponding to the TAI or ECGI included in the “Attach Request”.
- the control unit 51 searches the virtual entity management unit 50 for the address of the virtual MME 5A.
- the control unit 51 notifies the base station 2 of the address of the searched virtual MME 5A.
- the base station 2 retransmits “Attach Request” to the address of the notified virtual MME 5A.
- the legacy network is associated with the TAI or ECGI corresponding to the base station 2 (A). Therefore, the MME 5 selects the legacy network as the network to which the terminal 1 is connected in operation S6-2. Since the MME 5 is located in the legacy network, the EPS bearer establishment procedure is started without instructing the base station 2 (A) to reselect the MME (operation S6-3), and the EPS bearer is established in the legacy network. Is done.
- the terminal 1 communicates via an EPS bearer constructed in a legacy network.
- the terminal 1 transmits “Attach Request” to the base station 2 (B), connects in response to this, and the base station 2 (B) transmits “Attach Request” to the MME 5 of the legacy network. (Operation S6-4).
- the MME 5 searches for a network associated with the TAI or ECGI included in the “Attach Request” received from the base station 2 (B).
- a virtual network is associated with the TAI or ECGI corresponding to the base station 2 (B). Therefore, the MME 5 selects a virtual network as a network to which the terminal 1 is connected (Operation S6-5).
- the MME 5 transmits an instruction including the address of the virtual MME 5A (“MME Reselection Indication”) to the base station 2 (B) (Operation S6-6).
- the base station 2 (B) retransmits “Attach Request” to the instructed address, that is, the virtual MME 5A (operation S6-7).
- the virtual MME 5A When receiving the “Attach Request”, the virtual MME 5A starts an EPS bearer establishment procedure (operation S6-8), and thereby an EPS bearer is constructed in the virtual network.
- the terminal 1 communicates via an EPS bearer constructed in a virtual network.
- an MME is associated with each base station 2 in advance.
- the MME 5 of the legacy network is associated with the base station 2 (A)
- the virtual MME 5A of the virtual network is associated with the base station 2 (B).
- the base station 2 (A) transmits “Attach Request” transmitted from the terminal 1 to the MME 5 corresponding to the base station 2 (A) (operation S6-9). Receiving “Attach Request”, the MME 5 starts an EPS bearer establishment procedure in the legacy network (operation S6-10). As the EPS bearer establishment procedure is started by the MME 5, control signals are exchanged among the SGW 3, the PGW 4, the MME 5, and the base station 2, and the EPS bearer is established.
- the base station 2 (B) transmits “Attach Request” transmitted from the terminal 1 to the virtual MME 5 A corresponding to the base station 2 (B) (operation S 6-11).
- the virtual MME 5A receives the “Attach Request”, and starts an EPS bearer establishment procedure in the virtual network (operation S6-12).
- control signals are exchanged among the virtual SGW 3A, the virtual PGW 4A, the virtual MME 5A, and the base station 2 to establish an EPS bearer.
- a control device centrally manages a policy for network selection. Therefore, the efficiency of policy operation management for network selection or network node selection is improved.
- the fifth embodiment can be applied to any of the first to fourth embodiments and later-described embodiments.
- the communication system according to this embodiment illustrated in FIG. 20 has a policy for network selection to a plurality of networks (here, legacy network and virtual network), terminal 1, base station 2, base station 2 and / or MME. And a control device 8 having a function of notifying. Since the configurations of the legacy network and the virtual network are as described above, the same reference numerals are assigned and details are omitted.
- control device 8 includes a policy management DB (Data Base) 80, a control unit 81, and an interface 82.
- DB Data Base
- the interface 82 is an interface for communicating with the base station 2 and the MME 5.
- the control device 8 can communicate with the base station 2 and the MME 5 using a predetermined protocol via the interface 82.
- the policy management DB 80 manages policies for network selection. For example, the network operator inputs a policy to the policy management DB 80.
- the control unit 81 refers to the policy management DB 80 and notifies the policy to the base station 2 and the MME 5 via the interface 82.
- the control device 8 may be, for example, a SON (Self Organizing Network) server or an operation management device used by a network operator.
- SON Self Organizing Network
- the policy management DB 80 manages, for example, a policy used for the virtual network to offload the load on the legacy network. Examples of policies stored in the policy management DB 80 are as follows.
- a policy / MTC device related to the type of terminal is connected to the virtual network. Connect non-MTC devices to legacy networks. Connect a predetermined MTC device (eg, smart meter) to the virtual network. Connect MTC devices belonging to a predetermined MTC device group to the virtual network. -The terminal 1 corresponding to a predetermined user attribute (for example, premium user) is connected to the legacy network. The terminal 1 corresponding to a predetermined user attribute (for example, a general user) is connected to the virtual network. -Connect the terminal 1 of the user whose communication volume exceeds a predetermined value to the virtual network. -The policy is enabled only during a predetermined time period (for example, AM 1: 00-AM 4:00). (This policy is used in combination with at least one of the above policies.)
- a predetermined time period for example, AM 1: 00-AM 4:00.
- a predetermined application for example, SNS application
- Transfer a portion of communication traffic for a given application eg, SNS application
- Forward communication traffic for a given application eg, SNS application
- Connecting communication traffic corresponding to a predetermined charging characteristic for example, flat fee charging
- Connect communication traffic corresponding to a predetermined charging characteristic for example, pay-per-use charging
- the policy is validated only during a predetermined time period (Ex: AM 1: 00-AM 4:00). (This policy is used in combination with at least one of the above policies.)
- the terminal 1 connected to a predetermined base station is connected to the virtual network.
- a terminal 1 connected to a base station corresponding to a predetermined event or a predetermined location is connected to the virtual network.
- the terminal 1 connected to a predetermined cell is connected to the virtual network.
- a terminal 1 connected to a cell corresponding to a predetermined event or a predetermined location is connected to the virtual network.
- the policy is enabled only during a predetermined time period (for example, AM 1: 00-AM 4:00). (This policy is used in combination with at least one of the above policies.)
- the base station 2 and the MME 5 select a network or a network node by the method described in the above embodiment based on the received policy.
- the base station 2 and the MME 5 can use the above-described policies individually or in combination with the above-described policies.
- the base station 2 is assumed to communicate with the control device 8 via the interface 25.
- the base station 2 receives the policy from the control device 8 via the interface 25, the base station 2 stores the received policy in the identification unit 20.
- the identification unit 20 selects a network based on the received policy. Further, the identification unit 20 may select a network node based on the received policy.
- the MME 5 may have an interface for communicating with the control device 8, similarly to the base station 2.
- the MME 5 receives a policy from the control device 8 via the interface, and selects a network based on the received policy.
- the MME 5 may select a network node based on the received policy.
- control device can execute the provisioning of the virtual network resources, thereby improving the efficiency of the operation management of the virtual network.
- the sixth embodiment can be applied to both the first to fifth embodiments and the embodiments described later.
- the communication system according to this embodiment illustrated in FIG. 23 includes a plurality of networks (here, legacy network and virtual network), a terminal 1, a base station 2, and a control device 8. Since the configurations of the legacy network and the virtual network are as described above, the same reference numerals are assigned and details are omitted.
- the control device 8 executes virtual network resource provisioning. For example, the control device 8 can allocate resources (server resources, CPU resources, network resources, etc.) to virtual network nodes (virtual MME, virtual SGW, virtual PGW, etc.) in preparation for offloading of communication traffic. .
- the resource allocation for the virtual network node can be performed, for example, for a virtual machine that operates the virtual network node.
- control device 8 can predict a time zone during which communication traffic increases, and can provision virtual network resources prior to the time zone. Further, the control device 8 can dynamically execute the provisioning of the resources of the virtual network as the communication traffic increases.
- control device 8 is a virtual NW that executes provisioning of virtual network resources.
- a (network) control unit 83 is included.
- the configuration of the control device 8 according to the present embodiment is not limited to the example of FIG.
- the control device 8 may not have a function (policy management DB 80 or the like) for notifying the base station 2 or the like of a policy for selecting a network.
- the control device according to the present embodiment may be a device different from the control device according to the fifth embodiment (FIG. 21).
- the virtual NW control unit 83 allocates, for example, a resource capable of processing communication traffic by the MTC device to the virtual network prior to a time zone when communication by a predetermined type of MTC device occurs.
- the virtual NW control unit 83 allocates a resource for processing a control signal (for example, a control signal related to a connection request to the network) transmitted by the MTC device to the virtual MME 5A. Further, for example, the virtual NW control unit 83 allocates resources for processing U-Plane (user plane) data transmitted by the MTC device to the virtual SGW 3A and the virtual PGW 4A. The virtual NW control unit 83 may assign a resource for processing communication traffic related to a predetermined type of MTC device group to the virtual network. The virtual NW control unit 83 may release resources from the virtual network during a time period when no communication traffic is generated by the MTC device.
- a control signal for example, a control signal related to a connection request to the network
- U-Plane (user plane) data transmitted by the MTC device to the virtual SGW 3A and the virtual PGW 4A.
- the virtual NW control unit 83 may assign a resource for processing communication traffic related to a predetermined type of MTC device group to the virtual network.
- control unit 81 of the control device 8 notifies the base station 2 or the like of a policy for network selection in response to allocation of resources for processing communication traffic related to the MTC device.
- the policy notified to the base station 2 or the like is, for example, a policy related to the MTC device among the policies exemplified in the fifth embodiment.
- the virtual NW control unit 83 predicts a time zone in which communication traffic increases based on the analysis result of communication traffic in the communication system, and allocates resources for processing the increased communication traffic based on the prediction result. Can be assigned to a virtual network.
- the virtual NW control unit 83 may perform analysis of communication traffic.
- the virtual NW control unit 83 may acquire the result of traffic analysis from the network operator via OSS / BSS (Operation Support System / Business Support System).
- the virtual NW control unit 83 allocates a resource for processing a control signal of communication traffic expected to increase to the virtual MME 5A. Further, for example, the virtual NW control unit 83 allocates resources for processing U-Plane (user plane) data expected to increase to the virtual SGW 3A and the virtual PGW 4A.
- U-Plane user plane
- the control unit 81 of the control device 8 notifies the base station 2 or the like of a policy for network selection, for example, in response to the resource being allocated.
- the control unit 81 can also notify the base station 2 or the like of at least one of the policies exemplified in the fifth embodiment.
- the control unit 81 notifies the base station 2 or the like of a policy indicating that the communication traffic related to a predetermined application is transferred to the virtual network in order to offload the communication traffic.
- the virtual NW control unit 83 can allocate resources to the virtual network in response to a disaster such as an earthquake. Also, the virtual NW control unit 83 can allocate resources to the virtual network prior to the date and time when an event where a large number of terminal users gather is held, for example.
- the virtual NW control unit 83 can allocate, to the virtual SGW 3, the virtual PGW 4, and the virtual MME 5A, a resource for processing a call or data communication that is expected to increase with the occurrence of a disaster or with an event.
- the control unit 81 of the control device 8 notifies the base station 2 or the like of a policy for network selection in response to the resource being allocated.
- the control unit 81 can notify the base station 2 or the like of at least one of the policies exemplified in the fifth embodiment.
- the control unit 81 may notify the base station 2 or the like of a policy indicating that communication traffic related to a predetermined application is transferred to the virtual network in order to offload communication traffic.
- control unit 81 can notify the base station 2 or the like of a policy indicating that the terminal 1 corresponding to a predetermined user attribute (for example, a general user) is connected to the virtual network.
- the control unit 81 may notify the base station 2 or the like of a policy indicating that communication traffic related to a call is transferred to either the virtual network or the legacy network in a round robin manner for each user.
- the virtual NW control unit 83 can allocate resources to the virtual network based on performance required for the virtual network, for example. For example, the virtual NW control unit 83 allocates resources to the virtual network so as to satisfy SLA (Service Level Agreement) required for the virtual network. For example, the control unit 81 of the control device 8 notifies the base station 2 or the like of a policy for network selection in response to the resource being allocated. For example, the control unit 81 may notify the base station 2 or the like of at least one of the policies exemplified in the fifth embodiment.
- SLA Service Level Agreement
- the virtual NW control unit 83 can predict the amount of communication traffic that is assumed to flow into the virtual network, for example, according to a policy that has been notified to the base station 2 or the like.
- the virtual NW control unit 83 may predict the amount of communication traffic assumed to flow into the virtual network according to a policy scheduled to be notified to the base station 2 or the like.
- the virtual NW control unit 83 allocates resources to the virtual network based on the communication amount predicted in this way. For example, the virtual NW control unit 83 allocates resources necessary for processing communication traffic assumed to flow into the virtual network to the virtual network.
- the virtual NW control unit 83 may allocate resources necessary for processing communication traffic assumed to flow into the virtual network with performance satisfying a predetermined SLA to the virtual network.
- control unit 81 of the control device 8 notifies the base station 2 or the like of a policy for network selection in response to the resource being allocated.
- control unit 81 notifies the base station 2 or the like of at least one of the policies exemplified in the fifth embodiment.
- the communication device 100 is a device that operates a virtual machine that provides a virtual network function in a virtual network, that is, a function of a virtual network node (for example, virtual SGW 3A, virtual PGW 4A, virtual MME 5A, etc.). is there.
- a virtual network node for example, virtual SGW 3A, virtual PGW 4A, virtual MME 5A, etc.
- the communication device 100 includes a control unit 110 and at least one virtual network function (VNF) 120.
- VNF virtual network function
- the control unit 110 can operate the VNF 120 that provides the function of the virtual network node on the virtual machine.
- the control unit 110 may be configured by control software capable of executing computer virtualization, such as a hypervisor.
- the control unit 110 can execute at least one of start, stop, and migration (migration for migrating a virtual machine to another communication apparatus 100) of a virtual machine that operates the VNF 120.
- Each virtual network node has the following functions, for example.
- Virtual P-GW4A ⁇ Packet processing function (User-Plane function) -Function to manage the billing status according to communication (PCEF: Policy and Charging Enforcement Function) ⁇ Function to control policies such as QoS (PCRF: Policy and Charging Rule Function)
- Virtual S-GW3A ⁇ Packet processing function (User-Plane function) ⁇ Function to process control signaling (C-Plane function) ⁇ Lawful Interception (LI) function for intercepting communications
- Virtual MME5A ⁇ Function to process control signaling (C-Plane function) ⁇ Function to manage subscriber information of communication system in cooperation with HSS (Home Subscriber Server)
- the VNF 120 operates as the above-described virtual network node on the virtual machine.
- the VNF 120 is constructed for each virtual network node.
- the VNF 120 may be constructed for each function of each virtual network node.
- the VNF 120 may operate as a U-Plane function of the virtual PGW 4A on the virtual machine.
- the virtual NW control unit 83 of the control device 8 can instruct the control unit 110 of the communication device 100 to start, delete, and migrate at least one of the virtual machines for executing the VNF 120.
- the virtual NW control unit 83 can control the resources of the virtual network by instructing the control unit 110 to perform at least one of activation, deletion, and migration of the virtual machine.
- a virtual network operator can lend a virtual network to a legacy network operator. By lending the virtual network for a fee, the operator of the virtual network can obtain a usage fee for the virtual network. In addition, the operator of the legacy network can virtually augment the network without investing in the legacy network.
- the seventh embodiment can be applied to any of the first to sixth embodiments.
- a communication system includes a plurality of networks (legacy network and virtual network here) operated by respective operators, a terminal 1, and a base station 2.
- Terminal 1 is a legacy network subscriber terminal. Since the configurations of the legacy network and the virtual network are as described above, the same reference numerals are assigned and details are omitted.
- the virtual network operator (operator: B) can lend the virtual network to the legacy network operator (operator: A).
- the operator A can reduce the load on the legacy network by offloading communication traffic to the borrowed virtual network.
- the base station 2 is assumed to be owned by either the operator A or B, and can transmit at least a part of the communication traffic of the subscriber terminal of the operator A to the virtual network.
- the base station 2 can identify the communication traffic of the subscriber terminal and transmit the identified traffic to the virtual network.
- the base station 2 can transmit a part of the communication traffic of the subscriber terminal of the operator A to the virtual network, for example, based on the policy exemplified in the fifth embodiment described above.
- the operator A pays a usage fee to the operator B as consideration for using the virtual network owned by the operator B.
- a charging method for the operator A for example, a flat rate system in units of months or years, a pay-per-use system according to communication data or communication time of the virtual network, or a resource amount corresponding to a virtual machine assigned to the virtual network for the operator A A pay-as-you-go system can be adopted. Note that these charging methods are examples, and the charging method for the operator A is not limited to the above example.
- the policy for network selection set by the operator A in the base station 2 may be, for example, the policy illustrated in the fifth embodiment described above.
- the operator A may set a policy for the MME 5.
- the base station 2 or the MME 5 selects a network to which the terminal 1 is connected according to the set policy.
- the operator B of the virtual network may set a policy for the base station 2 or the like instead of the operator A.
- the base station 2 transmits the “Attach Request” received from the terminal 1 to the virtual MME 5A (operation S7-1).
- the base station 2 can select the virtual MME 5A by the operations S2-5 and S2-6 in FIG. 6 prior to the operation S7-1.
- the virtual MME 5A may be selected as the transmission destination of “Attach Request” by the operations S3-6 to S3-9 in FIG.
- the virtual MME 5A may be selected as the transmission destination of “Attach Request” by the operations S4-5 to S4-7 in FIG.
- “Attach Request” may be transmitted to the virtual MME 5A based on the operation illustrated in FIG. 16, FIG. 18, or FIG.
- the base station 2 can manage the virtual MME 5A for each operator using the virtual network.
- the network switching unit 21 of the base station 2 can select a dedicated virtual MME 5A for the operator A. That is, the base station 2 can select the dedicated virtual MME 5 for the traffic from the subscriber terminal 1 of the legacy network owned by the operator A.
- the virtual MME 5A executes the authentication process of the terminal 1 prior to the reception of “Attach Request”.
- the virtual MME 5A can authenticate the terminal 1 using, for example, the HSS 6 arranged in the virtual network.
- the virtual MME 5A may authenticate the terminal 1 using the HSS 6 arranged in the legacy network.
- the HSS 6 manages, for example, the IMSI of the terminal 1 and information related to the operator to which the terminal 1 subscribes.
- the virtual MME 5A acquires information regarding the operator to which the terminal 1 joins from the HSS 6 during the above authentication process, and recognizes the operator corresponding to the terminal 1.
- the virtual MME 5A starts building an EPS bearer.
- the virtual MME 5A assigns dedicated gateways (virtual SGW 3A, virtual PGW 4A) to the operator A who borrows the virtual network from the operator B. Even if another operator (for example, operator C) borrows a virtual network from operator B, different gateways are assigned to operator A and operator C, respectively. By assigning a different gateway to each operator who uses the virtual network, communication traffic relating to each operator is virtually separated, and security is improved.
- the virtual MME 5A selects the virtual SGW 3 dedicated to the operator A (operation S7-2).
- the virtual entity management unit 50 of the virtual MME 5A manages a virtual entity (virtual SGW 3A, virtual PGW 4A, etc.) for each operator using the virtual network.
- the control unit 51 of the virtual MME 5A selects the virtual SGW 3A corresponding to the operator A according to the virtual entity management unit 50.
- control unit 51 of the virtual MME 5A selects a virtual SGW 3A to be assigned to the operator A from the virtual entities managed by the virtual entity management unit 50.
- the virtual entity management unit 50 associates the virtual SGW 3A selected by the control unit 51 with the identification information of the operator to which the virtual SGW 3A is assigned.
- the control unit 51 selects a virtual entity that is not associated with operator identification information from among the virtual entities managed by the virtual entity management unit 50.
- the virtual MME 5A transmits a “Create Session Request” message to the virtual SGW 3A selected in operation S7-2 (operation S7-3).
- the virtual MME 5A allocates a dedicated virtual PGW 4A to the operator A who borrows a virtual network from the operator B.
- the virtual MME 5A includes the IP address of the virtual PGW 4A assigned to the operator A in the “Create Session Request” message.
- the virtual entity management unit 50 of the virtual MME 5A manages a virtual entity (virtual SGW 3A, virtual PGW 4A, etc.) for each operator using the virtual network.
- the control unit 51 of the virtual MME 5A includes the IP address of the virtual PGW 4A corresponding to the operator A in the “Create Session Request” message according to the virtual entity management unit 50.
- control unit 51 of the virtual MME 5A selects the virtual PGW 4A to be assigned to the operator A from the virtual entities managed by the virtual entity management unit 50.
- the virtual entity management unit 50 associates the virtual PGW 4A selected by the control unit 51 with the identification information of the operator to which the virtual PGW 4A is assigned.
- the control unit 51 selects a virtual entity that is not associated with operator identification information from among the virtual entities managed by the virtual entity management unit 50.
- the virtual SGW 3A In response to receiving the “Create Session Request” message from the virtual MME 5A, the virtual SGW 3A transmits a “Create Session Request” message to the virtual PGW 4A designated by the received message (operation S7-4).
- the virtual SGW 3A includes its own IP address in the message transmitted to the virtual PGW 4A.
- the virtual PGW 4A returns a “Create Session Response” message to the virtual SGW 3A (operation S7-5).
- the virtual SGW 3A returns a “Create Session Response” message to the virtual MME 5A (operation S7-6).
- the virtual MME 5A In response to receiving the “Create Session Response” message, the virtual MME 5A notifies the base station 2 of information for establishing a session between the virtual SGW 3A and the base station 2.
- the EPS bearer is constructed in the virtual network by the operation illustrated in FIG.
- the operator A's legacy network subscriber terminal (terminal 1 in FIG. 28) communicates via the constructed EPS bearer.
- the base station 2 transmits the “Attach Request” received from the terminal 1 to the virtual MME 5A (operation S8-1). For example, prior to the operation S8-1, the base station 2 selects the virtual MME 5A as the transmission destination of “Attach Request” by the operations S2-5 and S2-6 in FIG. Further, for example, the base station 2 may select the virtual MME 5A as the transmission destination of “Attach Request” by the operations S3-6 to S3-9 in FIG. Further, for example, the base station 2 may select the virtual MME 5A as the transmission destination of “Attach Request” by the operations S4-5 to S4-7 in FIG. For example, the base station 2 may transmit “Attach Request” to the virtual MME 5A based on the operations illustrated in FIG. 16, FIG. 18, and FIG.
- the virtual MME 5A executes the authentication process of the terminal 1 prior to the reception of “Attach Request”.
- the virtual MME 5A can authenticate the terminal 1 using, for example, the HSS 6 arranged in the virtual network.
- the virtual MME 5A may authenticate the terminal 1 using the HSS 6 arranged in the legacy network.
- the HSS 6 manages, for example, the IMSI of the terminal 1 and information related to the operator to which the terminal 1 subscribes.
- the virtual MME 5A acquires information regarding the operator to which the terminal 1 joins from the HSS 6 during the above authentication process, and recognizes the operator corresponding to the terminal 1.
- the virtual MME 5A When receiving the “Attach Request”, the virtual MME 5A transmits a “Create Session Request” message to the virtual SGW 3A (operation S8-2).
- the virtual MME 5A includes, for example, information about an operator corresponding to the terminal 1 in “Create Session Request”.
- the virtual MME 5A starts construction of an EPS bearer by transmitting a “Create Session Request” message.
- the virtual MME 5A, the virtual SGW 3A, and the virtual PGW 4A each allocate a dedicated TEID to the bearer related to the operator A who borrows the virtual network from the operator B. Even if another operator (for example, operator C) borrows a virtual network from operator B, the bearers related to operator A and operator C are assigned TEIDs specific to the respective operators. Security is improved by assigning a unique TEID to each operator using the virtual network.
- the virtual SGW 3A When receiving the “Attach Request” from the virtual MME 5A, the virtual SGW 3A transmits a “Create Session Request” message to the virtual PGW 4A (operation S8-3).
- the virtual SGW 3A assigns the TEID for the operator A to the terminal 1 which is the subscriber terminal of the operator A, and includes the selected TEID in the “Create Session Request” message. Further, the virtual SGW 3A may include information on an operator corresponding to the terminal 1 in the “Create Session Request”.
- the virtual SGW 3A can manage a candidate TEID group to be assigned to each operator for each operator using the virtual network. For example, the virtual SGW 3A manages a candidate TEID group to be assigned to the operator A and a candidate TEID group to be assigned to the operator C. The virtual SGW 3A selects the TEID based on the operator information notified from the virtual MME 5A.
- the virtual SGW 3A selects a TEID assigned to the operator A from the TEID group.
- the virtual SGW 3A associates the selected TEID with the identification information of the operator assigned with the TEID.
- the virtual SGW 3A selects a TEID that is not associated with operator identification information.
- the virtual PGW 4A When the virtual PGW 4A receives the “Create Session Request” message from the virtual SGW 3A, it returns a “Create Session Response” message to the virtual SGW 3A (operation S8-4).
- the virtual PGW 4A assigns a TEID for the operator A to the terminal 1 which is a subscriber terminal of the operator A, and includes the selected TEID in the “Create Session Request” message. For example, the virtual PGW 4A selects a TEID in the same manner as the virtual SGW 3A.
- the virtual SGW 3A When the virtual SGW 3A receives the “Create Session Request” message from the virtual PGW 4A, it transmits a “Create Session Response” message to the virtual MME 5A (operation S8-5).
- the virtual SGW 3A assigns the TEID for the operator A to the terminal 1 which is the subscriber terminal of the operator A, and includes the selected TEID in the “Create Session Request” message.
- the virtual MME 5A In response to receiving the “Create Session Response” message, the virtual MME 5A notifies the base station 2 of information for establishing a session between the virtual SGW 3A and the base station 2.
- the EPS bearer is constructed in the virtual network by the operation illustrated in FIG. A subscriber terminal (terminal 1 in FIG. 29) of the legacy network of operator A communicates via the constructed EPS bearer.
- a virtual PCRF (Policy and Charging Rule Function) 40 arranged in the virtual network monitors communication traffic.
- the virtual PCRF 40 is arranged for each operator (operator A, operator C) who borrows a virtual network from the operator B.
- the operator B of the virtual network arranges the virtual PCRF 40 in the virtual network by the control device 8, for example.
- the virtual NW control unit 83 of the control device 8 arranges the virtual PCRF 40 for monitoring the communication traffic related to the operator A using the virtual network in the virtual network.
- each virtual PGW 4A is connected to an operator virtual PCRF 40 associated with each virtual PGW 4A.
- Each of the virtual PGWs 4A can count the number of packets with a PCEF (Policy and Charging Enforcement Function) function, and can transfer the packet count result to the virtual PCRF 40 connected to each virtual PGW 4A.
- PCEF Policy and Charging Enforcement Function
- the operator (operator B) of the virtual network monitors the packet count by each virtual PCRF 40 and acquires the communication amount for each operator using the virtual network. For example, the operator B charges the usage fee of the virtual network to each operator based on the communication amount for each operator.
Abstract
Description
本発明は、通信に用いられる通信装置、通信方法、通信システムおよびプログラムに関する。
本発明の通信方法は、第一のネットワークにおいて所定の信号処理を実行する第一のネットワークノードと第二のネットワークにおいて前記第一のネットワークノードの機能を仮想マシンにより運用する第二のネットワークノードとを含む複数のネットワークノードから、通信相手の機器と自律通信が可能な端末に対して前記第二のネットワークノードを選択し、前記端末に関する通信データを、選択された前記第二のネットワークノードに送信する。
本発明の通信システムは、端末に関する通信データを処理する通信装置を含む通信システムであって、前記通信装置は、第一のネットワークにおいて所定の信号処理を実行する第一のネットワークノードと第二のネットワークにおいて前記第一のネットワークノードの機能を仮想マシンにより運用する第二のネットワークノードとを含む複数のネットワークから、通信相手の機器と自律通信が可能な端末に対して前記第二のネットワークノードを選択する第一の手段と、前記端末に関する通信データを、選択された前記第二のネットワークノードに送信する第二の手段と、を含む。
本発明のプログラムは、コンピュータに、第一のネットワークにおいて所定の信号処理を実行する第一のネットワークノードと第二のネットワークにおいて前記第一のネットワークノードの機能を仮想マシンにより運用する第二のネットワークノードとを含む複数のネットワークノードから、通信相手の機器と自律通信が可能な端末に対して前記第二のネットワークノードを選択する処理と、前記端末に関する通信データを、選択された前記第二のネットワークノードに送信する処理と、を実行させる。
以下、本発明の第1の実施形態による通信システムとして、LTEの通信システムの例を示す。ただし、本発明が適用される通信システムはLTEに限定されない。例えば、本発明は、GPRS(General Packet Radio Service)、UMTS(Universal Mobile Telecommunication System)、WiMAX(Worldwide Interoperability for Microwave Access)等にも適用可能である。
図1において、本実施形態による通信システムは、端末1、レガシーネットワークおよび仮想ネットワークを含むものとする。端末1は、携帯電話、PC(Personal Computer)、モバイルルータ、スマートデバイス(家庭の消費電力をモニタするスマートメータ、スマートテレビ、ウェアラブル端末)、M2M(Machine to Machine)デバイス等であり、M2Mデバイスは、例えば、上記のデバイスに加え、産業機器、車、ヘルスケア機器、家電等を含む。
・パケットを処理する機能(User-Plane機能)
・制御シグナリングを処理する機能(C-Plane機能)
・通信を傍受するための合法的傍受(LI:Lawful Interception)機能
PGW4:
・パケットを処理する機能(User-Plane機能)
・通信に応じた課金状態を管理する機能(PCEF:Policy and Charging Enforcement Function)
・QoS等のポリシを制御する機能(PCRF:Policy and Charging Rule Function)
MME5:
・制御シグナリングを処理する機能(C-Plane機能)
・HSS(Home Subscriber Server)と連携して、通信システムの加入者情報を管理する機能
図2は、本実施形態による通信装置の一例である基地局2の構成例を示す。基地局2は、識別部20およびネットワーク切替部21を含む。
基地局2は、端末1が送信する所定のメッセージに基づいて、ネットワークを選択することもできる。以下、図3を参照しながら、基地局2に対して所定のメッセージを送信可能な端末1の構成例を示す。
図4は本発明の第1の実施形態による通信システムの動作例を示すシーケンス図である。
本発明の第2の実施形態によれば、基地局2は、端末1がMTCデバイスであるか否かに応じて、端末1が接続するネットワークノードを選択することができる。第2の実施形態の技術は、第1の実施形態、後述の実施形態のいずれにも適用可能である。なお、MTCデバイスは、上述の実施形態で例示されたM2Mデバイスを含む。
図5に例示されるように、本実施形態による通信システムは図1と同様の構成を有するが、端末1はNon-MTCデバイス1AとMTCデバイス1Bとがあるものとする。Non-MTCデバイス1A、MTCデバイス1Bおよび基地局2の構成は、第1の実施形態と同様なので、同じ参照番号を付して詳細な説明は省略される。また、図5に例示されたネットワークノード(SGW3、PGW4、MME5)の機能も、第1の実施形態と同様であるから詳細な説明は省略される。
<第1動作例>
図6に例示するシーケンスは、3GPP(3rd Generation Partnership Project)の仕様書(TS23.401 v12.3.0)の5.3.2章に記載された“Attach Procedure”に本実施形態による通信方法を適用した第1動作例を示す。
図7-図9を参照しながら、第2の実施形態の第二の動作例を説明する。図7-図9に例示する第二動作例は、3GPPの仕様書(TS23.401 v12.3.0)の5.3.2章に記載された“Attach Procedure”に本実施形態を適用した例である。
次に、第2の実施形態の第3動作例について、図11を参照しながら説明するなお、図11における動作S4-1~動作S4-4は上述の図6の動作S2-1~動作S2-4と同様なので、詳細な説明は省略される。
本発明の第3の実施形態によれば、基地局2は、通信トラフィックの種別に応じて、端末1が接続するネットワークノードを選択することができる。第3の実施形態は、第1、第2の実施形態、あるいは後述の実施形態のいずれにも適用可能である。
図12に例示するように、基地局2およびルータ7は、通信種別に応じて、端末1と外部ネットワークとの間の通信トラフィックが経由するネットワークを、レガシーネットワークおよび仮想ネットワークから選択できる。レガシーネットワークおよび仮想ネットワークの構成は、第1および第2実施形態と同様であるから詳細は省略する。
図16に例示するように、基地局2は、端末1から“Attach Request”を受信すると、それをレガシーネットワークのMME5と仮想ネットワークの仮想MME5Aとにそれぞれ転送する(動作S5-1)。
本発明の第4の実施形態によれば、端末1の位置に関する情報に基づいて、端末1が接続するネットワークノードが選択される。第4の実施形態は、第1-第3の実施形態、後述の実施形態のいずれにも適用可能である。
図17に例示する通信システムは、複数のネットワーク(ここではレガシーネットワークと仮想ネットワーク)と、複数の基地局とを有し、端末1の地理的位置に依存して、接続するネットワークが選択される。レガシーネットワークおよび仮想ネットワークの構成はすでに述べたとおりであるから、詳細は省略する。以下、端末1が接続しうるネットワークは、端末1の位置に依存して、レガシーネットワークあるいは仮想ネットワークのいずれかに決定されるものとする。例えば、端末1は、基地局2(A)のカバーエリアに滞在する場合にはレガシーネットワークに接続され、基地局2(B)のカバーエリアに滞在する場合には仮想ネットワークに接続される。
<第1動作例>
図18において、端末1が基地局2(A)に対して“Attach Request”を送信し、これに応じて基地局2(A)が“Attach Request”をデフォルトのMME(ここでは、レガシーネットワークのMME5)に送信したものとする(動作S6-1)。“Attach Request”には、TAI(Tracking Area ID)とECGI(E-UTRAN Cell Grobal ID)とが含まれる。TAIは、端末1が位置登録を行ったエリアの識別子である。ECGIは、端末1が接続した基地局2のセルの識別子である。
図19に例示する本実施形態の他の動作例では、それぞれの基地局2に対して予めMMEが対応付けられている。例えば、基地局2(A)にはレガシーネットワークのMME5が、基地局2(B)には仮想ネットワークの仮想MME5Aが、それぞれ対応付けられている。
本発明の第5の実施形態によれば、ネットワーク選択のためのポリシを制御装置が集中管理する。よって、ネットワーク選択あるいはネットワークノード選択のためのポリシの運用管理の効率が向上する。第5の実施形態は、第1-第4の実施形態、後述の実施形態のいずれにも適用可能である。
図21において、制御装置8は、ポリシ管理DB(Data Base)80、制御部81およびインターフェース82を含む。
ポリシ管理DB80は、例えば、仮想ネットワークがレガシーネットワークの負荷をオフロードするために用いられるポリシを管理する。ポリシ管理DB80に記憶されるポリシの例は以下の通りである。
・MTCデバイスを仮想ネットワークに接続する。
・非MTCデバイスをレガシーネットワークに接続する。
・所定のMTCデバイス(例えば、スマートメーター)を仮想ネットワークに接続する。
・所定のMTCデバイスグループに属するMTCデバイスを仮想ネットワークに接続する。
・所定のユーザ属性(例えば、プレミアムユーザ)に対応する端末1をレガシーネットワークに接続する。
・所定のユーザ属性(例えば、一般ユーザ)に対応する端末1を仮想ネットワークに接続する。
・通信量が所定値を超過したユーザの端末1を仮想ネットワークに接続する。
・所定の時間帯(たとえばAM1:00-AM4:00)にのみポリシを有効化。(このポリシは、上記のポリシの少なくとも1つと組み合わせて使用される。)
・所定のアプリケーション(例えば、SNSアプリケーション)に関する通信トラフィックを仮想ネットワークに転送する。
・通話に関する通信トラフィックをレガシーネットワークに転送する。
・通話に関する通信トラフィックを、ユーザ毎にラウンドロビンで仮想ネットワークまたはレガシーネットワークのいずれかに転送する。
・所定のアプリケーション(例えば、SNSアプリケーション)に関する通信トラフィックの一部を仮想ネットワークに転送する。
・所定のアプリケーション(例えば、SNSアプリケーション)に関する通信トラフィックを、ユーザ毎にラウンドロビンで仮想ネットワークまたはレガシーネットワークのいずれかに転送する。
・所定の課金特性(例えば、定額課金)に対応する通信トラフィックを仮想ネットワークに接続する。
・所定の課金特性(例えば、従量型課金)に対応する通信トラフィックをレガシーネットワークに接続する。
・所定のQoS特性に関する通信トラフィックを仮想ネットワークに転送する。
・所定の時間帯(Ex:AM1:00-AM4:00)にのみポリシを有効化。(このポリシは、上記のポリシの少なくとも1つと組み合わせて使用される。)
・所定の基地局に接続した端末1を仮想ネットワークに接続する。
・所定のイベントや所定のロケーション(ショッピングモール等)に対応する基地局に接続した端末1を仮想ネットワークに接続する。
・所定のセルに接続した端末1を仮想ネットワークに接続する。
・所定のイベントや所定のロケーション(ショッピングモール等)に対応するセルに接続した端末1を仮想ネットワークに接続する。
・所定の時間帯(たとえばAM1:00-AM4:00)にのみポリシを有効化。(このポリシは、上記のポリシの少なくとも1つと組み合わせて使用される。)
図22において、基地局2はインターフェース25を介して制御装置8と通信するものとする。基地局2は、インターフェース25を介して制御装置8からポリシを受信すると、受信したポリシを識別部20に記憶する。識別部20は、受信したポリシに基づいて、ネットワークを選択する。また、識別部20は、受信したポリシに基づいて、ネットワークノードを選択してもよい。
本発明の第6の実施形態によれば、制御装置が仮想ネットワークのリソースのプロビジョニングを実行できることで、仮想ネットワークの運用管理の効率を向上させることができる。第6の実施形態は、第1-第5の実施形態、後述の実施形態のいずれにも適用可能である。
図23に例示する本実施形態による通信システムは、複数のネットワーク(ここではレガシーネットワークと仮想ネットワーク)と、端末1と、基地局2と、制御装置8と、を有する。レガシーネットワークおよび仮想ネットワークの構成はすでに述べた通りであるから、同一の参照番号を付して詳細は省略する。
図24に例示するように、制御装置8は、上述した第5の実施形態で例示された構成(図21参照)に加え、仮想ネットワークのリソースのプロビジョニングを実行する仮想NW(ネットワーク)制御部83を含む。ただし、本実施形態による制御装置8の構成は図24の例に限定されない。例えば、制御装置8は、基地局2等にネットワーク選択のためのポリシを通知する機能(ポリシー管理DB80等)を備えなくてもよい。また、本実施形態による制御装置は、第5の実施形態による制御装置(図21)と互いに異なる装置であってもよい。
図25に例示するように。通信装置100は、仮想ネットワークにおける仮想ネットワーク機能、すなわち仮想ネットワークノード(例えば、仮想SGW3A、仮想PGW4A、仮想MME5A等)の機能を提供する仮想マシンを運用する装置であり、例えば、サーバ、ルータ等である。
仮想P-GW4A:
・パケットを処理する機能(User-Plane機能)
・通信に応じた課金状態を管理する機能(PCEF:Policy and Charging Enforcement Function)
・QoS等のポリシを制御する機能(PCRF:Policy and Charging Rule Function)
・パケットを処理する機能(User-Plane機能)
・制御シグナリングを処理する機能(C-Plane機能)
・通信を傍受するための合法的傍受(LI:Lawful Interception)機能
・制御シグナリングを処理する機能(C-Plane機能)
・HSS(Home Subscriber Server)と連携して、通信システムの加入者情報を管理する機能
本発明の第7の実施形態によれば、仮想ネットワークのオペレータは、レガシーネットワークのオペレータに対して、仮想ネットワークを貸し出すことができる。仮想ネットワークを有償で貸し出すことにより、仮想ネットワークのオペレータは、仮想ネットワークの利用料金を得ることができる。また、レガシーネットワークのオペレータは、自らレガシーネットワークへの設備投資をしなくとも、ネットワークを仮想的に増強できる。第7の実施形態は、第1-第6の実施形態のいずれにも適用可能である。
図26に例示する本実施形態による通信システムは、それぞれのオペレータにより運用される複数のネットワーク(ここではレガシーネットワークと仮想ネットワーク)と、端末1と、基地局2と、を有し、端末1がレガシーネットワークの加入者端末であるものとする。レガシーネットワークおよび仮想ネットワークの構成はすでに述べた通りであるから、同一の参照番号を付して詳細は省略する。
図28に例示するように、基地局2は、端末1から受信した“Attach Request”を仮想MME5Aに送信する(動作S7-1)。この“Attach Request”の送信先として、基地局2が、動作S7-1に先立って、図6の動作S2-5および動作S2-6により仮想MME5Aを選択することができる。また、図8の動作S3-6~動作S3-9により、“Attach Request”の送信先に仮想MME5Aを選択してもよい。また、図11の動作S4-5~動作S4-7により、“Attach Request”の送信先に仮想MME5Aを選択してもよい。さらに、図16、図18あるいは図19に例示された動作に基づいて、“Attach Request”を仮想MME5Aに送信してもよい。
図29に例示するように、基地局2は、端末1から受信した“Attach Request”を、仮想MME5Aに送信する(動作S8-1)。基地局2は、例えば、動作S8-1に先立って、図6の動作S2-5およびS2-6により、“Attach Request”の送信先に仮想MME5Aを選択する。また、例えば、基地局2は、図8の動作S3-6~動作S3-9により、“Attach Request”の送信先に仮想MME5Aを選択してもよい。また、例えば、基地局2は、図11の動作S4-5~動作S4-7により、“Attach Request”の送信先に仮想MME5Aを選択してもよい。また、例えば、基地局2は、図16、図18および図19に例示された動作に基づいて、“Attach Request”を仮想MME5Aに送信してもよい。
図30に例示する通信システムでは、仮想ネットワークのオペレータ(オペレータB)が、仮想ネットワークをオペレータBから借りたオペレータの通信トラフィックをモニタすることができる。
10 メッセージ生成部
11 通信部
2 基地局
20 識別部
21 ネットワーク切替部
22 スイッチ部
23 ポート
24 ポリシ管理DB
3 SGW
3A 仮想SGW
4 PGW
4A 仮想PGW
40 仮想PCRF
5 MME
50 仮想エンティティ管理部
51 制御部
5A 仮想MME
7 ルータ
70 スイッチ部
71 ポート
72 ポリシ管理DB
8 制御装置
80 ポリシ管理DB
81 制御部
82 インターフェース
83 仮想NW制御部
100 通信装置
110 制御部
120 仮想ネットワーク機能
Claims (16)
- 第一のネットワークにおいて所定の信号処理を実行する第一のネットワークノードと第二のネットワークにおいて前記第一のネットワークノードの機能を仮想マシンにより運用する第二のネットワークノードとを含む複数のネットワークノードから、通信相手の機器と自律通信が可能な端末に対して前記第二のネットワークノードを選択する第一の手段と、
前記端末に関する通信データを、選択された前記第二のネットワークノードに送信する第二の手段と
を含むことを特徴とする通信装置。 - 前記第二の手段は、前記複数のネットワークの少なくとも1つと前記端末との接続処理に関する通信データを、選択された前記第二のネットワークノードに送信する
ことを特徴とする請求項1の通信装置。 - 前記第一の手段は、動的に構築された前記仮想マシンにより運用される前記第二のネットワークノードを、前記端末に対して選択する
ことを特徴とする請求項1又は2の通信装置。 - 前記第一の手段は、前記端末の通信データの処理に関する要求条件に応じて動的に構築された前記仮想マシンにより運用される前記第二のネットワークノードを、前記端末に対して選択する
ことを特徴とする請求項1乃至3のいずれか1項の通信装置。 - 前記第一の手段は、前記端末の通信データが発生するタイミングに応じて動的に構築された前記仮想マシンにより運用される前記第二のネットワークノードを、前記端末に対して選択する
ことを特徴とする請求項1乃至4のいずれか1項の通信装置。 - 前記第一の手段は、前記端末から送信された接続要求に含まれる情報に基づいて、当該端末に対して前記第二のネットワークノードを選択する
ことを特徴とする請求項1乃至5のいずれか1項の通信装置。 - 前記第一の手段は、通信相手の機器と自律通信が可能な前記端末のうち、所定のグループに属する端末に対して前記第二のネットワークノードを選択する
ことを特徴とする請求項1乃至6のいずれか1項の通信装置。 - 第一のネットワークにおいて所定の信号処理を実行する第一のネットワークノードと第二のネットワークにおいて前記第一のネットワークノードの機能を仮想マシンにより運用する第二のネットワークノードとを含む複数のネットワークノードから、通信相手の機器と自律通信が可能な端末に対して前記第二のネットワークノードを選択し、
前記端末に関する通信データを、選択された前記第二のネットワークノードに送信する
ことを特徴とする通信方法。 - 前記複数のネットワークの少なくとも1つと前記端末との接続処理に関する通信データを、選択された前記第二のネットワークノードに送信する
ことを特徴とする請求項8の通信方法。 - 動的に構築された前記仮想マシンにより運用される前記第二のネットワークノードを、前記端末に対して選択する
ことを特徴とする請求項8又は9の通信方法。 - 前記端末の通信データの処理に関する要求条件に応じて動的に構築された前記仮想マシンにより運用される前記第二のネットワークノードを、前記端末に対して選択する
ことを特徴とする請求項8乃至10のいずれか1項の通信方法。 - 前記端末の通信データが発生するタイミングに応じて動的に構築された前記仮想マシンにより運用される前記第二のネットワークノードを、前記端末に対して選択する
ことを特徴とする請求項8乃至11のいずれか1項の通信方法。 - 前記端末から送信された接続要求に含まれる情報に基づいて、当該端末に対して前記第二のネットワークノードを選択する
ことを特徴とする請求項8乃至12のいずれか1項の通信方法。 - 通信相手の機器と自律通信が可能な前記端末のうち、所定のグループに属する端末に対して前記第二のネットワークノードを選択する
ことを特徴とする請求項8乃至13のいずれか1項の通信方法。 - 端末に関する通信データを処理する通信装置を含む通信システムであって、
前記通信装置は、
第一のネットワークにおいて所定の信号処理を実行する第一のネットワークノードと第二のネットワークにおいて前記第一のネットワークノードの機能を仮想マシンにより運用する第二のネットワークノードとを含む複数のネットワークから、通信相手の機器と自律通信が可能な端末に対して前記第二のネットワークノードを選択する第一の手段と、
前記端末に関する通信データを、選択された前記第二のネットワークノードに送信する第二の手段と、
を含むことを特徴とする通信システム。 - コンピュータに、
第一のネットワークにおいて所定の信号処理を実行する第一のネットワークノードと第二のネットワークにおいて前記第一のネットワークノードの機能を仮想マシンにより運用する第二のネットワークノードとを含む複数のネットワークノードから、通信相手の機器と自律通信が可能な端末に対して前記第二のネットワークノードを選択する処理と、
前記端末に関する通信データを、選択された前記第二のネットワークノードに送信する処理と
を実行させることを特徴とするプログラム。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016520946A JP6460101B2 (ja) | 2014-05-23 | 2015-05-22 | 通信装置、通信方法、通信システムおよびプログラム |
CN201580026855.4A CN106416156B (zh) | 2014-05-23 | 2015-05-22 | 通信装置、通信方法、通信系统和程序 |
US15/313,490 US10299183B2 (en) | 2014-05-23 | 2015-05-22 | Communication apparatus, communication method, communication system, and program |
EP15796069.1A EP3148138B1 (en) | 2014-05-23 | 2015-05-22 | Communication apparatus, communication method, and communication system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014106616 | 2014-05-23 | ||
JP2014-106616 | 2014-05-23 |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/325,689 A-371-Of-International US10230886B2 (en) | 2014-07-30 | 2015-05-22 | Image pickup apparatus to capture a self image |
US16/268,010 Continuation US10477092B2 (en) | 2014-07-30 | 2019-02-05 | Image pickup apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015178032A1 true WO2015178032A1 (ja) | 2015-11-26 |
Family
ID=54553713
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/002586 WO2015178032A1 (ja) | 2014-05-23 | 2015-05-22 | 通信装置、通信方法、通信システムおよびプログラム |
Country Status (5)
Country | Link |
---|---|
US (1) | US10299183B2 (ja) |
EP (1) | EP3148138B1 (ja) |
JP (1) | JP6460101B2 (ja) |
CN (1) | CN106416156B (ja) |
WO (1) | WO2015178032A1 (ja) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2018137662A (ja) * | 2017-02-23 | 2018-08-30 | 日本無線株式会社 | 通信装置、および、通信方法 |
JP2018137661A (ja) * | 2017-02-23 | 2018-08-30 | 日本無線株式会社 | 通信装置、および、通信方法 |
JP2019500819A (ja) * | 2015-12-30 | 2019-01-10 | ドイッチェ テレコム アーゲー | 通信ネットワークを介して通信端末の通信接続を確立する方法 |
JP2021044716A (ja) * | 2019-09-12 | 2021-03-18 | 三菱電機株式会社 | 通信網選択装置及び通信システム |
JP7334396B2 (ja) | 2016-04-22 | 2023-08-29 | マーベル アジア ピーティーイー、リミテッド | 動的仮想システム・オン・チップのための方法および装置 |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108667634B (zh) * | 2017-03-27 | 2021-07-09 | 北京嘀嘀无限科技发展有限公司 | 通信方法、装置及存储介质 |
US10231116B2 (en) * | 2017-06-21 | 2019-03-12 | International Business Machines Corporation | Communication access services for mobile phones |
CN107948970B (zh) * | 2017-11-15 | 2020-12-08 | 中国联合网络通信集团有限公司 | 附属终端的实名制入网方法、系统及移动终端 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009124367A (ja) * | 2007-11-14 | 2009-06-04 | Nec Corp | 通信装置、ネットワーク選択方法、及びネットワーク選択プログラム |
US20110213871A1 (en) * | 2010-03-01 | 2011-09-01 | Interdigital Patent Holdings, Inc. | Machine-to-machine gateway architecture and functionality |
US20130238816A1 (en) * | 2010-11-24 | 2013-09-12 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and Arrangements For Enabling Data Transmission Between a Mobile Device and a Static Destination Address |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7965729B2 (en) * | 2001-05-23 | 2011-06-21 | Polytechnic University | Transferring data such as files |
GB2455939B (en) * | 2006-09-19 | 2011-04-27 | Firetide Inc | A multi-channel assignment method for multi-radio multi-hop wireless mesh networks |
US8072900B2 (en) | 2006-12-29 | 2011-12-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Automatic distribution of server and gateway information for pool configuration |
JP4970219B2 (ja) | 2007-11-08 | 2012-07-04 | Kddi株式会社 | 無線lanの輻輳状態を判定する無線端末、プログラム及び方法 |
EP2297893A2 (en) * | 2008-06-30 | 2011-03-23 | Nokia Siemens Networks OY | Selecting between normal and virtual dual layer ack/nack |
US8130641B2 (en) | 2009-03-13 | 2012-03-06 | Hewlett-Packard Development Company, L.P. | Methods and systems for managing network traffic within a virtual network system |
CN201699992U (zh) * | 2010-05-14 | 2011-01-05 | 北京邦讯技术有限公司 | 一种无线接入点共享基站带宽的系统 |
US9232544B2 (en) * | 2010-05-26 | 2016-01-05 | Telefonaktiebolaget L M Ericsson (Publ) | Connection states for a user entity in a serving gateway of an evolved packet core system |
US8699433B2 (en) * | 2010-07-21 | 2014-04-15 | Telefonaktiebolaget L M Ericsson (Publ) | System and method for providing mobility with a split home agent architecture |
CN102348214A (zh) | 2010-08-02 | 2012-02-08 | 中国移动通信集团公司 | 确定终端类型的方法、缓解网络拥塞的方法以及相关装置 |
PL2523401T3 (pl) * | 2011-05-10 | 2017-11-30 | Airbus Defence And Space Oy | Sieci wirtualne w obrębie sieci fizycznej |
US20130016649A1 (en) * | 2011-07-12 | 2013-01-17 | Qualcomm Incorporated | System design for user equipment relays |
CN103731811B (zh) * | 2012-10-11 | 2018-08-31 | 中兴通讯股份有限公司 | 一种演进的分组核心网络实现移动性管理的方法和系统 |
US9170834B2 (en) | 2012-10-31 | 2015-10-27 | Google Inc. | Metadata-based virtual machine configuration |
US9270596B2 (en) * | 2012-11-26 | 2016-02-23 | Verizon Patent And Licensing Inc. | Selection of virtual network elements |
JP2015216494A (ja) * | 2014-05-09 | 2015-12-03 | 株式会社東芝 | ゲートウェイ装置 |
-
2015
- 2015-05-22 WO PCT/JP2015/002586 patent/WO2015178032A1/ja active Application Filing
- 2015-05-22 US US15/313,490 patent/US10299183B2/en active Active
- 2015-05-22 JP JP2016520946A patent/JP6460101B2/ja active Active
- 2015-05-22 EP EP15796069.1A patent/EP3148138B1/en active Active
- 2015-05-22 CN CN201580026855.4A patent/CN106416156B/zh active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009124367A (ja) * | 2007-11-14 | 2009-06-04 | Nec Corp | 通信装置、ネットワーク選択方法、及びネットワーク選択プログラム |
US20110213871A1 (en) * | 2010-03-01 | 2011-09-01 | Interdigital Patent Holdings, Inc. | Machine-to-machine gateway architecture and functionality |
US20130238816A1 (en) * | 2010-11-24 | 2013-09-12 | Telefonaktiebolaget L M Ericsson (Publ) | Methods and Arrangements For Enabling Data Transmission Between a Mobile Device and a Static Destination Address |
Non-Patent Citations (1)
Title |
---|
See also references of EP3148138A4 * |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2019500819A (ja) * | 2015-12-30 | 2019-01-10 | ドイッチェ テレコム アーゲー | 通信ネットワークを介して通信端末の通信接続を確立する方法 |
US11057828B2 (en) | 2015-12-30 | 2021-07-06 | Deutsche Telekom Ag | Method for establishing a communication connection of a communication terminal via a communication network |
JP7334396B2 (ja) | 2016-04-22 | 2023-08-29 | マーベル アジア ピーティーイー、リミテッド | 動的仮想システム・オン・チップのための方法および装置 |
JP2018137662A (ja) * | 2017-02-23 | 2018-08-30 | 日本無線株式会社 | 通信装置、および、通信方法 |
JP2018137661A (ja) * | 2017-02-23 | 2018-08-30 | 日本無線株式会社 | 通信装置、および、通信方法 |
JP6990976B2 (ja) | 2017-02-23 | 2022-01-12 | 日本無線株式会社 | 通信装置、および、通信方法 |
JP2021044716A (ja) * | 2019-09-12 | 2021-03-18 | 三菱電機株式会社 | 通信網選択装置及び通信システム |
JP7224264B2 (ja) | 2019-09-12 | 2023-02-17 | 三菱電機株式会社 | 通信網選択装置及び通信システム |
Also Published As
Publication number | Publication date |
---|---|
EP3148138A1 (en) | 2017-03-29 |
JPWO2015178032A1 (ja) | 2017-04-27 |
US10299183B2 (en) | 2019-05-21 |
JP6460101B2 (ja) | 2019-01-30 |
EP3148138B1 (en) | 2021-01-06 |
EP3148138A4 (en) | 2018-02-21 |
US20170188283A1 (en) | 2017-06-29 |
CN106416156A (zh) | 2017-02-15 |
CN106416156B (zh) | 2020-04-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015178033A1 (ja) | 基地局、通信方法、mmeおよび通信システム | |
JP6460101B2 (ja) | 通信装置、通信方法、通信システムおよびプログラム | |
WO2015178035A1 (ja) | 通信装置、通信方法、通信システムおよびプログラム | |
WO2015178031A1 (ja) | 通信装置、通信方法、通信システムおよびプログラム | |
WO2016157821A1 (ja) | 通信装置、通信システム及び通信方法 | |
EP3223561B1 (en) | Offloading traffic of an mtc device | |
WO2016079993A1 (ja) | 基地局、通信装置、通信方法、通信システム及び記憶媒体 | |
WO2016079991A1 (ja) | 通信装置、通信方法、通信システム及び記憶媒体 | |
WO2015178034A1 (ja) | 制御装置、制御方法、通信システムおよびプログラム | |
US11057764B2 (en) | Communication device, communication method, communication system, and storage medium | |
WO2016079989A1 (ja) | 通信装置、通信方法、通信システム及び記憶媒体 | |
JP2016192641A (ja) | 端末、通信システム及び通信方法 | |
JP2016192642A (ja) | 通信システム、通信装置、通信方法及びプログラム | |
JP2016192643A (ja) | 制御装置、通信システム、通信方法及びプログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15796069 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2016520946 Country of ref document: JP Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15313490 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2015796069 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2015796069 Country of ref document: EP |