WO2007139161A1 - 移動端末及び通信方法 - Google Patents
移動端末及び通信方法 Download PDFInfo
- Publication number
- WO2007139161A1 WO2007139161A1 PCT/JP2007/061017 JP2007061017W WO2007139161A1 WO 2007139161 A1 WO2007139161 A1 WO 2007139161A1 JP 2007061017 W JP2007061017 W JP 2007061017W WO 2007139161 A1 WO2007139161 A1 WO 2007139161A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- communication
- mobile terminal
- data
- controller
- session
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1046—Call controllers; Call servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1083—In-session procedures
- H04L65/1095—Inter-network session transfer or sharing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/141—Setup of application sessions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- H04L69/164—Adaptation or special uses of UDP protocol
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/10—Flow control between communication endpoints
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/06—Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/08—Upper layer protocols
- H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
Definitions
- the present invention relates to a mobile terminal and a communication method, and more particularly to a communication technique for continuing a communication state even when a mobile terminal moves between access networks.
- FIG. 13 is an explanatory diagram for explaining a communication method using mopile IP.
- FIG. 13 shows a case where communication is performed between the mobile terminal la and the mobile terminal lb.
- a correspondence relationship between the home address (Ho A) 206 and the care-of address (CoA) 205 is registered in a home agent (HA) 201 that is a center server provided on the communication network 202.
- the home address 206 is an address that is assigned to each mobile terminal and does not change even when the mobile terminal moves.
- the care-of address 205 is an address that is assigned to communication media (network card) that can be used by the mobile terminal at the destination, and is changed as the mobile terminal moves.
- the home address 206 for the mobile terminal la is a constant care-of address 205 Is changed from the care-of address 205a to the care-of address 205b.
- the data packet transmitted from the mobile terminal lb receives the home agent 201 and is transferred from the home agent 201 to a foreign agent (not shown), and the foreign agent transmits this to the mobile terminal la.
- Patent Document 1 Japanese Unexamined Patent Application Publication No. 2006-80981
- Patent Document 2 Japanese Patent Laid-Open No. 2001-237869
- Patent Document 2 discloses a technique for transmitting and receiving communication data when communication is interrupted using a proxy, but this communication system performs location management in a mobile terminal. Yes, it is different from the communication system targeted by the present invention.
- the present invention has been made against the background described above, and the present invention provides a mobile terminal and a communication method capable of improving the continuity of communication and maintaining the communication quality of real-time communication. With the goal.
- a mobile terminal is a mobile terminal capable of wireless communication in a plurality of communication networks, and a controller for exchanging information necessary for establishing a communication session for communication with a communication partner.
- Communication means for establishing the communication session based on the exchanged necessary information, and executing communication with the communication partner through the established communication session, and the controller communicates with the communication partner via the call control device.
- the necessary information is acquired by executing call control between the necessary information and.
- the controller in response to a request from the communication application, the controller It is desirable to establish a local session with the case.
- controller when the controller performs a handover, it is preferable that the controller exchange information and shift to a new communication session.
- the controller transmits a signal indicating that data has been normally received from the communication partner to the communication partner.
- the controller transmits information specifying the normally received data to the communication partner when the communication session with the communication partner is disconnected.
- the controller can write data to a transmission buffer that is controlled so as to receive a signal indicating normal reception from a transmission destination and delete data from the transmission buffer on the controller. Depending on whether or not there is data that has been transmitted normally, if it is determined that there is data that has been transmitted normally, the data is discarded from the transmission buffer on the controller. It is good to.
- the controller of the mobile terminal preferably exchanges information necessary for establishing the communication session with the controller of the communication partner, and executes communication through the established communication session. .
- a communication method is a communication method between a first mobile terminal and a second mobile terminal capable of wireless communication in a plurality of communication networks, the first mobile terminal and the second mobile terminal.
- An information exchange step for exchanging information necessary for establishing a communication session for communication with the mobile terminal via the call control device, and establishing the communication session based on the exchanged necessary information
- a session establishment step for executing communication between the first mobile terminal and the second mobile terminal without passing through the call control device by an established communication session. is there.
- the information exchange step is executed by a controller that establishes a local session with the communication application in response to a request of the communication application.
- the information acquisition step is executed when a handover is performed.
- the first mobile terminal transmits a signal indicating normal reception from the second mobile terminal
- the method may further include a step of transmitting to the second mobile terminal, and a step of discarding data in the transmission buffer in response to the signal indicating the normal reception by the second mobile terminal.
- the first mobile terminal when the first mobile terminal disconnects a communication session, the first mobile terminal transmits information specifying normally received data to the second mobile terminal;
- the second mobile terminal may include a step of discarding the data of the transmission buffer based on the information specifying the normally received data.
- FIG. 1 is a configuration diagram of a wireless communication system to which a communication method according to the present invention is applied.
- FIG. 2 is a block diagram showing a configuration of a mobile terminal according to the present invention.
- FIG. 3 is a block diagram showing a specific software configuration of the mobile terminal according to the present invention.
- FIG. 4 is an explanatory diagram showing a connection method for realizing a communication method according to the present invention.
- FIG. 5 is an explanatory diagram showing a connection method for realizing the communication method according to the present invention.
- FIG. 6 is a diagram showing a network connection form in the communication system according to the present invention.
- FIG. 7 is a diagram showing a network connection form in the communication system according to the present invention.
- FIG. 8 is a sequence diagram showing a communication method according to the present invention.
- FIG. 9 is a sequence diagram showing a communication method according to the present invention.
- FIG. 10 is a sequence diagram showing a communication method that works on the present invention.
- FIG. 11 is a sequence diagram showing a communication method according to the present invention.
- FIG. 12A is an explanatory diagram for explaining a communication method according to the present invention.
- FIG. 12B is an explanatory diagram for explaining the communication method according to the present invention.
- FIG. 13 is an explanatory diagram for explaining a conventional communication method.
- a call control device 3 is connected to a packet switching network (IP network) 2.
- IP network 2 is a communication network serving as a core that performs voice or data communication by a packet switching method.
- the call control device 3 is also called a SIP server device (SIP: Session Initiation Protocol), and performs call control such as location registration of a mobile terminal.
- SIP Session Initiation Protocol
- SIP is a protocol that performs signaling related to sessions such as IP telephony and video conferencing, and is defined in RFC3261. Implementation with other protocols such as H.323 is also possible.
- the call control device 3 includes a network interface, a call control unit, a handover processing unit, a location registration processing unit, and a registration database 31, for example.
- the network interface is a physical network interface and a physical network interface. Network control functions such as corresponding device drivers and dial-up functions, and basic protocol stacks (TCP / UDP / IP, etc.) are provided.
- the call control unit transmits / receives a call control message to / from the mobile terminal la, and transmits / receives the call control message to the mobile terminal lb that is the destination, thereby executing a call / incoming call process.
- the handover processing unit performs voice handover processing between different networks such as a radio network and a packet switching network.
- the location registration processing unit executes location registration of the user's mobile terminal 1.
- the registration database 31 stores location information and connection status information of each user.
- the packet switching network 2 is connected to radio circuit switching networks 4a and 4b, radio packet switching networks (wireless LANs) 5a, 5b and 5c, and an IP telephone network 6.
- the radio circuit switching network 4a and the like are connected to the packet switching network 2 via the gateway device 41a and the like, and include a base station 42a and the like that can communicate with the mobile terminal 1.
- the wireless packet switching network 5a and the like include an access point 52a and the like that are connected to the packet switching network 2 via the router 51a and the like and can communicate with the mobile terminal 1.
- the IP telephone network 6 is connected to the packet switching network 2 via the router 61.
- the mobile terminal 1 can move seamlessly between communication networks while continuing voice and data communication.
- the mobile terminal 1 according to the present invention is installed with a middleware program 102 that executes session mobility control, which will be described in detail later.
- FIG. 2 is a block diagram showing a configuration of a mobile terminal that works on the present invention.
- the mobile terminal 1 includes a communication application processing unit 101, a session 'mobility control unit 102, a call control unit 103, an interface selection control unit 104, and a communication interface group 105.
- the communication application processing unit 101 is a functional block executed by an application program for realizing various communications such as a web browser and mail software.
- the session / mobility control unit 102 corresponds to a session / mobility controller which is a characteristic configuration of the present invention.
- the session mobility control unit 102 exchanges information necessary for establishing a communication session when communication is started or resumed between mobile terminals. The exchange is executed via the call control device 3.
- the communication process executed by the communication application processing unit 101 includes the session / mobility control unit 102, and the session 'mobility control unit 102 communicates with the communication partner.
- the communication application processing unit 101 performs communication processing with the session 'mobility control unit 102 by the same processing as that performed for communication with the communication partner.
- the call control unit 103 is provided in the session 'mobility control unit 102 and executes a process related to call control with the call control device 3.
- the interface selection control unit 104 executes processing for selecting an arbitrary communication interface from the communication interface group 105 based on a user request, communication cost, communication quality (electric field strength), and the like.
- the communication interface group 105 includes, for example, CSR—IF (Circuit Switch Radio Interface), which is an interface for the wireless circuit switching network 4, and PSR—IF (Packet Switch), which is an interface for the wireless packet switching network 5. Radio Interface) and other interfaces that support various communication networks are included.
- the communication interfaces included in this communication interface group 105 are the physical network interface, device driver corresponding to this physical network interface, network control function (NCU) such as dial-up function, and basic protocol stack (TCP / UDP / IP). Etc.
- FIG. 3 is a block diagram showing a specific software configuration of the mobile terminal that works for the present invention.
- the software corresponding to the application section 11 includes a TCP-based client application (hereinafter simply referred to as “TCP application”) 11 and a UDP-based client application (hereinafter simply referred to as “UDP application”). 12) is included.
- TCP application TCP-based client application
- UDP application 12 UDP-based client application
- UDP application 12 includes presence software 121, IM (Instant Messaging) software 122, PTT (Push To Talk) software 123, Video software 124, and VoIP (Voice Over Internet Protocol) software 125 for real-time communication Is done.
- IM Intelligent Messaging
- PTT Push To Talk
- Video software 124 Video software
- VoIP Voice Over Internet Protocol
- the middleware 13 includes a session 'mobility controller (hereinafter sometimes simply referred to as "SMS") 131 and a SIP processing program 132.
- SMS131 session in Figure 2 This is a communication computer program composed of middleware corresponding to the mobility control unit 102.
- the SIP processing program 132 corresponds to the call control unit 103.
- a dialer 14 is provided to exchange data with the SMC131.
- the dialer 14 is provided with a CCS (Cellular CS Network) interface 17.
- CCS Cellular CS Network
- the basic software 15 that is an OS (Operating System) includes a TCP / IP processing program 151, a UDPZIP processing program 152, and an interface selection and handover control program 153.
- the interface selection / handover control program 153 corresponds to the interface selection control unit 104.
- the communication interface 16 includes a WiFi interface 161, a CPS (Cellular PS Network) interface 162, a PHS interface 163, a Wire interface 164, a WiMAX interface 165, and the like.
- the SMC 131 is provided between the application 11 and the TCP / IP processing program 151 or the UDP / IP processing program 152.
- the SMC 131 also exchanges data with the TCP / IP processing program 151 and the UDP / IP processing program 152. Data is exchanged between the middleware 13 and the basic software 15 via the socket interface.
- the SMC 131 executes IPS (Inter-Process Communication) with the interface selection and handover control program 153.
- the SIP processing program 132 uses the UDP / IP processing program 152 to exchange signaling with the communication partner.
- FIG. 4 shows a case where communication is performed between the mobile terminal la functioning as a client and the mobile terminal Id functioning as a server via various communication networks including the packet switching network 2.
- the call control unit 132 of the mobile terminal la performs signaling using the SIP with the call control device 3 via the UDP processing program 1521 and the IP processing program 1512, and starts communication between the mobile terminals. Alternatively, when resuming, exchange of information necessary for establishing a communication session is performed via the call control device 3.
- the TCP applications 11 of the mobile terminals la and Id do not recognize the SMC 131, and normally communicate with each other. Is doing.
- the TCP application 11 such as the web browser of the mobile terminal la transmits and receives application data D1 to and from the SMC 131 via the TCP processing program 1511 and the IP processing program 1512. At this time, it is necessary for TCP application 11 to set a proxy in the local address.
- the SMC 131 is provided with an address correspondence table 1311. Based on this, the SMC 131 performs address conversion and the like between the SIP and the URI. Communicate with.
- the mobile terminal Id performs the same process as the mobile terminal la.
- the low power TCP connection in the mobile terminal 1 does not cause disconnection due to movement, but particularly when performing TCP communication between the SMC 131, the communication state is disconnected at the time of switching the communication network, that is, during the handover process. Is done.
- SMC131 can be implemented at the application level, so it can be realized relatively easily.
- the corresponding module must be installed for each application protocol such as ⁇ / FTP / POP / Telnet in SMC1 31.
- FIG. 5 is an explanatory diagram showing the TCP over UDP method, which is another connection method.
- the call control unit 132 of the mobile terminal 1 a performs signaling using the SIP with the call control device 3 via the UDP processing program 1521 and the IP processing program 1522, and performs TCP reconnection and retransmission control, etc. Do.
- the TCP application 11 of the mobile terminal la transmits / receives TCP / IP packet data D 3 to / from the SMC 131 via the TCP processing program 1511 and the Virtual IP processing program 1513. At this time, the TCP application 11 needs to set a proxy for the virtual IF address.
- the SMC131 has an address correspondence table 1311. Based on this, the SMC131 performs address conversion, etc., and encapsulates the TCP / IP packet data D3 with UDP / IP via the UDP processing program 1521 and the IP processing program 1522. Communicates with the mobile terminal Id that is the communication partner. Address mobility when moving through a powerful communication network established by an external UDP session is handled by SIP mobility between mobile terminal la and mobile terminal Id. The mobile terminal Id performs the same process as the mobile terminal la.
- FIG. 6 Each configuration shown in FIG. 6 is the same as that described in FIG. 1 and FIG.
- resource 10 is provided for each of mobile terminal la and mobile terminal Id, and mobile terminal la and mobile terminal Id are in communication.
- the mobile terminal la can be accommodated in the wireless packet switching network 5b, and the mobile terminal Id can be accommodated in another communication network by moving while being accommodated in the IP telephone network 6.
- the resource 10a is provided in the mobile terminal la, and the resource is transmitted to the sub-server 72 connected to the Internet network 7c connected to the packet switching network 2 and the router 71c. 10b is provided.
- the mobile terminal la can move and be accommodated in another communication network while being accommodated in the wireless packet switching network 5b.
- the relay device lc is accommodated in the wired network 6 connected to the packet switching network 2 via the router 61.
- the mobile terminal la can communicate with the web server 72 via the relay device lc, and can acquire the data of the resource 10b.
- FIG. 8 shows the initial signaling process that is first executed in communication between terminals (between client and server).
- the client obtains the web data from the web server by the web browser.
- the TCP application 11a on the client side (here, the web browser) establishes a TCP local session with the SMC 131a on the client side (S101).
- the TCP application 11a requests data of a predetermined URL from the SMC 131a (S102).
- the call control unit 103a of the SMC 131a converts the received URL into SIP (S103). Further, the call control unit 103a of the SMC 131a creates an entry in the correspondence table (S104). For example, TCP connection source address' Write the port, window size and segment size into the correspondence table.
- the call control unit 103a of the SMC 131a transmits an INVITE message to the call control device 3 (S105).
- the INVITE message is a connection request on SIP, and this INVI
- the TE message contains information necessary to establish a communication session for direct communication between SMC131a and SMC131b (here, a web server).
- Information necessary to establish a communication session includes the TCP connection source address of the client side SMC131a 'port, window size, and segment size.
- the call control device 3 transmits the received INVITE message to the SMC 131b on the server side installed in the mobile terminal 1 of the communication counterpart (S106). At this time, since the call control device 3 performs location registration management of each mobile terminal, based on the location registration information, the call control device 3 sends the INVITE message via the communication network in which the mobile terminal 1 of the communication partner is accommodated. It can be transmitted to the mobile terminal 1 of the communication partner.
- the SMC 131b on the server side receives the INVITE message, and stores at least information necessary for establishing a communication session (TCP / UDP session) in a predetermined storage area.
- the call control unit 103b of the SMC 131b further creates an entry in the correspondence table in response to receiving the INVITE message (S107). Further, a TCP local session is established between the SMC 131b and the server-side TCP application 1 lb (S108).
- the call control unit 103b of the SMC 131b sends information necessary for establishing a communication session to the call control device 3, such as the TCP connection source address of the server side SM C 131b 'port, window size, segment size, etc.
- a response signal including is transmitted (S109).
- the call control device 3 receives the response signal and transmits it to the SMC 131a on the client side (S110).
- the SMC 131a on the client side receives the response signal and stores at least information necessary for establishing a communication session in a predetermined storage area.
- a TCP or UDP session is directly established between SMC 131a and SMC 131b (Sl l l).
- SMC 131a and SMC 131b SMC 131b
- Sl l l SMC 131b
- information necessary for establishing a communication session is acquired by performing communication between the call control units 103a, 103b of the SMC 131a, via the call control device 3.
- a communication session is established directly between the SMC 131a and the SMC 131b without going through the call control device 3.
- SMC131af, SMC131b, S102, TCP application 1 la power The request signal having the same content as the received request signal is transmitted (SI 14).
- the SMC 131b transfers this request signal to the TCP application 1 lb (SI 15).
- the TCP application l ib sends a response signal to the SMC 131b (S1
- SMC131b sends a response signal to SMC131a on the client side (S1
- the SMC 131a transfers the response signal to the TCP application 1 la (S118).
- web data corresponding to the request signal is transmitted from the server-side TCP application l ib to the SMC 131b (S119).
- the SMC 131b transmits the received web data to the SMC 131a on the client side (S120).
- the SMC 131a transfers the received web data to the TCP application 11a (S121).
- a first TCP local session is established between the client-side TCP application 11a and the client-side SMC131a (S201), and a first TCP or UDP session is established between the SMC131a and the server-side SMC131b.
- the first TCP local session is established between the SMC 131b and the server-side TCP application l ib (S203).
- the mobile terminal 1 serving as a client moves and performs a handover process, and obtains a new IP address for realizing a second communication link with another communication network. It is assumed that the completion notification is received by the interface used for connection to the other communication network (S204).
- the SMC 131a on the client side sends a RE-IN VITE SIP signal to the call control device 3 in order to change to a communication session via the new communication network upon receipt of the notification of completion of acquisition of the new IP address.
- (Reconnection signal) is transmitted (S205).
- the RE_INVITE SIP signal includes the TCP connection source address of the client side SMC131a 'port, window size, segment size, response signal, etc. it can.
- the IP address is changed to the newly assigned IP address.
- the call control device 3 receives this signal and transfers it to the SMC 131b on the server side (S206).
- the server-side SMC 131b receives the RE_INVITE SIP signal and includes the new A new communication attribute (here, the changed new IP address) is recognized, and a response signal is transmitted to the call control device 3 based on this (S207).
- the response signal includes the SMC 13 lb TCP connection source address' port, window size, segment size, etc. on the server side.
- the call control device 3 receives this response signal and transfers it to the SMC 131a on the client side (S208). In this way, a second TCP (UDP) session with the new IP address is established between the SMC 131a on the client side and the SMC 131b on the server side (S209
- each of the SMCs 131a and 131b adds a correspondence table entry (S210 and S211). Thereafter, it is assumed that web data is transmitted from the server-side TCP application l ib to the SMC 131b (S212).
- the TCP application 11a, 1 lb since the TCP application 11a, 1 lb only recognizes the state where the first TCP local session is established as a remote session, it is performed between the SMCs 131. I don't recognize it.
- the SMC 131b transmits the web data directly to the SMC 131a on the client side using the second TCP (UDP) session without passing through the call control device 3 (S213).
- the server-side SMC 131b deletes the old entry in the correspondence table (S214).
- the SMC 131a on the client side transmits the received web data to the TCP application 11a (S215).
- the client-side TCP application 11a receives the web data and performs predetermined processing.
- the SMC 131a on the client side receives this data.
- the SMC 131a on the client side transmits the data to the SMC 131b on the server side using the second TCP (UDP) session (S217).
- the SMC 131a on the client side deletes the old entry in the correspondence table (S218).
- the SMC 131b on the server side transmits the received data to the TCP application l ib (S219).
- the server-side TCP application l ib receives the data and performs predetermined processing.
- the SMC transmission buffer data is transferred to the TCP transmission buffer and sent to the communication partner.
- the data transferred to the TCP transmission buffer is transferred to the SMC. Should not be discarded at the same time as the transfer from the send buffer.
- storing all of the past data in the SMC transmission buffer is difficult because the storage area allocated to the SMC transmission buffer is preferably as small as possible. In the present invention, these problems are solved by the following communication method.
- a data segment consisting of 1024 bytes (1) (2) ⁇ (K) continuously from the SMC 131b on the server side to the SMC 131a on the client side without going through the call control device 3 is TCP or UDP. (S301 to S303). Note that the segment size that determines the amount of data included in the data segment can be specified in the initial signaling described in FIG.
- the SMC 131a on the client side receives these data segments (1) to (K), and includes information indicating the last successfully received data segment ( ⁇ ) in the SIP-INFO signal.
- SIP—INFO signal is transmitted to the call control device 3 (S304).
- the SMC 131a on the client side receives a data segment of a predetermined number of window sizes, it transmits a SIP-INFO signal including an ACK signal (a signal indicating normal reception of data).
- the call control device 3 receives the SIP-INFO signal and transfers it to the SMC 131b on the server side (S305). This window size can be specified in the signaling described with reference to FIGS.
- the server-side SMC 131b receives the forwarded SIP-INFO signal, It becomes possible to recognize the last data segment (K) received by the SMC 131a on the side and discard the data segments (1) to (K) stored in the transmission buffer on the server side.
- the server-side SMC 131b transmits a response signal to the call control device 3 after discarding the data segments (1) to (K) (S306).
- the call control device 3 receives the response signal and transfers it to the SMC 131a on the client side (S307).
- the SMC 131a on the client side receives the response signal.
- the server-side SMC 131b resumes data transmission and transmits data segments (K + 1) and (K + 2) (S308, S309). Thereafter, it is assumed that the mobile terminal 1 has moved to a disconnected state due to the movement of the mobile terminal 1, and the transmission of the data segments (K + 3) and (K + 4) has been disconnected halfway (S310, S311).
- the SMC 131a on the client side adds to the data segment (successfully received last) in addition to the new IP address newly assigned by the destination communication network in the Re-INVITE signal that is a reconnection signal.
- the Re-INVITE signal including the information indicating K + 2) is transmitted to the call control device 3 (S312).
- the call control device 3 receives the Re-INVITE signal and transfers it to the SMC 13 lb on the server side (S313).
- the SMC 131b on the server side receives the Re-INVITE signal, recognizes that the data segment (K + 2) has been transmitted normally, and stores the data segment (K + 1), (K + 2) can be discarded. Then, the SMC 131b on the server side resumes data transmission and transmits data segments (K + 3) and (K + 4) (S314, S315).
- the receiving side SMC 131 determines that a predetermined amount of data has been received, the information for identifying the data that has been successfully received last is obtained. Since transmission is made to the SMC 131 on the transmission side, the SMC 131 on the transmission side can discard from the transmission buffer even data that has been successfully transmitted. Furthermore, since the information identifying the data that was successfully received last is transmitted from the receiving SMC 131 to the transmitting SMC 131 at the time of reconnection, the transmitting SMC 131 receives the data that has been successfully transmitted. It is possible to transmit data to be transmitted after. In the example shown in FIG. 10, the number of data segments is managed. However, the present invention is not limited to this, and information on the data amount such as the number of bytes may be managed.
- the data segment (1) (2) ⁇ ⁇ ⁇ (K + 2) continues from the server-side SMC 131b to the client-side SMC 131a without going through the call control device 3. Sent by TCP (S401 to S405). The client side SMC 131a does not transmit the power ACK signal for receiving these data segments (1) to (K + 2) to the server side SMC 131b.
- the data segments in the transmission buffer are sequentially discarded.
- data segments (1) to (20) are stored in the transmission buffer of the SMC 131b on the server side (hereinafter simply referred to as “SMC transmission buffer”).
- SMC transmission buffer the transmission buffer of the SMC 131b on the server side
- data segments (1) to (10) are written to the transmission buffer on the transport layer defined by TCP (hereinafter simply referred to as “TCP transmission buffer”).
- TCP transmission buffer When the data segment stored in the TCP transmission buffer is transmitted normally and an ACK signal is received by the TCP from the transmitting party, the normally transmitted data segment is deleted from the TCP transmission buffer.
- the SMC131b knows that the capacity of the TCP transmission buffer is 10 data segments when the SMC transmission buffer capacity fails to write to the TCP transmission buffer. Recognizes that data segment 10 including data segment 1 has not yet been successfully transmitted to SMC131a on the client side. In this case, the SMC 131b does not discard the data segments (1) to (: 10) stored in the SMC transmission buffer because they may be retransmitted. In this case, it is guaranteed that the client side SMC can acquire all the segments that have reached the client side TCP receive buffer.
- the segment in the client side TCP receive buffer is also subject to the retransmission request.
- the TCP receive buffer capacity on the client side is 5 segments, it can be solved by increasing the TCP send buffer capacity of 10 on the server side and considering 15 segments as the retransmission request target.
- the first segment is written when the 16th segment is written. That the client has reached the SMC on the client side.
- the TCP receive buffer size on the client side can be notified by the signaling shown in Figs.
- the SMC 131b when the SMC 131b was able to write the data segment (11) from the SMC transmission buffer to the TCP transmission buffer, the TCP corresponding to the data segment (11) It is possible to recognize that there is a vacancy in the transmission buffer, that is, the data segment (1) having the same amount of data as that vacant has already been successfully transmitted to the SMCl 31a on the client side. In this case, the SMC 131b can discard the normally transmitted data segment (1) from the SMC transmission buffer.
- the TCP determines that normal transmission has been completed only after receiving an ACK from the data transmission destination, and transmits data from the TCP transmission buffer. This is because it stipulates deletion. That is, this method can be applied to a transmission buffer that is controlled to receive a signal indicating normal reception of transmission destination power and delete data.
- the server-side SMC 131b resumes data transmission and transmits data segments (K + 3) and (K + 4) (S406, S407). It is assumed that the transmission of the data segments (K + 3) and (K + 4) is interrupted in the middle (S406, S407).
- the SMCl 31a on the client side adds the new IP address newly assigned by the destination communication network in the Re-INVITE signal, which is a reconnection signal, to the last data segment successfully received.
- the Re-INVITE signal including the information indicating (K + 2) is transmitted to the call control device 3 (S408).
- the call control device 3 receives the Re-INVITE signal and transfers it to the server-side SMC 131b (S409).
- the SMC 131b on the server side receives the Re—INVITE signal, recognizes that the data segment (K + 2) has been transmitted normally, resumes data transmission, and receives the data segment (K + 2).
- Data segments (K + 3) and (K + 4) to be transmitted next are transmitted (S410, S411)
- the SMC 131 on the transmission side can discard from the transmission buffer even data that has been successfully transmitted. Furthermore, since the information identifying the data that was successfully received last is transmitted from the SMC 131 on the receiving side to the SMC 131 on the sending side at the time of reconnection, the SMC 131 on the sending side transmits the data that has been successfully transmitted. It is possible to send data to be sent later.
- the present invention can be used for a mobile terminal capable of wireless communication in a plurality of communication networks, and is suitable for improving the continuity of connection-type communication and maintaining the communication quality of real-time communication.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/301,458 US20100015980A1 (en) | 2006-05-31 | 2007-05-30 | Mobile Terminal and Communication Method |
EP07744430A EP2034671A4 (en) | 2006-05-31 | 2007-05-30 | MOBILE TERMINAL AND COMMUNICATION PROCESS |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2006-150857 | 2006-05-31 | ||
JP2006150857A JP2007324788A (ja) | 2006-05-31 | 2006-05-31 | 移動端末及び通信方法 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2007139161A1 true WO2007139161A1 (ja) | 2007-12-06 |
Family
ID=38778679
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2007/061017 WO2007139161A1 (ja) | 2006-05-31 | 2007-05-30 | 移動端末及び通信方法 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20100015980A1 (ja) |
EP (1) | EP2034671A4 (ja) |
JP (1) | JP2007324788A (ja) |
CN (1) | CN101455117A (ja) |
WO (1) | WO2007139161A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009213108A (ja) * | 2008-02-05 | 2009-09-17 | Hitachi Communication Technologies Ltd | 移動通信システムにおける移動ノード装置のipアドレスの切替え方法、移動ノード装置およびサーバ |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5070568B2 (ja) * | 2007-06-08 | 2012-11-14 | ソフトバンクモバイル株式会社 | 通信モジュール、通信方法、通信プログラム、通信端末、及び通信制御装置 |
US9705935B2 (en) | 2008-01-14 | 2017-07-11 | Qualcomm Incorporated | Efficient interworking between circuit-switched and packet-switched multimedia services |
WO2009093308A1 (ja) * | 2008-01-22 | 2009-07-30 | Ntt Pc Communications, Inc. | 接続制御方法、接続制御サーバ装置、接続制御クライアント装置、及びプログラム |
JP4540720B2 (ja) * | 2008-04-02 | 2010-09-08 | 株式会社エヌ・ティ・ティ・ドコモ | データ通信端末、プロキシ装置、データ通信システム、及びデータ通信方法 |
JP4639246B2 (ja) * | 2008-06-20 | 2011-02-23 | 京セラ株式会社 | 無線端末、無線基地局および無線通信方法 |
TWI613285B (zh) * | 2010-09-03 | 2018-02-01 | 聖高拜磨料有限公司 | 粘結的磨料物品及形成方法 |
WO2013132560A1 (en) * | 2012-03-06 | 2013-09-12 | Nec Corporation | Communication apparatus, control apparatus, communication system, packet processing method, communication apparatus control method, and program |
TWI508609B (zh) * | 2014-01-08 | 2015-11-11 | 晶睿通訊股份有限公司 | 無線網路設定方法與無線網路系統 |
KR101984120B1 (ko) | 2014-09-19 | 2019-09-03 | 콘비다 와이어리스, 엘엘씨 | 서비스 레이어 세션 마이그레이션 및 공유 |
US10710207B2 (en) * | 2015-08-14 | 2020-07-14 | The Texas A&M University System | Method and apparatus for performing targeted polishing via manipulation of magnetic-abrasive fluid |
US10616285B2 (en) * | 2016-04-26 | 2020-04-07 | Comcast Cable Communications, Llc | Establishing and managing connections for real time communications |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001237869A (ja) | 2000-02-24 | 2001-08-31 | Nippon Telegr & Teleph Corp <Ntt> | サービス継続システムおよび移動端末 |
WO2001099355A1 (fr) * | 2000-06-23 | 2001-12-27 | Mitsubishi Denki Kabushiki Kaisha | Procede et systeme de retransmission de paquets |
JP2004527928A (ja) * | 2000-11-24 | 2004-09-09 | コロンビテック エービー | 異種通信ネットワーク間のハンドオーバ方法 |
JP2006080981A (ja) | 2004-09-10 | 2006-03-23 | Fujitsu Ltd | ハンドオーバ方法並びにこれを適用した移動通信システムおよび移動端末 |
JP2006115453A (ja) * | 2004-10-12 | 2006-04-27 | Hitachi Ltd | 移動通信制御方法及び移動通信システム |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH11110315A (ja) * | 1997-07-31 | 1999-04-23 | Matsushita Electric Ind Co Ltd | 通信装置 |
FI113323B (fi) * | 2000-08-21 | 2004-03-31 | Nokia Corp | Datapakettinumeroiden synkronointi pakettivälitteisessä tiedonsiirrossa |
SE0004338L (sv) * | 2000-11-24 | 2002-05-25 | Columbitech Ab | Datanätbaserat system |
JP4009136B2 (ja) * | 2001-06-07 | 2007-11-14 | 富士通株式会社 | 課金システム |
DE60329346D1 (de) * | 2002-03-13 | 2009-11-05 | Ntt Docomo Inc | Mobiler Knoten, Mobilkommunikationssystem, und Kommunikationssteuerungsprogramm |
US7814218B1 (en) * | 2002-10-17 | 2010-10-12 | Astute Networks, Inc. | Multi-protocol and multi-format stateful processing |
FI20031779A0 (fi) * | 2003-12-05 | 2003-12-05 | Nokia Corp | Menetelmä, järjestelmä ja lähetettävän puolen yhteyskäytäntöyksikkö datapakettien lähettämiseksi kuittaamattoman toimintamuodon palveluissa |
US7631239B2 (en) * | 2003-12-29 | 2009-12-08 | Electronics And Telecommunications Research Institute | Method for retransmitting packet in mobile communication system and computer-readable medium recorded program thereof |
US7307955B2 (en) * | 2003-12-31 | 2007-12-11 | Nokia Corporation | Method and equipment for lossless packet delivery to a mobile terminal during handover |
KR100592412B1 (ko) * | 2004-01-05 | 2006-06-22 | 삼성전자주식회사 | 실시간 트래픽 특성을 고려하여 큐를 관리하는 액세스네트워크 장치 및 그 큐 관리 방법 |
US7979072B2 (en) * | 2004-06-04 | 2011-07-12 | Nortel Networks Limited | Method and system for soft handoff in mobile broadband systems |
EP1821441A4 (en) * | 2004-12-10 | 2011-03-02 | Fujitsu Ltd | SENDING DEVICE, RECEPTION DEVICE AND SENDING / RECEIVING METHOD THEREFOR |
GB2429877B (en) * | 2005-09-06 | 2008-02-06 | Motorola Inc | Radio link handover in a cellular communication system |
-
2006
- 2006-05-31 JP JP2006150857A patent/JP2007324788A/ja active Pending
-
2007
- 2007-05-30 US US12/301,458 patent/US20100015980A1/en not_active Abandoned
- 2007-05-30 CN CNA2007800198862A patent/CN101455117A/zh active Pending
- 2007-05-30 EP EP07744430A patent/EP2034671A4/en not_active Withdrawn
- 2007-05-30 WO PCT/JP2007/061017 patent/WO2007139161A1/ja active Search and Examination
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001237869A (ja) | 2000-02-24 | 2001-08-31 | Nippon Telegr & Teleph Corp <Ntt> | サービス継続システムおよび移動端末 |
WO2001099355A1 (fr) * | 2000-06-23 | 2001-12-27 | Mitsubishi Denki Kabushiki Kaisha | Procede et systeme de retransmission de paquets |
JP2004527928A (ja) * | 2000-11-24 | 2004-09-09 | コロンビテック エービー | 異種通信ネットワーク間のハンドオーバ方法 |
JP2006080981A (ja) | 2004-09-10 | 2006-03-23 | Fujitsu Ltd | ハンドオーバ方法並びにこれを適用した移動通信システムおよび移動端末 |
JP2006115453A (ja) * | 2004-10-12 | 2006-04-27 | Hitachi Ltd | 移動通信制御方法及び移動通信システム |
Non-Patent Citations (1)
Title |
---|
See also references of EP2034671A4 |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009213108A (ja) * | 2008-02-05 | 2009-09-17 | Hitachi Communication Technologies Ltd | 移動通信システムにおける移動ノード装置のipアドレスの切替え方法、移動ノード装置およびサーバ |
Also Published As
Publication number | Publication date |
---|---|
US20100015980A1 (en) | 2010-01-21 |
EP2034671A1 (en) | 2009-03-11 |
JP2007324788A (ja) | 2007-12-13 |
CN101455117A (zh) | 2009-06-10 |
EP2034671A4 (en) | 2010-12-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2007139161A1 (ja) | 移動端末及び通信方法 | |
US9825802B2 (en) | Management of seamless handover between different communication systems in an IP dual-mode terminal | |
EP1929744B1 (en) | Wireless voip/vip roaming to access point of different network type | |
US7620015B2 (en) | Method and system for seamless handover of mobile devices in heterogeneous networks | |
EP1597934B1 (en) | Radio terminal session control and interface set up method | |
KR100498932B1 (ko) | 이동 노드들로 구성된 무선망에서의 세션 설정 장치 및 방법 | |
US8045522B2 (en) | Method and system for performing handoff in wireless networks | |
JP4856233B2 (ja) | 共通ipアドレス付きの移動端末および無線装置 | |
JP2007525130A (ja) | ワイヤレスネットワークにわたるインスタントメッセージ及びインターネット電話のためのシームレスなインターフェイス | |
KR20120067963A (ko) | 물리 네트워크들이 변경될 때 tcp 접속을 로밍하기 위한 시스템 및 방법 | |
EP1438812A2 (en) | Method and packet switched communication network with enhanced session establishment | |
US20090310495A1 (en) | Session Control System, Session Control Method, and Mobile Terminal | |
CN102984785B (zh) | 通过多个网络发送数据 | |
CN105141588A (zh) | Ip双模终端中不同通信***之间的无缝切换的管理 | |
JP5000355B2 (ja) | 無線通信端末、制御方法 | |
JP3935693B2 (ja) | データ通信用接続制御システム及び情報通信端末 | |
JP4605381B2 (ja) | 通信制御システム及び管理装置 | |
JP2006094105A (ja) | トンネリング方法および装置、ならびにそのプログラムと記録媒体 | |
Noonan et al. | Path Management and Selection in Heterogeneous Wireless Networks | |
JP2005223811A (ja) | 通信端末、通信端末用プログラム及び通信インタフェース切替方法 | |
JP2012039238A (ja) | 通信ネットワークシステム、パケット転送装置、宅内パケット転送装置、及び通信ネットワークシステム用セッション制御方法 | |
MXPA01004107A (en) | A mobile terminal and wireless device with common ip address | |
EP1733590A1 (en) | Method and system for seamless handover of mobile devices in heterogenous networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200780019886.2 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07744430 Country of ref document: EP Kind code of ref document: A1 |
|
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2291/MUMNP/2008 Country of ref document: IN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2007744430 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 12301458 Country of ref document: US |
|
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) |