Title of Invention

MEANS AND METHODS FOR IMPROVING THE HANDOVER CHARACTERISTICS OF RADIO ACCESS NETWORKS

Abstract

The invention provides a method for assisting handover of a communication session associated with a UT (240) from a first radio access point, AP1, (210) to a second radio access point, AP2, (220) in a radio access network, said method to be carried out by said AP1 (210) and comprising the steps of: - receiving a handover intention notify message comprising a session identifier identifying said session and indicating that said UT (240) intends to perform a session handover, - assigning said session a buffer memory space (213) in a memory (211) of said AP1 (210), - buffering downlink data packets addressed to said UT (240) in said buffer memory (213) as a response on receiving said handover intention notify message. The invention further provides a UT (240), an AP1, (210), AP2, (220), an AR, (250) and software program/s co-operating and/or realising the method according to the invention. The invention provides a smoother handover.

Full Text

TECHNICAL FIELD The invention relates generally to radio access networks and more specifically to methods and means for assisting handover of a communication session in such networks. BACKGROUND FIG 1 illustrates the basic network architecture of a conventional radio access network 100, in form of a wireless local area network, WLAN, comprising a first access point API 110, a second access point AP2 120, and an Access Router, AR 150. The WLAN 100 may be connected to other network/s 160 such as e.g. the Internet and/or a UTRAN (Universal Terrestrial Radio Access Network). In FIG. 1, API 110 and AP2 120 are connected with AR 150 via Multicast-enabled Layer 2 Switches, M-L2S1 130 and M- L2S2 135, respectively, but many other possibilities exist. The APs may e.g. be connected directly to AR 150 without any intermediate M-L2Ss, or they may be connected to the same M-L2S which in turn is connected to AR 150. Since the Ethernet (IEEE 802.3) protocol is used for most of the WLAN access points today as layer 2 protocol to communicate with fixed network infrastructure, an M-L2S is identical with an Ethernet switch. A User Terminal, UT, 140 having a communication session, e.g. a data session or a Voice over IP session with a peer connected to the network 160 (e.g. Internet or UTRAN), routed via API, 110, normally performs a handover of the session from API, 110, to AP2, 120, whenever a certain handover criterion is fulfilled. The criterion is normally a function of the offered radio link quality and/or QoS (quality of service) of API 110 and AP2 120, respectively, so that the UT's 140 communication session will be routed through the access point offering the highest/best radio link quality/QoS, in a conventional manner. However, the handover criterion may be based on other aspects e.g. regarding accounting, security etc. General problems regarding effective handover schemes for radio access networks relate e.g. to data loss minimization, interference suppression, packet delay minimization and to minimize network signaling. More specifically, for the WLAN in FIG. 1 exploiting the IEEE 802 standard, the establishment of a security association between the UT 140 and a target AP, i.e. AP2 120 in case of a handover from API 110 to AP2 120 in FIG. 1, when applying a standard EAP (Extensible Authentication Protocol) authentication in accordance with the IEEE 802.Hi security specification may pose a crucial issue regarding the caused interruption time, i.e. 2 it may cause unacceptable packet delay/loss for real time applications such as voice and/or video. Such an authentication is carried out after that the UT 140 has been successfully associated with the new AP (AP2 120 according to above example), and the radio link connectivity between UT 140 and the old AP (API, 110) is thus already aborted. During the period between the initiation of association with a new target AP (AP2, 120) and completion of the EAP authentication and installation of the security parameters at the new target AP, no data (e.g. IP-) packets can be exchanged between UT 140 and AR 150 over the WLAN transmission path, which of-course constitutes a problem. Another problem associated with the handover of TCP-sessions in radio access networks is that received packets being out of order will be retransmitted, which increases the radio interference, and the transmission rate may also be tuned down as a consequence, since the TCP interprets packets being out of order as a network congestion state. SUMMARY OF THE INVENTION The present invention seeks to mitigate/solve above problems. It is an object of the present invention to improve the handover characteristics of radio access networks, such as e.g. a WLAN or a UTRAN (Universal Terrestrial Radio Access Network). It is an object of the present invention to minimize data loss and/or to decrease the interference and/or the packet delay/loss and/or the network signaling, during a handover of a communication session from one radio access point to another, in a radio access network. It is a further object to mitigate the packet delay problems during handover, especially for real time applications such as voice and/or video, when applying an authentication procedure, such as an EAP standard procedure, in a wireless data network according to the IEEE 802 standard. According to a first aspect, the invention provides a method for assisting handover of a user terminal's, UT's, communication session from a first radio access point, API, to a second radio access point, AP2, in a radio access network, said method to be used by said API, said method comprising the following steps: - receiving a handover intention notify message comprising a session identifier and indicating that said UT intends to perform a session handover, 3 - assigning said session a buffer memory space (213) in a memory (211) of said API (210), - buffering downlink data packets addressed to said UT (240) in said buffer memory (213) as a response on receiving said handover intention notify message. In one embodiment, said radio access network is a wireless data network according to an IEEE 802 standard arranged to authenticate UTs requesting network access and wherein said session identifier is a MAC address of said UT (240) as defined by said IEEE 802 standard. In one embodiment, the method further comprises the step of: - blocking the transmission of downlink session packets to said UT as a response on receiving said handover intention notify message. In one embodiment, said handover intention notify message further comprises an AP-identifier identifying said AP2, indicating a handover of said session to said AP2, wherein the method further comprises the step of: - sending said buffered downlink packets to said AP2 as a response on receiving said handover intention notify message. In one embodiment, the method further comprises the steps of: - receiving an association update message identifying said AP2 and indicating that said UT is associated with said AP2, - sending said buffered downlink packets to said AP2 (220) as a response on receiving said association update message. In one embodiment, the method further comprises the step of: - sending a handover intention notify message to an access router, AR, in said radio access network, said message indicating a handover of said session and comprising a session identifier of said communications session and instructing said AR to buffer downlink data packets addressed to said UT. In one embodiment, said handover notify message which is sent to said AR further comprises an AP-identifier identifying said AP2. According to a second aspect, the invention provides a method for assisting a handover of a user terminal's, UT's communication session from a first access point, API, to a second access point, AP2, in a radio access network, said method to be used by said AP2 wherein said method comprises the following steps: 4 - establishing that said communication session is to be handed over from said API to said AP2, - sending a handover intention notify message to said API indicating a handover of said session and comprising a session identifier identifying said session. In one embodiment, the method further comprises the step of: - sending said handover notify message to an access router, AR, instructing said AR to buffer downlink data packets of said session addressed to said UT (240). In one embodiment, said handover notify message further comprises an AP- identifier identifying said AP2. In one embodiment, said radio access network is a wireless data network according to an IEEE 802 standard, said method further comprising the step of: - authenticating said UT by sending and receiving authentication credentials to/from UT, e.g. by means of the EAP standard. According to a third aspect, the invention provides a method for assisting a handover of a user terminal's, UT's communication session from a first access point, API, to a second access point, AP2, in a radio access network comprising an access router, AR, for routing data packets to/from said UT via said API and/or AP2, said method to be used by said AR and wherein said method comprises the following steps: - receiving a handover intention notify message indicating a handover of said communication session, - buffering downlink data packets of said session in a buffer memory, as a response to said handover intention notify message. In one embodiment, the method comprises the steps of: - receiving an AP-update-message comprising a session identifier identifying said session and an AP-identifier identifying said AP2, said message indicating a handover to said AP2, - forwarding said buffered downlink data packets of said session to said AP2.In one embodiment, said radio access network is a wireless data network according to an IEEE 802 standard being arranged to authenticate UTs requesting access to said network. According to a fourth aspect, the invention provides a method for assisting a handover of a user terminal's, UT's communication session from a first radio access point, API, to a second radio access point, AP2, in a radio access network, said method to be used by said UT and comprising the following steps: 5 a) establishing that said communication session is to be handed over from said API to said AP2, b) identifying a first data frame in a first buffer memory of said UT,, c) extracting a frame sequence number, FSN, from said first packet and storing said FSN in a first memory space of a second buffer memory of said UT, d) forwarding said first packet to an application running on said UT or to a higher level protocol of said UT, e) fetching a next packet from said first buffer memory being the next packet received by said UT after said first packet, f) extracting a frame sequence number from said next packet, FSNNEXT, g) establishing whether said next packet is a consecutive packet of said first packet by comparing said FSNNEXT with said FSN, and, h) storing said FSNNEXT in said first memory space of said second buffer memory and forwarding said "next packet" to a higher layer protocol or to a final application if it was established in step g) that said "next packet" is a consecutive packet of said first packet, and otherwise buffering said "next packet" in a second memory space of said second buffer memory. The step a) of establishing that said communication session is to be handed over from said API to said AP2, may comprise any of the following steps: - a de-association of API, or, - an association of AP2, or, - a handover decision taken by UT according to a certain handover criterion, or, - a handover decision according to a certain handover criterion taken by a network node and signaled to said UT. In one embodiment, the method further comprises the step of: - limiting the size of said second memory space of said second buffer memory by defining a maximum threshold number of stored packets/bytes for said second memory space or defining a maximum allowable storage time for a packet being stored in said second memory space. In one embodiment, data packets received from API and/or AP2 are stored in received chronological in said first buffer memory, being of a FIFO type, wherein said steps a) and e) of identifying a first and second data frame comprise the step of: - reading a data packet from said FIFO memory. 6 In one embodiment, the method further comprises the steps of: - reading a third data packet from said first buffer memory (FIFO) and establishing that said third data packet is a consecutive data packet of the data packet being the last packet forwarded to said application, - forwarding said third data packet to said application or higher protocol layer and updating the first memory space of said buffer memory with the frame sequence number of said third data packet, - establishing that there is at least one stored data packet in said second memory space of said second buffer memory, - searching said first memory space of said second buffer memory for a consecutive data packet of said third data packet. In one embodiment, said radio access network is a wireless data network according to the IEEE 802 standard and wherein said method further comprising the step of: - sending and receiving authentication credentials to/from AP2, for instance according to the EAP standard. According to a fifth aspect, the invention provides a radio access point API allowing a user terminal, UT, access to a radio access network by means of a radio link connection wherein said API comprises means realizing the method according to the first aspect when said API (210) is installed in a radio access network comprising a second access point AP2 and an access router AR. In one embodiment, said means of the access point API comprises a data memory having a first memory space with a first entrance forming a buffer memory for storing downlink packets addressed to said UT, said data memory further having a second memory space with stored program code means which, when loaded in a processing means of said API, make said processing means execute at least one procedure realizing said method. In one embodiment, the API is realised as an access point according to the IEEE 802 standard, arranged to realise said method when said API is installed in a wireless data network according to the IEEE 802 standard, and wherein said API is further arranged to authenticate user terminals requesting access to said wireless data network. According to a sixth aspect, the invention provides a computer program product comprising program code means which, when loaded into a processing means of a first access point API, being installed in a radio access network, make said processing means 7 execute at least one procedure realizing the method according to the first aspect of the invention. In one embodiment, the computer program product includes a computer readable medium having said program code means stored thereon. According to a seventh aspect, the invention provides a radio access point AP2 allowing a user terminal, UT, access to a radio access network by means of a radio link connection wherein said AP2 comprises means realizing the method according to the second aspect when said AP2 is installed in a radio access network comprising a first access point API and an access router AR. In one embodiment, said means of the access point AP2 comprises a data memory having a first memory space with a first entrance forming a buffer memory for storing downlink packets addressed to said UT, said data memory further having a second memory space with stored program code means which, when loaded in a processing means of said AP2, make said processing means execute at least one procedure realizing said method. In one embodiment, the AP2 is realised as an access point according to the IEEE 802 standard, arranged to realise said method when said AP2 is installed in a wireless data network according to the IEEE 802 standard, and wherein said AP2 is further arranged to authenticate user terminals requesting access to said wireless data network. According to an eighth aspect, the invention provides a computer program product comprising program code means which, when loaded into a processing means of a said access point AP2, being installed in a radio access network, make said processing means execute at least one procedure realizing the method according the second aspect of the invention. In one embodiment, said computer program product includes a computer readable medium having said program code means stored thereon. According to a ninth aspect, the invention provides an access router, AR, arranged to route a user terminal's, UT's communication session via a first access point, API (210), and/or via a second access point, AP2, (220), wherein said AR comprises means realizing the method according to the third aspect of the invention when said AR is installed in a radio access network comprising said API and AP2. In one embodiment, said means of the AR comprises a data memory having a first memory space with a first entrance forming a buffer memory for storing downlink packets 8 addressed to said UT, said data memory further having a second memory space with stored program code means which, when loaded in a processing means of said AR, make said processing means execute at least one procedure realizing said method. In one embodiment, the AR is realised according to the IEEE 802 standard, being arranged to realise said method when said AR is installed in a wireless data network according to the IEEE 802 standard, and wherein said AR is further arranged to authenticate user terminals requesting access to said wireless data network. According to a tenth aspect, the invention provides a computer program product comprising program code means which, when loaded into a processing means of an AR according to the ninth aspect and being installed in a radio access network, make said processing means execute at least one procedure realizing the method according to the second aspect of the invention. In one embodiment, the computer program product includes a computer readable medium having said program code means stored thereon. According to an eleventh aspect, the invention provides a UT for assisting a handover of a communication session from a first radio access point, API, to a second radio access point, AP2, in a radio access network, said UT comprising means realizing the method according to the fourth aspect of the invention. In one embodiment, said means of the UT comprises a data memory having a first memory space with a first entrance forming a buffer memory for storing downlink packets addressed to said UT and a second entrance for storing a packet sequence number associated with at least one downlink packet, said data memory further having a second memory space with stored program code means which, when loaded in a processing means of said UT, make said processing means execute at least one procedure realizing said method. In one embodiment, the UT is realised according to the IEEE 802 standard, being arranged to realise said method when said session is routed through a wireless data network according to the IEEE 802 standard, and further arranged to be authenticated by said wireless data network. According to a twelfth aspect, the invention provides a computer program product comprising program code means which, when loaded into a processing means of the UT communicating with a radio access network, make said processing means execute at least one procedure realizing the method according to the fourth aspect of the invention. 9 In one embodiment, the computer program product includes a computer readable medium having said program code means stored thereon. Even though the invention has been summarized above, the invention is defined by the accompanying claims 1-40. BRIEF DESCRIPTION OF THE DRAWINGS The features and advantages of the present invention will become more apparent from the following detailed description of the preferred embodiments with reference to the accompanying drawings, wherein FIG 1 illustrates a network architecture of a conventional radio access network in formofaWLAN, FIG 2 A illustrates a network architecture of a radio access network according to the present invention in form of a WLAN, FIG 2B illustrates an alternative network architecture of a radio access network according to the present invention in form of a WLAN,FIG 3 is an illustrative example of the user plane and control plane protocol stack for the network in FIG. 2A, FIG 4 A and 4B illustrate an example of the method according to some aspects the invention, in form of a flow chart diagram, FIG 5 A and 5B illustrate an example of an algorithm according to one aspect of the invention, in form of a flow chart diagram. FIG 6 A and 6B illustrate a signaling scenario for carrying out the method of the invention described in FIG 4A and B, in the network depicted in FIG 2A. DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS Now, with reference to FIG. 2-6, the present invention shall be described in more detail. In the Figures 1-6, corresponding elements have been given the same reference number along with a figure prefix number, e.g. AP 1,110, in FIG. 1 is referred to as AP 1, 210, in FIG. 2 etc. FIG. 2 A depicts an illustrative example of a radio access network according to the present invention in form of a WLAN 200. The WLAN 200 comprises at least two radio access points, AP 1,210, and AP 2,220, connected to an access router AR 250, optionally via conventional layer 2 switches M-L2S1,230, and M-L2S2,235, as illustrated in FIG. 10 2A. Many possibilities exist; the APs may e.g. be connected directly to AR 250. AR 250 may be connected to other ARs of the WLAN 200 (not illustrated in FIG. 2) and/or to other communication networks 260, such as e.g. the Internet and/or a 3GPP UTRAN. API, 210, and AP2,220, have a respective conventional radio transceiver unit (not illustrated in FIG. 2) connected to a respective antenna, allowing a user terminal, UT, 240, to establish a radio link connection with API, 210, or AP2,220, e.g. in form of a communication session with the WLAN 200. API, 210, AP2,220, UT 240 and AR 250 have a respective conventional processing means, PM, 212,222,242 and 252, normally a CPU, arranged to read and write from/to a respective conventional data memory, M, 211, 221,241 and 251, (e.g. RAMs) in a conventional manner exploiting a data/address/control bus. According to the invention, the respective data memory, M, 211,221, 241 and 251 have a first memory space, 213,223,243 and 253, allocated with stored program code means which, when loaded into the respective processing means, 212,222,242 and 252, make said processing means realize the method according to various aspects of the invention, as described further below. According to the invention, the respective data memory, M, 211,221,241 and 251 have a second buffer memory space, 214,224,244 and 254, allocated, for temporary storage of data packets associated with the UT 240, as explained further below. The UT 240 has a conventional first buffer memory 245, normally a FIFO, in which data packets/frames demodulated by the radio receiver unit of UT 240 are temporarily stored before they are forwarded to a higher protocol layer or to the right higher level final application (e.g. an end user multi-media application such as VoIP, Voice over IP) by the LLC-protocol, in a conventional manner. It is to be understood that the WLAN in FIG. 2 is only an illustrative example and that the invention may be realized in any radio access network, such as a e.g. a 3GPP UTRAN, wherein a 3GPP radio base station Node B corresponds with API, 210, a 3GPP radio network controller, RNC, corresponds with AR 250 etc, as understood by a person skilled in the art. However, the invention is advantageously realized in wireless data networks according to the IEEE 802 standard protocol, such as e.g. Wireless Personal Area Networks (WPAN, IEEE 802.15), Wireless Metropolitan Area Networks (WMAN, IEEE 802.16), Mobile Broadband Wireless Access (MBWA, IEEE 802.20), Wireless Regional Area Networks (WRAN, IEEE 802.22) etc, exploiting the EAP authentication scheme which causes significant delays during handover, since the invention decreases packet delay during handover. 11 FIG. 3 illustrates an example of the user plane and control plane protocol stacks at UT, 240, API, 210, M-L2S1,230 and AR, 250, in Fig. 2A. The protocol stack for M- L2S2,235, is identical with the stack of M-L2S1,230, and M-L2S2,235 has therefore been left out in Fig. 3. The physical layer 1 in Fig. 3, LI, at AR 350, M-L2S1,230 and API, 210, is a conventional Ethernet physical layer, above which a conventional WLAN- MAC layer is installed, i.e. the IEEE 802.3 MAC protocol, defining data ports for the various nodes in a conventional manner. The UT 340 and the API 310 have conventional IEEE 802.11 physical and MAC protocol layers installed, defining a physical radio link layer and data ports for UT 340 and API, 310, in a conventional manner. A conventional link control layer in the form of a IEEE 802.2 LLC-layer is installed above the MAC layer at UT 340, API, 310 and AR 350. The UT 340, API, 310, and AR 350 has further an IP protocol and a UDP/TCP protocol (not illustrated at UT 340) installed above the LLC layer. The UT 340 and AR 350 has further higher protocol layers/applications installed, such as e.g. a multi media application at UT 340 and packet handling applications (e.g. regarding tunneling, routing etc) at AR 350, in a conventional manner. The protocol layers allow the UT 340 and AR 250 to establish logical data connections by conventional protocol layer processing, as a person skilled in the art realizes. For instance, the MAC layer filters out packets intended for the physical device, the LLC layer forwards the packets to the "right" layer/application which in turn may forward the packet further up to a specific layer/application until it is received by the "right" final application or protocol layer. The Access Point Management Entity (APME) at API, 310, in Fig. 3 is not a layered protocol since it represents the main operational program of the API, 310, which implements AP manufacturer's proprietary features and algorithms, and incorporates the Station Management Entity (SME) of IEEE 802.11, e.g., the APME receives Association Request messages from WLAN terminals (UTs) and takes further action accordingly. What is important is that the STAME application at UT 340 and APME application at API, 310, allow the UT 340 and API, 310 to exchange and interpret various control messages, e.g. regarding radio link measurement etc. The Inter Access Point Protocol (IAPP) as specified in IEEE 802.1 If standard is installed in all the AP's of the network, such as at the API, 310, and at AR 350, as illustrated in Fig 3. The IAPP allows the API, 310 and AR 350 to communicate with each other, e.g. for signaling various control messages. The IAPP protocol also allows the API, 210 and AP2,220, to communicate with each other, in a conventional manner. The IAPP entity requires UDP and TCP to 12 distribute its messages as IP packets towards other IAPP entities, e.g. in order to notify a new association of a WLAN terminal at the API, 310. M-L2S1, 330, only functions as a relay of Ethernet frames to the destined stations or other L2 devices. The Ethernet frames may be unicast, multicast or broadcast frames. In one embodiment, the UT 340 has further a WLAN authentication entity installed, e.g. according to the 802. IX EAP/TLS/TTLS/PEAP standard, allowing UT 340 to communicate with a corresponding authentication entity of the WLAN, e.g. in form of a RADIUS or DIAMETER server connected to API, 310, for authentication purposes. The RADIUS or DIAMETER server may e.g. be integrated in AR 350, but many possibilities exist. Many other protocol options exist, as a person skilled in the art realizes, e.g. a LWAPP, (Light Weight Access Point Protocol), could be used instead of the IAPP, or RLC/RNC protocols could be used instead of the LLC/IAPP in case of a UTRAN etc. The RADIUS server normally exploits a conventional RADIUS protocol, e.g. as specified by the documents RFC 3579 (RADIUS support for EAP), RFC 2865, RFC 2869 (RADIUS Extensions), RFC 3576 (Dynamic Authorization Extensions to RADIUS) and RFC 3580 (IEEE 802.1X RADIUS Usage Guidelenes) and the DIAMETER server normally exploits a conventional DIAMETER protocol, e.g. as specified by RFC 3588 (DIAMETER Base Protocol), along with a conventional EAP (Extensible Authentication Protocol), e.g. as defined by standard AAA- (Authenticating, Authorization, Accounting) protocols RFC 2284 - PPP EAP, RFC 4017 (EAP requirements for WLAN) or RFC 3748 (EAP) or RFC 2716 (PPP EAP TLS) or the EAP-TTLS (EAP Tunneled TLS Authentication Protocol), issued by the IETF standard organisation (Internet Engineering Task Force), and may further exploit the EAP-PEAP (Protected EAP Protocol), as a person skilled in the art realises. Now, with reference to FIG. 4 and FIG 6A and B, the method according to the invention shall be described in more detail when realized in the network illustrated in Fig. 2A. It is assumed that each AP maintains its own up-to-date database containing information about the neighbor APs, whose coverage areas may overlap with its own ( normally each AP has a stored list of the IDs, e.g. the WLAN MAC address, of all its neighboring APs. This way, each AP is capable to provide associated UTs with a site report according to IEEE 802.1 Ik specification, which contains information about other APs in proximity to which the UT may roam (or handoff). This may only be achieved if all the involved APs are controlled by the same operator or if special inter-operator agreements exist. 13 In step 4100, there is an ongoing communication session between UT 240 and a Host/peer (e.g. on the Internet 260), wherein e.g. IP-packets are routed over the WLAN by means of the IEEE 802.2 LLC layer (and lower layers), as illustrated by step 1 in FIG 6A. The communication session may e.g. be a conventional VoIP-session (Voice over IP). At any given time, once a WLAN connectivity between UT 240 and API, 210, is established, API, 210, sends a conventional conditional beacon frame request to UT 240, as illustrated by step 2 in FIG 6A. The request indicates the reporting condition that a (periodical) beacon report for API, 210, should be sent by UT 240 to API, 210, when the average RCPI (Received Channel Power Indicator) level falls below a specified threshold value. The UT 240 then performs passive scanning and evaluates the current RCPI level continuously within certain measurement duration. In step 4110 the reporting condition is met, (i.e. RCPI level below threshold is determined), and the UT 240 sends a conventional beacon report to API, 210, illustrated by step 3 in FIG 6B, which thus estimates that the UT 240 will leave the coverage area of API, 210, soon and that a handover is to be effectuated. According to its own AP location database, API, 210, knows that its coverage area (partly) overlaps with the coverage area of one or some neighbor APs, including AP2,220. However API, 210, may not be capable to determine whether or not UT 240 is currently within this overlap area. In step 4120, API, 210 sends a conventional site report to UT 240, illustrated by step 4 in FIG 6A, in order to support the UT 240 to carry out its handover procedure, which site report includes further information about AP2,220, (i.e., its BSSID, PHY type, channel, etc.) and other neighbor APs. This site report informs the UT 240 about the registered neighbor APs, to which the UT 240 can associate according to the user's (subscription) profile. The UT 240 may also receive conventional broadcast beacon frames from APs that do not belong to the UT's 240 operator's network. In step 4130, the UT 240 initiates a conventional passive scanning to find a suitable AP having an adequate RCPI level. By performing passive scanning, the UT 240 may or may not receive beacon frames from the listed neighbour APs, depending on the UT's, 240, geographical location. Assuming that UT 240 receives the beacon frames broadcasted by AP2,220, as illustrated by step 5 in FIG 6A, the UT 240 compares the RCPI level of AP2,220, with the RCPI level of API and decides to change the association from API, 210, to AP2,220, if the RCPI level of AP2,220, exceeds the RCPI level of API, 210, in a 14 conventional manner, i.e. the UT 240 decides to cany out a handover from API, 210 to AP2,220. In step 4140, the UT announces the handover decision by sending a conventional standard Probe Request frame to AP2,220, illustrated by step 6 in FIG 6A. AP2,220, responds with a conventional Probe Response frame, as illustrated by step 7 in FIG 6A, which contains conventional detailed information about AP2,220. According to the invention, the AP2,220, then sends a handover intention notify message to API, 210, and/or AR 250, indicating a handover to AP2,220, and comprising a session identifier uniquely identifying the communication session of UT 240. The handover intention notify message may also comprise identifiers uniquely identifying AP2,220, and/or UT 240, e.g. the WLAN MAC address of AP2,220 and/or UT 240, for reasons explained further below. The session identifier may e.g. be a conventional LLC-connection identifier or a conventional TCP/IP-flow identifier or the WLAN MAC address, or the IP-address, of UT 240. The handover intention notify message may e.g. be realized as a modified IAPP- PROBE.Notify packet, as illustrated by step 8 in FIG 6B, which conventionally also includes the UT's WLAN MAC address, by adding said session identifier in a suitable data field or by simply defining the WLAN MAC address of UT 240 to be said session identifier, as understood by a person skilled in the art. The handover intention notify packet may in this case also have a defined handover identifier field, which may be set to "1" to indicate a handover intention and to "0" otherwise, in order to allow the receiving nodes to make a correct interpretation of the received message. However, the handover identifier may be left out and the receiving nodes (i.e. the API, 210 and AR 250) may be modified/arranged to interpret this handover intention notify message correctly even without such an identifier, as a person skilled in the art realises. This modified IAPP packet, which is sent as UDP/IP packet, is not defined in the IEEE 802.1 If specification, but a person skilled in the art realizes how to realise such an IAPP packet given the described functionality above. The handover intention notify message, in form of the modified IAPP-PROBE. NOTIFY packet, is normally multicasted to a group address towards M-L2S2, but may alternatively be unicasted to API, 210, and/or AR 250, e.g. in case AP2,220 knows that the session in question is currently associated with API, 210, (e.g. signaled by UT 240). The multicast address is according to the invention chosen in such a way that the neighbour APs (including API) and/or AR 250 receive/s the handover intention notify - IAPP packet. The handover intention notify message may alternatively 15 be formed and sent by UT 240 to API, 210, which forwards it to the AR 250, but still other possibilities exist. In step 4150, the API, 210, interprets the received handover intention notify message (e.g. in form of the modified IAPP-PROBE.Notify packet) as the intention of UT 240 to perform a session handover from API, 210, to AP2,220. According to the invention, API, 210, then starts caching (buffering) the downlink IP packets addressed to UT, 240, in memory (213). This reduces the risk of packet loss and the necessary amount of re-transmitted packets, (and thereby the interference level and network signaling) at least in a statistical sense. In one embodiment, in case said handover intention notify message comprises an identifier uniquely identifying AP2,220, e.g. the WLAN MAC address of AP2,220, then API, 210 starts to forward packets to AP2,220, immediately, as a response on receiving said handover intention notify message. This allows for a reduced packet delay and a "smoother" handover. According to an alternative embodiment, API, 210, continues to transmit downlink packets over its radio link to UT 240, and simultaneously forwards duplicate packets to AP2,220, allowing a soft handover realisation. Furthermore, in step 4150, according to one embodiment of the invention, the AR 250 may start to buffer downlink data packets of said session (i.e. addressed to UT 240) in a buffer memory (253) instead of forwarding them to API (210), as a response on receiving said handover intention notify message. This decreases the risk of packet delay/loss/retransmission and, in case the AR 250 forwards the downlink packets only to AP2,220, also reduces the necessary buffer memory size at API, 210, as a person skilled in the art realises. In one embodiment, in case said handover intention notify message comprises an identifier uniquely identifying the AP2,220, e.g. the WLAN MAC address of AP2,220, the AR 250 immediately starts to route downlink packets of said session to AP2,220, instead of API, 210. In an alternative embodiment, AR 250 starts to send downlink packets addressed to UT 240 to both API, 210, and AP2,220, as a response on said handover intention notify message, allowing a soft handover (bi-casting) by duplicate transmission over the respective radio link of API, 210, and AP2,220. This further reduces packet delays during the handover by means of a soft handover realisation. In step 4160, the UT 240 starts the (open system) EAP authentication procedure with AP2,220, and sends a conventional Association Request frame to AP2,220, as illustrated by step 9 in FIG 6B. This triggers an abortion of the radio connectivity between UT 240 and API, 210, in a conventional manner. According to one embodiment of the 16 invention, this also triggers a packet re-sequencing algorithm at UT 240, as illustrated in Fig. 5, and described further below. At the same time, since API, 210, does not receive any beacon reports from UT 240, the API, 210 sends after a certain pre-established time, Tl, a handover intention notify message to AR 250, according to one embodiment of the present invention, e.g. in case API, 210, has not yet sent this message to AP2,220. As already stated, the handover intention notify message comprises a session identifier, e.g. an LLC-connection identifier or IP-connection identifier or the WLAN address, or IP- address, of UT 240, uniquely identifying the data session and may be realized as above described modified IAPP PROBE Notify packet or e.g. as a modified LAPP- LEA VE.Notify packet, as illustrated by step 10 in FIG 6B. A person skilled in the art realizes how form a handover intention notify message with the described functionality by modifying these IEEE 802 standard packets. This provides a possibility of early "warning" to the AR 250 that a handover is to be carried out so that the AR 250 may start buffer session downlink packets as early as possible, which reduces the overall packet delay/loss and network signaling, at least in a statistical sense. Thus, the AR 250 may receive a handover intention notify message from API, 210, and/or AP2,220, and which message arrives first depends on network settings such as Tl etc. Alternately, a handover intention notify message, e.g. in form of a modified IAPP-LEAVE.Notify packet, may be sent from UT 240 to AR 250 via AP2,220, in step 4140. Many possibilities exist. In step 4170, when UT 240 has been associated with AP2,220, AP2 multicasts an association update message, e.g. as a IAPP-ADD .Notify packet, as illustrated by step 11 in FIG 6B, towards M-L2S2. The IAPP-ADD.Notify packet is sent as a multicast UDP/IP packet to notify other APs (e.g. API, 210) and AR 250 about the new association of the particular UT (UT 240 in this case) at the new target AP (i.e.AP2,220). AP2,220, concludes the association procedure by sending a conventional Association Response message to UT 240, as illustrated by step 12 in FIG 6B. According to the invention, the IAPP-ADD .Notify packet includes a session identifier uniquely identifying the session in question and may also comprise a sequence number indicating the packet's validity, along with the WLAN MAC address of UT 240 and/or AP2,220. The multicast IP (or MAC) address should be selected in such a way that only the AR 250 and other relevant APs (i.e. at least API, 210), which are geographically closely located to the sending AP2,220, can receive the IAPP-ADD.Notify packet, in order not to introduce excessive signaling within the WLAN domain. The multicast IP (or MAC) address specified for the L2 update frame 17 must be chosen in such a way that intermediate M-L2Ss and AR 250 can receive it to allow them to update their bridging table, if necessary. In accordance with its multicast IP (or MAC) address the IAPP-ADD.Notify packet will be received by API, 210, and AR, 250. Since AP2,220, is connected to the same M-L2S as API, 210, M-L2S1,230, and AR, 250, need not update their bridging tables. This means that AR, 250, will continue to forward all downlink IP packets for UT 240 through M-L2S1,230, and M-L2S2,235, as it did before receiving the L2 update frame and/or IAPP-ADD .notify packet. According to the invention, the API, 210, and AR 250 starts to forward downlink packets for said session to AP2,220, after having received this IAPP-ADD.Notify packet. This reduces the risk of packet delay/loss and the signaling within the WLAN during the handover, thereby providing a more "smooth" handover. It shall be understood that the present invention may be realised by means of (optionally) modified IAPP-MOVE.Notify packet/s along with IAPP-MOVE RESPONSE.Notify packet/s and/or by means of (optionally) modified IAPP-CASH.Notify packet/s along with IAPP-CASH.Response packet/s, instead of the above described (optionally) modified IAPP-ADD.notify packet/s, as a person skilled in the art realises. The IAPP-MOVE.Notify packet is then preferably unicasted by AP2,220, to API, 210, (as a dedicated message), further decreasing network signaling. In step 4180, after that the AP2,220, has sent the conventional Association Response in step 4170, the conventional 802. IX (EAP) based authentication is then carried out between UT, 240, AP2,220 and the network authentication entity (e.g. a RADIUS entity integrated in AR 250), as illustrated by step 13 in FIG 6B. Downlink and uplink IP packets can be sent over the radio link between UT 240 and the AP2,220, as soon as the EAP authentication procedure is completed. Meanwhile, in step 4180, AP2, 220, receives session downlink packets from AR 250 and/or API, 210, and buffers them in memory 223. All session downlink IP packets (encapsulated as LLC/Ethernet frames), that are still cached in API, 210, and/or not yet transmitted to or acknowledged by UT 240, can be sent directly to AP2,220, as illustrated by step 14 in FIG 6B, or alternatively, removed since their re-transmissions, if necessary, can be conducted between UT 240 and AR 250 through AP2,220. This forwarding procedure is thus carried out while the EAP authentication between UT 240 and AP2,220, and the network authentication entity, is still ongoing since both procedures are independent to each other. Since M-L2S2 has already updated its bridging table, according to their destination MAC address (i.e., UT's WLAN MAC address) the LLC/Ethernet frames can be forwarded through the specified 18 port of M-L2S2,235, to which AP2,220, is connected. The forwarded packets should not be routed through M-L2S1,230. The LLC/Ethernet frames forwarded by API, 210, and AR 250 via M-L2S1,230 (including new downlink packets), are according to the invention cached in memory 223 at AP2,220, and transmitted to UT 240 immediately after the EAP authentication procedure is completed. Memory 223 may be a FIFO memory, first in first out, so that a reordering of the downlink LLC/Ethernet frames must be performed by an algorithm residing at the LLC layer of UT 240, according to the invention. This solves problems regarding the TCP interpreting packets out of order as network congestion, and provides a "smoother" handover, especially important for real time applications such as VoIP. The session handover is concluded after both uplink and downlink IP packets can be exchanged as LLC/Ethernet frames between UT 240 and AR 250 through AP2,220, and the corresponding M-L2Ss, as illustrated by step 15 in FIG 6B. According to one embodiment of the present invention, the completion of the EAP authentication procedure triggers a packet re-sequencing algorithm of UT 240, as illustrated and described further with reference to Fig. 5. FIG 2B illustrates another example of a network architecture for which the invention is applicable. In FIG 2B, we may consider a session wherein the UT 240 is currently associated with API, 210', (i.e., old AP) and the IP packets, that are encapsulated as LLC/Ethernet frames, are being exchanged between UT 240' and AR 250' through the WLAN transmission path. The link between API, 210', and AR, 250', is thus bridged by two M-L2Ss, i.e., M-L2S1,230', and M-L2S2,235'. In contrast to the previous HO-1 scenario described with reference to FIG 2A, AP2,220', is connected to a different M-L2S, i.e., M-L2S3,236. However, both layer 2 switches, i.e., M-L2S2,235', and M- L2S3,236', are connected to the same AR, 250', via M-L2S1,230'. The coverage areas of API, 210', and AP2,220', are assumed to be (partly) overlapped and we consider a situation where UT 240' is going to hand off its current data session from API, 210', to AP2,220',(i.e.,newAP). In general, the session handover procedure for the network in FIG 2B is quite similar with the one illustrated in FIG 2A. The main differences between the procedures relate to steps 4140 and 4170, in the following way: In step 4140: UT 240' sends a Probe Request frame to AP2,220', to "announce" its intention to perform handover to AP2,220'. After responding with a Probe Response frame, AP2,220', sends the (non-standard) IAPP-PROBE.Notify packet, which includes 19 the UT's 240' WLAN MAC address, to a multicast group address towards M-L2S3,236. The multicast address should be chosen in such a way that API, 210', (in general the neighbour APs) and AR, 250', receives the IAPP packet after it is routed through M-L2S3, 236, M-L2S1,230', and M-L2S2,235'. API, 210', interprets the received IAPP- PROBE.Notify packet as the intention of UT 240' to perform a session handover from API, 210', to AP2,220'. API, 210', then starts caching the downlink IP packets for UT, 240', which will be forwarded to AP2,220', as soon as the handover takes place. The AR, 250', may use the information provided in the IAPP-PROBE.Notify packet to make its own decision whenever it receives an IAPP-LEAVE.Notify packet, which includes the UT's WLAN MAC address. In step 4170: After UT, 240', is successfully associated with AP2,220', AP2,220', multicasts the layer 2 update frame and the corresponding IAPP-ADD.Notify packet towards M-L2S3,236. The multicast MAC address of this L2 frame is chosen in such a way that M-L2S1,230', AR, 250', and M-L2S2,235', (and other L2 devices between them) can receive the L2 frame and update their bridging table. In accordance with its multicast IP address the IAPP-ADD.Notify packet will be received by API, 210', and AR, 250'. Since AP2,220', is connected to the same AR, 250' as API, 210', i.e., via M-L2S1, 230', no update of AR's, 250', bridging table is necessary (an update is required at M- L2S3, M-L2S1 and M-L2S2). This means that AR, 250', will continue to forward all the downlink IP packets for UT, 240', through M-L2S1,230', which now routes the packets through M-L2S3,236, (instead of M-L2S2,235'). Furthermore, API, 210', may optionally forward all UT downlink IP packets (encapsulated as LLC/Ethernet frames), that are still cached in API, 210', and/or not yet acknowledged, to AP2,220', through the switches M-L2S2,235', M-L2S1,230', and M- L2S3,236. This is possible because all these three L2 switches have already updated their bridging tables, and can therefore route the LLC/Ethernet frames based on its specified destination MAC address (i.e., UT's WLAN MAC address). The present invention provides a packet re-sequencing algorithm for UT 240, the working method of which shall now be described in more detail, with reference to FIG. 5. The re-sequencing algorithm normally resides at the LLC layer of UT 240 and is advantageously triggered by any conventional authentication procedure taking place between the UT 240 and the radio access network 200. For instance, the re-sequencing algorithm may be triggered by the UT 240 sending a conventional Association Request 20 frame to AP2,220, as described in association with step 4160 above, or e.g. by the completion of the EAP authentication procedure in step 4180, described above. Since the re-sequencing algorithm according to the invention reduces packet delay (reduced packet loss), it is advantageously used in combination with an authentication procedure, which itself is time consuming. Alternatively, the re-sequencing algorithm may be triggered by a handover decision taken by a suitable network node such as API (210) or AP2 (220) or AR, 250, in the network of FIG 2A, and signaled to UT 240, or taken by UT (240). Many possibilities exist and it is obvious for a person skilled in the art how to realize such a triggering. In step 5010, a first data packet addressed to said UT (240) and received from API (210) is fetched in a conventional manner from the first buffer memory 245 of UT 240 in which demodulated packets received over the radio link are temporarily stored before being forwarded to the "right" final higher level application, e.g. a real time multi-media application or a VoIP application. Since the re-sequencing algorithm is triggered before the AP2,220, has started to transmit downlink packets to the UT 240, the algorithm interprets any (i.e it fetches the first "packet in the queue") data packet in said first buffer memory 245 as being a packet from API, 210. In step 5020, a frame sequence number, FSN, is extracted from said first data packet, and said FSN is stored in a first memory space of a second buffer memory 243 of said UT 240. The first and second buffer memories may be physically separated memories, e.g. FIFOs, or may be defined by having different memory spaces allocated in e.g. a RAM 241 of said UT 240, but many possibilities exist. FSN may e.g. be a conventional LLC frame sequence number defined by the LLC protocol or a conventional IP-packet sequence number defined by the IP- or IPSec- or mobile IP-protocol or a conventional TCP- or SCTP (Stream Control Transmission Protocol) frame sequence number. The term "frame sequence number" shall here be interpreted to be any conventional sequence number identifying a packet or the payload thereof. In step 5030, said first packet is forwarded to a higher protocol layer, e.g. to "the right" final application running on said UT (240), e.g. a real time VoIP-application, in a conventional manner, as explained above. In step 5040, the next data packet addressed to said UT (240) is fetched from said first buffer memory 245. 21 In step 5050, the frame sequence number of said next data packet, FSNNEXT, is extracted. In step 5060, it is established whether said next packet is a consecutive packet of the last packet forwarded to the higher protocol layer/final application, referred to as "last forwarded packet" by comparing said FSNNEXT with said FSN. In case of extracted LLC packet sequence numbers, the "next packet" is a consecutive packet of the "last forwarded packet" if FSNNEXT=FSN +1, in case of extracted TCP frame sequence numbers, the "next packet" is a consecutive packet of the "last forwarded packet" if FSNNEXT=FSN +e.g.l460, since a commonly used segment size of TCP-packets comprise 1460 payload frames. The invention is however applicable for any segment size/s and a person skilled in the art knows how to realize said comparison in order to establish whether said "next packet" is a consecutive packet of said "last forwarded packet" or not. If it is established that said "next packet" is a consecutive packet of said "last forwarded packet", then the algorithm proceeds to step 5070, otherwise it proceeds to step 5080. In step 5070, said "next packet" is forwarded to a higher protocol layer/final application of UT 240 and the value of said FSNNEXT is stored in said first memory space of the second buffer memory (243). In one embodiment, said FSN is simply overwritten in said memory 243, thereby minimizing the required size of memory 243. The stored FSNNEXT value thus forms an updated FSN value for future frame sequence number comparisons in order to identify a consecutive packet of said "next packet" and so on. The algorithm then proceeds to step 5100. In step 5080, said "next packet" is buffered in a second memory space of said second buffer memory 243. Advantageously, said next packet" is stored in a list in said second buffer memory 243 on a row corresponding to the difference of FSN and FSNNEXT. For instance, in case of extracted LLC sequence numbers, if said difference is 3, then the "next packet" will be stored on the 3:rd row in this list, thereby minimizing the retrieval time when fetching packets from said second buffer memory 243 at a later stage, since the packets are stored in their correct consecutive order in said list. The re- sequencing algorithm according to the invention normally limits the required size of said second memory space of said buffer memory 243. This can be achieved e.g. by defining a threshold level size of said second memory space of memory 243 and forwarding the stored in front packet (i.e. the packet with the lowest frame sequence number) from said second memory space of buffer memory 243 before buffering the "next packet" in step 22 5080, if said threshold size have been reached. Another possibility is to buffer the "next packet" for a defined maximum time period after which the "next packet" is simply being forwarded to a higher protocol layer/final application. The "next packet" would then be associated with a specific packet timer when it is stored in the second memory space of buffer memory 243 and forwarded from said second memory space when said packet timer elapses (i.e. when the storage time of the "next packet" in said second memory space exceeds said maximum time period). A person skilled in the art realizes how to realize such memory limitations. This memory limitation is advantageous since it also hinders the blocking of the algorithm, as a person skilled in the art realizes. The algorithm then proceeds to step 5090. In step 5090, the further next data packet is fetched from the first buffer memory 245, which packet is treated as above "next packet". The algorithm then returns to step 5050. In step 5100, the second memory space of said second buffer memory 243 is searched in order to find a consecutive data packet, or a cluster of consecutive packets, of the "last forwarded packet" (e.g. forwarded to a real time VoIP application). The search is carried out by checking the (suitable) respective frame sequence number of the stored packets, and comparing these with the frame sequence number of the "last forwarded packet". If such a consecutive packet is found, or a cluster of such consecutive packets, this packet, or cluster of packets, is/are forwarded to a higher protocol/final application (e.g. a real time application such as VoIP) in step 5110 and the corresponding "latest" frame sequence number of the last forwarded packet is stored in the second memory space of said second buffer memory 243, i.e. FSN is updated accordingly, and the algorithm continues to step 5090. If no such a consecutive packet is found, or a cluster of such consecutive packets are found, after having searched through the second buffer memory, the algorithm then proceeds to step 5090. Since the receiver, i.e. the higher layer protocol/final application of UT 240, thus receives less packets out of order in this way, the invention reduces the number of necessary re-transmissions and interference level in the network and also reduces the risk of a reduced data rate, e.g. in the case of a TCP communication session, at least in a statistical sense. Since the invention reduces packet delay during handover, it is particularly advantageous for real time applications, such as e.g. VoIP, especially if an authentication procedure is to be carried out during the handover, such as an EAP procedure between UT 240 and AP2,220. 23 The method and algorithm according to the present invention is normally realized by means of software programs comprising code means which, when loaded in the processing means 252,212,222 and 242 of the AR 250, API, 210, AP2,220 and UT 240 realize said method and/or algorithm. The software programs may be stored on e.g. CD- ROMs, flash memories, etc. allowing an efficient distribution/installation.The principles of the present invention have been described in the foregoing by examples of embodiments or modes/examples of operations, i.e. in the case of a WLAN. However, as already stated, the invention is applicable for any radio access network and many modifications and/or combinations are possible. Therefore, the invention should not be construed as being limited to the particular embodiments/working examples discussed above, and it should be appreciated that variations may be made in those embodiments/working examples by persons skilled in the art, without departing from the scope of the present invention as defined by the appended claims. 24 WE CLAIM: 1, A method for assisting handover of a user terminal's, UT's, (240) communication session from a fust radio access point, API, (210) to a second radio access point, API, (220) in a radio access network, said method to be carried out by said API (210) characterized in that it comprises the following steps: - receiving a handover intention notify message from AP2 f220Y comprising a session identifier identifying said session and indicating that said UT (240) intends to perform a session handover, - assigning said session a buffer memory space (213) in a memory (211) of said API (210), - buffering downlink data packets addressed to said UT (240) in said buffer memory (213) as a response on receiving said handover intention notify message, * continuing transmission of downlink session packets to said UT (240) while buffering the downlink data packets addressed to said UT (240). 2. The method according to claim I wherein said radio access network is a wireless data network according to an IEEE 802 standard and wherein said network is arranged to authenticate UTs requesting network access, and wherein said session identifier is a MAC address of said UT (240) as defined by said IEEE 802 standard. 3. The method according to any of claims 1-2 wherein said handover intention notify message further comprises an AP-identifier identifying said second AP (220), indicating a handover of said session to said AP2 (220), said method further comprising the step of: - sending said buffered downlink packets to said AP2 (220) as a response on receiving said handover intention notify message. 4. The method according to any of claims 1-3 further comprising the steps of: 25 - receiving an association update message identifying said AP2 (220) and indicating that said UT (240) is associated with said AP2 (220), - sending said buffered downlink packets to said AP2 (220) as a response on receiving said association update message, 5. The method according to any of claims I -4 farther comprising the step of; - sending a handover intention notify message to an access router, Ail, (250) in said radio access network, said message indicating a handover of said session and comprising a session identifier of said communications session instructing said AR (250) to buffer downlink data packets addressed to said UT (240). 6. The method according to any of claims 5 wherein said handover notify message further comprises an AP-identifier identifying said AP2 (220). 7. A method for assisting a handover of a user terminal's, UT*s» (240) communication session from a first access point, API, (210) to a second access point, AP2, (220) in a radio access network, said method to be carried out by said AP2 (220) characterized! in that it comprises the following steps: - establishing that said communication session is to be handed over from said API (210) to said AP2 (220). - sending a handover intention notify message to said API (210) and/or an access router, AE, (250) indicating a handover of said session and comprising a session identifier identifying said session and an AP-identifier identifying said AP2 (220), allowing the AR (250) to start routing downlink packets of said session to AP2 (220). 8. The method according to claim 7, further comprising the step of: - sending said handover notify message to an instructing said AR (250) to buffer downlink data packets of said session addressed to said UT (240). 26 9. The method according to any of claims 7-8 wherein said radio access network is a wireless data network according to an IEEE 802 arranged to authenticate UTs requesting network access, said method further comprising the step of: - authenticating said UT (240) by sending and receiving authentication credentials to/from UT (240). 10. A method for assisting a handover of a user terminal's, UTs, (240) communication session from a first access point* API. (210) to a second access point, AP2, (220) in a radio access network comprising an access router, AR, (250), for routing data packets to/from said UT (240) via said API (210) and/or AP2 (220), said method to be carried out by said AR (250) characterized in that it comprises the following steps: receiving a handover intention notify message indicating a handover of said communication session and an AP-identifier identifying said AP2 (220), - buffering downlink data packets of said session in a buffer memory (253), as a response to said handover intention notify message, - forwarding said buffered downlink data packets of said session to said AP2 (220). 11. The method according to claim 10 further comprising the steps of: - routing downlink packets of said session to both API (220) and API (210). 12.The method according to claims 10 or 11 wherein said radio access network is a wireless data network according to an IEEE 802 being arranged to authenticate UTs requesting access to said network. 13. A method for assisting a handover of a user terminal's, UTs, (240) communication session from a first radio access point, API, (210) to a second radio access point, AP2, (220) in a radio access network, said method to be carried out by said UT (240) characterized in that it comprises the following steps: 27 a) establishing that said communication session is to be handed over from said API tosaidAP2, b) fetching a first packet from a first buffer memory (245) of said UT (240) in which buffer memory data packets received from API (210) and/or AP2 (220) are stored, c) extracting a frame sequence number, FSN, from said First packet and storing said FSN in a first memory space of a second buffer memory (243) of said UT (240), d) forwarding said first packet to an application running on said UT (240) or to a higher level protocol of said UT (240), e) fetching a next packet from said first buffer memory (245), said next packet being the next packet received by said UT (240) after said first packet, f) extracting a frame sequence number from said next packet, FSNNEXT, g) establishing whether said next packet is a consecutive packet of said first packet by comparing said FSNNEXT with said FSN, and, h) storing said FSNNEXT in said first memory space of said second buffer memory (243) and forwarding said "next packet" to a higher level protocol or a final application if it was established in step g) that said "next packet'* is a consecutive packet of said first packet, and otherwise buffering said "next packet" in a second memory space of said second buffer memory (243). 14, The method according to claim 13 wherein the step a) of establishing that said communication session is to be handed over from API (210) to AP2 (220), comprises any of the following steps: • a de-association of API (210), or, - an association of AP2 (220), or, - a handover decision taken by UT (240) according to a certain handover criterion, or, - a handover decision according to a certain handover criterion taken by a network node and signaled to said UT (240). 28 HThc method according lo claim 13 or 14 farther comprising the step of: " limiting the size of said second memory space of said second buffer memory 243 by defining a maximum threshold number of stored packets/bytes for said second memory space or defining a maximum allowable storage time for a packet being stored in said second memory space. !6.The method according to any of claims 13-15 wherein data packets received from API (210) and/or AP2 (220) are stored in received chronological order in said first buffer memory (245), said memory (245) being of a FIFO type, wherein said steps a) and c) of fetching a first and second data packet comprise the step of: - reading a data packet from said FIFO memory (245). 17. The method according to any of claims 13-16 further comprising the steps of: - reading a third data packet from said FIFO (245) and establishing that said third data packet is a consecutive data packet of the data packet being the last packet forwarded to said application, - forwarding said third data packet to said application and updating the first memory space of said buffer memory (243) with the frame sequence number of said third data packet, - establishing that there is at least one stored data packet in said second memory space of said second buffer memory (243), - searching said second memory space of said buffer memory (243) for a consecutive data packet of said third data packet, 18. The method according to any of claims 13-17 wherein said radio access network is a wireless data network according to the IEEE 802 standard and wherein said method further comprising the step of: - sending and receiving authentication credentials to/from AP2 (220), for instance 29 according to the EAP standard. 19. A radio access point API (210) allowing a user terminal, UT, (240) access to a radio access network by means of a radio link connection characterized in that it comprises means (213, 214, 212, 211) realizing the method according to any of claims 1-6 when said API (210) is installed in a radio access network comprising a second access point AP2 (220) and an access router AR (250). 20, The access point API (210) according to claim 19 wherein said means comprises a data memory (211) having a first memory space (213) with a first entrance forming a buffer memory for storing downlink packets addressed to said UT (240), said data memory (211) further having a second memory space (214) with stored program code means which, when loaded in a processing means (212) of said API (210), make said processing means (212) execute at least one procedure realizing said method. 21.The API (210) according to claim 19 or 20 realised as an access point according to the IEEE $02 standard wherein said API (210) is further arranged to authenticate user terminals requesting access to said wireless data network. 22. A computer program product comprising program code means which, when loaded into a processing means (212) of a first access point API, (210) being installed in a radio access network, make said processing means execute at least one procedure realizing the method according to any of claims 1-6. 23. A computer program product according to claim 22 including a computer readable medium having said program code means stored thereon. 24. A radio access point AP2 (220) allowing a user terminal, UT, (240) access to a radio access network by means of a radio link connection characterized in that it 30 comprises means (223, 224, 222, 221) realizing the method according to any of claims 7-9 when said AP2 (220) is installed in a radio access network comprising a firs! access point AP1 (210) and an access router AR (250). 25. The access point AP2 (220) according to claim 24 wherein said means comprises a data memory (221) having a first memory space (223) with a first entrance forming a buffer memory (240) for storing downlink packets addressed to said UT, said data memory (211) further having a second memory space (224) with stored program code means which, when loaded in a processing means (222) of said AP2 (220), make said processing means (222) execute at least one procedure realizing said method. 26. The AP2 (220) according to claim 24 or 25 realised as an access point according to the IEEE 802 standard, arranged to realise said method when said AP2 (220) is installed in a wireless data network according to the IEEE 802 standard, and wherein said AP2 (220) is tether arranged to authenticate user terminals requesting access to said wireless data network. 27. A computer program product comprising program code means which, when loaded into a processing means (222) of a second access point AP2, (220) being installed in a radio access network, make said processing means execute at least one procedure realizing the method according to any of claims 7-9. 28. A computer program product according to claim 27 including a computer readable medium having said program code means stored thereon. 29. An access router, AR, (250) arranged to route a user terminal's, UT*s, (240) communication session via a first access point, API (210), and/or via a second access point, AP2, (220), cbameteriaed in that it comprises means (253, 254,252, 31 251) realizing the method according to any of claims 10-12 when said AR (250) is installed in a radio access network comprising said AP1 (210) and AP2 (220). 30. The AR (250) according to claim 29 wherein said means comprises a data memory (251) having a first memory space (253) with a first entrance forming a buffer memory for storing downlink packets addressed to said UT (240), said data memory (251) further having a second memory space (254) with stored program code means which, when loaded in a processing means (252) of said AR (250), make said processing means (252) execute at least one procedure realizing said method, 31. The AR (250) according to claim 29 or 30 realised as an AR according to the IEEE 802 standard, being arranged to realise said method when said AR (250) is installed in a wireless data network according to the IEEE 802 standard, and wherein said AR (250) is further arranged to authenticate use? terminals requesting access to said wireless data network, 32. A computer program product comprising program code means which, when loaded into a processing means (252) of an AR (250) being installed in a radio access network, make said processing means execute at least one procedure realizing the method according to any of claims 10-12. 33. A computer program product according to claim 32 including a computer readable medium having said program code means stored thereon. 34. A UT (240) for assisting a handover of a communication session from a first radio access point, API, (210) to a second radio access point, AP2, (220) in a radio access network, said UT (240) characterized in that it comprises means (241, 242, 243, 244) realizing the method according to any of claims 13-18, 32 35. The UT (240) according to claim 34 wherein said means comprises a data memory (241) having a first memory space (243) with a first entrance forming a buffer memory for storing downlink packets addressed to said UT (240) and a second entrance for storing a frame sequence number associated with at least one downlink packet, said data memory (241) further having a second memory space (244) with stored program code means which, when loaded in a processing means (242) of said UT (240), make said processing means (242) execute at least one procedure realizing said method. 36. The UT (240) according to claim 34 or 35 realised as a UT according to the IEEE 802 standard, being arranged to realise said method when said session is routed through a wireless data network according to the IEEE 802 standard, and wherein said UT (240) is further arranged to be authenticated by said wireless data network. 37,A computer program product comprising program code means which, when loaded into a processing means (242) of a UT (240) communicating with a radio access network, make said processing means execute at least one procedure realizing the method according to any of claims 13-18. 38.A computer program product according to claim 37 including a computer readable medium having said program code means stored thereon. Dated this 22M day of February 2008. 33 The invention provides a method for assisting handover of a communication session associated with a UT (240) from a first radio access point, AP1, (210) to a second radio access point, AP2, (220) in a radio access network, said method to be carried out by said AP1 (210) and comprising the steps of: - receiving a handover intention notify message comprising a session identifier identifying said session and indicating that said UT (240) intends to perform a session handover, - assigning said session a buffer memory space (213) in a memory (211) of said AP1 (210), - buffering downlink data packets addressed to said UT (240) in said buffer memory (213) as a response on receiving said handover intention notify message. The invention further provides a UT (240), an AP1, (210), AP2, (220), an AR, (250) and software program/s co-operating and/or realising the method according to the invention. The invention provides a smoother handover.

Documents:

00785-kolnp-2008-abstract.pdf

00785-kolnp-2008-claims.pdf

00785-kolnp-2008-correspondence others.pdf

00785-kolnp-2008-description complete.pdf

00785-kolnp-2008-drawings.pdf

00785-kolnp-2008-form 1.pdf

00785-kolnp-2008-form 2.pdf

00785-kolnp-2008-form 3.pdf

00785-kolnp-2008-form 5.pdf

00785-kolnp-2008-gpa.pdf

00785-kolnp-2008-international exm report.pdf

00785-kolnp-2008-international publication.pdf

00785-kolnp-2008-international search report.pdf

00785-kolnp-2008-pct request form.pdf

785-KOLNP-2008-(04-08-2014)-ABSTRACT.pdf

785-KOLNP-2008-(04-08-2014)-ANNEXURE TO FORM 3.pdf

785-KOLNP-2008-(04-08-2014)-CLAIMS.pdf

785-KOLNP-2008-(04-08-2014)-CORRESPONDENCE.pdf

785-KOLNP-2008-(04-08-2014)-DESCRIPTION (COMPLETE).pdf

785-KOLNP-2008-(04-08-2014)-DRAWINGS.pdf

785-KOLNP-2008-(04-08-2014)-FORM-1.pdf

785-KOLNP-2008-(04-08-2014)-FORM-2.pdf

785-KOLNP-2008-(04-08-2014)-FORM-3.pdf

785-KOLNP-2008-(04-08-2014)-FORM-5.pdf

785-KOLNP-2008-(04-08-2014)-OTHERS.pdf

785-KOLNP-2008-(04-08-2014)-PA.pdf

785-KOLNP-2008-(11-04-2013)-CORRESPONDENCE.pdf

785-KOLNP-2008-(11-04-2013)-OTHERS.pdf

785-KOLNP-2008-(15-12-2014)-ANNEXURE TO FORM 3.pdf

785-KOLNP-2008-(15-12-2014)-CORRESPONDENCE.pdf

785-KOLNP-2008-(17-06-2014)-ANNEXURE TO FORM 3.pdf

785-KOLNP-2008-(17-06-2014)-CORRESPONDENCE.pdf

785-KOLNP-2008-(18-11-2013)-CORRESPONDENCE.pdf

785-KOLNP-2008-(31-05-2013)-CORRESPONDENCE.pdf

785-KOLNP-2008-(31-05-2013)-FORM 3.pdf

785-KOLNP-2008-CORRESPONDENCE OTHERS 1.1.pdf

785-KOLNP-2008-CORRESPONDENCE-1.1.pdf

785-KOLNP-2008-CORRESPONDENCE.pdf

785-kolnp-2008-form 18.pdf

785-KOLNP-2008-OTHERS-1.1.pdf

785-KOLNP-2008-OTHERS.pdf

abstract-00785-kolnp-2008.jpg

FORM 13 (Change inventors address).pdf