JP7112949B2 - Call control system - Google Patents

Description

One aspect of the present disclosure relates to call control systems.

A technique is known for converting the content of a call transmitted between terminals into text and displaying the text on at least one of the terminals. For example, in Patent Document 1, a speech signal input from a first terminal is subjected to speech recognition, reading information of the speech recognition result is generated, and at least the reading information is transmitted to a second communication partner of the first terminal. A telephone system is described for displaying on a terminal.

JP 2008-66866 A

This mechanism is one-way text conversion, since the telephone system described above converts one speaker's utterances to text and transmits the text to the other speaker's telephone. As a means for realizing a scene in which one speaker's utterance is visually recognized by both speakers, it is conceivable to install speech recognition servers on both the calling side and the called side. However, if the connection to the speech recognition engine differs between the caller and the callee, the results of speech recognition may differ. may differ. Therefore, it is desired to match the text of the call content between the caller and callee.

A call control system according to one aspect of the present disclosure is capable of executing a speech-to-text service that converts a call transmitted between a calling terminal and a called terminal into text. In the call control system, when both the caller using the calling terminal and the called party using the called terminal are users of the voice-to-text service, the calling-side media processing device corresponding to the calling terminal and the called terminal A control unit is provided that causes one of the corresponding destination media processing devices to function as a common media processing device. A common media processing unit interfaces with a speech recognition engine that converts the caller's or called party's speech to text. The common media processing device acquires the caller text by inputting the caller's caller's voice transmitted from the caller terminal into the speech recognition engine, and transmits the caller text to both the caller terminal and the callee terminal. do. The common media processing device acquires the called-side text by inputting the called-side voice of the called party transmitted from the called terminal into the speech recognition engine, and transmits the called-side text to both the calling terminal and the called terminal. do.

In this aspect, when both the caller and the callee are users of a speech recognition service, the voices of both the caller and the callee are converted to text through a common media processing device, and the A text is sent to both the originating terminal and the terminating terminal. Since a common media processor is used for both the originating and terminating parties, the text of the call can be matched between the originating and terminating parties.

According to one aspect of the present disclosure, the text of the call content can be matched between the calling party and the called party.

1 is a diagram showing an example of the overall configuration of a call control system according to an embodiment; FIG. It is a figure showing an example of functional composition of some communication control devices concerning an embodiment. 4 is a sequence diagram showing an example of the operation of the call control system according to the embodiment; FIG. 4 is a sequence diagram showing an example of the operation of the call control system according to the embodiment; FIG. 4 is a sequence diagram showing an example of the operation of the call control system according to the embodiment; FIG. 4 is a sequence diagram showing an example of the operation of the call control system according to the embodiment; FIG. It is a figure which shows an example of the hardware constitutions of the computer used for the communication control apparatus which concerns on embodiment.

Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the description of the drawings, the same or equivalent elements are denoted by the same reference numerals, and overlapping descriptions are omitted.

A call control system is a computer system that controls calls and conversations between originating and terminating terminals. A call is a communication path temporarily occupied between a calling terminal and a called terminal. A calling terminal is a communication terminal that first requests a call connection, and a receiving terminal is a communication terminal that responds to the call connection request. By establishing a call between these two communication terminals, the caller (user of the calling terminal) and the called party (user of the called terminal) can talk. A call means voice transmitted and received between a calling terminal and a called terminal, and also means voice transmission and reception between a calling terminal and a called terminal.

In this embodiment, the call control system converts a call between a calling terminal and a called terminal into text and displays the converted text on at least one of the calling terminal and the called terminal. (also called speech recognition service). In this disclosure, converted text is also referred to as spoken text.

FIG. 1 is a diagram showing the overall configuration of a call control system 1 according to an embodiment. The call control system 1 includes a calling-side network 21 in which a calling terminal 31 resides, a called-side network 22 in which a called terminal 32 resides, and a core network 10 connecting the calling-side network 21 and the called-side network 22. . In the call control system 1, a call (communication path) is established by transmitting control signals between a plurality of devices and terminals, and a call is completed by transmitting a data signal representing voice through the call. be possible.

Both the originating terminal 31 and the receiving terminal 32 are communication terminals having call functions. Each of the originating terminal 31 and the receiving terminal 32 may be a fixed terminal or a mobile terminal. Examples of the calling terminal 31 and receiving terminal 32 include mobile phones, smart phones, tablet terminals, wearable terminals, and personal computers, but the types of terminals are not limited to these. The type of terminals may be the same or different between the originating terminal 31 and the receiving terminal 32 .

Both the originating network 21 and the terminating network 22 are access networks to which terminals are directly connected. The configuration of the access network is not limited. For example, the access network may be any wireless or wired network. The types (protocols) of access networks may be the same or different between the originating network 21 and the terminating network 22 .

The core network 10 is a network forming the core of the call control system 1 and includes various communication control devices. In this embodiment, core network 10 is assumed to be an IMS network. The IMS network is a network that uses SIP as a communication protocol and can provide multimedia services that realize not only data communication but also voice or video real-time communication. In the IMS network, calls are processed by a plurality of communication control devices such as a Call Session Control Function (CSCF), an Application Server (AS), a gateway, and a Home Subscriber Server (HSS). be done. A CSCF is a call control device that sets up calls or sessions and activates predefined services. The application server is a device that executes a predetermined supplementary service (for example, speech-to-text service) and determines whether or not the supplementary service can be executed. A gateway is a device that connects an access network and a core network. The HSS is a device (database) that stores user profiles (subscriber information).

In this embodiment, the core network 10 further includes two types of communication control devices, an MCE (Media Composition Enabler) and an SMS-GW (SMS gateway). The MCE is a media processing device that provides additional call functionality. SMS-GW is a type of gateway that connects a core network and other networks, and is a device that provides short message service (SMS).

FIG. 1 shows a communication control device particularly related to control of calls involving supplementary services. An originating SMS-GW 17 and a terminating SMS-GW 18 are shown.

Both the originating CSCF 11 and the terminating CSCF 12 execute call control for connecting the originating terminal 31 and the terminating terminal 32 for communication. By transmitting and receiving control signals and data signals (for example, voice data) between the originating CSCF 11 and the terminating CSCF 12, the originating side and the terminating side are connected to each other. The originating AS 13 is an originating application server, and the terminating AS 14 is an terminating application server. The calling side MCE 15 is a calling side media processing device, and the called side MCE 16 is a called side media processing device. The calling-side SMS-GW 17 is the calling-side SMS gateway, and the called-side SMS-GW 18 is the called-side SMS gateway.

FIG. 1 further shows a calling side Web server 41 , a called side Web server 42 , and a speech recognition engine 43 . The calling-side Web server 41 and the speech recognition engine 43 constitute a calling-side service infrastructure that provides the calling terminal 31 with a speech-to-text conversion service. The called-side Web server 42 and the voice recognition engine 43 constitute a called-side service infrastructure that provides the called terminal 32 with a speech-to-text conversion service. The speech recognition engine 43 is a common computer used by both calling and called parties that uses speech recognition to convert speech into text. Both the originating side and the terminating side service infrastructure are provided in a communication network separate from the core network 10 . The calling-side Web server 41 can perform data communication with each of the calling terminal 31, the calling-side AS 13, and the calling-side MCE 15. FIG. The terminating-side Web server 42 can perform data communication with each of the terminating terminal 32, the terminating-side AS 14, and the terminating-side MCE 16. FIG. The speech recognition engine 43 can perform data communication with each of the originating MCE 15 and the terminating MCE 16 . The originating terminal 31 can provide a speech-to-text conversion service to the originator by connecting to the originating side Web server 41 . The receiving terminal 32 can provide a speech-to-text conversion service to the receiving party by connecting to the receiving side Web server 42 .

In this embodiment, the core network 10 further comprises a session database (session DB) 19 . The session database 19 is a device (storage unit) that stores session information regarding a call (session) involving a speech-to-text service, and is a common database used by both the caller and callee. Session database 19 can be accessed by originating AS 13 and terminating AS 14 .

For example, the session information corresponding to one call includes session ID, originating auxiliary session ID, terminating auxiliary session ID, subscriber number of originating terminal 31, subscriber number of terminating terminal 32, originating end point, terminating side Data items such as endpoint and recognition direction may be included. A session ID is an identifier that uniquely identifies a call (session). The auxiliary session ID is an identifier prepared so that even a web server located outside the core network 10 can uniquely identify a call. The calling side auxiliary session ID is used for the calling side Web server 41 and the called side auxiliary session ID is used for the called side Web server 42 . An endpoint is an identifier that uniquely identifies a web server. The originating endpoint uniquely identifies the originating Web server 41 , and the terminating endpoint uniquely identifies the terminating Web server 42 . The recognition direction is information indicating to which communication terminal the voice text is to be sent.

The data structure of session information is not limited and may be designed according to any policy. For example, the session information may be expressed by associating a calling-side record and a called-side record with each other. Alternatively, the session information may be expressed by integrating data items of both the originating side and the receiving side into one record.

Each device shown in FIG. 1 is configured using at least one computer. When a plurality of computers are used, these computers are interconnected via a communication network to logically construct one device.

One of the features of the call control system 1 is that when both the caller and the called party use the speech-to-text service, either the caller or the called party can reproduce the voices of both the caller and the called party. It's about converting to text. As shown in FIG. 1, even if the voice recognition engine 43 is common to both the calling side and the called side, if the connection to the voice recognition engine 43 differs between the calling side and the called side, the result of voice recognition will be different. It could be different. For example, there is a possibility that the speech text will be different when a certain utterance is input from the originating MCE 15 to the speech recognition engine 43 and when the same utterance is input from the destination MCE 16 to the speech recognition engine 43. . In the call control system 1, only one of the calling side MCE 15 and the called side MCE 16 functions as a common media processing device in order to match the text of the call content between both the calling side and the called side. This common media processing unit transmits both the caller's and called party's voice to the speech recognition engine 43 and the voice text to both the calling Web server 41 and the called Web server 42 . Figure 1 also shows the connections 51, 52 associated with this arrangement. The connection 51 is used when the calling side MCE 15 functions as a common media processing device in one call (session), and the connection 52 is used when the receiving side MCE 16 functions as a common media processing device in one call (session). used for

FIG. 2 is a diagram illustrating an example of a functional configuration of an application server; The originating AS 13 has a service control section 131, a session control section 132, and a service scenario section 133 as functional elements. The service control unit 131 is a functional element that transmits and receives data to and from the CSCF 11 on the calling side. The session control unit 132 is a functional element that transmits and receives data to and from the originating MCE 15 . The service scenario unit 133 is a functional element that transmits and receives data to and from the SMS-GW 17 on the calling side and the Web server 41 on the calling side. When the calling side MCE 15 processes the voices of the calling side and the called side respectively, the service scenario section 133 may also transmit and receive data to and from the called side Web server 42, and the connection 61 in FIG. Indicates communication.

The destination AS 14 has a service control section 141, a session control section 142, and a service scenario section 143 as functional elements. The service control unit 141 is a functional element that transmits and receives data to and from the CSCF 12 on the receiving side. The session control unit 142 is a functional element that transmits and receives data to and from the destination MCE 16 . The service scenario unit 143 is a functional element that transmits and receives data to and from the SMS-GW 18 on the receiving side and the Web server 42 on the receiving side. When the receiving side MCE 16 processes the voices of the calling side and the called side respectively, the service scenario section 143 may also transmit and receive data to and from the calling side Web server 41, and the connection 62 in FIG. Indicates communication.

Both the calling side AS 13 and the called side AS 14 control one of the calling side MCE 15 and the called side MCE 16 to function as a common media processing device when both the caller and the called party use the speech-to-text service. have a department. In the originating AS 13, at least one of the service control section 131, the session control section 132, and the service scenario section 133 corresponds to its control section. At least one of the service control section 141, the session control section 142, and the service scenario section 143 corresponds to the control section of the destination AS 14. FIG.

In this embodiment, an example in which the originating MCE 15 processes both voices will be described. Therefore, connection 51 shown in FIG. 1 and connection 61 shown in FIG. 2 are utilized. However, the present disclosure is not limited to that example, and the terminating MCE 16 may process both voices.

An example of the operation of the call control system 1 according to this embodiment will be described with reference to FIGS. 3 to 6. FIG. 3 to 6 are sequence diagrams showing an example of the operation of the call control system 1. FIG. FIG. 3 shows an example of the process of establishing a call. 4 and 5 show an example of processing for activating the speech-to-text service. FIG. 6 shows an example of the process of displaying the spoken text on the communication terminal. For ease of understanding, FIGS. 3-6 show only those components, processes, and data signals specifically related to the control of the call and speech-to-text services.

First, referring to FIG. 3, an example of a call establishment process will be described as a process flow S1.

In step S101, the originating terminal 31 transmits an INVITE message in response to the originator's originating operation, and the originating AS 13 receives the INVITE message. The INVITE message is a control signal (call establishment request signal) transmitted to establish a call (session) between the calling terminal 31 and the called terminal 32 . This INVITE message enters the core network 10 via the originating network 21 . In core network 10 , originating CSCF 11 forwards the INVITE message to originating AS 13 .

In step S102, the service control unit 131 responds to the INVITE message and activates the speech-to-text service for the calling terminal 31 (caller). The service control unit 131 accesses the subscriber management function, refers to the subscriber information of the caller, and determines whether or not the caller has a contract for the speech-to-text conversion service. If the caller subscribes to the speech-to-text service, the service control unit 131 activates the service. In this embodiment, it is assumed that the caller is a subscriber of the voice-to-text conversion service. In connection with service activation, the service control unit 131, the session control unit 132, and the service scenario unit 133 work together to establish the session ID of the call to be established, the calling side auxiliary session ID, and the subscriber of the calling terminal 31. The session information including the number and the subscriber number of the called terminal 32 is stored in the session database 19 .

In step S103, the service scenario unit 133 transmits a push notification to the originating SMS-GW 17, and in step S104, the originating SMS-GW 17 transmits a push request to the originating terminal 31 in response to the push notification. The service scenario unit 133 accesses the user profile in response to the instruction from the service control unit 131, refers to the user information of the caller, and determines the contract status of the speech-to-text service. The service scenario unit 133 sends a push notification when the speech-to-text service can be provided to the caller. This embodiment assumes that the caller is qualified to receive the speech-to-text service. The push request includes information necessary for the originating terminal 31 to receive the speech-to-text service from the originating Web server 41 (for example, the device token of the originating terminal 31 and the originating auxiliary session ID), and the push notification Contains at least part of the information that makes up the push request.

In step S<b>105 , the session control unit 132 transmits an INVITE message to the calling MCE 15 for connection with the calling MCE 15 . After the originating MCE 15 responds to the INVITE message and performs processing for the speech-to-text service, it transmits a 200_OK message in step S106. The 200_OK message is a response signal indicating that the processing corresponding to the INVITE message was successfully executed. That is, the 200_OK message is a success response signal corresponding to the INVITE message.

In step S107, the service control unit 131 transmits an INVITE message to the AS 14 on the receiving side. The service control unit 131 adds, in header information of the INVITE message, an originating media device ID, which is an identifier for uniquely identifying the originating MCE 15, and an originating-side service ID indicating that a speech-to-text conversion service is to be executed on the originating side. Add information. The service control unit 131 then transmits an INVITE message containing the originating media device ID and the originating service information. This INVITE message reaches terminating AS 14 via originating CSCF 11 and terminating CSCF 12 .

In step S108, the service control unit 141 responds to the INVITE message from the originating AS 13 and activates the speech-to-text service for the receiving terminal 32 (recipient). The service control unit 141 accesses the subscriber management function, refers to the subscriber information of the called party, and determines whether or not the called party has a contract for the speech-to-text conversion service. If the called party subscribes to the voice-to-text service, the service control unit 141 activates the service. In this embodiment, it is assumed that the called party is a subscriber of the voice-to-text conversion service. In connection with service activation, the service control unit 141, the session control unit 142, and the service scenario unit 143 cooperate to write the incoming side auxiliary session ID of the call to be established into the corresponding session information in the session database 19. .

In step S109, the service scenario unit 143 transmits a push notification to the called-side SMS-GW 18, and in step S110, the called-side SMS-GW 18 transmits a push request to the called terminal 32 in response to the push notification. The service scenario unit 143 accesses the user profile in response to the instruction from the service control unit 141, refers to the user information of the called party, and determines the contract status of the speech-to-text service. The service scenario unit 143 sends a push notification when the speech-to-text service can be provided to the called party. In this embodiment, it is assumed that the called party is entitled to enjoy the speech-to-text service. The push request includes information necessary for the receiving terminal 32 to receive the speech-to-text service from the receiving-side Web server 42 (for example, the device token of the receiving terminal 32 and the receiving-side auxiliary session ID). Contains at least part of the information that makes up the push request.

In step S111, the session control unit 142 transmits an INVITE message to the MCE 16 on the receiving side for connection with the MCE 16 on the receiving side. The terminating MCE 16 performs processing for the speech-to-text service in response to the INVITE message. By referring to the originating media device ID and the originating service information in the INVITE message, the terminating MCE 16 confirms that the originating side will execute the voice-to-text conversion service and that the originating MCE 15 will execute the service. recognize. Based on this recognition, the destination MCE 16 does not provide voice data to the voice recognition engine 43 . However, the connection between the terminating MCE 16 and the terminating AS 14 is maintained until the call is disconnected. In step S112, the terminating MCE 16 sends a 200_OK message to the terminating AS 14.

In step S<b>113 , the service control unit 141 transmits an INVITE message to the receiving terminal 32 . The INVITE message is sent from the terminating AS 14 to the terminating CSCF 12 and from the terminating CSCF 12 through the terminating network 22 to the terminating terminal 32 . When the receiving terminal 32 receives the INVITE message, the calling process for the receiving terminal 32 is completed.

In step S114, the terminating terminal 32 transmits a 200_OK message in response to the terminating party answering the call, and this 200_OK message reaches the terminating AS 14 via the terminating network 22 and the terminating CSCF 12 .

In step S115, each of service control unit 141, session control unit 142, and service scenario unit 143 of terminating AS 14 processes the message, and finally service control unit 141 transmits a 200_OK message to originating AS 13. . The service control unit 141 adds, in the header information of the 200_OK message, a called-side media device ID that is an identifier for uniquely identifying the called-side MCE 16 and a called-side service indicating that the speech-to-text conversion service is to be executed on the called side. Add information. The service control unit 141 then transmits a 200_OK message containing the destination media device ID and the destination service information. This 200_OK message reaches the originating AS 13 via the terminating CSCF 12 and the originating CSCF 11 .

In step S116, the session control unit 132 transmits the 200_OK message to the originating MCE 15. The originating MCE 15 refers to the terminating media device ID and the terminating service information in the 200_OK message, thereby recognizing that the terminating side also executes the speech-to-text service. Based on this recognition, the calling MCE 15 provides the voice data from the calling terminal 31 and the voice data from the receiving terminal 32 to the voice recognition engine 43 . Thus, the originating AS 13 causes the originating MCE 15 to function as a common media processing device. In step S117, the originating MCE 15 returns the 200_OK message to the originating AS 13, and in step S118, the originating AS 13 transmits the 200_OK message to the originating terminal 31. FIG. The 200_OK message reaches the originating terminal 31 via the originating CSCF 11 and the originating network 21 .

In step S119, the calling terminal 31 receives the 200_OK message, whereby a U-Plane (user plane) bus for transmitting data signals is established between the calling terminal 31 and the called terminal 32. FIG. That is, a call is established between the originating terminal 31 and the receiving terminal 32 . As a result, a call can be made between the calling terminal 31 and the receiving terminal 32 .

Next, referring to FIG. 4, an example of processing for activating the speech-to-text service will be described as a processing flow S2. This example shows a case where the start timing of the speech-to-text service at the communication terminal is the same or almost the same between the originating terminal 31 and the receiving terminal 32 .

In step S201, the originating terminal 31 transmits a connection request to the originating side Web server 41 in order to activate the application program for the speech-to-text service. The connection request is a data signal for establishing a communication connection between the originating terminal 31 and the originating Web server 41, and contains at least part of the information provided by the push request (e.g., the device token of the originating terminal 31 and Originating Auxiliary Session ID).

In step S202, processing for authenticating the caller is executed between the calling side Web server 41 and the service scenario section 133 of the calling side AS 13. FIG. The calling-side Web server 41 transmits to the calling-side AS 13 an authentication request including at least part of the information provided by the connection request (for example, the device token of the calling terminal 31). The service scenario unit 133 executes authentication processing in response to the authentication request. For example, the service scenario unit 133 checks whether the device token is valid. The service scenario unit 133 transmits the processing result to the originating Web server 41 . In this embodiment, it is assumed that the caller is authenticated.

In step S203, the originating terminal 31 activates the application program for the speech-to-text service and transmits an activation signal to the originating side Web server 41. FIG. A start signal is a data signal for executing the application program.

In step S204, the originating Web server 41 responds to the activation signal and transmits an event notification to the originating AS 13. FIG. This event notification includes the originating endpoint and the originating auxiliary session ID.

In step S 205 , the service scenario unit 133 of the originating AS 13 registers the originating endpoint in the session database 19 . The service scenario unit 133 writes the calling-side endpoint in the session information corresponding to the calling-side auxiliary session ID. This registration process enables the voice text of the currently established call (session) to be transmitted to the calling terminal 31 via the calling side Web server 41 .

The processing similar to steps S201 to S205 is executed on the receiving side as well. Similar processing is shown as steps S211 to S215.

In step S211, the receiving terminal 32 transmits a connection request to the receiving side Web server 42 in order to activate the application program for the speech-to-text service. The connection request includes at least some of the information provided by the push request (eg, the device token of the terminating terminal 32 and the terminating auxiliary session ID).

In step S212, a process for authenticating the caller is executed between the called-side Web server 42 and the service scenario section 143 of the called-side AS 14. FIG. In this embodiment, it is assumed that the called party is also authenticated.

In step S<b>213 , the receiving terminal 32 activates the application program for the speech-to-text service and transmits an activation signal to the receiving-side Web server 42 .

In step S214, the destination Web server 42 transmits an event notification to the destination AS 14 in response to the activation signal. This event notification includes the terminating endpoint and the terminating auxiliary session ID.

In step S 215 , the service scenario unit 143 of the terminating AS 14 registers the terminating endpoint in the session database 19 . The service scenario unit 143 writes the destination endpoint in the record corresponding to the destination auxiliary session ID. This registration process allows the voice text of the currently established call (session) to be sent to the called terminal 32 via the called Web server 42 .

On the calling side, steps S206 and S207 are executed after step S205. In step S206, the calling terminal 31 transmits to the calling side Web server 41 a consent signal indicating that the caller agrees to use the speech-to-text service. In step S207, originating side Web server 41 transmits an event notification to originating side AS 13 in response to the consent signal. This event notification indicates the consent of the caller. Both these consent signals and event notifications contain the originating auxiliary session ID.

On the receiving side, steps S216 and S217 are executed after step S215. In step S216, the receiving terminal 32 transmits to the receiving side Web server 42 a consent signal indicating that the receiving party agrees to use the speech-to-text service. In step S217, the destination Web server 42 transmits an event notification to the originating AS 13 in response to the consent signal. This event notification indicates the consent of the callee. Both these consent signals and event notifications contain the called party auxiliary session ID.

At step S208, the service scenario unit 133 sets the recognition direction of the session information corresponding to the established call to "bidirectional" based on the two event notifications at steps S207 and S217. Specifically, the service scenario unit 133 accesses the session database 19, identifies the session information corresponding to the auxiliary session ID of the originating side or the terminating side, and sets the recognition direction of this session information to "bidirectional". . In this way, the service scenario unit 133 sets the recognition direction to “two-way” in response to the consent signals being transmitted from both the calling terminal 31 and the receiving terminal 32 . As a result, as shown in step S220, the speech-to-text service is executed on both the originating and receiving sides.

Next, another example of processing for activating the speech-to-text service will be described as a processing flow S2A with reference to FIG. This example shows a case where the start timing of the speech-to-text service at the communication terminal is different between the calling terminal 31 and the called terminal 32. Indicates when to start the text conversion service.

In the processing flow S2A, steps S201 to S207 are executed on the originating side in the same manner as in the processing flow S2. If the timing of the process for starting the application program of the speech-to-text service differs to some extent between the calling side and the called side, step S208A is executed on the calling side after step S207. In step S208A, service scenario section 133 sets the recognition direction of the session information corresponding to the established call (session information corresponding to the calling side auxiliary session ID) to "calling side" based on the event notification in step S207. set to As a result, as shown in step S221, the speech-to-text service is executed only at the calling terminal 31. FIG.

After step S221, when steps S211 to S217 are executed on the receiving side, step S208B is executed on the calling side. In this step S208B, the service scenario unit 133 sets the recognition direction of the session information corresponding to the established call (session information corresponding to the receiving side auxiliary session ID) to "calling side" based on the event notification in step S217. to 'bidirectional' update. In this way, the service scenario unit 133 sets the recognition direction to “two-way” in response to the consent signals being transmitted from both the calling terminal 31 and the receiving terminal 32 . As a result, as shown in step S222, the voice-to-text conversion service can be executed on both the originating and terminating sides. Step S222 is the same as step S220 in the processing flow S2.

Next, an example of processing for displaying voice text on the communication terminal will be described as processing flow S3 with reference to FIG. The process flow S3 assumes that the voice-to-text service has become executable on both the originating and receiving sides (that is, step S220 or S222).

Steps S 301 to S 309 show processing for converting the voice of the called party (called voice) into text and displaying the voice text on both the calling terminal 31 and the called terminal 32 .

In step S301, voice data (receiving-side voice) transmitted from the receiving terminal 32 is sent to the core network 10 via the receiving-side network 22, and the communication control devices such as the receiving-side CSCF 12, the calling-side CSCF 11, and the calling-side AS 13 are It is transmitted to the originating side MCE 15 via. In step S<b>302 , the originating MCE 15 transmits the voice data to the voice recognition engine 43 . In step S<b>303 , the speech recognition engine 43 converts the incoming-side speech into text by executing speech recognition on the speech data, and transmits the speech text to the calling-side MCE 15 . This voice text corresponds to the destination text.

In step S304, the calling side MCE 15 transmits to the calling side Web server 41 the recognition result including the voice text and the utterance type indicating who the speaker is. Since the speech text indicates the speech of the called party, the speech type indicates the called party in the recognition result sent in this step. In step S<b>305 , the originating MCE 15 also transmits the recognition result to the destination Web server 42 . The originating MCE 15 acquires session information corresponding to the current call from the session database 19 via the originating AS 13 . In response to the recognition direction of the session information being "two-way", the originating MCE 15 acquires the originating endpoint and the terminating endpoint from the session information. The originating MCE 15 can acquire the destination of the recognition result (that is, the originating Web server 41 and the terminating Web server 42) from these endpoints. In this way, the originating MCE 15 transmits the destination text to both the originating Web server 41 and the destination Web server 42 in response to the "bidirectional" recognition direction.

In step S<b>306 , the calling-side Web server 41 transmits the recognition result to the calling terminal 31 . The originating side Web server 41 generates data including the voice text so that the voice text is displayed on the calling terminal 31 as that of the other party based on the fact that the utterance type included in the recognition result is the called side. do.

In step S307, the originating terminal 31 displays the voice text on the screen as that of the called party (communication partner) based on the data. This allows the caller to visually recognize what the other party has said.

In step S<b>308 , the receiving-side Web server 42 transmits the recognition result to the receiving terminal 32 . Based on the fact that the utterance type included in the recognition result is that of the called party, the called-side Web server 42 renders the data including the voice text so that the voice text is displayed on the called terminal 32 as that of the called party. Generate.

In step S309, the receiving terminal 32 displays the voice text on the screen based on the data as the text of the receiving party. This allows the called party to visually recognize his/her speech.

Steps S 310 to S 318 show processing for converting the voice of the caller (calling side voice) into text and displaying the voice text on both the calling terminal 31 and the receiving terminal 32 .

In step S310, voice data (calling-side voice) transmitted from the calling terminal 31 is sent to the core network 10 via the calling-side network 21, and sent to the calling-side MCE 15 via the calling-side CSCF 11 and calling-side AS 13. be. In step S<b>311 , the originating MCE 15 transmits the voice data to the voice recognition engine 43 . In step S<b>312 , the voice recognition engine 43 converts the calling side voice into text by executing voice recognition on the voice data, and transmits the voice text to the calling side MCE 15 . This voice text corresponds to the caller text.

In step S313, the calling side MCE 15 transmits to the calling side Web server 41 the recognition result including the voice text and the utterance type indicating who the speaker is. Since the speech text indicates the caller's voice, the utterance type indicates the caller's side in the recognition result sent in this step. In step S<b>314 , the originating MCE 15 also transmits the recognition result to the destination Web server 42 . The originating MCE 15 acquires session information corresponding to the current call from the session database 19 via the originating AS 13 . In response to the fact that the recognition direction of the session information is "bi-directional", the originating MCE 15 obtains the originating end point and the terminating end point from the session information. A server 42 can be identified. In this way, the calling side MCE 15 transmits the calling side text to both the calling side Web server 41 and the called side Web server 42 in response to the fact that the recognition direction is "bidirectional".

In step S<b>315 , the calling-side Web server 41 transmits the recognition result to the calling terminal 31 . Based on the fact that the utterance type included in the recognition result is that of the calling party, the originating side Web server 41 renders the data including the voice text so that the voice text is displayed on the calling terminal 31 as that of the caller himself/herself. Generate.

In step S316, the calling terminal 31 displays the voice text on the screen as the caller's own text based on the data. This allows the caller to visually recognize their own speech.

In step S<b>317 , the receiving-side Web server 42 transmits the recognition result to the receiving terminal 32 . The receiving-side Web server 42 generates data including the voice text so that the voice text is displayed on the receiving terminal 32 as that of the other party, based on the fact that the utterance type included in the recognition result is that of the calling party. do.

In step S318, the receiving terminal 32 displays the voice text on the screen as that of the caller (caller) based on the data. This allows the called party to visually recognize what the other party has said.

In this way, both Web servers set the display mode of the voice text based on the utterance type. The method of displaying the voice text as that of the speaker or the other party is not limited at all, and any method may be adopted. The Web server may change the display position of the voice text (for example, the display position of the balloon of the voice text) according to the utterance type. For example, the Web server controls the display mode so that the speaker's own voice text is displayed on the right side (an example of one side) and the voice text of the other party is displayed on the left side (an example of the other side). may Alternatively, the Web server may change the font of the voice text, the shape of the balloon, or the background color according to the type of utterance.

The setting of the display mode of the voice text based on the utterance type may be performed by the calling terminal 31 and the receiving terminal 32 . Specifically, each of the originating-side Web server 41 and the receiving-side Web server 42 transmits the utterance type together with the voice text to the corresponding communication terminal, so that the communication terminal receives the voice text based on the utterance type. A display mode may be set. This mechanism also allows each of the calling terminal 31 and the receiving terminal 32 to set the display mode, such as the display position, font, balloon shape, and background color.

Although the core network 10 is an IMS network in this embodiment, the call control system according to the present disclosure may be applied to any type of core network. In this regard, the call control system according to the present disclosure may use communication protocols other than SIP.

At least part of the functional elements implemented in the originating AS 13 may be implemented in a communication control device other than the originating AS 13 . Similarly, at least part of the functional elements implemented in the destination AS 14 may be implemented in a communication control device other than the destination AS 14 .

The block diagrams used in the description of the above embodiments show blocks for each function. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method of implementing each functional block is not particularly limited. That is, each functional block may be implemented using one device that is physically or logically coupled, or directly or indirectly using two or more devices that are physically or logically separated (e.g. , wired, wireless, etc.) and may be implemented using these multiple devices. A functional block may be implemented by combining software in the one device or the plurality of devices.

Functions include judging, determining, determining, calculating, calculating, processing, deriving, investigating, searching, checking, receiving, transmitting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, assuming, Broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc. can't For example, a functional block (component) that makes transmission work is called a transmitting unit or a transmitter. In either case, as described above, the implementation method is not particularly limited.

For example, a communication control device according to an embodiment of the present disclosure may function as a computer that performs processing of the present disclosure. FIG. 7 is a diagram showing an example of the hardware configuration of computer 100 that functions as the communication control device. Computer 100 may physically include processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, and the like.

Note that in the following description, the term "apparatus" can be read as a circuit, device, unit, or the like. The hardware configuration of the communication control device may be configured to include one or more of each device shown in the figure, or may be configured without some of the devices.

Each function in the communication control device is performed by causing the processor 1001 to perform calculations, controlling communication by the communication device 1004, and controlling the communication by the memory 1002 by loading predetermined software (programs) onto hardware such as the processor 1001 and the memory 1002. and by controlling at least one of reading and writing of data in the storage 1003 .

The processor 1001, for example, operates an operating system to control the entire computer. The processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like.

The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 to the memory 1002, and executes various processes according to them. As the program, a program that causes a computer to execute at least part of the operations described in the above embodiments is used. For example, each functional element of the communication control device may be implemented by a control program stored in memory 1002 and running on processor 1001 . Although it has been explained that the above-described various processes are executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. FIG. Processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via an electric communication line.

The memory 1002 is a computer-readable recording medium, and is composed of at least one of, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), and RAM (Random Access Memory). may be The memory 1002 may also be called a register, cache, main memory (main storage device), or the like. The memory 1002 can store executable programs (program code), software modules, etc. to perform a method according to an embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disc, a magneto-optical disc (for example, a compact disc, a digital versatile disc, a Blu-ray disk), smart card, flash memory (eg, card, stick, key drive), floppy disk, magnetic strip, and/or the like. Storage 1003 may also be called an auxiliary storage device. The storage medium described above may be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003 .

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes a high-frequency switch, a duplexer, a filter, a frequency synthesizer, and the like, for example, to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). may consist of

The input device 1005 is an input device (for example, keyboard, mouse, microphone, switch, button, sensor, etc.) that receives input from the outside. The output device 1006 is an output device (eg, display, speaker, LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated (for example, a touch panel).

Devices such as the processor 1001 and the memory 1002 are connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between devices.

In addition, the computer 100 includes hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array). A part or all of each functional block may be implemented by the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

As described above, the call control system according to one aspect of the present disclosure can execute a speech-to-text conversion service that converts a call transmitted between a calling terminal and a called terminal into text. In the call control system, when both the caller using the calling terminal and the called party using the called terminal are users of the voice-to-text service, the calling-side media processing device corresponding to the calling terminal and the called terminal A control unit is provided that causes one of the corresponding destination media processing devices to function as a common media processing device. A common media processing unit interfaces with a speech recognition engine that converts the caller's or called party's speech to text. The common media processing device acquires the caller text by inputting the caller's caller's voice transmitted from the caller terminal into the speech recognition engine, and transmits the caller text to both the caller terminal and the callee terminal. do. The common media processing device acquires the called-side text by inputting the called-side voice of the called party transmitted from the called terminal into the speech recognition engine, and transmits the called-side text to both the calling terminal and the called terminal. do.

In this aspect, when both the caller and the callee are users of a speech recognition service, the voices of both the caller and the callee are converted to text through a common media processing device, and the A text is sent to both the originating terminal and the terminating terminal. Since a common media processor is used for both the originating and terminating parties, the text of the call can be matched between the originating and terminating parties.

Also, since one of the originating media processing device and the terminating media processing device is used instead of both, at least one of the hardware resources and the number of usage licenses used to execute the speech-to-text service is used. can be saved. It also enables messages (eg, guidance) related to speech-to-text services to be sent from a common media processing device to both the originating terminal and the terminating terminal.

In a call control system according to another aspect, the control unit may cause the originating media processing device to function as a common media processing device. The timing at which the same type of processing is executed is earlier on the originating side than on the receiving side. Therefore, by using the originating side media processing device as a common media processing device, it is possible to start processing related to the voice-to-text service earlier, and to provide the user with the voice-to-text service more quickly. be possible.

In the call control system according to another aspect, the control unit transmits a calling-side media device ID that uniquely identifies the calling-side media processing device to the called-side media processing device. Receiving a destination media device ID that uniquely identifies a destination media processing device from a media processing device on the side, and in response to receiving the media device ID on the destination side, the originating media processing device functions as a common media processing device. You may let By acquiring the identifiers of the media processing devices on both the originating side and the terminating side, the common media processing device can be reliably operated.

In a call control system according to another aspect, a calling-side media processing device connects to a calling-side web server that transmits calling-side text or called-side text to a calling terminal, and a called-side media processing device transmits calling-side text or called-side text to a calling terminal. It may also be connected to a destination web server that sends the destination text to the destination terminal. The call control system may further comprise a database that stores session information including an originating endpoint that uniquely identifies the originating Web server and a terminating endpoint that uniquely identifies the terminating Web server. The common media processing device obtains the originating end point and the terminating end point of the session information, and transmits the originating text or the terminating text to the originating web server based on the originating end point. Terminate the calling or called text by sending the calling or called text to the originating terminal and sending the calling or called text to the called Web server based on the called endpoint. You can send it to your terminal. By referring to the endpoint, the web server to which the text should be sent can be specified.

In the call control system according to another aspect, the control unit generates the speech text in response to the consent signal indicating that the user agrees to use the speech-to-text service from both the calling terminal and the receiving terminal. is set to bidirectional, and the common media processing device transmits the originating side text or the terminating side text to the originating side Web in response to the fact that the recognition direction is bidirectional. It may be sent to both the server and the destination Web server. By setting the recognition direction according to the user's consent, it is possible to send the text to both the caller and the called party only if they both want the speech-to-text service.

In the call control system according to another aspect, the common media processing device further adds a speech type indicating whether the speaker is a caller or a callee for each of the caller text and the callee text. It may be sent to both the server and the destination Web server. By providing this utterance type to the web server, the web server can process the text according to the type of the utterer.

In the call control system according to another aspect, when the utterance type indicates a caller, the caller-side Web server displays the caller-side text as the voice text of the speaker himself/herself on the calling terminal. is set, and when the utterance type indicates the called party, the display mode of the called party text may be set so that the called party text is displayed as the voice text of the other party on the calling terminal. When the utterance type indicates the caller, the receiving-side Web server sets the display mode of the calling-side text so that the caller-side text is displayed as the voice text of the other party on the receiving terminal, and In the case of indicating the person, the display mode of the called party text may be set so that the called party text is displayed as the voice text of the speaker himself/herself on the called terminal.

By setting the text display mode as described above according to the speech type on each of the caller and callee, the text can be displayed according to the relationship between the user of the communication terminal and the speaker. The communication terminal displays the speech text of the user of the own device and the speech text of the other party in different display modes, which can contribute to improving the user interface of the speech-to-text service.

In the call control system according to another aspect, when the utterance type indicates a caller, the caller-side Web server displays the caller-side text as the voice text of the speaker himself/herself on the calling terminal. is displayed on the first side on the calling terminal, and if the utterance type indicates called party, the called text is displayed on the calling terminal as the spoken text of the other party on the calling terminal. may be displayed on the second side of the The called-side Web server displays the calling-side text on the first side of the called terminal such that the called-side text is displayed as the spoken text of the other party on the called terminal when the utterance type indicates the caller. and if the utterance type indicates a called party, the called party text may be displayed on the second side of the called terminal such that the called party text is displayed as the speaker's own voice text on the called terminal. good.

By setting the display position of the text according to the type of speech as described above, the text can be displayed according to the relationship between the user of the communication terminal and the speaker. Since the communication terminal displays the voice text of the user of the own device and the voice text of the other party on different sides, it is possible to clearly show the utterance of the user and the utterance of the other party to each of the caller and the called party. .

In the call control system according to another aspect, the originating-side Web server transmits the utterance type together with the originating-side text or the terminating-side text to the originating terminal, so that the originating-side text or the terminating-side text is sent to the originating terminal based on the utterance type. and the receiving-side Web server transmits the utterance type together with the calling-side text or the called-side text to the receiving terminal, thereby allowing the receiving terminal to display the calling-side text or the called-side text based on the utterance type. may be set.

By setting the text display mode as described above according to the speech type on each of the caller and callee, the text can be displayed according to the relationship between the user of the communication terminal and the speaker. The communication terminal displays the speech text of the user of the own device and the speech text of the other party in different display modes, which can contribute to improving the user interface of the speech-to-text service.

Although the present disclosure has been described in detail above, it should be apparent to those skilled in the art that the present disclosure is not limited to the embodiments described in this disclosure. The present disclosure can be practiced with modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Accordingly, the description of the present disclosure is for illustrative purposes and is not meant to be limiting in any way.

Notification of information is not limited to the aspects/embodiments described in this disclosure, and may be performed using other methods. For example, notification of information includes physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. RRC signaling may also be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.

Each aspect/embodiment described in the present disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark) )), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other suitable systems and extended It may be applied to at least one of the next generation systems. Also, a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G, etc.).

The processing procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be rearranged as long as there is no contradiction. For example, the methods described in this disclosure present elements of the various steps using a sample order, and are not limited to the specific order presented.

Certain operations that are described in this disclosure as being performed by a base station may also be performed by its upper node in some cases. In a network consisting of one or more network nodes with a base station, various operations performed for communication with a terminal may be performed by the base station and other network nodes other than the base station (e.g. MME or S-GW, etc. (including but not limited to). Although the case where there is one network node other than the base station is exemplified above, it may be a combination of a plurality of other network nodes (for example, MME and S-GW).

Information, etc., may be output from a higher layer (or lower layer) to a lower layer (or higher layer). It may be input and output via multiple network nodes.

Input/output information and the like may be stored in a specific location (for example, memory), or may be managed using a management table. Input/output information and the like can be overwritten, updated, or appended. The output information and the like may be deleted. The entered information and the like may be transmitted to another device.

The determination may be made by a value represented by one bit (0 or 1), by a true/false value (Boolean: true or false), or by numerical comparison (for example, a predetermined value).

Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be used by switching according to execution. In addition, the notification of predetermined information (for example, notification of “being X”) is not limited to being performed explicitly, but may be performed implicitly (for example, not notifying the predetermined information). good too.

Software, whether referred to as software, firmware, middleware, microcode, hardware description language or otherwise, includes instructions, instruction sets, code, code segments, program code, programs, subprograms, and software modules. , applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, and the like.

Software, instructions, information, etc. may also be sent and received over a transmission medium. For example, the software uses wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and/or wireless technology (infrared, microwave, etc.) to create websites, Wired and/or wireless technologies are included within the definition of transmission medium when sent from a server or other remote source.

Information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may refer to voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. may be represented by a combination of

The terms explained in this disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, the channel and/or symbols may be signaling. A signal may also be a message. A component carrier (CC) may also be called a carrier frequency, a cell, a frequency carrier, or the like.

As used in this disclosure, the terms "system" and "network" are used interchangeably.

In addition, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. may be represented. For example, radio resources may be indexed.

The names used for the parameters described above are not limiting names in any way. Further, the formulas, etc., using these parameters may differ from those expressly disclosed in this disclosure. Since the various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable designation, the various designations assigned to these various channels and information elements are in no way restrictive designations. is not.

In the present disclosure, "base station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", " "access point", "transmission point", "reception point", "transmission/reception point", "cell", "sector", "cell group", " Terms such as "carrier", "component carrier" may be used interchangeably. A base station may also be referred to by terms such as macrocell, small cell, femtocell, picocell, and the like.

A base station may serve one or more (eg, three) cells. When a base station accommodates multiple cells, the overall coverage area of the base station can be partitioned into multiple smaller areas, each smaller area being associated with a base station subsystem (e.g., an indoor small base station (RRH: The term "cell" or "sector" refers to part or all of the coverage area of a base station and/or base station subsystem serving communication in this coverage. point to

In this disclosure, terms such as “Mobile Station (MS),” “user terminal,” “User Equipment (UE),” “terminal,” etc. may be used interchangeably. .

A mobile station is defined by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless It may also be called a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

At least one of a base station and a mobile station may be called a transmitter, a receiver, a communication device, and the like. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, or the like. The mobile object may be a vehicle (e.g., car, airplane, etc.), an unmanned mobile object (e.g., drone, self-driving car, etc.), or a robot (manned or unmanned ). Note that at least one of the base station and the mobile station includes devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

Also, the base station in the present disclosure may be read as a user terminal. For example, communication between a base station and a user terminal is replaced with communication between multiple user terminals (for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.) Regarding the configuration, each aspect/embodiment of the present disclosure may be applied. In this case, the user terminal may have the functions that the base station has. Also, words such as "up" and "down" may be replaced with words corresponding to inter-terminal communication (for example, "side"). For example, uplink channels, downlink channels, etc. may be read as side channels.

Similarly, user terminals in the present disclosure may be read as base stations. In this case, the base station may have the functions that the user terminal has.

As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Judgement", "determining" are, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (eg, lookup in a table, database, or other data structure), ascertaining as "judged" or "determined", and the like. Also, "judgment" and "determination" are used for receiving (e.g., receiving information), transmitting (e.g., transmitting information), input, output, access (accessing) (for example, accessing data in memory) may include deeming that a "judgement" or "decision" has been made. In addition, "judgment" and "decision" are considered to be "judgment" and "decision" by resolving, selecting, choosing, establishing, comparing, etc. can contain. In other words, "judgment" and "decision" can include considering that some action is "judgment" and "decision". Also, "judgment (decision)" may be read as "assuming", "expecting", "considering", or the like.

The terms "connected", "coupled", or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, It can include the presence of one or more intermediate elements between two elements being "connected" or "coupled." Couplings or connections between elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access". As used in this disclosure, two elements are in the radio frequency domain using at least one of one or more wires, cables and printed electrical connections, and as some non-limiting and non-exhaustive examples. , electromagnetic energy having wavelengths in the microwave and optical (both visible and invisible) regions, and the like.

As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly specified otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

Any reference to elements using the "first," "second," etc. designations used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, reference to a first and second element does not imply that only two elements can be employed or that the first element must precede the second element in any way.

Where "include," "including," and variations thereof are used in this disclosure, these terms are inclusive, as is the term "comprising." is intended. Furthermore, the term "or" as used in this disclosure is not intended to be an exclusive OR.

In this disclosure, where articles have been added by translation, such as a, an, and the in English, the disclosure may include the plural nouns following these articles.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean that "A and B are different from C". Terms such as "separate," "coupled," etc. may also be interpreted in the same manner as "different."

DESCRIPTION OF SYMBOLS 1... Call control system 10... Core network 11... Calling-side CSCF 12... Calling-side CSCF 13... Calling-side AS 14... Calling-side AS 15... Calling-side MCE (calling-side media processing device) 16... Terminating side MCE (terminating side media processing device), 17 ... originating side SMS-GW, 18 ... destination side SMS-GW, 19 ... session database, 21 ... originating side network, 22 ... destination side network, 31 ... originating terminal, 32 Received terminal 41 Calling-side Web server 42 Calling-side Web server 43 Speech recognition engine 131, 141 Service control unit 132, 142 Session control unit 133, 143 Service scenario unit.

Claims (6)

A call control system capable of executing a voice-to-text conversion service for converting a call transmitted between a calling terminal and a called terminal into text,
When both the caller using the calling terminal and the called party using the called terminal are users of the speech-to-text service, the calling side media processing device corresponding to the calling terminal and the called terminal a control unit that causes one of the corresponding destination media processing devices to function as a common media processing device;
the common media processing unit interfaces with a speech recognition engine that converts the speech of the caller or the callee to text;
the common media processing device comprising:
obtaining a caller text by inputting the caller's caller's voice transmitted from the caller terminal into the speech recognition engine;
transmitting the calling-side text to both the calling terminal and the called terminal;
Acquiring a destination text by inputting the destination voice of the called party transmitted from the receiving terminal into the speech recognition engine;
sending the called party text to both the calling terminal and the called terminal;
call control system. the control unit causes the originating media processing device to function as the common media processing device;
The call control system according to claim 1. The control unit
transmitting an originating media device ID that uniquely identifies the originating media processing device to the destination media processing device;
receiving a destination media device ID that uniquely identifies the destination media processing device from the destination media processing device that received the originating media device ID;
causing the originating media processing device to function as the common media processing device in response to receiving the destination media device ID;
The call control system according to claim 2. the calling-side media processing device connects to a calling-side Web server that transmits the calling-side text or the called-side text to the calling terminal;
the called-side media processing device connects to a called-side Web server that transmits the calling-side text or the called-side text to the called terminal;
said call control system further comprising a database for storing session information including an originating endpoint that uniquely identifies said originating Web server and a terminating endpoint that uniquely identifies said terminating Web server;
the common media processing device comprising:
obtaining the originating end point and the terminating end point of the session information;
transmitting the calling-side text or the called-side text to the calling-side Web server based on the calling-side endpoint, thereby transmitting the calling-side text or the called-side text to the calling terminal;
transmitting the calling-side text or the called-side text to the called-side Web server based on the called-side endpoint, thereby transmitting the calling-side text or the called-side text to the called terminal;
4. The call control system according to claim 2 or 3. The control unit transmits the voice text to which communication terminal in response to the consent signal indicating that the user consents to the use of the voice-to-text conversion service is transmitted from both the calling terminal and the receiving terminal. Set the recognition direction to indicate whether to
The common media processing device transmits the originating text or the terminating text to both the originating web server and the terminating web server in response to the fact that the recognition direction is bidirectional. ,
The call control system according to claim 4. The common media processing device further adds, for each of the calling side text and the called side text, an utterance type indicating whether the speaker is the calling party or the called party, to the calling side Web server and the called side text. Send to both side Web servers,
6. The call control system according to claim 4 or 5.

Images