The present invention relates to communications protocols, and, more particularly, to Asynchronous Transfer Modes (ATM) defined in specifications associated with UTRAN (UMTS Terrestrial Radio Access Network) standards defined by the 3rd Generation Partnership Project (3GPP).
The invention has been developed to provide an additional feature to the presently accepted and proposed specifications defined by 3GPP, and will be described herein with reference to those specifications. However, it will be appreciated that telecommunications is a rapidly developing field, and that the invention may well have application to new and different standards and specifications that evolve from the various standards presently accepted or being proposed. Accordingly, the invention should not be seen as limited to existing specifications.
Various uses of ATM are defined in specifications issued by 3GPP. Of particular relevance is 3GPP TS 25.433 V3.3.0, the contents of which are incorporated herein by cross-reference.
ATM is a connection-oriented technique, comprising the concatenation of ATM layer links required to effect end-to-end transfers between access points. Connection identifiers are assigned to each link of a connection as required and released when no longer needed. In general, signalling and user information are carried on separate ATM connections. In the ATM modes, data to be transmitted is organised into cells.
At a given interface, in a given direction, the different Virtual Path (VP) links multiplexed at the ATM layer into the same physical layer connection are distinguished by a VPI. The different Virtual Channel (VC) links in a Virtual Path Connection (VPC) are distinguished by a VCI.
The AAL (ATM adaptation layer) performs functions required by the user, control and management planes and supports mapping between the ATM layer and the next higher layer. The functions performed in the AAL depend upon the higher layer requirements.
The AAL uses the ATM layer service and includes multiple protocols to fit the need of different AAL service users:
Termination points are managed objects that terminate entities, such as trails and connections. Technology-specific termination points are derived using subclassing. In ATM switching a termination point can be at the virtual path or virtual channel level, and it can be external or internal.
In the presently proposed UTRAN specification, a traffic termination point is determined either when a radio link is set up for a dedicated channel or a common transport channel is set up for a common channel. Each radio link has a traffic termination point, and each transport channel within each radio link may have its own AAL2 termination point. Similarly, each common transport channel has its own AAL2 termination point. Once a traffic termination or AAL2 termination point is defined, it is fixed for the duration of the connection.
In a Node B element, this fixing of termination points can generate a resource fragmentation problem. This means that even though a particular Node B element can have theoretically sufficient capacity to accept a requested high bandwidth call (such as a video call), but will need to reject the call because the available resources are scattered.
In accordance with a first aspect of the invention, there is provided a method of assigning resources within a network element within which a traffic termination point or AAL2 termination point has been established, the method including the steps of:
In accordance with a second aspect of the invention, there is provided a network element having resources to be allocated, within which a traffic termination point or AAL2 termination point has been established, the network element being configured to:
Preferably, prior to reallocating the termination points, it is determined which of the existing termination points should be reallocated to minimize fragmentation of resources within the network element, the termination points then being changed in accordance with that determination.
Preferably, reallocating the one or more termination points includes:
In a preferred embodiment, the TPSR includes one or more of the following:
Preferably, the network element is a Node B element in accordance with a 3GPP UTRA specification.
A preferred embodiment of the invention will now be described, by way of example only, with reference to the accompanying drawings, in which:
In its preferred form, the invention is applied to a Node B network element, forming part of an UTRA-based radio communications network for mobile telephony and other types of data transfer, operative portions of which are shown in
The operation of the network shown in
Upon receiving the request, the Node B ascertains whether the total network resources available at that point have sufficient bandwidth to carry the peak expected bandwidth for the data type the subject of the request. If sufficient bandwidth is available, and the way in which the termination points are allocated allows it, then the network resources sufficient for the requested connection are made available, and the connection established.
If, on the other hand, there are not sufficient resources available, the connection request is refused in the usual way. In prior art cases, the connection would also be refused in the event that there were sufficient resources, but the arrangement of terminations was such that the resources were too fragmented to be used by the requested (usually relatively high bandwidth) connection.
In the present case, if there is sufficient total bandwidth available, but previous allocations of available resources have fragmented the resources, the Node B ascertains how to best reallocate the resources to allow the new connection to be made. Depending upon the circumstances and implementation, for example, it may be preferable simply to defragment the resources only to the extent necessary to enable the presently requested connection to be made. Alternatively, a greater amount of defragmentation, ranging from slightly more than the minimum required up to complete defragmentation, may be undertaken. This could mean less of a delay in setting up new connections (subsequent to that presently requested) that might also not have been fulfilled without further defragmentation.
Once the desired reallocation of resources has been ascertained in the Node B network element, the element sends a Termination Point Switching Request (TPSR) message to Radio Network Controller (RNC). The TPSR message includes port information related to the specific termination points that the Node B has decided need to be reallocated. In the preferred form, the TPSR will include one or more of a Binding ID, a Transport Layer & Node B Communication Context ID, and a Communication Control Port ID. The actual combination of features will, however, vary between specific embodiments and applications.
The RNC will usually reply with a Switching Request Commit (SRC) message, which confirms that the resource reallocation is to take place. The SRC message also provides timing information enabling the Node B to synchronize the resource reallocation, such that the connections affected by the resource reallocations are maintained. The connection is then established in accordance with the timing information, ensuring that the reallocation is seamless to users of the system.
It will be appreciated that the invention can be applied to both traffic termination points and AAL2 termination points within a network element. In either case, the resource reallocation effectively results in switching of communication ports within the Node B network element.
Whilst the invention has been described with reference to a specific embodiment, it will be appreciated that the invention can be embodied in many other forms. For example, aspects of the invention may be embodied as computer readable instructions on one or more computer readable media.
Number | Date | Country | Kind |
---|---|---|---|
0028261.6 | Nov 2000 | GB | national |
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/IB01/02751 | 11/20/2001 | WO | 00 | 11/13/2002 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO02/41573 | 5/23/2002 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
4256925 | Goode | Mar 1981 | A |
4568930 | Livingston et al. | Feb 1986 | A |
4763321 | Calvignac et al. | Aug 1988 | A |
4965798 | Mostafa et al. | Oct 1990 | A |
5130982 | Ash et al. | Jul 1992 | A |
5737009 | Payton | Apr 1998 | A |
5875172 | Tabata | Feb 1999 | A |
6333936 | Johansson et al. | Dec 2001 | B1 |
6438370 | Einola et al. | Aug 2002 | B1 |
6466556 | Boudreaux | Oct 2002 | B1 |
6466559 | Johansson et al. | Oct 2002 | B1 |
6535583 | Bobick et al. | Mar 2003 | B1 |
6539415 | Mercs | Mar 2003 | B1 |
6542516 | Vialen et al. | Apr 2003 | B1 |
6639916 | Wakizaka | Oct 2003 | B1 |
6725038 | Subbiah | Apr 2004 | B1 |
6804246 | Petersen et al. | Oct 2004 | B1 |
6985455 | Heath et al. | Jan 2006 | B1 |
Number | Date | Country |
---|---|---|
5-268240 | Oct 1993 | JP |
8-237231 | Sep 1996 | JP |
WO 9722213 | Dec 1996 | WO |
WO 9956475 | Nov 1999 | WO |
Number | Date | Country | |
---|---|---|---|
20030093532 A1 | May 2003 | US |