JP2020088818A - Call control system - Google Patents

Abstract

An object of the present invention is to match the text of the contents of a call between both a calling party and a called party. A call control system according to one embodiment is capable of performing a speech-to-text service. When both the caller and the called party are users of the speech-to-text service, the call control system selects between the calling-side media processing device corresponding to the calling terminal and the called-side media processing device corresponding to the called terminal. function as a common media processing device. A common media processing unit interfaces with the speech recognition engine. The common media processing device acquires the calling side text by inputting the calling side voice to the speech recognition engine, and transmits the calling side text to both the calling terminal and the called terminal. The common media processing device acquires the destination text by inputting the destination speech to the speech recognition engine, and transmits the destination text to both the originating terminal and the terminating terminal. [Selection drawing] Fig. 2

Description

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

A technique is known in which the content of a call transmitted between terminals is converted into text and the text is displayed on at least one terminal. For example, in Patent Document 1, a voice signal input from a first terminal is voice-recognized, read information of a voice recognition result is generated, and at least the read information is read by a second party who is a communication partner of the first terminal. The telephone system displayed on the terminal is described.

JP, 2008-66866, A

This mechanism is a one-way text conversion because the above telephone system converts the utterance of one speaker into text and transmits the text to the telephone of the other speaker. As a means for realizing a situation in which both speakers visually recognize the utterance of one speaker, it is conceivable to install a voice recognition server on both the calling side and the receiving side. However, if the connection to the voice recognition engine is different between the caller side and the callee side, the result of voice recognition may be different, and as a result, the text representing one utterance may be different between the caller side and the callee side. May be different. Therefore, it is desired to match the text of the call content between the calling side and the called side.

A call control system according to an aspect of the present disclosure can execute a voice text service that converts a call transmitted between a calling terminal and a receiving terminal into text. When both the caller using the calling terminal and the callee using the called terminal are users of the voice text service, the call control system provides the calling media processing device and the called terminal corresponding to the calling terminal. A control unit that causes one of the corresponding receiving-side media processing devices to function as a common media processing device is provided. The common media processing device interfaces with a voice recognition engine that converts the voice of the caller or callee into text. The common media processing device acquires the calling side text by inputting the calling side calling voice of the calling party sent from the calling terminal to the voice recognition engine, and sends the calling side text to both the calling terminal and the called terminal. To do. The common media processing device acquires the callee text by inputting the callee voice of the callee sent from the callee terminal to the voice recognition engine, and sends the callee text to both the caller terminal and the callee terminal. To do.

In such an aspect, when both the caller and the callee are users of the voice recognition service, the voices of both the caller and the callee are converted to text through a common media processing device, and The text is sent to both the originating and terminating terminals. Since the common media processing device is used for both the calling side and the called side, the texts of the call contents can be matched between the calling side and the called side.

According to an aspect of the present disclosure, texts of call contents can be matched between the calling side and the called side.

It is a figure showing an example of the whole composition of the call control system concerning an embodiment. It is a figure showing an example of functional composition of some communication control units concerning an embodiment. It is a sequence diagram which shows an example of operation|movement of the call control system which concerns on embodiment. It is a sequence diagram which shows an example of operation|movement of the call control system which concerns on embodiment. It is a sequence diagram which shows an example of operation|movement of the call control system which concerns on embodiment. It is a sequence diagram which shows an example of operation|movement of the call control system which concerns on embodiment. 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 will be denoted by the same reference symbols, without redundant description.

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

In the present 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 voice recognition service). In the present disclosure, the converted text is also referred to as voice text.

FIG. 1 is a diagram showing an overall configuration of a call control system 1 according to an embodiment. The call control system 1 includes an originating network 21 in which an originating terminal 31 is located, a destination network 22 in which an incoming terminal 32 is located, and a core network 10 connecting the originating network 21 and the destination network 22. .. In the call control system 1, a call (communication path) is established by transmitting a control signal between a plurality of devices and terminals, and a call is established by transmitting a data signal indicating voice through the call. It will be possible.

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

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

The core network 10 is a network that forms the core of the call control system 1 and includes various communication control devices. In this embodiment, the core network 10 is an IMS network. The IMS network is a network that uses SIP as a communication protocol and can provide a multimedia service that realizes not only data communication but also voice or moving image real-time communication. In the IMS network, a call is processed by a plurality of communication control devices such as a call session control function (CSCF), an application server (AS), a gateway, and a subscriber management function (HSS: Home Subscriber Server). To be done. The CSCF is a call control device that sets up a call or session or activates a predetermined service. The application server is a device that executes a predetermined supplementary service (for example, a voice text conversion service) and determines whether or not the supplementary service can be executed. The gateway is a device that connects the access network and the core network. The HSS is a device (database) that stores user profiles (subscriber information).

In the present 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 an additional function of calling. The SMS-GW is a type of gateway that connects the core network and other networks, and is a device that provides a short message service (SMS).

FIG. 1 shows a communication control device particularly related to control of a call involving supplementary services, and specifically, a calling side CSCF 11, a called side CSCF 12, a calling side AS 13, a called side AS 14, a calling side MCE 15, a called side MCE 16, The originating side SMS-GW 17 and the destination side SMS-GW 18 are shown.

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

FIG. 1 further shows a calling side Web server 41, a receiving side Web server 42, and a voice recognition engine 43. The calling side Web server 41 and the voice recognition engine 43 constitute a calling side service infrastructure for providing a voice text service to the calling terminal 31. The receiving side Web server 42 and the voice recognition engine 43 constitute a receiving side service infrastructure that provides a voice text service to the receiving terminal 32. The voice recognition engine 43 is a common computer used by both the calling side and the receiving side, and converts voice into text using voice recognition. Both the originating and terminating service infrastructures are provided in a communication network separate from the core network 10. The originating Web server 41 can execute data communication with each of the originating terminal 31, the originating AS 13, and the originating MCE 15. The destination Web server 42 can execute data communication with each of the receiving terminal 32, the destination AS 14, and the destination MCE 16. The voice recognition engine 43 can perform data communication with each of the calling MCE 15 and the receiving MCE 16. The calling terminal 31 can provide a voice text service to the caller by connecting to the calling Web server 41. The receiving terminal 32 can provide a voice text service to the callee by connecting to the receiving side Web server 42.

In this embodiment, the core network 10 further includes 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 voice text service, and is a common database used by both the calling side and the called side. The session database 19 can be accessed by the originating AS 13 and the terminating AS 14.

For example, the session information corresponding to one call includes a session ID, a calling side auxiliary session ID, a called side auxiliary session ID, a subscriber number of the calling terminal 31, a subscriber number of the called terminal 32, a calling end point, a called side. It may include a data item group such as an endpoint and a recognition direction. The session ID is an identifier that uniquely identifies a call (session). The auxiliary session ID is an identifier prepared so that the Web server located outside the core network 10 can uniquely identify the call. The calling side auxiliary session ID is used for the calling side web server 41, and the receiving side auxiliary session ID is used for the receiving side web server 42. The endpoint is an identifier that uniquely identifies the Web server. The originating endpoint uniquely identifies the originating Web server 41, and the destination endpoint uniquely identifies the destination Web server 42. The recognition direction is information indicating to which communication terminal the voice text is transmitted.

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

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

One of the characteristics of the call control system 1 is that, when both the caller and the callee use the voice text conversion service, one of the caller and the callee receives the voice of both the caller and the callee. It is in the point of converting to text. As shown in FIG. 1, even if the voice recognition engine 43 is common to the caller side and the callee side, if the connection to the voice recognition engine 43 is different between the caller side and the callee side, the result of voice recognition may be different. It can be different. For example, the voice text may be different when a certain utterance is input from the originating MCE 15 to the voice recognition engine 43 and when the same utterance is input from the destination MCE 16 to the voice 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 texts of the call contents between the calling side and the called side. The common media processing device transmits the voices of both the caller and the callee to the voice recognition engine 43, and transmits the voice text to both the calling side web server 41 and the receiving side web server 42. FIG. 1 also shows the connections 51, 52 associated with this scheme. Connection 51 is used when the originating MCE 15 functions as a common media processing device in one call (session), and connection 52 is a case where the receiving MCE 16 functions as a common media processing device in one call (session). Used for.

FIG. 2 is a diagram illustrating an example of the functional configuration of the application server. The originating AS 13 includes a service control unit 131, a session control unit 132, and a service scenario unit 133 as functional elements. The service control unit 131 is a functional element that transmits and receives data to and from the originating CSCF 11. 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/receives data to/from each of the originating SMS-GW 17 and the originating Web server 41. When the originating MCE 15 processes the respective voices of the originating side and the destination side, the service scenario unit 133 may send/receive data to/from the destination Web server 42 as well, and the connection 61 in FIG. Indicates communication.

The destination AS 14 includes a service control unit 141, a session control unit 142, and a service scenario unit 143 as functional elements. The service control unit 141 is a functional element that transmits and receives data to and from the destination CSCF 12. 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/receives data to/from each of the destination SMS-GW 18 and the destination Web server 42. When the receiving-side MCE 16 processes the respective voices of the calling-side and the calling-side, the service scenario unit 143 may send/receive data to/from the calling-side Web server 41, and the connection 62 in FIG. Indicates communication.

Both the originating side AS13 and the destination side AS14 control to cause one of the originating side MCE15 and the destination side MCE16 to function as a common media processing device when both the caller and the callee use the voice text service. Section. At the calling side AS 13, at least one of the service control unit 131, the session control unit 132, and the service scenario unit 133 corresponds to the control unit. At the destination AS 14, at least one of the service control unit 141, the session control unit 142, and the service scenario unit 143 corresponds to the control unit.

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

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

First, an example of a process for establishing a call will be described as a process flow S1 with reference to FIG.

In step S101, the calling terminal 31 sends an INVITE message in response to the calling operation of the caller, and the calling side 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 receiving terminal 32. This INVITE message enters the core network 10 via the originating network 21. In the core network 10, the originating CSCF 11 transfers the INVITE message to the originating AS 13.

In step S102, the service control unit 131 activates the voice text service for the calling terminal 31 (caller) in response to the INVITE message. The service control unit 131 accesses the subscriber management function, refers to the subscriber information of the caller, and determines whether the caller has a voice text service contract. When the caller subscribes to the voice text service, the service control unit 131 activates the service. In the present embodiment, it is assumed that the caller is a voice text service contractor. In connection with the activation of the service, the service control unit 131, the session control unit 132, and the service scenario unit 133 cooperate with each other 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 receiving terminal 32 is stored in the session database 19.

In step S103, the service scenario unit 133 sends a push notification to the originating SMS-GW 17, and in step S104, the originating SMS-GW 17 sends a push request to the calling 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 state of the voice text service. When the voice text service can be provided to the caller, the service scenario unit 133 sends a push notification. In this embodiment, it is assumed that the caller is qualified to enjoy the voice text service. The push request includes information necessary for the calling terminal 31 to receive the voice text service from the calling Web server 41 (for example, the device token of the calling terminal 31 and the calling side auxiliary session ID), and the push notification indicates that It contains at least some of the information that makes up the push request.

In step S105, the session control unit 132 transmits an INVITE message to the calling MCE 15 for connection with the calling MCE 15. The calling MCE 15 responds to the INVITE message, executes the process for the voice text service, and then transmits the 200_OK message in step S106. The 200_OK message is a response signal indicating that the process corresponding to the INVITE message has been normally 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 sends an INVITE message to the destination AS 14. The service control unit 131 includes, in the header information of the INVITE message, a calling-side media device ID that is an identifier for uniquely identifying the calling-side MCE 15, and a calling-side service that indicates that the calling-side voice text service is executed. Add information and. Then, the service control unit 131 transmits an INVITE message including the calling-side media device ID and the calling-side service information. This INVITE message reaches the destination AS 14 via the originating CSCF 11 and the destination CSCF 12.

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

In step S109, the service scenario unit 143 sends a push notification to the destination SMS-GW 18, and in step S110, the destination SMS-GW 18 sends a push request to the receiving terminal 32 in response to the push notification. In response to the instruction from the service control unit 141, the service scenario unit 143 accesses the user profile, refers to the user information of the called party, and determines the contract status of the voice text service. When the text-to-speech service can be provided to the call recipient, the service scenario unit 143 sends a push notification. In the present embodiment, it is assumed that the called party is qualified to enjoy the voice text service. The push request includes information necessary for the receiving terminal 32 to receive the voice 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), and the push notification indicates that It contains at least some of the information that makes up the push request.

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

In step S113, the service control unit 141 transmits the INVITE message to the receiving terminal 32. The INVITE message is sent from the callee AS 14 to the callee CSCF 12, and is sent from the callee CSCF 12 to the callee terminal 32 via the callee network 22. When the called terminal 32 receives the INVITE message, the calling process for the called terminal 32 is completed.

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

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

In step S116, the session control unit 132 transmits the 200_OK message to the calling MCE 15. The calling side MCE 15 recognizes that the voice text service is also executed on the called side by referring to the called side media device ID and the called side service information in the 200_OK message. Based on this recognition, the originating MCE 15 provides the voice recognition engine 43 with the voice data from the calling terminal 31 and the voice data from the receiving terminal 32. In this way, the originating AS 13 causes the originating MCE 15 to function as a common media processing device. In step S117, the calling side MCE 15 returns a 200_OK message to the calling side AS 13, and in step S118, the calling side AS 13 transmits the 200_OK message to the calling terminal 31. The 200_OK message reaches the calling terminal 31 via the calling CSCF 11 and the calling network 21.

In step S119, when the calling terminal 31 receives the 200_OK message, a U-Plane (user plane) bus for transmitting a data signal is established between the calling terminal 31 and the called terminal 32. That is, a call is established between the originating terminal 31 and the terminating terminal 32. As a result, a call becomes possible between the calling terminal 31 and the receiving terminal 32.

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

In step S201, the calling terminal 31 transmits a connection request to the calling side Web server 41 to activate an application program for the voice 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 at least a part of the information provided by the push request (for example, the device token of the originating terminal 31, and Calling party auxiliary session ID).

In step S202, a process 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. The originating Web server 41 transmits an authentication request including at least a part of the information provided by the connection request (for example, the device token of the originating terminal 31) to the originating AS 13. The service scenario unit 133 executes the authentication process 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 sends the processing result to the originating Web server 41. In the present embodiment, it is assumed that the sender is authenticated.

In step S203, the transmission terminal 31 activates the application program for the voice text service and transmits the activation signal to the originating Web server 41. The activation signal is a data signal for executing the application program.

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

In step S205, 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. By this registration processing, it becomes possible to transmit the voice text in the currently established call (session) to the calling terminal 31 via the calling side Web server 41.

The same process as steps S201 to S205 is executed on the receiving side. The same processing is shown as steps S211 to S215.

In step S211, the receiving terminal 32 transmits a connection request to the destination Web server 42 to activate the application program for the voice text service. The connection request includes at least a part of the information provided by the push request (for example, the device token of the receiving terminal 32 and the called party auxiliary session ID).

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

In step S213, the receiving terminal 32 activates the application program for the voice text service and transmits the activation signal to the destination Web server 42.

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

In step S215, the service scenario unit 143 of the destination AS 14 registers the destination 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. By this registration processing, it becomes possible to transmit the voice text of the currently established call (session) to the receiving terminal 32 via the destination Web server 42.

On the calling side, steps S206 and S207 are executed after step S205. In step S206, the calling terminal 31 transmits a consent signal indicating that the caller agrees to use the voice text service to the calling-side Web server 41. In step S207, the originating Web server 41 transmits an event notification to the originating AS 13 in response to the consent signal. This event notification indicates the sender's consent. Both of these consent signals and event notifications include 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 a consent signal indicating that the callee agrees to use the voice text service to the destination Web server 42. In step S217, the destination Web server 42 sends an event notification to the originating AS 13 in response to the consent signal. This event notification indicates the recipient's consent. Both of these consent signals and event notifications include the receiving side auxiliary session ID.

In 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 in steps S207 and S217. Specifically, the service scenario unit 133 accesses the session database 19 to identify the session information corresponding to the auxiliary session ID of the calling side or the called 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 “bidirectional” in response to the consent signals transmitted from both the calling terminal 31 and the receiving terminal 32. As a result, as shown in step S220, the voice text service is executed on both the caller side and the callee side.

Next, with reference to FIG. 5, another example of the process of activating the voice text service will be described as a process flow S2A. This example shows a case where the start timing of the voice text service at the communication terminal is different between the calling terminal 31 and the called terminal 32. More specifically, the called terminal 32 outputs a voice after the calling terminal 31. The case where the text service is started is shown.

Also in the processing flow S2A, steps S201 to S207 are executed on the calling side as in the processing flow S2. When the timings of the processes relating to the activation of the application program of the voice text service are significantly different between the calling side and the called side, the calling side executes step S208A after step S207. In step S208A, the service scenario unit 133 sets the recognition direction of the session information (session information corresponding to the calling side auxiliary session ID) corresponding to the established call to "calling side" based on the event notification in step S207. Set to. As a result, as shown in step S221, the voice text service is executed only on the calling terminal 31.

When steps S211 to S217 are executed on the receiving side after step S221, step S208B is executed on the calling side. In 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 called-side auxiliary session ID) to "calling side" based on the event notification in step S217. To "bidirectional". In this way, the service scenario unit 133 sets the recognition direction to “bidirectional” in response to the consent signals transmitted from both the calling terminal 31 and the receiving terminal 32. As a result, as shown in step S222, the voice text service can be executed on both the caller side and the callee side. Step S222 is the same as step S220 in the process flow S2.

Next, with reference to FIG. 6, an example of processing for displaying voice text on the communication terminal will be described as a processing flow S3. The processing flow S3 is based on the premise that the voice text service can be executed on both the calling side (that is, step S220 or S222).

Steps S301 to S309 show a process of converting the voice of the called party (callee voice) into text and displaying the voice text on both the calling terminal 31 and the receiving terminal 32.

In step S301, the voice data (callee voice) sent from the receiving terminal 32 is sent to the core network 10 via the callee network 22, and the callee CSCF12, caller CSCF11, caller AS13, and other communication control devices are activated. It is transmitted to the calling side MCE 15 via. In step S302, the calling MCE 15 transmits the voice data to the voice recognition engine 43. In step S303, the voice recognition engine 43 performs voice recognition on the voice data to convert the destination voice into text, and transmits the voice text to the originating MCE 15. This voice text corresponds to the recipient text.

In step S304, the calling MCE 15 transmits the recognition result including the voice text and the utterance type indicating who is the speaker to the calling Web server 41. Since the voice text indicates the receiving side voice, in the recognition result transmitted in this step, the utterance type indicates the receiving side. In step S305, the originating MCE 15 also transmits the recognition result to the destination Web server 42. The calling MCE 15 acquires the session information corresponding to the current call from the session database 19 via the calling AS 13. In response to the recognition direction of the session information being “bidirectional”, the originating MCE 15 acquires the originating endpoint and the terminating endpoint from the session information. The originating MCE 15 can acquire the transmission destination of the recognition result (that is, the originating Web server 41 and the destination Web server 42) by these endpoints. In this way, the originating MCE 15 sends the destination text to both the originating Web server 41 and the destination Web server 42 in response to the recognition direction being “bidirectional”.

In step S306, the originating Web server 41 sends the recognition result to the originating terminal 31. The calling-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 on the basis of the utterance type included in the recognition result being the receiving side. To do.

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

In step S308, the destination Web server 42 sends the recognition result to the receiving terminal 32. Based on the utterance type included in the recognition result being the receiving side, the receiving side Web server 42 receives the data including the voice text so that the voice text is displayed on the receiving terminal 32 as the recipient's own. To generate.

In step S309, the receiving terminal 32 displays the voice text on the screen as the recipient's own, based on the data. This allows the callee to visually recognize his or her utterance.

Steps S310 to S318 show a process of 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, the voice data (calling side voice) sent from the calling terminal 31 is sent to the core network 10 via the calling side network 21, and is sent to the calling side MCE 15 via the calling side CSCF 11 and the calling side AS13. It In step S311, the originating MCE 15 transmits the voice data to the voice recognition engine 43. In step S312, the voice recognition engine 43 performs voice recognition on the voice data to convert the calling voice into text, and transmits the voice text to the calling MCE 15. This audio text corresponds to the calling text.

In step S313, the calling MCE 15 transmits the recognition result including the voice text and the utterance type indicating who is the speaker to the calling Web server 41. Since the voice text indicates the calling side voice, the utterance type indicates the calling side in the recognition result transmitted in this step. In step S314, the originating MCE 15 also transmits the recognition result to the destination Web server 42. The calling MCE 15 acquires the session information corresponding to the current call from the session database 19 via the calling AS 13. In response to the recognition direction of the session information being “bidirectional”, the originating MCE 15 acquires the originating endpoint and the terminating endpoint from the session information, and thereby the originating Web server 41 and the terminating Web server. The server 42 can be specified. 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 recognition direction being “bidirectional”.

In step S315, the originating Web server 41 sends the recognition result to the originating terminal 31. The calling side Web server 41 processes the data including the voice text so that the voice text is displayed on the calling terminal 31 as the caller's own, based on that the utterance type included in the recognition result is the calling side. To generate.

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

In step S317, the destination Web server 42 sends the recognition result to the receiving terminal 32. Based on the utterance type included in the recognition result being the calling party, 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. To do.

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

In this way, both Web servers set the display mode of voice text based on the utterance type. The method for displaying the voice text as that of the speaker himself or the other party of the call is not limited in any way, 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 voice text balloon) according to the utterance type. For example, the Web server controls the display mode so that the voice text of the speaker himself is displayed on the right side (an example of one side) and the voice text of the call partner is displayed on the left side (an example of the other side). May be. Alternatively, the Web server may change the font of the voice text or the shape of the balloon or the background color depending on the utterance type.

The setting of the display mode of the voice text based on the utterance type may be executed by the transmitting terminal 31 and the receiving terminal 32. Specifically, each of the calling-side Web server 41 and the receiving-side Web server 42 transmits the speech text together with the speech type to the corresponding communication terminal, so that the speech text of the speech text is transmitted to the communication terminal based on the speech type. You may set a display mode. With this mechanism as well, each of the transmitting terminal 31 and the receiving terminal 32 can set the display mode such as the display position, the font, the shape of the balloon, or the background color.

In the present embodiment, the core network 10 is an IMS network, but 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 a part of the functional elements mounted on the calling side AS 13 may be mounted on a communication control device other than the calling side AS 13. Similarly, at least a part of the functional elements mounted on the destination AS 14 may be mounted on a communication control device other than the destination AS 14.

The block diagrams used in the description of the above embodiment show blocks of functional units. These functional blocks (components) are realized by an arbitrary combination of at least one of hardware and software. The method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device physically or logically coupled, or directly or indirectly (for example, two or more devices physically or logically separated). , Wired, wireless, etc.) and may be implemented using these multiple devices. The functional blocks may be realized by combining the one device or the plurality of devices with software.

Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, observation, Broadcasting, notifying, communicating, forwarding, configuration, reconfiguring, allocating, mapping, assigning, etc., but not limited to these. I can't. For example, a functional block (component) that causes transmission to function is called a transmitting unit or a transmitter. In any case, as described above, the implementation method is not particularly limited.

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

In the following description, the word “device” can be read as a circuit, a device, a unit, or the like. The hardware configuration of the communication control device may be configured to include one or a plurality of each device shown in the figure, or may be configured not to include some devices.

For each function in the communication control device, a predetermined software (program) is read on hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs an arithmetic operation to control communication by the communication device 1004 and the memory 1002. Also, it is realized by controlling at least one of reading and writing of data in the storage 1003.

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

Further, the processor 1001 reads a program (program code), a software module, data, and the like into the memory 1002 from at least one of the storage 1003 and the communication device 1004, and executes various processes according to these. As the program, a program that causes a computer to execute at least a part of the operations described in the above-described embodiments is used. For example, each functional element of the communication control device may be realized by a control program stored in the memory 1002 and operating in the processor 1001. Although it has been described that the various processes described above are executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via an electric communication line.

The memory 1002 is a computer-readable recording medium, and is configured by at least one of a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), a RAM (Random Access Memory), and the like. May be done. The memory 1002 may be called a register, a cache, a main memory (main storage device), or the like. The memory 1002 may store an executable program (program code), a software module, etc. for performing the method according to the 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 disc). At least one of a (registered trademark) disk, a smart card, a flash memory (for example, a card, a stick, and a key drive), a floppy (registered trademark) disk, a magnetic strip, or the like. The storage 1003 may be called an auxiliary storage device. The storage medium described above may be, for example, a database including at least one of the memory 1002 and the storage 1003, a server, or another appropriate medium.

The communication device 1004 is hardware (transmission/reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, 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 in order to realize at least one of, for example, frequency division duplex (FDD: Frequency Division Duplex) and time division duplex (TDD). May be composed of

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

Further, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured by using a single bus, or may be configured by using a different bus for each device.

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). Alternatively, a part or all of each functional block may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these hardware.

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

In such an aspect, when both the caller and the callee are users of the voice recognition service, the voices of both the caller and the callee are converted to text through a common media processing device, and The text is sent to both the originating and terminating terminals. Since the common media processing device is used for both the calling side and the called side, the texts of the call contents can be matched between the calling side and the called side.

Also, since both the originating side media processing device and the destination side media processing device are not used, one of them is used, so at least one of the hardware resources and the number of licenses used for executing the voice text service is used. Can be saved. It is also possible to send a message (eg, guidance) related to the voice text service from the common media processing device to both the calling terminal and the called terminal.

In the 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 a certain type of processing is executed is earlier on the calling side than on the receiving side. Therefore, by using the calling-side media processing device as a common media processing device, it is possible to quickly start the processing related to the voice text conversion service, and the voice text conversion service can be provided to the user earlier accordingly. It will be possible.

In the call control system according to another aspect, the control unit transmits a calling-side media processing device that uniquely identifies the calling-side media processing device to the receiving-side media processing device, and receives the calling-side media device ID. The receiving side media processing device receives the receiving side media device ID that uniquely identifies the receiving side media processing device, and in response to the reception of the receiving side media device ID, the calling side media processing device functions as a common media processing device. You may let me. By acquiring the identifiers of the media processing devices on both the calling side and the receiving side, the common media processing device can surely function.

In the call control system according to another aspect, the calling-side media processing device is connected to a calling-side Web server that sends the calling-side text or the called-side text to the calling terminal, and the called-side media processing device causes the calling-side text or the called-side text processing device to be called. You may connect with the receiving side web server which transmits a side text to a receiving terminal. The call control system may further include a database that stores session information including a calling-side endpoint that uniquely specifies the calling-side Web server and a called-side endpoint that uniquely specifies the called-side Web server. The common media processing device acquires the caller endpoint and callee endpoint of the session information, and based on the caller endpoint, sends the caller text or callee text to the caller Web server, The destination text or destination text is received by sending the destination text or destination text to the originating terminal and sending the source text or destination text to the destination Web server based on the destination endpoint. You may transmit toward a terminal. By referring to the endpoint, the Web server to which the text should be transmitted can be specified.

In the call control system according to the other aspect, the control unit responds to the consent signal indicating that the user consents to the use of the voice text service by transmitting the voice text in response to both the originating terminal and the receiving terminal. The recognition direction indicating which communication terminal is transmitted is set to bidirectional, and the common media processing device responds to the bidirectional recognition direction by transmitting the calling side text or the called side text to the calling side web. It may be sent to both the server and the destination Web server. By setting the recognition direction according to the consent of the user, it becomes possible to send the text to both the caller and the callee only when both of them desire the voice text conversion service.

In the call control system according to another aspect, the common media processing device further sets, for each of the calling side text and the called side text, a calling type that indicates whether the calling party is a calling party or a called party. It may be sent to both the server and the destination Web server. By providing the utterance type to the web server, the web server can process the text according to the type of the speaker.

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

By setting the text display mode as described above according to the utterance type on the calling side and the called side, the text can be displayed according to the relationship between the user of the communication terminal and the speaker. The communication terminal displays the voice text of its own user and the voice text of the other party in different display modes, which can contribute to the improvement of the user interface of the voice text service.

In the call control system according to another aspect, when the utterance type indicates the caller, the calling Web server displays the calling text so that the calling text is displayed as the voice text of the speaker on the calling terminal. Is displayed on the first side of the calling terminal and the utterance type indicates the called party, the called side text is displayed on the calling terminal so that the called side text is displayed as the voice text of the other party on the calling terminal. May be displayed on the second side of. When the utterance type indicates the caller, the receiving side Web server displays the calling side text on the receiving side terminal on the first side so that the calling side text is displayed as the voice text of the caller. If the utterance type indicates the called party, the called side text may be displayed on the second side on the called terminal so that the called side text is displayed as the voice text of the calling person on the called terminal. Good.

By setting the display position of the text on each of the calling side and the receiving side as described above according to the utterance type, the text can be displayed according to the relationship between the user of the communication terminal and the utterer. Since the communication terminal displays the voice text of its own user and the voice text of the other party on different sides, it is possible to show the utterance of the user and the utterance of the other person to the caller and the callee in an easy-to-understand manner. ..

In the call control system according to another aspect, the calling side Web server transmits the utterance type together with the calling side text or the called side text to the calling terminal, so that the calling side text or the called side text is transmitted to the calling terminal based on the utterance type. The display mode of the calling side text or the receiving side text is displayed on the receiving terminal based on the utterance type by causing the receiving side Web server to transmit the utterance type together with the calling side text or the receiving side text to the receiving terminal. May be set.

By setting the text display mode as described above according to the utterance type on the calling side and the called side, the text can be displayed according to the relationship between the user of the communication terminal and the speaker. The communication terminal displays the voice text of its own user and the voice text of the other party in different display modes, which can contribute to the improvement of the user interface of the voice text service.

Although the present disclosure has been described in detail above, it is obvious to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modified and changed modes without departing from the spirit and scope of the present disclosure defined by the description of the claims. Therefore, the description of the present disclosure is for the purpose of exemplification, and does not have any restrictive meaning to the present disclosure.

The notification of information is not limited to the aspect/embodiment described in the present disclosure, and may be performed using another method. For example, the information is notified by physical layer signaling (for example, DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (for example, RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, It may be implemented by notification information (MIB (Master Information Block), SIB (System Information Block)), another signal, or a combination thereof. Further, the RRC signaling may be called an RRC message, and may be, for example, an RRC connection setup (RRC Connection Setup) message, an RRC connection reconfiguration message, or the like.

Each aspect/embodiment described in the present disclosure is 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 (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), systems using other suitable systems, and extensions based on these. It may be applied to at least one of the next-generation systems. Also, a plurality of systems may be combined and applied (for example, a combination of at least one of LTE and LTE-A and 5G).

As long as there is no contradiction, the order of the processing procedure, sequence, flowchart, etc. of each aspect/embodiment described in the present disclosure may be changed. For example, the methods described in this disclosure present elements of the various steps in a sample order, and are not limited to the specific order presented.

In the present disclosure, the specific operation performed by the base station may be performed by its upper node in some cases. In a network of one or more network nodes having a base station, the various operations performed for communication with a terminal are the base station and other network nodes other than the base station (eg MME or S-GW and the like are conceivable, but are not limited thereto, and it is clear that at least one of them can be used. Although the case where there is one other network node other than the base station has been illustrated above, a combination of a plurality of other network nodes (for example, MME and S-GW) may be used.

Information and the like can be output from the upper layer (or lower layer) to the lower layer (or upper layer). Input/output may be performed via a plurality of network nodes.

The input/output information and the like may be stored in a specific place (for example, a memory) or may be managed using a management table. Information that is input/output may be overwritten, updated, or added. The output information and the like may be deleted. The input information and the like may be transmitted to another device.

The determination may be performed based on a value represented by 1 bit (whether 0 or 1), may be performed based on a Boolean value (Boolean: true or false), or may be compared by a numerical value (for example, a predetermined value). (Comparison with the value).

Each aspect/embodiment described in the present disclosure may be used alone, may be used in combination, or may be switched according to execution. Further, the notification of the predetermined information (for example, the notification of “being X”) is not limited to the explicit notification, but is performed implicitly (for example, the notification of the predetermined information is not performed). Good.

Software, whether called software, firmware, middleware, microcode, hardware description language, or any other name, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules. , Application, software application, software package, routine, subroutine, object, executable, thread of execution, procedure, function, etc. should be construed broadly.

In addition, software, instructions, information, etc. may be sent and received via a transmission medium. For example, the software uses a website using at least one of wired technology (coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL), etc.) and wireless technology (infrared, microwave, etc.), When sent from a server, or other remote source, at least one of these wired and wireless technologies is included within the definition of transmission medium.

The 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 include voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any of these. May be represented by a combination of

The terms described in the present disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and the symbol may be a signal (signaling). The signal may also be a message. Moreover, a component carrier (CC:Component Carrier) may be called a carrier frequency, a cell, a frequency carrier, or the like.

The terms "system" and "network" used in this disclosure are used interchangeably.

Further, the information, parameters, etc. described in the present disclosure may be represented by using an absolute value, may be represented by using a relative value from a predetermined value, or by using other corresponding information. May be represented. For example, the radio resources may be those indicated by the index.

The names used for the above parameters are not limiting in any way. Further, mathematical formulas and the like using these parameters may differ from those explicitly disclosed in the present disclosure. Since various channels (eg PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are in no way limited names. 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", " The terms "carrier", "component carrier" and the like may be used interchangeably. A base station may be referred to by terms such as macro cell, small cell, femto cell, pico cell, and the like.

A base station can accommodate one or more (eg, three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, each smaller area being defined by a base station subsystem (eg, indoor small base station (RRH: Remote Radio Head) may also be used to provide communication services.The term "cell" or "sector" refers to part or all of the coverage area of a base station and/or a base station subsystem serving communication in this coverage. Refers to.

In this disclosure, terms such as “mobile station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” may be used interchangeably. ..

A mobile station can be 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, by a person skilled in the art. It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, or the like. Note that at least one of the base station and the mobile station may be a device mounted on the mobile body, the mobile body itself, or the like. The moving body may be a vehicle (eg, car, airplane, etc.), an unmanned moving body (eg, drone, self-driving car, etc.), or a robot (manned type or unmanned type). ). At least one of the base station and the mobile station also includes a device that does not necessarily move during a communication operation. 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.

Further, the base station in the present disclosure may be replaced by the user terminal. For example, the communication between the base station and the user terminal is replaced with communication between a plurality of user terminals (eg, may be called D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). Each aspect/embodiment of the present disclosure may be applied to the configuration. In this case, the user terminal may have the function of the base station. In addition, the wording such as “up” and “down” may be replaced with the wording corresponding to the communication between terminals (for example, “side”). For example, the uplink channel and the downlink channel may be replaced with the side channel.

Similarly, the user terminal in the present disclosure may be replaced with the base station. In this case, the base station may have the function of the user terminal.

The terms "determining" and "determining" as used in this disclosure may encompass a wide variety of actions. "Judgment", "decision", for example, judgment (judging), calculation (calculating), calculation (computing), processing (processing), derivation (deriving), investigating (investigating), searching (looking up, search, inquiry) (Eg, searching in a table, a database, or another data structure), considering ascertaining as “judging” or “deciding” may be included. In addition, "decision" and "decision" include receiving (eg, receiving information), transmitting (eg, transmitting information), input (input), output (output), access (accessing) (for example, accessing data in a memory) may be regarded as “judging” and “deciding”. In addition, "judgment" and "decision" are considered to be "judgment" and "decision" when things such as resolving, selecting, choosing, establishing, establishing, and comparing are done. May be included. That is, the “judgment” and “decision” may include considering some action as “judgment” and “decision”. In addition, "determination (decision)" may be read as "assuming," "expecting," "considering," and the like.

The terms "connected," "coupled," or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and It can include the presence of one or more intermediate elements between two elements that are “connected” or “coupled”. The connections or connections between the 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, with at least one of one or more wires, cables and printed electrical connections, and as some non-limiting and non-exhaustive examples. , Can be considered to be “connected” or “coupled” to each other, such as with electromagnetic energy having wavelengths in the microwave and light (both visible and invisible) regions.

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 designations "first," "second," etc. as used in this disclosure does not generally limit the amount or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, references to the first and second elements do not imply that only two elements may be employed or that the first element must precede the second element in any way.

Where the terms “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 exclusive-or.

In this disclosure, where translations add articles, such as a, an, and the in English, the disclosure may include that the noun that follows these articles is in the plural.

In the present disclosure, the term “A and B are different” may mean “A and B are different from each other”. The term may mean that “A and B are different from C”. The terms "remove", "coupled" and the like may be construed as "different" as well.

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... Destination side MCE (end side media processing device), 17... Originating side SMS-GW, 18... Destination side SMS-GW, 19... Session database, 21... Originating network, 22... Destination network, 31... Originating terminal, 32 ... Incoming terminal, 41... Originating Web server, 42... Destination Web server, 43... Voice 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 text service for converting a call transmitted between a calling terminal and a receiving terminal into text,
When both the caller who uses the caller terminal and the caller who uses the callee terminal are users of the text-to-speech service, the calling-side media processing device and callee terminal corresponding to the caller terminal And 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 device is connected to a voice recognition engine that converts the voice of the caller or the callee into text,
The common media processing device is
Acquiring a calling side text by inputting the calling side calling voice of the calling party transmitted from the calling terminal into the voice recognition engine,
Sending the originating text to both the originating and terminating terminals,
By inputting the callee voice of the callee transmitted from the callee terminal to the voice recognition engine, the callee text is acquired,
Sending the destination text to both the originating and terminating terminals,
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,
A sending media device ID that uniquely identifies the calling media processing device is transmitted to the receiving media processing device,
From the destination media processing device that has received the source media device ID, receives a destination media device ID that uniquely identifies the destination media processing device,
Causing the originating media processing device to function as the common media processing device in response to receipt of the destination media device ID,
The call control system according to claim 2. The calling side media processing device is connected to a calling side web server for transmitting the calling side text or the called side text to the calling terminal,
The receiving side media processing device is connected to a receiving side web server for transmitting the calling side text or the receiving side text to the receiving terminal,
The call control system further includes a database that stores session information including a calling endpoint that uniquely identifies the calling Web server and a called endpoint that uniquely specifies the called Web server,
The common media processing device is
Acquiring the originating endpoint and the terminating endpoint of the session information,
Based on the calling end point, by sending the calling side text or the called side text to the calling side web server, the calling side text or the called side text is sent toward 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 sending the calling side text or the called side text to the called terminal.
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 agrees to use the voice text service, transmitted from both the calling terminal and the receiving terminal. Set the recognition direction that indicates whether to
The common media processing device transmits the source text or the destination text to both the source Web server and the destination Web server in response to the recognition direction being bidirectional. ,
The call control system according to claim 4. The common media processing device further sets, for each of the calling-side text and the called-side text, a utterance type indicating whether the utterer is the caller or the callee, to the calling-side Web server and the callee. Sent to both side Web servers,
The call control system according to claim 4 or 5.

Images