WO2014077352A1 - ネットワークシステムと方法と装置並びにプログラム - Google Patents
ネットワークシステムと方法と装置並びにプログラム Download PDFInfo
- Publication number
- WO2014077352A1 WO2014077352A1 PCT/JP2013/080875 JP2013080875W WO2014077352A1 WO 2014077352 A1 WO2014077352 A1 WO 2014077352A1 JP 2013080875 W JP2013080875 W JP 2013080875W WO 2014077352 A1 WO2014077352 A1 WO 2014077352A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- offload
- network
- base station
- packet
- switch
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 42
- 238000012546 transfer Methods 0.000 claims abstract description 43
- 230000004044 response Effects 0.000 claims description 65
- 238000012545 processing Methods 0.000 claims description 41
- 230000008569 process Effects 0.000 claims description 20
- 230000006870 function Effects 0.000 description 96
- 101100314162 Candida albicans (strain SC5314 / ATCC MYA-2876) YBL053 gene Proteins 0.000 description 64
- 101150044955 tof1 gene Proteins 0.000 description 64
- 230000005540 biological transmission Effects 0.000 description 39
- 238000010586 diagram Methods 0.000 description 13
- 238000004891 communication Methods 0.000 description 12
- 101100370014 Neurospora crassa (strain ATCC 24698 / 74-OR23-1A / CBS 708.71 / DSM 1257 / FGSC 987) tof-1 gene Proteins 0.000 description 10
- 101100370021 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) TOF2 gene Proteins 0.000 description 9
- 230000009471 action Effects 0.000 description 8
- 210000004027 cell Anatomy 0.000 description 7
- RTZKZFJDLAIYFH-UHFFFAOYSA-N Diethyl ether Chemical compound CCOCC RTZKZFJDLAIYFH-UHFFFAOYSA-N 0.000 description 6
- 238000012217 deletion Methods 0.000 description 6
- 230000037430 deletion Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 201000006284 orofacial cleft 1 Diseases 0.000 description 6
- 208000010376 orofacial cleft 2 Diseases 0.000 description 6
- 210000001956 EPC Anatomy 0.000 description 5
- 238000004364 calculation method Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000007689 inspection Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000009467 reduction Effects 0.000 description 4
- 239000004065 semiconductor Substances 0.000 description 4
- 238000001914 filtration Methods 0.000 description 3
- 230000007704 transition Effects 0.000 description 3
- 230000004913 activation Effects 0.000 description 2
- 238000013475 authorization Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000006835 compression Effects 0.000 description 2
- 238000007906 compression Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 241000760358 Enodes Species 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 230000009849 deactivation Effects 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 238000004880 explosion Methods 0.000 description 1
- 238000005111 flow chemistry technique Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000007562 laser obscuration time method Methods 0.000 description 1
- 239000003550 marker Substances 0.000 description 1
- 238000005259 measurement Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
- 230000005641 tunneling Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
- H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/302—Route determination based on requested QoS
- H04L45/306—Route determination based on the nature of the carried application
-
- 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/0289—Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/22—Alternate routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W40/00—Communication routing or communication path finding
- H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/082—Mobility data transfer for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
Definitions
- the present invention is based on a Japanese patent application: Japanese Patent Application No. 2012-252426 (filed on November 16, 2012), and the entire description of the application is incorporated herein by reference.
- the present invention relates to a network system, method, apparatus, and program.
- a private network for example, a home LAN (Local Area Network) is connected to a base station (H (e) NB) such as a femto cell or a home cell.
- H (e) NB a base station
- the traffic between the host on the home network (Home Networks) and the enterprise (enterprise network)) and the mobile terminal UE (User Equipment) is not transferred to the core network. Instead, the traffic is offloaded from the H (e) NB to the private network via the local gateway (L-GW) (see Non-Patent Document 1: 5.2.3).
- H (e) NB represents HNB (Home (Node B) or HeNB (Home-evolved Node B).
- SIPTO Select IP Traffic Offload
- APN Access Point Name
- APN Access Point Name
- destination IP Internet Protocol
- FIG. 19 is a diagram based on FIG. 5.5.2.1 of Non-Patent Document 1.
- TOF is provided in Iu-PS and provides a standard Iu-PS interface to RNC and SGSN.
- Iu is an interface between the RNC and a core network (MSC (mobile Switching Center) or SGSN), and Iu-PS is an interface between the RNC and a packet (Switched) core network.
- Gi is an interface between GGSN (Gateway GPRS Support Node) and PDN (Packet Data Network).
- the TOF on the Iu-PS performs NAS (Non Access Stratum), RANAP (Radio Access Network Application Part) message inspection, acquires subscriber information, and establishes a local UE offload context. Further, the TOF acquires PDP (Packet Data Data Protocol) context information and establishes a local session offload context. The TOF determines whether to perform offloading based on the above information, for example, during an attach and PDP activation procedure. During offloading, TOF draws uplink traffic from GTP-U (GPRS Tunneling Protocol for User Plane) tunnel (tunnel between UE and GGSN) and executes NAT by NAT (Network Address Translation) gateway, for example. Offload.
- GTP-U GPRS Tunneling Protocol for User Plane
- NAT Network Address Translation
- the NAT performs address conversion from a private IP address to a global IP address in a router or the like.
- IP address and TCP (transmission control protocol) / UDP (user datagram protocol) port number are converted as a set.
- the TOF also performs reverse NAT on the downlink offload traffic and inserts it back into the GTP-U tunnel.
- the SIPTO solution 4 determines the offload by packet inspection and NAT based on the user, APN, service type, IP address, etc., and the Iu-PS interface that is an interface (user plane) between the RNC and the SGSN. Offload data traffic above. Note that it is necessary to add a local packet data network gateway (L-PGW (Packet Data Network) Gateway) to LTE (Long Term Term Evolution).
- L-PGW Packet Data Network Gateway
- SIPTO Solution 5 supports macrocells and HNB, and can support both UMTS and LTE (also supports multiple PDN connections and non-compatible UEs) It is connected to the Internet or the like via the L-PGW (L-GGSN) connected to the serving gateway SGW (RNC) (see Non-Patent Document 1, Figures 5.6.3.2 to 5.6.3.3, 5.6.3.4). SGW is also expressed as S-GW.
- traffic may be offloaded to other networks.
- a mobile terminal such as a smartphone or tablet with a Wi-Fi (Wireless Fidelity) connection function to the Internet from a Wi-Fi access point or other wireless LAN (Wireless Local Area Network) (Wi-Fi Also called Fi Offroad).
- Wi-Fi Wireless Fidelity
- Wi-Fi Wireless Local Area Network
- the present invention has been made in view of the above-mentioned problems, and its main purpose is to suppress an increase in network facilities due to an increase in traffic, and to realize a mobility, traffic offload, system, method, and apparatus , To provide a program.
- switch means disposed between the first network and the second network; Offload determination means for determining whether or not traffic is offloaded to the first network, and setting the offload path that bypasses the first network to the switch means when offloading When, With When offloading traffic to the first network, a system is provided in which a packet to be offloaded is transferred between the offload path and the second network via the switch means. .
- offload means for offloading traffic to the first network; Offload determination means for instructing the offload means to offload traffic to the first network; With The offload means receives the offload instruction, determines whether or not the received packet is offloaded, and transfers the packet through an offload route that bypasses the first network at the time of offload.
- a system is provided.
- the switch means disposed between the first network and the second network is performed, and when traffic is offloaded to the first network, the offload target packet includes the offload path and the A method is provided for transferring between second networks via the switch means.
- an offload unit that offloads traffic to the first network receives an offload instruction from an offload determination unit that determines whether or not there is an offload
- the reception is performed.
- an offload route setting request is transmitted to a node provided with offload determination means, and the presence or absence of offload is determined for a received packet.
- a base station apparatus is provided that transfers the packet to an offload path that bypasses the core network.
- an offload instruction is received from an offload determination unit that instructs to offload traffic to the core network.
- a base station apparatus that determines whether or not there is an offload with respect to a received packet and transfers a packet to be offloaded to an offload path that bypasses the core network.
- an offloading route setting request is received from an offloading unit that offloads traffic to the first network
- the first network and the second network are interposed.
- a control device is provided that sets an offload path that connects to the second network, bypassing the first network, for a switch to be connected.
- an offload instruction is transmitted to the offload unit.
- the offload means is provided with a control device that, when the received packet is a packet to be offloaded, causes the offload to be offloaded to the set offload route.
- a computer constituting the base station apparatus When it is determined that a packet arriving from a mobile terminal via a radio bearer falls under the object of offload, a connection request for an offload route that bypasses the first network is transmitted directly or via the first network. Processing to transmit to a switch disposed between the first network and the second network; When a predetermined command is received from a node that manages the mobility of the mobile terminal, a program for executing a process of transmitting a request for disconnecting the offload path to the switch is provided.
- a computer-readable recording medium semiconductor memory, magnetic disk / optical disk in which the program is recorded is provided.
- a computer constituting a control device that controls a switch disposed between a first network and a second network includes: When a connection request for an offload route that bypasses the first network is received from the base station device via the switch, the packet transferred from the base station device to the offload route is directed to the second network. And the switch is set to transfer the packet from the second network to the node via the offload path, and a connection response to the connection request for the offload path is transmitted to the base station.
- the gateway node of the first network is set in the switch to connect to the second network, and A program for executing a process of returning a disconnection response to an offload path disconnection request to the base station apparatus is provided.
- a computer-readable recording medium semiconductor memory, magnetic disk / optical disk in which the program is recorded is provided.
- the present invention it is possible to suppress the addition of mobile network equipment due to traffic increase, and realize mobility on traffic offload.
- switch means (SW) disposed between the first network (NW1) and the second network (NW2), and offloading of traffic to the first network (NW1)
- an off-load determination unit is provided for setting the off-load route that bypasses the first network (NW1) to the switch unit (SW).
- the packet to be offloaded is routed between the offload path and the second network (NW2) via the switch means (SW). Transferred.
- the offload means for offloading the traffic to the first network (NW1) transfers the packet to the offload path when the traffic is offloaded.
- the packet transferred to the offload path is transmitted to the second network (NW2) via the switch means (SW).
- the offload means when traffic is offloaded to the first network (NW1), the offload means transmits an offload route setting request to the offload determination means. In response to the offload route setting request, the offload determination means sets an offload route for the switch (SW) between the first and second networks.
- the offload means and the second network (NW2) are connected via the offload path and the switch means (SW), and packets transmitted and received between the mobile terminal and the second network (NW2) are:
- the data is transferred on the offload route that bypasses the first network (NW1).
- the first network (NW1) and the second network (NW2) may be a core network (CN) and a packet data network (PDN), respectively.
- the offload determination unit and the offload unit may be implemented in, for example, an open flow controller (OFC) and a base station with an offload function.
- the offload determination unit may be implemented in MME (Mobility Management Entity), SGSN, or the like that is a node that manages the mobility of the mobile terminal.
- the offload means may be mounted on a base station with an offload function, a SIPTO gateway, or the like.
- the present invention is not limited to a configuration in which the offload determination unit and the offload unit are mounted on separate nodes.
- the offload determination unit and the offload unit may be integrated and mounted on one network node, for example, a base station.
- an offload means for offloading traffic to the first network (NW1) and an instruction for offloading traffic to the first network (NW1) And offload determination means for the offload means.
- the offload means receives the offload instruction, determines whether or not there is an offload for the received packet, and uses the received packet to be offloaded for offload that bypasses the first network (NW1). Forward to route.
- the offload unit transmits an offload route setting request to the offload determination unit.
- the offload determination unit notifies the offload unit of an offload instruction.
- the offload determination means switches the setting of the offload path that bypasses the first network (NW1) to the switch means (SW) between the first network (NW1) and the second network (NW2). To do.
- the offload means and the second network (NW2) are connected to each other via the offload path and the switch means (SW).
- a node (eg, 102 in FIG. 1, 124 in FIG. 15, 133 in FIG. 16) having a function of offloading traffic to a core network (CN), and the core
- the gateway nodes of the network for example, the PGW (PDN Gateway) of the S / P-GW (SGW / PGW) 103 in FIG. 1 and FIG. 16 and the PGW 103P in FIG. 15)
- the external packet data network in FIG. 1, FIG. 15, FIG. 16
- a switch (OFS) (105 in FIGS. 1, 15, and 16) disposed between the PDNs 104).
- the switch (OFS) sends the node (for example, 102 in FIG.
- the node for example, 102 in FIG. 1, 124 in FIG. 15, 133 in FIG. 16
- the switch is a gateway node of the core network (CN)
- the PGW of the S / P-GW 103 in FIGS. 1 and 16 and the PGW 103P in FIG. 15 are connected to the external packet data network (the PDN 104 in FIGS. 1, 15 and 16).
- the packet corresponds to the unit of the data string, and includes, for example, a layer 3 (network layer) packet, a frame in the case of layer 2 (data link layer), and the like.
- FIG. 1 An embodiment of the present invention will be described with reference to FIG. 1 corresponds to the embodiment described with reference to FIG. 20A, and the first and second networks are a core network and a PDN (Packet Data Network), respectively.
- SGi (2G / 3G (2/3 generation)
- RP reference point
- Gi is arranged corresponding to the switch (OFS) 105, and at the time of traffic offload (TOF), uplink data traffic from the mobile terminal 101 is transmitted at a traffic offload node of a radio access network (RAN).
- RAN radio access network
- the traffic offload node of the radio access network is an eNB (evolved Node B) with a TOF function (103 in FIG. 1), UTRAN (Universal Terrestrial Random Access).
- RAN Evolved Universal Terrestrial Random Access
- UTRAN Universal Terrestrial Random Access
- Network is, for example, the above-described TOF on Iu-PS (124 in FIG. 15)).
- Downlink traffic from the PDN 104 bypasses the core network (CN) from the switch 105, is transferred to the traffic offload node of the radio access network (RAN), and is wirelessly transmitted to the mobile terminal 101.
- uplink data traffic from the mobile terminal 101 is transferred to the PDN 104 via the radio access network (RAN), the core network (CN), and the switch 105.
- Downlink traffic from the PDN 104 is transmitted from the switch 105 to the mobile terminal 101 via the core network (CN) and the radio access network (RAN).
- the switch 105 is an open flow switch (OFS). Further, an open flow controller 106 for controlling the open flow switch (OFS) is provided.
- the OpenFlow controller 106 sets the flow during traffic offload in the flow table of the OpenFlow switch (OFS).
- the flow set in the flow table of the open flow switch (OFS) may have a non-offload path (PGW) as a default value.
- PGW non-offload path
- OpenFlow is a network control technology advocated by the OpenFlow switch consortium, and includes identifiers such as physical port numbers (L1), MAC (Media Access Control) addresses (L2), IP addresses (L3), and port numbers (L4).
- L1 physical port numbers
- L2 Media Access Control
- L3 IP addresses
- L4 port numbers
- a series of communications determined by the combination is defined as a “flow” to realize path control in units of flows.
- An OpenFlow Switch (abbreviated as OFS) that functions as a forwarding node operates according to a flow table instructed to be added or rewritten by an OpenFlow Controller (abbreviated as OFC).
- OFS OpenFlow Switch
- OFC OpenFlow Controller
- rules filtering conditions to be checked against packet header information
- statistical information can be specified as a counter, including flow statistical information such as the number of packets, the number of bytes, and the period during which the flow is active) , Including actions (flow processing, packet forwarding (Forward), drop (Drop), modification of a specific field of the packet (Modify-Field) modification, etc.) that specify processing to be applied to a packet that matches the rule.
- the OFS searches the flow table in the OFS and matches (matches) the packet header information with the rule. Any combination of layer 1 (L1) to layer 4 (L4) can be used as a header field to be verified. An example is shown below.
- L1 Ingress Port (switch physical port number);
- L2 Ether src (source MAC address), Ether dst (destination MAC address), Ether type, VLAN (Virtual Local Area Network) -id, VLAN priority;
- L3 IP src (source IP address), IP dst (destination IP address), IP protocol type, TOS (Type Of Service) value;
- L4 Transmission Control Protocol (TCP) / User Datagram Protocol (UDP) src port (source L4 port number), TCP / UDP dst port (destination L4 port number)
- the OFS transfers the received packet to the OFC using a secure channel. OFC performs route calculation based on the transmission source / destination information of the received packet, determines the transfer route of the received packet, and realizes the determined transfer route for all OFS on the transfer route Set the flow table (flow setup).
- the OFC that has performed the flow setup transfers the received packet to, for example, the OFS that is the exit of the flow, and transmits the packet to the destination via the OFS that is the exit of the flow. Thereafter, the header information of the packet belonging to the same flow as the received packet matches the rule in the flow table of the OFS in which the flow setup is performed, and the transfer of the packet is performed according to the set flow table (rule and action).
- Each OFS on the route is transferred and sent to the destination terminal.
- a packet that does not match is often a packet transferred at the beginning of a certain flow. Such packets are also collectively referred to as “first packets”.
- FIG. 2 is a diagram illustrating an embodiment of the present invention.
- a base station eNB eNode B (a base station eNB with an offload function) connected to a mobile terminal (UE) (User Equipment) 101 and a UE 101 within a service area via a radio link and having a traffic offload function 102) (abbreviated as “+ TOF”) and a station 110.
- the station 110 includes a S / P-GW 103, an OFS 105, an OFC 106, a RADIUS (Remote Authentication In Dial User In Service) server 108 that functions as an AAA server that controls authentication, authorization, and accounting.
- 3 includes a router 109 that performs relay control, and the router 109 is connected to the PDN 104.
- the router 109 terminates the MAC address when relaying, and the MAC frame transmitted by the router becomes the MAC address of the port of the router 109.
- MME Mobility Management Entity
- HSS Home Subscriber Server
- PCRF Policy and Charging Rules
- FIG. 2 although not particularly limited, a layer 2 switch (L2SW) is connected to a local station (base station (eNB + TOF) 102 having an offload function) and a station building one level lower than the station 110. 110).
- L2SW layer 2 switch
- eNB + TOF base station
- one PGW is connected to the OFS 105 in the vicinity of the router 109.
- a scalable system configuration (subscription) is adopted in which a plurality of PGWs are connected to the OFS functioning as a layer 2 switch.
- System expansion / reduction corresponding to the increase / reduction of the user and the increase / reduction of the load), or a redundant configuration.
- OFS network scalability is easily improved.
- the OFC 106 adds an offload route 107 for each UE 101 based on a notification from the base station with an offload function (eNB + TOF) 102 (route 107 between the eNB + TOF 102 and the OFS 105 in FIG. 2), and sets the OFS 105.
- the OFS 105 follows the flow table (rules and actions set for each flow) set up from the OFC 106 at the time of offloading, and the uplink packet offloaded by the base station (eNB + TOF) 102 with the offload function.
- the packet is transferred to the router 109 and transmitted to the PDN 104, and the downlink packet transferred from the PDN 104 via the router 109 is transferred to the base station (eNB + TOF) 102 with an offload function.
- the OFS 105 forwards the uplink packet transferred from the base station (eNB + TOF) 102 with an offload function to the S / P-GW 103 to the router 109 in accordance with the flow table set up from the OFC 106 during non-offload.
- the downlink packet transmitted to the PDN 104 and transferred from the PDN 104 via the router 109 is transferred to the base station (eNB + TOF) 102 with an offload function via the S / P-GW 103.
- the RADUIS server performs authentication by connecting to the PGW, for example, but is also connected to the OFS 105 at the same time.
- the SGW Serving Gateway
- the PGW Packet Control Gateway
- the PGW Packet Control Gateway
- a network can be selected according to each application, such as Web browsing on the mobile terminal (UE) 101, mail acquisition, Tweet, settlement, video browsing, and the like.
- an optimal communication network can be used when the UE 101 receives a communication service by selecting a communication network for each flow.
- FIG. 3 is a diagram illustrating an example of the configuration of FIGS. 1 and 2. 3, the same elements as those in FIGS. 1 and 2 are denoted by the same reference numerals. Each element is outlined below.
- the eNB 102a is connected to the SGW via the S1-U interface and is connected to the MME via the S1-MME interface.
- the base stations 102-1 and 102-2 are provided with the traffic offload (TOF) function according to the present invention in the eNB 102a, and are denoted as eNB + TOF as described above.
- TOF traffic offload
- the SGW (Serving Gateway) of the S / P-GW 103 routes and transfers user data packets, and at the same time, functions as a mobility anchor for the user plane during inter-eNB handover.
- the SGW acts as an anchor for mobility between LTE and other 3GPP technologies (eg, terminates the S4 interface and relays traffic between the 2G / 3G system and the PGW). For idle UEs, the SGW terminates the downlink data path and triggers paging when downlink data arrives.
- the SGW manages and stores UE context (for example, IP bearer service parameters and network internal routing information).
- the MME (Mobility Management Entity) 112 functions as a mobility management node of the mobile terminal (UE) in the LTE access network, and for example, tracking, paging, bearer activation, deactivation of the idle mode mobile terminal (UE) , Selection of SGW and PGW at the time of initial attachment, management of tunnel establishment between SGW and PGW, selection of SGW for mobile terminal (UE) at the time of handover within LTE, user authentication in cooperation with HSS, and the like.
- the MME is connected to a base station (eNB) via an S1-MME interface that applies an S1-AP (application) protocol for message exchange. Further, the MME 112 is connected to the SGW via the S11 interface.
- the PGW (PDN Gateway) of the S / P-GW 103 realizes connection of the mobile terminal (UE) to the external PDN.
- a mobile terminal (UE) can simultaneously have connectivity with two or more PGWs for accessing multiple PDNs.
- the PGW maps, for example, IP address assignment (payout), policy application, packet filtering (eg deep packet inspection, etc.) to the attached mobile terminal (UE) in order to map the traffic to an appropriate QoS (Quality of Service) level. Packet screening).
- QoS Quality of Service
- the PGW and the SGW are located in the same PLMN (PublicWLand Mobile ⁇ Network)
- the PGW is connected to the SGW via the S5 interface
- the SGW is located in the external (located) PLMN.
- PCRF Policy Charging Rules Function
- the PCRF 113 controls policies and charging rules.
- the PCRF 113 is connected to the PGW via the S7 interface.
- An HSS Home Subscriber Server
- AAA Authentication, Authorization and Accounting
- the AAA server in FIG. 3 may be the RADIUS server 108 in FIG. In the operation explanatory diagrams after FIG. 5, it is indicated as RADIUS.
- two sets of SGi1 and SGi2 are provided as interfaces SGi between the PGW and the PDN, and OFS1 and OFS2 are arranged corresponding to each. Further, OFC1 and OFC2 are respectively connected to OFS1 and OFS2, and control OFS1 and OFS2, respectively. OFS1 and OFS2 are connected to PDN 104 via router 109-1 and router 109-2, respectively.
- the server 104-1 of the PDN 104 may be a Web server or the like, or may be a test server or the like that tests connectivity of the OpenFlow-based traffic offload function and performs various settings.
- the paths connected to the eNBs 102-1 and 102-2 and the OFS1 and OFS2 via the layer 2 switches (L2SW) 111 and 111-2 (broken lines connected to the eNBs 102-1 and 102-2) (Shown by a one-dot chain line and two-dot chain line, respectively) represents an off-road route that bypasses the S / P-GW 103.
- the OFC 1 is connected to the PCRF 113 and notifies the offload-processed packet count and the like as charging information.
- the OFC 2 performs the same processing.
- VLAN Virtual LAN
- OFC-OFS-MBH Mobile Back Haul: connecting base station and core network
- eNB + TOF Mobile Back Haul: connecting base station and core network
- Fig. 3 May be divided into VLANs connected to the same SGi.
- a different IP address space is allocated for each VLAN.
- the base station has a plurality of IP addresses.
- IP addresses 192.168.0.10 and 192.168.4.10 are assigned to the eNB 102-1.
- the router 115 between the layer 2 switch (L2SW) 111 and the S / P-GW 103 may be deleted.
- the router 115 routes the base station group connected to the layer 2 switch (L2SW) 111 to another S / P-GW (not shown).
- the layer 2 switch (L2SW) 111-2 may be deleted.
- OFC1, OFS1, OFC2, and OFS2 have the same IP address.
- SGi1 and SGi2 are connected to OFS1 and OFS2, respectively. If there is no duplication of addresses, etc., a configuration may be adopted in which a plurality of PGWs are connected to one OFS.
- the layer 2 switches (L2SW) 111 and 111-2 may be formed of OFS.
- the connection state between the mobile terminal (UE) and the base station (eNB) includes RRC (Radio Resource Control) idle (RRC resource) and connection state (RRC connected).
- the connection state between the UE and the core network (MME) includes ECM (EPS (Evolved Packet System) Connection Management) idle (ECM Idle) and ECM connection state (ECM Connected).
- ECM EPS (Evolved Packet System) Connection Management) idle (ECM Idle)
- ECM connection state ECM connection state
- a private IP address is used as the UE address because of the exhaustion of IP addresses in IPv4.
- the same base station does not connect to EPCs having overlapping private address spaces (private addresses do not overlap).
- FIG. 4 is a diagram illustrating an operation procedure (sequence) at the time of registration processing (attach processing) of the UE (101 in FIG. 2) to the network.
- eNB corresponds to eNB 102a in FIG. 3
- eNB + TOF1 are base stations with offload function (eNB + TOF1) 102-1 in FIG. 3, base stations with offload function (eNB + TOF2) 102-2 respectively.
- the RADIUS corresponds to 108 in FIG. 2
- the router corresponds to 109 in FIG. 2 and 109-1 or 109-2 in FIG. The same applies to each of FIGS.
- a bearer establishment request (attach request) from the UE establishes a bearer between the UE and the S / P-GW (1).
- the UE transmits an attach request message to the MME.
- the MME performs user authentication based on the authentication information acquired from the HSS that registered the subscriber information, and selects and selects the SGW and PGW based on the APN (Access Point Point Name) notified by the UE in the attach request message.
- the bearer setting request is transmitted to the SGW and the PGW that have performed.
- the PGW issues an IP address and sets up a bearer between the SGW and the PGW.
- the SGW returns a bearer setup response to the MME.
- MME transmits a context setting request
- the UE sends an attach completion response to the MME.
- the eNB returns a context setting response to the MME.
- the MME sends a bearer update request to the SGW based on the context setting response, and the SGW returns a bearer update response to the MME.
- the OFC (106 in FIG. 2) functions as a relay node of the RADIUS server (108 in FIG. 2) that performs authentication. That is, OFS (105 in FIG. 2) hooks a request packet transferred from the access point (for example, PGW) which is a RADIUS client to the RADIUS server (2). At that time, the OFS (105 in FIG. 2) takes in the request packet transferred to the RADIUS server by filtering, for example.
- the request packet is originally a packet addressed to the RADIUS server, and the header information of the packet does not match the rule of the flow table of the OFS. It is transferred to the OFC using a secure channel as a “first packet” (3). The request packet is transferred again from the OFC via the OFS to the RADIUS server (4, 5).
- the flow table may be set to transfer the request packet from the OFS to the OFC (in this case, the secure channel is not used).
- the RADIUS request packet (UDP (User Datagram Protocol)) from the PGW as a RADIUS client to the RADIUS server includes, for example, a user name, an encrypted password, a client IP address, and a port ID.
- UDP User Datagram Protocol
- the RADIUS server receives the authentication request, it checks the user database that matches the login request. The RADIUS server performs a user connection request and authentication, and returns necessary setting information as a response.
- the response packet from the RADIUS server to the PGW is also hooked by OFC (6) and transferred to the OFC (106 in FIG. 2) (7).
- the OFC (106 in FIG. 2) performs packet inspection, and records the correspondence relationship between the terminal ID (IMSI (International Mobile Subscriber Identity)), IP address, and VLAN (Virtual Local Area Network) (8).
- IMSI International Mobile Subscriber Identity
- IP address IP address
- VLAN Virtual Local Area Network
- the response packet from the RADIUS server is transferred to the PGW via the OFC (106 in FIG. 2) and OFS (105 in FIG. 2) (9, 10). It is to be noted that spoofing and tampering are prevented between the RADIUS server and the RADIUS client (PGW) by a common key method. For this reason, the OFC holds key information common to the RADIUS server.
- the RADIUS server is arranged as an AAA server
- the PGW is connected to the RADIUS server through, for example, an S6c interface.
- the PGW issues an IP address and notifies the UE of the IP address (11).
- FIG. 5 is a diagram for explaining an operation (addition of an offload route) when the UE starts communication under the control of a base station with an offload function (eNB + TOF).
- eNB + TOF offload function
- UE starts communication under eNB + TOF1.
- eNB + TOF a QCI (QOS (Quality of Service) Class Indicator) to be offloaded is set in eNB + TOF1 and 2 in advance.
- the IP address (private IP address) addressed to the OFC is set to eNB + TOF1,2.
- VoLTE Voice Over LTE
- Voice bearer GRR (Guaranteed Bit Rate)
- QCI 1
- Video bearer GR
- QCI 2
- Video bearer non-GBR
- QCI 7
- ENB + TOF1 receives the packet from the UE (1).
- First IP packet from the QCI radio bearer to be offloaded eg DNS (Domain Name Service) Query packet (query to DNS server), TCP SYN packet (packet forwarded from client to server when TCP connection is established)
- ENB + TOF1 acquires the source IP address. Uplink packets may be sent via S1.
- connection request (Connection Request) to the OFC by UDP (User Datagram Protocol) (2).
- the connection request (Connection Request) includes, for example, an eNB + TOF1 address, TMSI (Temporary Mobile Subscriber Identity), the IP address of the UE, and a radio bearer identifier E-RABID (Radio Access Bearer ID) in E-UTRAN.
- E-RABID Radio Access Bearer ID
- the UE address is a private address.
- the connection request (Connection Request) is transferred directly from the eNB + TOF 1 to the OFS, and the transfer of the connection request (Connection Request) from the OFS to the OFC is transferred as “packet IN” using the secure channel.
- connection request (Connection Request) packet may be transferred to the OFC by setting a rule in the flow table from the OFC to the OFS (in this case, the OFS is not a “packet IN” for each event, but a flow To the OFC).
- the OFC performs a connection request (Connection Request) process with the eNB + TOF 1 (setup to the OFS flow table), and the OFC identifies the IMSI (International Mobile Subscriber Identity) from the IP address of the UE (3).
- connection request Connection Request
- TOF 1 setup to the OFS flow table
- the OFC sends a connection response (Connection ACK) to eNB + TOF1 (4).
- the connection response (Connection ACK) includes TMSI and UE IP address.
- the OFC sets a MAC rewrite entry in the OFS flow table for the destination address of the header of the packet for the downlink packet (DL).
- the OFC adds uplink and downlink counter entries to the flow entry in the OFS flow table (5). Billing information is collected for uplink and downlink packets that are offloaded.
- the UE transmits a data packet to eNB + TOF1 (6).
- the eNB + TOF 1 transfers the packet to the OFS (7).
- packets that are not to be offloaded are transferred to the SGW of the S / P-GW, and transferred from the PGW to the router via the OFS.
- the OFS transmits the transferred packet from the router (Router) to the PDN (8).
- the determination of offload may be performed based on the QCI of the packet.
- the packet received from the PDN via the router (Router) is transferred to the OFS (9), the packet for the UE is transferred from the OFS to the eNB + TOF1 (10), and wirelessly transmitted from the eNB + TOF1 to the UE. (11).
- FIG. 6 is a diagram illustrating a sequence applied to an area where a private address is overlapped with respect to addition of an offload route when the UE starts communication under eNB + TOF, as described with reference to FIG. It is.
- the base station leads to EPC having overlapping private address spaces.
- the private IP addresses of OFS and OPC connected to different SGi are duplicated.
- the eNB + TOF sends an indirect connection request (abbreviated as iCR) to the OFC, and identifies the offload path from the response transmitted from the OFC. It corresponds to “Return Routability” of Mobile IPv6 for confirming the reachability of HOA (Home Of Address) and COA (Care-Of-Address).
- the QCI to be offloaded is set in advance, and an IP address (private IP address) is set to the OFC.
- eNB + TOF1 receives the packet from the UE (1).
- the first IP packet for example, DNS Query packet or TCP SYN packet
- eNB + TOF1 acquires the source IP address.
- ENB + TOF1 sends an indirect connection request (iCR) addressed to OFC to SGW via S1-U by UDP (User Datagram Protocol) (2).
- the agent also operates in the same way in 3GPP / 2, WiMAX (Worldwide Interoperability for Microwave Access) PMIP (Proxy Mobile IP).
- the indirect connection request includes the source UE, the destination OFC, the base station address list (IP addresses assigned to eNB + TOF1: 192.168.0.10 and 192.168.4.10), TMSI, UE IP address, E -RABID is included.
- PGW outputs an indirect connection request (iCR) to SGi (SGi1 or SGi2) and transfers it to OFS (OFS1 or OFS2) (3).
- the OFS (OFS1 or OFS2) transfers the indirect connection request (iCR) from the PGW to the OFC (OFC1 or OFC2) (4).
- the OFC that has received the indirect connection request performs connection request processing, SGi identification, and IMSI identification from the IP address of the UE (5).
- the OFC sends a connection response (Connect ACK) to the base station eNB + TOF1 (6).
- the base station eNB + TOF1 specifies the VLAN connected to the transmission source (OFC1 or OFC2) of the connection response from the received connection response (Connect ACK).
- the base station eNB + TOF1 sends the offload target packet to the VLAN.
- OFC set up OFS flow entry.
- a MAC address rewrite entry an action for correcting the MAC address when matching the rule for rewriting the destination address of the packet header is set in the OFS flow table. Further, a counter entry is added to the OFS flow table for the uplink (7).
- UE transmits data packet to base station eNB + TOF1 (8).
- eNB + TOF1 when a packet from the UE is a packet from a QCI radio bearer to be offloaded, the packet is transferred to a traffic offload destination route (9).
- eNB + TOF1 a packet that is not an offload target is transferred to the SGW of the S / P-GW, and the packet is transferred from the PGW to the router via the OFS.
- the OFS transmits the packet transferred via the offload route from the router to the PDN (10).
- offload determination may be performed based on, for example, the QCI of a packet.
- the packet received from the PDN via the router (Router) is transferred to the OFS (11), and the packet for the UE is transferred from the OFS to the base station eNB + TOF1 (12), from the base station eNB + TOF1. It is wirelessly transmitted to the UE (13).
- FIG. 7 is a diagram illustrating an example of an operation in the case of an offload path addition error.
- FIG. 7 illustrates a procedure when there is no OFS / OFC connected to SGi.
- the base station eNB + TOF 1 with an offload function sends an indirect connection request to the OFC, and a response transmitted from the OFC is applied to an area where private addresses overlap. From this, it is assumed that an offload route is specified.
- (1) and (2) are the same as (1) and (2) in FIG.
- the PGW outputs an indirect connection request (iCR) from the base station eNB + TOF1 with an offload function to SGi.
- eNB + TOF1 retransmits the indirect connection request (iCR), but the acknowledgment (Ack) is not returned from the OFC.
- the indirect connection request (iCR) is retransmitted a predetermined number of times from eNB + TOF1
- an acknowledgment (Ack) is not returned from the OFC, a retransmission over (retransmission timeout error) occurs, and the offload route addition processing is finish.
- the packet from the UE is transferred from the S / P-GW to the SGi and the PDN via the router via the S1-U (5-7).
- the packet received from the PDN via the router is transferred to the S / P-GW (8), transferred from the S / P-GW to eNB + TOF1 (9), and transmitted wirelessly from eNB + TOF1 to the UE. (10).
- ⁇ HO from eNB without offload function to eNB + TOF with offload function> A case where the UE performs handover (X2 handover) from an eNB area having no traffic offload function to an eNB area having a traffic offload function will be described with reference to FIG.
- the source and destination eNBs connected to the same MME perform handover using the connection interface X2 between the eNBs.
- the eNB that has received the measurement result of the neighboring base station from the UE determines handover (HO).
- the eNB transmits a handover (HO) request to the destination eNB + TOF1.
- the source eNB transmits a handover (HO) instruction to the UE by radio.
- the source eNB transmits undelivered packets and terminal information to the destination eNB + TOF1 on X2 (1). In this case, it is assumed that the packet has arrived via the X2 addressed to the off-load target QCI radio bearer.
- the destination eNB + TOF1 forwards the packet to the UE (2).
- the destination eNB + TOF1 sends an indirect connection request (iCR) addressed to the OFC to the S / P-GW via the S1-U interface using UDP (User Datagram Protocol) (3) .
- the indirect connection request (iCR) includes, for example, a transmission source UE, a destination OFC, a base station address list, TMSI, a UE IP address, and an E-RABID.
- S / P-GW outputs an indirect connection request (iCR) to SGi and transfers it to OFS (4).
- the OFS transfers the indirect connection request (iCR) from the S / P-GW to the OFC (5).
- the OFC receives the indirect connection request (iCR) and specifies the IMSI from the offload route connection processing, the SGi specification, and the IP address of the UE (6).
- the OFC sends a connection response (Connect ACK) including the UE IP address and TMSI information to the base station eNB + TOF1 directly from the offload route by TCP (Transmission Control Protocol) (7).
- the base station eNB + TOF1 recognizes the offload destination from the connection response (Connect ACK), and sends the offload target packet to the offload destination VLAN.
- the OFC sets up the OFS flow entry.
- a MAC address rewrite entry (action) for rewriting the destination MAC address in the header of the packet is set in the OFS flow table.
- a counter entry is added to the OFS flow table for uplink (8).
- the OFC may transmit an END Marker indicating the end of the transfer data to the eNB + TOF 1 (9).
- uplink data packets from the UE are offloaded at the base station eNB + TOF1, bypass the core network, forward to the OFS, and forward from the router to the PDN .
- Offload route update> A case where the UE performs handover between base stations having a traffic offload function (X2 handover) will be described with reference to FIG. It is assumed that private addresses overlap between OFS and OFC connected to different SGi.
- the source eNB + TOF 1 transmits a disconnection request (Disconnect Request: DR) to the OFC via the OFS by TCP (transmission control protocol) (1).
- the disconnection request (DR) includes UE information.
- the OFC reserves the processing of the disconnect request (ie, does not immediately disconnect the source eNB + TOF1 immediately, associates it with the UE entry, starts a timer, and performs the disconnect processing after T milliseconds. (2).
- a disconnection request is registered in a command buffer (queue) or the like to be in a waiting state, and when a timeout occurs, the disconnection process is performed by taking out from the command buffer.
- the source eNB + TOF1 transmits a user data packet to the destination eNB + TOF2 via the connection interface X2 between eNBs to the off-load target QCI radio bearer (3).
- the source eNB + TOF 1 transmits a handover (HO) instruction to the UE by radio.
- HO handover
- the destination base station eNB + TOF2 forwards the user data packet to the UE (4).
- the destination eNB + TOF2 sends an indirect connection request (iCR) addressed to the OFC via UDP to the S / P-GW via the S1 interface (5).
- the indirect connection request (iCR) includes a source UE, a destination OFC, a base station address list, a TMSI, a UE IP address, and an E-RABID.
- the S / P-GW outputs an indirect connection request (iCR) to SGi and transfers it to OFS (OFS1 or OFS2) (6).
- the OFS (OFS1 or OFS2) transfers the indirect connection request (iCR) from the PGW to the OFC (OFC1 or OFC2) (7).
- the OFC (OFC1 or OFC2) specifies the IMSI from the connection request processing, the SGi specification, and the UE IP address. Since the disconnection request from eNB + TOF1 remains in the UE entry, the OFC determines that the handover is between eNB + TOF.
- the OFC sends a connection response (Connect Ack) to the destination eNB + TOF2 by TCP (9).
- the destination eNB + TOF 2 receives the connection response (Connect Ack) and specifies the offload path (VLAN).
- the OFC sets up the OFS flow entry.
- a MAC rewrite entry for rewriting the destination MAC address in the header of the packet is set in the OFS flow table.
- the OFC adds an uplink counter entry to the OFS flow table, and further cancels the disconnection process reservation (10). Thereafter, offloading (PGW offloading) at the destination eNB + TOF2 is started.
- the uplink data packet from the UE is offloaded by the destination eNB + TOF2, transferred to the OFS, and transmitted to the PDN.
- the downlink packet from the PDN is transferred from the OFS to the destination eNB + TOF 2 (11-16).
- the OFC returns a disconnection response (Disconnect Ack) to the source eNB + TOF 1 using TCP (17).
- the offload in the source eNB + TOF1 is completed, the packet from the UE is transferred to the OFS via the S / P-GW, and the packet is transferred from the router to the PDN 104. To the UE via the eNB.
- ⁇ HO1 Offload path deletion from base station with offload function to base station without offload function>
- a handover when a UE that is offloading and communicating with a base station eNB + TOF1 with an offload function moves into the area of the base station eNB without the offload function will be described with reference to FIG.
- the source eNB + TOF 1 transmits a disconnection request (Disconnect Request: DR) to the OFC via the OFS (1).
- This disconnection request (DR) includes UE information.
- the OFC reserves the disconnection process (starts the timer in association with the UE entry and reserves the disconnection process after T milliseconds) (2).
- the source eNB + TOF1 transmits a user data packet to the destination eNB via the connection interface X2 between the eNBs (3), and the destination base station eNB sends the user data packet to the UE. (4).
- the OFC processes the disconnection request after a timer timeout occurs (T milliseconds have elapsed).
- the packet count is collected from the statistical information of the OFS flow table (5, 6), and the OFS is instructed to delete the downlink and uplink flow entries in the flow table (7).
- the OFC sends a disconnection completion response (Disconnect Ack: DA) to the source eNB + TOF 1 by TCP (8).
- the packet When a packet is input from the PDN to the OFS via the router (9), the packet is transferred from the OFS to the PGW and SGW (10), transferred from the SGW to the destination eNB (11), and wirelessly transmitted to the UE. (12). Packets from the UE are transferred from the eNB to the OFS via the S / P-GW and transmitted from the router to the PDN (13 to 16).
- the source eNB + TOF1 transmits a disconnection request (Disconnect Request: DR) to the OFC via TCP (2).
- the disconnection request (DR) includes UE information.
- the OFC reserves the processing of the disconnection request (starts the timer in association with the UE entry and reserves the disconnection processing after T milliseconds (T is a predetermined value)) (3).
- the disconnection request is processed (4).
- the packet count is collected from the statistical information of the OFS flow table (5), and the OFS is instructed to delete the downlink and uplink entries of the flow table (6).
- the OFC sends a disconnection response (Disconnect1Ack) to the source eNB + TOF1 via TCP (7).
- the eNB + TOF1 of the movement source transmits a disconnection request (Disconnect Request: DR) to the OFC via the OFS (1) .
- the disconnection request (DR) includes UE information.
- the OFC reserves the processing of the disconnection request (starts the timer in association with the UE entry and reserves the disconnection processing after T milliseconds) (2).
- the packet is transmitted from the source eNB + TOF1 to the destination eNB via the connection interface X2 between the eNBs (3), and the packet is wirelessly transmitted from the destination eNB to the UE (4).
- the transmission packet from the UE is transferred via the eNB and S / P-GW, and transferred from the OFS to the router (5 to 8).
- the OFC processes the disconnection request after a timeout of T milliseconds.
- the packet count is collected from the statistical information of the OFS flow table (9, 10), and the OFS is instructed to delete the flow table downlink and uplink flow entries (11).
- the OFC notifies the source eNB + TOF1 of a disconnection response (DisconnectTOAck) via TCP and ends offload (12).
- the packet When a packet is input from the PDN to the OFS via the router (13), the packet is transferred from the OFS to the PGW and SGW (14), transferred from the SGW to the destination eNB (15), and wirelessly transmitted to the UE. (16).
- a packet from the UE is transferred from the eNB to the OFS via the S / P-GW and transmitted from the router to the PDN (17 to 20).
- CSFB Circuit Switched Call control
- the CS network moves from the LTE network to the 3G (2G) network and performs CS communication.
- the UE hands over from EUTRAN to UTRAN.
- a signal indicating that there is an incoming call is sent from the source G-MSC (Kanmon mobile switching center) to the MSC / VLR via the CS network, and an incoming call is received at the MSC (Mobile Switching Center) / VLR (Visited Location Register).
- G-MSC Kernmon mobile switching center
- MSC Mobile Switching Center
- VLR Vehicle Location Register
- the corresponding MME is specified from the information, and a general call signal (Paging-Request-message) is transmitted to the MME.
- the MME transmits a general call signal to the eNB.
- This paging signal includes information indicating that the CS service is called.
- the UE recognizes this information (CS service call) and transmits a CS service request signal to the MME.
- the MME transmits a handover command (HO Command).
- the UE executes the handover procedure and switches to 3G.
- SRVCC also performs a voice call by handing over from LTE to 3G (2G) area.
- the source eNB + TOF1 transmits a disconnection request (DR) to the OFC via TCP via the OFS (2).
- the disconnection request includes UE information.
- eNB + TOF1 releases the S1 connection with the MME.
- the OFC reserves the processing of the disconnection request (starts the timer in association with the UE entry and reserves the disconnection processing after T milliseconds) (3).
- the disconnect request is processed.
- the packet count is collected from the statistical information of the OFS flow table (4, 5), and the OFS is instructed to delete the downlink and uplink entries of the flow table (6).
- the OFC notifies the eNB + TOF1 of a disconnection response (Disconnect Ack) by TCP (7).
- the offload path is disconnected, and the UE communicates with the 3G (2G) network.
- FIG. 14 is a diagram illustrating offload path deletion at the transition to ECM-IDLE.
- Figure 5.3.5-1 S1 Release Procedure for the S1 release procedure.
- the MME sends a Release Access Bearer Request (Release Access Bearers Request) to the SGW to release the S1-U bearer.
- the SS1-AP eNBS1 UE Context Release Request is transmitted from the eNB to the MME.
- the SGW deletes the eNB related information (address, tunnel identifier (Tunnel Endpoint ID: TEID)) and transmits a release access bearer response (Release Access Bearers Response) to the MME.
- the MME transmits an S1-AP S1 UE context release command message (S1 UE Context Release Command (cause)) to the base station eNB + TOF1 and releases S1 (1).
- the base station eNB + TOF1 confirms S1 Release and transmits S1 UE Context Release Complete message to the MME. If the RRC connection (RRC (Connection) is not released, eNB + TOF1 transmits an RRC Connection Release message to the UE.
- RRC Remote Control
- eNB + TOF1 transmits an RRC Connection Release message to the UE.
- the source eNB + TOF1 sends a disconnection request (DR) to the OFC via TCP via the OFS (2).
- the disconnection request (DR) includes UE information.
- eNB + TOF1 releases the S1 connection with the MME.
- the OFC reserves the processing of the disconnection request (starts the timer in association with the UE entry and reserves the disconnection processing after T milliseconds) (3).
- the disconnect request is processed.
- the packet count is collected from the statistical information of the OFS flow table (4, 5), and the OFS is instructed to delete the downlink and uplink entries of the flow table (6).
- the OFC notifies the disconnection response (Disconnect Ack) to the source eNB + TOF1 by TCP (7). In this way, the offload path is disconnected at the transition from the ECM connected state (ECMECConnected) to the ECM idle (ECM Idle).
- ECMECConnected ECM connected state
- ECM idle ECM idle
- paging and ISR Idle (signaling Reduction) to the UE in the ECM idle state are processed by the MME or SGSN.
- ISR is a 3G / LTE location registration omission function. Even if the radio access system is changed, location registration is performed as long as there is no change from the previously registered location registration area (UE, MME, or SGSN has the same PDN connection state). This function is omitted.
- FIG. 15 is a diagram for explaining the second embodiment.
- the above OpenFlow movement control is applied to the 3GPP SIPTO solution 4 described with reference to FIG. 17 to overcome the point where mobility cannot be realized.
- NAT is required, but according to the embodiment using OpenFlow, NAT is not required.
- a TOF (Traffic Offload) 124 arranged in the Iu-PS interface receives traffic (packets) from the UE 121 to the radio access network UTRAN (NB 122, RNC 123), and sends offload target packets to an offload route.
- the data is transferred to the OFS 105 via 127.
- the TOF 124 forwards non-offload (not offload target) packets to the SGSN 125.
- SGSN 125 and SGW 103S are connected by an S4 interface.
- the eNB 102, OFS 105, OFC 106, router 109, and PDN 104 are the same as those described with reference to FIG. In FIG.
- the SGW 103S and the PGW 103P are separately arranged, but may be integrated as shown in FIG.
- a GGSN (not shown) is connected to the SGSN 125, an OFS (not shown) is arranged at the interface Gi between the GGSN and the PDN, and traffic (packets) from the UE 121 to the radio access network UTRAN (NB 122, RNC 123) ) May be offloaded by the TOF 124, transferred to the OFS (not shown) ahead of the GGSN (not shown), and transmitted to the PDN.
- NB 122, RNC 123 radio access network UTRAN
- the packet offloaded by the TOF 124 may be transferred to the OFS 105 via the virtual switch (VSW) (in addition to the physical network interface in the management domain, the virtual switch (VSW) is incorporated as a network device). Can configure IP routing).
- the virtual switch (VSW) is configured by, for example, OFS, and the OFS is controlled by an OFC indicated by a broken line (an OFC different from 106 may be used). Good.
- the addition of SGSN, SGW, PGW and the like due to traffic increase is suppressed.
- FIG. 16 is a diagram for explaining the third embodiment.
- a traffic offload (TOF) function is added to the femto gateway 133.
- the data traffic (packet) to be offloaded is transferred to the OFS 105 via the offload path 137 that bypasses the core network, and transferred from the router 109 to the PDN 104. Further, the data traffic transferred from the PDN 104 to the OFS 105 via the router 109 bypasses the core network and is transferred to the femto gateway 133, and the femto cell base station (femto cell access point) (FAP) via the network 132. 131.
- FAP femto cell access point
- an MSC Mobile Switching Center
- a CS Circuit Switched core
- BSC Base Station Controller
- CSCF Circuit Switched Control Function
- IMS Internet Multimedia Services
- HLR Home Location Registry
- HSS is a subscriber information database. According to this embodiment, the addition of SGSN, SGW, PGW, etc. due to the increase in femtocell traffic is suppressed.
- the base station eNB includes user plane header compression and encryption functions. It hosts physical (PHY), media access control (MAC), radio link control (RLC), and packet data control protocol (PDCP) layers.
- the eNB provides a radio resource control (RRC) function corresponding to the control plane. Further, the eNB performs radio resource management, admission control, scheduling, negotiated UL-QoS (Uplink Quality of Service), cell information broadcast, user and control plane data encryption and decryption, DL / UL (Downlink / Uplink) Performs functions such as compression and decompression of user plane packet headers.
- the eNBs are also connected to the SGW, respectively, on the S1-U interface.
- FIG. 17 schematically shows an example of the configuration of the base station (eNB + TOF) 102 to which a traffic offload (TOF) function is added.
- FIG. 17 schematically illustrates the base station (eNB + TOF) 102, and of course, the functional configuration, block configuration, signal connection, and the like are not limited to such a configuration.
- the offload traffic determination unit 1022 determines that the packet from the radio bearer (packet transmitted from the UE) received by the radio reception unit 1020 based on the off-load target QCI is offloaded. It is determined whether it is a target.
- the connection request transmission / connection response reception unit 1023 sends an indirect connection request (Indirect Connect Request) from the S1-U interface 1031 to OFS. Send.
- the connection request transmission / connection response reception unit 1023 transmits a connection request (Connect Request) from the VLAN interface 1032 to the OFS.
- the connection request transmission / connection response reception unit 1023 transmits an indirect connection request (indirect Connect Request) from the S1-U interface 1031 to the OFS.
- connection request transmission / connection response reception unit 1023 transmits a connection request (Connect Request) from the VLAN interface 1032 to the OFS.
- the connection request transmission / connection response reception unit 1023 receives a connection response from the OFC from the VLAN interface 1032.
- the disconnection request transmission / disconnection response receiving unit 1024 transmits a disconnection request (indirect disconnection request) from the VLAN interface 1032 to the OFC.
- the disconnection request transmission / disconnection response receiving unit 1024 sends a disconnection request under the control of the handover processing unit 1026 or by an instruction (control signal) from the disconnection control unit 1027 at the time of transition to ECM-IDLE.
- the data is transmitted from the VLAN interface 1032 to the OFC.
- the disconnection request transmission / disconnection response receiving unit 1024 receives a disconnection response from the OFC from the VLAN interface 1032.
- the packet (uplink packet) received from the UE by the radio reception unit 1020 is transmitted / received as the offload target uplink traffic. Is transferred from the unit 1028 to the offload traffic transmitting / receiving unit 1025.
- the offload traffic transmission / reception unit 1025 transfers the uplink traffic to be offloaded from the VLAN interface 1032 to the OFS. Further, the offload traffic transmission / reception unit 1025 outputs the downlink traffic to be offloaded received from the VLAN interface 1032 to the radio transmission unit 1021 and transmits the radio traffic from the radio transmission unit 1021 to the UE.
- a packet (uplink packet) received from the UE received by the radio reception unit 1020 is transmitted from the traffic transmission / reception unit 1028 to the S1-U interface 1031. Is output and sent to the PDN via the S / P-GW, OFS, and router. Further, the downlink packet received from the S1-U interface 1031 is output from the traffic transmission / reception unit 1028 to the radio transmission unit 1021 and transmitted to the UE by radio.
- the wireless transmission unit 1021 and the wireless reception unit 1020 are illustrated as separate blocks for the convenience of drawing, but are configured integrally.
- the radio reception unit 1020 and the radio transmission unit 1021 include a transmission / reception antenna, a TX (transmission unit), an RF (Radio Frequency) unit such as an RX (reception unit), a modulation / demodulation unit, a baseband processing unit, a communication controller, a transmission / reception buffer, and the like.
- . 18 is responsible for the OFC sequence operation described with reference to FIGS. 4 to 14. In FIG.
- the processing of the disconnection control unit 1027 may be realized by part or all of the processing / function by a program executed on a computer constituting the base station.
- the program is provided by being stored in a medium (not shown) such as a semiconductor memory, a magnetic disk, or an optical disk.
- FIG. 18 is a diagram schematically illustrating a configuration example of the OFC 106 according to the embodiment.
- a packet transmission / reception unit 1061 that transmits and receives a packet from the OFS
- a route calculation unit 1062 that calculates a flow for transferring the packet
- the flow table setting unit 1063 for setting the follows the configuration of the existing OFC.
- the OFC 106 of the embodiment further includes an offload control unit 1069 in addition to the existing OFC configuration.
- the offload control unit 1069 A terminal information acquisition unit 1064 that acquires UE terminal information from a packet transferred from the OFS that hooks a handshake with the authentication server in the process of attaching the base station with an offload function to the network; A connection request processing unit that processes a connection request (Connect Request) or an indirect connection request (Indirect Connect Request) from a base station with an offload function, adds an offload route, and returns a connection response to the base station with an offload function 1065, A disconnect request processing unit 1066 that processes a disconnect request (Disconnect Request) transferred from a base station with an offload function, deletes an offload route, and returns a delete response to the base station with an offload function; Control connection processing (addition of offload route) in the connection request processing unit 1065, addition / deletion of an OFS flow table entry, route change, etc.
- the timer 1068 is a timer that counts a wait time (T milliseconds) from when the disconnection request processing unit 1066 receives the disconnection request until execution of the disconnection process, and notifies a timeout when T milliseconds have elapsed.
- the offload control unit 1069 is responsible for the OFC sequence operation described with reference to FIGS. 4 to 14. In the OFC, at least each part of the offload control unit 1069 may realize part or all of the processing / function with a program executed on a computer constituting the OFC.
- the program is provided by being stored in a medium (not shown) such as a semiconductor memory, a magnetic disk, or an optical disk.
- the offload determination function is implemented in the OFC.
- an offload determination unit or the like may be implemented in the MME, SGSN, or the like.
- an offload function for offloading received packets may be implemented in a base station (Embodiment 1), a TOF arranged in an Iu-PS interface, a SIPTO gate bay (SIPTO-GW), or the like.
- FIG. 21 is a diagram for explaining an embodiment corresponding to the embodiment of FIG. 21, the same elements as those in FIG. 1 are denoted by the same reference numerals.
- the difference from the embodiment of FIG. 1 is provided with a base station with an offload function (eNB + TOF) 102S and a switch 111S for switching to an offload path.
- the switch 111S may be an open flow switch (OFS), a virtual switch (VSW), or the layer 2 switch of FIG.
- OFS open flow switch
- VSW virtual switch
- the path setting of the switch 111S is controlled from the OFC 106A. That is, it is controlled by setting / deleting an entry in the OFS flow table from the OFC 106A.
- the switch 111S may be incorporated in the base station with offload function (eNB + TOF) 102S.
- the base station with an offload function (eNB + TOF) 102S has an offload path setting function.
- the base station with an offload function (eNB + TOF) 102S determines whether the received buffer is an offload target, and transfers the offload target packet to the offload path.
- the offload route connection request (Connect Request) to the OFC 106A from the base station (eNB + TOF) 102S with the offload function (Send Request), the reception of the response, the disconnection request (Disconnect Request), the reception of the response, etc. Basically, for example, the sequence described with reference to FIGS. 4 to 14 is followed.
- an indirect connection request (indirect Connect Request ).
- an offload instruction is received from the OFC 106A, the received packet from the radio bearer to be offloaded is transferred to the offload path 107, so that control and configuration can be simplified. Become.
- the offload control function (offload determination unit) performed by the OFC 106A may be incorporated in the base station (eNB + TOF) 102S with an offload function.
- the OFC that controls the OFS 105 and the OFC that controls the base station with the offload function (eNB + TOF) 102S may be configured separately.
- a node having the function of offloading traffic to the first network A switch disposed between a gateway node of the first network and a second network; With When traffic is offloaded, the switch connects the node to the second network via the first network detouring offload path, The network system in which the node connects to the first network and the switch connects the gateway node of the first network to the second network during non-offload.
- Appendix 2 The network system according to appendix 1, comprising a control device for controlling the switch.
- Appendix 3 The network system according to appendix 2, wherein the node having the traffic offload function is a base station of a radio access network.
- the node determines that a packet arriving from a mobile terminal via a radio bearer corresponds to an offload target, the node transmits an offload path connection request to the control device via the switch, The control device receives the connection request from the node, transfers a packet transferred from the node to the second network, and transfers a packet from the second network to the node.
- the network system according to claim 3, wherein the network system is set to the switch and a connection response is returned to the node.
- Appendix 5 The network system according to appendix 4, wherein the control device acquires information of the mobile terminal based on information transmitted and received between the gateway gate and an authentication server at the time of authentication accompanying attachment from the mobile terminal.
- a plurality of sets of at least one switch and the control device are provided between the gateway gate and the second network, With respect to the interface between the gateway gate and the second network, if the first address and the second set of switches connected to the first and second interfaces overlap with the private address of the control device, the node The connection request is transmitted from the gateway gate via the first network to the control device via the first or second set of switches,
- Appendix 10 The network system according to appendix 8 or 9, wherein when the control device receives an offload path disconnection request from the base station, the control device performs a disconnection process after a predetermined time delay by a timer.
- the base station When the base station receives a predetermined command from a node that manages mobility of a mobile terminal, the base station transmits a disconnection request for deleting an offload path to the control device via the switch, and the source base station A disconnect request for deleting an offload route is transmitted to the control device via the switch,
- Appendix 14 The network system according to appendix 1 or 2, wherein the node having a traffic offload function is arranged on an interface between a radio link controller and the first network.
- Appendix 15 The network system according to appendix 1 or 2, wherein the node having the traffic offload function is a femto gateway that connects a femtocell and the first network.
- a node for offloading traffic to the first network When offloading traffic using a switch disposed between the gateway node of the first network and a second network, The switch connects the node to the second network via an offload path for bypassing the first network; The network control method, wherein the node connects to the first network and the switch connects the gateway node of the first network to the second network during non-offload.
- a connection request for an offload route that bypasses the first network is transmitted directly or via the first network.
- the mobile terminal Upon receiving a predetermined command from a node that manages mobility of the mobile terminal, the mobile terminal comprises means for transmitting an offload path disconnection request to the switch, and the disconnection request is transmitted from the switch to the control device, and A base station device whose off-road route is disconnected.
- Appendix 18 Means for transmitting an offload path connection request to the switch directly or via the first network when the destination base station apparatus in the handover of the mobile terminal is a base station having an offload function;
- a control device for controlling a switch disposed between a gateway node of a first network and a second network When the switch receives a connection request for an offload route that bypasses the first network from the base station device, the packet forwarded from the base station device to the offload route is forwarded to the second network. And setting the switch to transfer a packet from the second network to the node via the offload path, and returning a connection response to the base station device; Upon receiving the switch from the base station apparatus, the switch is set so that the gateway node of the first network is connected to the second network, and the disconnection response is received. Means for returning to the base station apparatus.
Abstract
Description
本発明は、日本国特許出願:特願2012-252426号(2012年11月16日出願)に基づくものであり、同出願の全記載内容は引用をもって本書に組み込み記載されているものとする。
本発明は、ネットワークシステムと方法と装置並びにプログラムに関する。
前記第1のネットワークへのトラフィックのオフロードの有無を判定し、オフロードする場合、前記第1のネットワークを迂回するオフロード用の経路の設定を、前記スイッチ手段に対して行うオフロード判定手段と、
を備え、
前記第1のネットワークへのトラフィックのオフロード時に、オフロード対象のパケットは、前記オフロード用の経路と前記第2のネットワーク間を、前記スイッチ手段を介して転送される、システムが提供される。
前記第1のネットワークへのトラフィックのオフロードの指示を前記オフロード手段に対して行うオフロード判定手段と、
を備え、
前記オフロード手段は、前記オフロードの指示を受け、受信パケットに対してオフロードの有無を判断し、オフロード時には、前記パケットを、前記第1のネットワークを迂回するオフロード用の経路を転送する、システムが提供される。
受信パケットに対してオフロードの有無を判断し、オフロード対象のパケットを、前記コアネットワークを迂回するオフロード用の経路に転送する基地局装置が提供される。
移動端末から無線ベアラを介して到着したパケットがオフロード対象に該当すると判断した場合、第1のネットワークを迂回するオフロード経路の接続要求を、直接又は第1のネットワークを経由して、前記第1のネットワークと第2のネットワーク間に配設されたスイッチに送信する処理と、
前記移動端末のモビリティを管理するノードから所定のコマンドを受けると、前記オフロード経路の切断要求を、前記スイッチに送信する処理と、を実行させるプログラムが提供される。本発明によれば、該プログラムを記録したコンピュータ読み出し可能な記録媒体(半導体メモリ、磁気ディスク/光ディスク)が提供される。
基地局装置から、前記第1のネットワークを迂回するオフロード経路の接続要求を、前記スイッチを介して受け取ると、前記基地局装置から前記オフロード経路に転送されたパケットを前記第2のネットワーク向けに転送し、且つ、前記第2のネットワークからのパケットを前記オフロード経路を介して前記ノードに転送するように、前記スイッチに設定し、前記オフロード経路の接続要求に対する接続応答を前記基地局装置に返す処理と、
前記基地局装置から、前記オフロード経路の切断要求を、前記スイッチを介して受け取ると、前記第1のネットワークの前記関門ノードを前記第2のネットワークに接続するように前記スイッチに設定し、前記オフロード経路の切断要求に対する切断応答を前記基地局装置に返す処理と、を実行させるプログラムが提供される。本発明によれば、該プログラムを記録したコンピュータ読み出し可能な記録媒体(半導体メモリ、磁気ディスク/光ディスク)が提供される。
本発明の一実施形態について図1を参照して説明する。なお、図1は、図20(A)を参照して説明した形態に対応し、第1、第2のネットワークを、それぞれ、コアネットワーク、PDN(Packet Data Network)としている。この実施形態によれば、PDN(Packet Data Network)104とPGW間の参照ポイント(RP: Reference Point)であるSGi(2G/3G(第2/3世代)ではPDNとGGSN間の参照ポイントであるGi)に対応させてスイッチ(OFS)105を配置し、トラフィックオフロード(TOF)時には、移動端末101からのアップリンクデータトラフィックは、無線アクセスネットワーク(RAN:Radio Access Network)のトラフィックオフロードノードでオフロードされ、コアネットワーク(CN:例えばLTE/EPC(Long Term Evolution/Evolved Packet Core)ネットワーク)を迂回して、スイッチ105を介して、PDN104に転送される。無線アクセスネットワーク(RAN)のトラフィックオフロードノードは、例えばE-UTRAN(Evolved Universal Terrestrial Random Access Network)の場合、TOF機能付eNB(evolved Node B)(図1の103)、UTRAN(Universal Terrestrial Random Access Network)の場合、例えば、前述したIu-PS上のTOF(図15の124))である。PDN104からのダウンリンクトラフィックは、該スイッチ105から、コアネットワーク(CN)を迂回して、無線アクセスネットワーク(RAN)のトラフィックオフロードノードに転送され、移動端末101に無線送信される。なお、非オフロード時には、移動端末101からのアップリンクデータトラフィックは、無線アクセスネットワーク(RAN)、コアネットワーク(CN)、該スイッチ105を介してPDN104に転送される。またPDN104からのダウンリンクトラフィックは該スイッチ105からコアネットワーク(CN)、無線アクセスネットワーク(RAN)を介して移動端末101に送信される。
以下では、オープンフロー(Open Flow)について概説しておく。OpenFlowは、OpenFlowスイッチコンソーシアムが提唱した、ネットワーク制御技術のことであり、物理ポート番号(L1)、MAC(Media Access Control)アドレス(L2)やIPアドレス(L3)、ポート番号(L4)などの識別子の組み合わせによって決定される一連の通信を「フロー」として定義し、フロー単位での経路制御を実現する。転送ノードとして機能するオープンフロースイッチ(OpenFlow Switch:OFSと略記される)は、オープンフローコントローラ(OpenFlow Controller:OFCと略記される)から追加又は書き換えを指示されるフローテーブルに従って動作する。フローテーブルには、フロー毎に、ルール(パケットのヘッダ情報と照合されるフィルタリング条件)、統計情報(カウンタとして指定できる。パケット数、バイト数、フローがアクティブな期間等のフロー統計情報を含む)、ルールにマッチしたパケットに対して適用する処理を規定したアクション(フロー処理、パケット転送(Forward)、廃棄(Drop)、パケットの特定のフィールドを書き換える(Modify-Field)の修正等)を含む。パケット転送(Forward)には、例えば
・スイッチの特定のポートへの転送、
・スイッチの全てのポートへの転送、
・OFCに転送等
が選択される。
L2:Ether src(送信元MACアドレス)、Ether dst(宛先MACアドレス)、Etherタイプ、VLAN(Virtual Local Area Network)-id、VLANプライオリティ;
L3:IP src(送信元IPアドレス)、IP dst(宛先IPアドレス)、IPプロトコル種別、TOS(Type Of Service)値;
L4:TCP(Transmission Control Protocol)/UDP(User Datagram Protocol) src port(送信元L4ポート番号)、TCP/UDP dst port(宛先L4ポート番号)
無線アクセスネットワーク(RAN)をE-UTRAN、
コアネットワーク(CN)をEPC/LTEネットワーク、
とした場合の適用例を説明する。図3は、図1、図2の構成の一例を例示した図である。図3において、図1、図2と同一の要素には同一の参照符号が付されている。以下、各要素を概説しておく。eNB102aは、S1-UインタフェースによりSGWに接続され、S1-MMEインタフェースによりMMEに接続される。
図5は、UEが、オフロード機能付き基地局(eNB+TOF)の配下で通信を開始した場合の動作(オフロード経路の追加)を説明する図である。なお、前提として、異なるSGiに接続するOFS(OFC)のプライベートアドレスは重複しないものとする(例えば同一の基地局が、重複するプライベートアドレス空間を持つEPCには繋がらない場合である)。
音声ベアラ(GBR(Guaranteed Bit Rate)):QCI=1、
ビデオベアラ(GBR):QCI=2、
ビデオベアラ(非GBR):QCI=7、
VoLTEの制御信号であるSIP(Session Initiation Protocol)信号用デフォルトベアラ:CQI=5、
Internet Connectivity: QCI=8、又は9.
例えばQCI=8、9の無線ベアラは、eNB+TOFでオフロード判定対象とされる。
図6は、図5を参照して説明した、UEが、eNB+TOF配下で通信を開始した場合のオフロード経路の追加について、プライベートアドレスが重複している地域に適用されるシーケンスを示す図である。この場合、基地局が重複するプライベートアドレス空間を持つEPCにつながる。例えば、異なるSGiに接続するOFS、OPCのプライベートIPアドレスが重複する。この場合、eNB+TOFは、間接接続要求(indirect Connect Request)(iCRとの略記される)をOFCに送り、OFCから送信される応答からオフロード経路を特定する。HOA(Home Of Address)とCOA(Care-Of-Address)の到達可能性を確認するMobile IPv6の「Return Routability」に対応する。
図7は、オフロード経路の追加エラーとなる場合の動作の一例を例示する図である。図7では、SGiに接続されたOFS/OFCが存在しない場合の手順が例示されている。この場合も、図6と同様、例えばプライベートアドレスが重複する地域に適用され、オフロード機能付き基地局eNB+TOF1は、間接接続要求(indirect Connect Request)をOFCに送り、OFCから送信される応答から、オフロード経路を特定するものとする。
UEがトラフィックオフロード機能を備えていないeNBのエリアからトラフィックオフロード機能を備えたeNBのエリアにハンドオーバ(X2ハンドオーバ)する場合について図8を参照して説明する。なお、X2ハンドオーバでは、同一のMMEに接続される移動元、移動先のeNBが、eNB間の接続インタフェースX2を用いて、ハンドオーバする。
UEがトラフィックオフロード機能を備えた基地局間ハンドオーバ(X2ハンドオーバ)する場合について図9を参照して説明する。なお、異なるSGiに接続するOFS、OFC間でプライベートアドレスが重複するものとする。
オフロード機能付き基地局eNB+TOF1でトラフィックをオフロードして通信しているUEが、オフロード機能無し基地局eNBの圏内に移動した場合のハンドオーバについて図10を参照して説明する。
オフロード機能付き基地局eNB+TOF1でトラフィックをオフロードして通信しているUEがオフロード機能無し基地局eNBの圏内に移動した場合のハンドオーバについて図11を参照して説明する。なお、図11の例では、図10の場合と異なり、X2インターフェース経由で送るべきユーザデータパケットが無い場合を想定している。
オフロード機能付き基地局eNB+TOF1でトラフィックをオフロードして通信しているUEがオフロード機能無し基地局eNBの圏内に移動した場合のハンドオーバについて図12を参照して説明する。
CSFBでは、CS(Circuit Switched)呼制御を行うときだけ、LTEネットワークから3G(2G)ネットワークに移りCS通信を行う。UEは、EUTRANからUTRANにハンドオーバする。例えば発信元のG-MSC(関門移動交換局)からCS網を介してMSC/VLRに、着信があることを伝える信号が送信され、MSC(Mobile Switching Center)/VLR(Visited Location Register)では着信情報から対応するMMEを特定し、一斉呼び出し信号(Paging-Request-message)をMMEに送信する。MMEは一斉呼び出し信号をeNBに送信する。このページング信号には、CSサービスの呼び出しであることを示す情報が含まれている。UEはこの情報(CSサービスの呼出)を認識し、MMEに対してCSサービス要求信号を送信する。MMEはハンドオーバコマンド(HO Command)を送信する。UEはハンドオーバ手順を実行するとともに3Gに切り替える。SRVCCも、LTEから3G(2G)エリアにハンドオーバして音声通話を継続する。
図14は、ECM-IDLEへの遷移でのオフロード経路削除を例示する図である。S1リリース手順は、非特許文献3:Figure 5.3.5-1: S1 Release Procedure等)が参照される。
図15は、実施形態2を説明する図である。本実施形態では、前記したOpenFlowの移動制御を、図17を参照して説明した3GPP SIPTOソリューション4に適用し、モビリティが実現できない点を克服したものである。図17の3GPP SIPTOソリューション4では、NATが必要とされるが、OpenFlowを用いた実施形態によれば、NATは不要とされる。
図16は、実施形態3を説明する図である。本実施形態では、フェムト・ゲートウェイ133にトラフィックオフロード(TOF)機能を付加している。オフロード対象のデータトラフィック(パケット)を、コアネットワークを迂回するオフロード経路137を介して、OFS105に転送し、ルータ109からPDN104に転送する。またPDN104からルータ109を介してOFS105に転送されたデータトラフィックは、コアネットワークを迂回してフェムト・ゲートウェイ133に転送され、ネットワーク132を介してフェムトセル用基地局(フェムトセルアクセスポイント)(FAP)131に転送される。図16において、MSC(Mobile Switching Center)、CS(Circuit Switched)コアは、BSC(Base Station Controller:基地局制御装置)に接続される回線交換機と回線交換ネットワークである。CSCF(Call Session Control Function)、IMS(Internet Multimedia Services)コアはIPマルチメディアシステムを構成する(非特許文献4:3GPP TS 23.228 V11.6.0 (2012-09) Figure 4.0参照)。HLR(Home Location Registry)/HSSは加入者情報データベースである。本実施形態によれば、フェムトセルトラフィックの増大によるSGSN、SGW、PGW等の増設を抑制する。
基地局eNBは、ユーザプレーンのヘッダ圧縮及び暗号化の機能を含む。物理(PHY)、メディアアクセス制御(MAC:Media Access Control)、無線リンク制御(RLC:Radio Link Control)、及び、パケットデータ制御プロトコル(PDCP:Packet Data Control Protocol)の各レイヤをホストしている。eNBはコントロールプレーンに対応する無線リソース制御(RRC:Radio Resource Control)機能を提供する。さらに、eNBは、無線リソースマネジメント、アドミッション制御、スケジューリング、ネゴシエートされたUL-QoS(Uplink Quality of Service)の実施、セル情報の報知、ユーザ及びコントロールプレーンデータの暗号化及び復号化、DL/UL(ダウンリンク/アップリンク)ユーザプレーンパケットヘッダの圧縮と解凍等の機能を実行する。eNBはまた、S1-UインタフェースにSGWにそれぞれ接続される。
図18は、前記実施形態のOFC106の構成例を模式的に示す図である。図18において、OFSからのパケットを送受するパケット送受信部1061と、パケットを転送するフローを計算する経路計算部1062と、経路計算部1062で計算されたフローに従い、フロー上の各OFSのフローテーブルを設定するフローテーブル設定部1063は、既存のOFCの構成に従う。実施形態のOFC106は、既存のOFCの構成に加えて、さらに、オフロード制御部1069を備えている。
・オフロード機能付き基地局のネットワークへのアタッチ処理において、認証サーバとのハンドシェイクをフックするOFSから転送されたパケットから、UEの端末情報を取得する端末情報取得部1064と、
・オフロード機能付き基地局からの接続要求(Connect Request)又は間接接続要求(Indirect Connect Request)を処理しオフロード経路を追加し、接続応答を、オフロード機能付き基地局に返す接続要求処理部1065と、
・オフロード機能付き基地局から転送された切断要求(Disconnect Request)を処理しオフロード経路を削除し、削除応答を、オフロード機能付き基地局に返す切断要求処理部1066と、
・接続要求処理部1065での接続処理(オフロード経路の追加)、切断要求処理部1066でのオフロード経路の削除に伴い、OFSのフローテーブルのエントリの追加、削除、及び経路変更等を制御し、フローテーブル設定部1063からOFSに送信するフローテーブル管理部1067と、
を備えている。タイマ1068は、切断要求処理部1066が切断要求を受信してから切断処理を実行するまでのウェイト時間(Tミリ秒)を計時し、Tミリ秒経過でタイムアウトを通知するタイマである。オフロード制御部1069は、図4から図14の各図を参照して説明したOFCのシーケンス動作を担う。なお、OFCにおいて、少なくともオフロード制御部1069の各部は、OFCを構成するコンピュータ上で実行されるプログラムでその処理・機能の一部又は全てを実現するようにしてもよい。当該プログラムは半導体メモリ、磁気ディスク、光ディスク等の媒体(不図示)に記憶保持されて提供される。
図21は、図20(B)の形態に対応する一実施形態を説明する図である。図21において、図1と同一の要素には同一の参照符号が付されている。図1の実施形態との相違点は、オフロード機能付き基地局(eNB+TOF)102Sと、オフロード経路への切り替えを行うスイッチ111Sを備えている。スイッチ111Sは、オープンフロースイッチ(OFS)、仮想スイッチ(Virtual Switch: VSW)、あるいは図3のレイヤ2スイッチであってもよい。スイッチ111SをOFSで構成した場合、スイッチ111Sの経路設定は、OFC106Aから制御される。すなわち、OFC106AからのOFSのフローテーブルのエントリの設定/削除によって制御される。なお、本実施形態の変形例として、スイッチ111Sをオフロード機能付き基地局(eNB+TOF)102Sに組み込んだ構成としてもよいことは勿論である。この場合、オフロード機能付き基地局(eNB+TOF)102Sが、オフロード経路設定機能を具備することになる。
第1のネットワークへのトラフィックをオフロードさせる機能を備えたノードと、
前記第1のネットワークの関門ノードと第2のネットワーク間に配設されたスイッチと、
を備え、
トラフィックのオフロード時には、前記スイッチは、前記ノードを、前記第1のネットワーク迂回用のオフロード経路を介して前記第2のネットワークに接続し、
非オフロード時には、前記ノードは前記第1のネットワークに接続し、前記スイッチは、前記第1のネットワークの前記関門ノードを前記第2のネットワークに接続する、ネットワークシステム。
前記スイッチを制御する制御装置を備えた、付記1記載のネットワークシステム。
前記トラフィックオフロード機能を具備したノードが、無線アクセスネットワークの基地局である、付記2記載のネットワークシステム。
前記ノードは、移動端末から無線ベアラを介して到着したパケットがオフロード対象に該当すると判断した場合、オフロード経路の接続要求を、前記スイッチを介して前記制御装置に送信し、
前記制御装置は、前記ノードからの前記接続要求を受け、前記ノードから転送されたパケットを前記第2のネットワーク向けに転送し、且つ、前記第2のネットワークからのパケットを前記ノードに転送するように、前記スイッチに設定し、接続応答を前記ノードに返す、付記3記載のネットワークシステム。
前記制御装置は、前記移動端末からのアタッチに伴う認証時、前記関門ゲートと認証サーバ間で送受される情報に基づき、前記移動端末の情報を取得する、付記4記載のネットワークシステム。
前記関門ゲートと前記第2のネットワークとの間に、少なくとも一つの前記スイッチと、前記制御装置との組を、複数組備え、
前記関門ゲートと前記第2のネットワークとのインタフェースに関して、少なくとも第1、第2のインタフェースに接続する第1、第2の組の前記スイッチと前記制御装置のプライベートアドレスが重複する場合、前記ノードは、前記接続要求を、前記第1のネットワークを経由し前記関門ゲートから前記第1又は第2の組の前記スイッチを介して前記制御装置に送信し、
前記ノードは、前記制御装置からの前記接続応答を受信した経路から、オフロード先の前記スイッチへの経路を特定する、付記5記載のネットワークシステム。
前記移動端末が、トラフィックオフロード機能を具備しない移動元の基地局から、トラフィックオフロード機能を具備した移動先の基地局へハンドオーバするにあたり、
前記移動先の基地局は、オフロード経路の接続要求を、前記スイッチを介して前記制御装置に送信し、
前記制御装置は、前記接続要求を受け、前記ノードから転送されたパケットを前記第2のネットワーク向けに転送し、且つ、前記第2のネットワークからのパケットを前記移動先の基地局に転送するように前記スイッチに設定し、接続応答を前記移動先の基地局に返す、付記4乃至6のいずれか一に記載のネットワークシステム。
前記移動端末が、トラフィックオフロード機能を具備した移動元の基地局から、トラフィックオフロード機能を具備した移動先の基地局へハンドオーバするにあたり、
前記移動元の基地局は、前記オフロード経路を削除する切断要求を、前記スイッチを介して前記制御装置に送信し、
前記移動先の基地局は、オフロード経路の接続要求を、前記スイッチを介して前記制御装置に送信し、
前記制御装置は、前記接続要求を受け、前記ノードから転送されたパケットを前記第2のネットワーク向けに転送し、且つ、前記第2のネットワークからのパケットを前記移動先の基地局に転送するように、前記スイッチに設定し、接続応答を前記移動先の基地局に返し、
前記制御装置は、前記移動元の基地局のオフロード経路を切断処理し、切断応答を前記移動元の基地局に返す、付記4乃至6のいずれか一に記載のネットワークシステム。
前記移動端末が、トラフィックオフロード機能を具備した移動元の基地局から、トラフィックオフロード機能を具備しない移動先の基地局へハンドオーバするにあたり、
前記移動元の基地局は、オフロード経路を削除する切断要求を、前記スイッチを介して、前記制御装置に送信し、
前記制御装置は、前記移動元の基地局のオフロード経路を切断処理し、切断応答を前記移動元の基地局に返す、付記4乃至6のいずれか一に記載のネットワークシステム。
前記制御装置は、前記基地局からオフロード経路切断要求を受けると、タイマにより予め定められた所定時間遅延させた後に、切断処理を行う、付記8又は9記載のネットワークシステム。
前記移動端末が、トラフィックオフロード機能を具備した移動元の基地局から、トラフィックオフロード機能を具備しない移動先の基地局へハンドオーバするにあたり、
前記移動元の基地局は、オフロード経路を削除する切断要求を、前記スイッチを介して前記制御装置に送信し、
前記制御装置は、前記切断要求を受けると、前記タイマでのタイムアウト発生前に前記第2のネットワークからの受け取ったデータパケットを、基地局間インタフェースを介して、前記移動先の基地局に送信して前記移動端末に送信する、付記10記載のネットワークシステム。
トラフィックオフロード機能を具備した移動元の基地局から、他の第1のネットワークへのフォールバックを行うハンドオーバ時、前記移動元の基地局は、オフロード経路を削除する切断要求を、前記スイッチを介して前記制御装置に送信し、前記制御装置は、前記移動元の基地局のオフロード経路を切断処理し、切断応答を前記移動元の基地局に返す、付記4記載のネットワークシステム。
前記基地局は、移動端末のモビリティを管理するノードから所定のコマンドを受信すると、オフロード経路の削除する切断要求を前記スイッチを介して前記制御装置に送信し、前記移動元の基地局は、オフロード経路を削除する切断要求を、前記スイッチを介して前記制御装置に送信し、
前記制御装置は、前記移動元の基地局のオフロード経路を切断処理し、切断応答を前記移動元の基地局に返す、付記4記載のネットワークシステム。
トラフィックオフロード機能を具備した前記ノードが、無線リンクコントローラと前記第1のネットワーク間のインタフェース上に配設されている、付記1又は2記載のネットワークシステム。
前記トラフィックオフロード機能を具備したノードが、フェムトセルと、前記第1のネットワークを接続するフェムトゲートウェイである、付記1又は2記載のネットワークシステム。
第1のネットワークへのトラフィックをオフロードさせるノードと、
前記第1のネットワークの関門ノードと第2のネットワーク間に配設されたスイッチとを用いて、トラフィックをオフロードさせる場合、
前記スイッチは、前記ノードを、前記第1のネットワーク迂回用のオフロード経路を介して前記第2のネットワークに接続し、
非オフロード時には、前記ノードは前記第1のネットワークに接続し、前記スイッチは、前記第1のネットワークの前記関門ノードを前記第2のネットワークに接続する、ネットワーク制御方法。
移動端末から無線ベアラを介して到着したパケットがオフロード対象に該当すると判断した場合、第1のネットワークを迂回するオフロード経路の接続要求を、直接又は第1のネットワークを経由して、前記第1のネットワークの関門ノードと第2のネットワーク間に配設されたスイッチに送信する手段を備え、前記接続要求は、前記スイッチから前記制御装置に送信され、接続処理が行われ、前記スイッチを介して前記オフロード経路と第2のネットワークが接続され、
前記移動端末のモビリティを管理するノードから所定のコマンドを受けると、オフロード経路の切断要求を、前記スイッチに送信する手段を備え、前記切断要求は、前記スイッチから前記制御装置に送信されて前記オフロード経路が切断される基地局装置。
前記移動端末のハンドオーバにおいて移動先の基地局装置がオフロード機能を具備する基地局である場合、オフロード経路の接続要求を、直接又は第1のネットワークを経由して前記スイッチに送信する手段を備え、前記接続要求は、前記スイッチから前記制御装置に送信され、接続処理が行われ、前記スイッチを介して前記オフロード経路と第2のネットワークが接続される、付記17記載の基地局装置。
前記移動端末のハンドオーバにおいて移動元の基地局装置がオフロード機能を具備する基地局であり、オフロード経路が接続されている場合、前記オフロード経路の切断要求を前記スイッチに送信する手段を備えている、付記17又は18記載の基地局装置。
第1のネットワークの関門ノードと第2のネットワーク間に配設されたスイッチを制御する制御装置であって、
基地局装置から、前記第1のネットワークを迂回するオフロード経路の接続要求を、前記スイッチを受け取ると、前記基地局装置から前記オフロード経路に転送されたパケットを前記第2のネットワーク向けに転送し、且つ、前記第2のネットワークからのパケットを前記オフロード経路を介して前記ノードに転送するように、前記スイッチを設定し、接続応答を前記基地局装置に返す手段と、
前記基地局装置から、前記オフロード経路の切断要求を、前記スイッチを受け取ると、前記第1のネットワークの前記関門ノードを前記第2のネットワークに接続するように、前記スイッチを設定し、切断応答を前記基地局装置に返す手段と、を備えた制御装置。
102、102-1、102-2 基地局(オフロード機能付基地局eNB+TOF)
102a 基地局(オフロード機能無し基地局)
102S 基地局(オフロード機能付基地局eNB+TOF+SW)
103 S/P-GW
103S SGW
103P PGW
104 PDN
105 OFS
106、106A OFC
107、127、137 オフロード経路
108 RADIUS
109、109-1、109-2 ルータ
110 局舎
111、111-2 レイヤ2スイッチ
111S スイッチ
112 MME
113 PCRF
114 HSS/AAA
115 ルータ
121 UE
122 NB(NodeB)
123 RNC
124 TOF
125 SGSN
131 FAP
132 Internet & Broadband
133 Femto-GW+TOF
1020 無線受信部
1021 無線送信部
1022 オフロードトラフィック判断部
1023 接続要求送信/接続応答受信部
1024 切断要求送信/切断応答受信部
1025 オフロードトラフィック送受信部
1026 ハンドオーバ処理部
1027 切断制御部
1028 トラフィック送受信部
1031 S1-Uインタフェース
1032 VLANインタフェース
1033 S1-MMEインタフェース
1034 X2インタフェース
1061 パケット送受信部
1062 経路計算部
1063 フローテーブル設定部
1064 端末情報取得部
1065 接続要求処理部
1066 切断要求処理部
1067 フローテーブル管理部
1068 タイマ
1069 オフロード制御部
Claims (30)
- 第1のネットワークと第2のネットワーク間に配設されたスイッチ手段と、
前記第1のネットワークへのトラフィックのオフロードの有無を判定し、オフロードする場合、前記第1のネットワークを迂回するオフロード用の経路の設定を、前記スイッチ手段に対して行うオフロード判定手段と、
を備え、
前記第1のネットワークへのトラフィックのオフロード時に、オフロード対象のパケットは、前記オフロード用の経路と前記第2のネットワーク間を、前記スイッチ手段を介して転送される、ネットワークシステム。 - 前記第1のネットワークへのトラフィックをオフロードさせるオフロード手段をさらに備え、トラフィックのオフロード時に、前記オフロード手段は、オフロード対象のパケットを、前記オフロード用の経路に転送し、前記スイッチ手段を介して前記第2のネットワークに送信する、請求項1記載のネットワークシステム。
- 前記スイッチ手段を備えたスイッチと、
前記オフロード判定手段を備え、前記スイッチを制御する制御装置と、
を備え、
無線アクセスネットワークの基地局に、前記オフロード手段を備えた、請求項2記載のネットワークシステム。 - 前記オフロード判定手段を、移動端末のモビリティを管理するノードに備え、
無線アクセスネットワークの基地局、及び/又は、選択されたパケットをオフロードする関門ノードに、前記オフロード手段を備えた、請求項2記載のネットワークシステム。 - 前記オフロード判定手段と、前記オフロード手段を、無線アクセスネットワークの基地局に備えた、請求項1記載のネットワークシステム。
- 前記オフロード手段を、無線リンクコントローラと前記第1のネットワーク間のインタフェース上のノードに備えた、請求項2記載のネットワークシステム。
- 前記オフロード判定手段を、前記オフロード手段とともに前記ノードに備えた、請求項6記載のネットワークシステム。
- 前記オフロード手段を、フェムトセルと、前記第1のネットワークを接続するフェムトゲートウェイに備えた、請求項2記載のネットワークシステム。
- 前記オフロード判定手段を、前記オフロード手段とともに前記フェムトゲートウェイに備えた、請求項8記載のネットワークシステム。
- 前記制御装置は、前記オフロードが必要と判定した場合、前記スイッチに対して、オフロードの対象となるパケットを、前記基地局と前記第2のネットワーク間を接続する前記オフロード用の経路に転送するように指示する、請求項3記載のネットワークシステム。
- 前記基地局の前記オフロード手段は、移動端末からのパケットがオフロード対象の無線ベアラからのものである場合、前記制御装置の前記オフロード判定手段に対して、前記オフロード用の経路の設定要求を行う、請求項3記載のネットワークシステム。
- 前記基地局の前記オフロード手段は、移動端末から無線ベアラを介して到着したパケットがオフロード対象である場合、前記オフロード経路の接続要求を、前記スイッチを介して前記制御装置に送信し、
前記制御装置の前記オフロード判定手段は、前記接続要求を受け、前記基地局から前記オフロード経路を介して前記スイッチに転送されたパケットを前記第2のネットワーク向けに転送し、且つ、前記第2のネットワークからのパケットを前記スイッチから前記オフロード経路を介して前記基地局に転送するように、前記スイッチに設定し、接続応答を前記基地局に返す、請求項3記載のネットワークシステム。 - 前記移動端末のハンドオーバ時、移動元の基地局から移動先の基地局に関して、前記移動元の基地局で前記第1のネットワークへのトラフィックのオフロードを行っているか、前記移動先の基地局が前記オフロード手段を備えているかに応じて、前記制御装置では、前記移動元の基地局に対するオフロード経路の切断、前記移動先の基地局に対する前記オフロード経路の設定を行う、請求項12記載のネットワークシステム。
- 前記基地局は、前記移動端末のモビリティを管理するノードから、予め定められた所定のコマンドを受信すると、前記オフロード経路の削除する切断要求を、前記スイッチを介して、前記制御装置に送信し、前記制御装置は、前記オフロード経路を切断処理し、切断応答を前記基地局に返す、請求項12又は13記載のネットワークシステム。
- 第1のネットワークへのトラフィックをオフロードさせるオフロード手段と、
前記第1のネットワークへのトラフィックのオフロードの指示を前記オフロード手段に対して行うオフロード判定手段と、
を備え、
前記オフロード手段は、前記オフロードの指示を受け、受信パケットに対してオフロードの有無を判断し、オフロード時には、前記パケットを、前記第1のネットワークを迂回するオフロード用の経路を転送する、ネットワークシステム。 - スイッチを制御する制御装置に、前記オフロード判定手段を備え、
無線アクセスネットワークの基地局に、前記オフロード手段を備えた、請求項15記載のネットワークシステム。 - 前記基地局の前記オフロード手段は、前記移動端末からのパケットがオフロード対象の無線ベアラからのものである場合、前記パケットを前記オフロード用の経路に転送する、請求項16記載のネットワークシステム。
- 前記制御装置において、前記オフロード判定手段は、前記第1のネットワークへのトラフィックのオフロードが必要と判定した場合、前記基地局の前記オフロード手段に対して、オフロードの対象となるパケットを、前記オフロード用の経路に転送するように指示する、請求項16記載のネットワークシステム。
- 前記基地局の前記オフロード手段は、前記移動端末からのパケットがオフロード対象の無線ベアラからのものである場合、前記制御装置の前記オフロード判定手段に対してオフロード経路設定要求を行う、請求項16記載のネットワークシステム。
- 前記第1のネットワークと第2のネットワーク間に配設された第2のスイッチをさらに備え、
トラフィックをオフロードする場合、前記制御装置の前記オフロード判定手段は、前記第2のスイッチに対して、オフロードの対象となるパケットを、前記基地局と前記第2のネットワーク間を接続する前記オフロード経路に転送するように指示する、請求項16記載のネットワークシステム。 - コアネットワークへのトラフィックのオフロード時に、前記コアネットワークを迂回するオフロード経路の設定要求を、オフロード判定手段を備えたノードに送信し、
移動端末からの受信パケットに対してオフロードの有無を判断し、オフロード時には、前記受信パケットを、前記オフロード用の経路に転送する、基地局装置。 - コアネットワークへのトラフィックのオフロードの指示を行うオフロード判定手段からのオフロード指示を受け、
移動端末からの受信パケットに対してオフロードの有無を判断し、オフロード対象のパケットを、前記コアネットワークを迂回するオフロード用の経路に転送する、基地局装置。 - 第1のネットワークへのトラフィックをオフロードするオフロード手段からオフロード用の経路設定要求を受けると、前記第1のネットワークと第2のネットワークの間に接続するスイッチに対して、前記第1のネットワークを迂回して、前記第2のネットワークに接続するオフロード用の経路の設定を行う、制御装置。
- 第1のネットワークへのトラフィックをオフロードするオフロード手段からオフロード用の経路設定要求を受けると、前記オフロード手段に対してオフロード指示を送信する手段を備え、前記オフロード手段に、オフロード対象の受信パケットを、前記第1のネットワークを迂回するオフロード用の経路へオフロードさせる、制御装置。
- 第1のネットワークへのトラフィックのオフロードの有無を判定し、オフロードする場合、前記第1のネットワークを迂回するオフロード用の経路の設定を、前記第1のネットワークと第2のネットワーク間に配設されたスイッチ手段に対して行い、
前記第1のネットワークへのトラフィックのオフロード時に、オフロード対象のパケットは、前記オフロード用の経路と前記第2のネットワーク間を、前記スイッチ手段を介して転送される、ネットワーク制御方法。 - 前記第1のネットワークへのトラフィックをオフロードさせるオフロード手段では、トラフィックのオフロード時に、オフロード対象のパケットを、前記オフロード用の経路に転送し、さらに前記スイッチ手段を介して前記第2のネットワークに送信する、請求項25記載のネットワーク制御方法。
- 第1のネットワークへのトラフィックをオフロードさせるオフロード手段では、オフロードの有無を判定するオフロード判定手段からのオフロードの指示を受けると、受信パケットに対してオフロードの有無を判断し、オフロード時には、前記受信パケットを、前記第1のネットワークを迂回するオフロード用の経路に転送する、ネットワーク制御方法。
- 前記第1のネットワークと第2のネットワーク間に配設されたスイッチに対して、前記オフロード判定手段は、前記第1のネットワークを迂回して、前記第2のネットワークに接続するオフロード用の経路の設定を行う、請求項27記載のネットワーク制御方法。
- 基地局装置を構成するコンピュータに、
移動端末から無線ベアラを介して到着したパケットがオフロード対象である場合、第1のネットワークを迂回するオフロード経路の接続要求を、直接又は第1のネットワークを経由して、前記第1のネットワークと第2のネットワーク間に配設されたスイッチに送信する処理と、
前記移動端末のモビリティを管理するノードから所定のコマンドを受けると、前記オフロード経路の切断要求を、前記スイッチに送信する処理と、
を実行させるプログラム。 - 第1のネットワークと第2のネットワーク間に配設されたスイッチを制御する制御装置を構成するコンピュータに、
基地局装置から、前記第1のネットワークを迂回するオフロード経路の接続要求を、前記スイッチを介して受け取ると、前記基地局装置から前記オフロード経路に転送されたパケットを前記第2のネットワーク向けに転送し、且つ、前記第2のネットワークからのパケットを前記オフロード経路に転送するように、前記スイッチに設定し、前記オフロード経路の接続要求に対する接続応答を前記基地局装置に返す処理と、
前記基地局装置から、前記オフロード経路の切断要求を、前記スイッチを介して受け取ると、前記第1のネットワークの前記関門ノードを前記第2のネットワークに接続するように前記スイッチに設定し、前記オフロード経路の切断要求に対する切断応答を前記基地局装置に返す処理と、
を実行させるプログラム。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP13856030.5A EP2922345B1 (en) | 2012-11-16 | 2013-11-15 | Network system, method, device and program |
JP2014547049A JP6507641B2 (ja) | 2012-11-16 | 2013-11-15 | ネットワークシステムと方法と装置並びにプログラム |
RU2015122931A RU2616169C2 (ru) | 2012-11-16 | 2013-11-15 | Сетевая система, способ, устройство и программа |
US14/440,615 US9461919B2 (en) | 2012-11-16 | 2013-11-15 | Network system, method, apparatus, and program |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2012-252426 | 2012-11-16 | ||
JP2012252426 | 2012-11-16 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014077352A1 true WO2014077352A1 (ja) | 2014-05-22 |
Family
ID=50731261
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2013/080875 WO2014077352A1 (ja) | 2012-11-16 | 2013-11-15 | ネットワークシステムと方法と装置並びにプログラム |
Country Status (5)
Country | Link |
---|---|
US (1) | US9461919B2 (ja) |
EP (1) | EP2922345B1 (ja) |
JP (2) | JP6507641B2 (ja) |
RU (1) | RU2616169C2 (ja) |
WO (1) | WO2014077352A1 (ja) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105323847A (zh) * | 2014-07-04 | 2016-02-10 | 中国移动通信集团河北有限公司 | 基于虚拟化演进分组核心网的通信方法、控制器及虚拟机 |
US20160127966A1 (en) * | 2014-10-29 | 2016-05-05 | Research & Business Foundation Sungkyunkwan Universtiy | Openflow controller and control method for supporting handover in mobile ipv6 based on software definition network |
WO2016148224A1 (ja) * | 2015-03-19 | 2016-09-22 | 日本電気株式会社 | 制御装置、通信システム、ネットワーク機能提供装置、通信装置、通信方法及びプログラム |
US9762508B2 (en) | 2014-10-02 | 2017-09-12 | Microsoft Technology Licensing, Llc | Relay optimization using software defined networking |
JP2018527849A (ja) * | 2015-09-17 | 2018-09-20 | アルカテル−ルーセント | セルラアクセスネットワークにおけるネイティブでありブリッジされた通信のための装置、システムおよび方法 |
TWI659660B (zh) * | 2015-09-09 | 2019-05-11 | 阿爾卡特朗訊美國股份有限公司 | 用於在異質無線通訊系統中的重新路由封包之收費 |
Families Citing this family (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105122882B (zh) * | 2013-11-04 | 2019-05-10 | 华为技术有限公司 | 一种网络切换的方法、设备及系统 |
EP3070891B1 (en) | 2013-12-11 | 2018-06-20 | Huawei Technologies Co., Ltd. | Packet processing method and device |
KR101579070B1 (ko) * | 2014-08-11 | 2016-01-04 | 주식회사 이노와이어리스 | 펨토셀을 이용한 코어 네트워크 무선 데이터의 오프로딩 방법 |
EP3200499B1 (en) * | 2014-11-19 | 2019-03-13 | Huawei Technologies Co. Ltd. | Mobility management entity and home subscriber server for handling callee service according to csfb and a faulty state of a pgw |
US20170012866A1 (en) * | 2015-07-09 | 2017-01-12 | Infinera Corporation | Systems, methods, and apparatus for forwarding a data flow |
WO2017037193A1 (en) * | 2015-09-02 | 2017-03-09 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and network nodes for scalable top-of-chain selection in mobile service chaining |
CN108029036B (zh) | 2015-09-15 | 2021-07-16 | 华为技术有限公司 | 业务处理方法、业务处理装置和通信系统 |
WO2017177366A1 (en) * | 2016-04-11 | 2017-10-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and device for bearer establishment |
US10149193B2 (en) | 2016-06-15 | 2018-12-04 | At&T Intellectual Property I, L.P. | Method and apparatus for dynamically managing network resources |
US10454836B2 (en) | 2016-11-01 | 2019-10-22 | At&T Intellectual Property I, L.P. | Method and apparatus for dynamically adapting a software defined network |
US10284730B2 (en) | 2016-11-01 | 2019-05-07 | At&T Intellectual Property I, L.P. | Method and apparatus for adaptive charging and performance in a software defined network |
US10505870B2 (en) | 2016-11-07 | 2019-12-10 | At&T Intellectual Property I, L.P. | Method and apparatus for a responsive software defined network |
US10469376B2 (en) | 2016-11-15 | 2019-11-05 | At&T Intellectual Property I, L.P. | Method and apparatus for dynamic network routing in a software defined network |
US10039006B2 (en) * | 2016-12-05 | 2018-07-31 | At&T Intellectual Property I, L.P. | Method and system providing local data breakout within mobility networks |
US10264075B2 (en) * | 2017-02-27 | 2019-04-16 | At&T Intellectual Property I, L.P. | Methods, systems, and devices for multiplexing service information from sensor data |
US10469286B2 (en) | 2017-03-06 | 2019-11-05 | At&T Intellectual Property I, L.P. | Methods, systems, and devices for managing client devices using a virtual anchor manager |
US10212289B2 (en) | 2017-04-27 | 2019-02-19 | At&T Intellectual Property I, L.P. | Method and apparatus for managing resources in a software defined network |
US10673751B2 (en) | 2017-04-27 | 2020-06-02 | At&T Intellectual Property I, L.P. | Method and apparatus for enhancing services in a software defined network |
US10819606B2 (en) | 2017-04-27 | 2020-10-27 | At&T Intellectual Property I, L.P. | Method and apparatus for selecting processing paths in a converged network |
US10749796B2 (en) | 2017-04-27 | 2020-08-18 | At&T Intellectual Property I, L.P. | Method and apparatus for selecting processing paths in a software defined network |
US10257668B2 (en) | 2017-05-09 | 2019-04-09 | At&T Intellectual Property I, L.P. | Dynamic network slice-switching and handover system and method |
US10382903B2 (en) | 2017-05-09 | 2019-08-13 | At&T Intellectual Property I, L.P. | Multi-slicing orchestration system and method for service and/or content delivery |
CN107333295B (zh) * | 2017-06-09 | 2021-04-06 | 京信通信系统(中国)有限公司 | 一种数据分流方法和网关 |
US10070344B1 (en) | 2017-07-25 | 2018-09-04 | At&T Intellectual Property I, L.P. | Method and system for managing utilization of slices in a virtual network function environment |
US10104548B1 (en) | 2017-12-18 | 2018-10-16 | At&T Intellectual Property I, L.P. | Method and apparatus for dynamic instantiation of virtual service slices for autonomous machines |
CN112219443B (zh) * | 2018-04-06 | 2023-11-14 | 瑞典爱立信有限公司 | 无线通信网络中的第一单元、第二单元和方法 |
CN109067665B (zh) * | 2018-09-25 | 2022-01-11 | 华为技术有限公司 | 拥塞控制方法和网络设备 |
CN111988227B (zh) * | 2019-05-24 | 2023-05-09 | 中兴通讯股份有限公司 | 一种流量处理方法及相关设备、建立转发表的方法及装置 |
US20230013489A1 (en) * | 2021-07-16 | 2023-01-19 | Vmware, Inc. | Managing l4 ports |
US20230021019A1 (en) * | 2021-07-16 | 2023-01-19 | Vmware, Inc. | Managing l4 ports |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012035697A1 (ja) * | 2010-09-17 | 2012-03-22 | パナソニック株式会社 | 基地局及び通信システム |
US20120076121A1 (en) * | 2010-09-28 | 2012-03-29 | Noun Choi | Releasing Connections with Local GW When UE Moves Out of Residential/Enterprise Network Coverage |
JP2012175576A (ja) * | 2011-02-23 | 2012-09-10 | Ntt Docomo Inc | データオフロード装置を含む通信システム、データオフロード装置を含む通信システムのリロケーション制御装置 |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4755137B2 (ja) | 2007-05-01 | 2011-08-24 | 株式会社エヌ・ティ・ティ・ドコモ | 基地局装置及び通信制御方法 |
JP2009253431A (ja) * | 2008-04-02 | 2009-10-29 | Alcatel-Lucent Usa Inc | Iuインターフェースを有するUMTSフェムトセル解法においてPSトラフィックをオフロードする方法。 |
US8635335B2 (en) | 2009-01-28 | 2014-01-21 | Headwater Partners I Llc | System and method for wireless network offloading |
US8743696B2 (en) * | 2009-08-07 | 2014-06-03 | Cisco Technology, Inc. | Mobile transport solution for offloading to an alternate network |
US8103310B1 (en) | 2009-08-07 | 2012-01-24 | Sprint Spectrum L.P. | Methods and systems for using femtocells to address macro-network backhaul congestion |
GB2472866B (en) * | 2009-08-21 | 2013-05-08 | Samsung Electronics Co Ltd | Network elements, integrated circuits and methods for routing control |
US8831014B2 (en) * | 2009-09-26 | 2014-09-09 | Cisco Technology, Inc. | Providing services at a communication network edge |
US8432871B1 (en) * | 2010-03-26 | 2013-04-30 | Juniper Networks, Inc. | Offloading mobile traffic from a mobile core network |
US8493851B2 (en) * | 2010-05-07 | 2013-07-23 | Broadcom Corporation | Method and system for offloading tunnel packet processing in cloud computing |
JP5440696B2 (ja) * | 2010-05-13 | 2014-03-12 | 日本電気株式会社 | ゲートウェイ装置、基地局、移動管理サーバ、通信方法 |
JP5541037B2 (ja) * | 2010-09-22 | 2014-07-09 | 日本電気株式会社 | フェムトセルアクセスポイント及びそれに用いるパケットデータオフロード機能制御方法 |
US8547835B2 (en) * | 2010-10-21 | 2013-10-01 | Telefonaktiebolaget L M Ericsson (Publ) | Controlling IP flows to bypass a packet data network gateway using multi-path transmission control protocol connections |
-
2013
- 2013-11-15 EP EP13856030.5A patent/EP2922345B1/en active Active
- 2013-11-15 RU RU2015122931A patent/RU2616169C2/ru active
- 2013-11-15 US US14/440,615 patent/US9461919B2/en active Active
- 2013-11-15 JP JP2014547049A patent/JP6507641B2/ja active Active
- 2013-11-15 WO PCT/JP2013/080875 patent/WO2014077352A1/ja active Application Filing
-
2019
- 2019-03-29 JP JP2019065749A patent/JP7088557B2/ja active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012035697A1 (ja) * | 2010-09-17 | 2012-03-22 | パナソニック株式会社 | 基地局及び通信システム |
US20120076121A1 (en) * | 2010-09-28 | 2012-03-29 | Noun Choi | Releasing Connections with Local GW When UE Moves Out of Residential/Enterprise Network Coverage |
JP2012175576A (ja) * | 2011-02-23 | 2012-09-10 | Ntt Docomo Inc | データオフロード装置を含む通信システム、データオフロード装置を含む通信システムのリロケーション制御装置 |
Non-Patent Citations (6)
Title |
---|
"TECHNICAL SPECIFICATION GROUP SERVICES AND SYSTEM ASPECTS;LOCAL IP ACCESS AND SELECTED IP TRAFFIC OFFLOAD (LIPA-SIPTO)", 3GPP TR 23.829 V10.0.1, October 2011 (2011-10-01), XP050914505 * |
3GPP TR 23.829, V10.0.1, October 2011 (2011-10-01) |
3GPP TS 23.228, V11.6.0, September 2012 (2012-09-01) |
3GPP TS 23.401, V 1 1.3 .0, September 2012 (2012-09-01) |
3GPP TS 23.402, VI 1.4.0, September 2012 (2012-09-01) |
See also references of EP2922345A4 |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105323847A (zh) * | 2014-07-04 | 2016-02-10 | 中国移动通信集团河北有限公司 | 基于虚拟化演进分组核心网的通信方法、控制器及虚拟机 |
CN105323847B (zh) * | 2014-07-04 | 2018-12-07 | 中国移动通信集团河北有限公司 | 基于虚拟化演进分组核心网的通信方法、控制器及虚拟机 |
US9762508B2 (en) | 2014-10-02 | 2017-09-12 | Microsoft Technology Licensing, Llc | Relay optimization using software defined networking |
US20160127966A1 (en) * | 2014-10-29 | 2016-05-05 | Research & Business Foundation Sungkyunkwan Universtiy | Openflow controller and control method for supporting handover in mobile ipv6 based on software definition network |
US9992718B2 (en) * | 2014-10-29 | 2018-06-05 | Research & Business Foundation Sungkyunkwan University | Openflow controller and control method for supporting handover in mobile IPv6 based on software definition network |
WO2016148224A1 (ja) * | 2015-03-19 | 2016-09-22 | 日本電気株式会社 | 制御装置、通信システム、ネットワーク機能提供装置、通信装置、通信方法及びプログラム |
TWI659660B (zh) * | 2015-09-09 | 2019-05-11 | 阿爾卡特朗訊美國股份有限公司 | 用於在異質無線通訊系統中的重新路由封包之收費 |
JP2018527849A (ja) * | 2015-09-17 | 2018-09-20 | アルカテル−ルーセント | セルラアクセスネットワークにおけるネイティブでありブリッジされた通信のための装置、システムおよび方法 |
US10938598B2 (en) | 2015-09-17 | 2021-03-02 | Alcatel Lucent | Apparatus, system and methods for native bridged communication in cellular access network |
Also Published As
Publication number | Publication date |
---|---|
JP7088557B2 (ja) | 2022-06-21 |
US9461919B2 (en) | 2016-10-04 |
RU2015122931A (ru) | 2017-01-10 |
JP2019135865A (ja) | 2019-08-15 |
US20150295833A1 (en) | 2015-10-15 |
EP2922345B1 (en) | 2020-02-26 |
EP2922345A4 (en) | 2016-06-29 |
EP2922345A1 (en) | 2015-09-23 |
JPWO2014077352A1 (ja) | 2017-01-05 |
RU2616169C2 (ru) | 2017-04-12 |
JP6507641B2 (ja) | 2019-05-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP7088557B2 (ja) | ネットワークシステムと方法と装置並びにプログラム | |
US9167486B2 (en) | Inter-VPLMN handover via a handover proxy node | |
US8781474B2 (en) | Non-3GPP to 3GPP network handover optimizations | |
US9998569B2 (en) | Handling multipath transmission control protocol signaling in a communications network | |
JP5426025B2 (ja) | 移動ネットワークにおいてユーザ・プレーン・データをルーティングする方法、装置、及びシステム | |
US9769852B2 (en) | Maintaining current cell location information in a cellular access network | |
US9775079B2 (en) | Method and apparatus for mobile terminal connection control and management of local accesses | |
US8948137B2 (en) | Internetworking of cellular radio networks and wireless data networks | |
US8804682B2 (en) | Apparatus for management of local IP access in a segmented mobile communication system | |
US9668293B2 (en) | Relocation of mobility anchor for nomadic subscribers | |
JP6489019B2 (ja) | 通信システム、通信装置および通信制御方法 | |
US20120039213A1 (en) | Mobile communication method, mobile communication system, and corresponding apparatus | |
US20200008265A1 (en) | Method for avoiding handover failure | |
JP2013526087A (ja) | ローカルipネットワークに接続するueのハンドオーバ方法、ハンドオーバシステム、装置 | |
WO2011140927A1 (zh) | 一种增强移动性的分流方法及装置 |
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: 13856030 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14440615 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2013856030 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2014547049 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2015122931 Country of ref document: RU Kind code of ref document: A |