Patent Grant
12034776
The present invention relates to a call control technique using the SIP/SDP. Particularly, the present invention relates to SIP application software mounted in a Session Border Controller (SBC) that controls a boundary with a different network or terminal.
In audio and video communication using the Session Initiation Protocol (SIP), the Session Description Protocol (SDP) in which media information on this communication is described is exchanged between an outgoing terminal and an incoming terminal or between SIP servers in a network, media conditions of the audio and video (media type, codec, packetization period, and the like) are then settled by negotiation, and thereafter actual transmission and reception of audio packets with the Real-time Transport Protocol (RTP) are performed.
Particularly, negotiation on the media information (SDP negotiation) is performed such that the outgoing-side terminal describes the media (such as audio and video) desired to be used for communication and various parameters of the media (codec, packetization period, and the like) into SDP offer, and then the incoming-side terminal chooses media conditions to be used for the communication from the media conditions described in the SDP offer, describes the chosen media conditions into SDP answer, and sends back the SDP answer to the outgoing-side terminal. In this way, the conditions of the communication media to be used between the outgoing and incoming terminals are settled.
Meanwhile, in 3GPP, the IP Multimedia Subsystem (IMS) is defined as a system in which telecommunications carriers provide multimedia services including a telephone service. The IMS is a multimedia service system supporting any of access types (3G, LTE, WiFi, optical access, and so on) used by outgoing and incoming terminals such as mobile and fixed terminals. However, an IMS network including only the mobile terminal and an IMS network including only the fixed terminal may have a case where no common codec is supported by terminals in these different IMS networks.
For example, in general, the fixed terminal supports at least a G.711μ-law audio codec while the mobile terminal supports at least an AMR-NB audio codec. Thus, an IMS network of a telecommunications carrier requires a function of codec conversion to achieve intercommunication between the fixed terminal and the mobile terminal.
Note that, there is a function, generally called a transcoding function, in which an intermediate node in an IMS network executes not only the codec conversion but also rewrite processing of the SDP (such as adding or deleting of a codec) and conversion processing of media (RTP and the like) according to conditions before the SDP rewriting and after the SDP rewriting. Transcoding is usually executed using information on the codecs supported by the outgoing and incoming terminals, based on an operator policy defined by the carriers with an agreement between the carriers, the Service Level Agreement (SLA), and so on.
Specifically, when receiving SDP offer, the SBC (IBCF) adds a codec that can be transcoded by the own IMS network or a terminal in the own IMS network (in this example, codec b) to a codec list set in the SDP offer. Then, when a codec in SDP answer received thereafter includes a codec in the previously received SDP offer (in this example, codec a), the SBC transmits the SDP answer as it is without executing the transcoding function (
On the other hand, when the codec in the received SDP answer does not include a codec in the previously received SDP offer (codec a), the SBC (IBCF) chooses one codec from the codecs included in the previously received SDP offer (in this example, there is only codec a) and transmits SDP answer in which that codec information is described (
For example, when a single IMS network includes the mobile terminal and the fixed terminal, communication between the mobile terminal and the fixed terminal within the own IMS network is enabled by providing the transcoding function to a node such as an intermediate node (such as SIP server and media server) or the node nearest to the terminal (such as Proxy Call State Control Function (P-CSCF) and Media Gateway (MGW)).
In another case, when interconnecting the IMS network including only the mobile terminal and the IMS network including only the fixed terminal, communication between the mobile terminal and the fixed terminal in the different IMS networks is enabled by the IMS network of SDP offer transmitting side or the IMS network of SDP answer transmitting side executing transcoding. Processing procedures of the transcoding executed in the IMS network of SDP offer transmitting side and the IMS network of SDP answer transmitting side are respectively illustrated in
In addition,
As illustrated in
However, in an actual service, multiple times of SDP offer/answer are performed for communication involving media changing such as switching from a guidance or a video call to an audio call. Thus, there is a problem that a transcoding execution point cannot be fixed in an outgoing side network or an incoming side network like a case where, when the SDP offer is transmitted from the IMS network of incoming side, transcoding is executed in the IMS network of incoming side after the second SDP offer/answer even though transcoding is executed in the IMS network of outgoing side after the initial SDP offer/answer, as illustrated in
As a specific example,
Here, transcoding consumes much more resources than resources required by the processing of transparently forwarding the media packets. For this reason, when functions of a call control system are desired to be designed based on the number of outgoing and incoming calls, it is desirable to fix transcoding during one call to the outgoing side or the incoming side. In addition, since it is expected that the number of required functions varies depending on transcoding, carriers each also have a demand that, in interconnection between the carriers and another carrier, transcoding of outgoing calls from the own network be executed in the own network so as to reduce access charge from the destination network.
However, with the current processing procedure of transcoding, although transcoding can be executed on either of the SDP offer transmitting side and the SDP answer transmitting side, it is impossible to fix the transcoding execution point to the outgoing side or the incoming side through 1 call.
The present invention was made in light of the above-described circumstances and has an object to fix a transcoding execution network (outgoing side or incoming side).
In order to solve the above problems, a gist of a communication method according to one aspect of the invention is that, in a communication method executed between multiple communication devices, the method comprising causing a certain communication device out of the communication devices to perform: a first step of setting parameter information that requests any of the communication devices to execute transcoding into Session Description Protocol (SDP); and a second step of executing transcoding of media data by the certain communication device itself, when the parameter information set in the SDP requests the certain communication device itself.
A gist of a communication method according to one aspect of the invention is that, in the communication method, if the certain communication device requested by the parameter information is determined not to execute transcoding, the first step involves changing the parameter information to indicate an opposite one of the communication devices.
A gist of a communication method according to one aspect of the invention is that, in a communication method executed between multiple communication devices, the method comprising, when a certain communication device out of the communication devices is to execute transcoding of media data, causing the certain communication device to perform a first step of storing a codec type currently in use that is determined by Session Description Protocol (SDP) negotiation into a codec information storing unit, a second step of receiving a Session Initiation Protocol (SIP) message containing SDP offer, and a third step of transmitting the SIP message containing the SDP offer that includes a codec type currently in use in a forwarding destination.
A gist of a communication method according to one aspect of the invention is that, in the communication method, if the SDP offer in the received SIP message includes a codec type currently in use in a forwarding source, the third step involves including the codec type currently in use in the forwarding destination into the SDP offer in the SIP message to be transmitted.
A gist of a communication method according to one aspect of the invention is that, in the communication method, if the SDP offer in the received SIP message does not include a codec type currently in use in a forwarding source and if the certain communication device is capable of transcoding between the codec type included in the SDP offer and the codec type currently in use in the forwarding destination, the third step involves including the codec type currently in use in the forwarding destination into the SDP offer in the SIP message to be transmitted.
A gist of a communication method according to one aspect of the invention is that, in a communication method executed between multiple communication devices, the method comprising causing a certain communication device of the communication devices to: store a codec type currently in use that is determined by Session Description Protocol (SDP) negotiation into a codec information storing unit and if the certain communication device is determined not to execute transcoding of media data and receives a Session Initiation Protocol (SIP) message containing SDP offer that includes a codec type currently in use in a forwarding source, forward the SIP message without adding the codec type to the SDP offer.
A gist of a communication device according to one aspect of the invention is that a communication device includes: a transcoding unit that executes transcoding of media data; a codec information storing unit that stores a codec type currently in use that is determined by Session Description Protocol (SDP) negotiation; and an SDP processing unit that, if a Session Initiation Protocol (SIP) message containing SDP offer is received, includes a codec type currently in use in a forwarding destination into the SDP offer when forwarding the SIP message.
A gist of a communication device according to one aspect of the invention is that a communication device includes: a codec information storing unit that stores a codec type currently in use that is determined by Session Description Protocol (SDP) negotiation; and an SDP processing unit that, if the communication device is determined not to execute transcoding of media data and receives a Session Initiation Protocol (SIP) message containing an SDP offer that includes a codec type currently in use in a forwarding source, forwards the SIP message without adding the codec type to the SDP offer.
A gist of a communication system according to one aspect of the invention is that a communication system includes: a first communication device; and a second communication device, in which the first communication device includes a codec information storing unit that stores a codec type currently in use that is determined by Session Description Protocol (SDP) negotiation and an SDP processing unit that, if the first communication device is determined not to execute transcoding of media data and receives a Session Initiation Protocol (SIP) message containing an SDP offer that includes a codec type currently in use in a forwarding source, forwards the SIP message to the second communication device without adding the codec type into the SDP offer, and the second communication device includes a transcoding unit that executes transcoding of media data, a codec information storing unit that stores a codec type currently in use that is determined by the SDP negotiation, and an SDP processing unit that, if the SIP message is received, includes a codec type currently in use in a forwarding destination into the SDP offer when forwarding the SIP message.
A gist of a communication program according to one aspect of the invention is to cause a computer to execute the communication method described above.
According to the present invention, it is possible to fix a network (outgoing side, incoming side) determined to execute transcoding.
Hereinafter, two embodiments are described for a method of fixing a network (IMS network, SBC) determined to execute transcoding on an initial SDP offer transmitting side or an initial SDP answer transmitting side.
In First Embodiment, an IMS network that is to execute transcoding is selected by negotiation between an IMS network of SDP offer transmitting side and an IMS network of SDP answer transmitting side in first SDP negotiation (first SDP offer/answer).
Each of the SBC 1a and the SBC 1b includes an SDP processing unit 11, a transcoding unit 12, and a codec information storing unit 13.
The SDP processing unit 11 has not only a conventional function that is for example SDP rewrite processing (such as processing of adding and deleting a codec to and from the SDP) but also a function of selecting an IMS network that is to execute transcoding by negotiation. Specifically, the SDP processing unit 11 sets an information element (parameter information) that requests any of the IMS network to execute transcoding into the SDP and, at a timing when the SDP negotiation is performed, uses that information element to select an IMS network that executes transcoding with another IMS network (SBC).
For example, when the SBC 1a determines (requests) to execute transcoding in the own IMS network (SBC 1a) when transmitting the SDP offer to the other IMS network (SBC 1b), the SBC 1a sets an information element indicating that the transcoding is charged with the SDP offer transmitting side. For example, that information element is set as a transcoding execution point designation parameter “transcoder”, and “own-side” is set as a value of that information element. On the other hand, when the SBC 1a wants (requests) the other IMS network (SBC 1b) to be in charge of transcoding, the SBC 1a sets “opposite-side” as the value of the above-described information element. That information element and the value of that information element can be used in an arbitrary form such as a header field of the SIP and a value of that header field, “attribute” of the SDP, and the like.
If the other IMS network (SBC 1b) cannot execute transcoding even when the SBC 1a wants (requests) that other IMS network to be in charge of transcoding, that other IMS network may request the SBC 1a to be in charge of transcoding.
Thus, the SDP processing unit 11 further has a function of changing the above-described information element so as to indicate an IMS network other than the IMS network requested by that information element if the IMS network requested by that information element cannot execute transcoding.
The transcoding unit 12 has not only a conventional function of transcoding a media packet (media data) but also a function of executing or not executing transcoding depending on a result of the negotiation on a transcoding executor by the SDP processing unit 11. Specifically, when the IMS network determined to execute transcoding is the own IMS network, the transcoding unit 12 executes the transcoding, and when the IMS network determined to execute transcoding is the other IMS network, the transcoding unit 12 executes no transcoding.
The codec information storing unit 13 has not only a conventional function of storing codec information that can be transcoded by the own IMS network (own SBC) or a terminal in the own IMS network (e.g., when the G.711μ-law audio codec is supported by the own IMS network, G.711μ-law) and the operator policy defined with the agreement between the carriers or the SLA and so on, but also has a function of storing the above-described information element to be set or already set in the SDP while allowing that information element to be read or referred by the SDP processing unit 11 or the transcoding unit 12.
Note that, in the present invention, transcoding mainly indicates a function and processing of converting a codec (coding system) of audio and video communication media. For example, this is conversion of the G.711μ-law audio codec to the AMR audio codec and its inverse conversion. Note that G.711μ-law and AMR are an example of codecs, and the present invention is not limited to a specific type of codec.
So far, the functions of the SBC 1a and the SBC 1b are schematically described. However, detailed descriptions of the functions of the SBC 1a and the SBC 1b are needed for actually selecting the IMS network that is to execute transcoding by negotiation. Thus, specific operations performed by the SBC 1a (initial SDP offer transmitting side) and the SBC 1b (initial SDP answer transmitting side) are respectively exemplified in Table 1 and Table 2. The SDP processing unit 11 of the SBC 1a executes operation and processing according to the described details in Table 1 while the SDP processing unit 11 of the SBC 1b executes operation and processing according to the described details in Table 2.
Table 1
Table 1: Operation of Initial SDP Offer Transmitting Side
Next, a negotiation operation for selecting an executor (IMS network, SBC) of transcoding is described.
Firstly, a negotiation operation in a case where transcoding is to be executed in the IMS network of initial SDP offer transmitting side (SBC 1a) is described with reference to
First, after the SBC 1a receives the initial SDP offer from the own IMS network, if codec conversion is to be executed in the own IMS network (SBC 1a) based on the operator policy, the SBC 1a adds the codec that can be transcoded by the own IMS network or a terminal in the own IMS network (codec b) into the codec list set in the initial SDP offer, sets “own-side” into the initial SDP offer, and transmits the initial SDP offer to the other IMS network (SBC 1b) (step S101).
Next, once the SBC 1b receives the initial SDP offer from the SBC 1a, since “own-side” is set in the initial SDP offer, the SBC 1b transmits (transparently) the initial SDP offer to the own IMS network (step S102). At this time, the SBC 1b stores “own-side” into the codec information storing unit 13 and deletes “own-side” from the initial SDP offer.
Thereafter, a codec that the incoming-side terminal itself in the IMS network of the SBC 1b wants to use is selected. Specifically, when the media conditions in the initial SDP offer (codec a, b) includes a media condition that can be used by the incoming-call terminal itself for communication, the incoming-call terminal chooses that media condition (codec b), describes it into the initial SDP answer, and sends back the initial SDP answer.
Next, once the SBC 1b receives the initial SDP answer from the own IMS network, since “own-side” was set in the previously received SDP offer, the SBC 1b sets “opposite-side” into the initial SDP answer and transmits the initial SDP answer to the other IMS network (SBC 1a) (step S103).
Next, once the SBC 1a receives the initial SDP answer from the SBC 1b, since the initial SDP answer does not include the codec included in the previously received SDP offer (codec a) but the previously transmitted codec added by the SBC 1a itself (codec b), the SBC 1a chooses one codec from the codecs included in the previously received initial SDP offer (only codec a), sets that codec to the initial SDP answer, and transmits the initial SDP answer to the own IMS network (step S104).
With the processing so far, it is possible to select the IMS network of initial SDP offer transmitting side (SBC 1a) as the executor of transcoding based on “own-side” and “opposite-side” communicated between the SBC 1a and the SBC 1b in the first SDP negotiation. For example, the SBC 1b can figure out that the SBC 1b does not have to execute transcoding and the SBC 1a has to execute transcoding by referring to “own-side” set by the SBC 1a. Note that the SBC 1a may save “own-side” set by itself in step S101 and “opposite-side” set by the SBC 1b in step S104 and figure out that transcoding is executed by itself by referring to them.
Thereafter, when the media packet is transmitted from the other IMS network (SBC 1b), the SBC 1a executes transcoding of “codec b→a” and transmits the media packet to the own IMS network, and when the media packet is transmitted from the own IMS network, the SBC 1a executes transcoding of “codec a→b” and transmits the media packet to the other IMS network (step S105).
Then, a case where subsequent SDP offer is generated in the IMS network of initial SDP answer transmitting side is described.
Once the SBC 1b receives the subsequent SDP offer from the own IMS network, since the executor of transcoding is not the SBC 1b itself, the SBC 1b adds no codec into the codec list set in the subsequent SDP offer, sets “opposite-side” into the subsequent SDP offer, and transmits the subsequent SDP offer to the other IMS network (SBC 1a) (step S106).
Next, once the SBC 1a receives the subsequent SDP offer from the SBC 1b, since the executor of transcoding is the SBC 1a itself, the SBC 1a adds the codec that can be transcoded by the own IMS network or a terminal in the own IMS network (codec a) into the codec list set in the subsequent SDP offer, and transmits the subsequent SDP offer to the own IMS network (step S107).
Note that, if the SBC 1a is already executing transcoding by itself when receiving the subsequent SDP offer from the SBC 1b in step S107, the SBC 1a at least includes the codec currently in use in the own IMS network (codec a) as the codec to be added.
In addition, in step S107, independent of the result of selecting by the first SDP negotiation, the SBC 1a may newly select itself as the executor of transcoding based on “opposite-side” set in the subsequent SDP offer or the operator policy.
Next, once the SBC 1a receives subsequent SDP answer from the own IMS network, since the subsequent SDP answer does not include the codec included in the previously received SDP offer (codec b) but the previously transmitted codec added by the SBC 1a itself (codec a), the SBC 1a chooses one codec from the codecs included in the previously received SDP offer (only codec b), sets that codec to the subsequent SDP answer, and transmits the subsequent SDP answer to the other IMS network (SBC 1b) (step S108). At this time, since “opposite-side” was set in the previously received SDP offer, the SBC 1a sets “own-side” into the subsequent SDP offer.
Next, once the SBC 1b receives the subsequent SDP answer from the SBC 1a, since the subsequent SDP answer includes the codec included in the previously received SDP offer (codec b), the SBC 1b transmits (transparently) the subsequent SDP answer to the own IMS network (step S109).
Thereafter, when the media packet is transmitted from the other IMS network (SBC 1b), the SBC 1a executes the transcoding of “codec b→a” and transmits the media packet to the own IMS network, and when the media packet is transmitted from the own IMS network, the SBC 1a executes the transcoding of “codec a→b” and transmits the media packet to the other IMS network (step S110).
With the processing in steps S106 to S110, even when the subsequent SDP offer is generated in the IMS network of initial SDP answer transmitting side, it is possible to continue the transcoding in the IMS network of initial SDP offer transmitting side (SBC 1a).
Next, a negotiation operation in a case where transcoding is to be executed in the IMS network of initial SDP answer transmitting side (SBC 1b) is described with reference to
First, after the SBC 1a receives the initial SDP offer from the own IMS network, if no codec conversion is executed in the own IMS network (SBC 1a) based on the operator policy, the SBC 1a adds no codec into the codec list set in the initial SDP offer, sets “opposite-side” into the initial SDP offer, and transmits the initial SDP offer to the other IMS network (SBC 1b) (step S201).
Next, once the SBC 1b receives the initial SDP offer from the SBC 1a, if “opposite-side” is set in the initial SDP offer and the codec conversion is to be executed in the own IMS network (SBC 1b) based on the operator policy, the SBC 1b adds the codec that can be transcoded by the own IMS network or a terminal in the own IMS network (codec b) into the codec list set in the initial SDP offer, and transmits the initial SDP offer to the own IMS network (step S202).
Thereafter, the codec that the incoming-side terminal itself in the IMS network of the SBC 1b wants to use is selected. Specifically, when the media conditions in the initial SDP offer (codec a, b) includes a media condition that can be used by the incoming-call terminal itself for communication, the incoming-call terminal chooses that media condition (codec b), describes it into the initial SDP answer, and sends back the initial SDP answer.
Next, once the SBC 1b receives the initial SDP answer from the own IMS network, since “opposite-side” was set in the previously received SDP offer, the SBC 1b sets “own-side” into the initial SDP answer and transmits the initial SDP answer to the other IMS network (SBC 1a) (step S203).
Next, once the SBC 1a receives the initial SDP answer from the SBC 1b, since the initial SDP answer includes the codec included in the previously received SDP offer (codec a), the SBC 1a transmits (transparently) the initial SDP answer to the own IMS network (step S204).
With the processing so far, it is possible to select the IMS network of initial SDP answer transmitting side (SBC 1b) as the executor of transcoding based on “own-side” and “opposite-side” communicated between the SBC 1a and the SBC 1b in the first SDP negotiation. It is needless to say that the SBC 1b may save “opposite-side” set by the SBC 1a and figure out that transcoding is executed by itself by referring to it. In addition, the SBC 1a may save “own-side” set by the SBC 1b and figure out that the SBC 1a does not have to execute transcoding and the SBC 1b has to execute transcoding by referring to it.
Thereafter, when the media packet is transmitted from the own IMS network, the SBC 1b executes the transcoding of “codec b→a” and transmits the media packet to the other IMS network (SBC 1a), and when the media packet is transmitted from the other IMS network, the SBC 1b executes the transcoding of “codec a→b” and transmits the media packet to the own IMS network (step S205).
Then, a case where the subsequent SDP offer is generated in the IMS network of initial SDP answer transmitting side is described.
Once the SBC 1b receives the subsequent SDP offer from the own IMS network, since the executor of transcoding is the SBC 1b itself, the SBC 1b adds the codec that can be transcoded by the own IMS network or a terminal in the own IMS network (codec a) into the codec list set in the subsequent SDP offer, sets “own-side” into the subsequent SDP offer, and transmits the subsequent SDP offer to the other IMS network (SBC 1a) (step S206).
Next, once the SBC 1a receives the subsequent SDP offer from the SBC 1b, since the executor of transcoding is not the SBC 1a itself, the SBC 1a adds no codec into the codec list set in the subsequent SDP offer, deletes “own-side” from the subsequent SDP offer, and transmits the subsequent SDP offer to the own IMS network (step S207).
Next, once the SBC 1a receives the subsequent SDP answer from the own IMS network, since the subsequent SDP answer includes the codec included in the previously received SDP offer (codec a), the SBC 1a transmits (transparently) the subsequent SDP answer to the other IMS network (SBC 1b) (step S208). At this time, since “own-side” was set in the previously received SDP offer, the SBC 1a sets “opposite-side” into the subsequent SDP offer.
Next, once the SBC 1b receives the subsequent SDP answer from the SBC 1a, since the subsequent SDP answer does not include the codec included in the previously received SDP offer (codec b) but the previously transmitted codec added by the SBC 1b itself (codec a), the SBC 1b chooses one codec from the codecs included in the previously received SDP offer (only codec b), sets that codec to the subsequent SDP answer, and transmits (transparently) the subsequent SDP answer to the own IMS network (step S209).
Thereafter, when the media packet is transmitted from the own IMS network, the SBC 1b executes the transcoding of “codec b→a” and transmits the media packet to the other IMS network (SBC 1a), and when the media packet is transmitted from the other IMS network, the SBC 1b executes the transcoding of “codec a→b” and transmits the media packet to the own IMS network (step S210).
With the processing in steps S206 to S210, even when the subsequent SDP offer is generated in the IMS network of initial SDP answer transmitting side, it is possible to continue the transcoding in the IMS network of initial SDP answer transmitting side (SBC 1b).
Next, a renegotiation operation in a case where the IMS network that is requested to execute the transcoding cannot execute transcoding is described with reference to
First, after the SBC 1a receives the initial SDP offer from the own IMS network, if no codec conversion is executed in the own IMS network (SBC 1a) based on the operator policy, the SBC 1a adds no codec into the codec list set in the initial SDP offer, sets “opposite-side” into the initial SDP offer, and transmits the initial SDP offer to the other IMS network (SBC 1b) (step S301).
Next, once the SBC 1b receives the initial SDP offer from the SBC 1a, if no codec conversion is executed in the own IMS network (SBC 1b) based on the operator policy although “opposite-side” is set in the initial SDP offer, the SBC 1b transmits (transparently) the initial SDP offer to the own IMS network (step S302).
Thereafter, the codec that the incoming-side terminal itself in the IMS network of the SBC 1b wants to use is selected. Specifically, when the media condition in the initial SDP offer (codec a) does not include a media condition that can be used by the incoming-call terminal itself for communication, the incoming-call terminal sets the SDP to a 488 response (=Not Acceptable response; error response), describes the media condition that the incoming terminal itself wants to use for communication (codec b) into the SDP, and sends back the SDP.
Next, once the SBC 1b receives the SDP set to the 488 response from the own IMS network, since this is the 488 response although “opposite-side” was set in the previously received SDP offer, the SBC 1b sets “opposite-side” into the SDP and transmits the SDP to the other IMS network (SBC 1a) (step S303).
Note that, in step S303, although the same information element value “opposite-side” is formally set in the SDP, it is actually a request to change the executor of transcoding from the SBC 1b to the SBC 1a.
Next, once the SBC 1a receives the SDP from the SBC 1b, since no codec conversion is performed in the own IMS network (SBC 1a) at this timing likewise step S301 although “opposite-side” is set in the SDP, the SBC 1a transmits (transparently) the SDP to the own IMS network (step S304).
Thereafter, a second initial SDP offer to which the same codec (codec a) is set is transmitted again from the outgoing-call terminal in the IMS network of the SBC 1a.
Next, once the SBC 1a receives the second initial SDP offer from the own IMS network, if “opposite-side” is set in the SDP previously received from the other IMS network and transcoding can be executed by the SBC 1a itself although execution of the codec conversion was not planned in step S301, the SBC 1a adds the codec that can be transcoded by the own IMS network or a terminal in the own IMS network into the codec list set in the second initial SDP offer, sets “own-side” into the second initial SDP offer, and transmits the second initial SDP offer to the other IMS network (SBC 1b) (step S305).
Step S306 to Step S309 after this are the same as the above-described steps S102 to S105.
According to this embodiment, since the multiple IMS networks (SBC 1a and SBC 1b) set the information element that requests any of the IMS networks to execute transcoding into the SDP, use that information element to select an IMS network (SBC 1a or SBC 1b) that is to execute transcoding between the IMS networks (between SBC 1a and SBC 1b), and execute transcoding of media data in the selected IMS network, it is possible to fix the IMS network that is determined to execute the transcoding.
Thus, since the execution point and the executor of transcoding which consumes enormous resources can be fixed on the initial SDP offer transmitting side or the initial SDP answer transmitting side, it is possible to predict a resource to be required by the communications carrier and to design equipment, and this facilitates organizing access charges between the communications carriers.
In addition, according to this embodiment, when the IMS network requested by the information element of the SDP cannot execute transcoding, that information element is changed so as to indicate an IMS network other than that IMS network, and this makes it possible to appropriately change the IMS network (SBC) that is to execute transcoding. Thus, even when one IMS network cannot execute transcoding, transcoding still can be executed in any different IMS network, and this improves establishment of call connection between the outgoing and incoming terminals.
In Second Embodiment, the SDP offer transmitting side and/or the SDP answer transmitting side manage codec information, which is selected by the last SDP negotiation between the two sides of the own IMS network, as session-relevant information element to continue transcoding.
The overall configuration of the call control system according to this embodiment and the functional block configurations of the SBCs 1a, 1b are similar to those of First Embodiment illustrated in
The SDP processing unit 11 has the conventional function that is for example the SDP rewrite processing (such as processing of adding and deleting a codec to and from the SDP).
The codec information storing unit 13 has not only the conventional function of storing the codec information that can be transcoded by the own IMS network (own SBC) or a terminal in the own IMS network but also a function of storing the before-converted and after-converted codec information selected by the SDP negotiation as the session-relevant information element.
The transcoding unit 12 has not only the conventional function of transcoding the media packet (media data) but also a function of executing or not executing transcoding based on the session-relevant information element of the codec information storing unit 13. Specifically, when the converted codec information managed by the session-relevant information element is not included in the received SDP, the transcoding unit 12 is determined to execute transcoding, and when the converted codec information is included, the transcoding unit 12 is determined to not execute transcoding.
So far, the functions of the SBC 1a and the SBC 1b are schematically described. Note that, more specifically, each SDP processing unit 11 of the SBC 1a and the SBC 1b performs operation and processing according to the operation details exemplified in Table 3 and Table 4.
Next, an operation in a case where transcoding is determined to be executed in the IMS network of initial SDP offer transmitting side (SBC 1a) is described with reference to
First, after the SBC 1a receives the initial SDP offer from the own IMS network, if the codec conversion is determined to be executed in the own IMS network, the SBC 1a adds the codec that can be transcoded by the own IMS network or a terminal in the own IMS network (codec b) into the codec list set in the initial SDP offer and transmits the initial SDP offer to the other IMS network (SBC 1b) (step S401).
Next, once the SBC 1b receives the initial SDP offer from the SBC 1a, when no codec conversion is determined to be executed in the own IMS network, the SBC 1b adds no codec into the codec list set in the initial SDP offer and transmits (transparently) the initial SDP offer to the own IMS network (step S402).
Thereafter, the codec that the incoming-side terminal itself in the IMS network of the SBC 1b wants to use is selected. Specifically, when the media conditions in the initial SDP offer (codec a, b) includes a media condition that can be used by the incoming-call terminal itself for communication, the incoming-call terminal chooses that media condition (codec b), describes it into the initial SDP answer, and sends back the initial SDP answer.
Next, once the SBC 1b receives the initial SDP answer from the own IMS network, since the initial SDP answer includes the codec included in the previously received SDP offer, the SBC 1b transmits (transparently) the initial SDP answer to the other IMS network (SBC 1a) (step S403). At this time, the SBC 1b saves information on the received codec (codec b) and information on the transmitted codec (codec b). Particularly, the SBC 1b manages the information on the transmitted codec (codec b) as the converted codec information.
Next, once the SBC 1a receives the initial SDP answer from the SBC 1b, since the initial SDP answer does not include the codec included in the previously received SDP offer (codec a) but the previously transmitted codec added by the SBC 1a itself (codec b), the SBC 1a chooses one codec from the codecs included in the previously received initial SDP offer (only codec a), sets that codec to the initial SDP answer, and transmits the initial SDP answer to the own IMS network (step S404). At this time, the SBC 1a saves information on the received codec (codec b) and information on the transmitted codec (codec a). Particularly, the SBC 1b manages the information on the transmitted codec (codec a) as the converted codec information.
Thereafter, when the media packet is transmitted from the other IMS network (SBC 1b), the SBC 1a executes the transcoding of “codec b→a” and transmits the media packet to the own IMS network, and when the media packet is transmitted from the own IMS network, the SBC 1a executes the transcoding of “codec a→b” and transmits the media packet to the other IMS network (step S405).
Then, a case where the subsequent SDP offer is generated in the IMS network of initial SDP answer transmitting side is described.
Once the SBC 1b receives the subsequent SDP offer from the own IMS network, since the subsequent SDP offer includes the codec selected by the previous SDP negotiation between the SBC 1b itself and the opposite IMS network opposing to itself (SBC 1a) (the converted codec saved in step S403 (codec b)), the SBC 1b transmits (transparently) the subsequent SDP offer to the other IMS network (SBC 1a) (step S406).
Next, once the SBC 1a receives the subsequent SDP offer from the SBC 1b, since the subsequent SDP offer does not include the codec selected by the previous SDP negotiation between the SBC 1a itself and a device in the own IMS network (outgoing-side terminal and the like) (the converted codec saved in step S404 (codec a)) and since transcoding is possible between the codec selected by the previous SDP negotiation (codec a) and the codec included in the subsequent SDP offer (codec b), the SBC 1a adds the codec selected by the previous SDP negotiation (codec a) and transmits the subsequent SDP offer to the own IMS network (step S407).
Next, once the SBC 1a receives the subsequent SDP answer from the own IMS network, since the subsequent SDP answer does not include the codec included in the previously received SDP offer (codec b) but the previously transmitted codec added by the SBC 1a itself (codec a), the SBC 1a chooses one codec from the codecs included in the previously received SDP offer (only codec b), sets that codec to the subsequent SDP answer, and transmits the subsequent SDP answer to the other IMS network (SBC 1b) (step S408).
Next, once the SBC 1b receives the subsequent SDP answer from the SBC 1a, since the subsequent SDP answer includes the codec included in the previously received SDP offer (codec b), the SBC 1b transmits (transparently) the subsequent SDP answer to the own IMS network (step S409).
Thereafter, when the media packet is transmitted from the other IMS network (SBC 1b), the SBC 1a executes the transcoding of “codec b→a” and transmits the media packet to the own IMS network, and when the media packet is transmitted from the own IMS network, the SBC 1a executes the transcoding of “codec a→b” and transmits the media packet to the other IMS network (step S410).
Next, an operation in a case where transcoding is determined to be executed in the IMS network of initial SDP answer transmitting side (SBC 1b) is described with reference to
First, after the SBC 1a receives the initial SDP offer from the own IMS network, if no codec conversion is determined to be executed in the own IMS network, the SBC 1a adds no codec into the codec list set in the initial SDP offer and transmits the initial SDP offer to the other IMS network (SBC 1b) (step S501).
Next, once the SBC 1b receives the initial SDP offer from the SBC 1a, when the codec conversion is determined to be executed in the own IMS network, the SBC 1b adds the codec that can be transcoded by the own IMS network or a terminal in the own IMS network (codec b) into the codec list set in the initial SDP offer, and transmits the initial SDP offer to the own IMS network (step S502).
Thereafter, the codec that the incoming-side terminal itself in the IMS network of the SBC 1b wants to use is selected. Specifically, when the media conditions in the initial SDP offer (codec a, b) includes a media condition that can be used by the incoming-call terminal itself for communication, the incoming-call terminal chooses that media condition (codec b), describes it into the initial SDP answer, and sends back the initial SDP answer.
Next, once the SBC 1b receives the initial SDP answer from the own IMS network, since the initial SDP answer does not include the codec included in the previously received SDP offer (codec a) but the previously transmitted codec added by the SBC 1b itself (codec b), the SBC 1b chooses one codec from the codecs included in the previously received initial SDP offer (only codec a), sets that codec to the initial SDP answer, and transmits the initial SDP answer to the other IMS network (SBC 1a) (step S503). At this time, the SBC 1b saves information on the received codec (codec b) and information on the transmitted codec (codec a). Particularly, the SBC 1b manages the information on the transmitted codec (codec a) as the converted codec information.
Next, once the SBC 1a receives the initial SDP answer from the SBC 1b, since the initial SDP answer includes the codec included in the previously received SDP offer (codec a), the SBC 1a transmits (transparently) the initial SDP answer to the own IMS network (step S504). At this time, the SBC 1a saves information on the received codec (codec a) and information on the transmitted codec (codec a). Particularly, the SBC 1a manages the information on the transmitted codec (codec a) as the converted codec information.
Thereafter, when the media packet is transmitted from the own IMS network, the SBC 1b executes transcoding of “codec b→a” and transmits the media packet to the other IMS network (SBC 1a), and when the media packet is transmitted from the other IMS network, the SBC 1b executes the transcoding of “codec a→b” and transmits the media packet to the own IMS network (step S505).
Then, a case where the subsequent SDP offer is generated in the IMS network of initial SDP answer transmitting side is described.
Once the SBC 1b receives the subsequent SDP offer from the own IMS network, since the subsequent SDP offer does not include the codec selected by the previous SDP negotiation between the SBC 1b itself and the opposite IMS network opposing to itself (SBC 1a) (the converted codec saved in step S503 (codec a)) and since transcoding is possible between the codec selected by the previous SDP negotiation (codec a) and the codec included in the subsequent SDP offer (codec b), the SBC 1b adds the codec selected by the previous SDP negotiation (codec a) and transmits the subsequent SDP offer to the other IMS network (SBC 1a) (step S506).
Next, once the SBC 1a receives the subsequent SDP offer from the SBC 1b, since the subsequent SDP offer includes the codec selected by the previous SDP negotiation between the SBC 1a itself and a device in the own IMS network (outgoing-side terminal and the like) (the converted codec saved in step S504 (codec a)), the SBC 1a transmits (transparently) the subsequent SDP offer to the own IMS network (step S507).
Next, once the SBC 1a receives the subsequent SDP answer from the own IMS network, since the subsequent SDP answer includes the codec included in the previously received SDP offer (codec a), the SBC 1a transmits (transparently) the subsequent SDP answer to the other IMS network (SBC 1b) (step S508).
Next, once the SBC 1b receives the subsequent SDP answer from the SBC 1a, since the subsequent SDP answer does not include the codec included in the previously received SDP offer (codec b) but the previously transmitted codec added by the SBC 1b itself (codec a), the SBC 1b chooses one codec from the codecs included in the previously received SDP offer (only codec b), sets that codec to the subsequent SDP answer, and transmits the subsequent SDP answer to the own IMS network (step S509).
Thereafter, when the media packet is transmitted from the own IMS network, the SBC 1b executes transcoding of “codec b→a” and transmits the media packet to the other IMS network (SBC 1a), and when the media packet is transmitted from the other IMS network, the SBC 1b executes transcoding of “codec a→b” and transmits the media packet to the own IMS network (step S510).
According to this embodiment, since each of the multiple IMS networks (SBC 1a and SBC 1b) stores the converted codec information selected by the SDP negotiation and executes transcoding of the media data in the own IMS network (SBC 1a or SBC 1b) when the received SDP does not include the converted codec information, it is possible to fix the IMS network that is determined to execute the transcoding.
Thus, since the execution point and the executor of transcoding which consumes enormous resources can be fixed on the initial SDP offer transmitting side or the initial SDP answer transmitting side, it is possible to predict a resource to be required by the communications carrier and to design equipment, and this facilitates organizing access charges between the communications carriers.
Lastly, the SBC 1a and SBC 1b described in this embodiment can be implemented by a computer (information processing device) provided with a CPU, a memory, a hard disk, and so on. In addition, it is also possible to create a program for functioning the computer as the SBC 1a and SBC 1b (call control program) and a storing medium of that program.
At last, Table 3 and Table 4 are further described. In Second Embodiment, as described in the operation description column of “Subsequent” of “SDP offer” in Table 3 or Table 4, the processing of “If the selected codec is not included and also transcoding is possible between the previously negotiated codec and the codec included in the received SDP offer, add the previously negotiated codec” is executed.
As for such a processing, for example, a processing can be considered such as “In the SBC 1a determined to execute transcoding, if the SDP offer from the SBC 1b does not include the previously selected codec (codec b) and transcoding is possible between the codec selected by the previous negotiation (S401 to S404) (codec a) and the codec included in the received SDP offer (e.g., codec c), add the previously negotiated codec (codec a) to the SDP offer”. In this case, the SBC 1a keeps a transcodable list in advance for example, and if a codec type of “codec a” and a codec type of “codec c” are being associated with each other in that transcodable list, the SBC 1a determines that the transcoding is possible.
In other words, based on Table 3 or Table 4, an SBC 1 (communication device) may also execute a processing such as “If the own communication device is executing transcoding and also receives an SIP message containing the SDP offer not including the previously selected codec (codec b), and if transcoding is possible between the codec included in such an SDP offer (e.g., codec c) and the codec currently in use in the forwarding destination (codec a), add the codec currently in use in the forwarding destination (codec a) into the codec list in the SDP offer”.
Note that the transcodable list is an example of a method that enables the SBC 1 to figure out the transcodable codec type.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2016-139714 | Jul 2016 | JP | national |
This application is a divisional of Ser. No. 16/923,358 filed Jul. 8, 2020, which is a divisional of U.S. Ser. No. 16/309,612 filed Jul. 14, 2017, issued as U.S. Pat. No. 11,012,478. This application is also related to co-pending application U.S. Ser. No. 18/142,143 filed concurrently herewith and to U.S. Ser. No. 18/204,613 filed Jun. 1, 2023, all of which are hereby incorporated by reference in their entireties for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6359902 | Putzolu | Mar 2002 | B1 |
| 7512118 | Stephens | Mar 2009 | B1 |
| 7617319 | Burks et al. | Nov 2009 | B2 |
| 7751359 | Bienn et al. | Jul 2010 | B1 |
| 7940793 | Zilbershtein et al. | May 2011 | B2 |
| 7944862 | Taylor et al. | May 2011 | B2 |
| 8059656 | Telikepalli et al. | Nov 2011 | B1 |
| 8139541 | Ejzak et al. | Mar 2012 | B2 |
| 8199727 | Bienn et al. | Jun 2012 | B1 |
| 8213365 | Bienn et al. | Jul 2012 | B2 |
| 8249076 | Bertone et al. | Aug 2012 | B1 |
| 8289368 | Gopal et al. | Oct 2012 | B2 |
| 8472453 | Bangalore et al. | Jun 2013 | B2 |
| 8560729 | Jabri et al. | Oct 2013 | B2 |
| 8595018 | Kampmann et al. | Nov 2013 | B2 |
| 8670770 | Fitzgerald et al. | Mar 2014 | B2 |
| 8776161 | Gazier et al. | Jul 2014 | B2 |
| 8843992 | Fernandez Alonso et al. | Sep 2014 | B2 |
| 8893204 | Levin et al. | Nov 2014 | B2 |
| 9143534 | Kelliher | Sep 2015 | B1 |
| 9282131 | Hosur et al. | Mar 2016 | B2 |
| 9509725 | Belling et al. | Nov 2016 | B2 |
| 9629131 | Ozgur | Apr 2017 | B2 |
| 9876838 | Li et al. | Jan 2018 | B2 |
| 9961116 | Prajapat | May 2018 | B2 |
| 10075479 | Belling et al. | Sep 2018 | B2 |
| 10129300 | Sharma et al. | Nov 2018 | B2 |
| 10148703 | Mufti et al. | Dec 2018 | B2 |
| 10412136 | Gonzalez De Langarica et al. | Sep 2019 | B2 |
| 10594744 | Hori | Mar 2020 | B2 |
| 10848602 | Frankkila et al. | Nov 2020 | B2 |
| 11012478 | Ogawa et al. | May 2021 | B2 |
| 20040037312 | Spear | Feb 2004 | A1 |
| 20040240399 | Corrao et al. | Dec 2004 | A1 |
| 20050105511 | Poikselka | May 2005 | A1 |
| 20060153102 | Kuure et al. | Jul 2006 | A1 |
| 20070047707 | Mayer et al. | Mar 2007 | A1 |
| 20070153766 | Bienn et al. | Jul 2007 | A1 |
| 20080025414 | Kim et al. | Jan 2008 | A1 |
| 20080081648 | Kang | Apr 2008 | A1 |
| 20090183211 | Yan et al. | Jul 2009 | A1 |
| 20100134590 | Lindstrom | Jun 2010 | A1 |
| 20100150141 | Lee | Jun 2010 | A1 |
| 20110136483 | Dwight | Jun 2011 | A1 |
| 20120185600 | Belling | Jul 2012 | A1 |
| 20120219130 | Zhu et al. | Aug 2012 | A1 |
| 20130232273 | Lawn | Sep 2013 | A1 |
| 20130246052 | Tanaka et al. | Sep 2013 | A1 |
| 20140101328 | Coulombe | Apr 2014 | A1 |
| 20140328323 | Zhang et al. | Nov 2014 | A1 |
| 20150045041 | Polisetty et al. | Feb 2015 | A1 |
| 20160021163 | Lee | Jan 2016 | A1 |
| 20160149984 | Prajapat | May 2016 | A1 |
| 20180014168 | Lau et al. | Jan 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 1069738 | Jan 2001 | EP |
| 2010512106 | Apr 2010 | JP |
| 2010273103 | Dec 2010 | JP |
| 2011166453 | Aug 2011 | JP |
| 2012209638 | Oct 2012 | JP |
| 2013012856 | Jan 2013 | JP |
| Entry |
|---|
| “IP Multimedia Call Control Protocol Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)”, 3GPP TS 24.229 V14.0.1, Jun. 2016, 932 pages. |
| “IP Multimedia Subsystem (IMS)”, 3GPP TS 23.228 V14.0.0, Jun. 2016, 40 pages. |
| U.S. Appl. No. 16/309,612 , “Final Office Action”, Nov. 13, 2020, 7 pages. |
| U.S. Appl. No. 16/309,612 , “Non-Final Office Action”, Aug. 7, 2020, 8 pages. |
| U.S. Appl. No. 16/309,612 , “Notice of Allowance”, Mar. 19, 2021, 9 pages. |
| U.S. Appl. No. 16/923,358 , “Final Office Action”, Feb. 2, 2023, 21 pages. |
| U.S. Appl. No. 16/923,358 , “Final Office Action”, May 12, 2022, 15 pages. |
| U.S. Appl. No. 16/923,358 , “Non-Final Office Action”, Feb. 4, 2022, 11 pages. |
| U.S. Appl. No. 16/923,358 , “Non-Final Office Action”, Oct. 28, 2022, 16 pages. |
| Handley , et al., “SDP: Session Description Protocol”, Network Working Group, Apr. 1998, 42 pages. |
| JP2018-527680 , “Office Action”, Sep. 17, 2019, 6 pages. |
| PCT/JP2017/025713 , “International Preliminary Report on Patentability”, Jan. 24, 2019, 8 pages. |
| PCT/JP2017/025713 , “International Search Report and Written Opinion”, Oct. 3, 2017, 10 pages. |
| PCT/JP2017/025713 , “Written Opinion”, Oct. 3, 2017, 4 pages. |
| Rosenberg , et al., “An Offer/Answer Model With Tile Session Description Protocol (SDP)”, Network Working Group, Jun. 2002, 25 pages. |
| Rosenberg , et al., “SIP; Session Initiation Protocol”; Network Working Group, Available Online At: https://www.rfc-editor.org/rfc/rfc3261.txt, Jun. 2002, 269 pages. |
| Schulzrinne , et al., “RTP: A Transport Protocol for Real-Time Applications”, Network Working Group, Request for Comments: 3550, Jul. 2003, 104 pages. |
| U.S. Appl. No. 18/142,143, Non-Final Office Action mailed on Dec. 8, 2023, 16 pages. |
| U.S. Appl. No. 18/204,613, Notice of Allowance mailed on Jan. 31, 2024, 11 pages. |
| Japanese Application No. JP2019-208007, Notice of Decision to Grant mailed on Aug. 25, 2020, 5 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230269280 A1 | Aug 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16923358 | Jul 2020 | US |
| Child | 18142183 | US | |
| Parent | 16309612 | US | |
| Child | 16923358 | US |
