HK1145105A - Method and system for communication - Google Patents

Description

Communication method and communication system

Technical Field

The present invention relates to a communication system, and more particularly, to a method and system for a connection session switching procedure (connection session handover procedure) based on a client QoS.

Background

Currently, in emerging ubiquitous network environments, IP-based core networks are connected to a large number of wireless and/or wired access networks, providing end users with access to the services, such as live video and audio, with an attendant increase in the number of services provided to end users. The trend in the telecommunications industry is to provide multimedia services with high quality content. Quality of service (QoS) is designed to meet the needs of various applications and to provide different kinds of quality of service, for example, reduction of information loss rate, reduction of delay and delay jitter of information transmission, and for this reason, QoS employs different techniques such as traffic classification, network traffic monitoring, network congestion management, and network congestion avoidance.

Other drawbacks and limitations of conventional approaches will become apparent to one of ordinary skill in the art by comparing such systems with the present invention as set forth below with reference to the drawings.

Disclosure of Invention

The present invention provides a method and/or system for a client QoS-based connection session handoff procedure, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.

According to an aspect of the present invention, there is provided a communication method including:

generating, when service content is received at a user device over a particular transport route, a request to deliver further content for the service over an alternate transport route based on input received over a user interface of the user device; and

receiving, by the user equipment, the requested further content transmitted over the alternate transmission route.

Preferably, the method further comprises generating the request via the user interface by voice and/or touch.

Preferably, the request includes identification information of the specific transmission route.

Preferably, the backup transmission route is determined based on identification information of the specific transmission route.

Preferably, the determination of the alternative transport route is not dependent on any acknowledgement from the correspondent user equipment.

Preferably, the alternate transport route is determined based on an acknowledgement from the correspondent user equipment.

Preferably, a connection session profile (connection session profile) associated with the specific route is updated according to the alternate transmission route.

Preferably, the updated connection session profile is used for the requested transfer of further content via the alternative transmission route.

Preferably, the content of the service is delivered via the alternative transmission route after the relevant resources for the specific transmission route are released.

Preferably, the content of the service is delivered via the alternative transmission route before the associated resources for the particular transmission route are released.

Preferably, the method further comprises requesting a transition from the alternate transmission route to the particular transmission route.

Preferably, the request specifies a particular QoS.

According to an aspect of the present invention, there is provided a communication system including:

one or more circuits for use within a user device, wherein the one or more circuits are operable to generate a request to deliver further content for the service over an alternate transmission route based on input received through a user interface of the user device when service content is received at the user device over a particular transmission route; and

the one or more circuits are operable to receive the requested further content transmitted over the alternate transmission route.

Preferably, the input received through the user interface is generated using one or both of speech and/or touch.

Preferably, the request includes identification information of the specific transmission route.

Preferably, the connection management module (entity) determines the backup transmission route according to identification information of the specific transmission route.

Preferably, the determination of the alternative transport route is not dependent on any acknowledgement from the correspondent user equipment.

Preferably, the alternate transport route is determined based on an acknowledgement from the correspondent user equipment.

Preferably, the connection session profile associated with the particular route is updated in accordance with the alternate transmission route.

Preferably, the updated connection session profile is used for the requested transfer of further content via the alternative transmission route.

Preferably, the content of the service is delivered via the alternative transmission route after releasing the relevant resources for the particular transmission route.

Preferably, the content of the service is transmitted over the alternative transmission route before releasing the relevant resources for the particular transmission route.

Preferably, the one or more circuits are operable to request a transition from the alternate transmission route to the particular transmission route.

Preferably, the request specifies a particular QoS.

Various advantages, aspects and novel features of the invention, as well as details of an illustrated embodiment thereof, will be more fully described with reference to the following description and drawings.

Drawings

Fig. 1 is a block diagram of a communication system capable of client QoS-based connection session handoff according to an exemplary embodiment of the present invention;

FIG. 2 is a block diagram of a server device capable of client QoS based connection session handoff according to an exemplary embodiment of the present invention;

fig. 3 is a block diagram of a user equipment capable of implementing a client QoS-based connection session handoff according to an exemplary embodiment of the present invention;

fig. 4 is a flow diagram of an initial connection session establishment in accordance with an exemplary embodiment of the present invention;

FIG. 5 is a flowchart of an unsolicited connection session handoff initiation procedure in accordance with an exemplary embodiment of the present invention;

FIG. 6 is a flowchart of a requested connection session handoff initiation procedure in accordance with an exemplary embodiment of the present invention;

fig. 7 is a flowchart of a handover execution procedure according to an exemplary embodiment of the present invention;

fig. 8 is a flowchart of a client QoS based connection switching procedure according to an exemplary embodiment of the present invention.

Detailed Description

In accordance with various embodiments of the present invention, a method and system for client QoS based connection session crawling is provided. According to various embodiments of the present invention, a service may be initiated and provided between a pair of user devices. There may be cases where a service route that supports degradation in the network would cause a user of the user device to dissatisfy the quality of received content that is intended to be presented on the user interface of the user device. In various embodiments of the present invention, a user of a user device is provided with the ability to, for example, press or otherwise activate a toggle button or speak into a microphone to request that content be transmitted over an alternate route in a support network. In response to activation of the handover button, the user equipment is capable of generating a request, such as a connection Handover (HO) request, and communicating the request to a Network Management (NM) server, which is connected to the supporting network. Upon receiving the connection handover request, the NM server determines a backup route and communicates the determined backup route information, e.g. the determined IP address of the access router, with the user equipment and the correspondent user equipment, respectively. Upon receiving updated routing information from the NM server, the NM server transmits service information to the user equipment via the determined alternative route. The connection switching request includes session identification information associated with the degraded route, e.g., a session ID associated with the degraded route. When the NM server determines that the received session ID is an existing session ID stored by the NM server, the NM server selects an alternate route to continue the associated service. Depending on system configuration such as user equipment priority, the NM server may determine the backup route in case of communicating with the correspondent user equipment to acknowledge the received connection switch request, or in case of not communicating with the correspondent user equipment to acknowledge the received connection switch request. The connection session profile associated with the degraded route is updated in the NM server according to the determined backup routing information. The NM server uses the updated session profile to deliver the service on the alternate route.

The NM server supports hard or soft connection handover. The NM server transmits the service on the determined backup route after releasing the relevant resources for the degraded route when a hard connection handover is enabled, but for a soft connection handover the NM server transmits the service on the determined backup route before releasing the relevant resources for the degraded route. In addition, the user of the user equipment is allowed to request a switch back from the determined alternative route to the degraded route. The connection switch request specifies a particular QoS for the transmission of the service. For example, the connection switch request indicates that the user desires a better QoS than is currently provided.

Fig. 1 is a block diagram of a communication system capable of client QoS-based connection session handoff according to an exemplary embodiment of the present invention. Referring to FIG. 1, the system of FIG. 1 is shown to include a plurality of Network Management (NM) servers 110a-110e (collectively network management servers 110), a core network 120 including a plurality of routers 120a-120i, a plurality of access networks 130a-130c, and a plurality of clients, such as smart phone 140, laptop 150, and cell phone 160 in the drawing. Each client includes a switch button, e.g., switch buttons 140b through 150c, for triggering a connection session switch based on the client QoS experience presented through the respective headset 150b and/or display 140a, 150a, and/or 150 b.

Each NM server 110, such as NM server 110a, may comprise suitable logic, circuitry, and/or code that may manage aspects of network communications, such as selecting a client, e.g., smartphone 140, to use for accessing an access network of core network 120, determining core network routes for forwarding client packet data streams (packet streams) to intended recipients. NM server 110a is configured to manage client registration and associated client location, e.g., in a mobile IP environment, NM server 110a handles the available IP addresses of the clients and forwards the client packet data streams for each connection session using the appropriate IP address advertised by the associated client. Various client-server signaling messages, such as QoS signaling messages, are processed in NM server 110 a. For example, upon receiving a service request message from a client, such as smartphone 140, NM server 110a routes to form a connection between smartphone 140 and an intended peer client, such as laptop 150.

One type of connection is a physical link, which is implemented by a series of routers on a selected route between two clients. To enable communication over this connection, a session is created by NM server 110a indicating a sequence of client-server interactions within a time frame (timeframe). NM server 110a generates a unique session ID for the created session and transmits it to smartphone 140 and laptop 150, respectively. The associated session profile of the created session includes a number of session parameters, such as type of service (ToS), session ID, address and port, time of validity (live). The session profile is stored in NM server 110a for later use. The session parameters are mainly used to influence the operation of the server. For example, NM server 110a may activate, maintain, update, and/or end a session according to defined session parameters. In this regard, NM server 110a is configured to activate sessions upon service requests of associated clients, such as smartphone 140 and/or laptop 150. When a user of smartphone 140 and/or laptop 150 wants to perform a connection switch, NM server 110a is configured to determine whether one or more backup routes are available. Where one or more routes are available, NM server 110a is able to select an alternate route from the one or more available routes and activate the session accordingly on the selected alternate route. The session profile associated with the old route is updated with the selected alternate route information. The updated session profile is applied to the selected alternate route to facilitate continuation of the service. In addition, NM server 110a may switch the service back to the old route if required by the client.

The core network 120 may comprise suitable logic, circuitry, and/or code that may enable various access networks (e.g., access networks 130a-130c) to connect to external data networks such as PDNs and the internet. There are many routers in the core network 120 connected by links. Each router, such as router 120a, may comprise suitable logic, circuitry, and/or code that may enable forwarding of a packet data stream to an intended recipient. Router 120a is configured to exchange information (e.g., link resource information) between each link and each other. The link resource information includes information of available resources and information of reserved resources. The NM server 110 manages the routers within the core network 120 using a unified approach to allow simple and efficient maintenance.

Various clients (e.g., laptop computer 150) may comprise suitable logic, circuitry, and/or code that may enable various data communications via access network 130a and/or core network 120. For example, notebook computer 150 gains access to multiple services through NM server 110 a. The feature of the notebook computer 150 is to allow the user of the notebook computer 150 to request connection switching according to the user QoS experience by using the switching button 150 c. For example, when a user of a notebook computer is not satisfied with a QoS experience on display 150a and/or headset 150c, the user is allowed to activate switch button 150c and signal NM server 110a to continue service for an alternate route. Notebook computer 150 may also automatically perform the functions associated with toggle button 150c by running internal software. In this regard, the laptop computer 150 may be able to automatically request an alternate route for service based on the relevant QoS conditions (e.g., packet error rate, packet loss rate, latency) on the laptop computer 150. Additionally, if desired, notebook computer 150 is configured to allow switching of the service back to the previously selected route.

In typical operation, smartphone 140 expects to communicate with laptop 150 according to certain QoS requirements. In this regard, smartphone 140 issues a service request to NM server 110a with the required QoS, and NM server 110a then selects a route comprising a set of access routers (e.g., router 120d and router 120c) and a series of intermediate routers (e.g., routers 120e-120 i). NM server 110a establishes a session and generates an associated session ID. NM server 110a then notifies or reports the session ID and corresponding access router address generated by smartphone 140 and laptop 150. When the session is activated, the packet data stream of the service is forwarded on the selected route to the intended recipient. In case, for example, the user of the smartphone 140 is not satisfied with the quality of the received service presented by the display screen 140a, the user of the smartphone 140 then activates the switching function, for example, by pressing the switching button 140 b. Smartphone 140 then sends a signal to NM server 110a to request a connection switch for a better user QoS experience. In response, NM server 110 re-evaluates the core network resources (such as current route allocations). In case the NM server 110 determines that there are no other routes available, the NM server 110 then rejects the received connection switch request and signals to the smartphone 140. Otherwise, NM server 110 selects an alternate route for the service request.

NM server 110a may update the session profile associated with the old route based on the selected backup routing information. The updated session profile is then used for the selected alternate route to continue the session for the requested service. NM server 110 keeps the session from stopping due to a change in routing. In case the user of smartphone 140 is still not satisfied with the QoS performance on the selected backup route, NM server 110a is allowed to switch service back to the previously selected route to continue providing service to the user of smartphone 140, e.g. by switching the route of service from the selected backup route to the previously selected route.

Fig. 2 is a block diagram of a server apparatus capable of implementing a client QoS-based connection switching procedure according to an exemplary embodiment of the present invention. Referring to fig. 2, NM server 200 is shown to include a Server Connection Management Module (SCMM)202, a Server Mobility Management Module (SMMM)204, a Core Resource Management Module (CRMM)206, a Server Processor (SP)208, and a Server Memory (SM) 210.

The SCMM 202 may comprise suitable logic, circuitry, and/or code that may enable monitoring of network connectivity and processing of various connection session signaling messages with clients such as the smart phone 140 and the laptop 150. The connection session signaling information includes various service or QoS request messages. For example, upon receiving a QoS message from, for example, a smartphone 140 via a Server Processor (SP)208, the SCMM 202 is configured to perform operations related to access control and routing control by coordinating with the SMMM 204 and the CRMM 210. In this regard, due to poor user QoS experience, the received QoS information is triggered by, for example, pressing the toggle button 140a on the smartphone 140. SCMM 202 then evaluates the status of the network resources from CRMM 206 and selects an alternate route and/or access network for the requested service. Information on the selected alternate route and/or access network is forwarded back to SP208 for further processing. SCMM 202 is able to select a route by using various algorithms stored in SM 210. For example, routes are selected by maximizing the available bandwidth on the route, or by minimizing the number of routers or hops on the route line. The route may also be selected based on the cost of the route. Since high route costs can guarantee high QoS, high cost routes may be selected to ensure high quality QoS. SCMM 202 is used to maintain and release various routes in core network 120.

The SMMM 204 may comprise suitable logic, circuitry, and/or code that may manage mobility information, such as client addresses and client locations in the system shown in FIG. 1. The SMMM 204 is configured to process mobility information through various client address mappings to ensure a seamless user experience. The mobility information is provided to the SCMM 202, the CRMM 206, the SP208 so that the packet data stream for each active session is sent to the intended recipient notified by the respective client.

The CRMM 206 may comprise suitable logic, circuitry, and/or code that may enable processing of routing resource information according to various QoS requirements and system capabilities. When the CRMM 206 receives the resource request from the SCMM 202, the CRMM 206 evaluates the resource status of the core network 120. The CRMM 206 provides core resource information, such as the status of routes having available resources in the core network 120, to the SCMM 202 for various routing options.

SP208 comprises various types of processors or circuits, such as a microprocessor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), or a combination of processing type devices. In this regard, the SP208 may comprise suitable logic, circuitry and/or code that may be operable to execute a plurality of software instructions stored and downloaded from the Server Memory (SM) 210. In this regard, the SP208 is configured to calculate session IDs for various connection sessions using a variety of algorithms stored in the SM 210. SP208 may communicate various information, such as routing information from SCMM 202, with clients through core network 120 and various access networks, such as access network 130 a.

SM 210 may comprise suitable logic, circuitry, and/or code that may enable storage of data and/or other information for use by NM server apparatus 200. For example, server memory 210 is used to store processing data generated by SP 208. SM 210 is also used to store information such as client user information and session profiles for controlling various operations of NM server device 200. The SM 210 may store necessary information needed to enable or disable a particular service for a particular user equipment. The server memory 210 may also store executable instructions for, for example, establishment of a connection session, updating of a session profile, and/or reestablishing a connection session by reusing the updated session profile. SM 210 includes RAM, ROM, low latency nonvolatile memory such as flash memory, and/or other suitable electronic data storage capable of storing data and instructions.

In operation, NM server 200 receives a service request message from a client (e.g., smartphone 140). The service request message includes information such as QoS requirements associated with the requested service, candidate access networks for use by smartphone 140, and the identity of the intended correspondent client (e.g., laptop 150). SP208 forwards the received service request information to SCMM 202. The connection management module 202 can communicate with a peer user device (e.g., user device 150) to confirm the service request, and if the user device 150 agrees to communicate with the user device 140 for the requested service, then the SCMM 202 coordinates with the SMMM 204 to obtain mobility information for the relevant user device. The SCMM 202 then communicates with the CRMM 206 to determine if there is a route for the available resources in the core network 120. The CRMM 206 then provides the core resource information, which may include information about network nodes (routers), network node memory, and/or links, to the SCMM 202. The SCMM 202 determines the core network routing and/or access network based on the core resource information.

SP 206 generates a session ID for transmitting the packet data stream of the requested service between smartphone 140 and laptop 150. The generated session ID is transmitted to the relevant user equipment together with the selected access network information, and in addition, a relevant session profile including various session parameters such as session ID and service type is generated and stored to the SM 210 for subsequent communication. In the event that the service request received by the SP208 contains an existing session ID stored in the SM 210, the SP208 may signal the SCMM 202 to select an alternate route for the corresponding service. SCMM 202 determines an alternate route. The session profile associated with the current session is updated based on the determined alternate route. The session is activated through the determined alternate route and the updated session profile.

Fig. 3 is a block diagram of a user equipment capable of implementing a client QoS-based connection session handoff procedure according to an exemplary embodiment of the present invention. Referring to fig. 3, the user device 300 is shown to include a Client Application Management Module (CAMM)302, a Client Connection Management Module (CCMM)304, a Network Interface Module (NIM)306, a Client Processor (CP)308, a Client Memory (CM)310, and a User Interface (UI)312, the user interface 312 including a switch button 312a, a microphone (Mic)312b, a display 312c, and a speaker 312 d.

The CAMM 302 may comprise suitable logic, circuitry, and/or code that may manage various application requirements and application states. The various application requirements include information about the best user quality and QoS attributes. The application state indicates that, for example, the corresponding service is reserved and/or restored. The CAMM 302 may also be configured to monitor fixed and variable port numbers used to identify and monitor application data.

The CCMM 304 may comprise suitable logic, circuitry, and/or code that may monitor network connectivity and, for example, available bandwidth, transmission delay, and error rates of connected access networks (e.g., access networks 130a-130 c). The CCMM 304 may be configured to process various connection session signaling messages with the NM server 110a, e.g., to access services with a desired QoS through the CP 308. The connection session signaling messages include various services provided by the CAMM 302 or QoS request messages.

The NIM 306 may comprise suitable logic, circuitry, and/or code that may enable sending and/or receiving wireless signals over an access network communicatively coupled to the core network 120. The access network comprises a wired and/or wireless network, the transmitted wireless signals comprising information from the core network 120, the core network 120 being managed by the NM server 110.

The CP 308 may comprise suitable logic, circuitry, and/or code that may enable control and/or processing of data processing operations for the user equipment 300. CP 308 may process signals to communicate with a supporting communication network, which in this regard include various service signaling messages, such as QoS request messages. For connection session establishment and/or re-establishment, which enables streaming of packet data to the intended recipient via the core network 120, the user equipment 300 may signal the NM server 110. In this regard, the CP 306 is configured to identify a connection switch request input through the switch button 312a and/or the microphone 312b using various mechanisms (e.g., executing software stored within the CM 310). CP 306 then sends the identified connection switch request to NP server 110 through NIM 306.

The user interface 312 may comprise suitable logic, circuitry, and/or code that may enable a user of the user device 300 to be serviced by receiving user input and/or other various interfaces. The user interface 312 includes a toggle button 312a, a microphone (Mic)312b, a display screen 312c, a speaker 312d, and/or any other kind of interface employed by the user device 300. In the event that the user of the user device 300 is not satisfied with the QoS received from the display 312c and/or the speaker 312d, the user is allowed to trigger a connection switch request by activating the switch button 312a and/or by using voice input from the microphone 312 b.

The CM310 may comprise suitable logic, circuitry, and/or code that may store data and/or other information used by the CP 308. For example, using CM310 to store process data generated by CP 308, CM310 may store information, such as user device configuration information, which is used to control various operations of user device 300, such as user-device interactions. Some software and/or code stored in the CM310 is used to translate user input via the toggle button 312a and/or microphone into a trigger event recognizable by the CP 308 to issue a connection toggle request. For example, when the user of the user device 300 is not satisfied with the QoS experience obtained from the user interface 312 (e.g., the display 312c and/or the speaker 312d), the user can activate or press the toggle button 312a for a new connection session. The connection session information received from NM server 110, such as the IP address and session ID of the relevant access router, is stored in memory 310. The CM310 may store execution instructions for running various services on the user device 300.

At run-time, when user device 300 wishes to communicate with a peer user device, the CAMM provides the CP 308 with the client application requirements and/or port number in user device 300 identifying the client application data. Typical client application requirements include the service type of the application and various QoS attributes (such as bit rate and delay constraints associated with the application). CCMM 304 may communicate the identity of the peer device and the IP address of the NM server (e.g., NM server 110a) to CP 308. CP 308 then initiates a service request to NM110a through NIM 306. The service request indicates a request to initiate a session with NM server 110a for a desired QoS, including a desired data rate, latency, and error rate with a peer device. Upon receiving the response from NM server 110a through NIM 306, CP 308 may extract the connection session information from the response and store it in CM 310. When the received response indicates that the point-to-point connection session was successfully established, CP 308 can transmit a service-related packet data stream over NIM 306 according to the established connection session.

The content of the received service is presented to the user via the user interface 312, such as a respective display screen 312c and/or speaker 312 d. When the QoS presented through the display 312c and/or speaker 312d is not satisfactory, the user is allowed to activate the switch button 312a and/or speak speech into the microphone to request a connection switch. CP 308 identifies the connection switch request by executing software and/or code stored in CM310 and forwards the connection switch request to NM server 110a through NIM 306. Upon receiving the relevant response from NM server 110a, CP 308 updates connection session information related to the service based on the received response, and the service continues with the updated connection session. In the event that the user is not satisfied with the QoS of the updated connection session, the user can request a switch back to the previous connection session, for example, by activating the switch button 312 a. The toggle button 312a can be activated by remaining for a predetermined period of time or activated multiple times within a particular period of time.

Fig. 4 is a flow chart of initial connection session establishment according to an exemplary embodiment of the present invention. Referring to fig. 4, exemplary steps begin in step 402 when a user device, such as smartphone 140, desires to establish a connection session with a peer user device, such as laptop 150. The smartphone 140 sends a connection session establishment request to the NM server 110a, the request including various information, e.g. a client application QoS profile (client application requirements), an identity, e.g. an IP address of the NM server 110a, a port number used to identify application data, and/or a candidate access network for the smartphone 140.

Upon receiving the request, NM server 110a communicates with notebook computer 150 to acknowledge receipt of the received request in step 404. In step 406, notebook computer 150 accepts the received request and notifies NM server 110a of the decision. In step 408, NM server 110a may determine whether notebook computer 150 is willing to accept the request. In case notebook 150 accepts the request, then step 410 is entered where NM server 110a determines if there are network resources available in core network 120 for the requested service. In case NM server 110a determines that there are available network resources in core network 120 for the requested service, then step 412 is entered where NM server 110a determines a route, generates a session ID, and creates a session profile. The session profile may include the determined routing information, the generated session ID, a time-of-live (time-of-live), a type of service, and/or a QoS profile. The created session profile is stored in SM 210.

NM server 110a signals the access router and the address and session ID to smartphone 140 and laptop 150, respectively, in step 414. In step 416, smartphone 140 may extract the relevant access router address and session ID from the received response information from NM server 110 a. In step 418, notebook computer 150 may extract and store the relevant access router address and session ID from the received response information from NM server 110 a. In step 408, in case NM server 110a determines that notebook computer 150 is not willing to accept the request, NM server 110a then sends a rejection message to smartphone 140. In step 410, NM server 110a may signal a rejection to smartphone 140 when NM server 110a determines that no resources are available for the request.

Fig. 5 is a flowchart of an unsolicited connection session handoff initiation procedure in accordance with an exemplary embodiment of the present invention. Referring to fig. 5, exemplary steps begin at step 502, where smartphone 140 is in an active connection session state transmitting a packet data stream with laptop 150. The smart phone 140 is a master user device and the laptop computer 150 is a slave user device. Smartphone 140 may determine whether a connection handoff is required based on a user QoS experience obtained from a user interface (e.g., display 140a of smartphone 140). In step 504, smartphone 140 determines whether a connection switch request requesting connection switching is received via switch button 312a and/or microphone 312 b. In case a connection handover is requested, step 506 is entered, and smartphone 140 sends a connection handover request to NM server 110, comprising e.g. the currently relevant session ID.

In step 508, NM server 110 recognizes that the received session ID is an existing session ID stored in SM 210. NM server 110 determines for the received connection handover request whether there are resources available to core network 120 in step 510. In case there are available network resources for this connection handover request, then step 512 is entered, where NM server 110 selects a new route. Based on the selected new route, route-related information in the session profile associated with the old connection is updated. In step 514, NM server 110 sends a connection switching response and corresponding access router address to smartphone 140 and laptop 150, respectively. In step 516, the smartphone 140 extracts the corresponding access router address and session ID and stores it in the CM 310. In step 518, notebook computer 150 extracts the corresponding access router address and session ID and stores it in CM 310. The connection switch initiation flow ends and the exemplary steps return to step 502.

In step 510, NM server 110a sends a signal to smartphone 140 to reject in case NM server 110a determines that there are no available resources for the request.

Fig. 6 is a flow diagram of a requested connection session handoff initiation procedure in accordance with an exemplary embodiment of the present invention. Referring to fig. 6, exemplary steps begin at step 602, where smartphone 140 is in an active connection session state transmitting a packet data stream with laptop 150. The smartphone 140 and the laptop have the same priority level in requesting connection switching based on terminal QoS. In step 604, the user device, such as smartphone 140, determines whether a connection switch request has been received via switch button 312a and/or microphone 312 b. In case a connection handover is requested, then step 606 is entered, smartphone 140 sends a connection handover request to NM server 110, including e.g. the currently relevant session ID. In step 608, NM server 110 determines that the received session ID is an existing session ID stored in SM 210. In step 610, notebook computer 150 determines whether the request was accepted and informs NM server 110a of the determination. NM server 110 determines for the received connection handover request whether there are resources available to core network 120 in step 612. In case network resources are available for this connection handover request, then step 614 is entered where NM server 110 selects a new route. Based on the selected new route, route-related information in the session profile associated with the old connection is updated. In step 616, NM server 110 sends a connection switching response and corresponding access router IP address to smartphone 140 and laptop 150, respectively. In step 618, the smartphone 140 extracts the corresponding access router IP address and session ID and stores it in the CM 310. In step 620, the notebook computer 150 extracts the corresponding access router IP address and session ID and stores them in the CM 310. The connection switch initiation flow ends and the exemplary steps return to step 602.

In step 612, in case NM server 110a determines that there are no available resources for the request, NM server 110a sends or informs smartphone 140 of the rejected signal.

Fig. 7 is a flowchart of a handover execution procedure according to an exemplary embodiment of the present invention. Referring to fig. 7, exemplary steps begin at step 702, where NM server 110 completes the connection switch initiation procedure, such as described in connection with fig. 5 and 6, and NM server 110 reestablishes a session on the selected new route using the updated session profile at step 704. In step 706, NM server 110 determines whether a hard connection handover should be established. Hard-wired handover is a connection-switching scheme in which a session is resumed on a newly selected route after stopping on an old route. In the case that a hard-wired handover is required, step 708 is entered and the packet data flow on the old route is suspended. In step 710, the old connection is released. In step 712, the packet data flow resumes on the new connection. The connection switching procedure ends at step 718. In step 706, in the event that a hard-wired handoff is not required, then step 708 is entered where the packet data flow on the old route is suspended. In step 714, the packet data flow starts on the new route. In step 716, resources for the old route are released. The connection switching procedure ends at step 718.

Fig. 8 is a flowchart of a client QoS based connection switching procedure according to an exemplary embodiment of the present invention. Referring to fig. 8, the exemplary steps begin at step 802, where a connection session between smartphone 140 and laptop 150 has been established and begins to transmit a packet data stream for the service. Thd HO represents a threshold value of the number of connection handover switching times set for the service, and the parameter i is a connection handover counter and is initialized to i ═ 0. In step 804, the user of the user equipment (e.g., mobile phone 140 and laptop 150) determines whether the terminal QoS as seen, for example, from display screen 140 and/or display screen 150a is satisfactory. In case, for example, the user of the smartphone 140 is not satisfied with the terminal QoS of the received service presented by the display screen 140a, then step 806 is entered, where the user of the smartphone 140 activates or presses the switch button 140b to conduct a new connection session by means of the connection switching procedure as described in connection with fig. 5, 6 and 7. The connection switch counter is incremented by 1. In step 808, NM server 110 determines if i > Thd _ HO. When i is not greater than Thd _ HO, then step 810 is entered and the packet data flow transmission and exemplary steps return to step 804.

In step 804, with the smartphone 140 satisfied with the QoS of the content presented by the display 140a, then exemplary steps continue in step 810. In step 808, when i is greater than Thd HO, then step 812 is entered where the NM server may determine if the user equipment would like to use the previous connection session. In case the relevant user device (e.g. smartphone 140 and/or laptop 150) is willing to continue service using the previous connection session, then step 814 is entered where NM server 110 switches the current connection session back to the previous connection session to continue the transfer of the packet data stream. The exemplary steps return to step 804. In step 812, in case the smartphone 140 and/or the laptop 150 is not willing to continue the service using the previous connection session, then continuing step 816, the NM server 110 stops the transmission of the packet data stream, the related connection session stops and the service between the smartphone 140 and the laptop 150 is suspended.

Aspects of a method and system for client QoS based connection session handoff are provided. According to embodiments of the present invention, initiating and providing service between one user device (e.g., smartphone 140) and an opposite user device (e.g., laptop), there may be situations where degraded routing in the support network results in the user of the laptop 150 device being dissatisfied with the quality of service of the content received and presented on the user interface (e.g., display screen 150a and/or headset 150 b).

A user of notebook computer 150 can, for example, press or otherwise activate switch button 150c or make a voice request to a microphone to request that content be delivered through an alternate route in core network 120. In response to activation of the switch button 150c, the notebook computer 150 generates a request (e.g., a connection switch (HO) request) and sends the request to the NM server 110 connected to the core network 120. NM server 110, upon receiving the connection switching request, NM server 110 determines an alternate route and transmits the determined alternate route information (e.g., the determined IP address of the access router) to laptop 150 and smartphone 140, respectively. Upon receiving updated routing information from NM server 110, NM server delivers service to notebook computer 150 via the determined alternate route. The connection switch request includes connection identification information associated with the degraded route, e.g., a session ID associated with the degraded route. When NM server 110 determines that the received session ID is an existing session ID stored in NM server 110, NM server 110 selects an alternate route to continue the associated service. Depending on the system configuration, e.g. priority of the user equipment, NM server 110 may determine the alternative route in case of communicating with smartphone 140 to acknowledge the received connection switch request or in case of not communicating with smartphone 140 to acknowledge the connection switch request as described in fig. 6 and 5. In the NM server 110, the connection session profile associated with the degraded route is updated according to the determined backup routing information. NM server 110 uses the updated session profile to transport the service on the alternate route. NM server 110 supports hard or soft connection handoffs. As depicted in fig. 7, when a hard connection handover is enabled, the NM server 110 transmits the service on the determined backup route after releasing the relevant resources for the degraded route, whereas for a soft connection handover, the NM server 110 transmits the service on the determined backup route before releasing the relevant resources for the degraded route. In addition, the user of laptop 150 and/or smartphone 140 is allowed to request a switch back from the determined alternate route to the degraded route. The connection switch request indicates a particular QoS for the service delivery, e.g., the connection switch request indicates that the user desires to provide a better QoS than the current QoS.

Another embodiment of the present invention provides a machine and/or machine-readable storage and/or medium, having stored thereon, a machine code and/or a computer program having at least one code section executable by a machine and/or a computer, thereby causing the machine and/or computer to perform a client QoS-based connection session handoff procedure as described herein.

The present invention can be realized in hardware, software, or a combination of hardware and software. The present invention can be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software could be a general purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.

The present invention can also be implemented by a computer program product, which comprises all the features enabling the implementation of the methods of the invention and which, when loaded in a computer system, is able to carry out these methods. The computer program in this document refers to: any expression, in any programming language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following a) conversion to another language, code or notation; b) reproduced in different formats to implement specific functions.

While the invention has been described with reference to an exemplary embodiment, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the claims. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the invention without departing from the scope thereof as claimed. Therefore, it is intended that the invention not be limited to the particular embodiment disclosed, but that the invention will include all embodiments falling within the scope of the appended claims.

Claims (10)

1. A method of communication, the method comprising:

generating, when service content is received at a user device over a particular transport route, a request to deliver further content for the service over an alternate transport route based on input received over a user interface of the user device; and

receiving, by the user equipment, the requested further content transmitted over the alternate transmission route.

2. The method of claim 1, further comprising generating the request via the user interface by voice and/or touch.

3. The method of claim 1, wherein the request includes identification information of the particular transmission route.

4. The method of claim 1, wherein the alternate transmission route is determined based on identification information of the particular transmission route.

5. The method of claim 1, wherein the determination of the alternate transport route is independent of any acknowledgement from the peer user equipment.

6. The method of claim 1, wherein the alternate transmission route is determined based on an acknowledgement from a peer user device.

7. A communication system, the system comprising:

one or more circuits for use within a user device, wherein the one or more circuits are operable to generate a request to deliver further content for the service over an alternate transmission route based on input received through a user interface of the user device when service content is received at the user device over a particular transmission route; and

the one or more circuits are operable to receive the requested further content transmitted over the alternate transmission route.

8. The system of claim 7, wherein the input received through the user interface is generated using one or both of speech and/or touch.

9. The system of claim 7, wherein the request includes identification information of the particular transmission route.

10. The system of claim 9, wherein the connection management module determines the alternate route based on identification information of the particular transmission route.