WO2008044265A1 - Call connection processing method and message transmitting and receiving proxy device - Google Patents
Call connection processing method and message transmitting and receiving proxy device Download PDFInfo
- Publication number
- WO2008044265A1 WO2008044265A1 PCT/JP2006/319958 JP2006319958W WO2008044265A1 WO 2008044265 A1 WO2008044265 A1 WO 2008044265A1 JP 2006319958 W JP2006319958 W JP 2006319958W WO 2008044265 A1 WO2008044265 A1 WO 2008044265A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- call connection
- mobile terminal
- user terminal
- message
- processing method
- 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
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2854—Wide area networks, e.g. public data networks
- H04L12/2856—Access arrangements, e.g. Internet access
-
- 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/1045—Proxies, e.g. for session initiation protocol [SIP]
-
- 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/40—Support for services or applications
-
- 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
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1016—IP multimedia subsystem [IMS]
Definitions
- the present invention relates to a call connection processing method and a message transmission / reception proxy device, and in particular, a call connection processing method and message for performing call connection between a user terminal and a backbone network via an access network using the SIP protocol.
- the present invention relates to a transmission / reception proxy device.
- IP Internet Protocol
- SIP Session Initiation Protocol
- IMS IP Multimedia Subsystem
- FIG 18 shows a configuration example of the Evolved 3GPP system, which is a next-generation network system connected to IMS (see Non-Patent Document 1).
- the Evolved 3GPP system is a base station eNB (evolved-UTRAN NodeB) la to ln, an access gateway aG W (evolved-UTRAN Access Gateway) 2a to 2c that controls them together, and an anchor for the entire network It consists of IAS A (Inter Access System Anchor) 3, etc., and aGW 2a-2c and IASA 3 form an access network ACN for IMS.
- eNB evolved-UTRAN NodeB
- aG W evolved-UTRAN Access Gateway
- the base stations eNB la to ln have almost the same functions as those of the conventional base station NB and the radio network controller RNC (Radio Network Controller).
- RNC Radio Network Controller
- the mobile terminal (Mobil e Station) and the eNB are connected by RRC (Radio Resource Control), and then the mobile terminal and aGW are connected by Attach h and the unique terminal ID of the mobile terminal Power GW is notified.
- the aGWs 2a to 2c exchange messages between the mobile terminals 4a and 4b and the IMS 5, and form an LTE-RAN (Radio Access Network) with the eNB la to ln.
- LTE-RAN Radio Access Network
- IA SA3 with router-like functions connects to IMS 5 and to HSS (Home Subscriber Server) 6, PCRF (Policy & Charging Rule Function) 7, and PCEF (Policy & Charging Enhance Function).
- HSS Home Subscriber Server
- PCRF Policy & Charging Rule Function
- PCEF Policy & Charging Enhance Function
- the HSS is a sano that stores the subscriber's profile, the PCRF determines the bearer conditions, and the PCRF sets the determined bearer in the aGW.
- the HSS authenticates the user terminal via IASA 3 and aGW2a to 2c, and the aGW registers in the HSS6 that it is in charge of the user's call.
- aGW 2a to 2c After the completion of processing such as authentication and registration, if a call is made from the mobile terminal, aGW 2a to 2c will be eNB la to ln
- Call control SIP messages from user terminals received via IASA 3 are sent to CSCF (Call Session Control Function) 8 of IMS 5 via IASA 3, and received via CSIA 8 of IMS 5 via IASA 3.
- a control SIP message is sent to the mobile terminals 4a and 4b via eNB la to ln. Then, after the call connection control is completed, the aGW 2a to 2c transmits the data from the mobile terminal to the eNB la
- FIG. 19 is an explanatory diagram of the procedure for registering the mobile terminal in IMS5 when purchasing the mobile terminal 4a which is an IMS terminal.
- the mobile terminal and eNB are connected by RRC (Radio Resource Control), and after that, the mobile terminal and aGW are connected by Attach, and the mobile terminal's unique number (Terminal ID) Power GW is notified.
- RRC Radio Resource Control
- HSS 6 authenticates mobile terminal 4a via IASA 3, aGW2a, and aGW is in charge of the call of mobile terminal 4a.
- MME Mobile Management Entity
- the mobile terminal 4a requests registration to the CSCF 8 of IMS5 to receive the IMS service (Register). Since CSCF8 is not registered in mobile terminal 4a, 401
- the mobile terminal 4a needs to register again with the authentication data.
- the CSCF refers to the authentication data and registers the mobile terminal 4a if it is valid, and transmits a 200OK message indicating that it has been registered to the mobile terminal 4a.
- the mobile terminal 4a can receive the IMS service.
- FIG. 20 is a diagram for explaining the calling procedure of the IMS terminal.
- the mobile terminal 4a When the mobile terminal 4a makes a call, the mobile terminal and the eNBlla are connected by RRC (Radio Resource Control), and after that, the mobile terminal and the aGW are connected by Attach, and the mobile terminal's unique number (terminal ID) is notified to aGW.
- RRC Radio Resource Control
- HSS 6 authenticates mobile terminal 4a via IAS A 3, aGW2a.
- the mobile terminal 4a sends an INVITE message to the CSCF 8, and the CSCF 8 returns a 100 Trying message indicating that the INVITE has been accepted.
- the INVITE message contains the QoS information desired by the calling mobile terminal 4a (for example, bi-directional audio / video communication), codec information, the type of message used, and the presence / absence of a confirmation response in addition to the other party's telephone number.
- QoS stands for Quality of Service.
- the CSCF 8 sends an INVITE message to the terminating mobile terminal 14a, but if the mobile terminal and the aGW are not connected, the aGW 12a paging. If the receiving side mobile terminal 14a responds by this pagin, RRC connection and authentication / confidential processing are performed in the same way as the originating side.
- the aGW 12a sends an INVITE message to the mobile terminal 14a.
- the mobile terminal 14a receives the INVITE message, it returns a 100 Trying message indicating acceptance and issues a 183 Session Progress indicating the progress of the session.
- the 183 Session Progress message includes QoS information (for example, two-way audio / video communication) of the terminating mobile terminal 14a, codec information, type of message to be used, presence / absence of a confirmation response, and the like.
- QoS information for example, two-way audio / video communication
- CSCF 8 receives the 183 Session Progress message, it notifies the originating mobile terminal 4a, and when the mobile terminal 4a receives the 183 Session Progress message, it sends PRACK, which is an acknowledgment, via CSCF 8 to the receiving mobile terminal 14a. Send to.
- PRACK which is an acknowledgment
- the AF (Application Function) of CSCF 8 performs QoS information in the INVITE message 183 Session Progress message and contract information of each mobile terminal.
- the information necessary for bearer setting is passed to PCRF / PCEF7, and PCRF / PCEF7 performs bearer setting between calling side aGW2a and called side aGW12a. Set up bearer with 14a.
- the originating mobile terminal 4a If the originating mobile terminal 4a updates based on the bearer settings, it sends UPDATE to the terminating mobile terminal 14a via CSCF 8. If the receiving mobile terminal 14a also completes the update based on the bearer settings, a 200OK message is sent to the calling mobile terminal 4a via CSCF 8 and a ringing tone generation message (Ringing) is also sent. . If the originating mobile terminal 4a receives the Ringing message, it sends an acknowledgment PRACK to the terminating mobile terminal 14a via CSCF 8, and the terminating mobile terminal 14a sends a PRACK reception to the originating mobile terminal 4a by a 200OK message.
- Ringing ringing tone generation message
- the called mobile terminal 14a sends 200OK (INVITE) to the calling mobile terminal 4a via CSCF 8, and the receiving mobile terminal 4a returns ACK to the called mobile terminal 14a when receiving 200OK (INVITE).
- This enables communication between the mobile terminals 4a and 14a.
- Figure 21 shows the sequence when the receiving terminal 14a is out of service area and there is no response even if the aGW 12a is paging.
- CSCF 8 monitors the elapsed time since the INVITE was sent to the aGW 12a, and the elapsed time is less than the set time. If the lOOTrying message is not returned even if it becomes large, it times out and 408 Request
- Calling side mobile terminal 14a notifies the calling side mobile terminal 4a that the receiving side mobile terminal 14a does not respond with Timeout, and the calling side mobile terminal moves.
- Terminal 4a transmits ACK to CSCF 8 and ends the process.
- FIG. 22 shows a sequence when the called terminal 14a is in the busy state.
- the called terminal 14a receives the INVITE from the CSCF 8, if it is busy, it returns a 486 Busy Here message.
- CSCF 8 sends a 486 Busy Here message to originating mobile terminal 4a to notify that terminating mobile terminal 14a is busy, and originating mobile terminal 4a sends ACK to CS CF 8 for processing.
- CSCF 8 sends a 486 Busy Here message to originating mobile terminal 4a to notify that terminating mobile terminal 14a is busy, and originating mobile terminal 4a sends ACK to CS CF 8 for processing.
- FIG. 23 is a sequence in the case where an error occurs during the call connection procedure of processing. Arrival If any error occurs after the receiving mobile terminal 14a generates a 200OK message in response to the UPDATE reception, an error message 480 Temporarily Unavailable indicating that the XXX ( error ) message is temporarily unavailable, such as CSCF 8 To the originating mobile terminal 4a, and the originating mobile terminal 4a sends ACK to CSCF 8 and ends the process.
- Patent Document 2 The second prior art (see Patent Document 2) enables signaling to be transferred to a terminal without going through a redundant path even when the terminal moves beyond the subnet of the acquired address.
- the conventional technology is not intended to reduce the number of signaling in the radio section at the time of call connection, and is not intended to reduce call connection time.
- an object of the present invention is to reduce the number of signaling in a radio section at the time of call connection. Another object of the present invention is to reduce the call connection time prior to the start of communication.
- Non-Patent Document 1 3GPP, TS24.228v5.14.0
- Patent Document 1 Japanese Translation of Special Publication 2006—506012
- Patent Document 2 Japanese Patent Laid-Open No. 2005-64646
- a first aspect of the present invention is a call connection processing method for performing call connection between a user terminal and a backbone network via an access network using a SIP protocol, and a device (proxy device) in the access network Instructing the user terminal to transmit a predetermined SIP signaling message to the backbone network on behalf of the user terminal, and in accordance with the instruction, the SIP signaling message having the predetermined SIP signaling message is Do not send to terminal or other messages on behalf of user terminal
- a step of transmitting to the trunk network and a step of transmitting and receiving messages other than the predetermined SIP signaling message between the user terminal and the backbone network are included.
- the instruction in the first step is performed by declaring in the SIP protocol INVITE message that the user terminal (1) does not request a reliability response and (2) does not specify a precondition for bearer configuration.
- the proxy device performs transmission / reception of a SIP signaling message related to a reliability response and transmission / reception of a predetermined SIP signaling message after setting a bearer instead of the user terminal.
- the proxy device when the user terminal instructs to perform transmission / reception of a predetermined SIP signaling message on behalf of the user terminal, transmits / receives the predetermined SIP signaling message to the user.
- the call connection processing method further includes a call connection processing sequence from the time when a caller terminal terminal power IP protocol I NVITE message is transmitted at the time of call connection to the point immediately before the callee user terminal responds with 200 OK to the INVITE message.
- Network of the called user terminal Steps independently proceeding on the calling side regardless of the connection state to the network, after the calling user terminal receives the 200OK from the receiving user terminal, the calling user terminal and the receiving user terminal via the backbone network And performing communication between them.
- the second aspect of the present invention is provided in an access network that accesses a backbone network that performs call connection processing with a user terminal using the SIP protocol, and acts as a proxy for the user terminal during call connection.
- Is a message transmission / reception proxy device that transmits and receives SIP signaling messages to and from the user information storage unit that acquires and stores capability information information and subscriber information of user terminals, processing that receives and analyzes SIP signaling messages, Bearer setting process using the stored information, relay process of SIP signaling message between mobile terminal and base station, processing unit for processing to create and send SIP signaling message on behalf of mobile terminal, transmission / reception of message to / from user terminal Transmission / reception unit, transmission / reception unit for sending / receiving messages to / from the backbone network side Equipped with, Ru.
- FIG. 1 is a diagram illustrating the principle of the present invention.
- FIG. 2 is a configuration diagram of a communication system to which the present invention can be applied.
- FIG.3 This is a processing flow that determines which sequence processing to execute depending on whether or not the IMS terminal is equipped with SIP.
- FIG. 4 An explanatory diagram of the procedure for registering an IMS terminal equipped with SIP improved for Evolved 3GPP in IMS after purchase.
- FIG. 5 is an explanatory diagram of a call connection sequence (first embodiment) at the time of a call of an IMS mobile terminal equipped with SIP improved for Evolved 3GPP.
- FIG. 6 is an explanatory diagram of a modification of the call connection sequence of the first embodiment.
- FIG. 7 shows another call connection sequence (second embodiment) when an IMS mobile terminal equipped with SIP improved for Evolved 3GPP is called.
- FIG. 8 is an explanatory diagram of a modification of the call connection sequence of the second embodiment.
- FIG. 9 is an explanatory diagram of a call connection sequence (first embodiment) at the time of calling a normal IMS mobile terminal not equipped with SIP improved for Evolved 3GPP.
- FIG. 10 is an explanatory diagram of a modification of the call connection sequence of the first embodiment.
- FIG. 11 shows another call connection sequence (second embodiment) when a normal IMS mobile terminal makes a call.
- FIG. 12 is an explanatory diagram of a modification of the call connection sequence of the second embodiment.
- FIG.13 Call connection sequence (out of service area) of IMS terminal equipped with SIP improved for Evolved 3GPP.
- FIG.14 Call connection sequence (out of service area) of IMS terminal equipped with SIP improved for Evolved 3GPP.
- FIG. 15 Call connection sequence (busy state) of an IMS terminal equipped with SIP improved for Evolved 3GPP.
- FIG. 16 Call connection sequence (busy state) of an IMS terminal equipped with SIP improved for Evolved 3GPP.
- FIG. 18 This is an example configuration of the Evolved 3GPP system, which is a next-generation network system connected to IMS.
- FIG. 19 is an explanatory diagram of a procedure for registering a mobile terminal in IMS when the mobile terminal is purchased as an IMS terminal.
- FIG. 20 is an explanatory diagram of a calling procedure of an IMS terminal.
- FIG. 22 is a sequence in a case where the receiving terminal power is in a 3 ⁇ 4 usy state.
- FIG. 23 This is a sequence when an error occurs during the call connection procedure of processing.
- the present invention reduces the number of data in the radio section by reducing the number of SIP protocol messages between the mobile terminal and the IMS in the radio section, and reduces the occupied time of the frequency band.
- the present invention makes it possible for the intermediate node to perform connection processing in advance during the call of the called terminal and to reduce the number of nodes through which the message passes, thereby shortening the call connection time.
- the IMS (core network) side uses the SIP message already determined by the specifications. It is determined that call control cannot be performed without transmission and reception. For this reason, the number of messages that reach IMS and the number of messages that are sent from IMS cannot be reduced. Therefore, in the present invention, transmission / reception of a part of SIP message originally transmitted / received between the IMS and the mobile terminal UEOJser Equipment) to / from an intermediate node (referred to as a proxy device) between the base station eNB and IMS performing wireless communication. To act. In this way, it is possible to minimize the number of SIP messages that are transmitted to the mobile terminal and received from the mobile terminal, thereby reducing the number of messages in the radio section.
- the proxy device may be a base station eNB, but in the embodiment, aGW is used as the proxy device.
- FIG. 1 is a diagram for explaining the principle of the present invention.
- FIG. 1 (A) shows the flow of a SIP message in the present invention
- FIG. 1 (B) shows the flow of a conventional SIP message.
- the aGW2a, 2b which is the proxy device, substitutes the mobile terminal for transmission / reception of a part of the SIP message that is originally transmitted / received between the CSCF 8 of the IMS 5, the backbone network, and the mobile terminals 4a, 4b. To do.
- the aGW 2a, 2b sends only the minimum necessary SIP message received from the CSCF 8 to the mobile terminals 4a, 4b, and receives only the minimum necessary SIP message from the mobile terminal and sends it to the CSCF 8. .
- the number of messages in the wireless section can be reduced.
- all SIP messages are transmitted and received between CSCF 8 and mobile terminals 4a and 4b via aGW 2a and 2b, so the number of messages in the radio section becomes very large.
- the receiving mobile terminal is configured so that part of the SIP message that is originally transmitted and received between CSCF 8 and the receiving mobile terminal can be delegated to the receiving aGW (not shown). This makes it possible to advance the call connection sequence on the caller side during connection between the callee side aGW and the callee mobile terminal, and to shorten the call connection time.
- Fig. 2 is a block diagram of a communication system to which the present invention can be applied.
- the left side of the backbone network IM S5 is the Evolved 3GPP system on the transmitting side. I have.
- the right side of IMS5 is the Evolved 3GPP system on the receiving side, which has base stations lla, aGW12a, IASA13, mobile terminal 14a, and PCRF / PCEF17 IMS5 has CSCF8 and AF (Application Function) 9 on the transmitting side and CSCF18 and AF19 on the receiving side to perform call connection sequence processing.
- CSCF8 and AF (Application Function) 9 9 on the transmitting side and CSCF18 and AF19 on the receiving side to perform call connection sequence processing.
- CSCF force S Performs call connection sequence processing, which will be described later, and the AF analyzes the information required for the bearer setting presented from the CSCF and instructs the PCRF / PCEF to set the bearer.
- IMS5 transmits and receives data between the caller and receiver via a router (not shown) after the call connection is completed.
- Originating side aGW2a is a user information storage unit 51 that acquires and stores terminal information and subscriber information of each mobile terminal, processing that receives and analyzes SIP signaling messages MAL, and bearer setting processing that uses the storage information BST, relay processing of SIP signaling message between mobile terminal and base station MRL, processing to create and send SIP signaling message on behalf of mobile terminal 52 processing unit to perform SAP, transmission / reception unit to transmit / receive messages to / from mobile terminal 53 includes a transmission / reception unit 54 for transmitting / receiving messages to / from the backbone network side.
- the receiving side aGW12a has the same configuration! /
- IMS terminals equipped with SIP improved for Evolved 3GPP there are IMS terminals equipped with SIP improved for Evolved 3GPP as IMS terminals, and IMS terminals not equipped with the improved SIP, and the sequence processing is different depending on each.
- Figure 3 shows the processing flow for deciding which sequence processing to execute depending on whether the SIP is installed in the IMS terminal.
- GW2a goes through the authentication process at the beginning of the call connection (step 101), and the mobile terminal
- step 102 It is determined whether the IMS terminal is equipped with a SIP improved for 3GPP (step 102). If “YES”, the first sequence processing (for example, the sequence processing in FIG. 5) is executed (step 103). If it is not an IMS terminal equipped with SIP improved for lved 3GPP, the second sequence processing (for example, the sequence processing of FIG. 9) is executed (step 104).
- Figure 4 is an explanatory diagram of the procedure for registering IMS terminal 4a equipped with SIP modified for Evolved 3GPP in IMS5 after purchase.
- the RRC Radio Resource
- the mobile terminal 4a and the aGW 2a are connected by Attach.
- the unique number (terminal ID) of the mobile terminal 4a and the capability information (media information, codec information) of the terminal GW2a Will be notified.
- Media information is media information that can be handled by a mobile terminal. For example, it indicates whether the mobile terminal can handle only audio information or both audio information and video information.
- the codec information indicates a method for encoding audio and video information.
- the HSS 6 authenticates the mobile terminal 4a via IASA 3, aGW2a, and the aGW 2a registers in the HSS 6 that the mobile terminal 4a is its own terminal.
- the aGW 2a stores subscriber information (for example, subscriber service information) acquired from the HSS 6 in association with the mobile terminal. This makes it possible for the aGW 2a to recognize the QoS that should be set for the originating mobile terminal during call connection.
- the mobile terminal 4a requests registration from the CSCF 8 of IMS5 to receive the IMS service (Register). Since CSCF8 is not registered in mobile terminal 4a, 401
- the mobile terminal 4a attaches authentication data and requests registration again (Register).
- the CSCF refers to the authentication data and registers the mobile terminal 4a if it is valid, and transmits a 200OK message indicating that it has been registered to the mobile terminal 4a.
- the mobile terminal 4a can receive the IMS service.
- FIG. 5 is an explanatory diagram of a call connection sequence when an IMS mobile terminal 4a equipped with SIP improved for Evolved 3GPP makes a call.
- INVITE tel +1 -212-555-2222 SIP / 2.0
- “Require: precondition” is an instruction to follow the QoS precondition in the INVITE message when setting the bearer. Also,
- the normal IMS mobile terminal generates the INVITE message shown in Table 1.
- the INVITE message generated by the mobile terminal 4a equipped with SIP improved for Evolved 3GPP does not include the message indicated by the underline in Table 1. If the precondition is not included in the INVITE message! /, And! /, This means that the mobile terminal 4a does not specify the QoS precondition, and “Supported: 100rel” is specified in the INVITE message. Not included! /, And! /, Means that the mobile terminal 4a does not require an acknowledgment, and not including PRACK or UPDATE means that the mobile terminal 4a does not use PRACK or UPDATE. Means that.
- aGW2a does not refer to the preconditions in the INVITE message for subsequent bearer settings, and performs bearer settings based on pre-registered terminal information and subscriber information.
- the aGW 2a does not send an acknowledgment to the mobile terminal 4a, and issues PRACK and UPDATE on behalf of the mobile terminal 4a.
- the aGW 2a sends the received INVITE message to the CSCF 8, and the CSCF 8 returns a 100 Trying message indicating that the INVITE message has been accepted to the mobile terminal 4a via the aGW 2a.
- CSCF 8 sends an INVITE message to the receiving mobile terminal 14a, but if the receiving mobile terminal and the aGW are not connected, the aGW 12a performs paging. If the paging mobile terminal 14a responds by this paging, RRC connection and authentication / confidential processing are performed in the same way as the calling side. When the authentication is completed, the aGW 12a sends an INVITE message to the mobile terminal 14a.
- the mobile terminal 14a When the mobile terminal 14a receives the INVITE message, it returns a 100 Trying message indicating acceptance and sends a 183 Session Progress message indicating the progress of the session to the CSCFs 8 and 18. Originating side aGW12a interprets / relays 183 Session Progress message.
- the 183 Session Progress message has the contents shown in Table 2. [Table 2]
- the first QoS precondition means that neither you nor the other party's QoS is set for video, but you want two-way communication.
- the second QoS precondition means that both voice and voice are currently set for QoS, but two-way communication is desired.
- the aGW 12a does not refer to the preconditions of the 183 Session Progress message for the subsequent bearer setting, and sets the bearer based on the pre-registered terminal information and subscriber information. Also, the aGW 12a does not send an acknowledgment to the mobile terminal 14a, and issues a PRACK, UPDATE on behalf of the mobile terminal 14a.
- the aGW 12a sends the received 183 Session Progress message to the CSCFs 8 and 18, and the CSCF 8 and 18 notify the originating mobile terminal 4a of the 183 Session Progress message via the originating side aGW 2a.
- the aGW 2a sends a PRACK as a confirmation response on behalf of the mobile terminal 4a to the receiving side aGW 12a via the CSCFs 8 and 18. If the receiving side aGWl 2a receives PRACK, the receiving side mobile terminal 14a will act on behalf of the receiving side mobile terminal 14a and 200OK will be sent via CSCF8, 18 to the calling side aGW2 Notify a. In this case, the originating side aGW 2a does not transmit the confirmation response 200OK to the terminating side mobile terminal 14a.
- the AF of CSCF8, 18 determines the information necessary for the bearer settings of terminals 4a, 14a based on the pre-registered terminal information and subscriber information, and passes them to PCRF / PCEF 7, 17 PCRF / PCEFs 7 and 17 perform bearer settings between the originating side aGW 2a and the terminating side aGW 12a, and the originating side aGW 2a and the terminating side aGW 12a perform bearer settings between the mobile terminals 4a and 14a.
- the originating side aGW 2a sends UPDATE to the terminating side & 0 ⁇ ⁇ 12 & via CSCF 8,18 on behalf of the originating side mobile terminal 4a.
- the receiving side aGW 12a receives the UPDATE, it does not send the UPDATE to the receiving side mobile terminal 14a.
- the receiving side aGW 12a sends a 200OK message to the calling side & ⁇ ⁇ ⁇ 2 & via CSCF 8,18 on behalf of the mobile terminal 14a.
- Calling side aGW2a does not send it to mobile terminal 4a even if it receives 200OK message.
- the called mobile terminal 14a When the bearer setting is completed, the called mobile terminal 14a sends a ringing message to the calling mobile terminal 4a via the called aGW 12a, CSCF 8, 18, and the called aGW 2a after the ringing tone is generated. If the originating side aGW2a sends a Ringing message to the originating mobile terminal 4a, it transmits PRACK on behalf of the mobile terminal 4a to the terminating mobile terminal 14a via CSCF8, 18, and the terminating mobile terminal 14a receives the PRACK. Even if it is not sent to the called mobile terminal 14a, 200OK is immediately sent on behalf of the mobile terminal 14a.
- the callee mobile terminal 14a sends 2 OOOK (INVITE) to the callee mobile terminal 4a via the callee aGW12a, CSCF8, 18, caller aGW2a, and the callee mobile terminal 4a receives 200OK (INVITE) ACK is returned to the called mobile terminal 14a.
- 2 OOOK IVSITE
- the callee mobile terminal 4a receives 200OK (INVITE) ACK is returned to the called mobile terminal 14a.
- communication is possible between the mobile terminals 4a and 14a.
- the number of messages at the time of call connection in the transmission side radio section is halved from 12 to 6, and the number of messages at the time of call connection in the reception side radio section is also reduced from 12. Halves to 6. In this way, the number of signaling in the radio section can be reduced. Therefore, more calls can be connected at the same time while enabling high-speed communication.
- FIG. 6 is an explanatory diagram of a modification of the call connection sequence of the first embodiment.
- the originating side aGW 2a when the originating side aGW 2a receives the 183 Session Progress message, it immediately transmits the message to the originating mobile terminal 4a.
- the modified example of FIG. Send the Progress message to the originating mobile terminal 4a.
- the media and QoS desired by the calling mobile terminal 4a may not be normally selected.
- the receiving side aGW12a or CSCF8, 18 may not give 200OK but give NG, and an error may occur. Therefore, the receiving side aGW 2a sends a 183 Session Progress message to the calling side mobile terminal 4a after receiving 200OK, and notifies the calling side mobile terminal 4a of an error when receiving NG. In this way, the 183 Session Progress response can be sent to the terminal after confirming that media, QoS, etc. have been successfully selected.
- the error message can be received before receiving 183 Session Progress as seen from the originating mobile terminal 4a, and a normal error occurs.
- the order of messages received by the mobile terminal can be matched.
- Fig. 7 shows another call connection sequence when an IMS mobile terminal 4a equipped with SIP improved for Evolved 3GPP makes a call.
- the call connection time can be shortened.
- the receiving side aGW12a issues a 183 Session Progress message while performing connection control (RRC connection, authentication processing, etc.) between the receiving side aGW12a and the receiving side mobile terminal 14a.
- connection control RRC connection, authentication processing, etc.
- the calling side performs the call connection sequence processing 500 up to 200 OK (INVITE) indicating the connection completion / communication start related to the receiving side mobile terminal 14a,
- the called mobile terminal 14a If the user of the called mobile terminal 14a picks up the receiver, for example (Off Hook), after the ringing is transmitted to the called mobile terminal 14a (Off Hook), the called mobile terminal 14a passes through the called aGW 12a, CSCF 8, 18, and the calling aGW 2a. 200OK0NVITE) is sent to the originating mobile terminal 4a, and the originating mobile terminal 4a returns ACK to the terminating mobile terminal 14a upon receiving 200OK (INVITE). As described above, communication is possible between the mobile terminals 4a and 14a.
- the call connection processing is performed in a short time because the call connection sequence processing up to 200 OK (INVITE) is performed before the connection control between the receiving side aGW 12a and the receiving side mobile terminal 14a is completed. It becomes possible.
- FIG. 8 is an explanatory diagram of a modification of the call connection sequence of the second embodiment.
- the originating side aGW 2a when the originating side aGW 2a receives the 183 Session Progress message, it immediately transmits the message to the originating mobile terminal 4a. Send the Progress message to the originating mobile terminal 4a.
- the media and QoS desired by the calling mobile terminal 4a may not be normally selected.
- the receiving side aGW12a or CSCF8, 18 may not give 200OK but give NG, and an error may occur. Therefore, the receiving side aGW 2a sends a 183 Session Progress message to the calling side mobile terminal 4a after receiving 200OK, and notifies the calling side mobile terminal 4a of an error when receiving NG. In this way, the 183 Session Progress response can be sent to the terminal after confirming that media, QoS, etc. have been successfully selected.
- the error message can be received before receiving 183 Session Progress as seen from the originating mobile terminal 4a, and a normal error occurs.
- the order of messages received by the mobile terminal can be matched.
- the improved SIP for Evolved 3GPP is not installed!
- the registration procedure for a normal IMS terminal 4a is the same as the conventional example in FIG. (b) Normal IMS terminal call connection sequence of the first embodiment
- FIG. 9 is an explanatory diagram of a call connection sequence at the time of calling a normal IMS mobile terminal 4a not equipped with SIP improved for Evolved 3GPP.
- the mobile terminal and eNBlla are connected by RRC (Radio Resource Control), and after that, the mobile terminal and aGW are connected by Attach, and the mobile terminal's unique number (Terminal ID) is notified to aGW.
- RRC Radio Resource Control
- HSS 6 authenticates the mobile terminal 4a via I ASA 3, aGW2a.
- the mobile terminal 4a sends an INVITE message to the CSCFs 8 and 18.
- the INVITE message transmitted by a normal IMS mobile terminal 4a has the contents shown in Table 1.
- the originating side aGW2a interprets / relays the INVITE message and sends it to CSCF 8 and 18, and CSCF 8 and 18 return a 100 Trying message indicating that the INVITE has been accepted to the mobile terminal 4a via aGW2a.
- CSCF 8 and 18 send an INVITE message to the mobile terminal 14a on the receiving side, but if the mobile terminal on the receiving side and the aGW are not connected, the aGW 12a makes a paging.
- the callee aGW 12a sends the INVITE to the callee mobile terminal 14a. send.
- the mobile terminal 14a receives the INVITE message, it returns a 100 Trying message indicating that it has been accepted, and sends a 183 Session Progress indicating the progress of the session to the CSCFs 8 and 18.
- 183 Session Progress has the contents shown in Table 2.
- the receiving side aGW 12a relays / interprets the 183 Session Progress message and sends it to the CSCF 8, 18 and the CSCF 8, 18 sends the 183 Session Progress message to the originating mobile terminal 4a.
- the receiving side aGW2a receives the 183 Session Progress message, it deletes the item related to the reliability response in the 183 Session Progress message and notifies the calling side mobile terminal 4a.
- the item related to the reliability response is “Require: lOOrel” but 'PRACK ”, so that the mobile terminal 4a on the sending side does not send PRACK even if it receives the 183 Session Progress message.
- PRA CK which is an acknowledgment of the 183 Session Progress message
- PRA CK which is an acknowledgment of the 183 Session Progress message
- the mobile terminal 14a sends a 200OK message to the calling side aGW 2a via CSCF 8 and 18. Even if the sending side aGW2a receives the 200OK message, it does not send it to the calling party terminal 4a.
- the AF of CSCF 8, 18 refers to the QoS information in the INVITE message or 183 Session Progress message and the contract information of each mobile terminal, and sets the information necessary for bearer configuration to PCRF / PCEF7, 17, PCRF / PCEF 7 and 17 perform bearer settings between the originating side aGW 2 a and the terminating side aGW 12 a, and each aGW 2 a and 12 a perform bearer settings with the mobile terminals 4 a and 14 a.
- the caller side aGW2a, CSCF
- Sending side UPDATE is sent to receiving side mobile terminal 14a via aGW 12a.
- the receiving-side mobile terminal 14a also completes the update based on the bearer settings, and then sends a 200OK message to the calling-side mobile terminal 4a via the receiving-side a GW12a, CSCF 8, 18, and the calling-side aGW2a.
- Send ringing message (Ringing) is sent to receiving side mobile terminal 14a via aGW 12a.
- the originating side aGW 2a When the originating side aGW 2a receives the Ringing message, it deletes the item related to the reliability response in the Ringing message and notifies the originating side mobile terminal 4a. As a result, the originating mobile terminal 4a does not send a PRACK even if it receives a Ringing message.
- the originating side aGW2a sends a Ringing message to the originating mobile terminal 4a, and then sends PRACK as an acknowledgment on behalf of the originating mobile terminal 4a to the terminating mobile terminal 14a via CSCF8, 18 and the terminating side aGW12a.
- the called mobile terminal 14a sends a 200OK message to the calling mobile terminal 4a via CSCF 8 and 18.
- Calling side aGW2a does not send 200OK message to calling side mobile terminal 4a.
- the called mobile terminal 14a sends 200OK (INVITE) to the calling mobile terminal 4a via CSCF 8.
- the originating mobile terminal 4a If the originating mobile terminal 4a returns ACK to the terminating mobile terminal 14a upon receipt of 200OK0NVITE), communication between the mobile terminals 4a and 14a becomes possible.
- the number of messages at the time of call connection in the radio section on the transmission side Is reduced from 12 to 8. In this way, since the number of signaling in the radio section can be reduced, even with a normal IMS terminal, high-speed communication is possible, and at the same time, more call connections are possible.
- FIG. 10 is an explanatory diagram of a modification of the call connection sequence of the first embodiment.
- the calling side aGW 2a receives the 183 Session Progress message, it immediately sends the message to the calling side mobile terminal 4a.
- the modified example of FIG. Send a Session Progress message to the originating mobile terminal 4a.
- the media and QoS desired by the calling mobile terminal 4a may not be normally selected.
- the receiving side aGW12a or CSCF8, 18 may not give 200OK but give NG, and an error may occur. Therefore, the receiving side aGW 2a sends a 183 Session Progress message to the calling side mobile terminal 4a after receiving 200OK, and notifies the calling side mobile terminal 4a of an error when receiving NG. In this way, the 183 Session Progress response can be sent to the terminal after confirming that media, QoS, etc. have been successfully selected.
- the error message can be received before receiving 183 Session Progress as seen from the originating mobile terminal 4a, and a normal error occurs.
- the order of messages received by the mobile terminal can be matched.
- FIG. 11 shows another call connection sequence at the time of calling the normal IMS mobile terminal 4a, and the call connection time can be shortened.
- the receiving side aGW12a issues the 183 Session Progress message on behalf of the mobile terminal 14a. To do,
- the terminating mobile terminal 14a After the terminating mobile terminal 14a transmits Ringing, if the user of the terminating mobile terminal 14a picks up the receiver (Off Hook), for example, the terminating mobile terminal 14a passes through the terminating aGW12a, CSCF8, 18, and the originating aGW2a. 200OK0NVITE) is sent to the originating mobile terminal 4a, and the originating mobile terminal 4a returns ACK to the terminating mobile terminal 14a upon receiving 200OK (INVITE). As described above, communication is possible between the mobile terminals 4a and 14a.
- the call connection processing is performed in a short time because the call connection sequence processing up to 200 OK (INVITE) is performed before the connection control between the receiving side aGW 12a and the receiving side mobile terminal 14a is completed. It becomes possible.
- FIG. 12 is an explanatory diagram of a modification of the call connection sequence of the second embodiment.
- the originating side aGW 2a receives the 183 Session Progress message, it immediately sends the message to the originating mobile terminal 4a.
- CS CF8,18 is 200OK when it works
- the calling side aGW2a receives 200OK.
- a 183 Session Progress message is transmitted to the originating mobile terminal 4a, and if an NG is received, an error is notified to the originating mobile terminal 4a. Since the calling-side mobile terminal 4a has not received the 183 Session Progress message, it can immediately terminate the call connection by an error notification.
- Figures 13 to 16 show the busy state when the terminating mobile terminal is out of service area in the call connection sequence of the IMS terminal equipped with SIP improved for Evolved 3GPP (second embodiment in Figure 7). It is a processing sequence in a case.
- Figure 13 shows the processing sequence when the mobile terminal 14a at the receiving end times out with no response after sending a 183 Session Progress message to the calling mobile terminal 4a, and the receiving side aGW12a generates an error due to 406Reque st Timeout. It is.
- Figure 14 shows the process when the receiving mobile terminal 14a is out of service area and no time-out occurs before the 183 Session Progress message is sent to the calling mobile terminal 4a and the receiving side aGW12a generates a 406Reque st Timeout and results in an error. It is a sequence.
- FIG. 15 shows a processing sequence in the case where, after the 183 Session Progress message is transmitted to the calling-side mobile terminal 4a, the called-side mobile terminal 14a is in a busy state, so that the called-side aGW 12a generates 486 Busy Here and an error occurs.
- FIG. 16 shows the processing sequence when the terminating mobile terminal 14a generates a 486 Busy Here error because the terminating mobile terminal 14a is busy before sending the 183 Session Progress message to the originating mobile terminal 4a.
- Fig. 17 shows the processing sequence when an error message XXX (error) occurs and an error occurs before the normal response 200OK0NVITE) to INVITE is generated.
- the calling side mobile terminal 4a receives 200OK0NVITE), so it becomes an error when calling normally.
- the present invention it is possible to reduce the number of signaling in a radio section while enjoying various services, and at the same time, more links can communicate. Also, by reducing the number of SIP messages that flow from end to end, call connection time can be shortened, and radio resources can be effectively used without occupying the frequency band.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
Claims
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2006800559902A CN101536601B (zh) | 2006-10-05 | 2006-10-05 | 呼叫连接处理方法和消息收发代理装置 |
JP2008538506A JP4454680B2 (ja) | 2006-10-05 | 2006-10-05 | 呼接続処理方法およびメッセージ送受信代理装置 |
PCT/JP2006/319958 WO2008044265A1 (en) | 2006-10-05 | 2006-10-05 | Call connection processing method and message transmitting and receiving proxy device |
KR20097003069A KR101051820B1 (ko) | 2006-10-05 | 2006-10-05 | 호 접속 처리 방법 및 메시지 송수신 대리 장치 |
EP06811296A EP2063617A4 (en) | 2006-10-05 | 2006-10-05 | CALL CONNECTION PROCESSING AND MESSAGE TRANSMISSION AND RECEPTION PROXY DEVICE |
US12/416,574 US20090193128A1 (en) | 2006-10-05 | 2009-04-01 | Call Connection Processing Method And Message Transmission/Reception Proxy Apparatus |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2006/319958 WO2008044265A1 (en) | 2006-10-05 | 2006-10-05 | Call connection processing method and message transmitting and receiving proxy device |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/416,574 Continuation US20090193128A1 (en) | 2006-10-05 | 2009-04-01 | Call Connection Processing Method And Message Transmission/Reception Proxy Apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2008044265A1 true WO2008044265A1 (en) | 2008-04-17 |
Family
ID=39282477
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2006/319958 WO2008044265A1 (en) | 2006-10-05 | 2006-10-05 | Call connection processing method and message transmitting and receiving proxy device |
Country Status (6)
Country | Link |
---|---|
US (1) | US20090193128A1 (ja) |
EP (1) | EP2063617A4 (ja) |
JP (1) | JP4454680B2 (ja) |
KR (1) | KR101051820B1 (ja) |
CN (1) | CN101536601B (ja) |
WO (1) | WO2008044265A1 (ja) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2010206248A (ja) * | 2009-02-27 | 2010-09-16 | Ntt Docomo Inc | 位置登録システム、位置登録装置、及び位置登録方法 |
WO2018214873A1 (zh) * | 2017-05-22 | 2018-11-29 | 中兴通讯股份有限公司 | 语音信令传输方法和装置 |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100054177A1 (en) * | 2008-09-02 | 2010-03-04 | Serdar Sahin | Method and system of using ip multimedia system for call setup in mobile satellite systems |
US8903244B2 (en) * | 2008-12-19 | 2014-12-02 | At&T Intellectual Property I., L.P. | Modular network terminals and methods to use the same |
CN102625382B (zh) * | 2011-01-31 | 2017-08-11 | 中兴通讯股份有限公司 | 跨无线网络控制器的切换方法及系统 |
US8719926B2 (en) * | 2011-02-11 | 2014-05-06 | Verizon Patent And Licensing Inc. | Denial of service detection and prevention using dialog level filtering |
US9185152B2 (en) * | 2011-08-25 | 2015-11-10 | Ustream, Inc. | Bidirectional communication on live multimedia broadcasts |
KR102072713B1 (ko) | 2013-09-02 | 2020-02-03 | 에스케이텔레콤 주식회사 | 호 처리 통합형 통화 연속성 제공 방법 및 장치 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH03198497A (ja) * | 1989-12-26 | 1991-08-29 | Nec Corp | 自動車電話加入者呼び出し方式 |
JP2005064646A (ja) | 2003-08-08 | 2005-03-10 | Mitsubishi Electric Corp | 移動体ネットワークにおけるシグナリング転送方法および移動体ネットワーク |
JP2006506012A (ja) | 2002-11-12 | 2006-02-16 | ノキア コーポレイション | 通信方法及び通信システム |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6910074B1 (en) * | 2000-07-24 | 2005-06-21 | Nortel Networks Limited | System and method for service session management in an IP centric distributed network |
US7609673B2 (en) * | 2002-02-08 | 2009-10-27 | Telefonaktiebolaget Lm Ericsson (Publ) | Packet-based conversational service for a multimedia session in a mobile communications system |
US7240366B2 (en) * | 2002-05-17 | 2007-07-03 | Microsoft Corporation | End-to-end authentication of session initiation protocol messages using certificates |
US20030236892A1 (en) * | 2002-05-31 | 2003-12-25 | Stephane Coulombe | System for adaptation of SIP messages based on recipient's terminal capabilities and preferences |
US6798755B2 (en) * | 2002-12-31 | 2004-09-28 | Motorola, Inc. | Apparatus and method for controlling and managing individual directed sessions in a communications system |
KR100514196B1 (ko) * | 2003-02-14 | 2005-09-13 | 삼성전자주식회사 | 네트웍 어드레스 변환 및 세션 관리 시스템 및 그 방법 |
GB0311006D0 (en) * | 2003-05-13 | 2003-06-18 | Nokia Corp | Registrations in a communication system |
CN1243432C (zh) * | 2003-06-26 | 2006-02-22 | 中国科学院计算技术研究所 | 一种ip视频电话系统会话和媒体授权方法 |
US7162236B2 (en) * | 2004-04-26 | 2007-01-09 | Motorola, Inc. | Fast call set-up for multi-mode communication |
EP1806008B1 (en) * | 2004-10-06 | 2018-06-20 | Telecom Italia S.p.A. | Method, and related mobile communications system, for providing combinational network services |
US20080022000A1 (en) * | 2004-11-11 | 2008-01-24 | Shinji Furuya | Ip-Packet Relay Method and Gateway in Communication Network |
US8473617B2 (en) * | 2004-12-31 | 2013-06-25 | Sony Corporation | Media client architecture for networked communication devices |
US20070049329A1 (en) * | 2005-08-26 | 2007-03-01 | Net2Phone, Inc. | IP-enhanced cellular services |
-
2006
- 2006-10-05 CN CN2006800559902A patent/CN101536601B/zh not_active Expired - Fee Related
- 2006-10-05 KR KR20097003069A patent/KR101051820B1/ko not_active IP Right Cessation
- 2006-10-05 WO PCT/JP2006/319958 patent/WO2008044265A1/ja active Application Filing
- 2006-10-05 JP JP2008538506A patent/JP4454680B2/ja not_active Expired - Fee Related
- 2006-10-05 EP EP06811296A patent/EP2063617A4/en not_active Withdrawn
-
2009
- 2009-04-01 US US12/416,574 patent/US20090193128A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH03198497A (ja) * | 1989-12-26 | 1991-08-29 | Nec Corp | 自動車電話加入者呼び出し方式 |
JP2006506012A (ja) | 2002-11-12 | 2006-02-16 | ノキア コーポレイション | 通信方法及び通信システム |
JP2005064646A (ja) | 2003-08-08 | 2005-03-10 | Mitsubishi Electric Corp | 移動体ネットワークにおけるシグナリング転送方法および移動体ネットワーク |
Non-Patent Citations (2)
Title |
---|
"the 3rd generation partnership project, 3GPP TS 24.228 v5.14.0", HEISEI 18 NEN 11 GATSU 24 NICHI UHEISEI 16 NEN 12 GATSU 7 NICHI KENSAKU], December 2005 (2005-12-01), XP008105002, Retrieved from the Internet <URL:http://www.3gpp.org.ftp/Specs/archive/24_series/24.228/24228-5e0.zip> * |
See also references of EP2063617A4 |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2010206248A (ja) * | 2009-02-27 | 2010-09-16 | Ntt Docomo Inc | 位置登録システム、位置登録装置、及び位置登録方法 |
WO2018214873A1 (zh) * | 2017-05-22 | 2018-11-29 | 中兴通讯股份有限公司 | 语音信令传输方法和装置 |
US11582353B2 (en) | 2017-05-22 | 2023-02-14 | Zte Corporation | Voice signaling transmission method and device |
Also Published As
Publication number | Publication date |
---|---|
US20090193128A1 (en) | 2009-07-30 |
KR101051820B1 (ko) | 2011-07-25 |
EP2063617A4 (en) | 2012-11-21 |
JPWO2008044265A1 (ja) | 2010-02-04 |
JP4454680B2 (ja) | 2010-04-21 |
CN101536601B (zh) | 2012-05-30 |
CN101536601A (zh) | 2009-09-16 |
EP2063617A1 (en) | 2009-05-27 |
KR20090035705A (ko) | 2009-04-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1920572B1 (en) | Multimedia subsystem service control for circuit-switched subsystem calls | |
US8717876B2 (en) | Providing packet-based multimedia services via a circuit bearer | |
KR100909542B1 (ko) | Csi 단말과 ims 단말 사이의 음성 및 멀티미디어 서비스 연동을 위한 방법 및 장치 | |
JP5148509B2 (ja) | Csi端末によるimsドメインを介して受信されたリアルタイムサービスのための要求を含むims端末の呼要求の処理方法及び装置 | |
KR100775349B1 (ko) | 서비스 도메인 선택 방법 및 장치 | |
US20040249887A1 (en) | Conversational bearer negotiation | |
KR101133199B1 (ko) | 패킷 교환 도메인의 상태를 변경하기 위한 방법, 단말기 및 네트워크 장치 | |
WO2008044265A1 (en) | Call connection processing method and message transmitting and receiving proxy device | |
US20100284267A1 (en) | Call set-up in a communication network | |
US20120213346A1 (en) | Method, server and terminal device for playing multimedia ring tone during call | |
KR100747468B1 (ko) | 콤비네이션 서비스를 위한 단말 능력정보 갱신 통지 방법및 시스템 | |
JP2007325191A (ja) | 移動体通信システム及びセッション継続方法 | |
US20120120877A1 (en) | Expedited call setup | |
EP1998517B1 (en) | METHOD AND aPPARATUS FOR CHANGING STATUS OF PACKET SWITCHED DOMAIN | |
Tanaka et al. | Overview of GSMA VoLTE Profile | |
JP6549523B2 (ja) | 要求先端末のオプション機能の非使用を整合する網間制御方法、sipサーバ及びプログラム | |
JP5118417B2 (ja) | 通信システム及び通信方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200680055990.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: 06811296 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008538506 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020097003069 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2006811296 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |