WO2004077745A2 - Session maintenance method and mobile nodes for heterogeneous network - Google Patents

Session maintenance method and mobile nodes for heterogeneous network Download PDF

Info

Publication number
WO2004077745A2
WO2004077745A2 PCT/EP2004/050227 EP2004050227W WO2004077745A2 WO 2004077745 A2 WO2004077745 A2 WO 2004077745A2 EP 2004050227 W EP2004050227 W EP 2004050227W WO 2004077745 A2 WO2004077745 A2 WO 2004077745A2
Authority
WO
WIPO (PCT)
Prior art keywords
session
user
mobile nodes
section
mobile node
Prior art date
Application number
PCT/EP2004/050227
Other languages
French (fr)
Other versions
WO2004077745A3 (en
Inventor
Tomohiro Ubukata
Hidehiko Eguchi
Original Assignee
Motorola Inc
Motorola Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Motorola Inc, Motorola Limited filed Critical Motorola Inc
Publication of WO2004077745A2 publication Critical patent/WO2004077745A2/en
Publication of WO2004077745A3 publication Critical patent/WO2004077745A3/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters

Definitions

  • the present invention relates to a session maintenance method and mobile nodes for use in a heterqgeneous network.
  • a heterogeneous network is conceived as one basic configuration for a future mobile communication network.
  • a common core network CCN
  • RANs radio access networks
  • MNs Mobile nodes within the heterogeneous network provide multimedia communication services by selecting an optimum radio access network in accordance with the user's purpose of use and environment and dynamically switching from one radio access network to another as needed.
  • Nonpatent Document 1 Session Initiation Protocol (http: //www. ietf . org/rfcZrfc3261.txt)
  • the present invention has been made to solve the above problems, and provides a session maintenance method and mobile nodes for use in a heterogeneous network, thereby making it possible to dynamically readjust session parameters without requiring any complicated process for an application while communication is maintained for the mobile nodes within the heterogeneous network.
  • One aspect of the present invention provides a session maintenance method for use in a heterogeneous network that comprises a plurality of different access networks and a core network interconnecting the access networks.
  • Mobile nodes in the heterogeneous network are provided with an agent section that generates new session parameters for session maintenance.
  • the session maintenance method comprises the steps of transmitting, when new session parameters for maintaining a session for the mobile nodes are generated by the agent section of a first mobile node in a situation where a session is established for the mobile nodes, the new session parameters to the agent section of a second mobile node; causing the agent section of the second mobile node to receive the new session parameters, to analyze the new session parameters, and to transmit the analyzed session parameters to the agent section of the first mobile node; and causing the agent sections of both the first and second mobile nodes to maintain the session in accordance with the new session parameters .
  • the agent section generates new session parameters in accordance with certain information while a session is established, and transmits the generated session parameters to a remote party to maintain communication.
  • certain information represents a dynamic switch from one radio access network to another (e.g., from a wireless LAN to a Personal Handyphone System) , which is made by the prior art described earlier.
  • the remote party targeted for communication may be provided with an agent section so that new session parameters are received rom that agent section to maintain communication.
  • the agent sections of both parties involved in communication may exchange information and determine the session parameters to maintain communication.
  • Another aspect of the present invention provides a session maintenance method for use in a heterogeneous network that comprises a plurality of different access networks and a core network interconnecting the access networks.
  • Mobile nodes in the heterogeneous network are provided with an agent section that generates new session parameters for session maintenance.
  • the session maintenance method comprises the steps of establishing a session for the mobile nodes by causing applications provided for the mobile nodes to generate and transmit the information for session establishment; terminating the session for the mobile nodes by causing applications provided for the mobile nodes to generate and transmit the information for session termination; transmitting, when new session parameters for maintaining the session for the mobile nodes are generated by the agent section of a first mobile node in a situation where the session is established for the mobile nodes, the new session parameters to the agent section of a second mobile node; causing the agent section of the second mobile node to receive the new session parameters, to analyze the new session parameters, and to transmit the analyzed session parameters to the agent section of the first mobile node; and causing the agent sections of both the first and second mobile nodes to maintain the session in accordance with the new session parameters.
  • session establishment and termination are performed end-to-end between applications.
  • session maintenance is performed by the agent section instead of the applications.
  • the method for session maintenance is as stated earlier.
  • mobile nodes for use in a heterogeneous network that comprises a plurality of different access networks and a core network interconnecting the access networks are provided with an agent section that generates new session parameters for session maintenance .
  • the agent section described above is incorporated so that session maintenance can be achieved by updating the session parameters without causing an application to perform a complicated process.
  • FIG. 1 is a schematic diagram illustrating the configuration of one embodiment of a heterogeneous network according to the present invention.
  • FIG. 2 is a block diagram illustrating the configuration of a mobile node.
  • FIG. 3 is a sequence chart illustrating a session establishment/termination process .
  • FIG. 4 is a sequence chart illustrating a session maintenance process.
  • Fig. 1 schematically illustrates the configuration of one embodiment of a heterogeneous network according to the present invention.
  • the heterogeneous network 10 comprises a plurality of radio access networks 11, an IP network 12 that serves as a common core network (CCN) , and mobile nodes (MNs) 13.
  • the plurality of radio access networks 11 comprise a plurality of different radio access networks.
  • the plurality of different radio access networks comprise, for instance, wireless LANs (WLANs or wireless local area networks) 11a, Personal Handyphone Systems lib, and cellular phones lie.
  • WLANs wireless local area networks
  • cellular phones lie.
  • a plurality of service areas for the networks lla-llc coexist within the plurality of radio access networks 11.
  • the IP network 12 interconnects the networks lla-llc within the plurality of radio access networks 11.
  • the IP network 12 is provided with a CCN server 12a, which manages the connection among the networks lla-llc.
  • the CCN server 12a encrypts the session information required for establishing, maintaining, and terminating a session between the mobile nodes 13 and other information necessary for communication, and transmits the encrypted information to the mobile nodes 13.
  • the CCN server 12a exercises session management and performs a necessary process for permitting a provider, for instance, to perform billing of the users of the mobile nodes 13.
  • a mobile node 13 communicates with another mobile node 13 in the same network lla-llc or a certain mobile node 13 in another network lla-llc. Further, a mobile node 13 can also communicate with an IP telephone or other I? terminal (not shown) via the IP network 12.
  • the mobile nodes are portable mobile nodes. Therefore, the mobile nodes 13 can communicate with another mobile node 13 within the networks lla-llc while moving from one radio access network to another. For this reason, the mobile nodes 13 are provided with wireless interfaces for the networks lla-llc, which will be described later, a plurality of applications, and a function for controlling the interfaces and applications.
  • an agent section 20c which is provided for a mobile node 13 and will be described later, functions as an SIP server that merely transfers an SIP message, and an SIP application within an application section 20b, which is provided for a mobile node 13, performs a process for session establishment and termination.
  • the agent section 20c provided for a mobile node 13 functions as a controller that exercises SIP 3rd party call control (3PCC) . In this manner, the agent section 20c exercises control over new session parameter setup for session maintenance.
  • PCC SIP 3rd party call control
  • the CCN server 12a which is provided for the IP network 12, incorporates a server function for transferring an SIP message, and a gateway function for transferring SIP to a specific radio access network lla-llc.
  • Fig. 2 is a system configuration block diagram illustrating the configuration of a mobile node 13. As shown in Fig. 2, the mobile node 13 comprises an interface section 20a, an application section 20b, and an agent section 20c.
  • the interface section 20a comprises a first interface 21 which is a wireless LAN interface (first interface) for wireless LANs 11a, a second interface 11 which is a Personal Handyphone System interface for Personal Handyphone Systems lib, and a third interface 23 which is a cellular phone interface for cellular phones lie.
  • first interface 21 which is a wireless LAN interface (first interface) for wireless LANs 11a
  • second interface 11 which is a Personal Handyphone System interface for Personal Handyphone Systems lib
  • a third interface 23 which is a cellular phone interface for cellular phones lie.
  • the application section 20b comprises a voice application 25, which uses SIP for voice data transmission/reception, a video application 26, which uses SIP for image data transmission/reception, and a message application 27 which uses SIP for message data transmission/reception.
  • the agent section 20c comprises a call controller (CC) 31, a session manager (SM) 32, a profile manager (PM) 33, and a resource manager (RM) 34.
  • CC call controller
  • SM session manager
  • PM profile manager
  • RM resource manager
  • the session manager 32 comprises an SIP server and a controller function that exercises SIP 3rd party call control, which is mentioned earlier. Therefore, the session manager 32 functions as an SIP server for transferring an SIP message when an SIP application establishes or terminates a session.
  • the session manager 32 passes the associated session information to the call controller 31.
  • the session information includes, for instance, a call ID for session identification, media parameters (voice, video, message, etc.), and codec.
  • the session manager 32 receives a notification from the call controller 31 and functions as an SIP 3rd party call controller in accordance with new session parameters.
  • the profile manager 33 includes a database that stores various SIP applications 25-27 of the application section 20b, the information about SIP applications available to the user, and the information about various settings of the user.
  • the profile manager 33 passes these items of information to the call controller 31 as needed. Further, the profile manager 33 is capable of presenting the status of the agent section 20c to the user upon notification from the call controller 31.
  • the resource manager 34 is a management section that controls the first to third interfaces 21-23. Upon notification from the call controller 31, the resource manager 34 controls the first to third interfaces 21-23. Further, while the resource manager 34 is in a state for constantly monitoring the first to third interfaces 21-23, it monitors, for instance, the reception status (the carrier's electric field strength, etc.) as well. The resource manager 34 also passes the information concerning such monitoring to the call controller 31.
  • the resource manager 34 monitors the associated reception status. If, in this instance, a mobile node 14 moves out of the service area of the wireless LAN 11a (it is possible that the communication may be cut off by reduced electric field strength) , the resource manager 34 receives a notification from the call controller 31 before the current communication is cut off. In such an instance, the resource manager 34 puts the second and third interfaces on standby, performs a monitoring operation, then detects and analyzes the electric field , strength of another radio access network that is available for communication. Then, the resource manager 34 makes a connection to a Personal Handyphone System lib that is available for communication, and notifies the call controller 31 of such a connection.
  • the call controller 31 collects various information, including the session information from the session manager 32, the user setting information from the profile manager 33, and the information about the status of the first to third interfaces 21-23 from the resource manager 34, and controls the agent section 20c.
  • the application section 20b of user A To permit the mobile node 13 of user A to establish a session with the mobile node 13 of user B, the application section 20b of user A generates an SIP request message (INVITE) and transmits it to the CCN server 12a via the agent section 20c of user A.
  • the CCN server 12a transmits the SIP request message (INVITE) to the mobile node 13 of user B.
  • the SI? request message (INVITE)
  • the SI? request message (INVITE) is transmitted to the application section 20b of user B via the agent section 20c.
  • the application section 20b of user B generates an SIP response message (180 ringing) in response to the SIP request message (INVITE) and transmits the SIP response message
  • the CCN server 12a transmits the SIP response message
  • the application section 20b of user B then generates an SIP response message (200 OK) to grant a request indicated by the SIP request message (INVITE) , and transmits the SI? response message (200 OK) to the CCN server 12a via the agent section 20c of user B.
  • the CCN server 12a transmits the SIP response message (200 OK) to the application section 20b of user B via the agent section 20c of user A.
  • the application section 20b of user A returns an SIP response message (ACK) in response to the SIP response message (200 OK) , which is received from the application section 20b of user B.
  • the SIP response message (ACK) is transmitted to the application section 20b of user B via the agent section 20c of user A, the CCN server 12a, and the agent section 20c of user B.
  • the application section 20b of user B receives the SIP response message (ACK)
  • the session is established to open communication between users A and B. Passage of the above SIP messages causes the agent sections 20c of both users to detect that the session is established.
  • the application section 20b of user A or user B (user A in he example shown in Fig. 3) transmits an SIP request message (BYE) for session termination.
  • This SIP request message (BYE) is transmitted to the application section 20b of user B via the agent section 20c of user A, the CCN server 12a, and the agent section 20c of user B.
  • the application section 20b of user B Upon receipt of the SIP request message (BYE) , the application section 20b of user B returns an SIP response message (200 OK) to grant a request indicated by the SIP request message (BYE).
  • the SIP response message (200 OK) is transmitted to the application section 20b of user A via the agent section 20c of user B, the CCN server 12a, and the agent section 20c of user A.
  • the application section 20b of user A receives the SIP response message (200 OK)
  • the session terminates so that the communication between users A and B comes to an end. Passage of the above SIP messages causes the agent sections 20c of both users to detect that the session is terminated.
  • the following description deals with a situation where the session is maintained by readjusting the session parameters when, for instance, the mobile node 13 of at least user A or user B moves, making it necessary to switch from one radio access network to another.
  • radio access network switching involves wireless LANs 11a and Personal Handyphone Systems lib.
  • the Personal Handyphone Systems lib have a data transfer rate of 9.2 Kbps, whereas the wireless LANs 11a have a data transfer rate of 11 Mbps. Therefore, when a switch is to be made from a wireless LANlla to a Personal Handyphone System lib while the session is established as shown in Fig. 1, the communication needs to be maintained by changing the session parameters due, for instance, to a band difference. If a switch is made to a Personal Handyphone System lib without changing the session parameters while 64 Kbps codec communication is established with a wireless LAN 11a, the communication can no longer be maintained due to band insufficiency.
  • Fig. 4 is a sequence chart that illustrates how the session parameters are readjusted while a session is established. For explanation purposes, the following description deals with a situation where the mobile node 13 of user A switches rom a wireless LAN 11a to a Personal Handyphone System lib.
  • the resource manager 34 of the mobile node 13 of user A is monitoring the reception state of the first interface 21 for the wireless LANlla.
  • the resource manager 34 receives a notification from the call controller 31 before the current communication is cut off.
  • the resource manager 34 puts the second and third interfaces 22, 23 on standby, performs a monitoring operation, then detects and analyzes the electric field strength of another radio access network that is available for communication.
  • the resource manager 34 concludes that the Personal Handyphone System lib is a radio access network that is available for communication, makes a connection to the Personal Handyphone System lib, and notifies the call controller 31 of such a connection (step SI) .
  • the session manager 32 concludes that the session parameters should be changed (step ⁇ 2) .
  • the session parameters may also be changed in compliance with the information about various settings that are entered by the user via the profile manager 33.
  • the session manager 32 transmits an SIP request message (re-INVITE) , including new session parameters, to the application section 20b of user A by operating the SIP 3rd party call controller in compliance with the session information (step S3) .
  • the application section 20b of user A checks whether the session parameters can be updated (step S4) . If it is concluded that communication can be established even when the session parameters are updated, the application section 20b of user A returns an SIP response message (200 OK) to the agent section 20c of user A to grant a request indicated by the SIP request message (re-INVITE) . Upon receipt of the SIP response message (200 OK) , the agent section 20c of user A transmits the SIP request message (re-INVITE) to the CCN server 12a of the IP network 12 to request the mobile node 13 of user B to change the session parameters.
  • SIP request message re-INVITE
  • the CCN server 12a transmits the SIP request message (re-INVITE) to the agent section 20c of the mobile node 13 of user B.
  • the agent section 20c of user B acquires the session information from the SIP request message (re-INVITE) , compares the acquired information against the information collected from the resource manager 34 and profile manager 33, and checks whether the session parameters should be transferred to the application section 20b of user B (step S5) .
  • the agent section 20c of user B operates as an SIP server to transfer the SIP request message (re-INVITE) to the application section 20b of user B.
  • the application section 20b of user B compares the session parameters with the SIP request message (re-INVITE) (step S6) , and then returns an SIP response message (200 OK) to the agent section 20c of user B to grant a request indicated by the SIP request message (re-INVITE) .
  • the agent section 20c of user B transmits the SIP response message (200 OK) to the CCN server 12a of the IP network 12.
  • the CCN serer 12a transmits the SIP response message (200 OK) to the session manager 32 in the agent section 20c of user A's mobile node 13.
  • the agent section 20c of user A first returns an SIP request message (ACK) to the application section 20b of user A in response to the affirmative SIP response message (200 OK) from the application section 20b of user A. Further, the agent section 20c of user A transmits an SIP request message (ACK) to the CCN server 12a in response to the affirmative SIP response message (200 OK) from the application section 20b of user B. The agent section 20c of user B transmits the SIP request message (ACK) to the application section 20c of user B.
  • the communication between the mobile nodes 13 of users A and B is established in accordance with the updated session parameters to maintain the session. If the communication between the mobile nodes 13 of users A and 3 fails due, for instance, to non-support of codec functionality, the communication is established in accordance with the previous session parameters to maintain the session.
  • the mobile node 13 includes the agent section 20c, which comprises the call controller 31, session manager 32, profile manager 33, and resource manager 34, and retains and manages the information about the first to third interfaces 21-23 and applications 25-27.
  • agent section 20c which comprises the call controller 31, session manager 32, profile manager 33, and resource manager 34, and retains and manages the information about the first to third interfaces 21-23 and applications 25-27.
  • session establishment and session termination are accomplished end-to-end between the applications 25-27 (application sections) of respective mobile nodes.
  • session maintenance is provided by the agent section 20c.
  • the session parameters are dynamically updated as needed by the information that is collected with the session established, for instance, from the resource manager 34 and profile manager 33, such as the monitoring information about the first to third interfaces 21-23 and the information about various settings of the user. Therefore, the session can be maintained.
  • session maintenance is accomplished by providing the session manager 32 in the agent section 20c of the mobile node 13 with a controller function that exercises SI? 3rd party call control (3PCC) to readjust the session parameters. Therefore, the application side does not have to perform any complicated process. As a result, highly versatile applications can be developed and implemented with ease.
  • 3PCC 3rd party call control
  • the embodiment of the present invention may be altered as described below. In the present embodiment described above, the process for readjusting the session parameters is performed via the CCN server 12a. Alternatively, however, the process may be performed directly between the mobile nodes and without via the CCN server 12a.
  • the session maintenance process is performed when a switch is made from one radio access network to another.
  • the information about the user's various settings may be used to change the session parameters to the satisfaction of the user via the profile manager 33.
  • the present embodiment described above relates to the communication session between two points. However, the present invention can also be applied to the communication session among three or more points .
  • the SIP request message (re-INVITE) is transmitted first to the application section 20b of user A who has set the new session parameters.
  • the SIP request message may be transmitted first to the mobile node 13 of user B or simultaneously transmitted to the mobile nodes of users A and B.
  • the agent section 20c comprises the call controller 31, session manager 32, profile manager 33, and resource manager 34.
  • the agent section 20c is not limited to such a configuration. An alternative is to exclude the profile manager 33 or incorporate additional means for exercising a new function.
  • the present embodiment described above assumes that communication is established between mobile nodes 13 that include the agent section 20c.
  • the remote party for communication is not limited to a mobile node having the agent section 20c.
  • the mobile node for the remote party may alternatively be without the agent section 20c.
  • the SIP requests message (INVITE) is used to update the session parameters.
  • the SIP request message (INVITE) is used to update the session parameters.
  • UPDATE may be used for updating purposes. Any update method can be used as far as the agent section sets new session parameters to exercise control for session maintenance without imposing any load on the applications.
  • each mobile node is provided with a plurality of interfaces.
  • software defined radio (SDR) or Ethernet cable may be used instead of such interfaces.
  • the present invention permits the session parameters to be readjusted for session maintenance purposes without causing the applications to perform any complicated process.
  • IP network serving as a core network
  • Wireless LAN Wireless LAN
  • e Cellular phone
  • CCN server Interface section
  • Application section c Agent section : Wireless LAN interface (first interface) : Personal Handyphone System interface (second interface) : Cellular phone interface (third interface) : Voice application : Video application : Message application : Call controller : Session manager : Profile manager : Resource manager

Abstract

A session maintenance method and mobile nodes that allow dynamic readjustment of session parameters within a heterogeneous network. Before the environment in which user A is positioned switches to a different access network, an agent section of user A’s mobile node delivers new session parameters to the agent section and application section of user B's mobile node via a CCN server. The application section of user B's mobile node receives the new session parameters, creates a response to them, and transmits the response to the agent section of user A's mobile node via user B's agent section and the CCN server. The agent sections of both mobile nodes perform setup again as needed with new session parameters in order to maintain a session between both application sections.

Description

SESSION MAINTENANCE METHOD AND MOBILE NODES FOR HETEROGENEOUS NETWORK
BACKGROUND OF THE INVENTION [0001] The present invention relates to a session maintenance method and mobile nodes for use in a heterqgeneous network.
[0002] A heterogeneous network is conceived as one basic configuration for a future mobile communication network. In the heterogeneous network, a common core network (CCN) is overlayed with different types of radio access networks (RANs) for seamless integration. Mobile nodes (MNs) within the heterogeneous network provide multimedia communication services by selecting an optimum radio access network in accordance with the user's purpose of use and environment and dynamically switching from one radio access network to another as needed.
[0003] To maintain an established session by dynamically switching from one radio access network to another within a heterogeneous network communication system, it is necessary to ensure that session parameters (such as those related to media streaming and codec) can be readjusted. When switching, for instance, from a wireless LAN (data transfer rate: 11 Mbps) to a Personal Handyphone System (data transfer rate: 29.2 Kbps) in a situation where a session is established, the following problems arise because the bands of the wireless LAN and the Personal Handyphone System differ from each other. The problems will now be described with reference to voice communication based on VoIP (Voice over Internet Protocol) .
[0004] (1) Switching from a wireless LAN to a Personal Handyphone System
If a switch is made to a Personal Handyphone System while 64 Kbps codec communication is established via a wireless LAN, the communication is lost due to band insufficiency. It is therefore necessary to readjust the codec and other relevant session parameters.
[0005] (2) Switching from a Personal Handyphone System to a wireless LAN
Even if a switch is made to a wireless LAN while 8 Kbps codec communication is established via a Personal Handyphone System, the communication can be maintained. However, the session parameters are readjusted for codec quality enhancement if the user desires such enhancement and if the band is sufficient.
[0006] It is therefore necessary to change the session parameters while maintaining the communication. As regards SIP (Session Initiation Protocol), which serves as a signaling protocol for session establishment, maintenance, and termination, a method for end-to-end session parameter readjustment is studied, for instance, in Nonpatent Document 1.
[0007] [Nonpatent Document 1] SIP: Session Initiation Protocol (http: //www. ietf . org/rfcZrfc3261.txt)
[0008] However, when the above-mentioned method is used, an SIP application readjusts the session parameters. Therefore, it is necessary that the SIP application of each mobile node constantly keep the information, for instance, for maintaining voice communication and switching to another radio access network. In other words, a complicated process is required for the application so that application development and implementation tend to be complicated and not sufficiently versatile.
[0009] The present invention has been made to solve the above problems, and provides a session maintenance method and mobile nodes for use in a heterogeneous network, thereby making it possible to dynamically readjust session parameters without requiring any complicated process for an application while communication is maintained for the mobile nodes within the heterogeneous network.
SUMMARY OF THE INVENTION [0010] One aspect of the present invention provides a session maintenance method for use in a heterogeneous network that comprises a plurality of different access networks and a core network interconnecting the access networks. Mobile nodes in the heterogeneous network are provided with an agent section that generates new session parameters for session maintenance. The session maintenance method comprises the steps of transmitting, when new session parameters for maintaining a session for the mobile nodes are generated by the agent section of a first mobile node in a situation where a session is established for the mobile nodes, the new session parameters to the agent section of a second mobile node; causing the agent section of the second mobile node to receive the new session parameters, to analyze the new session parameters, and to transmit the analyzed session parameters to the agent section of the first mobile node; and causing the agent sections of both the first and second mobile nodes to maintain the session in accordance with the new session parameters .
[0011] In another aspect of the present invention, the agent section generates new session parameters in accordance with certain information while a session is established, and transmits the generated session parameters to a remote party to maintain communication. For example, the term "certain information" represents a dynamic switch from one radio access network to another (e.g., from a wireless LAN to a Personal Handyphone System) , which is made by the prior art described earlier. The remote party targeted for communication may be provided with an agent section so that new session parameters are received rom that agent section to maintain communication. Further,, the agent sections of both parties involved in communication may exchange information and determine the session parameters to maintain communication.
[0012] Another aspect of the present invention provides a session maintenance method for use in a heterogeneous network that comprises a plurality of different access networks and a core network interconnecting the access networks. Mobile nodes in the heterogeneous network are provided with an agent section that generates new session parameters for session maintenance. The session maintenance method comprises the steps of establishing a session for the mobile nodes by causing applications provided for the mobile nodes to generate and transmit the information for session establishment; terminating the session for the mobile nodes by causing applications provided for the mobile nodes to generate and transmit the information for session termination; transmitting, when new session parameters for maintaining the session for the mobile nodes are generated by the agent section of a first mobile node in a situation where the session is established for the mobile nodes, the new session parameters to the agent section of a second mobile node; causing the agent section of the second mobile node to receive the new session parameters, to analyze the new session parameters, and to transmit the analyzed session parameters to the agent section of the first mobile node; and causing the agent sections of both the first and second mobile nodes to maintain the session in accordance with the new session parameters.
[0013] In another aspect of the present invention, session establishment and termination are performed end-to-end between applications. However, session maintenance is performed by the agent section instead of the applications. The method for session maintenance is as stated earlier. [0014] According to another aspect of the present invention, mobile nodes for use in a heterogeneous network that comprises a plurality of different access networks and a core network interconnecting the access networks are provided with an agent section that generates new session parameters for session maintenance .
[0015] According to still another aspect of the present invention, the agent section described above is incorporated so that session maintenance can be achieved by updating the session parameters without causing an application to perform a complicated process.
BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is a schematic diagram illustrating the configuration of one embodiment of a heterogeneous network according to the present invention.
FIG. 2 is a block diagram illustrating the configuration of a mobile node.
FIG. 3 is a sequence chart illustrating a session establishment/termination process .
FIG. 4 is a sequence chart illustrating a session maintenance process.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0016] One embodiment of the present invention will now be described with reference to the accompanying drawings . The subsequent explanation is based on the use of SIP, which permits session establishment, maintenance, and termination as described in conjunction with the aforementioned prior art. Fig. 1 schematically illustrates the configuration of one embodiment of a heterogeneous network according to the present invention. As shown in Fig. 1, the heterogeneous network 10 comprises a plurality of radio access networks 11, an IP network 12 that serves as a common core network (CCN) , and mobile nodes (MNs) 13. The plurality of radio access networks 11 comprise a plurality of different radio access networks. In the present embodiment, the plurality of different radio access networks comprise, for instance, wireless LANs (WLANs or wireless local area networks) 11a, Personal Handyphone Systems lib, and cellular phones lie. In other words, a plurality of service areas for the networks lla-llc coexist within the plurality of radio access networks 11.
[0017] The IP network 12 interconnects the networks lla-llc within the plurality of radio access networks 11. In the present embodiment, the IP network 12 is provided with a CCN server 12a, which manages the connection among the networks lla-llc. The CCN server 12a encrypts the session information required for establishing, maintaining, and terminating a session between the mobile nodes 13 and other information necessary for communication, and transmits the encrypted information to the mobile nodes 13. The CCN server 12a exercises session management and performs a necessary process for permitting a provider, for instance, to perform billing of the users of the mobile nodes 13.
[0018] Within the plurality of radio access networks, a mobile node 13 communicates with another mobile node 13 in the same network lla-llc or a certain mobile node 13 in another network lla-llc. Further, a mobile node 13 can also communicate with an IP telephone or other I? terminal (not shown) via the IP network 12. The mobile nodes are portable mobile nodes. Therefore, the mobile nodes 13 can communicate with another mobile node 13 within the networks lla-llc while moving from one radio access network to another. For this reason, the mobile nodes 13 are provided with wireless interfaces for the networks lla-llc, which will be described later, a plurality of applications, and a function for controlling the interfaces and applications.
[0019] For session establishment and termination purposes, an agent section 20c, which is provided for a mobile node 13 and will be described later, functions as an SIP server that merely transfers an SIP message, and an SIP application within an application section 20b, which is provided for a mobile node 13, performs a process for session establishment and termination.
[0020] For session maintenance purposes, on the other hand, the agent section 20c provided for a mobile node 13 functions as a controller that exercises SIP 3rd party call control (3PCC) . In this manner, the agent section 20c exercises control over new session parameter setup for session maintenance.
[0021] The CCN server 12a, which is provided for the IP network 12, incorporates a server function for transferring an SIP message, and a gateway function for transferring SIP to a specific radio access network lla-llc.
[0022] The configuration of a mobile node will now be described. Fig. 2 is a system configuration block diagram illustrating the configuration of a mobile node 13. As shown in Fig. 2, the mobile node 13 comprises an interface section 20a, an application section 20b, and an agent section 20c.
[0023] The interface section 20a comprises a first interface 21 which is a wireless LAN interface (first interface) for wireless LANs 11a, a second interface 11 which is a Personal Handyphone System interface for Personal Handyphone Systems lib, and a third interface 23 which is a cellular phone interface for cellular phones lie.
[0024] The application section 20b comprises a voice application 25, which uses SIP for voice data transmission/reception, a video application 26, which uses SIP for image data transmission/reception, and a message application 27 which uses SIP for message data transmission/reception.
[0025] The agent section 20c comprises a call controller (CC) 31, a session manager (SM) 32, a profile manager (PM) 33, and a resource manager (RM) 34.
[0026] The session manager 32 comprises an SIP server and a controller function that exercises SIP 3rd party call control, which is mentioned earlier. Therefore, the session manager 32 functions as an SIP server for transferring an SIP message when an SIP application establishes or terminates a session. The session manager 32 passes the associated session information to the call controller 31. The session information includes, for instance, a call ID for session identification, media parameters (voice, video, message, etc.), and codec. When, on the other hand, a session needs to be maintained, the session manager 32 receives a notification from the call controller 31 and functions as an SIP 3rd party call controller in accordance with new session parameters.
[0027] The profile manager 33 includes a database that stores various SIP applications 25-27 of the application section 20b, the information about SIP applications available to the user, and the information about various settings of the user. The profile manager 33 passes these items of information to the call controller 31 as needed. Further, the profile manager 33 is capable of presenting the status of the agent section 20c to the user upon notification from the call controller 31.
[0028] The resource manager 34 is a management section that controls the first to third interfaces 21-23. Upon notification from the call controller 31, the resource manager 34 controls the first to third interfaces 21-23. Further, while the resource manager 34 is in a state for constantly monitoring the first to third interfaces 21-23, it monitors, for instance, the reception status (the carrier's electric field strength, etc.) as well. The resource manager 34 also passes the information concerning such monitoring to the call controller 31.
[0029] More specifically, while communication is established using a wireless LAN 11a, that is, via the third interface 21, the resource manager 34 monitors the associated reception status. If, in this instance, a mobile node 14 moves out of the service area of the wireless LAN 11a (it is possible that the communication may be cut off by reduced electric field strength) , the resource manager 34 receives a notification from the call controller 31 before the current communication is cut off. In such an instance, the resource manager 34 puts the second and third interfaces on standby, performs a monitoring operation, then detects and analyzes the electric field , strength of another radio access network that is available for communication. Then, the resource manager 34 makes a connection to a Personal Handyphone System lib that is available for communication, and notifies the call controller 31 of such a connection.
[0030] The call controller 31 collects various information, including the session information from the session manager 32, the user setting information from the profile manager 33, and the information about the status of the first to third interfaces 21-23 from the resource manager 34, and controls the agent section 20c.
[0031] The operation of the mobile node 13, which is configured as described above, will now be described with reference to the sequence chart in Fig. 3, which illustrates the session establishment and termination sequences followed by the mobile node 13, and the sequence chart in Fig. 4, which illustrates the session maintenance sequence followed by the mobile node 13.
[0032] Session establishment
To permit the mobile node 13 of user A to establish a session with the mobile node 13 of user B, the application section 20b of user A generates an SIP request message (INVITE) and transmits it to the CCN server 12a via the agent section 20c of user A. The CCN server 12a transmits the SIP request message (INVITE) to the mobile node 13 of user B.
[0033] When the mobile node 13 of user B acquires the SI? request message (INVITE), the SI? request message (INVITE) is transmitted to the application section 20b of user B via the agent section 20c.
[0034] The application section 20b of user B generates an SIP response message (180 ringing) in response to the SIP request message (INVITE) and transmits the SIP response message
(180 ringing) to the CCN server 12a via the agent section 20c of user B. The CCN server 12a transmits the SIP response message
(180 ringing) to the application section 20b of user A via the agent section 20c of user A.
[0035] The application section 20b of user B then generates an SIP response message (200 OK) to grant a request indicated by the SIP request message (INVITE) , and transmits the SI? response message (200 OK) to the CCN server 12a via the agent section 20c of user B. The CCN server 12a transmits the SIP response message (200 OK) to the application section 20b of user B via the agent section 20c of user A.
[0036] The application section 20b of user A returns an SIP response message (ACK) in response to the SIP response message (200 OK) , which is received from the application section 20b of user B. The SIP response message (ACK) is transmitted to the application section 20b of user B via the agent section 20c of user A, the CCN server 12a, and the agent section 20c of user B. When the application section 20b of user B receives the SIP response message (ACK) , the session is established to open communication between users A and B. Passage of the above SIP messages causes the agent sections 20c of both users to detect that the session is established.
[0037] Session termination
When the session is to be terminated, the application section 20b of user A or user B (user A in he example shown in Fig. 3) transmits an SIP request message (BYE) for session termination. This SIP request message (BYE) is transmitted to the application section 20b of user B via the agent section 20c of user A, the CCN server 12a, and the agent section 20c of user B.
[0038] Upon receipt of the SIP request message (BYE) , the application section 20b of user B returns an SIP response message (200 OK) to grant a request indicated by the SIP request message (BYE). The SIP response message (200 OK) is transmitted to the application section 20b of user A via the agent section 20c of user B, the CCN server 12a, and the agent section 20c of user A. When the application section 20b of user A receives the SIP response message (200 OK), the session terminates so that the communication between users A and B comes to an end. Passage of the above SIP messages causes the agent sections 20c of both users to detect that the session is terminated.
[0039] Session maintenance
The following description deals with a situation where the session is maintained by readjusting the session parameters when, for instance, the mobile node 13 of at least user A or user B moves, making it necessary to switch from one radio access network to another.
[0040] As described in conjunction with the aforementioned prior art, radio access network switching involves wireless LANs 11a and Personal Handyphone Systems lib. The Personal Handyphone Systems lib have a data transfer rate of 9.2 Kbps, whereas the wireless LANs 11a have a data transfer rate of 11 Mbps. Therefore, when a switch is to be made from a wireless LANlla to a Personal Handyphone System lib while the session is established as shown in Fig. 1, the communication needs to be maintained by changing the session parameters due, for instance, to a band difference. If a switch is made to a Personal Handyphone System lib without changing the session parameters while 64 Kbps codec communication is established with a wireless LAN 11a, the communication can no longer be maintained due to band insufficiency.
[0041] Fig. 4 is a sequence chart that illustrates how the session parameters are readjusted while a session is established. For explanation purposes, the following description deals with a situation where the mobile node 13 of user A switches rom a wireless LAN 11a to a Personal Handyphone System lib.
[0042] While communication is established between the mobile nodes 13 of users A and B, the resource manager 34 of the mobile node 13 of user A is monitoring the reception state of the first interface 21 for the wireless LANlla. When the mobile node 13 of user A moves out of the service area of the wireless LAN 11a, the resource manager 34 receives a notification from the call controller 31 before the current communication is cut off. In this instance, the resource manager 34 puts the second and third interfaces 22, 23 on standby, performs a monitoring operation, then detects and analyzes the electric field strength of another radio access network that is available for communication. Then, the resource manager 34 concludes that the Personal Handyphone System lib is a radio access network that is available for communication, makes a connection to the Personal Handyphone System lib, and notifies the call controller 31 of such a connection (step SI) .
[0043] In compliance with an instruction that is received from the resource manager 34 via the call controller 3, the session manager 32 concludes that the session parameters should be changed (step Ξ2) . The session parameters may also be changed in compliance with the information about various settings that are entered by the user via the profile manager 33. The session manager 32 transmits an SIP request message (re-INVITE) , including new session parameters, to the application section 20b of user A by operating the SIP 3rd party call controller in compliance with the session information (step S3) .
[0044] In accordance with the SIP request message (re-INVITE) for the session parameters to be changed, the application section 20b of user A checks whether the session parameters can be updated (step S4) . If it is concluded that communication can be established even when the session parameters are updated, the application section 20b of user A returns an SIP response message (200 OK) to the agent section 20c of user A to grant a request indicated by the SIP request message (re-INVITE) . Upon receipt of the SIP response message (200 OK) , the agent section 20c of user A transmits the SIP request message (re-INVITE) to the CCN server 12a of the IP network 12 to request the mobile node 13 of user B to change the session parameters.
[0045] The CCN server 12a transmits the SIP request message (re-INVITE) to the agent section 20c of the mobile node 13 of user B. The agent section 20c of user B acquires the session information from the SIP request message (re-INVITE) , compares the acquired information against the information collected from the resource manager 34 and profile manager 33, and checks whether the session parameters should be transferred to the application section 20b of user B (step S5) .
[0046] If it is concluded that the session parameters should be transferred, the agent section 20c of user B operates as an SIP server to transfer the SIP request message (re-INVITE) to the application section 20b of user B. Upon receipt of the SIP request message (re-INVITE) , the application section 20b of user B compares the session parameters with the SIP request message (re-INVITE) (step S6) , and then returns an SIP response message (200 OK) to the agent section 20c of user B to grant a request indicated by the SIP request message (re-INVITE) .
[0047] The agent section 20c of user B transmits the SIP response message (200 OK) to the CCN server 12a of the IP network 12. The CCN serer 12a transmits the SIP response message (200 OK) to the session manager 32 in the agent section 20c of user A's mobile node 13.
[0048] In accordance with the SIP response message (200 OK), the agent section 20c of user A first returns an SIP request message (ACK) to the application section 20b of user A in response to the affirmative SIP response message (200 OK) from the application section 20b of user A. Further, the agent section 20c of user A transmits an SIP request message (ACK) to the CCN server 12a in response to the affirmative SIP response message (200 OK) from the application section 20b of user B. The agent section 20c of user B transmits the SIP request message (ACK) to the application section 20c of user B.
[0049] Subsequently, the communication between the mobile nodes 13 of users A and B is established in accordance with the updated session parameters to maintain the session. If the communication between the mobile nodes 13 of users A and 3 fails due, for instance, to non-support of codec functionality, the communication is established in accordance with the previous session parameters to maintain the session.
[0050] The features of the present embodiment, which is configured as described above, will now be described. (1) In the present embodiment, the mobile node 13 includes the agent section 20c, which comprises the call controller 31, session manager 32, profile manager 33, and resource manager 34, and retains and manages the information about the first to third interfaces 21-23 and applications 25-27.
[0051] (2) In the present embodiment, session establishment and session termination are accomplished end-to-end between the applications 25-27 (application sections) of respective mobile nodes. However, session maintenance is provided by the agent section 20c.
[0052] (3) In the present embodiment, the session parameters are dynamically updated as needed by the information that is collected with the session established, for instance, from the resource manager 34 and profile manager 33, such as the monitoring information about the first to third interfaces 21-23 and the information about various settings of the user. Therefore, the session can be maintained.
[0053] (4) In the present embodiment, session maintenance is accomplished by providing the session manager 32 in the agent section 20c of the mobile node 13 with a controller function that exercises SI? 3rd party call control (3PCC) to readjust the session parameters. Therefore, the application side does not have to perform any complicated process. As a result, highly versatile applications can be developed and implemented with ease. [0054] The embodiment of the present invention may be altered as described below. In the present embodiment described above, the process for readjusting the session parameters is performed via the CCN server 12a. Alternatively, however, the process may be performed directly between the mobile nodes and without via the CCN server 12a.
[0055] In the present embodiment described above, the session maintenance process is performed when a switch is made from one radio access network to another. Alternatively, however, the information about the user's various settings may be used to change the session parameters to the satisfaction of the user via the profile manager 33.
[0056] The present embodiment described above relates to the communication session between two points. However, the present invention can also be applied to the communication session among three or more points . When new session parameters are set in the present embodiment described above, the SIP request message (re-INVITE) is transmitted first to the application section 20b of user A who has set the new session parameters.
[0057] Alternatively, however, the SIP request message (re-INVITE) may be transmitted first to the mobile node 13 of user B or simultaneously transmitted to the mobile nodes of users A and B. In the present embodiment described above, the agent section 20c comprises the call controller 31, session manager 32, profile manager 33, and resource manager 34. However, the agent section 20c is not limited to such a configuration. An alternative is to exclude the profile manager 33 or incorporate additional means for exercising a new function.
[0058] The present embodiment described above assumes that communication is established between mobile nodes 13 that include the agent section 20c. The remote party for communication is not limited to a mobile node having the agent section 20c. The mobile node for the remote party may alternatively be without the agent section 20c.
[0059] In the present embodiment described above, the SIP requests message (INVITE) is used to update the session parameters. Alternatively, however, the SIP request message
(UPDATE) may be used for updating purposes. Any update method can be used as far as the agent section sets new session parameters to exercise control for session maintenance without imposing any load on the applications.
[0060] The present embodiment described above assumes that each mobile node is provided with a plurality of interfaces. Alternatively, however, software defined radio (SDR) or Ethernet cable may be used instead of such interfaces.
[0061] The present embodiment described above assumes that wireless mobile nodes are used as the mobile nodes. However, the present invention is not limited to the use of wireless mobile nodes.
[0062] As described above, the present invention permits the session parameters to be readjusted for session maintenance purposes without causing the applications to perform any complicated process.
Description of the Symbols
10: Heterogeneous network
11: Radio Access Networks
12: IP network serving as a core network
13: Mobile node
11a: Wireless LAN (WLAN) b : Personal Handyphone System e : Cellular phone a : CCN server a: Interface section b: Application section c: Agent section : Wireless LAN interface (first interface) : Personal Handyphone System interface (second interface) : Cellular phone interface (third interface) : Voice application : Video application : Message application : Call controller : Session manager : Profile manager : Resource manager

Claims

1. A session maintenance method for use in a heterogeneous network that comprises a plurality of dif erent access networks and a core network interconnecting said access networks , wherein mobile nodes are provided with an agent section that generates new session parameters for session maintenance, said session maintenance method comprising the steps of: transmitting, when new session parameters for maintaining a session for said mobile nodes are generated by the agent section of a first mobile node in a situation where a session is established for said mobile nodes, the new session parameters to the agent section of a second mobile node; causing the agent section of the second mobile node to receive said new session parameters, to analyze the new session parameters, and to transmit the analyzed session parameters to the agent section of the first mobile node; and causing the agent sections of both the first and second mobile nodes to maintain the session in accordance with said new session parameters.
2. A session maintenance method for use in a heterogeneous network that comprises a plurality of di erent access networks and a core network interconnecting said access networks, wherein mobile nodes are provided with an agent section that generates new session parameters for session maintenance, said session maintenance method comprising the steps of: establishing a session for said mobile nodes by causing applications provided for said mobile nodes to generate and transmit the information for session establishment; terminating the session for said mobile nodes by causing applications provided for said mobile nodes to generate and transmit the information for session termination; transmitting, when new session parameters for maintaining the session for said mobile nodes are generated by the agent section of a first mobile node in a situation where the session is established for said mobile nodes, the new session parameters to the agent section of a second mobile node; causing the agent section of the second mobile node to receive said new session parameters, to analyze the new session parameters, and to transmit the analyzed session parameters to the agent section of the first mobile node; and causing the agent sections of both the first and second mobile nodes to maintain the session in accordance with said new session parameters.
3. Mobile nodes for use in a heterogeneous network that comprises a plurality of different access networks and a core network interconnecting said access networks, wherein said mobile nodes include an agent section that generates new session parameters for session maintenance.
PCT/EP2004/050227 2003-02-28 2004-02-27 Session maintenance method and mobile nodes for heterogeneous network WO2004077745A2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2003054997A JP2004265154A (en) 2003-02-28 2003-02-28 Session maintaining method in heterogeneous network, and its mobile node
JP3/054997 2003-02-28

Publications (2)

Publication Number Publication Date
WO2004077745A2 true WO2004077745A2 (en) 2004-09-10
WO2004077745A3 WO2004077745A3 (en) 2005-01-27

Family

ID=32923483

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2004/050227 WO2004077745A2 (en) 2003-02-28 2004-02-27 Session maintenance method and mobile nodes for heterogeneous network

Country Status (2)

Country Link
JP (1) JP2004265154A (en)
WO (1) WO2004077745A2 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006136889A2 (en) * 2005-06-20 2006-12-28 Nokia Corporation Method, apparatus and computer program product providing interoperable qos parameters and signaling thereof in a 3gpp2-3gpp and 3gpp2-3gpp2 conversational multimedia exchange
WO2008034128A1 (en) * 2006-09-15 2008-03-20 Intel Corporation Apparatus, systems, and methods for mobile client secure session parameter updates
TWI561035B (en) * 2013-08-12 2016-12-01 Chunghwa Telecom Co Ltd Dynamic dispatching business operations in heterogeneous systems
WO2023102286A1 (en) * 2021-12-03 2023-06-08 Qualcomm Incorporated Inter-radio access technology handoff procedure
WO2024019875A1 (en) * 2022-07-22 2024-01-25 Qualcomm Incorporated Connected call recovery
US11974176B2 (en) 2021-12-03 2024-04-30 Qualcomm Incorporated Inter-radio access technology handoff procedure

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006237815A (en) * 2005-02-23 2006-09-07 Kddi Corp Method and system for switching communication session
JP4285655B2 (en) * 2005-07-19 2009-06-24 インターナショナル・ビジネス・マシーンズ・コーポレーション Method, apparatus, and program for providing Web service
KR100802658B1 (en) 2006-08-31 2008-02-13 서울통신기술 주식회사 Apparatus and method for session assign count management of ev-do service system
JPWO2008059570A1 (en) 2006-11-15 2010-02-25 パナソニック株式会社 COMMUNICATION TERMINAL DEVICE, COMMUNICATION SYSTEM, AND SEAMLESS HANDOVER METHOD

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002091678A1 (en) * 2001-05-10 2002-11-14 Nokia Corporation Method, system and network element device for controlling sessions between terminals
US20020181424A1 (en) * 2001-05-29 2002-12-05 Interdigital Technology Corporation System and method for reducing information communicated between universal mobile telecommunication system multimedia capable units

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002091678A1 (en) * 2001-05-10 2002-11-14 Nokia Corporation Method, system and network element device for controlling sessions between terminals
US20020181424A1 (en) * 2001-05-29 2002-12-05 Interdigital Technology Corporation System and method for reducing information communicated between universal mobile telecommunication system multimedia capable units

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
EGUCHI, H. UBUKATA, T. ET AL.: "Development of SIP-based signaling for heterogeneous Wireless Networks" October 2003 (2003-10), pages 1-5, XP002307733 JAPAN Retrieved from the Internet: URL:http://www2.crl.go.jp/mt/b193/member/m ahmud/kmahmud/docs/103.pdf> [retrieved on 2004-11-25] *
RADHIKA R. ROY: "Transparent third party call control model for SIP-H.323 Interworking" INTERNET ENGINEERING TASK FORCE, INTERNET DRAFTS, 21 October 2002 (2002-10-21), XP015005117 *
WOLFGANG KELLERER: "Intelligence on Top of Networks: SIP based Service Cntrol Layer Signalling" 9 May 2001 (2001-05-09), pages 1-6, XP002307732 BOSTON,USA Retrieved from the Internet: URL:http://www.lkn.e-technik.tu-muenchen.d e/~wolfgang/wk/publ/kellerer_in2001f.pdf> [retrieved on 2004-11-25] *

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006136889A2 (en) * 2005-06-20 2006-12-28 Nokia Corporation Method, apparatus and computer program product providing interoperable qos parameters and signaling thereof in a 3gpp2-3gpp and 3gpp2-3gpp2 conversational multimedia exchange
WO2006136889A3 (en) * 2005-06-20 2007-03-08 Nokia Corp Method, apparatus and computer program product providing interoperable qos parameters and signaling thereof in a 3gpp2-3gpp and 3gpp2-3gpp2 conversational multimedia exchange
WO2008034128A1 (en) * 2006-09-15 2008-03-20 Intel Corporation Apparatus, systems, and methods for mobile client secure session parameter updates
TWI561035B (en) * 2013-08-12 2016-12-01 Chunghwa Telecom Co Ltd Dynamic dispatching business operations in heterogeneous systems
WO2023102286A1 (en) * 2021-12-03 2023-06-08 Qualcomm Incorporated Inter-radio access technology handoff procedure
US11974176B2 (en) 2021-12-03 2024-04-30 Qualcomm Incorporated Inter-radio access technology handoff procedure
WO2024019875A1 (en) * 2022-07-22 2024-01-25 Qualcomm Incorporated Connected call recovery

Also Published As

Publication number Publication date
WO2004077745A3 (en) 2005-01-27
JP2004265154A (en) 2004-09-24

Similar Documents

Publication Publication Date Title
US7397775B2 (en) Method and apparatus for routing calls
JP4607871B2 (en) Communication unit for handoff
US8717876B2 (en) Providing packet-based multimedia services via a circuit bearer
US7664103B2 (en) Method for providing VoIP services for wireless terminals
US7027818B2 (en) Method, telecommunication framework network and user equipment for provisioning of subscribed quality of service guarantees to subscribers of a network when they have to communicate by means of another network
US7986665B2 (en) Conferencing PSTN gateway methods and apparatus to facilitate heterogeneous wireless network handovers for mobile communication devices
JP4338993B2 (en) Wireless terminal session control method and interface setting method
EP1580938B1 (en) Communication control device, communication terminal device, server device, and communication control method
KR100701637B1 (en) Circuit-switched and packet-switched communications
US7990926B2 (en) Conversion of voice-over-IP media control messaging into mobile control channel signaling using a voice-over IP gateway
US7200400B2 (en) Mobile to 802.11 voice multi-network roaming utilizing SIP signaling with SIP proxy or redirect server
CN101491156B (en) Switching of multimedia sessions of a mobile terminal
EP1435748A1 (en) Handover between wireless networks of different technologies
KR100915781B1 (en) Network-initiated service change from speech to multimedia
JP2006521040A (en) Method and system for configuring application settings in a PushTalk service
WO2007043180A1 (en) Access network selecting method
US7315742B2 (en) Voice-over IP mobile roaming using SIP refer
CN102047648A (en) Mobile communications system, node device, and method for controlling migration between networks
WO2004077745A2 (en) Session maintenance method and mobile nodes for heterogeneous network
EP2187609B1 (en) Communication apparatus and communication control method
CN101489268A (en) Mobile terminal call fast switching method based on SIP
JP2008141490A (en) Emergency notification controller, radio communication terminal and base station
Thanh et al. Link-based service customization for NGN

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): BW GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase in:

Ref country code: JP