Proactive seamless service provisioning in mobile networks through transferring of application context

Description

BACKGROUND OF THE INVENTION:

Field of the invention

[0001] The present invention relates to mobile communication, and especially to a method for supporting a relocation of an IP session during a network layer handover in a mobile communication system, and a mobile node and a mobile communication system supporting the method.

Description of the Related Art

[0002] A mobile communications system refers generally to any telecommunications system wherein the access point to the system may change when users move within the service area of the system. The mobile communications network is, correspondingly, an access network providing an end user with wireless access to external networks, hosts, or services offered by specific service providers. The service area of the system may comprise different access technologies and several administrative domains.

[0003] The new mobile communication systems have been developed to facilitate widespread use of new applications, also including ones that require more bandwidth and extended transmission sessions compared to earlier technologies. On the other hand, the ubiquitous coverage of current cellular systems has led the end users to expect similar availability of services from the next generations of systems. Therefore, seamless service provisioning for the considerable range of different applications will be a critical issue for the success of the new mobile communication systems.

[0004] In the context of providing wireless access using the Internet Protocol (IP), seamless IP layer mobility refers to the ability to hand over a mobile node (MN) to a new access router (AR) with minimal disruption to the IP connectivity. In the auspices of the Internet Engineering Task Force (IETF), a number of solutions for seamless IP layer mobility have been generated. Mobile IP, as defined in Request for Comments (RFC) 2002, is an enhancement of the Internet Protocol version 4 (IPv4) that adds mechanisms for forwarding Internet traffic to mobile nodes when they are connecting through a network other than their home network. Similar mechanisms have been developed for Internet Protocol version 6, referred to as IPv6. Each mobile node is assigned a permanent home address on its home network and a care-of address that identifies the current location of the device within a network and its subnets. Each time a mobile node moves to a different network, it acquires a new care-of address. A mobility agent (also known as Home Agent) on the home network associates each permanent address with its care-of address.

[0005] As an enhancement to this, fast handover protocol allows a mobile node to configure a new care-of-address before it moves towards a new subnetwork with the aim of being able to use it directly after its connection to the new access router. Consequently, the latency time is minimized and potential loss of packets during handoff is effectively eliminated.

[0006] In the process of establishing the new forwarding path for IP flows, mere creation of connection to the new nodes, however, might not be enough. The nodes along the new path must be prepared to provide similar forwarding treatment to the IP packets. This is especially important for services with particular requirements, such as time sensitive VoIP telephony and video and streaming services, whose successful employment in mobile environment depends heavily upon the ability to minimize the impact of the traffic redirections. A context transfer procedure is a specified method, which aims at provisioning of seamless IP layer connectivity. Context relates to the information transferred from one network entity to another as a means of re-establishing routing related services on a new subnet or a group of subnets. Context transfer thus facilitates seamless transfer of the mobile node's (also known as mobile terminal, station or device) packet session a the new access router while the session can be re-established without having to perform the entire protocol exchange between the new node and the mobile node.

[0007] In order to perform fast handover and context transfer procedures as described above, the Candidate Access Router Discovery (CARD) as described in the IETF Seamoby Working Group Internet Drafts "Candidate Access Router Discovery" of October 2002, and "A Dynamic Protocol for Candidate Access Router Discovery" of October 2002, provides means for discovering the IP addresses of the potential next access routers, and such characteristics of the access routers that may be of interest to an MN when the access router is evaluated as a handover candidate. Through this potential next access router discovery (CARD), at the time of the IP layer handover the potential next access router whose capabilities appropriately match with the requirements of the mobile node may be selected as a target access router. For enhancing the established CARD solution, a protocol for maintaining and updating the information on capabilities of the neighboring access routers in each of the access routers has also been proposed in the prior art.

[0008] However, even though the presented mechanisms allow the mobile node to be able to immediately exchange packets with the new network node and even transfer a session to a new access router without interruption, there are cases where the mobile node may still not be able to continue the service without disruption after the handoff. This is due to the fact that the existing solutions are designed to reveal the existence of a requested capability in the new access router, but they do not disclose whether the pre-discovered resource is available to the transferable session at the time of the handoff. Such temporary lack of appropriate resources is imminent, however, whenever the application requires a specific functionality of a network node, and the successful execution of the application functionality does not allow for breaks in the data transfer.

[0009] For example, let us consider a user of a mobile node MN1 moving along a road and utilizing a streaming application with a specific bandwidth. Through the specified potential next access router discovery the capability of the selected target access router to support said bandwidth may be verified. However, before the initiation of the network layer handover of the mobile node MN1, another mobile node MN2 may have already been handed off to the selected target access router, and the resulting available bandwidth in the access router is lower than what is necessary for a successful continuation of the ongoing session in the mobile node MN1. The result of such a situation is degradation or even teardown of the session of MN1 at handover.

[0010] Chaskar et al. :"QoS support in mobile IP version 6' IEEE BROADBAND WIRELESS SUMMIT (NETWORLD+INTEROP 2001) May 2001, discloses establishing QoS support for a mobile node's packet stream along a new packet path. The document addresses the step of listing the requirements that Mobile IP places on the QoS mechanism, and also highlights shortcomings of some proposals for establishing QoS support for the packet stream in the network, when directly used with Mobile IP.

[0011] As another example, let us consider a user of a mobile node moving along a certain road, and crossing a sequence of access routers and administrative domains. Somewhere along this route the user may also need to cross a technology boundary from 2G to 3G, which means that a specific transcoding functionality is needed because of the different bandwidth capabilities of the traversed networks. However, it is possible that at the time of the actual handover the transcoding functionality is no longer available for the mobile node. It is also possible that the discovery of the transcoding element may take too much time for the relocation to happen without disruption. In such a case, the handoff will severely disrupt the active service.

[0012] Koodli R et al: "Fast Handovers and Context Transfers in Mobile Networks" Computer Communication Review, Association for Computing Machinery. Vol. 31, no. 5, describes recent work enabling fast handovers and context transfer between access routers offering Internet connectivity for mobile (often wireless) nodes.

[0013] EP 1189405 discloses a network system, method and an access server for data transfer between an application server and a user terminal across heterogeneous wired and wireless networks.

[0014] In view of the above, in addition to the comprehensive measures for IP layer mobility and connectivity, a solution for enhancing the seamless relocation of an IP session of a mobile node during a network layer handover is desirable.

SUMMARY OF THE INVENTION:

[0015] Such solution is achieved by a method, a mobile node, and a mobile communication system, which are characterized by what is stated in independent claims 1, 4 and 5. The preferred embodiments of the invention are disclosed in the dependent claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In the following, the invention will be described in greater detail by means of preferred embodiments and with reference to the attached drawings, in which

Figure 1 shows a simplified system architecture that supports information transfer according to an embodiment of the invention;

Figure 2 shows a flow chart of information transfer according to an example of the invention that is not claimed;

Figure 3 shows a diagrammatic representation of application context information;

Figure 4 shows a diagrammatic representation of alternative application context information;

Figure 5 shows a simplified system architecture according to another embodiment of the invention;

Figure 6 shows a flow chart illustrating information transfer in the embodiment of Figure 5;

Figure 7 shows a flow chart illustrating information transfer in a further embodiment of the invention;

Figure 8 shows a logical functional structure of a mobile node; and

Figure 9 shows a logical functional structure of a network node.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS:

[0017] The present invention can be applied to any mobile communication system providing packet data services for mobile nodes within a defined service area, and it can be embodied in various forms. Figure 1 shows a simplified system architecture that supports information transfer according to an embodiment of the invention. Only basic parts of a mobile communication system 1 are illustrated; it is obvious to a person skilled in the art that the system 1 comprises numerous network nodes, functions and structures, which need not be described in greater detail herein.

[0018] The embodiment of the mobile communication system 100 of Figure 1 shows a mobile node 111 in a current cell 112 of a current access point 113. The mobile node 111 can be an IP node that is capable of changing its point of attachment to the network. The access point 113 can be a device that provides an access link to the mobile node 111, typically a link layer (layer 2) device with a radio transceiver. The mobile node may be, for example, a laptop computer, mobile/cellular terminal, personal digital assistant or the like. In the illustrated embodiment, the access point 113 is a base station of the mobile communication system. The cell 112 covers a geographical area within which wireless communication between the access point 113 and the mobile node 111 is possible. A current access router 114 acts as an IP router for the current access point 113. One access router may be connected to one or more access points, and one access network comprises one or more access routers. An access point may be a separate physical entity or co-located with an access router. The mobile node 111 is attached to the current cell 112 but may be simultaneously communicating with access points of surrounding cells 116, 120 in order to be able to change its point of attachment whenever necessary or appropriate. A mobile node 111 travelling in the direction of the arrow, as shown in Figure 1, will at some point of time enter the coverage of the first potential next cell 116 provided by a first potential next access point 115, and coverage of the second potential next cell 120, provided by a second potential next access point 121. A more detailed functional description of a mobile node and of a network node is given with reference to Figures 8 and 9.

[0019] In Figure 1, the current access router 114 is thus connected to the current access point 113. The current access router 114 and the first potential next access router 117 are included in the access network of the current administrative control (ISP-A) 118. A collection of networks under the same administrative control, grouped together for administrative purposes, can constitute one administrative domain. For clarity's sake, only some of the network elements for describing one access network for the administrative domains are shown. It is clear that an administrative domain may comprise several networks that may implement different access technologies, and each access network may comprise a plurality of network elements not shown in the drawing. The second potential next cell 120 is part of another administrative domain, controlled by a second administrative control (ISP-B) 119. A person of ordinary skill in the art would be able to make and use the invention based on the information contained herein.

[0020] The point of attachment of the mobile node 111 can be defined with an IP address. Each mobile node 111 is assigned a home address, and according to the need, one or more care-of-addresses. The home address is an IP address permanently assigned to a mobile node and stored in the home network. When the mobile node is not attached to the home network, the incoming datagrams destined to the mobile node are encapsulated and sent from the home network to the care-of address of the mobile node. In mobile IPv6, mobile nodes may be identified with a home address stored by its home agent.

[0021] A packet data connection between users or between users and applications during which data can be transferred between the participants is called a session. In Figure 1, the mobile node 111 has a session with an application server 123 for data transfer related to a defined communication application. A session can include transmission of any type of data, for example, voice or video data. The mobile nodes may have several simultaneous connections to different service applications.

[0022] A network layer handover provides a procedure by which the mobile node 111 can change its point of attachment to the network. When the mobile node 111 changes its point of attachment from the current access point 113 to another access point connected to the same current access router 114 a network layer (layer 2) handover occurs, which is transparent to the routing at the IP layer. When the mobile node 111 changes its point of attachment from the current access point 113 to another access point 121 connected to another access router 122, also an IP layer handover occurs, preferably as defined by the Mobile IP of the IETF. In one embodiment, the present invention relates to a method and apparatus for minimizing the interference by the IP layer handover at the network layer handover to the ongoing session between the mobile node 111 and the application server 123.

[0023] While the mobile node 111 is in the current cell 112 of the current access point 113 of the current access router 114, the access routers 117, 122, serving the potential next access points 115, 121 of the potential next cells 116, 120, are potential next access routers for the mobile node for to performing an IP level handover. The mobile node 111 can support the wireless interface of the potential next access points 115, 121 connected to the potential next access routers 117, 122 and the coverage of the access points 115, 121 of the potential next access routers (here the cells 116, 120) can overlap with the coverage of the current access router 114 (here cell 112). The potential next access router discovery (CARD), for example as specified in the IETF document D. Trossen et al., "A Dynamic Protocol for Candidate Access Router Discovery", Work In Progress, IETF Internet Draft, October 2002, describes a procedure for identifying the potential next access routers, and also discovering the characteristics of their offered services when considered as a handoff candidate. Based on the information thus available, a group of candidate access routers may be selected, and one of which may be further selected as a target access router (TAR). The selection of TAR typically takes into account the capabilities of potential next access routers, preferences of the mobile node and potential local policies. The invention relates to with information transfer facilitating the selection, and thus the TAR selection as such, does not fall in the scope of the invention.

[0024] In Figure 1, assume that a user carrying the mobile node 111 is moving in the direction of the arrow. The mobile node is engaged to a session with an application server 123 for an ongoing application that requires special services from the mobile network. The special services may relate to any feature or functionality facilitated by a specific access router, for example quality of service for transmission, security level, header compression, availability of transcoding service element, etc. Thereby, for example, the downlink data packets are flowing from the application server 123 through the serving access router 114 under the first administrative control 118 to the serving access point 113, and linked over the radio interface to the mobile node.

[0025] The radio access network comprises defined mechanisms for network level handover control. In order to prepare also for the coming IP level handover, the IP address of the potential next access routers 117 and 122 that connect to the potential next access points 115, 121 are identified. There are several possibilities for this reverse address translation. In some cases the AP beacon comprises the IP address of the access router the AP is connected to. In the prior art, mechanisms are also proposed for caching the mapping between the L2 addresses of the neighbouring access points and IP addresses of the access routers connected to them into dedicated network nodes. The choice of procedure for identifying the potential new access routers may as such vary within the scope of the present claims.

[0026] Referring to the flow chart of Figure 2, at some point, for example a parameter defined point, before the network layer handover, the mobile node 111 generates application context information for the ongoing session with the application server 123. The application context information includes general information on the application semantics, possibly including information on the current state of the session. The application context information on the current state of the session facilitates re-establishment of the session on a new access router without having to re-perform the entire protocol exchange between the mobile node and the new access router. There are various possibilities for generating the application context. The application context information may, for example, be based on descriptive information on session description protocol in the session initiation protocol (SIP) messages between the mobile node 111 and the application server 123. The application context information is provided in a pre-defined format of information elements that allows it to be supported in access routers as well. The format may be according to a specified standard, as the ones recommended by the IETF. Examples of such standards comprise Distributed Component Object Model (DCOM), Simple Object Access Protocol (SOAP), Common Object Request Broker Architecture (CORBA), Enterprise Java Beans (EJB), and Type Length Value (TLV), Extensible Markup Language (XML).

[0027] The application context information is essentially generated in the mobile node, but it may also include information on the correspondent node of the mobile node. Some application functionality of the correspondent node of the mobile node may depend on the location of the mobile node, for example a web server that tailors the content of the delivered web page based on the location of the mobile user. In such a case, for maintaining an IP session, it might be necessary that the application context information includes such information on the correspondent node as well, preferably included in the same message generated by the mobile node.

[0028] It should be noted that the above-mentioned concept of application context information constitutes the framework of the application semantics, which is fundamental for the ongoing session between a mobile node and an application server. The application context information serves as a basis for extracting the required access router capabilities. In some cases, the application context information can be directly mapped onto the required access router capability information, and in some cases further processing is necessary. The procedure of deriving the necessity of a certain access router capability by the mobile node, from the application context information may as such vary within the scope of the claims.

[0029] According to one example, not claimed, part of the information in the dynamically generated application context information relates to such handover related procedures in the access router which, for seamless service, are advantageously performed pro-actively before the network layer handover. Advantageously in this context means that performing the defined procedures pro-actively is not mandatory, but improves the probability of successful relocation of the IP session at handover. Thus, the mobile node includes in the application context information a first indication that enables the access routers to identify the information elements of the application context information that relate to such pro-active procedures. The first indication may comprise, for example, flag bits that are associated with individual information elements of the application context information and which show whether the associated information element relates to a pro-active procedure or not. This is illustrated in Figure 3, where a diagrammatic data block of application context information is illustrated. The data block 300 shows an optional header part 310 for header information that precedes the data, and a payload part 320 for carrying individual information elements data1,..., data 5 of the application context information. The information elements are essentially data fields of equal or different amounts of bits. The data block 300 also comprises a flag part 330, which comprises a group f1, f2, ..., f5 of flag bits, each flag bit 331 of the flag part being associated with an information element 321 of the payload part 320. Various possible methods of formatting information comprising a plurality of information elements and indicating properties attached to them are obvious to a person skilled in the art.

[0030] In step 2-1 of Figure 2, the mobile node 111 sends the application context information to the current access router 114. The sending takes place before the handover procedure is triggered, preferably timed such that several consecutive interactive signalling messages may be exchanged between the serving access router and its neighbouring nodes before the handover is triggered. The optimisation of timing is an implementation related issue that may vary. If the application context information is delivered very early before the handover takes place, there is a risk that the registered information becomes obsolete before it is used. On the other hand, if the time between the context transfer and the handover does not facilitate required procedures in the serving access node and the potential next access node, the success of seamless service may be at risk.

[0031] In step 2-2 of Figure 2, the received application context information is stored in the current access router 114. In step 2-3, the mobile node 111 generates a triggering message for initiating the transfer of application context from the current access router 114 to a potential next access router 122. In this example, the two signals, the one (step 2-1) for delivering the application context information to the current access router 114, and the one (step 2-3) for triggering the application context information from the current access router 114 to one or more potential next access routers are shown as separate signalling events initiated by the mobile node 111. Furthermore, it is anticipated that the time elapsed between the two signalling events (2-1, 2-3) changes dynamically according to the state of the mobile node, i.e. it is dependent on the actual behaviour of the user, as well as on the implementation-specific settings of the network on how it is configured to respond to the behaviour of the user by its mobility management functionality. It is also possible that the two signals are combined, i.e. that the first signal (step 2-1) also acts as a trigger, and the application context information transfer from the current access router 114 is initiated in response of the received application context information from the mobile node 111.

[0032] The triggering message 2-3 thus acts as a request from the mobile node 111 to the serving access router 114 to forward a defined part of the application context information to the potential next access router 122. The format of the triggering message as such may vary, for example appropriate Internet control message protocol (ICMP) messages or user datagram protocol (UDP) messages may be used. The triggering message preferably comprises an indication that allows the current access router 114 to identify the potential next access router 122, to which the application context information transfer should be addressed, typically by the IP address of the new access router. The mobile node 111 may send one triggering message addressing one potential next access router 122, or several triggering messages addressing a group of potential next access routers 117, 122. The mobile node 111 may also generate one combined triggering message that simultaneously addresses a group of access routers 117, 122.

[0033] In step 2-4, the current access router 114 transfers the application context information to the addressed new access router(s). The transferred information can comprise the whole application context information as delivered from the mobile node, or it can comprise a defined part of it. Essentially the transferred application context information comprises the information elements that relate to pro-active procedures which, for seamless service, need to be performed pro-actively before the actual IP handover.

[0034] In step 2-5, the potential next access router 122 analyses the received application context information and, based on the data in the information elements that relate to pro-active procedures, implements them. The necessity of the pro-active procedures may be explicitly indicated in the application context information, and/or the access router may be able to determine the necessity based on the received information. Examples of such pro-active actions include reservation of resources for a defined quality of service, reservation of a defined transcoding entity for the use of mobile node, initialization of defined authentication procedures, or contacting defined communication entities in preparation of the expected handover. These pro-active procedures can be implemented in access routers that receive the application context information, including information elements that relate to pro-active procedures. At this stage the mobile node has indicated an intent to perform an IP layer handover to the new access routed addressed by the triggering message.

[0035] In step 2-6, the mobile node 111 sends a commitment message to the potential next access router that has been selected as a next access router 122. This commitment message 2-6 acts as a confirmation of the intent that was earlier indicated in connection with step 2-4. The format of the commitment message 2-6 may as such vary, for example appropriate Internet control message protocol (ICMP) messages or user datagram protocol (UDP) messages may be used. The commitment message to the selected next access router may be sent before or after the network layer handover, typically before the handover.

[0036] In step 2-7, the next access router 122 implements the handover actions still pending, essentially such handover procedures pending the actual commitment to the next access router which have not yet pro-actively been implemented. Depending on the specified content of the application context information, the division between the pro-active procedures and the procedures may be exclusive, or some procedures of the pro-active procedures may be implemented after commitment, or repeated at the time of commitment. The application context information for the pending handover procedures may already be available in the new access router if the complete context information was transferred in step 2-4. If only partial application context information was transferred in step 2-4, the next access router 122 needs to request the missing application context information from the current access router 114. To facilitate this, the mobile node 111 preferably includes the address of the serving access router 114 to the commitment message to the next access router 122. The next access router 122 requests necessary information from the current access router 114. The protocols and procedures of context transfer as specified by the IETF can be utilized for pulling the information from the serving access router 114 to the new access router 122.

[0037] In the embodiment as described above, the division of handover activities facilitates timely performance of the necessary handover procedures to support seamless continuation of a service for an ongoing application. This reduces the possibility of failures that may otherwise appear, for example, due to the duration of some handover procedures, or due to a requested resource not being available at the time of handover. Correspondingly, the communication related to the application context transfer happens between the access routers, thus reducing the time and radio resource consuming communication over the air interface.

[0038] In Figure 2, the line of MN is marked with slashes to indicate that the time between the steps may vary considerably from case to case. It is clear that if a mobile node is relatively stable, i.e. does not move much, the time between handovers is long, the periods between the steps of application context transfer, as shown, also being long. In these cases, a very predictive approach in timing the application context information transfer may end up in wasting resources in the pro-active reservation procedures, and/or the more dynamic part of the context information becoming obsolete before the actual handover. On the other hand, when a mobile node is moving fast, for example in a train, the consecutive steps need to follow each other very quickly.

[0039] Appropriate timing of the actions may be facilitated by including in the application context information a second indication that enables access routers to determine the temporal validity of the context information. Such second indication may be implemented, for example, as illustrated with the diagrammatic representation of context information in Figure 4. The header part 410, the payload part 420, and the flag part 430 of the data block 400 correspond with the parts of the data block 300 in Figure 3. In addition to these, the data block 400 comprises a lifetime part 440 with lifetime information elements I1...I5, each associated with the individual information elements data1...data5 of the payload part 420 and comprising a sequence of bits to indicate the period of validity of the information in the information elements of the payload part 420. The lifetime information elements I1...I5 may be utilized by the current access router 114 for determining whether the application context information to be transferred to the potential next access router 122 is still valid when the triggering message arrives. The lifetime information elements I1...I5 may also be utilized by the potential next access router 122 for timing the duration of the pro-active action. If, for example, the potential next access router 122 does not receive a commitment message within the lifetime indicated by a defined lifetime element I2, the potential next access router 122 will release an allocated resource associated with the information element data2. Other possible applications of the lifetime information are apparent to a person skilled in the art.

[0040] The mobile node 111 may send the application context information to the current access router 114. Another scenario for providing the information for disposal of the access routers is to arrange a source of application context information into the network side. This example is illustrated in Figure 5. The elements 511 to 523 of Figure 1 correspond directly with the elements 111 to 123 of Figure 1, and will not be re-described herein. According to the current example, a mobile proxy server 524 is further connected to the mobile communication system. In figure 5, the connection of one mobile proxy server 524 is shown via the Internet. It is clear that the mobile communication system may comprise one or more such servers, and that a mobile proxy server 524 can also be located in any of the access networks of the mobile communication system. The mobile proxy server 524 can be a separate physical network element or it can be implemented as a logical unit integrated together within another network element.

[0041] The basic role of a mobile proxy server 524 in the context of this example is to maintain updated personal information on the mobile user. An implementation of this is, for example, a server for executing advanced applications, targeted to facilitate providing of services that are chosen and/or tailored according to the current personal information of the mobile user. Such a mobile proxy server 524 is configured to collect static and dynamic information from various sources and, based on the dynamically changing personal status and context information of the mobile user, provides a defined service or defined services for the user. The collected information may, for example, comprise a user location, user profile input by the user himself or herself, background data retrieved via the Internet, monitoring data on the physical or emotional status of the user, status of the ongoing applications, etc. For example, let us consider that the application is configured to pull out information from a data source for user location information, a data source for event schedules, a data source for league information, and a data source for user monitoring data. Let us assume that the data source for location information indicates the mobile user to be in a football stadium, the data source for event schedules indicates a particular match to take place in the detected football stadium, the data source for league information facilitates listing all the other teams in the league that the particular match may concern and, additionally, user monitoring data that indicates that the user does not feel enthusiastic about the progress of the current game. Based on this information, the application may be configured to trigger a service where it retrieves clippings of goals and scores of the other simultaneously ongoing matches of that league, and offers them to the user.

[0042] In order to maintain relevant dynamic information in the mobile proxy server 524, the mobile node 511 transfers relevant application context information and monitoring information to the mobile proxy server 524. Between the mobile node 111 and the mobile proxy server 524 is a trust relationship, which means that appropriate security measures for ensuring the identity of the communicating parties and the integrity of the exchanged messages are taken in their mutual communication. Such measures may comprise authentication and encryption procedures, generally known to a person skilled in the art. Through this proxy arrangement, updated information for generating the application context information for a mobile node is made available in the network side, thus being available for the purpose of the invented solution.

[0043] Referring to Figure 6, the actions as such are similar to the example of Figure 2, but the logical elements responsible for some individual actions may be different. The mobile proxy server 524 that, as disclosed above, now possesses updated context information, generates (step 6-1) the application context information on the mobile node 511. Since the generic trust relationship essentially exists only between the mobile proxy server 524 and the mobile node 511, necessary security measures need to be followed between the mobile proxy server 524 and the serving access router 514, at least to facilitate authentication of the source of application context information. Such security measures may comprise, for example, signing of the application context transfer message with the mobile node's private key in the mobile proxy server 524, and verification of the signature in the serving access router 514 with the mobile node's public key. Other applicable security measures are apparent to persons skilled in the art. In this example, after the current access router 514 has received the application context information, the procedure continues as described in the first embodiment through steps 6-2 to 6-7. The triggering message 6-3 is preferably given by the mobile proxy server 524, and the commitment message 6-6 is preferably sent by the mobile node 511 itself.

[0044] A further advantage of this example is that the activities for service relocation are allotted to the network side, thereby reducing the more critical communication over the air interface. By this embodiment, also the sensitivity of the handover operations due to a range of mobile node equipment communicating with an equally versatile range of potential next access routers is reduced which, especially in transition between generations of access technologies, is a clear advantage. A still further advantage of synergy is perceived with the application context information being transferred from the mobile node 111 to the mobile proxy server 524 for the purposes of the context-based applications as well.

[0045] In the previous examples, the application context transfer to the potential next access routers was distributed via the current access router 514. In a still further example, the role of the current access router 514 is further reduced by allotting some of its functionality to the mobile proxy server 524. Initially, the mobile node 111 generates the application context information, and transfers it to the mobile proxy server 524, as already described earlier. The mobile proxy server 524 also stores the received information, in addition to the collected and stored information on the access routers, including the information on the neighbouring relationships of the access routers. Based on the information stored in the mobile proxy server 524, and the updating information continually arriving at it, the mobile proxy server 524 may generate the application context information and, instead of delivering it to the current access router, send it directly to the potential new access router 522. Referring to Figure 6, this means that steps 6-1 to 6-4 are replaced by a single step, which illustrates the transfer of application context information from the mobile proxy server 524 to the potential new access router 522. Furthermore, the mobile proxy server 524 may include appropriate security measures therein to facilitate at least authentication of the source of the application context information. The mobile proxy server may also determine the time of triggering the application context information transfer, or the triggering may still be issued by the mobile node itself. This embodiment brings in an additional advantage by compiling the responsibility for the relocation activities more comprehensively into one element in the network side. The solution enhances information distribution, especially because it reduces communication over the air interface and therefore has less restrictions by the limited radio resource. Additionally, the centralized approach that comprises an essentially dedicated server facilitates more advanced and complicated routines for data distribution and target access router selection.

[0046] A further example of the invention, where the proactive procedures are utilized in selection of target access router, is described by referring to Figure 7, and also to the architecture of Figure 5. The availability of resources is naturally one of the essential handover criteria in access network level mobility management. The embodied target access router selection aims at solutions where the access network level criteria are only part of the overall handover criteria, and where especially the interruption by the IP layer handover to the ongoing session between the mobile node and the application server is minimized. In the example, it is assumed that the functionality for target access router selection, hereinafter called as selection module, is located in the current access router. The selection module can be correspondingly implemented in the mobile node 511 or in any applicable network node, also including elements like the mobile proxy server 524 as described earlier. Adjustment of embodied information transfer according to the different locations of the TAR selection module is obvious to a person skilled in the art. Steps 7-1 to 7-4 correspond to the steps 2-1 to 2-4 and will not be re-explained here. Let us, however, assume that the transferred context information 7-4 comprises a requirement on a defined bandwidth for the ongoing application. In step 7-5, the first potential next access router 517 analyses the application context information and detects that the requested bandwidth matches its capability set, but that due to heavy temporary network load such a bandwidth is not presently available for the mobile node 511. The first potential next access router 517 sends back to the current access router 514 a message (step 7-6) that indicates the incapability of this potential next access router to reserve the requested resource for the mobile node.

[0047] The selection module in the current access router 514 may be configured to transfer (step 7-7) the application context information with the requirement on bandwidth for the ongoing application to potential next access routers until it detects that none of the potential next access routers is capable of providing the requested resource. In the example of Figure 7, the application context information is transferred to a second potential next access router 522. The second potential next access router 522 analyses (step 7-8) the received application context information and detects that the requested bandwidth matches its capability set and that such a bandwidth is presently available for the mobile node. The second potential next access router 522 may send back to the current access router 514 a message (step 7-9) that indicates the capability of this potential next access router to reserve the requested resource for the mobile node. Based on this, and potentially some other decision criteria, the selection module in the current access router 514 may determine the second potential next access router 522 to be the target access router (step 7-10) and indicate this to the mobile node (step 7-11). In step 7-12, the mobile node sends a commitment message to the access router that has been selected as a target access router, corresponding to step 2-6 of Figure 2, and in step 7-13, the target access router implements the handover actions still possibly pending, essentially such handover procedures related to actual commitment that have not yet been pro-actively implemented.

[0048] The described information transfer is only one example of the embodied solution. It is clear that, as shown, the requirements for resources can be included in one message, or the communication related to transferring the resource related requirements to the target access router may comprise several consecutive resource reservation messages. Examples of the first alternative include appropriate ICMP or UDP messages, and an example of the latter alternative is resource reservation protocol (RSVP), or the like. However, any applicable message format is possible. Depending on the location of the selection module, the choice for the possible or optimal message format may vary.

[0049] If none of the potential next access routers returns a positive response to the request for resource allocation, the selection module for target access router selection may initiate an error procedure. Such error procedure may, for example, comprise a notification to the user. The error procedure may also comprise reduction of the requirement and repetition of the attempt for pro-active resource allocation with the reduced requirement level.

[0050] Hereinafter, reference is made to a more detailed functional description of the mobile node by referring to Figure 8. The mobile node 111 comprises processing means 81, an element that comprises an arithmetic logic unit, a number of special registers and control circuits. Connected to the processing means are memory means 82, a data medium where computer-readable data or programs or user data can be stored. The memory means typically comprise memory units that allow both reading and writing (RAM), and a memory whose contents can only be read (ROM). The mobile node also comprises an interface block 83 with input means 84 for inputting data by the user for internal processing in the unit, and output means 85 for outputting user data from the internal processes of the unit. Examples of said input means comprise a keypad, or a touch screen, a microphone, or the like. Examples of said output means comprise a screen, a touch screen, a loudspeaker, or the like. The mobile node also comprises a radio unit 86 that is connected to the central processing means, and configured with receiving means for receiving information from the air interface and processing it for inputting to the processing means 81, as well as with transmitting means for receiving information from the processing means 81, and processing it for sending via the air interface. The implementation of such a radio unit is generally known to a person skilled in the art. The processing means 81, memory means 82, interface block 83, and radio unit 86 are electrically interconnected for performing systematic execution of operations on the received and/or stored data according to the predefined, essentially programmed processes of the unit. In a solution according to the invention, the operations comprise the functionality of the mobile node as described above.
Correspondingly, Figure 9 schematically illustrates the basic functional structure of a network node of the communications system as discussed above. Such nodes are referred above, for example, as access points, current access routers, potential next access routers, target access routers, and mobile proxy servers. The network node comprises processing means 91, an element that comprises an arithmetic logic unit, a number of special registers and control circuits. Connected to the processing means are memory means 92, a data medium where computer-readable data or programs or user data can be stored. The memory means typically comprise memory units that allow both reading and writing (RAM), and a memory whose contents can only be read (ROM). The unit also comprises an interface block 93 with input means 94 for inputting data for internal processing in the unit, and output means 95 for outputting data from the internal processes of the unit. Examples of said input means comprise a plug-in unit acting as a gateway for the information delivered to its external connection points. For receiving information on the operator of the network node, the network node may also comprise a keypad, or a touch screen, a microphone, or the like. Examples of said output means include a plug-in unit feeding information to the lines connected to its external connection points. For outputting information to the operator of the network node, it may also comprise a screen, a touch screen, a loudspeaker, or the like. The processing means 91, memory means 92, and interface block 93 are electrically interconnected for performing systematic execution of operations on the received and/or stored data according to the predefined, essentially programmed processes of the unit. In a solution according to the invention, the operations comprise a functionality for implementing the operations as described above.

Claims

1. A method for supporting relocation of an Internet Protocol session, the relocation occurring during a network layer handover in a mobile communication system, characterised in that the method comprises:

sending application context information including information about the Internet Protocol session from a mobile node (111, 511) to a second device (117) before network layer handover, the application context information indicating activities to be executed pro-actively before a network layer handover and including a requested communication requirement;

receiving a first message from the second device at the mobile node, the first message including a first indicator indicating whether or not the second device can satisfy the requested communication requirement;

if the first indicator indicates that the second device cannot satisfy the requested communication requirement, sending the application context information from the mobile node to a third device (122) and receiving a second message from the third device at the mobile node, the second message including a second indicator indicating whether or not the third device can satisfy the requested communication requirement; and

if the second indicator indicates that the third device can satisfy the requested communication requirement, selecting the third device as a target access router for the network layer handover and sending (7-12) a commitment message to the third device, the commitment message confirming an intent to initiate communication with the third device, wherein the second device and the third device are network access routers.

2. The method of claim 1, wherein the method further comprises, if the first indicator indicates that the second device can satisfy the requested communication requirement, sending a commitment message to the second device, the commitment message confirming an intent to initiate communication with the second device.

3. The method of claim 1, further comprising, if the second indicator indicates that the third device cannot satisfy the requested communication requirement, initiating an error procedure at the mobile node, wherein the error procedure comprises a reduction in the requested communication requirement.

4. A mobile node, characterised by comprising:

an output interface (85) configured to send application context information including information about an Internet Protocol session, which is to be relocated during a network layer handover, to a second device (117) before the network layer handover, the application context information indicating activities to be executed pro-actively before the network layer handover and including a requested communication requirement;

an input interface (84) configured to receive a first message from the second device, the first message including a first indicator indicating whether or not the second device can satisfy the requested communication requirement; and

a processor (81) operably coupled to the output interface and the input interface and configured to execute a computer-readable program configured to cause the mobile node to determine if the second device can satisfy the requested communication requirement based on the first indicator;

if the second device cannot satisfy the requested communication requirement, to send the application context information to a third device (122) and to receive a second message from the third device, the second message including a second indicator indicating whether or not the third device can satisfy the requested communication requirement;

to determine if the third device can satisfy the requested communication requirement based on the second indicator; and

if the third device can satisfy the requested communication requirement, to select the third device as a target access router for the network layer handover and to send a commitment message to the third device, the commitment message confirming an intent to initiate communication with the third device, wherein the second device and the third device are network access routers.

5. A mobile communications system (100, 500) comprising two or more access routers (117, 122) and a mobile node (111, 511) according to claim 4.

Ansprüche

1. Verfahren zum Unterstützen der Ortsverlagerung einer Internet-Protokoll-Sitzung, wobei die Ortsverlagerung während einer Netzschicht-Übergabe in einem Mobilfunk-Kommunikationssystem auftritt, dadurch gekennzeichnet, dass das Verfahren Folgendes umfasst:

Senden von Anwendungskontext-Informationen, die Informationen über die Internet-Protokoll-Sitzung von einem Mobilfunkknoten (111, 511) zu einer zweiten Vorrichtung (117) vor der Netzschicht-Übergabe, wobei die Anwendungskontext-Informationen Aktivitäten angeben, die vor einer Netzschicht-Übergabe proaktiv ausgeführt werden müssen und die eine angeforderte Kommunikationsanforderung beinhalten;

Empfangen einer ersten Nachricht von der zweiten Vorrichtung an dem Mobilfunkknoten, wobei die erste Nachricht einen ersten Indikator beinhaltet, der angibt, ob die zweite Vorrichtung die angeforderte Kommunikationsanforderung erfüllen kann oder nicht;

wenn der erste Indikator angibt, dass die zweite Vorrichtung die angeforderte Kommunikationsanforderung nicht erfüllen kann, Senden der Anwendungskontext-Informationen von dem Mobilfunkknoten an eine dritte Vorrichtung (122) und Empfangen einer zweiten Nachricht von der dritten Vorrichtung an dem Mobilfunkknoten, wobei die zweite Nachricht einen Indikator beinhaltet, der angibt, ob die dritte Vorrichtung die angeforderte Kommunikationsanforderung erfüllen kann oder nicht; und

wenn der zweite Indikator angibt, dass die dritte Vorrichtung die angeforderte Kommunikationsanforderung erfüllen kann, Auswählen der dritten Vorrichtung als ein Zielzugangs-Router für die Netzschicht-Übergabe und Senden (7-12) einer Zusage-Nachricht an die dritte Vorrichtung, wobei die Zusage-Nachricht eine Absicht bestätigt, Kommunikation mit der dritten Vorrichtung einzuleiten, wobei die zweite Vorrichtung und die dritte Vorrichtung Netzzugriffs-Router sind.

2. Verfahren nach Anspruch 1, wobei das Verfahren ferner, wenn der erste Indikator angibt, dass die zweite Vorrichtung die angeforderte Kommunikationsanforderung erfüllen kann, das Senden einer Zusage-Nachricht an die zweite Vorrichtung umfasst, wobei die Zusage-Nachricht die Absicht bestätigt, Kommunikation mit der zweiten Vorrichtung einzuleiten.

3. Verfahren nach Anspruch 1, das ferner, wenn der zweite Indikator angibt, dass die dritte Vorrichtung die angeforderte Kommunikationsanforderung nicht erfüllen kann, das Einleiten einer Fehlerprozedur an dem Mobilfunkknoten umfasst, wobei die Fehlerprozedur eine Reduktion in der angeforderten Kommunikationsanforderung umfasst.

4. Mobilfunkknoten, dadurch gekennzeichnet, dass dieser Folgendes umfasst:

eine Ausgabeschnittstelle (85), die dafür ausgelegt ist, Anwendungskontext-Informationen, die Informationen über eine Internet-Protokoll-Sitzung, die während einer Netzschicht-Übergabe ortsverlagert werden soll, vor der Netzschicht-Übergabe an eine zweite Vorrichtung (117) zu senden, wobei die Anwendungskontext-Informationen Aktivitäten angeben, die vor einer Netzschicht-Übergabe proaktiv ausgeführt werden müssen und die eine angeforderte Kommunikationsanforderung beinhalten;

eine Eingabeschnittstelle (84), die dafür ausgelegt ist, eine erste Nachricht von der zweiten Vorrichtung zu empfangen, wobei die erste Nachricht einen ersten Indikator beinhaltet, der angibt, ob die zweite Vorrichtung die angeforderte Kommunikationsanforderung erfüllen kann oder nicht; und

einen Prozessor (81), der betreibbar mit der Ausgabeschnittstelle und der Eingabeschnittstelle verbunden und dafür ausgelegt ist, ein computerlesbares Programm auszuführen, das dafür ausgelegt ist, den Mobilfunkknoten zu veranlassen, basierend auf dem ersten Indikator, zu bestimmen, ob die zweite Vorrichtung die angeforderte Kommunikationsanforderung erfüllen kann;

falls die zweite Vorrichtung die angeforderte Kommunikationsanforderung nicht erfüllen kann, die Anwendungskontext-Informationen an die dritte Vorrichtung (122) zu senden und eine zweite Nachricht von der dritten Vorrichtung zu empfangen, wobei die zweite Nachricht einen zweiten Indikator beinhaltet, der angibt, ob die dritte Vorrichtung die angeforderte Kommunikationsanforderung erfüllen kann oder nicht;

zu bestimmen, basierend auf dem zweiten Indikator, ob die dritte Vorrichtung die angeforderte Kommunikationsanforderung erfüllen kann; und

falls die dritte Vorrichtung die angeforderte Kommunikationsanforderung erfüllen kann, die dritte Vorrichtung als einen Zielzugangs-Router für die Netzschicht-Übergabe auszuwählen und eine Zusage-Nachricht an die dritte Vorrichtung zu senden, wobei die Zusage-Nachricht eine Absicht bestätigt, Kommunikation mit der dritten Vorrichtung einzuleiten, wobei die zweite Vorrichtung und die dritte Vorrichtung Netzzugriffs-Router sind.

5. Mobilfunkkommunikationssystem (100, 500), das zwei oder mehrere Zugriffs-Router (117, 122) und einen Mobilfunkknoten (111, 511) nach Anspruch 4 umfasst.

Revendications

1. Procédé de prise en charge d'une relocalisation d'une session de protocole Internet, la relocalisation se produisant pendant un transfert de couche réseau dans un système de communication mobile, ledit procédé étant caractérisé en ce qu'il consiste à :

envoyer des informations de contexte d'application incluant des informations sur la session de protocole Internet d'un noeud mobile (111, 511) à un deuxième dispositif (117) avant le transfert de couche réseau, les informations de contexte d'application indiquant les activités à exécuter de manière proactive avant un transfert de couche réseau et incluant une condition de communication demandée ;

recevoir un premier message du deuxième dispositif au niveau du noeud mobile, le premier message incluant un premier indicateur indiquant si le deuxième dispositif peut ou non satisfaire la condition de communication demandée ;

si le premier indicateur indique que le deuxième dispositif ne peut pas satisfaire la condition de communication demandée, envoyer les informations de contexte d'application du noeud mobile à un troisième dispositif (122) et recevoir un second message du troisième dispositif au niveau du noeud mobile, le second message incluant un second indicateur indiquant si le troisième dispositif peut ou non satisfaire la condition de communication demandée ; et

si le second indicateur indique que le troisième dispositif peut satisfaire la condition de communication demandée, sélectionner le troisième dispositif comme routeur d'accès cible pour le transfert de couche réseau, et envoyer (7-12) un message d'engagement au troisième dispositif, le message d'engagement confirmant un souhait d'amorcer une communication avec le troisième dispositif, le second dispositif et le troisième dispositif étant des routeurs d'accès réseau.

2. Procédé selon la revendication 1, le procédé consistant en outre, si le premier indicateur indique que le deuxième dispositif peut satisfaire la condition de communication demandée, à envoyer un message d'engagement au second dispositif, le message d'engagement confirmant une tentative d'amorce d'une communication avec le deuxième dispositif.

3. Procédé selon la revendication 1, consistant en outre, si le second indicateur indique que le troisième dispositif ne peut pas satisfaire la condition de communication demandée, à amorcer une procédure d'erreur au niveau du noeud mobile, la procédure d'erreur comprenant une réduction de la condition de communication demandée.

4. Noeud mobile, caractérisé en ce qu'il comprend :

une interface de sortie (85) conçue pour envoyer des informations de contexte d'application incluant des informations sur une session de protocole Internet, qui doit être relocalisée pendant un transfert de couche réseau, à un deuxième dispositif (117) avant le transfert de couche réseau, les informations de contexte d'application indiquant les activités à exécuter de manière proactive avant le transfert de couche réseau et incluant une condition de communication demandée ;

une interface d'entrée (84) conçue pour recevoir un premier message du deuxième dispositif, le premier message incluant un premier indicateur indiquant si le deuxième dispositif peut ou non satisfaire la condition de communication demandée ; et

un processeur (81) couplé de manière fonctionnelle à l'interface de sortie et à l'interface d'entrée, et conçu pour exécuter un programme lisible par ordinateur configuré pour amener le noeud mobile à déterminer si le deuxième dispositif peut satisfaire la condition de communication demandée sur la base du premier indicateur ;

si le deuxième dispositif ne peut pas satisfaire la condition de communication demandée, envoyer les informations de contexte d'application à un troisième dispositif (122) et recevoir un second message du troisième dispositif, le second message incluant un second indicateur indiquant si le troisième dispositif peut ou non satisfaire la condition de communication demandée ;

déterminer si le troisième dispositif peut satisfaire la condition de communication demandée sur la base du second indicateur ; et

si le troisième dispositif peut satisfaire la condition de communication demandée, sélectionner le troisième dispositif comme routeur d'accès cible pour le transfert de couche réseau, et envoyer un message d'engagement au troisième dispositif, le message d'engagement confirmant un souhait d'amorcer une communication avec le troisième dispositif, le second dispositif et le troisième dispositif étant des routeurs d'accès réseau.

5. Système de communication mobile (100, 500) comprenant au moins deux routeurs d'accès (117, 122) et un noeud mobile (111, 511) selon la revendication 4.

Drawing