JP2018530199A - Node and method for managing packet data network connections - Google Patents

Abstract

The exemplary embodiments presented herein are directed to a serving gateway, a core network node and a Policy Control and Charging Rules Function (PCRF) for managing packet data network connections of wireless devices, and corresponding methods in them. To do.
[Selection] Figure 1

Description

  The exemplary embodiments presented herein are directed to a serving gateway, a core network node and a Policy Control and Charging Rules Function (PCRF) for managing packet data network connections of wireless devices, and corresponding methods in them. To do.

  In a typical cellular system, also referred to as a wireless communication network, wireless terminals, also known as mobile stations and / or user equipment units, communicate via a radio access network (RAN) to one or more core networks. A wireless terminal is a user equipment such as a machine-to-machine (M2M) device, an IoT (Internet-of-Things) device, a mobile station, or a mobile phone, also known as a “cellular” phone, or a laptop with wireless capabilities. For example, it can be a portable, pocket-type, handheld, built-in computer or in-vehicle mobile device that communicates voice and / or data with a radio access network.

  The radio access network covers a geographical area that is divided into a plurality of cell areas, each cell area being served by a base station such as a radio base station (RBS). Radio base stations are also referred to as “Node B”, “B Node” or “Extended Node B”, “eNodeB” or “eNB” in some networks, which are also referred to as base stations in this document. A cell is a geographical area where radio coverage is provided by radio base station equipment at a base station site. Each cell is identified by an identity within the local radio area, which is broadcast within the cell. The base station communicates with user equipment units within the range of the base station via an air interface that operates on a radio frequency.

  In some versions of a radio access network, multiple base stations are typically connected to a radio network controller (RNC), for example, by landline or microwave. A radio network controller, sometimes referred to as a base station controller (BSC), oversees and coordinates the various activities of multiple base stations connected to it. The radio network controller is typically connected to one or more core networks.

  UMTS (Universal Mobile Telecommunications System) is a third generation mobile communication system, which has evolved from GSM (Global System for Mobile Communications). UMTS is intended to provide improved mobile communication services based on WCDMA (Wideband Code Division Multiple Access) access technology. UTRAN (UMTS Terrestrial Radio Access Network) is essentially a radio access network that uses WCDMA for user equipment units (UEs). The 3rd Generation Partnership Project (3GPP) has been working on further evolving UTRAN and GSM based radio access network technologies. Long Term Evolution (LTE) along with EPC (Evolved Packet Core) is the latest addition to the 3GPP family.

  There may be moments during the operation of the wireless communication network where the core network node needs to be failed or restarted. Various procedures are in place to keep communication disruption to a minimum during such failures or restarts of the core network node. An example of such a procedure is the Network Triggered Service Restoration procedure as specified in Chapter 25 of 3GPP TS 23.007. In this procedure, a node called a serving gateway (SGW) detects the occurrence of a failure of a mobility management node, which is a mobility management entity (MME) or a serving general packet radio service (GPRS) support node (SGSN), for example. The SGW will be required to maintain the PDN connection. Thereafter, if the SGW receives downlink data for a wireless device, it will issue a downlink data notification with the IMSI of that wireless device associated with the PDN connection.

  However, in a new scheme that has been developed soon, especially for machine-type wireless devices, the wireless device may use enhanced DRX or enter Power Saving Mode, which listens for paging requests. In such cases, paging triggered by reception of downlink data does not make any sense and simply creates extra signaling on the network. Such wireless devices often use a delay-tolerant service, i.e., the service can be delayed until the wireless device is reachable by the network. However, it does not exclude the possibility of using a service that is not delayed-tolerant.

  Moreover, depending on what type of service the wireless device is authorized to use, a means of providing dynamic or updated information regarding the possibility of changing the attribute of the PDN connection being delayed tolerant Currently does not exist.

  In addition, there is currently no specification of how such a delay-tolerant attribute of a PDN connection can affect the management of the PDN connection in the presence of a mobility management node failure or restart.

  Thus, at least one objective of the exemplary embodiment presented here is how a network triggered service recovery procedure is deployed in a communication network where the wireless device may be in enhanced DRX or power saving mode. Whether to provide it effectively. Specifically, the purpose of the exemplary embodiment presented here is for a PDN for a wireless device with a network deployed with a network triggered service recovery procedure in the presence of a mobility management node failure or restart How to manage connections.

  At least one exemplary advantage of the embodiments presented here is that unnecessary signaling is reduced. Based on the ability of the PDN connection associated with the wireless device to receive delayed communications, the PDN connection may or may not be maintained in the presence of a mobility management node failure or restart. Moreover, another exemplary advantage is that changes in delay tolerance, for example due to service or application usage, can be taken into account with respect to management of PDN connections.

  Accordingly, some of the exemplary embodiments are directed to methods in the SGW for managing PDN connections for wireless devices. The SGW is configured to support network triggered service recovery procedures. The method includes receiving, from at least one GTP entity, a delay tolerant connection indicator (DTCI) that indicates whether communications on the identified PDN connection for the wireless device can be delayed. The method further includes storing the DTCI in the SGW. The method also includes managing the PDN connection after detection of a failure (with or without restart) of a mobility management node serving the wireless device. The managing includes deleting the PDN connection when the DTCI indicates that the PDN connection is delay tolerant. Alternatively, the managing further comprises maintaining the PDN connection when the DTCI indicates that the PDN connection is not delay tolerant.

  Some exemplary embodiments are directed to SGWs for managing PDN connections for wireless devices. The SGW is configured to support network triggered service recovery procedures. The SGW includes a processor and a memory. The memory includes instructions executable by the processor so that the SGW can receive a DTCI indicating whether communication on the identified PDN connection for the wireless device can be delayed from at least one GTP entity. Is operable to receive. The SGW is further operable to store the DTCI within the SGW. The SGW is also operable to manage the PDN connection after detection of a failure (with or without restart) of a mobility management node serving the wireless device. Within the management of the PDN connection, the SGW is operable to delete the PDN connection when the DTCI indicates that the PDN connection is delay tolerant. Alternatively, the SGW is operable to maintain the PDN connection if the DTCI indicates that the PDN connection is not delay tolerant.

  Some example embodiments are directed to a method at a core network node for dynamically managing PDN connections for wireless devices. The core network node includes a stored DTCI that indicates whether communication on the identified PDN connection for the wireless device can be delayed. The method includes receiving an updated DTCI from a PCRF or other core network node that indicates an altered status regarding whether the identified PDN connection for the wireless device is delayed tolerant. The method also includes storing the updated DTCI in the core network node.

  Some example embodiments are directed to a core network node for dynamically managing PDN connections for wireless devices. The core network node includes a stored DTCI that indicates whether communication on the identified PDN connection for the wireless device can be delayed. The core network node includes a processor and a memory. The memory includes instructions executable by the processor such that the core network node changes from a PCRF or other core network node as to whether the identified PDN connection for the wireless device is delay tolerant. To receive an updated DTCI that points to The core network node is further operable to store the updated DTCI in the core network node.

  Some example embodiments are directed to methods in a PCRF for dynamically managing PDN connections for wireless devices. The method includes detecting a status change in the delay tolerance of the PDN connection. The status change presents a change as to whether the identified PDN connection for the wireless device can receive delayed communications. The method further includes updating the DTCI based on the detected status change. The method further includes transmitting the updated DTCI to the PGW.

  Some exemplary embodiments are directed to PCRFs for dynamically managing PDN connections for wireless devices. The PCRF includes a processor and a memory. The memory includes instructions executable by the processor so that the PCRF is operable to detect status changes in the delay tolerance of the PDN connection. The status change presents a change as to whether the identified PDN connection for the wireless device can receive delayed communications. The PCRF is further operable to update the DTCI based on the detected status change. The PCRF is also operable to send the updated DTCI to a PDN gateway (PGW).

[Abbreviation]
3GPP Third Generation Partnership Project
AS Application Server
BSC Base Station Controller
DRX Discontinuous Reception
DTCI Delay Tolerance Connection Indicator
E-UTRAN Evolved Universal Terrestrial Radio Access Network
eNodeB Evolved NodeB
EPC Evolved Packet Core
GERAN GSM / EDGE Radio Access Network
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GTP GPRS Tunneling Protocol
GSM Global System for Mobile Communications
HSS Home Subscriber Server
IMSI International Mobile Subscriber Identity
IoT Internet of Things
LTE Long Term Evolution
M2M Machine-to-Machine
MME Mobility Management Entity
PCRF Policy Control and Charging Rules Function
PDN Packet Data Network
PGW PDN Gateway
RAN Radio Access Network
RAU Routing Area Update
RBS Radio Base Station
RNC Radio Network Controller
RRC Radio Resource Control
SGSN Serving GPRS Support Node
SGW Serving Gateway
TAU Tracking Area Update
UE User Equipment
UMTS Universal Mobile Telecommunications System
UTRAN UMTS Terrestrial Radio Access Network
WCDMA Wideband Code Division Multiple Access

  The foregoing will become apparent from the following more specific description of exemplary embodiments, as illustrated in the accompanying drawings. In the accompanying drawings, like reference numerals designate identical parts throughout the different views. The drawings are not necessarily to scale, emphasis instead being placed upon depiction of exemplary embodiments.

It is an explanatory example of a wireless network. FIG. 6 is a message progress diagram depicting management of PDN connections during a mobility procedure that handles SGW relocation, according to some of the exemplary embodiments presented herein. FIG. 4 is a message flow diagram depicting the management of a PDN connection that handles DTCI dynamic updates, according to some of the exemplary embodiments presented herein. 2 is an exemplary node configuration of an SGW, a core network node, and a PCRF, according to some of the exemplary embodiments. FIG. 5 is a flow diagram depicting exemplary operations that may be taken by the SGW, in accordance with some of the exemplary embodiments. FIG. 5B is a module diagram depicting modules configured to perform the operations of FIG. 5A, according to some example embodiments. FIG. 6 is a flow diagram depicting exemplary operations that may be taken by a core network node, according to some of the exemplary embodiments. FIG. 6B is a module diagram depicting modules configured to perform the operations of FIG. 6A, according to some example embodiments. FIG. 6 is a flow diagram depicting exemplary operations that may be taken by a PCRF, in accordance with some of the exemplary embodiments. 7B is a module diagram depicting modules configured to perform the operations of FIG. 7A, according to some example embodiments. FIG.

  In the following description, for purposes of explanation and not limitation, specific details such as specific components, elements, techniques, etc. are set forth in order to provide a thorough understanding of the exemplary embodiments. However, it will be apparent to those skilled in the art that the exemplary embodiments may be practiced in other ways apart from these specific details. In other instances, detailed descriptions of well-known methods and elements are omitted so as not to obscure the description of the exemplary embodiments. The terminology used herein is for the purpose of describing example embodiments and is not intended to limit the embodiments presented herein. It should be understood that all of the exemplary embodiments presented here may be applicable to GERAN, UTRAN or E-UTRAN systems. It should further be understood that the terms wireless device, wireless terminal, M2M device, MTC device, IoT device, and user equipment may be used interchangeably.

[General outline]
The exemplary embodiment presented here is directed to managing PDN connections in a communication network that supports network-triggered service recovery procedures. In order to provide a better description of the exemplary embodiments presented herein, problems will first be identified and discussed.

Communication Network Overview FIG. 1 provides a general example of a communication network 100. As shown in FIG. 1, a user equipment (UE) 101 has a UTRAN (Universal Terrestrial Radio Access Network) 103, an E-UTRAN (Evolved UTRAN) 104 in order to access communication to an operator server or application server 105. Or a communication relationship with a GERAN (GSM Edge Radio Access Network) 102 subsystem. In acquiring access to the SCS, AS, or host 105, the UTRAN / E-UTRAN / GERAN subsystems 102 to 104 communicate with a GPRS (General Packet Radio Service) subsystem 107 or an EPC (Evolved Packet Core) subsystem 109. There can be a relationship. Although not shown in FIG. 1, it should also be understood that the network may further include a WiFi subsystem.

  The GPRS subsystem 107 may include a serving GPRS support node (SGSN) 111, also known as Gn / Gp-SGSN, which is used for data packets to and from mobile stations within the associated geographic service area. Can be responsible for delivery. The SGSN 111 may also be responsible for packet routing, transfer, mobility management and connectivity management. The GPRS subsystem 107 may also include a gateway GPRS support node 113, which may be responsible for interworking between the GPRS subsystem 107 and the PDN 105.

  The EPC subsystem 109 may include a mobility management entity 115, which is mobility management, connectivity management, idle mode UE tracking, paging procedure, attachment and activation procedure, and small for E-UTRAN 104. Responsible for scale data and message transfer. The EPC subsystem may include a serving gateway (SGW) 117, which may be responsible for routing and forwarding data packets. The EPC subsystem may include a packet data network gateway (PGW) 119, which may be responsible for providing connectivity from the user equipment 101 to one or more PDNs 105. Any of the SGSN 111, S4-SGSN 110 and MME 115 may be in communication with a home subscriber server (HSS) 121, which may provide device identification information, IMSI (International Mobile Subscriber Identity), subscriber information, etc. . It should be understood that the EPC subsystem 109 may also include the S4-SGSN 110, thereby allowing access to the GERAN 102 or UTRAN 103 subsystem when the GPRS 107 is replaced with the EPC 109.

  The network further includes a Policy Control and Charging Rules Function (PCRF) 120. The PCRF 120 includes functionality for policy control decisions and flow-based charging control.

Extended idle mode DRX
3GPP has partially completed a new technical study-“Machine-Type and other mobile data applications Communications enhancements”. More precisely, it is part of “UE Power Consumption Optimizations (UEPCOP)”, in which extended DRX for wireless devices in idle mode and power saving mode of wireless devices (Power Saving Mode) are introduced. .

  Wireless devices and networks can use their power consumption over NAS (non-access stratum) signaling for mobile terminated data and / or network-initiated procedures within a certain delay depending on the DRX cycle value. The use of extended idle mode DRX to reduce the may be negotiated.

  Applications desiring to use enhanced idle mode DRX need to consider the inherent handling of mobile termination services or data transfer, and specifically the delay tolerance of mobile termination data. Applications on the network side may send mobile termination data, SMS or device triggers and need to recognize that extended idle mode DRX may be being set up.

  In order to negotiate the use of extended idle mode DRX, the wireless device requests extended idle mode DRX parameters during the attach procedure and the RAU / TAU procedure. The SGSN / MME may reject or accept the wireless device's request to enable enhanced idle mode DRX. In the case where the SGSN / MME accepts the extended idle mode DRX, the SGSN / MME may provide a value for the extended idle mode DRX parameter different from that requested by the UE based on the operator policy. If the SGSN / MME accepts the use of extended idle mode DRX, the wireless device applies extended idle mode DRX based on the received extended idle mode DRX parameters. If the wireless device does not receive the extended idle mode DRX parameters in the accept message involved because the SGSN / MME rejected its request or because the request was received by an SGSN / MME that does not support extended idle mode DRX, TS 23.060 The normal discontinuous reception as defined in section 8.2.3 of the above and chapter 5.13 of TS23.401 shall apply.

If the wireless device requires via NAS to enable both PSM (which requires an active time and possibly a periodic TAU timer) and extended idle mode DRX (with a unique extended I-DRX cycle value) The decision to do the following is left to the SGSN / MME:
1. Enable PSM only, ie do not accept requests for extended idle mode DRX.
2. Only the enhanced idle mode DRX is enabled, i.e. it does not accept requests for active time.
3. Enable both PSM (ie providing active time) and extended idle mode DRX (ie providing extended idle mode DRX parameters).

  The decision between the above three, as well as the determination of which active time, periodic TAU timer and / or extended idle mode DRX cycle value should be provided to the UE depends on the local configuration and possibly other available in the SGSN / MME Implementation-dependent based on information. The selected method is then used until the next attach or RAU / TAU procedure is initiated, at which time a new decision can be made. If both extended I-DRX and PSM are enabled, an extended I-DRX cycle should be set up with the purpose of having multiple paging opportunities while the active timer is running.

  In the unique case where the PSM active time provided by the wireless device is greater than the extended idle mode DRX cycle value provided by the wireless device, the SGSN / MME may enable both PSM and extended idle mode DRX. This allows the wireless device to minimize power consumption during the active time, for example when the active time is slightly longer, for example on the order of a few minutes, than typical active time values.

  In the case where extended idle mode DRX is enabled, the network shall be configured for high latency communication as described in Section 4.5.7 “GTP-C retransmissions” as described in TS 23.060 and TS 23.401. Features are used to handle mobile termination data and apply techniques to handle mobile termination SMS as TS23.272 and location service as TS23.271.

Wireless device power saving mode
A wireless device may employ PSM to reduce its power consumption. The mode is similar to power off, but remains registered in the network and there is no need for reattach or re-establishing the PDN connection. Wireless devices in PSM are not immediately reachable for mobile termination services. Wireless devices using PSM are available for mobile termination services during the period of time in connected mode and over the period of active time after connected mode. Connected mode is triggered by a mobile-originated event such as data transfer or signaling after periodic TAU / RAU procedures, for example. Accordingly, PSM is intended for wireless devices that are only expecting infrequent mobile originating and mobile terminating services and can accept corresponding latencies in mobile terminated communications.

[Outline of Exemplary Embodiment]
During the operation of the wireless communication network, there may be moments when the core network node fails or requires a restart. Various procedures are in place to keep communication disruption to a minimum during such failures or restarts of the core network node. An example of such a procedure is a network-triggered service recovery procedure, as specified in Chapter 25 of 3GPP TS 23.007. In this procedure, a node called a serving gateway (SGW) detects the occurrence of a failure of a mobility management node, which is a mobility management entity (MME) or a serving general packet radio service (GPRS) support node (SGSN), for example. The SGW will be required to maintain the PDN connection. Thereafter, if the SGW receives downlink data for a wireless device, it will issue a downlink data notification with the IMSI of that wireless device associated with the PDN connection.

  However, in a new scheme that has been developed soon, especially for machine-type wireless devices, the wireless device may use enhanced DRX or enter Power Saving Mode, which listens for paging requests. In such cases, paging triggered by reception of downlink data does not make any sense and simply creates extra signaling on the network.

  Moreover, depending on what type of service the wireless device is authorized to use, a means of providing dynamic or updated information regarding the possibility of changing the attribute of the PDN connection being delayed tolerant Currently does not exist.

  In addition, there is currently no specification of how such a delay-tolerant attribute of a PDN connection can affect the management of the PDN connection in the presence of a mobility management node failure or restart.

  Thus, at least one objective of the exemplary embodiments presented herein is to work out a mechanism for the case where a network triggered service recovery procedure is deployed in a communication network where the wireless device may be in enhanced DRX or power saving mode. It is how to provide it effectively. Specifically, the purpose of the exemplary embodiment presented here is how to manage PDN connections for wireless devices in a network that is configured to support network-triggered service recovery procedures. At least one other objective of the exemplary embodiment is how to effectively manage PDN connections in the presence of a mobility management node failure or restart.

  At least one exemplary advantage of the embodiments presented here is that unnecessary signaling is reduced. Based on the ability of the PDN connection associated with the wireless device to receive delayed communications, the PDN connection may or may not be maintained in the presence of a mobility management node failure or restart. Moreover, another exemplary advantage is that, in terms of mobility management node failure or restart, changes in delay tolerance, eg due to service or application usage, can be taken into account with respect to management of PDN connections. It is.

  A new indicator called “Delay Tolerant Connection” has been introduced, which is used to indicate by the PGW that the PDN connection is delayed tolerant. For example, the PGW receives a rejection cause from the MME / SGSN via the SGW during the network initiated procedure, indicating that the wireless device is temporarily unreachable due to power savings and its network initiated. A pending bearer request with a UASI indicating that the wireless device is available for end-to-end signaling for the PDN connection. ) Until the message is received by the PGW. However, this delay-tolerant connection indicator is not used by the SGW.

PDN connection management during the mobility procedure with SGW changes According to some exemplary embodiments, the SGW detects an MME / SGSN failure (failure of MME / SGSN restart or no restart) This indicator should be used in the form of not retaining PDN connections labeled as delayed tolerant connections. In order to achieve this, in addition, the above information that “PDN connection is labeled with a delay-tolerant connection” is used during the mobility procedure with SGW changes, ie inter-MME for UEs in idle mode. / SGSN TAU / RAU and during the inter MME / SGSN handover procedure for UEs in active / connected mode shall be transferred to the new SGW.

  In the session creation request message (Create Session Request) from the (target) MME / SGSN when a new SGW is contacted, or the modify bearer response (Modify Bearer Response) from the PGW The new SGW can include its own update in a response from the PGW when it sends it to the PGW with a Modify Bearer Request message.

  FIG. 2 shows how the Delayed Tolerance Connection Indicator (DTCI) is transferred to a new SGW (SGW2 is the new SGW) during the mobility procedure with SGW changes.

  The green bold text represents the first means of using the context transfer procedure (Context Request / Response / Acknowledge) to transfer DTCI from the old MME / SGSN to the new MME / SGSN. , DTCI is included in a Create Session Request message to the new SGW.

  The red bold text represents the second means by which the PGW provides DTCI to the new SGW using the Modify Bearer Response. This option implicitly allows the DTCI to be changed in the way that the new SGW should forward the DTCI to the new MME / SGSN in subsequent Create Session Response signaling.

  The MME is only an example, which may be S4-SGSN, MME or Gn / Gp SGSN as the source (old) mobility management node and S4-SGSN or MME as the target (new) mobility management node. . The PGW may be a PGW. A wireless device (UE) may stay in either 2G / 3G or LTE.

Dynamic management of delayed-tolerance connection indications for a given PDN connection According to prior art methods, delayed tolerance is set only when a PDN connection is established for each PDN connection, and the PDN connection is active When you can't change it.

  On the other hand, according to the exemplary embodiment presented here, a PDN connection can be labeled as a delayed tolerant connection during a PDN connection, but may be modified to be non-delay tolerant at a later stage and vice versa. It is also true.

Example:
1. When the wireless device activates the PDN connection, the PCRF may set the PDN connection as a delayed tolerant connection according to the currently available subscription, eg, the access point name. However, the wireless device may contact a non-delay-tolerant service, for example, via a web portal for subscribing to a non-delay-tolerant service, or by contacting an application server for registering a non-delay-tolerant service. If you activate later;
2. When the wireless device activates the PDN connection, the PCRF may set the PDN connection as a non-delayed tolerant connection, while the wireless device has expired its authorization quota or, for example, the web by the end user A wireless device subscription changes, such as when it is modified through the portal (when the end user tries to sleep).

  In short, the setting of whether or not tolerant to delay does not depend on whether the wireless device has activated the power saving mode or enhanced DRX, but depends on the service used by the UE. To that end, the PCRF should be able to change the setting of the delayed tolerance connection indicator while the PDN connection remains active.

  FIG. 3 shows that a delayed tolerance connection indicator is made during the PDN connection creation procedure, but the PDN connection is later reset to a normal PDN using an Update Bearer Request message. When the updated PCRF determination requires bearer generation / deletion, the PGW can use a bearer generation / deletion request (Create / Delete Bearer Request). Text highlighted in red represents changes resulting from the present invention. According to some of the exemplary embodiments, such changes may be based on application or service changes experienced by the wireless device.

[Example node configuration]
FIG. 4 shows an exemplary node configuration of nodes. Any node discussed herein may have the configuration shown in FIG. Examples of such nodes are SGW 117, core network nodes (eg, SGSN 111, S4-SGSN 110, MME 115 or PGW 119), and PCRF 120. In accordance with the exemplary embodiment described herein, nodes may provide PDN connection management in a communication network. The node may comprise a receiver 401 that may be configured to receive communication data, instructions, delay tolerance information, wireless device application or service usage information, and / or messages. The node may also include a transmitter 402 that may be configured to transmit communication data, instructions, delay tolerance information, wireless device application or service usage information, and / or messages. It should be understood that the receiver 401 and transmitter 402 may be provided as any number of transmit / receive, receive and / or transmit units, modules or circuits. It should further be appreciated that receiver 401 and transmitter 402 may be in the form of any input or output communication port known in the art. The receiver 401 and transmitter 402 may include an RF circuit and a baseband processing circuit (not shown).

  The node may also include a processing unit or circuit 403 that may be configured to process information related to managing PDN connections as described herein. The processing circuit 403 may be any suitable type of computation, for example a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC) or any other type of circuit or module. It may be a unit. The node may further comprise a memory unit or circuit 405 that is any suitable type of computer readable memory and may be volatile and / or non-volatile. The memory 405 stores data, device parameters, communication priority, delay tolerance information, wireless device application or service usage information, and / or executable program instructions received, transmitted and / or measured. Can be configured.

[Example Node Behavior]
FIG. 5A is a flow diagram depicting exemplary operations that may be taken by the SGW to manage a PDN connection for a wireless device as described herein. It should also be appreciated that FIG. 5A includes some actions drawn with solid boundaries and some actions drawn with dashed boundaries. The operations included within the solid line boundaries are those included in the broadest exemplary embodiment. Actions that fall within the boundaries of the dashed line may be included in the actions of the broader exemplary embodiments, may be part of them, or are additional actions that may be incorporated in addition to them. Embodiment. It should be understood that the operations may not be performed in order. Moreover, it should be understood that not all of these operations need to be performed. The example operations may be performed in any order and may be performed in any combination. These exemplary operations are further described in at least a non-limiting overview of exemplary embodiments.

  It should be understood that the numbering employed in FIG. 5A corresponds to the reference number described in the section “Overview of Exemplary Embodiments”.

  FIG. 5B is a module diagram depicting modules that may perform at least some of the operations of FIG. 5A.

  FIG. 6A is a flow diagram depicting exemplary operations that may be taken by a core network node to manage a PDN connection for a wireless device as described herein. It should also be recognized that FIG. 6A includes some actions drawn with solid boundaries and some actions drawn with dashed boundaries. The operations included within the solid line boundaries are those included in the broadest exemplary embodiment. Actions that fall within the boundaries of the dashed line may be included in the actions of the broader exemplary embodiments, may be part of them, or are additional actions that may be incorporated in addition to them. Embodiment. It should be understood that the operations may not be performed in order. Moreover, it should be understood that not all of these operations need to be performed. The example operations may be performed in any order and may be performed in any combination. These exemplary operations are further described in at least a non-limiting overview of exemplary embodiments.

  It should be understood that the numbering employed in FIG. 6A corresponds to the reference number described in the section “Overview of Exemplary Embodiments”.

  FIG. 6B is a module diagram depicting modules that may perform at least some of the operations of FIG. 6A.

  FIG. 7A is a flow diagram depicting exemplary operations that may be taken by a PCRF to manage a PDN connection for a wireless device as described herein. It should also be appreciated that FIG. 7A includes some actions drawn with solid boundaries and some actions drawn with dashed boundaries. The operations included within the solid line boundaries are those included in the broadest exemplary embodiment. Actions that fall within the boundaries of the dashed line may be included in the actions of the broader exemplary embodiments, may be part of them, or are additional actions that may be incorporated in addition to them. Embodiment. It should be understood that the operations may not be performed in order. Moreover, it should be understood that not all of these operations need to be performed. The example operations may be performed in any order and may be performed in any combination. These exemplary operations are further described in at least a non-limiting overview of exemplary embodiments.

  It should be understood that the numbering employed in FIG. 7A corresponds to the reference number described in the section “Overview of Exemplary Embodiments”.

  FIG. 7B is a module diagram depicting modules that may perform at least some of the operations of FIG. 7A.

  Some of the embodiments described above may be summarized as follows:

  Certain embodiments are directed to a method in the SGW for managing a PDN connection for a wireless device. Receiving the DTCI from at least one GTP entity indicating whether communication on the identified PDN connection for the wireless device can be delayed; and storing the DTCI in the SGW; Managing the PDN connection after detection of a failure (with or without restart) of a mobility management node serving the wireless device, wherein the managing includes the PDN connection being delayed tolerant. Deleting the PDN connection if the DTCI indicates that it is present, or maintaining the PDN connection if the DTCI indicates that the PDN connection is not delayed tolerant.

  It should be understood that not setting DTCI may be used along with other features and other operator policies to determine whether a PDN connection should be maintained. Examples of such features and operator policies are QCI / ARP / APN and such parameters. The SGW may determine whether to maintain the PDN connection based on DTCI, which may include any number of parameters.

  According to the exemplary embodiment, the SGW will store the DTCI and manage the PDN connection based on the stored DTCI value. In contrast to prior art methods, the SGW blindly forwards those values to the mobility management node. In the prior art method, the SGW does not utilize DTCI.

  In the use of DTCI, the SGW may maintain the PDN connection if the DTCI value indicates that the PDN connection is not delayed-tolerant after detection of a mobility management node failure (with or without restart). If the PDN connection is delayed tolerant, the PDN connection will be deleted, i.e. the PDN connection is not eligible for the network triggered service recovery procedure. This is to avoid unnecessary paging signaling since the wireless device may activate a power saving mechanism, eg, enhanced DRX is enabled or enters a power saving state.

  The DTCI may be provided with a flag, cause code, or any other form of indicator known in the art.

  In the method, the at least one GTP entity may be a PGW, and the receiving may further include receiving the DTCI from the PGW during a PDN connection creation procedure.

  According to the exemplary embodiment, the DTCI may be provided during a PDN connection creation procedure, for example, in a Create Session Response message.

  In the method, the receiving is performed during a mobility procedure with SGW relocation, the SGW may be a new SGW, and the at least one GTP entity completes the mobility procedure. It may be a new mobility management node that will later serve the wireless device, and the receiving further comprises receiving the DTCI during a mobility procedure from the new mobility management node. .

  According to the exemplary embodiment, the DTCI may be provided in a Context Response message, for example. It should be understood that the new mobility management node receives the DTCI in a Context Response message from the old mobility management node.

  In the method, the receiving is performed during a mobility procedure with SGW relocation, the SGW may be a new SGW, and the at least one GTP entity may be a PGW. Well, the receiving further includes receiving (eg, current) DTCI during the mobility procedure from the PGW.

  According to the exemplary embodiment, the DTCI may be provided in a Modify Bearer Response message, eg, from a PGW.

  The method may further include receiving a dynamically updated DTCI from the at least one GTP entity.

  It should be understood that the dynamically updated DTCI may be provided in an Update / Create / Delete bearer request or Modify Bearer Response message. According to some exemplary embodiments, such dynamic updates of DTCI may be based on changes in the usage of services or applications employed by the wireless device. It should be understood that such dynamically updated DTCI may originate from the PCRF and be provided to the SGW via the PGW.

  In the above method, the mobility management node may be MME, SGSN, or S4-SGSN.

  Some other embodiments described above may be summarized as follows:

  One other embodiment is directed to an SGW for managing PDN connections for wireless devices. The SGW includes a processor and a memory, the memory including instructions executable by the processor, whereby the SGW is identified from at least one GTP entity with an identified PDN connection for the wireless device. After detecting a failure (with or without restart) of a mobility management node that receives DTCI indicating whether the above communication can be delayed, stores the DTCI in the SGW, and serves the wireless device Managing the PDN connection, wherein the management deletes the PDN connection when the DTCI indicates that the PDN connection is delay tolerant, or the PDN connection is If the DTCI indicates that it is not delayed tolerance, the PDN connection is maintained. To it, including the.

  It should be understood that not setting DTCI may be used along with other features and other operator policies to determine whether a PDN connection should be maintained. Examples of such features and operator policies are QCI / ARP / APN and such parameters. The SGW may determine whether to maintain the PDN connection based on DTCI, which may include any number of parameters.

  According to the exemplary embodiment, the SGW will store the DTCI and manage the PDN connection based on the stored DTCI value. In contrast to prior art methods, the SGW blindly forwards those values to the mobility management node. In the prior art method, the SGW does not utilize DTCI.

  In the use of DTCI, the SGW may maintain a PDN connection if the DTCI value indicates that the connection is not delayed-tolerant after detection of a failure (with or without restart) of the mobility management node. If the PDN connection is delayed tolerant, the PDN connection will be deleted, i.e. the PDN connection is not eligible for the network triggered service recovery procedure. This is to avoid unnecessary paging signaling since the wireless device may activate a power saving mechanism, eg, enhanced DRX is enabled or enters a power saving state.

  The DTCI may be provided with a flag, cause code, or any other form of indicator known in the art.

  With respect to the SGW of this exemplary embodiment, the at least one GTP entity may be a PGW, and the SGW receives the DTCI during the PDN connection creation procedure from the PGW, and so on. It may be operable.

  According to the exemplary embodiment, the DTCI may be provided during a PDN connection creation procedure, for example, in a Create Session Response message.

  With respect to the SGW of this exemplary embodiment, the SGW may be further operable to receive the DTCI during a mobility procedure with SGW relocation, wherein the SGW is a new SGW The at least one GTP entity may be a new mobility management that will serve the wireless device after completion of the mobility procedure, and the SGW may be from the new mobility management node. It may be further operable to receive the DTCI during a mobility procedure.

  According to the exemplary embodiment, the DTCI may be provided in a Context Response message, for example. It should be understood that the new mobility management node receives the DTCI in a Context Response message from the old mobility management node.

  With respect to the SGW of this exemplary embodiment, the SGW may be operable to receive the DTCI during a mobility procedure with SGW relocation, wherein the SGW is a new SGW And the at least one GTP entity may be a PGW, and the SGW is further operable to receive DTCI (eg, at that time) during the mobility procedure from the PGW. There may be.

  According to the exemplary embodiment, the DTCI may be provided in a Modify Bearer Response message, eg, from a PGW.

  With respect to the SGW of this exemplary embodiment, the SGW may be further operable to receive dynamically updated DTCI from the at least one GTP entity.

  It should be understood that the dynamically updated DTCI may be provided in an Update / Create / Delete bearer request or Modify Bearer Response message. According to some exemplary embodiments, such dynamic updates of DTCI may be based on changes in the usage of services or applications employed by the wireless device. It should be understood that such dynamically updated DTCI may originate from the PCRF and be provided to the SGW via the PGW.

  With respect to the SGW of this exemplary embodiment, the mobility management node may be a mobility management entity, a serving general packet radio service (GPRS) support node (SGSN), or an S4-SGSN.

  Some other embodiments described above may be summarized as follows:

  One other embodiment is directed to a method at a core network node for dynamically managing PDN connections for a wireless device (101), wherein the core network node is identified PDN for the wireless device. The core network node is configured for a network-triggered service recovery procedure, including a stored DTCI that indicates whether communication on the connection can be delayed. The method includes receiving an updated DTCI from a PCRF or other core network node indicating an altered status regarding whether the identified PDN connection for the wireless device is delayed tolerant; Storing DTCI in the core network node.

  According to the embodiment, the DTCI as an attribute of the PDN connection is provided in a dynamic manner. Thus, an updated DTCI is provided when the PDN connection is active (ie not only during the initial attach or PDN connection creation or mobility procedure).

  According to the exemplary embodiment, the update to the DTCI is based on the application or service being utilized by the identified PDN connection for the wireless device. For example, PDN connections that were previously identified as being delay tolerant according to subscribed or approved services are later used for services where the delay is not acceptable. Thus, an updated DTCI is sent indicating that the PDN connection is not delay tolerant.

  The DTCI may be provided with a flag, cause code, or any other form of indicator known in the art.

  In the method, the updated DTCI may be received from the PCRF, the core network node may be a PGW, and the method forwards the updated DTCI to the SGW. Further, it may be included.

  According to the exemplary embodiment, the updated DTCI may be provided from the PCRF to the PGW in a Re-Authorization Request message.

  In the method, the updated DTCI may be received from a PGW, the core network node may be an SGW, and the method forwards the updated DTCI to a mobility management node; May further be included.

  The method may further comprise managing the PDN connection, wherein the managing deletes the PDN connection when the DTCI indicates that the PDN connection is delayed tolerant, or Maintaining the PDN connection if the DTCI indicates that the PDN connection is not delayed tolerant.

  According to the exemplary embodiment, the updated DTCI may be provided in the Update / Create / Delete Bearer Request message from the PGW to the SGW.

  In the method, the updated DTCI may be received from the SGW, and the core network node may be a mobility management node.

  In the method, the mobility management node may be a mobility management entity, a serving general packet radio service (GPRS) support node (SGSN), or an S4-SGSN.

  Some other embodiments described above may be summarized as follows:

  One other embodiment is directed to a core network node for dynamically managing PDN connections for wireless devices. The core network node includes a stored DTCI that indicates whether communication on the identified PDN connection for the wireless device can be delayed. The core network node includes a processor and a memory, the memory including instructions executable by the processor, whereby the core network node is identified for the wireless device from a PCRF or other core network node. Receiving an updated DTCI indicating a changed status as to whether the PDN connection is tolerant of delay and storing the updated DTCI in the core network node.

  According to the embodiment, the DTCI as an attribute of the PDN connection is provided in a dynamic manner. Thus, an updated DTCI is provided when the PDN connection is active (ie not only during the initial attach or PDN connection creation or mobility procedure).

  According to the exemplary embodiment, the update to the DTCI is based on the application or service being utilized by the identified PDN connection for the wireless device. For example, PDN connections that were previously identified as being delay tolerant according to subscribed or approved services are later used for services where the delay is not acceptable. Thus, an updated DTCI is sent indicating that the PDN connection is not delay tolerant.

  The DTCI may be provided with a flag, cause code, or any other form of indicator known in the art.

  With respect to the core network node of this exemplary embodiment, the updated DTCI may be received from the PCRF, the core network node may be a PGW, and the core network node is updated. It may be further operable to forward the DTCI to the SGW.

  According to the exemplary embodiment, the updated DTCI may be provided from the PCRF to the PGW in a Re-Authorization Request message.

  For the core network node of this exemplary embodiment, the updated DTCI may be received from a PGW, the core network node may be an SGW, and the core network node is updated. It may be further operable to forward the DTCI to a mobility management node.

  With respect to the core network node of this exemplary embodiment, the management of the PDN connection deletes the PDN connection when the DTCI indicates that the PDN connection is delay tolerant. Or may be operable to maintain the PDN connection if the DTCI indicates that the PDN connection is not delayed tolerant.

  According to the exemplary embodiment, the updated DTCI may be provided in the Update / Create / Delete Bearer Request message from the PGW to the SGW.

  For the core network node of this exemplary embodiment, the updated DTCI may be received from the SGW, and the core network node may be a mobility management node.

  With respect to the core network node of this exemplary embodiment, the mobility management node is a mobility management entity (115), a serving general packet radio service (GPRS) support node (SGSN) (111), or S4-SGSN (110). It may be.

  Some other embodiments described above may be summarized as follows:

  One other embodiment is directed to a method in a PCRF for dynamically managing PDN connections for wireless devices. The method detects a status change in the delay tolerance of the PDN connection, and the status change presents a change as to whether the identified PDN connection for the wireless device can receive delayed communications. And updating the DTCI based on the detected status change and transmitting the updated DTCI to the PGW.

  Some other embodiments described above may be summarized as follows:

  One other embodiment is directed to a PCRF for dynamically managing PDN connections for wireless devices. The PCRF may comprise a processor and a memory, the memory including instructions executable by the processor, whereby the PCRF is a status change in the delay tolerance of the PDN connection, the wireless device Detecting the status change presenting a change as to whether the identified PDN connection is capable of receiving delayed communications, updating the DTCI based on the detected status change, and updating the updated DTCI Is sent to the PGW.

  It should be noted that although terminology from 3GPP LTE is used here to describe the exemplary embodiment above, this limits the scope of the exemplary embodiment to only the systems described above. Should not be seen as. Other wireless systems including WCDMA, WiMAX, UMB, WiFi, and GSM may also benefit from the exemplary embodiments disclosed herein.

  The description of the exemplary embodiments provided herein is presented for purposes of illustration. The description is not intended to be exhaustive or to limit the exemplary embodiments to the precise forms disclosed, and may be modified or provided in light of the above teachings Modifications and variations may be obtained from the practice of various alternatives to the embodiments. The examples discussed herein are selected to illustrate the principles and nature of various exemplary embodiments and practical applications that enable those skilled in the art to utilize the exemplary embodiments in various ways. It is described and described, with various modifications suitable for the specific application envisioned. The features of the embodiments described herein may be combined in any possible combination of methods, apparatus, modules, systems and computer program products. It should be understood that the exemplary embodiments presented herein may be practiced in any combination with each other.

  It should be noted that the word “comprising” does not necessarily exclude the presence of other elements or steps other than those listed, but “a” or “an” preceding the element. Does not exclude the presence of multiple such elements. It is further noted that any reference signs do not limit the scope of the claims, and the exemplary embodiments may be implemented at least in part by both hardware and software means, and a plurality of "means" "," Unit "or" device "may be represented by the same item of hardware.

  As noted, terminology such as user equipment should be considered non-limiting. Device or user equipment, as the term is used herein, refers to internet / intranet access, web browser, organizer, calendar, camera (eg, video and / or still image camera), audio recorder (eg, microphone), And / or a radiotelephone with the capability for a global positioning system (GPS) receiver, a personal communications system (PCS) user equipment that can combine a cellular radiotelephone for data processing, and a radiotelephone or wireless communication system PDAs (personal digital assistance), laptops, cameras with communication capabilities (eg video and / or still image cameras), personal computers, home entertainment systems, televisions, etc. It should be interpreted broadly to include any other computing or communication device capable of transmitting and receiving. It should be understood that the term user equipment may include any number of connected devices. Further, it should be understood that the term “user equipment” shall be construed to define any device that may have access to the Internet or a network. Moreover, it should be understood that the term M2M device shall be construed to be a subclass of user equipment engaged in infrequent communication.

  The various exemplary embodiments described herein are described in the general context of method steps or processors, which in one aspect are implemented by a computer program product embodied in a computer-readable medium. Often, a computer-readable medium includes computer-executable instructions, such as program code, executed by a computer in a networked environment. Computer readable media include, but are not limited to, removable and non-removable, including ROM (Read Only Memory), RAM (Random Access Memory), CD (compact discs), DVD (digital versatile discs), etc. A storage device may be included. Generally, program modules may include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of program code for executing steps of the methods disclosed herein. The specific sequence of such executable instructions or associated data structures represents an example of a corresponding operation for implementing the functionality described in such steps or processes.

In the drawings and specification, there have been disclosed exemplary embodiments. However, many variations and modifications can be made to these embodiments. Thus, although specific terminology is employed, they are used in a generic and descriptive sense only and are not intended to be limiting, and the scope of the embodiments is that of the following exemplary embodiments Defined by summary.

With respect to the SGW of this exemplary embodiment, the SGW may be further operable to receive the DTCI during a mobility procedure with SGW relocation, wherein the SGW is a new SGW The at least one GTP entity may be a new mobility management node that will serve the wireless device after completion of the mobility procedure, and the SGW may be the new mobility management node. May be further operable to receive the DTCI during a mobility procedure.

In the drawings and specification, there have been disclosed exemplary embodiments. However, many variations and modifications can be made to these embodiments. Thus, although unique terminology is employed, they are used in a generic and descriptive sense only, not for purposes of limitation, and the scope of the embodiments is defined by the appended claims. Is done.

Claims (26)

A method at a serving gateway (SGW) (117) for managing a packet data network (PDN) connection for a wireless device (101) comprising:
Delay tolerance indicating whether communication on the identified PDN connection for the wireless device can be delayed from at least one General Packet Radio Service (GPRS) Tunneling Protocol (GTP) entity (110, 111, 115, 119) Receiving (10) a sex connection indicator (DTCI);
Storing the DTCI in the SGW (18);
Managing the PDN connection after detection of a failure of a mobility management node serving the wireless device (20);
Including
The managing (20)
Deleting the PDN connection if the DTCI indicates that the PDN connection is delayed tolerant (22), or
Maintaining the PDN connection if the DTCI indicates that the PDN connection is not delayed tolerant (24);
Including a method.   The at least one GTP entity is a PDN gateway (PGW) (119), and the receiving (10) receives the DTCI from the PGW during a PDN connection creation procedure (12); The method of claim 1 further comprising:   The receiving (10) is performed during a mobility procedure with SGW relocation, the SGW is a new SGW, and the at least one GTP entity A new mobility management node (110, 111, 115) that will serve (101) and the receiving (10) receives the DTCI from the new mobility management node during a mobility procedure The method of claim 1, further comprising:   The receiving (10) is performed during a mobility procedure with SGW relocation, the SGW is a new SGW, the at least one GTP entity is a PGW (119), and the receiving The method of any of claims 1-2, wherein doing (10) further comprises receiving (16) the DTCI during a mobility procedure from the PGW.   5. The method of any of claims 1-4, further comprising receiving (26) dynamically updated DTCI from the at least one GTP entity.   The method according to any of the preceding claims, wherein the mobility management node is a mobility management entity (115), a serving general packet radio service (GPRS) support node (SGSN) (111), or an S4-SGSN (110). . A serving gateway (SGW) (117) for managing a packet data network (PDN) connection for a wireless device (101), the SGW comprising a processor (403) and a memory (405), wherein the memory Includes instructions executable by the processor so that the SGW
Delay tolerance indicating whether communication on the identified PDN connection for the wireless device can be delayed from at least one General Packet Radio Service (GPRS) Tunneling Protocol (GTP) entity (110, 111, 115, 119) Receiving (10) a sex connection indicator (DTCI);
Storing (18) the DTCI in the SGW;
Managing (20) the PDN connection after detecting a failure of a mobility management node serving the wireless device;
Is operable and
The management is
Delete (22) the PDN connection if the DTCI indicates that the PDN connection is delayed tolerant, or
Maintaining (24) the PDN connection if the DTCI indicates that the PDN connection is not delayed tolerant;
SGW (117).   The at least one GTP entity is a PDN gateway (PGW) (119), and the SGW is further operable to receive (12) the DTCI from the PGW during a PDN connection creation procedure. The SGW (117) of claim 7.   The SGW is operable to receive the DTCI during a mobility procedure with SGW relocation, the SGW is a new SGW, and the at least one GTP entity New mobility management (110, 111, 115) that will serve the wireless device after completion, and the SGW receives (14) the DTCI during the mobility procedure from the new mobility management node The SGW (117) of any of claims 7-8, further operable.   The SGW is operable to receive the DTCI during a mobility procedure with SGW relocation, the SGW is a new SGW, and the at least one GTP entity is a PGW (119) The SGW (117) of any of claims 7-8, wherein the SGW is further operable to receive (16) the DTCI during a mobility procedure from the PGW.   11. The method of any of claims 7-10, wherein the SGW is further operable to receive (26) dynamically updated DTCI from the at least one GTP entity (110, 111, 115, 119). SGW (117).   12. The SGW of any of claims 7-11, wherein the mobility management node is a mobility management entity (115), a serving general packet radio service (GPRS) support node (SGSN) (111), or an S4-SGSN (110). (117). A method in a core network node (110, 111, 115, 117, 119) for dynamically managing packet data network (PDN) connections for a wireless device (101), the core network node comprising: A stored delay tolerant connection indicator (DTCI) that indicates whether communication on the identified PDN connection for the wireless device is deferrable, wherein the core network node is for a network triggered service recovery procedure The method comprising:
Updated from a Policy Control and Charging Rules Function (PCRF) (120) or other core network node (117, 119) to indicate a changed status as to whether the identified PDN connection for the wireless device is delayed-tolerant Receiving DTCI (30);
Storing the updated DTCI in the core network node (32);
Including methods.   The updated DTCI is received from the PCRF (120), the core network node is a PDN gateway (PGW) (119), and the method uses the updated DTCI as a serving gateway (SGW) (117). 14. The method of claim 13, further comprising: transferring to (34).   The updated DTCI is received from a PDN gateway (PGW) (119), the core network node is a serving gateway (SGW) (117), and the method transfers the updated DTCI to a mobility management node ( 110. The method of claim 13, further comprising: forwarding to (110, 111, 115). The method further comprises managing the PDN connection (38);
The managing (38)
Deleting the PDN connection if the DTCI indicates that the PDN connection is delayed tolerant (40), or
Maintaining the PDN connection if the DTCI indicates that the PDN connection is not delayed tolerant (42);
16. The method of claim 15, comprising:   14. The method of claim 13, wherein the updated DTCI is received from a serving gateway (SGW) (117) and the core network node is a mobility management node (110, 111, 115).   The method according to any of claims 15 to 17, wherein the mobility management node is a mobility management entity (115), a serving general packet radio service (GPRS) support node (SGSN) (111), or an S4-SGSN (110). . A core network node (110, 111, 115, 117, 119) for dynamically managing packet data network (PDN) connections for a wireless device (101), wherein the core network node is for the wireless device Including a stored delay tolerant connection indicator (DTCI) that indicates whether communication on the identified PDN connection can be delayed, the core network node comprising a processor (403) and a memory (405); The memory includes instructions executable by the processor, whereby the core network node
Updated from a Policy Control and Charging Rules Function (PCRF) (120) or other core network node (117, 119) to indicate a changed status as to whether the identified PDN connection for the wireless device is delayed-tolerant Received DTCI (30),
Storing (32) the updated DTCI in the core network node;
Core network nodes (110, 111, 115, 117, 119) that are operable as follows.   The updated DTCI is received from the PCRF (120), the core network node is a PDN gateway (PGW) (119), and the core network node serves the updated DTCI as a serving gateway (SGW) 20. The core network node (110, 111, 115, 117, 119) of claim 19, further operable to forward (34) to (117).   The updated DTCI is received from a PDN gateway (PGW) (119), the core network node is a serving gateway (SGW) (117), and the core network node manages the updated DTCI. 20. The core network node (110, 111, 115, 117, 119) of claim 19, further operable to forward (36) to a node (110, 111, 115). The management of the PDN connection deletes (40) the PDN connection when the DTCI indicates that the core network node is delay tolerant, or
Maintain (42) the PDN connection if the DTCI indicates that the PDN connection is not delayed tolerant;
The core network node (110, 111, 115, 117, 119) of claim 21, further comprising:
According to these exemplary embodiments, the updated DTCI may be provided from the PGW to the SGW in a bearer update / generate / delete request message.   The core network node (110, 111, 115) of claim 19, wherein the updated DTCI is received from a serving gateway (SGW) (117) and the core network node is a mobility management node (110, 111, 115). 115, 117, 119).   24. The core of any of claims 21 to 23, wherein the mobility management node is a mobility management entity (115), a serving general packet radio service (GPRS) support node (SGSN) (111), or an S4-SGSN (110). Network node (110, 111, 115, 117, 119). A method in a Policy Control and Charging Rules Function (PCRF) (120) for dynamically managing packet data network (PDN) connections for a wireless device (101), comprising:
Detecting a status change in delay tolerance of the PDN connection (50) and the status change presents a change as to whether the identified PDN connection for the wireless device is capable of receiving delayed communications. And
Updating a delayed tolerant connection indicator (DTCI) based on the detected status change (52);
Sending (54) the updated DTCI to a PDN gateway (PGW) (119);
Including methods. A Policy Control and Charging Rules Function (PCRF) (120) for dynamically managing packet data network (PDN) connections for the wireless device (101), the PCRF comprising a processor (403) and a memory (405) The memory includes instructions executable by the processor, whereby the PCRF comprises:
Detecting (50) a status change in delay tolerance of the PDN connection, presenting a change related to whether the identified PDN connection for the wireless device is capable of receiving delayed communications;
Updating (52) a delay tolerance connection indicator (DTCI) based on the detected status change;
Sending (54) the updated DTCI to a PDN gateway (PGW) (119);
A PCRF (120) that is operable as follows.

Images