Call method, device, electronic equipment, medium and product of voice conversation

Abstract

This application provides a method, apparatus, electronic device, medium, and product for voice conversation calls. The method includes: an MCX proxy server determining a target group from multiple pre-configured groups in an Interworking Function (IWF) whose first attribution information is information of interest; receiving a call request initiated by a first user terminal; and establishing a conversational call channel between the IWF and the Mission-Critical Service (MCX) based on the call request. Then, it receives voice information sent by the first user terminal and sends the voice information to the target group through the established conversational call channel, so that multiple second user terminals in the target group receive the voice information. This method, through the MCX proxy server, requires only one conversation between the IWF and the MCX to send voice information to multiple terminals, reducing bandwidth and conversation resource consumption.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, electronic device, medium and product for voice conversation. Background Technology

[0002] With the rapid development of communication technology, voice conversations have become particularly important for interoperability between groups of systems, including Mission Critical X (MCX) systems and Interworking Function (IWF) systems.

[0003] In related technologies, when a large number of user group calls are established, the IWF needs to initiate a call to each MCX user terminal to establish a session call channel corresponding to the number of MCX user terminals. The voice information transmitted in each session call channel is the same.

[0004] However, the above method results in redundant session paths between IWF and MCX, and consumes a lot of bandwidth and session resources. Summary of the Invention

[0005] This application provides methods, apparatus, electronic devices, media, and products for voice conversations, which aim to reduce the number of conversation paths between the IWF and MCX, and reduce bandwidth and conversation resource consumption.

[0006] In a first aspect, embodiments of this application provide a method for making a voice session, applied to a mission-critical service MCX proxy server, including:

[0007] From multiple pre-configured groups in the Interworking Function (IWF), the target group whose first attribution information is information of interest is determined, wherein the first attribution information includes information of interest or information of no interest;

[0008] Receive a call request initiated by a first user terminal, which is an Interworking Function (IWF) user terminal or a Mission-critical Service (MCX) user terminal.

[0009] Based on the call request, establish a session call channel between the Interworking Function (IWF) and the Mission-Critical Service (MCX);

[0010] Receive voice information sent by the first user terminal;

[0011] The voice information is sent to the target group through the session call channel so that multiple second user terminals in the target group receive the voice information.

[0012] In one possible implementation, determining the target group from a plurality of pre-configured groups in the Interworking Function (IWF) where the first attribution information is information of interest includes:

[0013] Subscribe to multiple pre-configured groups in the Interworking Function (IWF) to obtain the second attribution information of each subscribed group, which includes information of interest or information of no interest.

[0014] Receive requests from the MCX user terminal of the mission-critical service for changes in interest in different groups;

[0015] Based on the interest change requests from the different groups, the target group whose first affiliation information is the information of interest is determined from the subscribed groups.

[0016] In one possible implementation, subscribing to multiple pre-configured groups in the Interworking Function (IWF) to obtain the second affiliation information of each subscribed group includes:

[0017] Send subscription requests to multiple pre-configured groups in the Interoperability Function (IWF);

[0018] Receive corresponding first notification information sent by multiple pre-configured groups in the Interworking Function (IWF);

[0019] For any group's first notification message, if the first notification message carries a first indication message to indicate successful subscription, then the subscription to the group is successful, and the second affiliation information corresponding to the group is obtained.

[0020] In one possible implementation, determining the target group from the subscribed groups whose first affiliation information is the information of interest based on the interest change requests from the different groups includes:

[0021] Receive interest change requests sent by the MCX user terminal of the mission-critical service;

[0022] Send the interest change request to multiple subscribed groups belonging to the Interworking Function IWF;

[0023] Receive corresponding second notification information sent by multiple subscribed groups belonging to the Interworking Function (IWF);

[0024] For any group's second notification information, if the second notification information carries second indication information for indicating that the first attribution information is information of interest, then the group is the target group.

[0025] In one possible implementation, establishing a session call channel between the Interoperability Function (IWF) and the Mission-Critical Service (MCX) based on the call request includes:

[0026] Based on the call request, configure the response status and voice service playback.

[0027] Based on the response status configuration and the voice service playback configuration, a session call channel is established between the Interoperability Function (IWF) and the Mission-Critical Service (MCX).

[0028] In one possible implementation, sending the voice information to the target group through the session call channel includes:

[0029] The voice information is sent to the target group via the session call channel in a multicast or unicast manner.

[0030] Secondly, embodiments of this application provide a voice session calling device applied to a mission-critical service MCX proxy server, comprising:

[0031] The determination module is used to determine, from multiple groups pre-configured in the Interworking Function (IWF), the target group whose first attribution information is information of interest, wherein the first attribution information includes information of interest or information of no interest;

[0032] The receiving module is used to receive a call request initiated by a first user terminal, which is an Interworking Function (IWF) user terminal or a Mission-critical Service (MCX) user terminal.

[0033] The module is used to establish a session call channel between the Interworking Function (IWF) and the Mission-Critical Service (MCX) based on the call request.

[0034] The receiving module is also used to receive voice information sent by the first user terminal;

[0035] The sending module is used to send the voice information to the target group through the session call channel, so that multiple second user terminals in the target group can receive the voice information.

[0036] Thirdly, embodiments of this application provide an electronic device, including: a memory and a processor;

[0037] The memory stores computer-executed instructions;

[0038] The processor executes computer execution instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0039] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible implementations of the first aspect.

[0040] Fifthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0041] The voice session calling method, apparatus, electronic device, medium, and product provided in this application are applied to a mission-critical service MCX proxy server. The mission-critical service MCX proxy server determines a target group from multiple pre-configured groups in the Interoperability Function (IWF) where the first attribution information includes either information of interest or information of no interest. It receives a call request initiated by a first user terminal, which may be an IWF user terminal or a mission-critical service MCX user terminal, and establishes a session call channel between the IWF and the MCX based on the call request. It then receives voice information sent by the first user terminal and transmits the voice information to the target group through the established session call channel, so that multiple second user terminals in the target group receive the voice information. The method of this application, through the MCX proxy server, requires only one session to be established between the IWF and the MCX to send voice information to multiple terminals, reducing bandwidth and session resource consumption. Attached Figure Description

[0042] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0043] Figure 1 A schematic diagram of a voice conversation call scenario provided in an embodiment of this application;

[0044] Figure 2 A flowchart illustrating a voice conversation calling method provided in an embodiment of this application;

[0045] Figure 3 A schematic diagram of an IWF interface provided for an embodiment of this application;

[0046] Figure 4 A flowchart illustrating a method for subscribing to multiple pre-configured groups in an Interworking Function (IWF) provided in this application embodiment;

[0047] Figure 5A signaling diagram illustrating the subscription of multiple pre-configured groups in the Interworking Function (IWF) provided in this application embodiment;

[0048] Figure 6 A flowchart illustrating a method for determining a target group from subscribed groups, provided as an embodiment of this application;

[0049] Figure 7 A signaling diagram illustrating the identification of a target group from subscribed groups, provided as an embodiment of this application;

[0050] Figure 8 A signaling diagram illustrating an IWF user terminal initiating a group call, provided as an embodiment of this application;

[0051] Figure 9 A signaling diagram illustrating an MCX user terminal initiating a group call, provided in an embodiment of this application;

[0052] Figure 10 A schematic diagram of the structure of a voice conversation calling device provided in an embodiment of this application;

[0053] Figure 11 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0054] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0055] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0056] In the description of the embodiments of this application, the terms "inner" and "outer", etc., which indicate the direction or positional relationship, are based on the direction or positional relationship shown in the drawings. This is only for the convenience of description and is not intended to indicate or imply that the device or component must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, it should not be construed as a limitation of this application.

[0057] In the description of the embodiments of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Furthermore, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which needs to be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0058] In the description of the embodiments of this application, unless otherwise expressly specified and limited, the terms "connected" and "linked" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in the embodiments of this application according to the specific circumstances.

[0059] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0060] The MCX protocol defines the interface and protocol between the MCX and IWF for cross-system group interoperability. There are two types of cross-system groups: groups belonging to the MCX and groups belonging to the IWF. Groups belonging to the MCX are controlled by the MCX, while groups belonging to the IWF are controlled by the IWF. Control functions can include group configuration and decision-making regarding call rights. User terminals in groups belonging to the MCX can be broadband users, while user terminals in groups belonging to the IWF can be narrowband users.

[0061] In the existing technology, taking the MCX user terminal as an example, when a large number of MCX user terminal group calls are established, the IWF needs to initiate a call to each MCX user terminal to establish multiple session call channels corresponding to the number of MCX user terminals.

[0062] However, in reality, the main speaker voice information transmitted in each session call channel is the same, resulting in redundancy in the number of session paths between the IWF and MCX. For both the MCX and IWF, there are specifications (quantities) limitations on the number of concurrent voice paths they support, and the above method results in a large consumption of bandwidth and session resources for voice transmission.

[0063] Therefore, in response to the aforementioned technical problems in the prior art, the inventors discovered during their research that, for groups belonging to the IWF, by subscribing to MCX agent users (i.e., MCX agent servers), when a call is established, only one session call channel needs to be established through the MCX agent server. Then, multiple real users within the MCX agent server make calls, thereby calling a large number of MCX user terminals. Specifically, from multiple groups pre-configured in the IWF, a target group with the first attribution information of interest is determined. A call request initiated by a first user terminal is received. Based on the call request, a session call channel is established between the IWF and the mission-critical service MCX. Voice information sent by the first user terminal is received and transmitted to the target group through the aforementioned session call channel, so that multiple second user terminals in the target group receive the voice information. Based on this, this application proposes a method, apparatus, electronic device, medium, and product for voice session calling.

[0064] To facilitate understanding of this application, the following is provided: Figure 1 The application scenarios of this application are illustrated by example. Figure 1 This is a schematic diagram of a voice conversation call scenario provided in an embodiment of this application, such as... Figure 1 As shown, the specific application scenario of this application may include: user terminal 01, MCX proxy server 02 and group 03. Group 03 includes multiple real user terminals 031, which are used to receive the main voice information sent by user terminal 01.

[0065] Specifically, MCX proxy server 02 determines the target group for receiving the main voice information from multiple pre-configured groups in the Interoperability Function (IWF). MCX proxy server 02 receives a call request from user terminal 01 and establishes a session call path for itself. It then transmits the main voice information from user terminal 01 to group 03 through this established session call path, enabling multiple real user terminals 031 in group 03 to receive the main voice information.

[0066] It is understood that this application does not limit the type of user terminal, which includes, but is not limited to, various devices with voice transmission and reception functions, such as smartphones, laptops, tablets, and wearable devices. This application also does not limit the number of user terminals, which can be determined based on actual circumstances.

[0067] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0068] Figure 2 A flowchart illustrating a voice session calling method provided in an embodiment of this application is shown below. Figure 2 As shown, the executing entity of this method can be a device for making a voice session call, which can be implemented by a computer program; it can also be implemented by a medium storing the relevant computer program, such as a USB flash drive and / or optical disc, or it can be implemented by a physical device that integrates or installs the relevant computer program, such as a chip or electronic device, where the electronic device can be an MCX proxy server, etc. The method includes:

[0069] S201. From multiple groups pre-configured in the Interoperability Function (IWF), determine the target group whose first attribution information is information of interest. The first attribution information includes information of interest or information of no interest.

[0070] Please see Figure 3 , Figure 3 This is a schematic diagram of an IWF interface provided for an embodiment of the present application, including an IWF-1 interface, an IWF-2 interface and an IWF-3 interface.

[0071] The IWF-1 interface corresponds to the Mission Critical Push-To-Talk Server (MCPTT server), which can be used for call management. The IWF-2 interface corresponds to the storage server (MCData server). The IWF-3 interface corresponds to the Common Services Core, which includes, but is not limited to: Group management server, Configuration management server, Identify management server, Key management server, and Location management server.

[0072] In this embodiment, the target group's main service is voice service, and the interface involved in the IWF is the IWF-1 interface.

[0073] In this embodiment, before proceeding with the steps, it is necessary to first configure the groups belonging to IWF.

[0074] Optionally, the MCX proxy server marks user terminals belonging to a first preset range field as MCX user terminals belonging to an IWF group based on the unique identifier field of the actual user terminal, thus obtaining an IWF group. Users in this group can be narrowband users. The IWF configures this IWF group, and the subscriber to the MCX proxy server becomes an MCX proxy user. Correspondingly, it can also mark user terminals belonging to an MCX group based on the unique identifier field of the actual user terminal.

[0075] The MCX proxy server first subscribes to multiple pre-configured groups in the IWF, and then identifies the target group from among the subscribed groups.

[0076] Optionally, multiple pre-configured groups in the Interoperability Function (IWF) are subscribed to, obtaining second attribution information for each subscribed group. This second attribution information includes information of interest or information of no interest. The system receives interest change requests for different groups from the MCX user terminal and, based on these requests, determines the target groups from the subscribed groups whose first attribution information is of interest. For specific implementation details, please refer to the following embodiments.

[0077] S202, Receive a call request initiated by the first user terminal.

[0078] In this embodiment, the first user terminal is an Interoperability Function (IWF) user terminal or a Mission-Critical Service (MCX) user terminal.

[0079] The MCX proxy server receives call requests initiated by IWF user terminals or MCX user terminals, which are used to initiate voice services.

[0080] S203. Based on the call request, establish a session call channel between the Interoperability Function (IWF) and the Mission-Critical Service (MCX).

[0081] One possible implementation is:

[0082] Based on the call request, the MCX proxy server configures the response status and voice service playback. Then, based on these configurations, it establishes a session call channel between the Interoperability Function (IWF) and the Mission-Critical Service (MCX).

[0083] S204. Receive voice information sent by the first user terminal.

[0084] The MCX proxy server receives the main voice information sent by the IWF user terminal or the MCX user terminal.

[0085] S205. Send the voice information to the target group through the session call channel so that multiple second user terminals in the target group can receive the voice information.

[0086] The MCX proxy server establishes a session call channel between the Interoperability Function IWF and the Mission-Critical Service MCX through the above steps, and sends the main voice information sent by the IWF user terminal or the MCX user terminal to the target group in a unicast or multicast manner.

[0087] The target group includes multiple real user terminals. These real user terminals can obtain the speaker voice information sent by the IWF user terminal or the MCX user terminal through the aforementioned session call channel.

[0088] In the above embodiments of this application, the Mission Critical Service (MCX) proxy server determines a target group from multiple pre-configured groups in the Interworking Function (IWF) whose first attribution information is information of interest. The first attribution information includes information of interest or information of no interest. It receives a call request initiated by a first user terminal, which may be an IWF user terminal or a Mission Critical Service (MCX) user terminal, and establishes a session call channel between the IWF and the MCX based on the call request. Then, it receives voice information sent by the first user terminal and sends the voice information to the target group through the established session call channel, so that multiple second user terminals in the target group receive the voice information. In this embodiment, the method, through the MCX proxy server, only requires establishing one session between the IWF and the MCX to send voice information to multiple terminals, reducing bandwidth and session resource consumption during voice information transmission.

[0089] Furthermore, based on the above embodiments, the following embodiments illustrate the process of subscribing to multiple pre-configured groups in the Interworking Function (IWF).

[0090] Please see Figure 4 , Figure 4 A flowchart illustrating a method for subscribing to multiple pre-configured groups in an Interworking Function (IWF) provided in this application embodiment is shown. The method includes the following steps:

[0091] S401. Send subscription requests to multiple pre-configured groups in the Interworking Function (IWF).

[0092] Figure 5 A signaling diagram illustrating the subscription to multiple pre-configured groups in the Interworking Function (IWF) provided in this application embodiment is shown below. Figure 5 As shown, the following is based on Figure 5 right Figure 4 The proposed solution will be introduced below.

[0093] The MCX user terminal initiates a subscription request (SIP SUBSCRIBE). Once the MCX proxy server starts, it automatically subscribes to all attachment affiliation information belonging to groups within the IWF in the name of the MCX proxy user.

[0094] Specifically, the MCX proxy server sends subscription requests to each IWF group individually. When the MCX proxy server adds a new group belonging to IWF, it can automatically initiate a subscription request for that new group.

[0095] S402, Receive the corresponding first notification information sent by multiple pre-configured groups in the Interworking Function (IWF).

[0096] The IWF group responds to the subscription request sent by the MCX proxy server by sending a subscription request response SIP SUBSCRIBE RSP to the MCX proxy server.

[0097] Optionally, the MCX proxy server receives the 200 OK status code returned by each group in the IWF. When the MCX proxy server receives 200 OK, it means that the subscription request has been successfully received by the IWF, and it waits for the first notification NOTIFY information, i.e., SIP NOTIFY, to be returned by the IWF.

[0098] After receiving the first NOTIFY message, the MCX proxy server sends a SIPNOTIFY RSP response to the IWF to indicate that it has received the message.

[0099] S403. For any group's first notification information, if the first notification information carries a first indication information to indicate successful subscription, then the group subscription is successful, and the second attribution information corresponding to the group is obtained.

[0100] For the first notification message to any group, the NOTIFY message carries the first instruction information.

[0101] The first indication information includes, but is not limited to: entity status information application / pidf+xml MIME body and identification information. Identification information includes, but is not limited to: the group ID, the ID of the MCX user terminal that sent the subscription request, and the expiration time information expires.

[0102] If the MCX proxy server receives the first instruction information mentioned above and the expires have not expired, the MCX proxy server successfully subscribes to the group, and the second affiliation information corresponding to the group is the information of interest, i.e., the attachment.

[0103] If the first instruction information received by the MCX proxy server is missing either the group ID or the ID of the MCX user terminal that sent the subscription request, or if the expires is the current or previous time, then the second affiliation information corresponding to that group is not of interest, i.e., no deaffiliation is attached.

[0104] The MCX proxy server sends a SIP SUBSCRIBERSP response to the MCX user terminal indicating that the group has subscribed, and also sends a SIP NOTIFY message to the MCX user terminal. The MCX user terminal sends a SIP NOTIFY RSP response to the MCX proxy server, indicating that it has received the notification.

[0105] In the above embodiments of this application, the MCX proxy server sends subscription requests to multiple pre-configured groups in the Interoperability Function (IWF) and receives corresponding first notification information from these groups. For any group's first notification information, if the first notification information carries first indication information indicating successful subscription, then the group subscription is successful, and the second affiliation information corresponding to the group is obtained. This embodiment's method, by subscribing to groups belonging to the IWF through the MCX proxy server, enables the management of IWF groups solely through the MCX proxy user.

[0106] Furthermore, based on the above embodiments, the following embodiments illustrate the process of determining the target group whose first attribution information is the information of interest from the subscribed groups according to the interest change requests of different groups.

[0107] Please see Figure 6 , Figure 6 A flowchart illustrating a method for determining a target group from subscribed groups, provided for embodiments of this application, includes the following steps:

[0108] S601, Receive interest change request sent by the critical mission service MCX user terminal.

[0109] Figure 7 A signaling diagram illustrating the identification of a target group from subscribed groups, as provided in this application embodiment, is shown below. Figure 7 As shown, the following is based on Figure 7 right Figure 6 The proposed solution will be introduced below.

[0110] When an MCX user terminal is set to be interested in at least one group belonging to the IWF, the MCX user terminal can send an interest change request, i.e., an update request (SIP PUBLISH), to the MCX proxy server. "Interested" indicates that the group can receive and initiate group voice services, while "not interested" indicates that the group cannot receive or initiate group voice services.

[0111] A change of interest request can be either an affiliation request or a deaffiliation request.

[0112] S602. Send interest change requests to multiple subscribed groups belonging to the Interoperability Function (IWF).

[0113] After receiving the data, the MCX proxy server counts the groups of interest in this PUBLISH update and makes a judgment for each group to exclude MCX proxy users. Optionally, an MCX user may change from being deaffiliated to being affiliated, or from having only one affiliated MCX user to being deaffiliated.

[0114] If any of the above conditions are met, the MCX proxy server sends PUBLISH requests (i.e., SIP PUBLISH) to multiple subscribed groups belonging to the Interoperability Function (IWF) on a group-by-group basis.

[0115] Optionally, PUBLISH may include, but is not limited to, group ID, MCPPT ID of the MCX proxy server, ID of the MCX user terminal, and affiliation or deaffiliation value information.

[0116] S603, Receive corresponding second notification information sent by multiple subscribed groups belonging to the Interworking Function (IWF).

[0117] The IWF group responds to the PUBLISH request sent by the MCX proxy server by sending an update request response SIP SUBSCRIBE RSP to the MCX proxy server, and the MCX proxy server sends an update request response SIPSUBSCRIBE RSP to the MCX user terminal.

[0118] Optionally, the MCX proxy server receives the 200 OK status code returned by each group in the IWF. Upon receiving 200 OK, the MCX proxy server indicates that the PUBLISH request has been successfully received by the IWF, and it awaits the second notification information (SIP SUBSCRIBE RSP) returned by the IWF. After receiving the SIP SUBSCRIBE RSP, the MCX proxy server sends the SIP SUBSCRIBE RSP to the MCX user terminal.

[0119] S604. For any group's second notification information, if the second notification information carries second indication information for indicating that the first attribution information is information of interest, then the group is the target group.

[0120] For any group's second notification message, the NOTIFY message carries a second instruction message.

[0121] The second indication information includes, but is not limited to: entity status information application / pidf+xml MIME body and identification information. Identification information includes, but is not limited to: the group ID, the ID of the MCX user terminal that sent the PUBLISH request, and the expiration time information expires.

[0122] If the MCX proxy server receives the second instruction information mentioned above and the expires have not expired, the MCX proxy server will successfully update the group. The first attribution information corresponding to the group is the information of interest, i.e., the attached affiliation, and the group is the target group.

[0123] If the second instruction information received by the MCX proxy server is missing either the group ID or the ID of the MCX user terminal that sent the PUBLISH request, or if the expires is the current or previous time, then the first affiliation information corresponding to that group is not of interest, i.e. no deaffiliation is attached, and that group is not the target group.

[0124] The MCX proxy server needs to wait until it receives all the NOTIFY messages from the PUBLISH server sent to the IWF, and then, after considering the group affiliation status of the local MCX and the IWF, it replies with a NOTIFY message to the MCX user terminal. The MCX proxy server needs to start a timer, assuming a default of 3 seconds (configurable internally). If it hasn't received all the NOTIFY messages from the IWF by the timeout, the timed-out group NOTIFY is considered failed, and the group affiliation status is assumed to remain unchanged. If a NOTIFY message is received subsequently, the status is refreshed before sending another NOTIFY message to the MCX user terminal.

[0125] The notification message SIP NOTIFY can be either SIP NOTIFY(affliating) or SIP NOTIFY(affliated). Upon receiving the SIP NOTIFY, the MCX proxy server sends a notification message response SIP NOTIFYRSP to the IWF, indicating receipt. It then sends a notification message response SIP NOTIFY(affliating) or SIPNOTIFY(affliated) to the MCX user terminal. Upon receiving this, the MCX user terminal sends a notification message response SIP NOTIFYRSP to the MCX proxy server, indicating receipt.

[0126] In the above embodiments of this application, the MCX proxy server receives an interest change request sent by a mission-critical service MCX user terminal, sends the interest change request to multiple subscribed groups belonging to the Interoperability Function (IWF), and receives corresponding second notification information sent by the multiple subscribed groups belonging to the IWF. For any group's second notification information, if the second notification information carries second indication information indicating that the first attribution information is information of interest, then the group is the target group. The method of this embodiment determines the target groups of interest from the subscribed groups belonging to the IWF through the MCX proxy server, enabling the management of target groups of interest in the IWF to be achieved solely through the MCX proxy user.

[0127] Furthermore, the following embodiment illustrates the calling method for a voice session when an IWF user terminal initiates a group call, wherein the group of calls belongs to the IWF. Please refer to [link / reference]. Figure 8 , Figure 8 A signaling diagram illustrating an IWF user terminal initiating a group call, provided in an embodiment of this application, includes:

[0128] When an IWF user terminal initiates a group call, the IWF user terminal can be a narrowband user terminal. As the group master, the IWF can determine the list of attached users in the group. When it finds an MCX agent server (i.e., an MCX agent user), it sends a call request (INVITE message) to the MCX agent server to invite the MCX agent server to join the group call.

[0129] Optionally, the INVITE message may include, but is not limited to, the configured header field information, format information, and the called user terminal's MCPTT ID, group ID, and other configuration information, wherein the aforementioned format information may be application / vnd.3gpp.mcptt-info+xml MIME body.

[0130] After receiving the INVITE message, the MCX proxy server sends the Session Progress response code (SIP 183) to the IWF control server, configures the response status P-Answer-State to "Unconfirmed", and configures relevant information for voice service playback, such as configuring the identity information P-Asserted-Identity to the P server's Public Service Identity (PSI).

[0131] The MCX proxy server replies to the IWF with a 200 OK status code indicating that the INVITE request has been successfully processed. Simultaneously, it initiates an on-demand unicast, pre-establishing a unicast or multicast session call channel. This channel serves as the uplink channel for the main speaker and the downlink channel for the group. Even if the main speaker changes, the uplink voice stream can still be sent to the IWF through this session call channel. It's important to note that when other MCX user terminals request talk time, a separate uplink session call channel from the MCX to the IWF must be established, as the IWF cannot recognize other MCX user terminals and the connection will fail. If no user terminal is listening in the MCX, the MCX proxy server will not release the session call channel.

[0132] After receiving the 200 OK, the IWF user terminal begins to send voice information (voice stream). The MCX proxy server obtains the voice information and sends it to the target group through the established session call channel, so that multiple second user terminals, i.e., MCX user terminals in the target group, can receive the voice information.

[0133] After receiving 200 OK, the IWF user terminal will also send a FLOOR TAKEN message when sending voice information to the MCX proxy server. Correspondingly, the MCX proxy server will obtain the FLOOR TAKEN message and send it to the target group through the established session call channel, so that multiple second user terminals in the target group, i.e., MCX user terminals, can receive the call cancellation information.

[0134] In the above embodiments of this application, when the MCX proxy server receives a call request initiated by an IWF user terminal, it establishes a session call channel between the IWF user terminal and the target group to which the call belongs. The voice information sent by the IWF user terminal can be sent to multiple MCX user terminals through only one session call channel, so that multiple MCX user terminals can receive voice information by sharing one session call channel, thereby reducing the consumption of bandwidth and session resources.

[0135] Furthermore, the following embodiment illustrates the calling method for a voice session when an MCX user terminal initiates a group call, wherein the group of the call belongs to the IWF. Please refer to [link / reference]. Figure 9 , Figure 9 A signaling diagram illustrating a group call initiated by an MCX user terminal, provided in an embodiment of this application, includes:

[0136] When an MCX user terminal initiates a group call, the MCX proxy server receives the call request (INVITE message) and sends the INVITE message to the IWF.

[0137] As the group controller, the IWF can determine the list of attached users in the group. When it finds an MCX agent server (i.e., an MCX agent user), it sends a call request (INVITE message) to the MCX agent server to invite it to join the group call.

[0138] Optionally, the INVITE message may include, but is not limited to, the configured header field information, format information, and the MCPTT CLIENT ID of the MCX user terminal that initiated the call, the ID of the MCX proxy server, the group ID, and other configuration information. The format information mentioned above may be application / vnd.3gpp.mcptt-info+xml MIME bod.

[0139] The IWF replies to the MCX proxy server with a 200 OK status code indicating that the INVITE has been successfully processed. The MCX proxy server then sends the 200 OK status code to the MCX user terminal. The IWF also sends configuration information to the MCX proxy server, including the P-Answer-State header field with the value "Unconfirmed" and Session Description Protocol (SDP) information. The SDP includes "mc_granted" for the calling party, indicating that talk rights are granted. Simultaneously, it sends a Floor Granted message to the MCX proxy server to grant speaking permissions. The MCX proxy server then sends the Floor Granted speaking permission to the MCX user terminal, which begins sending voice information (voice stream) to the IWF.

[0140] It is important to note that when the MCX proxy server sends a 200 OK or Floor Granted message to the MCX user terminal, it cannot send it directly. The information must be assembled from the above information. The relevant information of the MCX proxy server cannot be sent directly to the MCX user terminal.

[0141] The MCX proxy server simultaneously performs on-demand unicast, pre-establishing unicast or multicast session call channels. These channels serve as the uplink for the main speaker and the downlink for the group. Even if the main speaker changes, the uplink voice stream can still be sent to the IWF through these channels. It's important to note that when other MCX user terminals request talk time, a separate uplink session call channel from the MCX to the IWF must be established, as the IWF cannot recognize other MCX user terminals and the connection will fail. If no user terminal is listening in the MCX, the MCX proxy server will not release the session call channel.

[0142] After receiving the voice information, the IWF sends the voice information and FLOOR TAKEN to the MCX proxy server through the established session call channel between the IWF and the MCX. After obtaining the voice information and FLOOR TAKEN, the MCX proxy server sends them to the target group through the established session call channel, so that multiple second user terminals in the target group, i.e., MCX user terminals, can receive the voice information.

[0143] After receiving 200 OK, the IWF user terminal will also send a FLOOR TAKEN message when sending voice information to the MCX proxy server. Correspondingly, the MCX proxy server will obtain the FLOOR TAKEN message and send it to the target group through the established session call channel, so that multiple second user terminals in the target group, i.e., MCX user terminals, can receive the call cancellation information.

[0144] In the above embodiments of this application, when the MCX proxy server receives a call request initiated by an MCX user terminal, it establishes a session call channel between the MCX user terminal and the target group of the call belonging to the IWF. The voice information sent by the MCX user terminal can be sent to multiple MCX user terminals through only one session call channel, so that multiple MCX user terminals can receive voice information by sharing one session call channel, thereby reducing the consumption of bandwidth and session resources.

[0145] Figure 10 This application provides a schematic diagram of the structure of a voice session calling device, applied to a mission-critical service MCX proxy server, such as... Figure 10 As shown, the voice session calling device provided in this embodiment includes:

[0146] The determination module 1001 is used to determine the target group from multiple pre-configured groups in the Interworking Function (IWF) whose first attribution information is information of interest. The first attribution information includes information of interest or information of no interest.

[0147] The receiving module 1002 is used to receive a call request initiated by a first user terminal, which is either an Interworking Function (IWF) user terminal or a Mission-Critical Service (MCX) user terminal.

[0148] Establishment module 1003 is used to establish a session call channel between the Interoperability Function (IWF) and the Mission-Critical Service (MCX) based on a call request.

[0149] The receiving module 1002 is also used to receive voice information sent by the first user terminal.

[0150] The sending module 1004 is used to send voice information to a target group through a session call channel so that multiple second user terminals in the target group can receive the voice information.

[0151] One possible implementation is to determine module 1001, specifically for:

[0152] From multiple pre-configured groups in the Interoperability Function (IWF), the target group whose first attribution information is information of interest is determined. The first attribution information includes information of interest or information of no interest.

[0153] Receive a call request initiated by a first user terminal, which is either an IWF user terminal or a mission-critical service MCX user terminal.

[0154] Based on the call request, establish a session call channel between the Interoperability Function (IWF) and the Mission-Critical Service (MCX).

[0155] Receive voice information sent by the first user terminal.

[0156] Voice information is sent to the target group through a session call channel so that multiple second user terminals in the target group can receive the voice information.

[0157] One possible implementation is to determine module 1001, which is further specifically used for:

[0158] Send subscription requests to multiple pre-configured groups in the Interoperability Function (IWF).

[0159] Receive the first notification information sent by multiple pre-configured groups in the Interworking Function (IWF).

[0160] For any group's first notification message, if the first notification message carries a first indication message to indicate successful subscription, then the group subscription is successful, and the corresponding second attribution information for the group is obtained.

[0161] One possible implementation is to determine module 1001, which is further specifically used for:

[0162] Receive interest change requests sent by the MCX user terminal of the mission-critical service.

[0163] Send interest change requests to multiple subscribed groups belonging to the Interoperability Function (IWF).

[0164] Receive corresponding second notification messages from multiple subscribed groups belonging to the Interoperability Function (IWF).

[0165] For any group's second notification message, if the second notification message carries a second indication message for indicating that the first attribution information is information of interest, then the group is the target group.

[0166] One possible implementation is to create module 1003, specifically for:

[0167] Configure the response status and voice service playback based on the call request.

[0168] Based on the response status configuration and voice service playback configuration, establish a session call channel between the Interoperability Function (IWF) and the Mission-Critical Service (MCX).

[0169] One possible implementation is that the sending module 1004 is specifically used for:

[0170] Voice messages are sent to the target group via multicast or unicast through a session call channel.

[0171] The voice session call provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0172] Figure 11 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application, such as... Figure 11 As shown, the electronic device 110 provided in this embodiment includes at least one processor 1101 and a memory 1102. Optionally, the device 110 further includes a communication component 1103. The processor 1101, the memory 1102, and the communication component 1103 are connected via a bus 1104.

[0173] In a specific implementation, at least one processor 1101 executes computer execution instructions stored in memory 1102, causing at least one processor 1101 to perform the above-described method.

[0174] The specific implementation process of processor 1101 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0175] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0176] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0177] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0178] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0179] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0180] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0181] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0182] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0183] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0184] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0185] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0186] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0187] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A method for making a voice conversation, characterized in that, Applications include the mission-critical service MCX proxy server, including: From multiple pre-configured groups in the Interworking Function (IWF), the target group whose first attribution information is information of interest is determined, wherein the first attribution information includes information of interest or information of no interest; Receive a call request initiated by a first user terminal, which is an Interworking Function (IWF) user terminal or a Mission-critical Service (MCX) user terminal. Based on the call request, establish a session call channel between the Interworking Function (IWF) and the Mission-Critical Service (MCX); Receive voice information sent by the first user terminal; The voice information is sent to the target group through the session call channel so that multiple second user terminals in the target group receive the voice information.

2. The method according to claim 1, characterized in that, The step of determining the target group whose first attribution information is information of interest from multiple pre-configured groups in the Interworking Function (IWF) includes: Subscribe to multiple pre-configured groups in the Interworking Function (IWF) to obtain the second attribution information of each subscribed group, which includes information of interest or information of no interest. Receive requests from the MCX user terminal of the mission-critical service for changes in interest in different groups; Based on the interest change requests from the different groups, the target group whose first affiliation information is the information of interest is determined from the subscribed groups.

3. The method according to claim 2, characterized in that, The process of subscribing to multiple pre-configured groups in the Interworking Function (IWF) to obtain the second affiliation information of each subscribed group includes: Send subscription requests to multiple pre-configured groups in the Interoperability Function (IWF); Receive corresponding first notification information sent by multiple pre-configured groups in the Interworking Function (IWF); For any group's first notification message, if the first notification message carries a first indication message to indicate successful subscription, then the subscription to the group is successful, and the second affiliation information corresponding to the group is obtained.

4. The method according to claim 2, characterized in that, The step of determining the target group from the subscribed groups whose first attribution information is the information of interest based on the interest change requests of the different groups includes: Receive interest change requests sent by the MCX user terminal of the mission-critical service; Send the interest change request to multiple subscribed groups belonging to the Interworking Function IWF; Receive corresponding second notification information sent by multiple subscribed groups belonging to the Interworking Function (IWF); For any group's second notification information, if the second notification information carries second indication information for indicating that the first attribution information is information of interest, then the group is the target group.

5. The method according to any one of claims 1-4, characterized in that, The step of establishing a session call channel between the Interoperability Function (IWF) and the Mission-Critical Service (MCX) based on the call request includes: Based on the call request, configure the response status and voice service playback. Based on the response status configuration and the voice service playback configuration, a session call channel is established between the Interoperability Function (IWF) and the Mission-Critical Service (MCX).

6. The method according to any one of claims 1-4, characterized in that, Sending the voice information to the target group through the session call channel includes: The voice information is sent to the target group via the session call channel in a multicast or unicast manner.

7. A voice conversation calling device, characterized in that, Applications include the mission-critical service MCX proxy server, including: The determination module is used to determine, from multiple groups pre-configured in the Interworking Function (IWF), the target group whose first attribution information is information of interest, wherein the first attribution information includes information of interest or information of no interest; The receiving module is used to receive a call request initiated by a first user terminal, which is an Interworking Function (IWF) user terminal or a Mission-critical Service (MCX) user terminal. The module is used to establish a session call channel between the Interworking Function (IWF) and the Mission-Critical Service (MCX) based on the call request. The receiving module is also used to receive voice information sent by the first user terminal; The sending module is used to send the voice information to the target group through the session call channel, so that multiple second user terminals in the target group can receive the voice information.

8. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-6.

10. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-6.

Images