WO2017128524A1 - 多方通话的方法、装置和终端 - Google Patents

多方通话的方法、装置和终端 Download PDF

Info

Publication number
WO2017128524A1
WO2017128524A1 PCT/CN2016/078227 CN2016078227W WO2017128524A1 WO 2017128524 A1 WO2017128524 A1 WO 2017128524A1 CN 2016078227 W CN2016078227 W CN 2016078227W WO 2017128524 A1 WO2017128524 A1 WO 2017128524A1
Authority
WO
WIPO (PCT)
Prior art keywords
participant
capability
call
participants
party
Prior art date
Application number
PCT/CN2016/078227
Other languages
English (en)
French (fr)
Inventor
张子敬
文立新
Original Assignee
宇龙计算机通信科技(深圳)有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 宇龙计算机通信科技(深圳)有限公司 filed Critical 宇龙计算机通信科技(深圳)有限公司
Publication of WO2017128524A1 publication Critical patent/WO2017128524A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/56—Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/403—Arrangements for multi-party communication, e.g. for conferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/224—Monitoring or handling of messages providing notification on incoming messages, e.g. pushed notifications of received messages
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/58—Message adaptation for wireless communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1073—Registration or de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H04L65/4061—Push-to services, e.g. push-to-talk or push-to-video
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Definitions

  • the present invention relates to the field of multi-party calling technologies, and in particular, to a method for multi-party calling, a device for multi-party calling, and a terminal.
  • Multi-party calling technology is a multi-party online audio and video call realized by various means, which can realize real-time online communication in multiple parties and in different places, mainly used in business meetings, and typical implementation methods such as conference calls.
  • VoLTE Voice over LTE
  • IMS IP Multimedia Subsystem
  • VoLTE can support multi-party calling function, that is, a mobile terminal supporting VoLTE can initiate multi-party calling with one button, realizing real-time communication of audio and video.
  • the calling terminal usually does not know the network registration status of the called terminal, that is, the calling terminal does not know whether the called terminal has registered VoLTE, and if the calling terminal initiates a multiparty call, the called terminal also VoLTE is not registered, that is, the called terminal does not meet the capability requirements of the multi-party call, then the called party cannot complete the video call, and the calling terminal can only promptly urge the called terminal to make adjustment as soon as possible (here The adjustment specifically refers to registration to VoLTE.
  • the user of the calling terminal notifies the user of the called terminal by calling or sending a text message, resulting in poor user experience.
  • the invention is based on at least one of the above technical problems, and proposes a new multi-party calling scheme, which can promptly remind the participants that the service capability does not meet the capability requirements of the multi-party call in multiple parties. Make adjustments as soon as possible before the call starts to ensure multi-party calls, improve the efficiency of multi-party call access, and help improve the user experience.
  • a method for multi-party calling includes: receiving a multi-party call request sent by a call originator, where the multi-party call request includes a start time of a multi-party call, and information of all participants And a capability requirement for each participant; obtaining the business capability of each of the participants, and determining whether the business capability of each of the participants meets the capability requirement; at a time point predetermined from the start time And sending reminding information to the participants in the all participants that the business capability does not satisfy the capability requirement.
  • the service capability of each participant by acquiring the service capability of each participant, and determining whether the service capability of each participant satisfies the capability requirement of the multi-party call, and at a time point from the start time to the predetermined time, the service capability is not satisfied.
  • the participants of the call requesting capability send reminder information, so that the participants whose ability to meet the capability of the multi-party call cannot be promptly adjusted to make adjustments as soon as possible before the start of the multi-party call, so as to ensure multi-party call and improve multi-party call access.
  • the efficiency is beneficial to enhance the user experience.
  • the acquiring the service capability of each participant may be real-time acquisition, or may be obtained periodically or periodically.
  • the capability requirements of each participant included in the multi-party call request sent by the call originator may be the same or may not be the same.
  • the multi-party call request includes the participant A and the participant B.
  • the capability requirement of the participant A is to support the video call
  • the capability requirement of the participant B is to support only the voice call
  • the technical solution of the present invention can be According to the business capabilities and capability requirements of different participants, it is determined whether each participant's business capability meets the corresponding capability requirements. Certainly, if the capability requirements for the participant A and the participant B are both support video calls, it is determined whether the video call can be supported according to the service capabilities of the participant A and the participant B.
  • the step of acquiring the service capability of each participant includes: determining, according to the information of each participant, the home subscription user server corresponding to each participant; The home subscriber network server corresponding to each participant is obtained to obtain the capability identifier of each participant; and the service capability of each participant is determined according to the capability identifier of each participant.
  • the subscriber since the participant is registered in the network, the subscriber will be served at the home subscriber.
  • the capability identifier is recorded in the Home Subscriber Server (HSS). Therefore, by querying the HSS corresponding to each participant to obtain the capability identifier of each participant, it is convenient to determine the service of each participant according to the capability identifier. ability. Specifically, for example, if the participant registers with the IMS network and has the capability of video call and voice call, the corresponding capability identifier is recorded in the HSS to indicate that the participant has the capability of video call and voice call.
  • HSS Home Subscriber Server
  • hardware information of each participant may also be obtained, and then, according to hardware information of each participant, whether or not it has corresponding service capabilities, such as requesting participation in a multi-party call request.
  • the party can support the video call, but the participant does not have a camera, and it is determined that the participant does not have the ability to make a video call.
  • the step of sending the reminder information to the participant that the service capability does not meet the capability requirement in the all the participants includes: determining that the service capability of the all participants is not satisfied. Determining the target participant of the capability requirement; querying the home subscriber server corresponding to the target participant to obtain the network currently registered by the target participant; according to the communication mode supported by the network currently registered by the target participant, The target participant sends the reminder information.
  • the reminder information can be timely sent to the target participant, and the reminder information cannot be sent to the target participant.
  • the reminder information may be sent to the target participant by using a short message to avoid sending the reminder information through the data network, so that the target participant cannot receive the promptly. problem.
  • the method further includes: when the start time is reached, reminding the call initiator whether to initiate a multi-party call.
  • the call originator can be reminded in time.
  • the method further includes: sending the obtained service capability of each participant to the call initiator, and/or detecting that the service capability of any participant changes. And transmitting, by the call initiator, the changed service capability of the any participant to the call initiator, to determine whether the multiparty call is initiated at the start time.
  • the call initiator by sending the acquired service capability of each participant to the call initiator, and/or sending the changed service capability of any participant to the call initiator, it is ensured that the call initiator is involved in the call.
  • the party's business ability to determine whether to initiate a multiparty call at the start time For example, when the call originator determines that the participant C does not meet the corresponding capability requirement according to the service capability of the participant C, the caller may continue to wait for the participant C to make adjustments to meet the corresponding capability requirements at the start time, or do not wait to directly initiate the multi-party call. .
  • a device for multi-party calling comprising: a receiving unit, configured to receive a multi-party call request sent by a call originator, where the multi-party call request includes a start time of the multi-party call, all participants The information and the capability requirements for each of the participants; the obtaining unit, configured to obtain the business capability of each of the participants; the first determining unit, configured to determine whether the business capability of each of the participants meets the capability And a sending unit, configured to send reminding information to the participants in the all participants that the service capability does not satisfy the capability requirement at a time point that is longer than the start time.
  • the service capability of each participant by acquiring the service capability of each participant, and determining whether the service capability of each participant satisfies the capability requirement of the multi-party call, and at a time point from the start time to the predetermined time, the service capability is not satisfied.
  • the participants of the call requesting capability send reminder information, so that the participants whose ability to meet the capability of the multi-party call cannot be promptly adjusted to make adjustments as soon as possible before the start of the multi-party call, so as to ensure multi-party call and improve multi-party call access.
  • the efficiency is beneficial to enhance the user experience.
  • the acquiring the service capability of each participant may be real-time acquisition, or may be obtained periodically or periodically.
  • the capability requirements of each participant included in the multi-party call request sent by the call originator may be the same or may not be the same.
  • the multi-party call request includes the participant A and the participant B.
  • the capability requirement of the participant A is to support the video call
  • the capability requirement of the participant B is to support only the voice call
  • the technical solution of the present invention can be According to the business capabilities and capability requirements of different participants, it is determined whether each participant's business capability meets the corresponding capability requirements. Certainly, if the capability requirements for the participant A and the participant B are both support video calls, it is determined whether the video call can be supported according to the service capabilities of the participant A and the participant B.
  • the acquiring unit includes: a second determining unit, Determining, according to the information of each participant, the home subscription subscriber server corresponding to each participant; the first query unit is configured to query the home subscription subscriber server corresponding to each participant to obtain the foregoing The capability identification of the participants; the third determining unit is configured to determine the service capability of each of the participants according to the capability identifier of each participant.
  • the participant since the participant records the capability identifier in the HSS after registering the network, it is convenient to according to the capability by querying the HSS corresponding to each participant to obtain the capability identification of each participant.
  • the identity identifies the business capabilities of each party. Specifically, for example, if the participant registers with the IMS network and has the capability of video call and voice call, the corresponding capability identifier is recorded in the HSS to indicate that the participant has the capability of video call and voice call.
  • hardware information of each participant may also be obtained, and then, according to hardware information of each participant, whether or not it has corresponding service capabilities, such as requesting participation in a multi-party call request.
  • the party can support the video call, but the participant does not have a camera, and it is determined that the participant does not have the ability to make a video call.
  • the sending unit includes: a fourth determining unit, configured to determine a target participant that the service capability of the all participants does not meet the capability requirement; and the second query unit uses Querying a home subscriber server corresponding to the target participant to obtain a network currently registered by the target participant; and an execution unit, configured to send, according to a communication manner supported by the network currently registered by the target participant, The target participant sends the reminder information.
  • the reminder information can be timely sent to the target participant, and the reminder information cannot be sent to the target participant.
  • the reminder information may be sent to the target participant by using a short message to avoid sending the reminder information through the data network, so that the target participant cannot receive the promptly. problem.
  • the method further includes: a reminding unit, configured to remind the call originator whether to initiate a multi-party call when the start time is reached.
  • the call originator can be reminded in time.
  • the sending unit is further configured to: send the service capability of each participant acquired by the acquiring unit to the call initiator, and/or in the When the acquiring unit detects that the service capability of any participant changes, the changed service capability of any one of the participants is sent to the call initiator, so that the call initiator determines whether to initiate at the start time. Multi-party calls.
  • the call initiator by sending the acquired service capability of each participant to the call initiator, and/or sending the changed service capability of any participant to the call initiator, it is ensured that the call initiator is involved in the call.
  • the party's business ability to determine whether to initiate a multiparty call at the start time For example, when the call originator determines that the participant C does not meet the corresponding capability requirement according to the service capability of the participant C, the caller may continue to wait for the participant C to make adjustments to meet the corresponding capability requirements at the start time, or do not wait to directly initiate the multi-party call. .
  • the present invention also provides a terminal, comprising the apparatus for multiparty calling as described in any of the above technical solutions.
  • FIG. 1 shows a schematic flow chart of a method of multiparty calling according to an embodiment of the present invention
  • FIG. 2 shows a schematic block diagram of an apparatus for multiparty calling in accordance with an embodiment of the present invention
  • FIG. 3 is a schematic diagram showing an interaction process of devices in a multiparty call according to an embodiment of the present invention
  • Figure 4 shows a schematic block diagram of a terminal in accordance with one embodiment of the present invention.
  • FIG. 1 shows a schematic flow chart of a method of multiparty calling in accordance with an embodiment of the present invention.
  • a method for multi-party calling includes:
  • Step 102 Receive a multi-party call request sent by a call originator, where the multi-party call request includes a start time of the multi-party call, information of all participants, and a capability requirement for each participant;
  • Step 104 Obtain the service capability of each participant, and determine whether the service capability of each participant meets the capability requirement;
  • Step 106 Send a reminder message to a participant in the all participants that the service capability does not satisfy the capability requirement at a time point that is longer than the start time.
  • the service capability of each participant by acquiring the service capability of each participant, and determining whether the service capability of each participant satisfies the capability requirement of the multi-party call, and at a time point from the start time to the predetermined time, the service capability is not satisfied.
  • the participants of the call requesting capability send reminder information, so that the participants whose ability to meet the capability of the multi-party call cannot be promptly adjusted to make adjustments as soon as possible before the start of the multi-party call, so as to ensure multi-party call and improve multi-party call access.
  • the efficiency is beneficial to enhance the user experience.
  • the acquiring the service capability of each participant may be real-time acquisition, or may be obtained periodically or periodically.
  • the capability requirements of each participant included in the multi-party call request sent by the call originator may be the same or may not be the same.
  • the multi-party call request includes the participant A and the participant B.
  • the capability requirement of the participant A is to support the video call
  • the capability requirement of the participant B is to support only the voice call
  • the technical solution of the present invention can be According to the business capabilities and capability requirements of different participants, it is determined whether each participant's business capability meets the corresponding capability requirements. Certainly, if the capability requirements for the participant A and the participant B are both support video calls, it is determined whether the video call can be supported according to the service capabilities of the participant A and the participant B.
  • the step of acquiring the service capability of each participant includes: determining, according to the information of each participant, the home subscription user server corresponding to each participant; The home subscriber network server corresponding to each participant is obtained to obtain the capability identifier of each participant; and the service capability of each participant is determined according to the capability identifier of each participant.
  • the participant since the participant records the capability identifier in the home subscriber server HSS after registering the network, the HSS corresponding to each participant is queried to obtain the capability identifier of each participant. It is convenient to determine the business capabilities of each participant based on the capability identification. Specifically, for example, if the participant registers with the IMS network and has the capability of video call and voice call, the corresponding capability identifier is recorded in the HSS to indicate that the participant has the capability of video call and voice call.
  • hardware information of each participant may also be obtained, and then, according to hardware information of each participant, whether or not it has corresponding service capabilities, such as requesting participation in a multi-party call request.
  • the party can support the video call, but the participant does not have a camera, and it is determined that the participant does not have the ability to make a video call.
  • the step of sending the reminder information to the participant that the service capability does not meet the capability requirement in the all the participants includes: determining that the service capability of the all participants is not satisfied. Determining the target participant of the capability requirement; querying the home subscriber server corresponding to the target participant to obtain the network currently registered by the target participant; according to the communication mode supported by the network currently registered by the target participant, The target participant sends the reminder information.
  • the reminder information can be timely sent to the target participant, and the reminder information cannot be sent to the target participant.
  • the reminder information may be sent to the target participant by using a short message to avoid sending the reminder information through the data network, so that the target participant cannot receive the promptly. problem.
  • the method further includes: when the start time is reached, reminding the call initiator whether to initiate a multi-party call.
  • the call originator can be reminded in time.
  • the method further includes: sending the obtained service capability of each participant to the call initiator, and/or detecting that the service capability of any participant changes. Sending the changed service capability of any of the participants to the call Starting from the call originator to determine whether to initiate a multiparty call at the start time.
  • the call initiator by sending the acquired service capability of each participant to the call initiator, and/or sending the changed service capability of any participant to the call initiator, it is ensured that the call initiator is involved in the call.
  • the party's business ability to determine whether to initiate a multiparty call at the start time For example, when the call originator determines that the participant C does not meet the corresponding capability requirement according to the service capability of the participant C, the caller may continue to wait for the participant C to make adjustments to meet the corresponding capability requirements at the start time, or do not wait to directly initiate the multi-party call. .
  • FIG. 2 shows a schematic block diagram of an apparatus for multiparty calling in accordance with an embodiment of the present invention.
  • the apparatus 200 for multi-party calling includes: a receiving unit 202, an obtaining unit 204, a first determining unit 206, and a transmitting unit 208.
  • the receiving unit 202 is configured to receive a multi-party call request sent by the call originator, where the multi-party call request includes a start time of the multi-party call, information of all participants, and a capability requirement for each participant; the acquiring unit 204, For obtaining the service capability of each of the participants, the first determining unit 206 is configured to determine whether the service capability of each of the participants meets the capability requirement, and the sending unit 208 is configured to reserve at a distance from the start time. At the time of the duration, the reminder information is sent to the participants in the all participants who do not meet the capability requirements.
  • the service capability of each participant by acquiring the service capability of each participant, and determining whether the service capability of each participant satisfies the capability requirement of the multi-party call, and at a time point from the start time to the predetermined time, the service capability is not satisfied.
  • the participants of the call requesting capability send reminder information, so that the participants whose ability to meet the capability of the multi-party call cannot be promptly adjusted to make adjustments as soon as possible before the start of the multi-party call, so as to ensure multi-party call and improve multi-party call access.
  • the efficiency is beneficial to enhance the user experience.
  • the acquiring the service capability of each participant may be real-time acquisition, or may be obtained periodically or periodically.
  • the capability requirements of each participant included in the multi-party call request sent by the call originator may be the same or may not be the same.
  • the multi-party call request includes the participant A and the participant B.
  • the capability requirement of the participant A is to support the video call
  • the capability requirement of the participant B is to support only the voice call
  • the technical solution of the present invention can be According to the business capabilities and capability requirements of different participants, it is determined whether each participant's business capability meets the corresponding capability requirements.
  • the ability requirements of Participant A and Participant B are supportive
  • it is determined whether the video call can be supported according to the service capabilities of the participant A and the participant B.
  • the obtaining unit 204 includes: a second determining unit 2042, configured to determine, according to the information of each participant, the home subscription user server corresponding to each participant; the first query The unit 2044 is configured to query the home subscription subscriber server corresponding to each participant to obtain the capability identifier of each participant, and the third determining unit 2046 is configured to use, according to the capability identifier of each participant, Determine the business capabilities of each of the participants.
  • the participant since the participant records the capability identifier in the HSS after registering the network, it is convenient to according to the capability by querying the HSS corresponding to each participant to obtain the capability identification of each participant.
  • the identity identifies the business capabilities of each party. Specifically, for example, if the participant registers with the IMS network and has the capability of video call and voice call, the corresponding capability identifier is recorded in the HSS to indicate that the participant has the capability of video call and voice call.
  • hardware information of each participant may also be obtained, and then, according to hardware information of each participant, whether or not it has corresponding service capabilities, such as requesting participation in a multi-party call request.
  • the party can support the video call, but the participant does not have a camera, and it is determined that the participant does not have the ability to make a video call.
  • the sending unit 208 includes: a fourth determining unit 2082, configured to determine a target participant that the service capability of the all participants does not meet the capability requirement; and the second query unit 2084, configured to query a home subscriber server corresponding to the target participant to obtain a network that is currently registered by the target participant, and an execution unit 2086, configured to use, according to the communication mode supported by the network currently registered by the target participant Sending the reminder information to the target participant.
  • the reminder information can be timely sent to the target participant, and the reminder information cannot be sent to the target participant.
  • the reminder information may be sent to the target participant by using a short message to avoid sending the reminder information through the data network, so that the target participant cannot receive the promptly. problem.
  • the method further includes: a reminding unit 210, configured to remind the call originator whether to initiate a multi-party call when the start time is reached.
  • the call originator can be reminded in time.
  • the sending unit 208 is further configured to: send the service capability of each participant acquired by the acquiring unit 204 to the call initiator, and/or When the acquiring unit 204 detects that the service capability of any of the participants changes, the service capability of the changed participant is sent to the call initiator, where the call initiator is at the start time. Determine if a multiparty call is initiated.
  • the call initiator by sending the acquired service capability of each participant to the call initiator, and/or sending the changed service capability of any participant to the call initiator, it is ensured that the call initiator is involved in the call.
  • the party's business ability to determine whether to initiate a multiparty call at the start time For example, when the call originator determines that the participant C does not meet the corresponding capability requirement according to the service capability of the participant C, the caller may continue to wait for the participant C to make adjustments to meet the corresponding capability requirements at the start time, or do not wait to directly initiate the multi-party call. .
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • the IMS network-based multi-party communication system is taken as an example, that is, each participant needs to register to the IMS network to perform multi-party communication. specifically:
  • the conference initiator needs to set the conference schedule (that is, the information of the multi-party call), and the conference schedule needs to set information such as the conference participant, the conference time, and the required service type (such as audio, video, etc.).
  • the service type here means that the capability requirements for all participants are the same. If the required service type is video, it means that all participants need to be able to support video calls.
  • the initiator terminal After the conference initiator sets the conference schedule, the initiator terminal packages the set conference information to the IMS network to initiate a conference subscription request (ie, the multi-party call request described above), where the initiator terminal may send a SUBSCRIBE subscription message to the IMS network. Initiate a meeting subscription request.
  • a conference subscription request ie, the multi-party call request described above
  • the IMS network After receiving the subscription message, the IMS network monitors the registration status information of each participant in real time (that is, the registration status of the IMS network), acquires the service capability of each participant, and then sends the monitored registration status information and service capabilities to the Initiator terminal and monitoring registration status The initiator terminal is also notified when the information changes and/or the service capability changes.
  • the IMS network reminds the participants of the unregistered IMS network within a predetermined time of the conference time. Of course, the participants who have registered the IMS network but whose service capabilities do not meet the capability requirements may also be reminded. Finally, when the conference time is reached, the initiator terminal is reminded whether to initiate a conference. At this time, the sender terminal may select one button to initiate a conference connection, or continue to wait for the participant of the unregistered IMS network to change the registration state.
  • the initiator of the conference is the A user, and the conference participants are the B user and the C user.
  • a user needs to set the meeting schedule, set the meeting time (such as 14:00), the meeting participant (B user and C user), the service type (video), and may also include the meeting theme (the national business report).
  • the A user After setting the conference schedule, the A user will package the set information and send it to the multi-party call server of the IMS network through the SUBSCRIBE subscription message.
  • the multi-party call server After receiving the subscription message, the multi-party call server creates a multi-party call subscription record, saves the information, and detects the network registration status of user B and user C in real time.
  • the multi-party call server When the scheduled time of the meeting time (for example, 15:45 in advance) is detected, if it is detected that the user B has registered the IMS network and has the video calling capability, the user C is in the offline state (the offline state in this embodiment is specific). If the user C is not in the GSM network, and the user C is in the GSM network, the multi-party call server will send a reminder message to the user C to remind the user that the C conference call starts at 14:00. Please go online as soon as possible (in this embodiment, go online) Specifically refers to registration to the IMS network). At the same time, the multi-party call server will send the registration status of each participant and the service capability that can be supported to the conference initiator through a NOTIFY notification message.
  • user C When user C receives the reminder, it can go online as soon as possible, but if the condition is limited, it will not be processed.
  • user A When user A receives the notification message of the network, it will consider whether to continue waiting or to initiate a conference with one button according to the registration status of each participant and the service capabilities that can be supported.
  • the reminder of the user C may be prompted by the network form currently registered by the user C.
  • the user C registers the 2/3G network, and the notification message may be sent by using a short message or data.
  • Step 302 The conference initiator UE_A sets a conference schedule, including conference time, conference topic, conference participant, service type, and the like.
  • the UE is User Equipment and user equipment.
  • step 304 the conference initiator UE_A sends a subscription message to the IMS network.
  • Step 306 The IMS network sends a conference subscription message to the conference call server.
  • Step 308 the conference call server receives the conference subscription request, creates a conference call subscription record, and saves.
  • Step 310 The conference call server feeds back the conference subscription accept message to the IMS network.
  • step 312 the IMS network feeds back a 200 OK message to the conference initiator UE_A.
  • step 314 the conference call server monitors the registration status of user B and user C in real time.
  • step 316 the conference call server alerts the participants who are not in the registration state within a predetermined time of the conference time. Specifically, if the UE_B is not in the registration state, step 318 is performed, that is, the conference call server reminds the UE_B conference call to start at 14:00 through the NOTIFY notification message, please go online as soon as possible; if the UE_C is not in the registration state, go to step 320, that is, The conference call server reminds the UE_C conference call through the NOTIFY notification message at 14:00, please go online as soon as possible.
  • Step 322 The conference call server feeds back the registration status of the conference participant and the service capability that each participant can provide to the UE_A through the NOTIFY notification message for reference by the UE_A.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • each participant may register with the IMS network or not with the IMS network, as long as it has corresponding service capabilities, specifically:
  • the conference initiator needs to set the conference schedule (that is, the information of the multi-party call).
  • the conference schedule needs to set the conference participants, the conference time, and the capability requirements for each participant. Among them, the ability requirements of each participant can be the same or different.
  • the initiator terminal packages the set conference information to a server that manages the multi-party call (such as a session server that can be an IMS network) to initiate a conference subscription request (ie, the multi-party call request described above).
  • a server that manages the multi-party call such as a session server that can be an IMS network
  • the server After receiving the subscription message, the server obtains the service capabilities of each participant in real time to determine whether the service capability of each participant meets the corresponding capability requirements, and sends the acquired service capability to the initiator terminal, and obtains the The initiator terminal is also notified when a participant's business capability changes.
  • the server can learn the business capabilities of each participant by querying the HSS.
  • the server does not meet the corresponding capabilities for the business capability within the predetermined time of the meeting time. The required participants are reminded. Finally, when the conference time is reached, the initiator terminal is reminded whether to initiate a conference. At this time, the sender terminal may select one button to initiate a conference connection, or continue to wait for the participant whose service capability does not meet the corresponding capability requirement to make an adjustment.
  • the initiator of the conference is the E user, and the conference participants are the F user and the G user.
  • E users need to set the meeting schedule, set the meeting time (such as 14:00), the meeting participants (F users and G users), and the ability requirement of the participating party F is to support the video call.
  • the capability requirement for the participant G is Support at least voice calls.
  • the set information is packaged and sent to the multi-party call server.
  • the multi-party call server After receiving the subscription message, the multi-party call server creates a multi-party call subscription record, saves the information, and obtains the service capabilities of the user F and the user G in real time.
  • the multi-party call server When the scheduled service time of the conference time (for example, 15:45 in advance), if the acquired service capability of the user F indicates that it can perform a video call, and the service capability of the user G indicates that it cannot support the video call, However, it can support voice calls, and the multi-party call server does not need to remind the user G to change the status information. If the service capability of user G indicates that it cannot support voice calls, the multi-party call server can remind the user that the G conference call starts at 14:00. Please go online as soon as possible (the online line in this embodiment specifically refers to making adjustments to support voice calls). ). At the same time, the multi-party call server will send the business capabilities of each participant to the conference initiator.
  • the adjustment can be made as soon as possible, and if the condition is limited, the user cannot go online and does not process it.
  • user E receives the notification message of the network, it will consider whether to continue waiting or to initiate a conference with one button according to the service capabilities of each participant.
  • Figure 4 illustrates a terminal in accordance with one embodiment of the present invention.
  • the present invention also provides a terminal 400 comprising the apparatus 200 for multi-party calling as described in any of the above aspects.
  • the technical solution of the foregoing embodiment of the present invention establishes a conference subscription through schedule setting, and promptly reminds the called terminal that the service capability does not satisfy the multi-party call, prompts the called party to make an adjustment as soon as possible, so as to be able to perform multi-party calling, thereby greatly improving the multi-party
  • the efficiency of call access improves the user experience.
  • the present invention proposes a new multi-party calling scheme, which can promptly prompt the participants whose service capabilities do not meet the capability requirements of the multi-party call to make adjustments as soon as possible before the start of the multi-party call. To ensure multi-party calls and improve The efficiency of multi-party call access is conducive to improving the user experience.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本发明提供了一种多方通话的方法、装置和终端，其中，所述多方通话的方法，包括：接收通话发起方发送的多方通话请求，所述多方通话请求包含多方通话的开始时间、所有参与方的信息和对每个参与方的能力要求；获取所述每个参与方的业务能力，并确定所述每个参与方的业务能力是否满足所述能力要求；在距离所述开始时间预定时长的时间点，向所述所有参与方中业务能力不满足所述能力要求的参与方发送提醒信息。本发明的技术方案可以及时提醒业务能力不满足多方通话的能力要求的参与方在多方通话开始之前尽快做出调整，以确保能够进行多方通话，提高了多方通话接入的效率，有利于提升用户的体验。

Description

多方通话的方法、装置和终端 技术领域
本发明涉及多方通话技术领域，具体而言，涉及一种多方通话的方法、一种多方通话的装置和一种终端。
背景技术
多方通话技术就是通过各种手段实现的多方在线音视频通话，可以实现多方、异地实时的在线交流，主要应用于商务会谈，典型的实现方式如电话会议。
VoLTE(Voice over LTE)是基于IMS(IP Multimedia Subsystem，IP多媒体子系统)的语音业务。目前，VoLTE已经能够支持多方通话功能，即支持VoLTE功能的移动终端可以一键发起多方通话，实现音视频的实时交流。但是，在相关技术中，主叫终端通常并不知道被叫终端的网络注册状态，即主叫终端并不知道被叫终端是否已注册VoLTE，若主叫终端发起多方通话时，被叫终端还未注册VoLTE，即被叫终端还不满足多方通话的能力要求，那么此被叫是无法完成视频通话的，主叫终端只能赶紧通过其他方式催促该被叫终端尽快做出调整(此处的调整具体指注册到VoLTE)，如主叫终端的用户通过打电话、发短信等方式通知被叫终端的用户，导致用户体验不佳。
因此，如何能够及时提醒不满足多方通话的能力要求的被叫终端尽快做出调整，以提高多方通话的接入效率，提升用户的体验成为亟待解决的技术问题。
发明内容
本发明正是基于上述技术问题至少之一，提出了一种新的多方通话的方案，可以及时提醒业务能力不满足多方通话的能力要求的参与方在多方 通话开始之前尽快做出调整，以确保能够进行多方通话，提高了多方通话接入的效率，有利于提升用户的体验。
有鉴于此，根据本发明的第一方面，提出了一种多方通话的方法，包括：接收通话发起方发送的多方通话请求，所述多方通话请求包含多方通话的开始时间、所有参与方的信息和对每个参与方的能力要求；获取所述每个参与方的业务能力，并确定所述每个参与方的业务能力是否满足所述能力要求；在距离所述开始时间预定时长的时间点，向所述所有参与方中业务能力不满足所述能力要求的参与方发送提醒信息。
在该技术方案中，通过获取每个参与方的业务能力，并确定每个参与方的业务能力是否满足多方通话的能力要求，并在距离开始时间预定时长的时间点，向业务能力不满足多方通话的能力要求的参与方发送提醒信息，使得能够及时提醒业务能力不满足多方通话的能力要求的参与方在多方通话开始之前尽快做出调整，以确保能够进行多方通话，提高了多方通话接入的效率，有利于提升用户的体验。其中，获取每个参与方的业务能力可以是实时获取，也可以是周期性获取或非周期性获取。
具体来说，通话发起方发送的多方通话请求中包含的每个参与方的能力要求可以是相同的，也可以是不相同的。比如：多方通话请求中包含了参与方A和参与方B，对参与方A的能力要求为支持视频通话，对参与方B的能力要求为仅支持语音通话即可，则本发明的技术方案可以根据不同参与方的业务能力和能力要求来确定每个参与方的业务能力是否满足相应的能力要求。当然，若对参与方A与参与方B的能力要求均为支持视频通话，则需要根据参与方A与参与方B的业务能力确定是否都能够支持视频通话。
在上述技术方案中，优选地，获取所述每个参与方的业务能力的步骤，具体包括：根据所述每个参与方的信息确定所述每个参与方对应的归属签约用户服务器；查询所述每个参与方对应的归属签约用户服务器，以得到所述每个参与方的能力标识；根据所述每个参与方的能力标识，确定所述每个参与方的业务能力。
在该技术方案中，由于参与方在注册网络后，会在归属签约用户服务 器(即Home Subscriber Server，HSS)中记录出其能力标识，因此通过查询每个参与方对应的HSS，以得到每个参与方的能力标识，可以方便地根据能力标识确定每个参与方的业务能力。具体地，比如参与方注册了IMS网络，并且其具有视频通话和语音通话的能力，则会在HSS中记录相应的能力标识，以表示该参与方具有视频通话和语音通话的能力。
此外，在本发明的其它实施例中，也可以获取每个参与方的硬件信息，进而根据每个参与方的硬件信息来确定其是否具有相应的业务能力，如多方通话请求中要求某个参与方能够支持视频通话，但是该参与方没有摄像头，则确定该参与方不具备视频通话的能力。
在上述任一技术方案中，优选地，向所述所有参与方中业务能力不满足所述能力要求的参与方发送提醒信息的步骤，具体包括：确定所述所有参与方中业务能力不满足所述能力要求的目标参与方；查询所述目标参与方对应的归属签约用户服务器，以得到所述目标参与方当前注册的网络；根据所述目标参与方当前注册的网络所支持的通信方式，向所述目标参与方发送所述提醒信息。
在该技术方案中，通过根据目标参与方当前注册的网络所支持的通信方式，向目标参与方发送提醒信息，可以确保提醒信息及时发送到目标参与方，避免提醒信息无法发送到目标参与方的情况出现。具体地，如通过查询HSS确定目标参与方当前注册的网络是2G网络，则可以通过短信向所述目标参与方发送提醒信息，避免通过数据网络发送提醒信息而导致目标参与方无法及时收到的问题。
在上述任一技术方案中，优选地，还包括：在到达所述开始时间时，提醒所述通话发起方是否发起多方通话。
在该技术方案中，通过在到达开始时间时，提醒通话发起方是否发起多方通话，可以及时对通话发起方进行提醒。
在上述任一技术方案中，优选地，还包括：将获取到的所述每个参与方的业务能力发送至所述通话发起方，和/或在检测到任一参与方的业务能力发生变化时，将所述任一参与方变化后的业务能力发送至所述通话发起方，以供所述通话发起方在所述开始时间确定是否发起多方通话。
在该技术方案中，通过将获取到的每个参与方的业务能力发送至通话发起方，和/或将任一参与方变化后的业务能力发送至通话发起方，可以确保通话发起方掌握参与方的业务能力，以在开始时间确定是否发起多方通话。比如通话发起方在根据参与方C的业务能力确定参与方C不满足相应的能力要求时，在开始时间可以继续等待参与方C做出调整以满足相应的能力要求，或不等待直接发起多方通话。
根据本发明的第二方面，还提出了一种多方通话的装置，包括：接收单元，用于接收通话发起方发送的多方通话请求，所述多方通话请求包含多方通话的开始时间、所有参与方的信息和对每个参与方的能力要求；获取单元，用于获取所述每个参与方的业务能力；第一确定单元，用于确定所述每个参与方的业务能力是否满足所述能力要求；发送单元，用于在距离所述开始时间预定时长的时间点，向所述所有参与方中业务能力不满足所述能力要求的参与方发送提醒信息。
在该技术方案中，通过获取每个参与方的业务能力，并确定每个参与方的业务能力是否满足多方通话的能力要求，并在距离开始时间预定时长的时间点，向业务能力不满足多方通话的能力要求的参与方发送提醒信息，使得能够及时提醒业务能力不满足多方通话的能力要求的参与方在多方通话开始之前尽快做出调整，以确保能够进行多方通话，提高了多方通话接入的效率，有利于提升用户的体验。其中，获取每个参与方的业务能力可以是实时获取，也可以是周期性获取或非周期性获取。
具体来说，通话发起方发送的多方通话请求中包含的每个参与方的能力要求可以是相同的，也可以是不相同的。比如：多方通话请求中包含了参与方A和参与方B，对参与方A的能力要求为支持视频通话，对参与方B的能力要求为仅支持语音通话即可，则本发明的技术方案可以根据不同参与方的业务能力和能力要求来确定每个参与方的业务能力是否满足相应的能力要求。当然，若对参与方A与参与方B的能力要求均为支持视频通话，则需要根据参与方A与参与方B的业务能力确定是否都能够支持视频通话。
在上述技术方案中，优选地，所述获取单元包括：第二确定单元，用 于根据所述每个参与方的信息确定所述每个参与方对应的归属签约用户服务器；第一查询单元，用于查询所述每个参与方对应的归属签约用户服务器，以得到所述每个参与方的能力标识；第三确定单元，用于根据所述每个参与方的能力标识，确定所述每个参与方的业务能力。
在该技术方案中，由于参与方在注册网络后，会在HSS中记录出其能力标识，因此通过查询每个参与方对应的HSS，以得到每个参与方的能力标识，可以方便地根据能力标识确定每个参与方的业务能力。具体地，比如参与方注册了IMS网络，并且其具有视频通话和语音通话的能力，则会在HSS中记录相应的能力标识，以表示该参与方具有视频通话和语音通话的能力。
此外，在本发明的其它实施例中，也可以获取每个参与方的硬件信息，进而根据每个参与方的硬件信息来确定其是否具有相应的业务能力，如多方通话请求中要求某个参与方能够支持视频通话，但是该参与方没有摄像头，则确定该参与方不具备视频通话的能力。
在上述任一技术方案中，优选地，所述发送单元包括：第四确定单元，用于确定所述所有参与方中业务能力不满足所述能力要求的目标参与方；第二查询单元，用于查询所述目标参与方对应的归属签约用户服务器，以得到所述目标参与方当前注册的网络；执行单元，用于根据所述目标参与方当前注册的网络所支持的通信方式，向所述目标参与方发送所述提醒信息。
在该技术方案中，通过根据目标参与方当前注册的网络所支持的通信方式，向目标参与方发送提醒信息，可以确保提醒信息及时发送到目标参与方，避免提醒信息无法发送到目标参与方的情况出现。具体地，如通过查询HSS确定目标参与方当前注册的网络是2G网络，则可以通过短信向所述目标参与方发送提醒信息，避免通过数据网络发送提醒信息而导致目标参与方无法及时收到的问题。
在上述任一技术方案中，优选地，还包括：提醒单元，用于在到达所述开始时间时，提醒所述通话发起方是否发起多方通话。
在该技术方案中，通过在到达开始时间时，提醒通话发起方是否发起多方通话，可以及时对通话发起方进行提醒。
在上述任一技术方案中，优选地，所述发送单元还用于：将所述获取单元获取到的所述每个参与方的业务能力发送至所述通话发起方，和/或在所述获取单元检测到任一参与方的业务能力发生变化时，将所述任一参与方变化后的业务能力发送至所述通话发起方，以供所述通话发起方在所述开始时间确定是否发起多方通话。
在该技术方案中，通过将获取到的每个参与方的业务能力发送至通话发起方，和/或将任一参与方变化后的业务能力发送至通话发起方，可以确保通话发起方掌握参与方的业务能力，以在开始时间确定是否发起多方通话。比如通话发起方在根据参与方C的业务能力确定参与方C不满足相应的能力要求时，在开始时间可以继续等待参与方C做出调整以满足相应的能力要求，或不等待直接发起多方通话。
本发明还提供了一种终端，包括如上述任一技术方案所述的多方通话的装置。
通过以上技术方案，可以及时提醒业务能力不满足多方通话的能力要求的参与方在多方通话开始之前尽快做出调整，以确保能够进行多方通话，提高了多方通话接入的效率，有利于提升用户的体验。
附图说明
图1示出了根据本发明的实施例的多方通话的方法的示意流程图；
图2示出了根据本发明的实施例的多方通话的装置的示意框图；
图3示出了根据本发明的一个实施例的多方通话中各设备的交互过程示意图；
图4示出了根据本发明的一个实施例的终端的示意框图。
具体实施方式
为了能够更清楚地理解本发明的上述目的、特征和优点，下面结合附图和具体实施方式对本发明进行进一步的详细描述。需要说明的是，在不冲突的情况下，本申请的实施例及实施例中的特征可以相互组合。
在下面的描述中阐述了很多具体细节以便于充分理解本发明，但是，本发明还可以采用其他不同于在此描述的其他方式来实施，因此，本发明 的保护范围并不受下面公开的具体实施例的限制。
图1示出了根据本发明的实施例的多方通话的方法的示意流程图。
如图1所示，根据本发明的实施例的多方通话的方法，包括：
步骤102，接收通话发起方发送的多方通话请求，所述多方通话请求包含多方通话的开始时间、所有参与方的信息和对每个参与方的能力要求；
步骤104，获取所述每个参与方的业务能力，并确定所述每个参与方的业务能力是否满足所述能力要求；
步骤106，在距离所述开始时间预定时长的时间点，向所述所有参与方中业务能力不满足所述能力要求的参与方发送提醒信息。
在该技术方案中，通过获取每个参与方的业务能力，并确定每个参与方的业务能力是否满足多方通话的能力要求，并在距离开始时间预定时长的时间点，向业务能力不满足多方通话的能力要求的参与方发送提醒信息，使得能够及时提醒业务能力不满足多方通话的能力要求的参与方在多方通话开始之前尽快做出调整，以确保能够进行多方通话，提高了多方通话接入的效率，有利于提升用户的体验。其中，获取每个参与方的业务能力可以是实时获取，也可以是周期性获取或非周期性获取。
具体来说，通话发起方发送的多方通话请求中包含的每个参与方的能力要求可以是相同的，也可以是不相同的。比如：多方通话请求中包含了参与方A和参与方B，对参与方A的能力要求为支持视频通话，对参与方B的能力要求为仅支持语音通话即可，则本发明的技术方案可以根据不同参与方的业务能力和能力要求来确定每个参与方的业务能力是否满足相应的能力要求。当然，若对参与方A与参与方B的能力要求均为支持视频通话，则需要根据参与方A与参与方B的业务能力确定是否都能够支持视频通话。
在上述技术方案中，优选地，获取所述每个参与方的业务能力的步骤，具体包括：根据所述每个参与方的信息确定所述每个参与方对应的归属签约用户服务器；查询所述每个参与方对应的归属签约用户服务器，以得到所述每个参与方的能力标识；根据所述每个参与方的能力标识，确定所述每个参与方的业务能力。
在该技术方案中，由于参与方在注册网络后，会在归属签约用户服务器HSS中记录出其能力标识，因此通过查询每个参与方对应的HSS，以得到每个参与方的能力标识，可以方便地根据能力标识确定每个参与方的业务能力。具体地，比如参与方注册了IMS网络，并且其具有视频通话和语音通话的能力，则会在HSS中记录相应的能力标识，以表示该参与方具有视频通话和语音通话的能力。
此外，在本发明的其它实施例中，也可以获取每个参与方的硬件信息，进而根据每个参与方的硬件信息来确定其是否具有相应的业务能力，如多方通话请求中要求某个参与方能够支持视频通话，但是该参与方没有摄像头，则确定该参与方不具备视频通话的能力。
在上述任一技术方案中，优选地，向所述所有参与方中业务能力不满足所述能力要求的参与方发送提醒信息的步骤，具体包括：确定所述所有参与方中业务能力不满足所述能力要求的目标参与方；查询所述目标参与方对应的归属签约用户服务器，以得到所述目标参与方当前注册的网络；根据所述目标参与方当前注册的网络所支持的通信方式，向所述目标参与方发送所述提醒信息。
在该技术方案中，通过根据目标参与方当前注册的网络所支持的通信方式，向目标参与方发送提醒信息，可以确保提醒信息及时发送到目标参与方，避免提醒信息无法发送到目标参与方的情况出现。具体地，如通过查询HSS确定目标参与方当前注册的网络是2G网络，则可以通过短信向所述目标参与方发送提醒信息，避免通过数据网络发送提醒信息而导致目标参与方无法及时收到的问题。
在上述任一技术方案中，优选地，还包括：在到达所述开始时间时，提醒所述通话发起方是否发起多方通话。
在该技术方案中，通过在到达开始时间时，提醒通话发起方是否发起多方通话，可以及时对通话发起方进行提醒。
在上述任一技术方案中，优选地，还包括：将获取到的所述每个参与方的业务能力发送至所述通话发起方，和/或在检测到任一参与方的业务能力发生变化时，将所述任一参与方变化后的业务能力发送至所述通话发 起方，以供所述通话发起方在所述开始时间确定是否发起多方通话。
在该技术方案中，通过将获取到的每个参与方的业务能力发送至通话发起方，和/或将任一参与方变化后的业务能力发送至通话发起方，可以确保通话发起方掌握参与方的业务能力，以在开始时间确定是否发起多方通话。比如通话发起方在根据参与方C的业务能力确定参与方C不满足相应的能力要求时，在开始时间可以继续等待参与方C做出调整以满足相应的能力要求，或不等待直接发起多方通话。
图2示出了根据本发明的实施例的多方通话的装置的示意框图。
如图2所示，根据本发明的实施例的多方通话的装置200，包括：接收单元202、获取单元204、第一确定单元206和发送单元208。
其中，接收单元202，用于接收通话发起方发送的多方通话请求，所述多方通话请求包含多方通话的开始时间、所有参与方的信息和对每个参与方的能力要求；获取单元204，用于获取所述每个参与方的业务能力；第一确定单元206，用于确定所述每个参与方的业务能力是否满足所述能力要求；发送单元208，用于在距离所述开始时间预定时长的时间点，向所述所有参与方中业务能力不满足所述能力要求的参与方发送提醒信息。
在该技术方案中，通过获取每个参与方的业务能力，并确定每个参与方的业务能力是否满足多方通话的能力要求，并在距离开始时间预定时长的时间点，向业务能力不满足多方通话的能力要求的参与方发送提醒信息，使得能够及时提醒业务能力不满足多方通话的能力要求的参与方在多方通话开始之前尽快做出调整，以确保能够进行多方通话，提高了多方通话接入的效率，有利于提升用户的体验。其中，获取每个参与方的业务能力可以是实时获取，也可以是周期性获取或非周期性获取。
具体来说，通话发起方发送的多方通话请求中包含的每个参与方的能力要求可以是相同的，也可以是不相同的。比如：多方通话请求中包含了参与方A和参与方B，对参与方A的能力要求为支持视频通话，对参与方B的能力要求为仅支持语音通话即可，则本发明的技术方案可以根据不同参与方的业务能力和能力要求来确定每个参与方的业务能力是否满足相应的能力要求。当然，若对参与方A与参与方B的能力要求均为支持视 频通话，则需要根据参与方A与参与方B的业务能力确定是否都能够支持视频通话。
在上述技术方案中，优选地，所述获取单元204包括：第二确定单元2042，用于根据所述每个参与方的信息确定所述每个参与方对应的归属签约用户服务器；第一查询单元2044，用于查询所述每个参与方对应的归属签约用户服务器，以得到所述每个参与方的能力标识；第三确定单元2046，用于根据所述每个参与方的能力标识，确定所述每个参与方的业务能力。
在该技术方案中，由于参与方在注册网络后，会在HSS中记录出其能力标识，因此通过查询每个参与方对应的HSS，以得到每个参与方的能力标识，可以方便地根据能力标识确定每个参与方的业务能力。具体地，比如参与方注册了IMS网络，并且其具有视频通话和语音通话的能力，则会在HSS中记录相应的能力标识，以表示该参与方具有视频通话和语音通话的能力。
此外，在本发明的其它实施例中，也可以获取每个参与方的硬件信息，进而根据每个参与方的硬件信息来确定其是否具有相应的业务能力，如多方通话请求中要求某个参与方能够支持视频通话，但是该参与方没有摄像头，则确定该参与方不具备视频通话的能力。
在上述任一技术方案中，优选地，所述发送单元208包括：第四确定单元2082，用于确定所述所有参与方中业务能力不满足所述能力要求的目标参与方；第二查询单元2084，用于查询所述目标参与方对应的归属签约用户服务器，以得到所述目标参与方当前注册的网络；执行单元2086，用于根据所述目标参与方当前注册的网络所支持的通信方式，向所述目标参与方发送所述提醒信息。
在该技术方案中，通过根据目标参与方当前注册的网络所支持的通信方式，向目标参与方发送提醒信息，可以确保提醒信息及时发送到目标参与方，避免提醒信息无法发送到目标参与方的情况出现。具体地，如通过查询HSS确定目标参与方当前注册的网络是2G网络，则可以通过短信向所述目标参与方发送提醒信息，避免通过数据网络发送提醒信息而导致目标参与方无法及时收到的问题。
在上述任一技术方案中，优选地，还包括：提醒单元210，用于在到达所述开始时间时，提醒所述通话发起方是否发起多方通话。
在该技术方案中，通过在到达开始时间时，提醒通话发起方是否发起多方通话，可以及时对通话发起方进行提醒。
在上述任一技术方案中，优选地，所述发送单元208还用于：将所述获取单元204获取到的所述每个参与方的业务能力发送至所述通话发起方，和/或在所述获取单元204检测到任一参与方的业务能力发生变化时，将所述任一参与方变化后的业务能力发送至所述通话发起方，以供所述通话发起方在所述开始时间确定是否发起多方通话。
在该技术方案中，通过将获取到的每个参与方的业务能力发送至通话发起方，和/或将任一参与方变化后的业务能力发送至通话发起方，可以确保通话发起方掌握参与方的业务能力，以在开始时间确定是否发起多方通话。比如通话发起方在根据参与方C的业务能力确定参与方C不满足相应的能力要求时，在开始时间可以继续等待参与方C做出调整以满足相应的能力要求，或不等待直接发起多方通话。
以下以两个具体实施例详细说明本发明的技术方案：
实施例一：
在该实施例中，以基于IMS网络的多方通话系统为例进行说明，即假设每个参与方都需要注册到IMS网络来进行多方通话。具体地：
会议发起者需要设定会议日程(即多方通话的信息)，会议日程中需要设定会议参与方、会议时间及所需业务类型(如音频、视频等)等信息。此处的业务类型表示对所有参与方的能力要求是一样的，如所需业务类型为视频，则说明需要所有参与方都能够支持视频通话。
在会议发起者设定会议日程后，发起方终端将设定的会议信息打包向IMS网络发起会议订阅请求(即上述的多方通话请求)，其中，发起方终端可以发送SUBSCRIBE订阅消息来向IMS网络发起会议订阅请求。
IMS网络接收该订阅消息后会实时监测各参与方的注册状态信息(即对IMS网络的注册状态)，并获取每个参与方的业务能力，然后将监测到的注册状态信息和业务能力发送至发起方终端，并且在监测到注册状态 信息发生变化和/或业务能力发送变化时也会通知发起方终端。
IMS网络在临近会议时间的预定时间内对于未注册IMS网络的参与方进行提醒，当然也可以提醒虽然注册了IMS网络，但是业务能力不满足能力要求的参与方。最后在到达会议时间时提醒发起方终端是否发起会议，此时，发送方终端可以选择一键发起会议连接，或者继续等待未注册IMS网络的参与方改变注册状态。
具体应用场景如下：
会议发起者为A用户，会议参与方为B用户和C用户。A用户需要设定会议日程，设定会议时间(如14：00)、会议参与方(B用户和C用户)、业务类型(视频)，也可以包括会议主题(各省业务汇报)。
A用户在设定会议日程后，会将设置的信息打包通过SUBSCRIBE订阅消息发送到IMS网络的多方通话服务器。多方通话服务器在接收到该订阅消息后会创建多方通话订阅记录，保存这些信息，并实时检测用户B和用户C的网络注册状态。
在临近会议时间的预定时间(如提前15分钟，即13：45)时，若检测到用户B已注册IMS网络且具有视频通话能力，而用户C处于离线状态(此实施例中的离线状态具体指未注册到IMS网络)，且用户C处于GSM网络下，此时多方通话服务器会向用户C发送提醒信息，提醒用户C会议通话在14：00开始，请尽快上线(此实施例中的上线具体指注册到IMS网络)。同时，多方通话服务器会将各参与方的注册状态以及所能支持的业务能力通过NOTIFY通知消息发送到会议发起者。
当用户C收到提醒时，可以尽快上线，而对于条件所限无法上线的，不做处理。当用户A收到网络的通知消息时，会根据各参与方的注册状态以及所能支持的业务能力，考虑后续是否继续等待还是一键发起会议。
其中，对于用户C的提醒，可以通过用户C当前注册的网络形式进行提醒，如用户C注册2/3G网络，可通过短信或数据发送通知消息。
上述过程如图3所示，包括：
步骤302，会议发起者UE_A设定会议日程，包括会议时间、会议主题、会议参与方、业务类型等信息。其中，UE即User Equipment，用户设备。
步骤304，会议发起者UE_A向IMS网络发送订阅消息。
步骤306，IMS网络向会议通话服务器发送会议订阅消息。
步骤308，会议通话服务器接收会议订阅请求，创建会议通话订阅记录，并保存。
步骤310，会议通话服务器向IMS网络反馈会议订阅接受消息。
步骤312，IMS网络向会议发起者UE_A反馈200OK消息。
步骤314，会议通话服务器实时监测用户B和用户C的注册状态。
步骤316，会议通话服务器在临近会议时间的预定时间内对于未处于注册状态的参与者进行提醒。具体地，若UE_B未处于注册状态，则执行步骤318，即会议通话服务器通过NOTIFY通知消息提醒UE_B会议通话在14:00开始，请尽快上线；若UE_C未处于注册状态，则执行步骤320，即会议通话服务器通过NOTIFY通知消息提醒UE_C会议通话在14:00开始，请尽快上线。
步骤322，会议通话服务器通过NOTIFY通知消息向UE_A反馈会议参与方的注册状态及每个参与方所能提供的业务能力，以供UE_A参考。
实施例二：
在该实施例中，每个参与方既可以注册到IMS网络，也可以不注册到IMS网络，只要其具有相应的业务能力即可，具体地：
会议发起者需要设定会议日程(即多方通话的信息)，会议日程中需要设定会议参与方、会议时间及对每个参与方的能力要求。其中，既可以对每个参与方的能力要求相同，也可以不同。
在会议发起者设定会议日程后，发起方终端将设定的会议信息打包向管理多方通话的服务器(如可以是IMS网络的会话服务器)发起会议订阅请求(即上述的多方通话请求)。
服务器接收该订阅消息后会实时获取各参与方的业务能力，以确定每个参与方的业务能力是否满足相应的能力要求，并将获取到的业务能力发送至发起方终端，并且在获取到任一参与方的业务能力发生变化时也会通知发起方终端。其中，服务器可以通过查询HSS来获知各参与方的业务能力。
服务器在临近会议时间的预定时间内对于业务能力不满足相应的能力 要求的参与方进行提醒。最后在到达会议时间时提醒发起方终端是否发起会议，此时，发送方终端可以选择一键发起会议连接，或者继续等待业务能力不满足相应的能力要求的参与方做出调整。
具体应用场景如下：
会议发起者为E用户，会议参与方为F用户和G用户。E用户需要设定会议日程，设定会议时间(如14：00)、会议参与方(F用户和G用户)，对参与方F的能力要求为支持视频通话，对参与方G的能力要求为至少支持语音通话。
E用户在设定会议日程后，会将设置的信息打包发送到多方通话服务器。多方通话服务器在接收到该订阅消息后会创建多方通话订阅记录，保存这些信息，并实时获取用户F和用户G的业务能力。
在临近会议时间的预定时间(如提前15分钟，即13：45)时，若获取到的用户F的业务能力表明其能够进行视频通话，而用户G的业务能力表明其不能够支持视频通话，但是能够支持语音通话，此时多方通话服务器也无需提醒用户G改变状态信息。而若用户G的业务能力表明其不能够支持语音通话时，多方通话服务器可以提醒用户G会议通话在14：00开始，请尽快上线(此实施例中的上线具体指做出调整以支持语音通话)。同时，多方通话服务器会将各参与方的业务能力发送到会议发起者。
当用户G收到提醒时，可以尽快做出调整，而对于条件所限无法上线的，不做处理。当用户E收到网络的通知消息时，会根据各参与方的业务能力，考虑后续是否继续等待还是一键发起会议。
图4示出了根据本发明的一个实施例的终端。本发明还提供了一种终端400，包括如上述任一技术方案所述的多方通话的装置200。
本发明上述实施例的技术方案通过日程设定建立会议订阅，并对业务能力不满足多方通话的被叫终端进行实时提醒，提醒被叫尽快做出调整，以能够进行多方通话，大大提高了多方通话接入效率，提升了用户的体验。
以上结合附图详细说明了本发明的技术方案，本发明提出了一种新的多方通话的方案，可以及时提醒业务能力不满足多方通话的能力要求的参与方在多方通话开始之前尽快做出调整，以确保能够进行多方通话，提高 了多方通话接入的效率，有利于提升用户的体验。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (11)

  1. 一种多方通话的方法，其特征在于，包括：
    接收通话发起方发送的多方通话请求，所述多方通话请求包含多方通话的开始时间、所有参与方的信息和对每个参与方的能力要求；
    获取所述每个参与方的业务能力，并确定所述每个参与方的业务能力是否满足所述能力要求；
    在距离所述开始时间预定时长的时间点，向所述所有参与方中业务能力不满足所述能力要求的参与方发送提醒信息。
  2. 根据权利要求1所述的多方通话的方法，其特征在于，获取所述每个参与方的业务能力的步骤，具体包括：
    根据所述每个参与方的信息确定所述每个参与方对应的归属签约用户服务器；
    查询所述每个参与方对应的归属签约用户服务器，以得到所述每个参与方的能力标识；
    根据所述每个参与方的能力标识，确定所述每个参与方的业务能力。
  3. 根据权利要求2所述的多方通话的方法，其特征在于，向所述所有参与方中业务能力不满足所述能力要求的参与方发送提醒信息的步骤，具体包括：
    确定所述所有参与方中业务能力不满足所述能力要求的目标参与方；
    查询所述目标参与方对应的归属签约用户服务器，以得到所述目标参与方当前注册的网络；
    根据所述目标参与方当前注册的网络所支持的通信方式，向所述目标参与方发送所述提醒信息。
  4. 根据权利要求1至3中任一项所述的多方通话的方法，其特征在于，还包括：
    在到达所述开始时间时，提醒所述通话发起方是否发起多方通话。
  5. 根据权利要求1至3中任一项所述的多方通话的方法，其特征在于，还包括：
    将获取到的所述每个参与方的业务能力发送至所述通话发起方，和/或在检测到任一参与方的业务能力发生变化时，将所述任一参与方变化后的业务能力发送至所述通话发起方，以供所述通话发起方在所述开始时间确定是否发起多方通话。
  6. 一种多方通话的装置，其特征在于，包括：
    接收单元，用于接收通话发起方发送的多方通话请求，所述多方通话请求包含多方通话的开始时间、所有参与方的信息和对每个参与方的能力要求；
    获取单元，用于获取所述每个参与方的业务能力；
    第一确定单元，用于确定所述每个参与方的业务能力是否满足所述能力要求；
    发送单元，用于在距离所述开始时间预定时长的时间点，向所述所有参与方中业务能力不满足所述能力要求的参与方发送提醒信息。
  7. 根据权利要求6所述的多方通话的装置，其特征在于，所述获取单元包括：
    第二确定单元，用于根据所述每个参与方的信息确定所述每个参与方对应的归属签约用户服务器；
    第一查询单元，用于查询所述每个参与方对应的归属签约用户服务器，以得到所述每个参与方的能力标识；
    第三确定单元，用于根据所述每个参与方的能力标识，确定所述每个参与方的业务能力。
  8. 根据权利要求7所述的多方通话的装置，其特征在于，所述发送单元包括：
    第四确定单元，用于确定所述所有参与方中业务能力不满足所述能力要求的目标参与方；
    第二查询单元，用于查询所述目标参与方对应的归属签约用户服务器，以得到所述目标参与方当前注册的网络；
    执行单元，用于根据所述目标参与方当前注册的网络所支持的通信方式，向所述目标参与方发送所述提醒信息。
  9. 根据权利要求6至8中任一项所述的多方通话的装置，其特征在于，还包括：
    提醒单元，用于在到达所述开始时间时，提醒所述通话发起方是否发起多方通话。
  10. 根据权利要求6至8中任一项所述的多方通话的装置，其特征在于，所述发送单元还用于：
    将所述获取单元获取到的所述每个参与方的业务能力发送至所述通话发起方，和/或在所述获取单元检测到任一参与方的业务能力发生变化时，将所述任一参与方变化后的业务能力发送至所述通话发起方，以供所述通话发起方在所述开始时间确定是否发起多方通话。
  11. 一种终端，其特征在于，包括如权利要求6至10中任一项所述的多方通话的装置。
PCT/CN2016/078227 2016-01-29 2016-03-31 多方通话的方法、装置和终端 WO2017128524A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610066311.7A CN105763537A (zh) 2016-01-29 2016-01-29 多方通话的方法及装置
CN201610066311.7 2016-01-29

Publications (1)

Publication Number Publication Date
WO2017128524A1 true WO2017128524A1 (zh) 2017-08-03

Family

ID=56342851

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/078227 WO2017128524A1 (zh) 2016-01-29 2016-03-31 多方通话的方法、装置和终端

Country Status (2)

Country Link
CN (1) CN105763537A (zh)
WO (1) WO2017128524A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022222691A1 (zh) * 2021-04-22 2022-10-27 华为技术有限公司 一种通话处理方法及相关设备

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108076452A (zh) * 2016-11-18 2018-05-25 大唐移动通信设备有限公司 一种通知业务能力的方法、装置和系统
CN108124243A (zh) * 2016-11-29 2018-06-05 展讯通信（上海）有限公司 一种多通路终端多方通话方法及装置
CN109428873A (zh) * 2017-08-31 2019-03-05 中兴通讯股份有限公司 多方通话方法、装置及实现系统和计算机可读存储介质
CN111131741B (zh) * 2019-12-13 2021-08-13 中移（杭州）信息技术有限公司 多方视频通话方法、电子设备、装置及计算机可读存储介质
CN112203038B (zh) * 2020-10-12 2022-09-16 北京字节跳动网络技术有限公司 在线会议的处理方法、装置、电子设备及计算机存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030053612A1 (en) * 2001-09-14 2003-03-20 Henrikson Eric Harold Targeted and intelligent multimedia conference establishment services
CN101325504A (zh) * 2008-07-11 2008-12-17 中兴通讯股份有限公司 一种应用服务器控制多媒体会议的方法及装置
CN103414836A (zh) * 2013-07-23 2013-11-27 中国联合网络通信集团有限公司 接入基于ip的电话会议的处理方法及装置
CN104580247A (zh) * 2015-01-27 2015-04-29 宇龙计算机通信科技(深圳)有限公司 基于ims多方通话的信息同步方法和信息同步装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101472235B (zh) * 2007-12-25 2012-08-15 华为技术有限公司 一种多终端通信方法、系统和装置
CN101800950A (zh) * 2009-12-29 2010-08-11 宇龙计算机通信科技(深圳)有限公司 一种通话过程中实现语音留言的方法、系统及移动终端
CN103118349B (zh) * 2013-01-21 2016-02-10 东莞宇龙通信科技有限公司 多卡通信终端的移动增值业务实现方法及多卡通信终端
CN104811537A (zh) * 2015-03-26 2015-07-29 努比亚技术有限公司 一种文件接收方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030053612A1 (en) * 2001-09-14 2003-03-20 Henrikson Eric Harold Targeted and intelligent multimedia conference establishment services
CN101325504A (zh) * 2008-07-11 2008-12-17 中兴通讯股份有限公司 一种应用服务器控制多媒体会议的方法及装置
CN103414836A (zh) * 2013-07-23 2013-11-27 中国联合网络通信集团有限公司 接入基于ip的电话会议的处理方法及装置
CN104580247A (zh) * 2015-01-27 2015-04-29 宇龙计算机通信科技(深圳)有限公司 基于ims多方通话的信息同步方法和信息同步装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022222691A1 (zh) * 2021-04-22 2022-10-27 华为技术有限公司 一种通话处理方法及相关设备

Also Published As

Publication number Publication date
CN105763537A (zh) 2016-07-13

Similar Documents

Publication Publication Date Title
WO2017128524A1 (zh) 多方通话的方法、装置和终端
US11849072B2 (en) Method and system for automating conferencing in a communication session
CA2859716C (en) Method and apparatus for providing session initiator privilege, priority and presence notification for push-to-talk chat group communications
US8112106B2 (en) Method and apparatus for obtaining group information by an invited user during a session
JP5628296B2 (ja) セッションプッシュ伝送
US20050259803A1 (en) Managing a conference session
CA2760901A1 (en) System and method for implementing a transfer of control of a collaborative session using sip protocol
WO2014154262A1 (en) Teleconference message box
WO2015131709A1 (zh) 一种电视会议中与会者私聊的方法及装置
JP2010259070A (ja) ｊｏｉｎ−ｕｓコールログ及びコールアンサーメッセージ
US10602092B2 (en) Personalized audio-video invitations via peer-to-peer connection
US20160037129A1 (en) Method and Apparatus for Enhanced Caller ID
EP3172880B1 (en) Method of and communications handling equipment for controlling communication session establishment in a multimedia communications network.
WO2016101790A1 (zh) 一种加入会议及会议邀请的方法、相关设备及系统
AU2018350926A1 (en) Personalized audio/video invitations for phone calls
WO2008064575A1 (fr) Procédé, système et appareil permettant la mise en place de service de partage vidéo
EP3070876A1 (en) Method and system for improving teleconference services
JP2008535408A (ja) 複数のデバイスへのパケットベースの呼出しの接続
WO2016119300A1 (zh) 基于ims多方通话的信息同步方法、信息同步装置和终端
WO2009036662A1 (fr) Procédé, système et appareil permettant d'accéder à une réunion multimédia en réseau
CN109391606A (zh) 一种通信方法、装置和移动终端
WO2018214735A1 (zh) 视讯会议实现方法及服务器、计算机可读存储介质
WO2012163098A1 (zh) 一种用应用服务器实现子会议功能的方法和系统
KR20180077720A (ko) Id 기반의 통화와 전화번호 기반의 통화를 연동하기 위한 장치 및 방법
WO2012034423A1 (zh) 会话中早媒体的播放方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16887406

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16887406

Country of ref document: EP

Kind code of ref document: A1