US9191872B2 - System and method to correlate handover transitions between 3GPP network access and untrusted non-3GPP network access - Google Patents
System and method to correlate handover transitions between 3GPP network access and untrusted non-3GPP network access Download PDFInfo
- Publication number
- US9191872B2 US9191872B2 US14/133,254 US201314133254A US9191872B2 US 9191872 B2 US9191872 B2 US 9191872B2 US 201314133254 A US201314133254 A US 201314133254A US 9191872 B2 US9191872 B2 US 9191872B2
- Authority
- US
- United States
- Prior art keywords
- response
- node
- network
- monitoring device
- receiving
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
- 238000000034 method Methods 0.000 title claims description 57
- 230000007704 transition Effects 0.000 title description 14
- 230000004044 response Effects 0.000 claims abstract description 65
- 238000012806 monitoring device Methods 0.000 claims abstract description 45
- 238000012544 monitoring process Methods 0.000 claims description 20
- 230000006870 function Effects 0.000 claims description 18
- 238000004891 communication Methods 0.000 claims description 15
- 230000008569 process Effects 0.000 claims description 11
- 238000013507 mapping Methods 0.000 claims description 6
- 238000004321 preservation Methods 0.000 claims 1
- 238000012546 transfer Methods 0.000 description 11
- 241000760358 Enodes Species 0.000 description 10
- 238000010586 diagram Methods 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 7
- 230000004048 modification Effects 0.000 description 6
- 238000012986 modification Methods 0.000 description 6
- 230000011664 signaling Effects 0.000 description 4
- 230000001413 cellular effect Effects 0.000 description 3
- 230000008520 organization Effects 0.000 description 3
- 230000032258 transport Effects 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000000644 propagated effect Effects 0.000 description 1
- 238000004705 quadratic configuration interaction calculation Methods 0.000 description 1
- 238000012216 screening Methods 0.000 description 1
- 238000007493 shaping process Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 230000005641 tunneling Effects 0.000 description 1
- 239000011800 void material Substances 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/14—Reselecting a network or an air interface
- H04W36/144—Reselecting a network or an air interface over a different radio air interface technology
- H04W36/1446—Reselecting a network or an air interface over a different radio air interface technology wherein at least one of the networks is unlicensed
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/18—Service support devices; Network management devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/02—Inter-networking arrangements
Definitions
- the present disclosure relates to tracking User Equipment (UE) amongst various types of network access, and more particularly, to correlating UE to a particular subscriber during handover transitions.
- UE User Equipment
- the 3rd Generation Partnership Project (3GPP) organization specifies the architecture of mobile cellular networks like Global System for Mobile Communications (GSM) and Universal Mobile Telecommunications System (UMTS).
- GSM Global System for Mobile Communications
- UMTS Universal Mobile Telecommunications System
- the latest mobile network architecture defined by the 3GPP is called Evolved 3GPP Packet Switched Domain—also known as the Evolved Packet System (EPS).
- EPS Evolved Packet Switched Domain
- the EPS combines an Evolved Packet Core (EPC) network that is able to connect a new generation of an access network technology called Evolved Universal Terrestrial Radio Access Network (E-UTRAN) as well as the pre-successor of the E-UTRAN called Universal Terrestrial Radio Access Network (UTRAN).
- EPC Evolved Packet Core
- UTRAN Universal Terrestrial Radio Access Network
- the 3GPP EPS is also able to provide connectivity to mobile terminals (also known as User Equipment(s) (UEs)) attached non-3GPP access networks.
- UEs User Equipment
- 3GPP networks also provide for inter-connection between the EPC and non-3GPP access networks. While the 3GPP access networks are based on access technologies standardized by the 3GPP organization, non-3GPP access networks are based on access technologies defined by other organizations like Institute of Electrical and Electronics Engineers (IEEE) and 3rd Generation Partnership Project 2 (3GPP2). For example two technologies defined by the IEEE that may interwork with the EPC are WLAN (Wireless Local Area Network), i.e. the IEEE standard 802.11 family, and WiMAX (Worldwide Interoperability for Microwave Access), also known as the IEEE standard 802.16 family.
- IEEE Institute of Electrical and Electronics Engineers
- 3GPP2 3rd Generation Partnership Project 2
- mobile data offloading refers to the use of complementary network technologies for delivering data originally targeted for 3GPP communication networks.
- Rules triggering the mobile offloading action can be set by either an end-user (mobile subscriber) or an operator.
- the code operating on the rules resides in an end-user device, in a server, or is divided between the two. End users use data offloading for data service cost control, the availability of higher bandwidth and the like. Operators use data offloading to ease congestion of cellular networks.
- subscriber UE transfers to/from 3GPP access from/to non-3GPP access e.g., untrusted 3GPP access
- subscriber information is typically lost. That is, tracking subscribers during UE transfers between networks is difficult at best, which affects accuracy when monitoring key performance indicators, Quality of Service (QoS), and other operating metrics for subscribers.
- QoS Quality of Service
- This disclosure provides systems and methods that correlate handovers for subscribers between 3GPP networks and untrusted non-3GPP networks.
- the invention provides seamless tracking for subscribers' User Equipment (UE) across the various networks and correlates network connections established prior to a handover as well as post-handover.
- UE User Equipment
- KPIs Key Performance Indicators
- a passive network monitoring device correlates a subscriber to UE during a handover transition from 3GPP network access to untrusted non-3GPP network access.
- the passive network monitoring device monitors one or more network interfaces between network nodes including a serving gateway (SGW) node, a packet data network gateway (PGW) node, an evolved Packet Data Gateway (ePDG) node, and a Policy Control and Charging Rules Function (PCRF) node and a Policy and Charging Enforcement Function (PCEF) node.
- SGW serving gateway
- PGW packet data network gateway
- ePDG evolved Packet Data Gateway
- PCRF Policy Control and Charging Rules Function
- PCEF Policy and Charging Enforcement Function
- the device receives a handover indication for the UE from untrusted non-3GPP network access to 3GPP network access (e.g., from a create session request from the network interfaces between the SGW node and the PGW node, which indicates the handover for the UE, etc.), and receives a response to an attach request from one or more of the network interfaces (e.g., a create session response, etc.).
- the response includes a mobile service internet protocol (MSIP) address (e.g., in a PDN Address Allocation field) and a charging identification (ID) for the UE.
- MSIP mobile service internet protocol
- ID charging identification
- the device determines the UE is from a single subscriber based on each of the handover, the MSIP of the response and the charging ID of the response, and correlates information for the UE at each of the one or more network interfaces with the single subscriber.
- the passive network monitoring device also determines data bearer contact information for the UE prior to receiving the attach request, determines data bearer context information for the UE after receiving the response, and maps the data bearer context information prior to receiving the attach request to the data bearer context information after receiving the response when the UE is from the single subscriber.
- the passive network monitoring device correlates a subscriber to UE during a handover transition from untrusted non-3GPP network access to 3GPP network access.
- the passive network monitoring device monitors one or more network interfaces between network nodes including a serving gateway (SGW) node, a packet data network gateway (PGW) node, an evolved Packet Data Gateway (ePDG) node, and a Policy Control and Charging Rules Function (PCRF) node and a Policy and Charging Enforcement Function (PCEF) node.
- SGW serving gateway
- PGW packet data network gateway
- ePDG evolved Packet Data Gateway
- PCRF Policy Control and Charging Rules Function
- PCEF Policy and Charging Enforcement Function
- the response includes a mobile service internet protocol (MSIP) address and a charging identification (ID) for the UE.
- MSIP mobile service internet protocol
- ID charging identification
- the passive network monitoring device also determines that the UE is from a single subscriber based on each of: the handover indication, the MSIP of the response and the charging ID of the response, and correlates information for the UE at each of the one or more network interfaces with the single subscriber.
- FIG. 1 shows an overview on the architecture of a 3GPP Evolved Packet System (EPS);
- EPS Evolved Packet System
- FIG. 2 illustrates an example network device/node
- FIG. 3 illustrates an example view of a communication network showing transition of UE between 3GPP network access and untrusted non-3GPP network access;
- FIG. 4 illustrates an example signal diagram, showing communications between the various network nodes shown in FIG. 3 , particularly from the perspective of UE transfer or transition from untrusted non-3GPP network access to 3GPP network access;
- FIG. 5 illustrates an example signal diagram, showing communications between the various network nodes shown in FIG. 3 , particularly from the perspective of UE transfer or transition from 3GPP network access to untrusted non-3GPP network access;
- FIG. 6 illustrates an example simplified procedure for correlating a handover for UE from untrusted non-3GPP network access to 3GPP network access;
- FIG. 7 illustrates an example simplified procedure for correlating a handover for UE from 3GPP network access to untrusted non-3GPP network access.
- 3GPP 3rd Generation Partnership Project
- GSM Global System for Mobile Communications
- UMTS Universal Mobile Telecommunications System
- Evolved 3GPP Packet Switched Domain also known as the Evolved Packet System (EPS).
- EPS Evolved Packet System
- 3GPP also defines a mobile network as a Public Land Mobile Network (PLMN) that is established and operated by an operator for providing mobile telecommunications services.
- PLMN Public Land Mobile Network
- a UE subscribed to 3GPP services has a Home PLMN (HPLMN) that maintains the subscription data and allowed services and QoS levels.
- HPLMN Home PLMN
- VPLMN visited PLMN
- MN Mobile Node
- the 3GPP specifies two data packet gateways located in the EPC supporting the UE's mobility—Serving Gateway (SGW) and Packet Data Network Gateway (PGW).
- SGW terminates the interface towards the radio access networks, e.g. the UTRAN or the E-UTRAN.
- the PGW performs UE IP address allocation and packet filtering (e.g. deep packet inspection, packet screening) in order to map the UE's traffic to appropriate Quality of Service (QoS) level.
- QoS Quality of Service
- the PGW performs the function of a home agent (HA), in case of MIPv6 (Mobile IPv6) based mobility management, or the function of a Local Mobility Anchor (LMA), in case Proxy MIPv6 protocols are used for mobility management.
- HA home agent
- MIPv6 Mobile IPv6
- LMA Local Mobility Anchor
- FIG. 1 shows an EPS architecture where the PGW is connected to the 3GPP access networks (independent of the access technology type, i.e. UTRAN, E-UTRAN) via the so-called S5 interface, i.e. to the SGW, and further to the non-3GPP access network via the so-called S2a interface, i.e. to the Access Gateway (AGW) or via the so-called S2b interface, i.e. to the evolved Packet Data Gateway (ePDG). Further, the UE may also to connect to the PGW when attached to the non-3GPP access network using the so-called S2c interface when employing Dual Stack MIPv6 (DSMIPv6).
- DSMIPv6 Dual Stack MIPv6
- the UE When the UE is attached to the 3GPP access network, the UE is connected to the eNode B (NB) or to the evolved Node B (eNode B) that terminates the air interface.
- the eNode B is connected to the SGW via the S1-U interface (i.e. the user interface for user plane data).
- the S5 interface between the SGW and the PGW can be based either on the GPRS Tunneling Protocol (GTP) or the Proxy MIPv6 (PMIPv6) protocol.
- GTP GPRS Tunneling Protocol
- PMIPv6 Proxy MIPv6
- the S1-U interface is based on the GTP protocol according to the current 3GPP specifications.
- the S2a, respectively S2b interface between the AGW, respectively ePDG and the PGW is based on the PMIPv6 protocol.
- the mobile network i.e. the EPS
- PDN packet data network
- PDN Connectivity Service the data flow between the UE and the PGW is usually referred to as a PDN connection.
- PDN connection For each PDN connection the UE has a different IP configuration, i.e. a different IPv4 address and/or an IPv6 prefix.
- a PDN connection between the UE and the PGW is represented by an Access Point Name (APN).
- APN Access Point Name
- the UE When the UE requests connectivity during the attach procedure to 3GPP access network, the UE usually indicates the APN to the Mobility Management Entity (MME) in the 3GPP access network or to the AGW/ePDG in the non-3GPP access network (see FIG. 1 ).
- MME Mobility Management Entity
- the MME (or correspondingly the AGW/ePDG) chooses a proper PGW of the EPS, which can provide connectivity to the desired APN.
- the UE In case of using DSMIPv6 between the UE, and when the PGW is used for mobility management, the UE itself can choose the PGW.
- the PDN connectivity service is provided by a so-called EPS bearer.
- a UE may run multiple applications, such as VoID call and FTP download simultaneously. Each application could have different QoS requirements, i.e. different QoS parameters like packet delay and/or packet delay jitter, packet loss rate, guaranteed bit rate, etc.
- the 3GPP defines that different EPS bearers meet the different QoS requirements of each different application.
- An EPS bearer uniquely identifies traffic flows that receive a common QoS treatment between a UE and a PGW.
- There could be multiple applications with different QoS requirements to the same PDN i.e. to the same PDN connection, or just one application per PDN connection. So to say, a PDN connection is provided by one or more EPS bearers to the UE.
- one EPS bearer is established and remains established throughout the lifetime of the PDN connection to provide the UE with always-on IP connectivity to that PDN.
- This one bearer is referred to as the “default bearer”.
- a default EPS bearer context is activated, when the UE requests a PDN connection, i.e. a new default EPS bearer is set up for every new PDN connection.
- a dedicated EPS bearer context is always linked to a default EPS bearer context and represents additional EPS bearer resources between the UE and the PDN.
- the decision to establish or modify a dedicated bearer can only be taken by the EPC, and the bearer level QoS parameter values are always assigned by the EPC. Therefore, the MME shall not modify the bearer level QoS parameter values received on the S11 reference point during establishment or modification of a dedicated bearer.
- the SGW informs the MME via the S11 interface about the setup of a dedicated bearer with the corresponding QoS parameters and QoS Class Identifier (QCI) level.
- the MME triggers the eNode B to establish the corresponding 51 bearer (between eNode B and the SGW) and radio bearer (between eNode B and UE on the air interface).
- the UE can have maximum 8 user plane EPS bearers simultaneously, independent of the number of PDN connections.
- Several applications can be mapped onto one EPS bearer.
- Each bearer has an associated QCI.
- Each QCI is characterized by priority, packet delay budget and acceptable packet loss rate.
- the data traffic mapped to the same EPS bearer receive the same packet forwarding treatment (e.g. scheduling policy, queue management policy, rate shaping policy, RLC configuration, etc.).
- a limited number of QCIs have been standardized so that vendors can all have the same understanding of the underlying service characteristics and thus provide the corresponding forwarding treatment.
- the S5 interlace can be based either on GTP or on PMIPv6 protocol.
- the EPS bearer consists of a concatenation of S5 bearer (PGWSGW), S1 bearer (SGWeNode B)—strictly speaking, a S1-U bearer for the user plane traffic—and a radio bearer (eNode BUE).
- An S5 bearer transports the packets of an EPS bearer between a PGW and a SGW.
- the SGW stores a one-to-one mapping between an S1 bearer and an S5 bearer.
- the bearer is identified in the corresponding gateway by the GTP tunnel endpoint ID (TEM) across both interfaces, i.e.
- TEM GTP tunnel endpoint ID
- the SGW identifies the S1 bearer by the GTP-TEID (also: S1-TEID) used for the S1 interface and the SGW identifies the S5 bearer by the GTP-TEID (also: S5-TEID) used for the S5 interface.
- An S1 bearer transports the packets of an EPS bearer between the SGW and an eNode B.
- a radio bearer transports the packets of an EPS bearer between a UE and an eNodeB.
- the EPS bearer is a concatenation of IP connectivity between PGW and SGW, one S1 bearer and one radio bearer.
- the EPS bearer is no “S5 bearer”, but IP connectivity between the PGW and the SGW is provided.
- Deleted means that the resources reserved for the EPS bearers are released (where applicable) and the bearers' context information are deleted in UE, eNode B, MME and SGW.
- the UE When the UE hands over from non-3GPP to the 3GPP access, the UE initiates handover attach procedure.
- the MME keeps the security context in the DEREGISTERED state.
- the security context contains the security related information of the UE obtained from the UE's Home Subscriber Server (HSS) or the AAA server.
- HSS Home Subscriber Server
- the availability of the security context in the MME avoids the repeated interaction between the MME and the HSS for the UE's authentication during the attach procedure. For example, in a handover attach procedure to 3GPP netowks, the MME first initiates the establishment of the S5 bearer between the SGW and the PGW.
- the MME instructs the eNode B to start the establishment of the radio bearer and S1 bearer.
- the complete handover attach procedure takes a long time.
- the handover from non-3GPP to 3GPP access may happen abrupt, because a non-3GPP access like WLAN has small cell coverage and the handover to the 3GPP access may not be predicted.
- FIG. 2 is a schematic block diagram of an example node/device 200 that may be used with one or more embodiments described herein, e.g., as any of the gateway devices, servers, network devices, etc., shown in communication network 100 .
- Device 200 can also be used as a passive network monitoring device, as discussed with respect to FIG. 3 below.
- the device 200 may comprise one or more network interfaces 210 , at least one processor 220 (e.g., a microcontroller), and a memory 240 interconnected by a system bus 250 .
- processor 220 e.g., a microcontroller
- the network interface(s) 210 contain the mechanical, electrical, and signaling circuitry for communicating data over physical and/or wireless links coupled to the network 100 .
- the network interfaces may be configured to transmit and/or receive data using a variety of different communication protocols, including, inter alia, TCP/IP, UDP, wireless protocols (e.g., IEEE Std. 802.15.4, WiFi, Bluetooth®), Ethernet, powerline communication (PLC) protocols, etc.
- the memory 240 comprises a plurality of storage locations that are addressable by the processor 220 and the network interfaces 210 for storing software programs and data structures associated with the embodiments described herein. As noted above, certain devices may have limited memory or no memory (e.g., no memory for storage other than for programs/processes operating on the device).
- the processor 220 may comprise necessary elements or logic adapted to execute the software programs and manipulate data structures 245 , such as routes or prefixes (notably on capable devices only).
- An operating system 242 portions of which are typically resident in memory 240 and executed by the processor, functionally organizes the device by, inter alia, invoking operations in support of software processes and/or services executing on the device.
- These software processes and/or services may comprise passive network monitoring process/services 244 . It will be apparent to those skilled in the art that other processor and memory types, including various computer-readable media, may be used to store and execute program instructions pertaining to the techniques described herein. Also, while the description illustrates various processes, it is expressly contemplated that various processes may be embodied as modules configured to operate in accordance with the techniques herein (e.g., according to the functionality of a similar process).
- Passive network monitoring process (services) 244 contains computer executable instructions executed by the processor 220 to perform functions such as packet monitoring (e.g., packet sniffing, decoding packets, analyzing contents, subscriber mapping/correlation, etc.).
- packet monitoring e.g., packet sniffing, decoding packets, analyzing contents, subscriber mapping/correlation, etc.
- the techniques described herein may be performed by hardware, software, and/or firmware, such as in accordance with the routing process 244 , which may contain computer executable instructions executed by the processor 220 (or independent processor of interfaces 210 ) to perform functions relating to the techniques described herein, e.g., in conjunction with passive network monitoring process 244 .
- this disclosure provides systems and methods that correlate handovers for subscribers between 3GPP networks and untrusted non-3GPP networks.
- the invention provides seamless tracking for subscribers' User Equipment (UE) across the various networks and correlates network connections established prior to a handover as well as post-handover.
- UE User Equipment
- FIG. 3 illustrates an example view of a communication network showing transition of UE between 3GPP network access and untrusted non-3GPP network access.
- FIG. 3 also provides a passive network monitoring system 305 , which (as discussed above) can include one or more network nodes 200 (ref. FIG. 2 ).
- UE transitions between 3GPP access (e.g., via eNB) and untrusted 3GPP access (e.g., Internet Protocol (IP) based access, etc.).
- 3GPP access e.g., via eNB
- IP Internet Protocol
- transition signaling e.g., via attach requests, attach responses, etc.
- the various network nodes e.g., SGW, PGW, PCRF, and ePDG, etc.
- passive network monitoring system 305 monitors communications lines including a S5/S8 network interface (e.g., between the SGW node and PGW node), a S7/Gx network interface (e.g., between the PCRF node and the PGW node), and a S2b network interface (e.g., between the ePDG node and the PGW node).
- Network monitoring system 305 is shown as a single system and may comprise one or more devices (i.e., network device 200 discussed above).
- FIG. 4 illustrates an example signal diagram 400 showing communications between the various network nodes shown in FIG. 3 , particularly from the perspective of UE transfer or transition from untrusted non-3GPP network access to 3GPP network access.
- the UE detects EUTRAN radio access (e.g., eNB) (e.g., via the LTE-Uu network interface) and determines to transfer its current sessions to EUTRAN.
- EUTRAN radio access e.g., eNB
- the UE sends an “attach request” including a handover indication to the eNB via the S1U network interface.
- the attach request also includes any one of the access point names (APNs) that it was previously connected to.
- the UE may be connected to several packet data networks (PDNs) during untrusted non-3GPP network access.
- PDNs packet data networks
- the SGW node sends the create session request with a handover indication flag set to true to the PGW node (e.g., via the S5 network interface).
- passive network monitoring system 305 receives the handover indication flag, which can be used to infer that the S5 network interface session is not a new allocation, but instead, refers to a handover from untrusted non-3GPP network access.
- the PGW node since the handover flag is set, the PGW node does not allocate any new MSIP addresses or default bearers to the PDN connection. Instead, the PGW node executes a PCEF-Initiated IP CAN Session Modification procedure with the PCRF node (e.g., via the Gx network interface).
- the passive network monitoring system 305 From this procedure, all active sessions the UE established in the untrusted non-3GPP network access are observed by the passive network monitoring system 305 . For example, as shown, this includes any MSIP address (e.g., located in the PDN Address Allocation (PAA) field of the create session response) allocated for a particular APN.
- the PGW node Next, the PGW node generates a create session response that contains a same charging identification (ID) previously assigned to the untrusted non-3GPP network access for the UE.
- ID charging identification
- the passive network monitoring system 305 passively monitors communication (e.g., data packets) amongst the various network nodes and correlates the UE to a subscriber based on a combination of the handover flag from the create session request on the S5 network interface, the MSIP of the create session response on the S5 network interface, and the charging ID in the create session response(s) of the S5/S8, S2b and the Gx network interfaces. In this fashion, the passive network monitoring system 305 can maintain context information for the UE and further correlate the UE to a single subscriber across the network handover interfaces.
- communication e.g., data packets
- FIG. 5 illustrates an example signal diagram 500 showing communications between the various network nodes shown in FIG. 3 , particularly from the perspective of UE transfer or transition from 3GPP network access to untrusted non-3GPP network access.
- FIG. 5 shows UE transfer to non-3GPP network access (e.g., via the ePDG node).
- the UE sends an attach request with a handover indication to the ePDG node (e.g., via the Wn interface).
- Such handover indication can indicate a preserve session flag thereby maintaining a same MSIP previously assigned for 3GPP access.
- the ePDG node similar to the SGW node of FIG. 4 , receives the attach request and sends a create session request with the handover indication flag with or without the preserve session flag to the PGW node (e.g., via the S2b network interface).
- the PGW node does not allocate any new MSIP address or default bearers since the handover indication included the preserve session flag from the UE.
- the PGW node resolves this handover via the PCEF-Initiated IP CAN session modification procedure, as discussed above.
- the PCEF-Initiated IP CAN Session all active sessions the UE established for 3GPP access are observed by the passive network monitoring system 305 . As shown, this includes any MSIP address (e.g., located in the PDN Address Allocation (PAA) field of the create session response) allocated for a particular APN.
- PAA PDN Address Allocation
- the PGW node generates a create session response that contains a same charging identification (ID) previously assigned to the untrusted non-3GPP network access for the UE.
- ID charging identification
- the PGW since the preserve session flag was provided in the handover indication in the attach request, the PGW includes the same MSIP address previously allocated to the UE and additionally, the same charging ID previously assigned to the default bearer of the PDN connection as in 3GPP access. However, if the UE does not indicate a preserve session flag, the PGW node proceeds with a new session allocation.
- Passive network monitoring system 305 passively monitors the communication (e.g., data packets) for transitions from 3GPP network access to untrusted non-3GPP network access correlates the UE to a subscriber based on a combination of the handover flag from the create session request on the S2b network interface, the MSIP of the create session response on the S2b network interface, and the charging ID in the create session response(s) of the S2b and the Gx network interfaces. In this fashion, the passive network monitoring system 305 can maintain context information for the UE and further correlate the UE to a single subscriber across the network handover interfaces.
- the communication e.g., data packets
- FIGS. 6-7 collectively illustrate simplified procedures 600 and 700 , respectively, for correlating UE handovers between 3GPP network access and untrusted non-3GPP network access, in accordance with one or more embodiments described herein.
- the procedure 600 of FIG. 6 illustrates correlating a handover for UE from untrusted non-3GPP network access to 3GPP network access.
- the procedure 600 starts at step 605 , and continues to step 610 , where, as described in greater detail above, a passive network monitoring device (i.e., passive network monitoring system 305 ) monitors one or more network interfaces between network nodes.
- the passive network monitoring device monitors the network interfaces between a serving gateway (SGW) node, an evolved packet data gateway (ePDG) node, a policy and charging enforcement function (PCEF) node, etc.
- SGW serving gateway
- ePDG evolved packet data gateway
- PCEF policy and charging enforcement function
- the passive network monitoring device receives a handover indication (e.g., via an attach request, via network interfaces between the SGW node and the PGW node, etc.) for User Equipment (UE) transitioning from untrusted non-3GPP network access to 3GPP network access.
- UE User Equipment
- the passive network monitoring device receives a response (e.g., a create session response) to the attach request from one or more of the network interfaces.
- the response includes a mobile service internet protocol (MSIP) address, which is typically in the PAA field and a charging identification (ID) for the UE.
- MSIP mobile service internet protocol
- ID charging identification
- the passive network monitoring device determines the UE is from a single subscriber and, in step 630 , further correlates information (e.g., mapping data bearer context information) for the UE at each of the one or more network interfaces with the single subscriber.
- Procedure 600 may subsequently end in step 635 , or can continue to step 610 , where the passive network monitoring device monitors one or more network interfaces, discussed above.
- Procedure 700 shown in FIG. 7 , particularly illustrates correlating a handover for UE from 3GPP network access to untrusted non-3GPP network access.
- Procedure 700 starts at step 705 and continues to step 710 where, like step 610 in procedure 600 , the passive network monitoring node monitors one or more network interfaces between network nodes that include a serving gateway (SGW) node, a packet data network (PGW) node, an evolved packet data gateway (ePDG) node.
- SGW serving gateway
- PGW packet data network
- ePDG evolved packet data gateway
- the passive network monitoring device receives, in step 715 a handover indication (e.g., a preserve session continuity, etc.) for the UE transitioning from 3GPP network access to untrusted non-3GPP network access.
- a handover indication e.g., a preserve session continuity, etc.
- the passive network monitoring device receives a response to an attach request from one or more of the network interfaces.
- the attach request includes a mobile service internet protocol (MSIP) and a charging ID for the UE.
- MSIP mobile service internet protocol
- the passive network monitoring device determines the UE is from a single subscriber in step 725 .
- the passive network monitoring device correlates information (data bearers, context information, etc.) for the UE at each of the network interfaces with the single subscriber.
- procedure 700 may end in step 740 , or may continue to step 710 where the passive network monitoring device monitors one or more network interfaces, discussed above.
- procedures 600 - 700 may be optional as described above, the steps shown in FIGS. 6-7 are merely examples for illustration, and certain other steps may be included or excluded as desired. Further, while a particular order of the steps is shown, this ordering is merely illustrative, and any suitable arrangement of the steps may be utilized without departing from the scope of the embodiments herein. Moreover, while procedures 600 - 700 are described separately, certain steps from each procedure may be incorporated into each other procedure, and the procedures are not meant to be mutually exclusive.
- the techniques described herein therefore, provide for correlating subscribers to User Equipment during handover between 3GPP network access and untrusted non-3GPP network access.
- the techniques herein map packet data network connections, default bearers, context information, etc., for User Equipment during handovers between different types of network access. Such information is useful, for example, when determining key performance indicators (KPIs).
- KPIs key performance indicators
- using these techniques subscribers can be seamlessly tracked across network access technologies, which can provide additional metrics to measure quality of service (QoS) and other network performance criteria.
- QoS quality of service
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (18)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/133,254 US9191872B2 (en) | 2013-12-18 | 2013-12-18 | System and method to correlate handover transitions between 3GPP network access and untrusted non-3GPP network access |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/133,254 US9191872B2 (en) | 2013-12-18 | 2013-12-18 | System and method to correlate handover transitions between 3GPP network access and untrusted non-3GPP network access |
Publications (2)
Publication Number | Publication Date |
---|---|
US20150172981A1 US20150172981A1 (en) | 2015-06-18 |
US9191872B2 true US9191872B2 (en) | 2015-11-17 |
Family
ID=53370173
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/133,254 Active 2034-05-23 US9191872B2 (en) | 2013-12-18 | 2013-12-18 | System and method to correlate handover transitions between 3GPP network access and untrusted non-3GPP network access |
Country Status (1)
Country | Link |
---|---|
US (1) | US9191872B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160157159A1 (en) * | 2014-12-01 | 2016-06-02 | Verizon Patent And Licensing Inc. | Non-invasive differentiated wireless transmission detection |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10917787B2 (en) * | 2013-12-20 | 2021-02-09 | Mcafee, Llc | Security gateway for a regional/home network |
US9179436B1 (en) | 2014-08-22 | 2015-11-03 | Cisco Technology, Inc. | System and method for location reporting in an untrusted network environment |
US9986478B2 (en) * | 2014-09-15 | 2018-05-29 | Apple Inc. | Enhanced Wi-Fi-cellular mobility |
JP6745346B2 (en) * | 2016-03-29 | 2020-08-26 | オッポ広東移動通信有限公司Guangdong Oppo Mobile Telecommunications Corp., Ltd. | Wireless communication method and apparatus |
KR102606289B1 (en) | 2017-08-09 | 2023-11-24 | 삼성전자주식회사 | Method and system for handling registration and session management in a wireless communication system |
CN109743789B (en) * | 2018-11-22 | 2021-04-09 | 京信通信系统(中国)有限公司 | Method and device for clearing residual session of Gx interface |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20080305799A1 (en) * | 2007-06-06 | 2008-12-11 | Interdigital Technology Corporation | Heterogeneous network handover-support mechanism |
US20080316972A1 (en) * | 2007-06-22 | 2008-12-25 | Interdigital Technology Corporation | Resource management for mobility between different wireless communications architectures |
US20100040024A1 (en) * | 2007-05-11 | 2010-02-18 | Huawei Technologies Co., Ltd. | Method, system, and apparatus for registration processing |
US20100150046A1 (en) * | 2007-08-20 | 2010-06-17 | Huawei Technologies Co., Ltd. | Charging method and network system thereof, packet data network gateway and charging system thereof |
US20100323700A1 (en) * | 2008-01-09 | 2010-12-23 | Panasonic Corporation | Non-3gpp to 3gpp network handover optimizations |
US20110138447A1 (en) * | 2008-05-05 | 2011-06-09 | Datang Mobile Communications Equipment Co., Ltd. | Method, System and Device for Obtaining a Trust Type of a Non-3GPP Access System |
-
2013
- 2013-12-18 US US14/133,254 patent/US9191872B2/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100040024A1 (en) * | 2007-05-11 | 2010-02-18 | Huawei Technologies Co., Ltd. | Method, system, and apparatus for registration processing |
US20080305799A1 (en) * | 2007-06-06 | 2008-12-11 | Interdigital Technology Corporation | Heterogeneous network handover-support mechanism |
US20080316972A1 (en) * | 2007-06-22 | 2008-12-25 | Interdigital Technology Corporation | Resource management for mobility between different wireless communications architectures |
US20100150046A1 (en) * | 2007-08-20 | 2010-06-17 | Huawei Technologies Co., Ltd. | Charging method and network system thereof, packet data network gateway and charging system thereof |
US20100323700A1 (en) * | 2008-01-09 | 2010-12-23 | Panasonic Corporation | Non-3gpp to 3gpp network handover optimizations |
US20110138447A1 (en) * | 2008-05-05 | 2011-06-09 | Datang Mobile Communications Equipment Co., Ltd. | Method, System and Device for Obtaining a Trust Type of a Non-3GPP Access System |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160157159A1 (en) * | 2014-12-01 | 2016-06-02 | Verizon Patent And Licensing Inc. | Non-invasive differentiated wireless transmission detection |
US9699709B2 (en) * | 2014-12-01 | 2017-07-04 | Verizon Patent And Licensing Inc. | Non-invasive differentiated wireless transmission detection |
Also Published As
Publication number | Publication date |
---|---|
US20150172981A1 (en) | 2015-06-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11432202B2 (en) | Monitoring and reporting service performance in roaming scenario | |
CA3030741C (en) | Method for processing pdu session establishment procedure and amf node | |
US9191872B2 (en) | System and method to correlate handover transitions between 3GPP network access and untrusted non-3GPP network access | |
US10064120B2 (en) | Method and nodes for handling a UE which roams into a visited network | |
EP3211938B1 (en) | System and method to prevent packet loss during handover | |
TWI472210B (en) | Method of ip flow mobility | |
US9380446B2 (en) | Policy and charging control method supporting IP flow mobility in roaming scenario | |
US20120269167A1 (en) | Enhanced attachment procedure for attaching a ue to a 3gpp access network | |
US20080320149A1 (en) | Service request device wireless access detach and bearer deactivation methods withou loss of internet protocol connectivity | |
US10342054B2 (en) | IP address assignment for a UE in 3GPP | |
EP2945317B1 (en) | Selective real-time gtp session tracking using distributed processing techniques | |
US20190364458A1 (en) | User equipment maximum bandwidth control method and device, computer storage medium | |
US20140169332A1 (en) | Method for supporting selection of pdn connections for a mobile terminal and mobile terminal | |
JP2017526242A (en) | Network-based flow mobility for multi-connectivity devices | |
KR20180039090A (en) | A terminal device, a base station device, a communication control method of a terminal device, and a communication control method of a base station device | |
JP6515247B2 (en) | Method and node for handling network connection | |
KR102477066B1 (en) | Terminal device, AMF, SMF, core network device, and communication control method | |
WO2019031433A1 (en) | Terminal device, device in core network, and communication control method | |
US20150304908A1 (en) | Method, apparatus, and system for selecting pdn gateway | |
WO2019031434A1 (en) | Terminal device, device in core network, and communication control method | |
WO2012090401A1 (en) | Method for ip-based flow mobility and associated apparatus thereof | |
AU2019274046A1 (en) | User equipment, control apparatus, and communication control method | |
US20130242918A1 (en) | Method for providing a local traffic shortcut in a packet-oriented mobile communication network | |
WO2015018324A1 (en) | Method and device for realizing ip flow mobility in multi-access system | |
JP6698618B2 (en) | UE and UE communication control method |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TEKTRONIX, INC., OREGON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:JANAKIRAMAN, VIGNESH, MR.;REEL/FRAME:032147/0573 Effective date: 20131218 |
|
AS | Assignment |
Owner name: TEKTRONIX TEXAS, LLC, MASSACHUSETTS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:TEKTRONIX, INC.;REEL/FRAME:036355/0563 Effective date: 20150813 Owner name: JPMORGAN CHASE BANK, N.A., NEW YORK Free format text: SECURITY INTEREST;ASSIGNOR:NETSCOUT SYSTEMS, INC.;REEL/FRAME:036355/0586 Effective date: 20150714 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: NETSCOUT SYSTEMS TEXAS, LLC, MASSACHUSETTS Free format text: CHANGE OF NAME;ASSIGNOR:TEKTRONIX TEXAS, LLC;REEL/FRAME:039665/0256 Effective date: 20160627 |
|
AS | Assignment |
Owner name: NETSCOUT SYSTEMS TEXAS, LLC, MASSACHUSETTS Free format text: CHANGE OF NAME;ASSIGNOR:TEKTRONIX TEXAS, LLC;REEL/FRAME:039919/0208 Effective date: 20160819 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |