Management techniques for wireless network mobility procedures

• US 9,826,390 B2
• Filed: 03/27/2014
• Issued: 11/21/2017
• Est. Priority Date: 03/29/2013
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: Stojanovski, Alexandre S., Sirotkin, Sasha
• Primary Examiner(s): Pham, Chi H
• Assistant Examiner(s): HOM, SHICK C
• Application Number:
  US14/411,498
• Publication Number:
  US 20150146532A1
• Time in Patent Office: 1,335 Days
• Field of Search: None
• CPC Class Codes: H04B 1/56 with provision for simultaneous communication in two directions
• CPC Class Codes: H04B 7/0417 Feedback systems
• CPC Class Codes: H04B 7/0452 Multi-user MIMO systems
• CPC Class Codes: H04B 7/0617 for beam forming
• CPC Class Codes: H04B 7/0619 using feedback from receiving side feedback signaling for adaptive modulation/coding H04L1/0001
• CPC Class Codes: H04B 7/063 Parameters other than those covered in groups H04B7/0623 - H04B7/0634, e.g. channel matrix rank or transmit mode selection
• CPC Class Codes: H04B 7/0695 using beam selection
• CPC Class Codes: H04B 7/088 using beam selection
• CPC Class Codes: H04L 1/1864 ARQ related signaling H04L1/1607 takes precedence
• CPC Class Codes: H04L 2025/03426 transmission using multiple-input and multiple-output channels
• CPC Class Codes: H04L 25/0204 of multiple channels
• CPC Class Codes: H04L 25/03305 Joint sequence estimation and interference removal joint detection of several desired signals H04L25/03331
• CPC Class Codes: H04L 47/803 Application aware
• CPC Class Codes: H04L 47/83 based on usage prediction
• CPC Class Codes: H04L 5/0007 the frequencies being orthogonal, e.g. OFDM(A), DMT
• CPC Class Codes: H04L 5/0048 Allocation of pilot signals, i.e. of signals known to the receiver
• CPC Class Codes: H04L 5/0051 of dedicated pilots, i.e. pilots destined for a single user or terminal
• CPC Class Codes: H04L 5/0053 Allocation of signaling, i.e. of overhead other than pilot signals
• CPC Class Codes: H04L 5/0055 Physical resource allocation for ACK/NACK for physical mapping arrangements in ARQ protocols H04L1/1861
• CPC Class Codes: H04L 5/0057 Physical resource allocation for CQI
• CPC Class Codes: H04L 5/0085 : when channel conditions change
• CPC Class Codes: H04L 5/1469 : using time-sharing
• CPC Class Codes: H04L 65/613 : for the control of the source by the destination control signals issued by the client directed to the server or network components specially adapted for selective content distribution H04N21/637
• CPC Class Codes: H04L 65/65 : Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 65/70 : Media network packetisation
• CPC Class Codes: H04L 65/75 : Media network packet handling
• CPC Class Codes: H04L 65/752 : adapting media to network capabilities
• CPC Class Codes: H04L 65/756 : adapting media to device capabilities
• CPC Class Codes: H04L 65/762 : at the source reformatting of additional data in video distribution servers H04N21/2355
• CPC Class Codes: H04L 65/764 : at the destination reformatting of additional data in video clients H04N21/4355
• CPC Class Codes: H04L 65/80 : Responding to QoS
• CPC Class Codes: H04M 1/72457 : according to geographic location
• CPC Class Codes: H04N 21/2402 : Monitoring of the downstream path of the transmission network, e.g. bandwidth available traffic monitoring in data switching networks H04L43/00; monitoring data switching networks utilization H04L43/0876
• CPC Class Codes: H04N 21/8456 : by decomposing the content in the time domain, e.g. in time segments
• CPC Class Codes: H04N 21/8543 : using a description language, e.g. Multimedia and Hypermedia information coding Expert Group [MHEG], eXtensible Markup Language [XML] information retrieval of semistructured data, the underlying structure being taken into account, e.g. mark-up language structure data G06F16/80
• CPC Class Codes: H04W 24/00 : Supervisory, monitoring or testing arrangements
• CPC Class Codes: H04W 24/02 : Arrangements for optimising operational condition
• CPC Class Codes: H04W 28/02 : Traffic management, e.g. flow control or congestion control
• CPC Class Codes: H04W 28/0226 : based on location or mobility handoff or reselection H04W36/00; mobile application services making use of the location of users or terminals H04W4/02
• CPC Class Codes: H04W 28/0289 : Congestion control load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 28/082 : among bearers or channels
• CPC Class Codes: H04W 28/20 : Negotiating bandwidth
• CPC Class Codes: H04W 36/0011 : for data sessions of end-to-end connection
• CPC Class Codes: H04W 36/0022 : for transferring data sessions between adjacent core network technologies
• CPC Class Codes: H04W 36/0072 : of resource information of target access point
• CPC Class Codes: H04W 36/08 : Reselecting an access point
• CPC Class Codes: H04W 36/125 : involving different types of service backbones
• CPC Class Codes: H04W 36/22 : for handling the traffic
• CPC Class Codes: H04W 36/26 : by agreed or negotiated communication parameters
• CPC Class Codes: H04W 4/021 : Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 48/06 : based on traffic conditions
• CPC Class Codes: H04W 48/12 : using downlink control channel
• CPC Class Codes: H04W 48/16 : Discovering, processing access restriction or access information
• CPC Class Codes: H04W 48/18 : Selecting a network or a communication service
• CPC Class Codes: H04W 56/001 : Synchronization between nodes
• CPC Class Codes: H04W 72/0446 : Resources in time domain, e.g. slots or frames
• CPC Class Codes: H04W 72/046 : the resource being in the space domain, e.g. beams
• CPC Class Codes: H04W 72/541 : using the level of interference
• CPC Class Codes: H04W 76/15 : Setup of multiple wireless link connections
• CPC Class Codes: H04W 8/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
• CPC Class Codes: H04W 8/06 : Registration at serving network Location Register, VLR or user mobility server
• CPC Class Codes: H04W 8/082 : for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
• CPC Class Codes: H04W 84/042 : Public Land Mobile systems, e.g. cellular systems
• CPC Class Codes: H04W 84/045 : using private Base Stations, e.g. femto Base Stations, home Node B
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: H04W 88/08 : Access point devices
• CPC Class Codes: H04W 88/10 : adapted for operation in multiple networks, e.g. multi-mode access points
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Connection management techniques for wireless network mobility procedures are described. In one embodiment, for example, an evolved packet core (EPC) node may comprise a processor circuit to receive a notification of a mobility procedure for a user equipment (UE), determine whether to release a local gateway (L-GW)-provided packet data network (PDN) connection of the UE, and in response to a determination that the L-GW-provided PDN connection is to be released, send either a detach request message or a delete session request message to initiate a process for releasing the L-GW-provided PDN connection. Other embodiments are described and claimed.

Claims

1. A mobility management entity (MME), comprising:

a memory; and

logic, at least a portion of which is implemented in circuitry coupled to the memory, the logic to receive a forward relocation request during a handover procedure for a user equipment (UE), determine, based on the forward relocation request, whether a local home network of the UE changes, determine whether to maintain a selected internet protocol traffic offload at local network (SIPTO@LN) packet data network (PDN) connection of the UE following the handover procedure based on whether the local home network of the UE changes, and maintain the SIPTO@LN PDN connection in response to a determination that the local home network of the UE does not change.

2. The MME of claim 1, the logic to determine whether the local home network of the UE changes according to the handover procedure based on a local home network identifier (ID) comprised in the forward relocation request.

3. The MME of claim 1, the logic to initiate a procedure to release the SIPTO@LN PDN connection in response to a determination that the local home network of the UE changes, the logic to select the procedure based on a determination of whether the SIPTO@LN PDN connection comprises an only PDN connection of the UE.

4. The MME of claim 3, the logic to initiate an MME-requested PDN disconnection procedure to release the SIPTO@LN PDN connection in response to a determination that the SIPTO@LN PDN connection does not comprise the only PDN connection of the UE.

5. The MME of claim 4, the logic to send a delete session request to initiate the MME-requested PDN disconnection procedure.

6. The MME of claim 5, the logic to send the delete session request with a reactivation requested cause.

7. The MME of claim 3, the logic to initiate an MME-initiated detach procedure to release the SIPTO@LN PDN connection in response to a determination that the SIPTO@LN PDN connection comprises the only PDN connection of the UE.

8. A mobility management entity (MME), comprising:

a memory; and

logic, at least a portion of which is implemented in circuitry coupled to the memory, the logic to;

determine whether to release a selected internet protocol traffic offload at local network (SIPTO@LN) packet data network (PDN) connection of a user equipment (UE) following a tracking area update (TAU) procedure for the UE based on a local home network identifier (ID) comprised in a received context response message, the SIPTO@LN PDN connection to comprise a connection to a packet data network through a stand-alone gateway (GW); and

in response to a determination to release the SIPTO@LN PDN connection;

determine whether SIPTO@LN PDN connection comprises an only PDN connection of the UE; and

initiate an MME-initiated detach procedure to release the SIPTO@LN connection in response to a determination that the SIPTO@LN PDN connection comprises the only PDN connection of the UE.

9. The MME of claim 8, the logic to determine, based on the local home network ID, whether a local home network of the UE changes, and determine whether to release the SIPTO@LN PDN connection based on whether the local home network of the UE changes.

10. The MME of claim 9, the logic to determine not to release the SIPTO@LN PDN connection in response to a determination that the local home network of the UE does not change.

11. The MME of claim 9, the logic to determine to release the SIPTO@LN PDN connection in response to a determination that the local home network of the UE changes.

12. The MME of claim 8, the logic to send a detach request to initiate the MME-initiated detach procedure.

13. At least one non-transitory computer-readable storage medium comprising a set of instructions that, in response to being executed at a mobility management entity (MME), cause the MME to:

receive a forward relocation request message during a handover of a user equipment (UE);

determine whether to release a selected internet protocol traffic offload at local network (SIPTO@LN) packet data network (PDN) connection of the UE following the handover based on the forward relocation request message, the SIPTO@LN PDN connection to comprise a connection with a packet data network through a stand-alone gateway (GW); and

in response to a determination to release the SIPTO@LN PDN connection, select a procedure for releasing the SIPTO@LN PDN connection based on whether the SIPTO@LN PDN connection comprises an only PDN connection of the UE.

14. The at least one non-transitory computer-readable storage medium of claim 13, comprising instructions that, in response to being executed at the MME, cause the MME to:

determine whether a local home network of the UE changes as a result of the handover based on the forward relocation request message; and

determine whether to release the SIPTO@LN PDN connection following the handover based on whether the local home network of the UE changes as a result of the handover.

15. The at least one non-transitory computer-readable storage medium of claim 14, comprising instructions that, in response to being executed at the MME, cause the MME to determine whether the local home network of the UE changes as a result of the handover based on a local home network identifier (ID) comprised in the forward relocation request message.

16. The at least one non-transitory computer-readable storage medium of claim 14, comprising instructions that, in response to being executed at the MME, cause the MME to determine to maintain the SIPTO@LN PDN connection following the handover in response to a determination that the local home network of the UE does not change as a result of the handover.

17. The at least one non-transitory computer-readable storage medium of claim 14, comprising instructions that, in response to being executed at the MME, cause the MME to determine to release the SIPTO@LN PDN connection following the handover in response to a determination that the local home network of the UE changes as a result of the handover.

18. At least one non-transitory computer-readable storage medium comprising a set of instructions that, in response to being executed at a mobility management entity (MME), cause the MME to:

determine whether to release a selected internet protocol traffic offload at local network (SIPTO@LN) packet data network (PDN) connection of a user equipment (UE) following a tracking area update (TAU) procedure for the UE based on whether a local home network of the UE changes, the SIPTO@LN PDN connection to comprise a connection to a packet data network through a stand-alone gateway (GW); and

in response to a determination to release the SIPTO@LN PDN connection;

determine whether the SIPTO@LN PDN connection comprises an only PDN connection of the UE; and

initiate an MME-requested PDN disconnection procedure to release the SIPTO@LN connection in response to a determination that the SIPTO@LN PDN connection does not comprise the only PDN connection of the UE.

19. The at least one non-transitory computer-readable storage medium of claim 18, comprising instructions that, in response to being executed at the MME, cause the MME to determine whether the local home network of the UE changes based on a local home network identifier (ID) comprised in a received context response message.

20. The at least one non-transitory computer-readable storage medium of claim 18, comprising instructions that, in response to being executed at the MME, cause the MME to determine to release the SIPTO@LN PDN connection in response to a determination that the local home network of the UE changes.

21. The at least one non-transitory computer-readable storage medium of claim 18, comprising instructions that, in response to being executed at the MME, cause the MME to send a delete session request to initiate the MME-requested PDN disconnection procedure.

22. The at least one non-transitory computer-readable storage medium of claim 21, comprising instructions that, in response to being executed at the MME, cause the MME to send the delete session request with a reactivation requested cause.