This invention relates generally to call processing in a communication system and more particularly to memory management of call-related information.
Using a network element such as a Packet Data Serving Node (PDSN) to facilitate a communication is well known in the art. This includes, in more recent times, supporting communication sessions such as voice and/or data calls as between two or more parties. In many cases, the number of calls that a given network element can support at any given time is less than the network as a whole might otherwise support. As a result, a plurality of such network elements are typically deployed in order to make effective use of a given network's available resources.
There are, however, various causes contributing to the limited call capacity of a network element. One important causative agent comprises available memory. To illustrate, when a new call arrives at a Packet Data Serving Node, different modules as comprise the Packet Data Serving Node each allocate memory to store corresponding call context information. A not untypical Packet Data Serving Node chassis, for example, allocates about 30 KB of memory for each call for these purposes. As a result, many Packet Data Serving Nodes can only support a maximum of about 40,000 calls per card.
One can, of course, increase available memory by increasing the available quantity of memory. In many cases, however, this approach is unattractive. Increasing memory may, in some cases, be physically impossible. In other cases it may represent an unacceptable increase in cost.
The above needs are at least partially met through provision of the method and apparatus to increase session capacity described in the following detailed description, particularly when studied in conjunction with the drawings, wherein:
Skilled artisans will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of various embodiments of the present invention. Also, common but well-understood elements that are useful or necessary in a commercially feasible embodiment are often not depicted in order to facilitate a less obstructed view of these various embodiments of the present invention. It will also be understood that the terms and expressions used herein have the ordinary meaning as is usually accorded to such terms and expressions by those skilled in the corresponding respective areas of inquiry and study except where other specific meanings have otherwise been set forth herein.
Generally speaking, pursuant to these various embodiments, an enabling process detects a change in the operational status of a mobile station during a communication session and, in response to detecting that change, automatically increases memory capacity that is available to support additional communication sessions while simultaneously persisting at least some session information from that communication session for potential subsequent use during that communication session.
In a preferred approach, this process detects, in particular, a change in operational status from an active status to a dormant status though other approaches are available and may be preferable in a given setting.
There are, also, various ways to effect the indicated increase in memory capacity. Pursuant to one approach, some, but not all, session context information as corresponds to that communication session is deleted. The retained session context information is then stored. This stored information can then be quickly retrieved should the mobile station again become active in this communication session. Pursuant to a related approach, the retained session content information (in whole or in part) can be compressed prior to storing such information.
So configured, critical and/or useful session content information can persist and be available to quickly facilitate subsequent participation of the mobile station in a given communication session while also effecting a dynamic and significant increase in the quantity of available memory. This, in turn, can lead to a significant increase in the number of calls that can be supported by a given network element as the average storage requirements per call will typically drop.
These and other benefits may become more evident upon making a thorough review and study of the following detailed description. Referring now to the drawings, and in particular to
The memory 12 has session context information stored therein. More particularly, and as will be explained below in more detail, from time to time and during the course of a given communication session for a given mobile station, this session context information comprises an incomplete set of session context information as corresponds to that communication session. In a preferred approach, this incomplete set of session context information comprises, at the least, a minimal necessary subset of information as is necessary to facilitate subsequent restoration of a given call.
This memory 12 can be realized in any of a wide variety of ways. For example, this memory 12 can comprise a centralized storage platform or, if desired, the storage role can be distributed over a larger number of platforms. Further, this memory can be integral to the network element 10 or, if desired, some or all of the storage role described herein can be assigned to a more remotely located memory. Such architectural options are well understood in the art and require no further description here.
Network elements, including Packet Data Serving Nodes, typically comprise a partially or wholly programmable platform. Those skilled in the art will recognize and understand that such a platform can be readily programmed, configured, and arranged to accord with these teachings. More particularly, this programming and/or configuration can comprise provision of a session facilitation platform 11 that can detect a change in operational status of a given mobile station during the course of a communication session and, in response to detecting that change, automatically increase memory capacity that is available to support additional communication sessions while simultaneously persisting some session information for potential subsequent use during the communication session. More particularly, in a preferred approach the session facilitation platform 11 stores such session information in the memory 12 as the incomplete set of session context information noted above.
Further, and also pursuant to a preferred approach, the session facilitation platform 11 can also detect another change in the operational status of the given mobile station during that communication session (such as, and again as will be described below in more detail, a change from a dormant to an active mode of operation) and, in response to detecting that change, can automatically retrieve the incomplete set of session information for use during the communication session to at least substantially recreate a complete session context for the given mobile station.
With reference to
Referring now to
As yet another example, this detection can comprise receiving a message indicating the change in operational status. For example, the enabling network element can receive a Radio Network Node (RNN) to Packet Data Serving Node (PDSN) (RP) protocol compatible message in this regard (such as, to illustrate, an ACTIVE_STOP message over an A11 control channel, though other parameters will do doubt be appropriate to use to generate such a trigger in other systems as will be well understood by those skilled in the art).
As yet another example, this detection can comprise detecting the conclusion of an inactivity duration of time. To illustrate, the network element (or a surrogate acting on its behalf) can initiate a timer (by beginning a countdown or incrementing a count) upon detecting inactivity on the part of the mobile station. When that timer concludes, the persistent inactivity of the mobile station can be used to detect the mobile station as now being in a dormant state of operation.
Other possibilities exist as well. For example, historical information (regarding, for example, the active and inactive behaviors of the mobile station) may also be used to inform, directly or indirectly, such a detection process.
This process 30 then provides for automatically increasing 32 memory capacity that is available to support available communication sessions while simultaneously persisting at least some session information for potential subsequent use during the communication session. Memory capacity can be so increased using any of a wide variety of techniques. As one example, memory capacity can be increased by compressing at least some of the previously stored session information. This can comprise compressing some, or all, of the previously stored session information. As another example, memory capacity can be so increased by deleting at least some, but not all, of the session context information as corresponds to the communication session. More particularly, previously stored session information that is not critical to subsequent restoration of a corresponding call can be so deleted.
In a preferred approach, memory capacity is increased by deleting at least some, but not all, session context information as corresponds to the communication session to thereby provide some resultant retained session context information, and then compressing at least some of the retained session context information to provide compressed retained session context information. This reduced and compressed quantity of information can then be stored in a memory that also stores session context information to support additional communication sessions and/or in a memory that is discrete from a memory that stores such session context information, as may best suit the needs of a given context or application.
So configured, the network element significantly reduces through deletion and/or compression the amount of session context information that is retained by (or on behalf of) the network element notwithstanding that the communication session has not concluded. This, in turn, results in memory space that would otherwise have been allocated during such a session. This additional memory space can be used to support additional calls, thereby increasing the number of calls that can be handled and supported by a single network element. The particular information that persists can vary with the particular application. In general, such information will preferably comprise any kind of information that is usable at a later time to facilitate call restoration including particularly relevant session context information. Such information can comprise, for example, Radio Network Node to Packet Data Serving Node protocol session context information, Point-to-Point Protocol session context information, Internet Protocol session context information, or some relevant combination thereof.
In an optional but preferred approach, this process 30 can further comprise then detecting 33 another change in the operational status of the mobile station during the communication session (for example, a change from a dormant status to an active status). Upon detecting such a change, the process 30 can then automatically retrieve 34 at least some of the stored session information to use during the communication session. This retrieval can be effected with respect to whichever local or remote memory (or memories) contains such information. In a preferred embodiment, this comprises retrieving session context information comprising, for example, any of Radio Network Node to Packet Data Serving Node protocol session context information, Point-to-Point Protocol session context information, Internet Protocol session context information, or some combination thereof.
Such retrieval can also comprise, when the information has been previously compressed as described above, the automatic decompression of at least a part of such stored session information.
So configured, the network element can utilize the recovered session context information to reconstruct or otherwise restore a desired level of connectivity for the mobile station at such time as the mobile station shifts from a dormant to an active status. This occurs notwithstanding that the network element had previously deleted and/or compressed the relevant information in order to make room available to accommodate an increased quantity of other communication sessions.
If desired, and referring now to
In the more specific illustrative examples provided above, RP, PPP, and IP session context information was presented as examples of session specific information of interest. Those skilled in the art will appreciate that any information deemed critical to call restoration can be similarly identified and processed to achieve or maintain the benefits set for herein.
Those skilled in the art will appreciate that considerable memory savings can be achieved using these teachings and that these savings can be directly applied in favor of supporting additional communication sessions. This, in turn, permits an existing network element such as a Packet Data Serving Node to be further leveraged with respect to the number of communication sessions that such a network element might otherwise be expected to reasonably accommodate. At the same time, these benefits are not gained at the undue expense of delay or inefficiency with respect to supporting subsequent participation of a given mobile station in a later portion of a given communication session, as the network element has the requisite core of information necessary to effect, for example, a rapid shift to reflect a change by the mobile station from a dormant status to an active status.
Those skilled in the art will recognize that a wide variety of modifications, alterations, and combinations can be made with respect to the above described embodiments without departing from the spirit and scope of the invention, and that such modifications, alterations, and combinations are to be viewed as being within the ambit of the inventive concept.
Number | Date | Country | Kind |
---|---|---|---|
11018299 | Dec 2004 | US | national |
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/US05/44559 | 12/9/2005 | WO | 00 | 9/2/2008 |