Patent Application
20060165093
This invention relates generally to Internet Protocol usage and support and more particularly to multi-stack Internet Protocol usage and support.
Internet Protocol-based network communications are well know in the art and include, at present, both Internet Protocol version 4 and Internet Protocol version 6-based protocols. Some approaches (such as CDMA2000) permit and support the use of so-called dual-stack client devices having an ability to operate with either Internet Protocol version 4 and Internet Protocol version 6, individually (with singular or multiple usage) or simultaneously with one another. This typically means that the client device and a corresponding remote network access server (such as, but not limited to, a packet data serving node) are able to run at least two different network control protocols (such as Internet Protocol Control Protocol and Internet Protocol version 6 Control Protocol) over a single Point-to-Point Protocol session.
Such multi-stack support, however, gives rise to new problems. For example, accounting streams are typically based on Remote Authentication Dial-In User Service (RADIUS) messages and assume the existence of only one Network Control Protocol that is associated with a given Point-to-Point Protocol session. Multi-stack support, however, contemplates associating multiple Network Control Protocols (and/or multiple instances of a same Network Control Protocol) with a single Point-to-Point Protocol session. Present accounting protocols and practices, therefore, are unable to provide a desired data granularity with respect to actual network resource usage in all cases. This, in turn, can lead to lost revenue opportunities for a network operator and/or unfair billing practices for network users.
Another problem concerns the amount of network resources required to construct and/or to tear down, for example, the Link Control Protocol layer of a Point-to-Point Protocol session. With earlier configurations, lacking multi-stack support, resource wastage associated with tearing down such a layer at the conclusion of a communication session, only to momentarily rebuild an identical capability for that same user a moment later to support a continuation of that communication session has been largely tolerated. With multi-stack support, however, the likelihood that an apparent end of given communication session will be momentarily followed by, for example, a new communication session for that same client device using a different Network Control Protocol increases. This, in turn, increases the rate at which corresponding Point-to-Point Protocol layers are needlessly torn down and rebuilt, thereby inefficiently consuming network resources and potentially lowering system throughput capability and overall quality of service levels.
The above needs are at least partially met through provision of the method and apparatus to support multi-stack hang time usage and multi-stack accounting 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 and/or relative positioning 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 accorded to such terms and expressions with respect to their corresponding respective areas of inquiry and study except where specific meanings have otherwise been set forth herein.
Generally speaking, pursuant to these various embodiments, a network access element (such as, but certainly not limited to, a packet data serving node) is provided with an ability to support communication sessions for a multi-stack Internet Protocol device (such as, but not limited to, a mobile station). Pursuant to a preferred but optional approach, that network access element is then also provided with an ability to use a hang time in conjunction with at least one of the communication sessions. Also pursuant to a preferred but optional approach, that network access element is also provided with an ability to differentiate between various network resources (such as, for example, Network Control Protocol layers of a Point-to-Point Protocol session) as are used to support various communication sessions that share at least one common network resource (such as, for example, a Link Control Protocol layer of a Point-to-Point Protocol session) to thereby facilitate discrete accounting recordations corresponding thereto.
The hang time capability permits the network access element to avoid needlessly tearing down a shared resource (such as a Link Control Protocol layer of a Point-to-Point Protocol session) as various discrete resources (such as different, or multiple instances of, Network Control Protocol sessions of a Point-to-Point Protocol session) are brought up and down in relatively quick succession by or on behalf of a given multi-stack Internet Protocol device. The improved accounting capability, used alone and/or in conjunction with a hang time capability, permits greater flexibility and accuracy with respect to tracking and/or billing with respect to the actual network usage of a given client device.
These and other benefits may become clearer upon making a thorough review and study of the following detailed description. Referring now to the drawings, and in particular to
The packet data serving node establishes corresponding authentication 13 with an authorization, authentication, and accounting element and then establishes an Internet Protocol Control Protocol (IPCP) session 14 with the mobile station to support, for example, a requested Internet Protocol version 4 session. With establishment of this IPCP session 14, the packet data serving node updates the authorization, authentication, and accounting element by providing an accounting start RADIUS message 15.
Eventually, the mobile station will conclude this communication session and termination 16 of the Link Control Protocol layer of the Point-to-Point Protocol session will follow. The packet control function and packet data serving node then tear down 17 the corresponding Radio Protocol session and the packet data serving node sends accounting stop information 18 to the authorization, authentication, and accounting element (those skilled in the art will know and recognize that, in some instances, the accounting stop may be instigated by the tearing down of the Point-to-Point Protocol session as versus the tear down of the Radio Protocol link). (Those skilled in the art will also known and recognize that other accounting start and stop message pairs may occur during the course of such a communication session based upon such triggers as the handoff of that call to a new packet control function, the dynamic changing of Usage Data Record (UDR) accounting attributes, the reception of active start or active stop Radio Protocol messages from a packet control function, the actions of an interim accounting timer and/or a time-of-day timer, and so forth.)
It can therefore be seen that the accounting information developed in this way corresponds, more or less, to actual network resource usage of the mobile station to support the described communication session. As noted above, however, this relatively straight-forward approach obscures much of relevance when applied in a multi-stack context and introduces other concerns and issues due to its single-minded reliance upon a one-to-one correspondence between a given type and duration of network usage with maintenance and existence of all layers of the Point-to-Point Protocol session itself.
Referring now to
Pursuant to one approach, this ability to use a hang time further comprises providing the network access element with an ability to use a selectively variable duration hang time (over a range, for example, of from about zero to about 15 seconds, though longer durations may be preferable for some applications). In general, and pursuant to a preferred approach, this ability to use a hang time further comprises an ability to maintain at least a lower level Point-to-Point Protocol session for the multi-stack Internet Protocol device during at least a portion, and preferably during all, of the hang time.
The above-described ability to use a hang time can be realized in any of a wide variety of ways. A preferred process 30 will now be described with reference to
When the specific session conclusion signal has not been detected (or when this option has not otherwise been deployed), the network access element responds to the detection 31 of a likely termination of the first communication session by providing 33 a hang time. The duration of the hang time can be static or dynamic (automatically varying, for example, with respect to the nature of the first communication session itself, a profile as characterizes the mobile station itself, a day of the week and/or time of the day, and so forth). When static, the hang time duration may also be nevertheless changeable by, for example, an authorized network administrator.
To provide 33 this hang time window, the network access element preferably continues to maintain at least one network resource notwithstanding having released/torn down some portion of the first communication session. For example, the network access element may have torn down the Network Control Protocol layer of a Point-to-Point Protocol session as was used to facilitate the first communication session but will continue to maintain the Link Control Protocol layer of that Point-to-Point Protocol session.
The network access element then monitors to detect 34 whether a relevant communication session occurs for the multi-stack Internet Protocol device. A relevant communication session might be, for example, a continuation of the first communication session and/or a new communication session (possibly using, for example, a different Network Control Protocol or a same Network Control Protocol as the first communication session). While repeatedly monitoring in this regard, the network access element preferably continues checking to determine 35 if the hang time window has expired. If and when the hang time window expires without having detected a communication session of interest, the network access element can, for example, terminate 36 all presently supported aspects of the first communication session (thereby finally tearing down, for example, the Link Control Protocol layer of the Point-to-Point Protocol session).
When a communication session of interest is detected 34 during the hang time window, however, the network access device will preferably extend 37 at least some supported aspect of the first communication session to thereby provide support for the detected communication session. As one illustrative example, the network access device can continue to maintain the Link Control Protocol layer of the Point-to-Point Protocol session and to use that session in support of the detected communication session. In a preferred approach, this extension of support 37 will further comprise concluding the hang time monitoring and response window.
If desired, and as will be described in more detail below, the various actions taken above can also lead to an optional corresponding updating 38 of accounting information. For example, information regarding the duration of hang time during which the specific network resource was maintained can be locally logged and/or automatically forwarded to a remote accounting server such that an account as corresponds to the multi-stack Internet Protocol device can be debited with respect to hang time network resource usage notwithstanding the earlier release of at least some of the network resources. For example, if desired, one accounting charge may be made with respect to maintenance of the Link Control Protocol layer and a different accounting charge may be made with respect to the Network Control Protocol layer as was earlier terminated.
Referring now to
In this illustrative example, and following Radio Protocol setup 41A as between a packet control function and a packet data serving node, a multi-stack mobile station establishes the Link Control Protocol portion 42 of a Point-to-Point Protocol session with the packet data serving node and seeks authentication. The packet data serving node establishes authentication 43 with a corresponding authorization, authentication, and accounting element and then establishes a Network Control Protocol session with the mobile station (in particular, in this example, the Network Control Protocol session 44A comprises an Internet Protocol Control Protocol as characterizes, for example, Internet Protocol version 4). The packet data serving node then provides a RADIUS accounting start message 45A to the authorization, authentication, and accounting element.
Upon concluding its use of the Internet Protocol Control Protocol session, the mobile station/packet data serving node tear down 44B the Internet Protocol Control Protocol session. Notwithstanding this action, and pursuant to these teachings, the packet data serving node continues to maintain the Link Control Protocol layer of the corresponding Point-to-Point Protocol session and begins the above-described hang time window 46A. In this example, the mobile station/packet data serving node bring up a new communication session that makes use of an Internet Protocol version 6 Control Protocol session 47A prior to the conclusion of the hang time window. When this occurs, the packet data serving node terminates the hang time process and supports the new communication session using the original Link Control Protocol session.
When this second communication session eventually concludes, the mobile station/packet data serving node tear down 47B the Internet Protocol version 6 Control Protocol layer of the Point-to-Point Protocol session and the packet data serving node again initiates the hang time process 46B. This time, the mobile station does not seek to continue an earlier session nor initiate a new communication session during the full run of the hang time window 46B. At the conclusion of the hang time window 46B, the packet data serving node tears down 48 the Link Control Protocol layer of the Point-to-Point Protocol session and/or tears down 41B the Radio Protocol session.
So configured, the network is able to support a series of communication sessions without repeatedly needing to tear down/build up a supporting lower level Point-to-Point Protocol session. Depending upon network loading and individual mobile station usage, this can provide considerable savings with respect to overall network resource usage and allocation and/or can significantly reduce access time for the client device.
In the depicted example, the packet data serving node concludes by sending a RADIUS accounting stop 45B to the authorization, authentication, and accounting element. So configured, an account for the mobile station will simply reflect total time used by the mobile station when using a corresponding Network Control Protocol in addition to hang time spent supporting the lower level(s) of a facilitating Point-to-Point Protocol session. This may be adequate for some purposes. In many cases, however, this undetailed accounting information will be considered insufficient. It does not differentiate, for example, between the two kinds of Network Control Protocols being supported. This, in turn, renders it more difficult to differentiate billing rates and restrictions with respect to supporting different sessions.
It should be noted that, in the example provided, the multiple sessions do not overlap with one another. The problems noted, however, can further complicate the accounting issues when simultaneous sessions are supported. For example, if a given mobile station uses two simultaneous Network Control Protocol sessions in conjunction with a common Point-to-Point Protocol session, the mobile station may be able to effectively receive a two-for-the-price-of-one pricing allocation when only the start and end points of the overall Point-to-Point Protocol session are used to trigger the relevant accounting data points.
It may therefore be preferable, at least in some settings, to provide for accounting information prompts as correspond to bringing up and tearing down communication sessions as viewed from the standpoint of, for example, Network Control Protocol sessions rather than the Link Control Protocol layer of the corresponding Point-to-Point Protocol session and/or the Radio Protocol session(s). To illustrate, and referring now to
Later, and prior to concluding that Internet Protocol version 6 Control Protocol-based session 51A, the mobile station establishes a second communication session simultaneous with that first session. In particular, in this example, the mobile station establishes an Internet Protocol Control Protocol layer 53A (again in conjunction with the original Point-to-Point Protocol session). At this point, and notwithstanding that the packet data serving node is already supporting a first communication session with that Point-to-Point Protocol session, the packet data serving node transmits another accounting start message 54A to the authorization, authentication, and accounting element. This accounting start message 54A, in this example, corresponds to and reflects initiation of the new communication session 53A and provides for resource usage and tracking that is somewhat removed from the lower layers of an enabling Point-to-Point Protocol session (this separation is not complete, as termination of the Link Control Protocol layer of the Point-to-Point Protocol session will also necessarily terminate the higher layer Network Control Protocol sessions as well and may therefore be used as an accounting stop trigger if desired).
At this point, the mobile station is simultaneously using two essentially separate communication sessions using, in this example, two separate Network Control Protocols that share a common lower layer of a shared Point-to-Point Protocol session. The packet data serving node, in turn, has taken actions to permit individual accounting record taking for each such communication session. Additional sessions could be similarly added and layered if desired, including sessions based upon the same, or different, Network Control Protocols with corresponding accounting recording keeping responses by the packet data serving node.
In this example, the mobile station now tears down the second communication session by tearing down the Internet Protocol Control Protocol layer 53B. Notwithstanding that the associated Link Control Protocol layer of the Point-to-Point Protocol session remains active, and notwithstanding that another communication session using its own Network Control Protocol also remains active, the packet data serving node, pursuant to these teachings, responds to the conclusion of the second communication session by sourcing a corresponding accounting stop message 54B. This action permits accounting information regarding the specific duration of the second communication session to be developed and/or maintained notwithstanding the continued presence of a fundamental part of that session (i.e., the Link Control Protocol layer of the Point-to-Point Protocol session).
In this example, the mobile station next rebuilds an Internet Protocol Control Protocol session 55A (this may comprise a continuation of the earlier second communication session or may comprise a new session). Again, as before, the packet data serving node responds by sourcing an accounting start message 56A that corresponds with initiation of the new communication session. At this point, then, there are again two separate communication sessions being simultaneously supported for this mobile station using a shared Point-to-Point Protocol session.
Eventually, the mobile station concludes the first communication session and tears down that Internet Protocol version 6 Control Protocol-based session 51B. As with the earlier terminated Network Control Protocol session, the packet data serving node again sends a corresponding accounting stop 52B to the authorization, authentication, and accounting element.
At a later time, the mobile station concludes its last active communication session and tears down the one existing Network Control Protocol session 55B. In this instance, there are no other extant Network Control Protocol sessions being supported for the mobile station. Accordingly, and again in conformance with a preferred approach set forth above, the packet data serving node initiates a corresponding hang time 46B. During this hang time 46B the packet data serving node monitors to detect whether the mobile station seeks to initiate a new or follow-on communication session. And also as set forth above, in such a case, the packet data serving node preferably does not yet send a corresponding accounting stop notwithstanding that the mobile station has torn down the Network Control Protocol session.
In this example, the mobile station does not initiate any new or renewed communication sessions, and the hang time 46B concludes in due course. When this occurs, the Link Control Protocol layer of the Point-to-Point Protocol session is torn down 48 and, in a typical approach, the Radio Protocol session is also terminated 41B. And, again in conformance with the teachings set forth above, the packet data serving node at this point now transmits a final accounting stop 56B to close the accounting record for the last communication session conducted on behalf of the mobile station.
So configured, it can be seen and appreciated that a network element can monitor a network communication session that is supported, at least in part, by a first network resource and a second network resource, wherein the second network resource relies at least in part upon the first network resource. Upon detecting that apparent use of the second network resource concludes notwithstanding continued persistence of the first network resource, the network element is able to close an accounting record for the network communication session based on detecting this apparent conclusion of use of the second network resource. This permits great flexibility with respect to monitoring network usage and/or billing for used services.
In the above examples, a higher layer protocol session concludes while a more fundamental layer protocol session continues. It is possible, however, for the more fundamental layer to terminate first. To accommodate such a situation, and referring now to
To illustrate, and referring now to
The teachings set for herein comprise, in the aggregate, a flexible and powerful tool set for network administrators and are able to accommodate a wide variety of operational scenarios. As one illustrative example, and referring now to
Instead, as illustrated, a final accounting stop 88 for the terminated Network Control Protocol session can be automatically sent by the packet data serving node following conclusion of the hang time 83 (and, in this embodiment, receipt of a final active stop 87 to pair with a last active start 85 that had been received during the hang time 83). In a preferred approach, the packet data serving node may use information from that final active stop 73 as well as other information of interest in the mobile station's UDR to form the substance of that accounting stop 74.
As another illustrative example, and referring now to
In general, a supporting network access element, such as a packet data serving node, will record the times at which Network Control Protocol sessions begin and are terminated, the times at which a most recent Radio Protocol active start was received, and the times at which a most recent active stop was received, as such information can comprise a useful part of, or can be used to extrapolate the content of, corresponding accounting start and stop messages.
These teachings are implementable using a variety of realization techniques. In general, a supporting network access element 100 (see
In a preferred approach, the communication session controller 101 serves to use the communication link hang time value to delay tearing down the more fundamental communication link when the more fundamental communication link is no longer supporting a communication session for the multi-stack Internet Protocol mobile station using any of the plurality of communication protocols. The communication session controller 101 further preferably serves (alone or in conjunction with a hang time capability) to determine when to start and stop accounting records for the communication sessions as a function, at least in part, of starting and stopping use of various ones of the plurality of communication protocols notwithstanding continued persistence of the more fundamental communication link.
So configured, these teachings permit accounting information to be more readily and more accurately gathered and retained for a multi-stack network device such as a multi-stack Internet Protocol mobile station. These teachings are also employable to permit improved efficiency with respect to the use of at least some network resources.
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.
