WO2020216063A1 - 业务呼叫的实现方法、装置和设备 - Google Patents

业务呼叫的实现方法、装置和设备 Download PDF

Info

Publication number
WO2020216063A1
WO2020216063A1 PCT/CN2020/083731 CN2020083731W WO2020216063A1 WO 2020216063 A1 WO2020216063 A1 WO 2020216063A1 CN 2020083731 W CN2020083731 W CN 2020083731W WO 2020216063 A1 WO2020216063 A1 WO 2020216063A1
Authority
WO
WIPO (PCT)
Prior art keywords
rcs
app
terminal
message
called terminal
Prior art date
Application number
PCT/CN2020/083731
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 WO2020216063A1 publication Critical patent/WO2020216063A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H04W8/265—Network addressing or numbering for mobility support for initial activation of new user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates to, but is not limited to, a method, device, device and computer-readable storage medium for implementing a business call.
  • RCS applications can be deployed on multiple smart terminals at the same time, such as smart watches, smart phones, tablet computers (Portable Device, PAD), personal computers ( Personal Computer, PC), etc. Therefore, the RCS multi-terminal voice service (IPCentrex) based on the IP Multimedia Subsystem (IMS) was created, that is, the same RCS APP account can be logged in to multiple terminals at the same time, and the user can make/receive calls on any terminal , Multi-terminal business realizes the process and logic control of the entire multi-terminal call.
  • IMS IP Multimedia Subsystem
  • the embodiments of the present disclosure provide a method, device, device, and computer-readable storage medium for realizing a service call, so as to improve the call completion rate.
  • the embodiments of the present disclosure provide a method for implementing a service call, including: determining that the calling terminal initiates a call and the RCS APP of the called terminal is offline; waking up the RCS APP of the called terminal; and paging the RCS APP of the called terminal.
  • the embodiment of the present disclosure also provides a device for implementing a service call, including: a determining module, used to determine that the calling terminal initiates a call but the RCS APP of the called terminal is not online; a wake-up module, used to wake up the RCS APP of the called terminal; and The paging module is used to page the RCS APP of the called terminal.
  • the embodiment of the present disclosure also provides a device for realizing a service call, including: a memory, a processor, and a computer program stored on the memory and running on the processor, and the processor executes the program when the program is executed.
  • a device for realizing a service call including: a memory, a processor, and a computer program stored on the memory and running on the processor, and the processor executes the program when the program is executed.
  • the embodiments of the present disclosure also provide a computer-readable storage medium storing computer-executable instructions, and when the computer-executable instructions are executed by a processor, the processor executes the method for implementing a business call according to the present disclosure.
  • Figure 1 is a system architecture diagram according to an embodiment of the present disclosure
  • Figure 2 is a flowchart of a method for implementing a service call according to an embodiment of the present disclosure
  • Figure 3 is a signaling flow chart of a method for implementing a service call according to an application example of the present disclosure
  • Fig. 4 is a schematic diagram of the composition of an apparatus for implementing a service call according to an embodiment of the present disclosure.
  • Fig. 5 is a schematic diagram of the composition of a service call realization device according to an embodiment of the present disclosure.
  • the RCS multi-terminal service does not have a call wake-up function. If the RCS APP of the called end is not online, the call establishment fails, and there will be a message of missed calls on the RCS APP, and there is no function to wake up the RCS APP on the called end to complete the call .
  • the embodiment of the present disclosure proposes that when the called RCS APP goes offline, the RCS multi-terminal service sends a message through the IPCentrex to wake up the RCS APP of the called terminal to realize a service call.
  • the multi-terminal service network element of RCS is an IPCentrex application server (Application Server, AS) 11.
  • IPCentrex AS 11 implements multi-terminal call control functions on the basis of the IMS core network, and uses the Session Initiation Protocol (SIP) between the Serving-Call Session Control Function (S-CSCF) of the IMS Perform message interaction to realize multi-terminal media information exchange and call control.
  • SIP Session Initiation Protocol
  • S-CSCF Serving-Call Session Control Function
  • the always-on push platform (Always Online Infrastructure, AOI) 13 network elements of the RCS-based multi-terminal business system 1 are mainly used to interface with the message push server 2, and deliver push (PUSH) messages to the terminal, that is, the user equipment (User Equipment, UE), so as to realize the automatic wake-up of RCS APP.
  • the message push server may include Apple Push Notification Service (APNS), and may also include Google Cloud Messaging (GCM).
  • APNS Apple Push Notification Service
  • GCM Google Cloud Messaging
  • the RCS-based multi-terminal business system 1 also Including the database 12 and other network elements 14, which are not specifically described here.
  • the method for implementing a service call according to an embodiment of the present disclosure, applied to IPCentrex AS, includes the following steps 101 to 103.
  • step 101 it is determined that the calling terminal initiates a call and the RCS APP of the called terminal is not online.
  • the RCS APP of the called end is offline according to the received response message that the RCS APP is offline.
  • IPCentrex AS when IPCentrex AS receives the 480/408/430/500 message returned by the S-CSCF, it means that the RCS APP of the called end is offline.
  • step 102 the RCS APP of the called terminal is awakened.
  • the RCS APP of the called terminal is awakened by sending a PUSH message.
  • the PUSH message may be sent to the AOI, so that the AOI wakes up the RCS APP of the called terminal through the message push server.
  • the terminal type and token information of the called terminal are determined by querying a database.
  • IPCentrex AS carries the terminal type and token information in the push message and sends it to the AOI.
  • the token information may be a token value.
  • the AOI After receiving the PUSH message from IPCentrex AS, the AOI will convert the message to a standard interface and send it to APNS/GCM, and the APNS/GCM will send it to the called end.
  • AOI determines which push message server (APNS or GCM) the PUSH message is sent to according to the terminal type, and determines the corresponding called terminal according to the token information.
  • APNS push message server
  • GCM GCM
  • the IPCentrex AS after the IPCentrex AS sends the push message, it also sends a ring back tone instruction, that is, a 180 ringing (Ringing) message to the calling terminal.
  • a ring back tone instruction that is, a 180 ringing (Ringing) message
  • the IPCentrex AS after the IPCentrex AS sends the push message, it also determines that the RCS APP has been awakened according to the received registration message sent by the RCS APP.
  • IPCentrex AS When IPCentrex AS receives the third-party registration message, it determines that the RCS APP of the UE of the called end has been awakened, and can initiate paging to the called end.
  • step 103 the RCS APP of the called end is paged.
  • the RCS APP of the called end When IPCentrex AS pages the RCS APP of the called end, the RCS APP of the called end has been woken up, so the RCS APP of the called end rings and the answer/reject interface pops up. After the called user chooses to answer, the call is established and the caller The user and the called user can make a call.
  • a wake-up operation is performed when the RCS APP of the called terminal is not online, so that the called user is notified in real time to answer the call, so that the call is established successfully and the user's demand for timely communication is met.
  • the multi-terminal service network element IPCentrex AS 11 mainly implements service logic call control based on the IMS core network.
  • IPCentrex AS 11 pages the called terminal (UE B).
  • the core network of the called side returns a response (480/408/430/500) that the RCS APP on the called side is not online (480/408/430/500)
  • the IPCentrex AS 11 queries the local terminal registration database 12 for the terminal type and token information of the called side.
  • IPCentrex AS 11 sends a PUSH message to AOI 13 according to the terminal type and the Token value of the token information.
  • AOI 13 After AOI 13 receives the message from IPCentrex AS 11, it converts the message to a standard interface and sends it to APNS/GCM, and then sends it to the called terminal (UEB) through APNS/GCM.
  • the RCS APP on the called terminal (UE B) will be automatically awakened, so that the awakened RCS APP will send a third-party registration message to IPCentrex AS 11.
  • IPCentrex AS 11 When IPCentrex AS 11 receives the registration message of RCS APP, IPCentrex AS 11 then calls the called terminal (UE B). At this time, the call acceptance/rejection interface of RCS APP will pop up on the called terminal (UE B), and the called user clicks to answer, and the call is established successfully.
  • the method for implementing a service call includes the following steps 201 to 239. :
  • step 201 the RCS APP on the terminal (UE B) of the called user B initiates a registration request (REGISTER) to the session border controller (Session Border Controller, SBC) B to which it belongs.
  • REGISTER Session Border Controller
  • step 202 SBC B sends a registration request to the S-CSCF B where it is located.
  • step 203 S-CSCF B returns a 200 OK message to SBC B.
  • step 204 SBC B returns a 200 OK message to UE B.
  • step 205 S-CSCF B sends a third-party registration request to IPCentrex AS.
  • IPCentrex AS saves the terminal type and token information in the registration request in the local database.
  • step 207 IPCentrex AS returns a 200 OK message to S-CSCF B.
  • step 208 UE B has successfully registered and is online at this time. After a period of time, it may be that the user actively offline RCS APP or the process of RCS APP is terminated by the IOS/Android operating system, causing RCS APP to go offline.
  • step 209 the RCS APP on the terminal (UE A) of the calling user A initiates a voice call to the UE B, and the UE A sends an invitation (Invitation) message to the SBC A.
  • step 210 SBC A forwards the invitation message to S-CSCF A.
  • step 211 S-CSCF A forwards the invitation message to IPCentrex AS.
  • step 212 the calling process of IPCentrex AS is triggered. After the IPCentrex AS parses the message, it finds the called number and initiates an invitation message to UE B according to the called number. In this step, IPCentrex AS sends the invitation message to S-CSCF A.
  • step 213 S-CSCF A sends an invitation message to S-CSCF B.
  • step 214 S-CSCF B sends an invitation message to IPCentrex AS to trigger the called process of IPCentrex AS.
  • step 215 IPCentrex AS sends an invitation message to S-CSCF B.
  • step 216 S-CSCF B sends an invitation message to SBC B.
  • step 217 because UE B has gone offline, SBC B returns a 480/408/430/500 message to S-CSCF B.
  • step 218 S-CSCF B sends a 480/408/430/500 message to IPCentrex AS.
  • step 219 after the called process of IPCentrex AS receives the 480/408/430/500 message, it knows that the RCS APP on the called end is not online, so it queries the local database to find the terminal type and command of the called end UE B ⁇ .
  • IPCentrex AS issues a Pushkit-based Voice over Internet Protocol (VOIP) PUSH message to AOI.
  • VOIP Voice over Internet Protocol
  • the message is sent to ANPS/GCM, and then through ANPS/GCM Send to the corresponding terminal.
  • step 221 IPCentrex AS sends a 180 ringing message to S-CSCF B.
  • step 222 S-CSCF B sends a 180 ringing message to S-CSCF A.
  • step 223 S-CSCF A sends a 180 ringing message to IPCentrex AS.
  • step 224 IPCentrex AS sends a 180 ringing message to S-CSCF A.
  • step 225 S-CSCF A sends a 180 ringing message to SBC A.
  • step 2266 SBC A sends a 180 ringing message to UE A.
  • step 227 after the UE B terminal receives the PUSH message, the RCS APP is automatically awakened.
  • step 229 SBC B sends a registration message to S-CSCF B.
  • step 230 S-CSCF B returns a 200 OK message to SBC B.
  • step 231 SBC B returns a 200 OK message to UE B.
  • step 232 S-CSCF B sends a third-party registration message to IPCentrex AS.
  • step 233 when the IPCentrex AS receives the third-party registration message, it knows that UEB has been woken up and goes online, and the IPCentrex AS initiates paging to UE B again.
  • step 2334 IPCentrex AS sends an invitation message to S-CSCF B.
  • step 235 S-CSCF B sends an invitation message to SBC B.
  • step 2366 SBC B sends an invitation message to UE B.
  • step 237 the RCS APP on UE B rings and pops up the answer/reject interface, and sends a 180 ringing message to SBC B.
  • step 2308 SBC B sends a 180 ringing message to S-CSCF B.
  • step 239 S-CSCF B sends a 180 ringing message to IPCentrex AS.
  • the PUSH message is sent to the called terminal through IPCentrex AS, and the called terminal automatically wakes up the RCS APP.
  • IPCentrex AS will continue to call the called end, and the RCS APP call answer/reject interface will pop up on the called end. The called user clicks answer and the call is established successfully.
  • the internal processing of IPCentrex AS does not have any abnormal experience or impact on the host user.
  • an embodiment of the present disclosure also provides a device for implementing a service call, including a determination module 31, a wake-up module 32 and a paging module 33.
  • the determining module 31 is used to determine that the calling terminal initiates a call and the RCS APP of the called terminal is not online.
  • the wake-up module 32 is used to wake up the RCS APP of the called terminal.
  • the paging module 33 is used to page the RCS APP of the called terminal.
  • the determining module 31 is configured to determine that the RCS APP of the called terminal is offline according to the received response message that the RCS APP is offline.
  • the wake-up module 32 is used to wake up the RCS APP of the called terminal by sending a push message.
  • the wake-up module 32 is configured to send the push message to the AOI, so that the AOI wakes up the RCS APP of the called end through the message push server.
  • the wake-up module 32 is configured to determine the terminal type and token information of the called terminal by querying a database, and carry the terminal type and token information in the push message and send to the AOI .
  • the wake-up module 32 is also used to send a ring back tone instruction to the calling terminal.
  • the awakening module 32 is further configured to determine that the RCS APP has been awakened according to the received registration message sent by the RCS APP.
  • a wake-up operation is performed when the RCS APP of the called terminal is not online, so that the called user is notified in real time to answer the call, so that the call is established successfully and the user's demand for timely communication is met.
  • an embodiment of the present disclosure also provides a device for implementing a service call, which includes a memory 41, a processor 42 and a computer program 43 stored on the memory 41 and running on the processor 42.
  • a device for implementing a service call which includes a memory 41, a processor 42 and a computer program 43 stored on the memory 41 and running on the processor 42.
  • the processor 42 executes the computer program 43, the method for implementing the service call according to the embodiments of the present disclosure is implemented.
  • the embodiments of the present disclosure also provide a computer-readable storage medium that stores computer-executable instructions.
  • the processor executes the implementation of the business call according to the embodiments of the present disclosure. method.
  • the foregoing storage medium may include, but is not limited to: U disk, Read-Only Memory (ROM), Random Access Memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk, etc.
  • U disk Read-Only Memory
  • RAM Random Access Memory
  • RAM Random Access Memory
  • mobile hard disk magnetic disk or optical disk, etc.
  • Computer storage medium includes volatile and non-volatile memory implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data).
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassette, tape, magnetic disk storage or other magnetic storage device, or Any other medium used to store desired information and that can be accessed by a computer.

Abstract

一种业务呼叫的实现方法、装置和设备，所述方法包括：确定主叫端发起呼叫而被叫端的RCS APP不在线；唤醒被叫端的RCS APP；以及寻呼被叫端的RCS APP。

Description

业务呼叫的实现方法、装置和设备 技术领域
本公开涉及但不限于一种业务呼叫的实现方法、装置、设备和计算机可读存储介质。
背景技术
随着移动宽带和智能终端的不断发展，各种以即时通信为核心的OTT(Over The Top)应用蓬勃发展，这些应用通过免费和丰富的用户体验，聚集了大量的用户，对运营商传统消息和语音业务造成了巨大的冲击。为适应新的市场环境和竞争需要，运营商希望在电信网络下依托于个人融合通信业务实现对传统语音、消息、通信录等基础通信业务的平滑升级，提升4G/5G网络环境下用户业务体验，重新抢占用户入口。在此背景下，产生了融合通信系统(Rich Communication Suite，RCS)。
随着RCS系统的不断发展和智能终端的丰富，RCS的应用(Application，APP)可以同时部署在多个智能终端上，如智能手表、智能手机、平板电脑(Portable Device，PAD)、个人计算机(Personal Computer，PC)等。所以产生了基于IP多媒体子系统(IP Multimedia Subsystem，IMS)的RCS多端语音业务(IPCentrex)，即，同一个RCS APP账号可以在多个终端上同时登陆，用户可以在任一终端上拨打/接听电话，多端业务实现整个多端呼叫的流程和逻辑控制。
用户在使用RCS多端业务进行语音通话时，通常会遇到，被叫用户所有端的RCS APP都不在线的情况，导致电话无法通知到被叫用户，从而电话无法及时接通。
发明内容
以下是对本公开详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本公开实施例提供了一种业务呼叫的实现方法、装置、设备和 计算机可读存储介质，以提高呼叫接通率。
本公开实施例提供了一种业务呼叫的实现方法，包括：确定主叫端发起呼叫而被叫端的RCS APP不在线；唤醒被叫端的RCS APP；以及寻呼被叫端的RCS APP。
本公开实施例还提供一种业务呼叫的实现装置，包括：确定模块，用于确定主叫端发起呼叫而被叫端的RCS APP不在线；唤醒模块，用于唤醒被叫端的RCS APP；以及寻呼模块，用于寻呼被叫端的RCS APP。
本公开实施例还提供一种业务呼叫的实现设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述程序时实现根据本公开的业务呼叫的实现方法。
本公开实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器运行时，所述处理器执行根据本公开的业务呼叫的实现方法。
附图说明
图1是根据本公开实施例的系统架构图；
图2是根据本公开实施例的业务呼叫的实现方法的流程图；
图3是根据本公开应用实例的业务呼叫的实现方法的信令流程图；
图4是根据本公开实施例的业务呼叫的实现装置的组成示意图；以及
图5是根据本公开实施例的业务呼叫的实现设备的组成示意图。
具体实施方式
下文中将结合附图对本公开的实施例进行详细说明。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
目前RCS多端业务没有呼叫唤醒功能，若被叫端的RCS APP不在线时，呼叫建立失败，RCS APP上会有未接电话的消息提示，没有能够在线唤醒被叫端上RCS APP来完成呼叫的功能。
本公开实施例提出RCS多端业务在被叫RCS APP下线时，通过IPCentrex发送消息唤醒被叫端的RCS APP，实现业务呼叫。
参照图1，在根据本公开实施例的基于RCS的多端业务系统1中，RCS的多端业务网元为IPCentrex应用服务器(Application Server，AS)11。IPCentrex AS 11在IMS核心网的基础上实现多端的呼叫控制功能，与IMS的服务呼叫会话控制功能(Serving-Call Session Control Function，S-CSCF)之间通过会话初始协议(Session Initiation Protocol，SIP)进行消息交互，以实现多端的媒体信息交换和呼叫控制。基于RCS的多端业务系统1的永远在线推送平台(Always Online Infrastructure，AOI)13网元主要用于跟消息推送服务器2对接，将推送(PUSH)消息下发给终端，即用户设备(User Equipment，UE)，从而实现RCS APP的自动唤醒。所述消息推送服务器可以包括苹果公司的推送知服务器(Apple Push Notification Service，APNS)，也可以包括谷歌云消息服务器(Google Cloud Messaging，GCM)，需要说明的是，基于RCS的多端业务系统1还包括数据库12和其他网元14，在此不作具体说明。
如图2所示，根据本公开实施例的业务呼叫的实现方法，应用于IPCentrex AS，包括如下步骤101至103。
在步骤101，确定主叫端发起呼叫而被叫端的RCS APP不在线。
在实施例中，可以根据接收到的RCS APP不在线的响应消息，确定被叫端的RCS APP不在线。
例如，当IPCentrex AS接收到S-CSCF返回的480/408/430/500消息，表示被叫端的RCS APP不在线。
在步骤102，唤醒被叫端的RCS APP。
在实施例中，通过发送PUSH消息唤醒被叫端的RCS APP。
可以将所述PUSH消息发送至AOI，以使所述AOI通过消息推送服务器唤醒被叫端的RCS APP。
在实施例中，在将所述推送消息发送至AOI之前，通过查询数据库确定所述被叫端的终端类型和令牌信息。
IPCentrex AS将所述终端类型和令牌信息携带在所述推送消息中，发送至所述AOI。
所述令牌信息可以是令牌(Token)值，AOI收到IPCentrex AS的PUSH消息后，会把消息转成标准接口发给APNS/GCM，APNS/GCM发送给被叫端。
AOI根据终端类型确定将PUSH消息发送给哪个消息推送服务器(APNS还是GCM)，根据令牌信息确定对应的被叫端。
在实施例中，在IPCentrex AS发送所述推送消息之后，还向所述主叫端发送回铃音指令，也即180振铃(Ringing)消息。
在实施例中，在IPCentrex AS发送所述推送消息之后，还根据接收到的所述RCS APP发送的注册消息，确定所述RCS APP已被唤醒。
当IPCentrex AS接收到第三方注册消息时，就确定被叫端的UE的RCS APP已被唤醒，可以发起对被叫端的寻呼。
在步骤103，寻呼被叫端的RCS APP。
IPCentrex AS寻呼被叫端的RCS APP时，由于被叫端的RCS APP已被唤醒，所以被叫端的RCS APP振铃并弹出接听/拒绝的界面，在被叫用户选择接听后，呼叫建立，主叫用户和被叫用户可以进行通话。
需要说明的是，由于被叫端的RCS APP可以是多个，所以在实际应用时，可以根据预设策略，在被叫端的全部和部分RCS APP不在线时，寻呼被叫端RCS APP。在寻呼被叫端RCS APP时，可以根据预设策略寻呼被叫端所有不在线的RCS APP，也可以寻呼优先级最高的一个或多个不在线的RCS APP，还可以寻呼指定的一个或多个不在线的RCS APP。
本公开实施例通过在被叫端RCS APP不在线时进行唤醒操作，从而实时通知到被叫用户来接听通话，使得呼叫建立成功，满足用户及时通讯的需求。
下面以本公开的一些实施例进行说明。
参照图1和图3，多端业务网元IPCentrex AS 11主要是在IMS 核心网的基础上实现业务逻辑的呼叫控制。当主叫端(UE A)发起呼叫时，IPCentrex AS 11寻呼被叫端(UE B)。当被叫侧核心网返回被叫端上RCS APP不在线的响应(480/408/430/500)时，IPCentrex AS 11在本地的终端注册数据库12中查询被叫端的终端类型和令牌信息。IPCentrex AS 11根据终端类型和令牌信息的Token值发送PUSH消息的操作给AOI 13。AOI 13收到IPCentrex AS 11的消息后，把消息转成标准接口发给APNS/GCM，进而通过APNS/GCM发送给被叫端(UE B)。被叫端(UE B)上的RCS APP会被自动唤醒，从而使得被唤醒的RCS APP向IPCentrex AS 11发送第三方注册消息。当IPCentrex AS 11收到RCS APP的注册消息时，IPCentrex AS 11再去呼叫被叫端(UE B)。此时在被叫端(UE B)上会弹出RCS APP的呼叫接听/拒绝的界面，被叫用户点击接听，呼叫建立成功。
参照图3，根据本公开实施例的业务呼叫的实现方法包括如下步骤201至239。：
在步骤201，被叫用户B的终端(UE B)上的RCS APP，发起注册请求(REGISTER)给所归属的会话边界控制器(Session Border Controller，SBC)B。
在步骤202，SBC B把注册请求发给所在的S-CSCF B。
在步骤203，S-CSCF B给SBC B返回200OK消息。
在步骤204，SBC B给UE B返回200OK消息。
在步骤205，S-CSCF B发送第三方注册请求给IPCentrex AS。
在步骤206，IPCentrex AS把注册请求里的终端类型和令牌信息保存在本地数据库。
在步骤207，IPCentrex AS给S-CSCF B返回200OK消息。
在步骤208，此时UE B已经注册成功并在线了，过了一段时间，可能是用户主动下线了RCS APP或者RCS APP的进程被IOS/Android操作系统终止了，导致RCS APP下线。
在步骤209，主叫用户A的终端(UE A)上的RCS APP，发起对UE B的语音呼叫，UE A发送邀请(Invitation)消息至SBC A。
在步骤210，SBC A转发邀请消息至S-CSCF A。
在步骤211，S-CSCF A转发邀请消息至IPCentrex AS。
在步骤212，触发IPCentrex AS的主叫流程，IPCentrex AS解析消息后，找到被叫号码，根据被叫号码发起对UE B的邀请消息，本步骤中，IPCentrex AS发送邀请消息至S-CSCF A。
在步骤213，S-CSCF A发送邀请消息至S-CSCF B。
在步骤214，S-CSCF B发送邀请消息至IPCentrex AS，触发IPCentrex AS的被叫流程。
在步骤215，IPCentrex AS发送邀请消息至S-CSCF B。
在步骤216，S-CSCF B发送邀请消息至SBC B。
在步骤217，因为UE B已经下线，所以SBC B返回480/408/430/500消息给S-CSCF B。
在步骤218，S-CSCF B发送480/408/430/500消息给IPCentrex AS。
在步骤219，IPCentrex AS的被叫流程收到480/408/430/500消息后，知道被叫端上的RCS APP都不在线，所以查询本地数据库，找到被叫端UE B的终端类型和令牌信息。
在步骤220，IPCentrex AS下发基于Pushkit的基于IP的语音传输协议(Voice over Internet Protocol，VOIP)PUSH消息给AOI，AOI转换成标准消息后，把消息发送给ANPS/GCM，进而通过ANPS/GCM发送给相应终端上。
在步骤221，IPCentrex AS发送180振铃消息给S-CSCF B。
在步骤222，S-CSCF B发送180振铃消息给S-CSCF A。
在步骤223，S-CSCF A发送180振铃消息给IPCentrex AS。
在步骤224，IPCentrex AS发送180振铃消息给S-CSCF A。
在步骤225，S-CSCF A发送180振铃消息给SBC A。
在步骤226，SBC A发送180振铃消息给UE A。
在步骤227，UE B终端收到PUSH消息后，RCS APP被自动唤醒。
在步骤228，UE B发起注册消息给SBC B。
在步骤229，SBC B向S-CSCF B发送注册消息。
在步骤230，S-CSCF B向SBC B返回200OK消息。
在步骤231，SBC B向UE B返回200OK消息。
在步骤232，S-CSCF B向IPCentrex AS发送第三方注册消息。
在步骤233，IPCentrex AS收到第三方注册消息时，知道UEB已经被唤醒上线，IPCentrex AS又发起对UE B的寻呼。
在步骤234，IPCentrex AS向S-CSCF B发送邀请消息。
在步骤235，S-CSCF B向SBC B发送邀请消息。
在步骤236，SBC B向UE B发送邀请消息。
在步骤237，UE B上的RCS APP振铃并弹出接听/拒绝的界面，向SBC B发送180振铃消息。
在步骤238，SBC B向S-CSCF B发送180振铃消息。
在步骤239，S-CSCF B向IPCentrex AS发送180振铃消息。
用户B选择接听后，呼叫成功建立，A用户和B用户可以进行语音通话。
本公开实施例中，RCS多端业务在被叫端RCS APP下线时，通过IPCentrex AS下发PUSH消息给被叫端，由被叫端自动把RCS APP唤醒。IPCentrex AS会继续呼叫被叫端，被叫端上会弹出RCS APP的呼叫接听/拒绝的界面，被叫用户点击接听，呼叫建立成功。这个IPCentrex AS内部的处理过程，对主机用户没有任何异常体验或影响。
如图4所示，本公开实施例还提供一种业务呼叫的实现装置，包括确定模块31、唤醒模块32和寻呼模块33。
确定模块31用于确定主叫端发起呼叫而被叫端的RCS APP不在线。
唤醒模块32用于唤醒被叫端的RCS APP。
寻呼模块33用于寻呼被叫端的RCS APP。
在实施例中，所述确定模块31用于根据接收到的RCS APP不在线的响应消息，确定被叫端的RCS APP不在线。
在实施例中，所述唤醒模块32用于通过发送推送消息唤醒被叫端的RCS APP。
在实施例中，所述唤醒模块32用于将所述推送消息发送至AOI， 以使所述AOI通过消息推送服务器唤醒被叫端的RCS APP。
在实施例中，所述唤醒模块32用于通过查询数据库确定所述被叫端的终端类型和令牌信息，并且将所述终端类型和令牌信息携带在所述推送消息中发送至所述AOI。
在实施例中，所述唤醒模块32还用于向所述主叫端发送回铃音指令。
在实施例中，所述唤醒模块32还用于根据接收到的所述RCS APP发送的注册消息，确定所述RCS APP已被唤醒。
本公开实施例通过在被叫端RCS APP不在线时进行唤醒操作，从而实时通知到被叫用户来接听通话，使得呼叫建立成功，满足用户及时通讯的需求。
如图5所示，本公开实施例还提供一种业务呼叫的实现设备，包括：存储器41、处理器42及存储在存储器41上并可在处理器42上运行的计算机程序43。所述处理器42执行所述计算机程序43时实现根据本公开各实施例的业务呼叫的实现方法。
本公开实施例还提供一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器运行时，使得所述处理器执行根据本公开各实施例的业务呼叫的实现方法。
在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)。如本 领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。

Claims (11)

  1. 一种业务呼叫的实现方法，包括：
    确定主叫端发起呼叫而被叫端的融合通信系统应用RCS APP不在线；
    唤醒被叫端的RCS APP；以及
    寻呼被叫端的RCS APP。
  2. 如权利要求1所述的方法，其中，确定主叫端发起呼叫而被叫端的RCS APP不在线的步骤包括：
    根据接收到的RCS APP不在线的响应消息，确定被叫端的RCS APP不在线。
  3. 如权利要求1所述的方法，其中，唤醒被叫端的RCS APP的步骤包括：
    通过发送推送消息唤醒被叫端的RCS APP。
  4. 如权利要求3所述的方法，其中，通过发送推送消息唤醒被叫端的RCS APP的步骤包括：
    将所述推送消息发送至永远在线推送平台AOI，以使所述AOI通过消息推送服务器唤醒被叫端的RCS APP。
  5. 如权利要求4所述的方法，其中，在将所述推送消息发送至AOI的步骤之前，所述方法还包括：
    通过查询数据库确定所述被叫端的终端类型和令牌信息。
  6. 如权利要求5所述的方法，其中，将所述推送消息发送至AOI的步骤包括：
    将所述终端类型和所述令牌信息携带在所述推送消息中，发送至所述AOI。
  7. 如权利要求3至6中任意一项所述的方法，其中，在通过发送推送消息唤醒被叫端的RCS APP的步骤之后，所述方法还包括：
    向所述主叫端发送回铃音指令。
  8. 如权利要求3至6中任意一项所述的方法，其中，在通过发送推送消息唤醒被叫端的RCS APP的步骤之后，所述方法还包括：
    根据接收到的所述RCS APP发送的注册消息，确定所述RCS APP已被唤醒。
  9. 一种业务呼叫的实现装置，包括：
    确定模块，用于确定主叫端发起呼叫而被叫端的RCS APP不在线；
    唤醒模块，用于唤醒被叫端的RCS APP；以及
    寻呼模块，用于寻呼被叫端的RCS APP。
  10. 一种业务呼叫的实现设备，包括：存储器、处理器及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现权利要求1至8中任意一项所述业务呼叫的实现方法。
  11. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器运行时，使得所述处理器执行权利要求1至8中任意一项所述业务呼叫的实现方法。
PCT/CN2020/083731 2019-04-23 2020-04-08 业务呼叫的实现方法、装置和设备 WO2020216063A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910328927.0 2019-04-23
CN201910328927.0A CN111836254B (zh) 2019-04-23 2019-04-23 一种业务呼叫的实现方法、装置和设备

Publications (1)

Publication Number Publication Date
WO2020216063A1 true WO2020216063A1 (zh) 2020-10-29

Family

ID=72912238

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/083731 WO2020216063A1 (zh) 2019-04-23 2020-04-08 业务呼叫的实现方法、装置和设备

Country Status (2)

Country Link
CN (1) CN111836254B (zh)
WO (1) WO2020216063A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113840245B (zh) * 2021-11-16 2023-03-31 中国电信股份有限公司 用于rcs消息的通信方法和通信系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103051863A (zh) * 2011-10-17 2013-04-17 腾讯科技（深圳）有限公司 一种会话发起方法和系统
CN103905374A (zh) * 2012-12-24 2014-07-02 中国移动通信集团公司 一种呼叫方法、系统和设备
US20140301258A1 (en) * 2013-04-09 2014-10-09 Broadcom Corporation Sip signaling cut-through
CN104426893A (zh) * 2013-09-09 2015-03-18 中国移动通信集团公司 唤醒移动终端的方法、装置及系统
CN105554000A (zh) * 2015-08-13 2016-05-04 伍威 一种网络电话唤醒方法
CN106470194A (zh) * 2015-08-20 2017-03-01 中兴通讯股份有限公司 网络电话连接处理方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6526131B1 (en) * 1999-04-30 2003-02-25 Hewlett-Packard Company Initiation of communication between network service system and customer-premises equipment
CN102377887B (zh) * 2010-08-12 2015-08-12 中兴通讯股份有限公司 一种实现网络电话呼叫建立的方法及系统
CN103475792B (zh) * 2012-06-08 2015-12-09 上海鱼游网络科技有限公司 一种接收离线网络电话呼叫的方法及系统
CN103905674A (zh) * 2012-12-24 2014-07-02 中国电信股份有限公司 应用于互联网与电信网双网通信的装置和方法
US9094050B2 (en) * 2013-01-25 2015-07-28 Blackberry Limited Methods and apparatus to facilitate device-to-device communication

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103051863A (zh) * 2011-10-17 2013-04-17 腾讯科技（深圳）有限公司 一种会话发起方法和系统
CN103905374A (zh) * 2012-12-24 2014-07-02 中国移动通信集团公司 一种呼叫方法、系统和设备
US20140301258A1 (en) * 2013-04-09 2014-10-09 Broadcom Corporation Sip signaling cut-through
CN104426893A (zh) * 2013-09-09 2015-03-18 中国移动通信集团公司 唤醒移动终端的方法、装置及系统
CN105554000A (zh) * 2015-08-13 2016-05-04 伍威 一种网络电话唤醒方法
CN106470194A (zh) * 2015-08-20 2017-03-01 中兴通讯股份有限公司 网络电话连接处理方法及装置

Also Published As

Publication number Publication date
CN111836254A (zh) 2020-10-27
CN111836254B (zh) 2023-05-26

Similar Documents

Publication Publication Date Title
US10736078B1 (en) Dynamic muting of communication notifications
US10212192B2 (en) Systems and methods for interworking with over the top applications in communications network
US10827065B2 (en) Systems and methods for providing integrated computerized personal assistant services in telephony communications
US9736298B2 (en) Voice to text conversion during active call including voice
WO2017028567A1 (zh) 网络电话连接处理方法及装置
WO2014206281A1 (zh) 移动终端的呼叫方法、控制移动终端的方法及相关设备
AU2018350926B2 (en) Personalized audio/video invitations for phone calls
US9210110B2 (en) Predictive messaging service for active voice calls
WO2017161723A1 (zh) 一种补充业务的实现方法以及终端
WO2022257851A1 (zh) 语音通话方法和语音通话装置
WO2021103214A1 (zh) 呼叫的方法、存储介质以及终端
US9924042B2 (en) Uniform RCS voice/videomail services
EP2974159B1 (en) Method, device and system for voice communication
WO2020216063A1 (zh) 业务呼叫的实现方法、装置和设备
WO2020073793A1 (zh) 状态提示多媒体播放的方法、系统及装置
CN105704684B (zh) 一种彩铃的实现方法、装置、服务器及系统
US20150031341A1 (en) Method for responding to push notification based communication request
CN107920174B (zh) 一种网络电话呼叫方法和装置
US20200084286A1 (en) Method, apparatus and system for call prompting
CN114980066B (zh) 语音通话方法、装置及电子设备
WO2017166642A1 (zh) 移动终端通话重拨方法、装置及移动终端
EP2949083A1 (en) Receiving a communication event
WO2016107511A1 (zh) 一种视频通信方法、终端及系统
US11909782B2 (en) Systems and methods for using machine learning techniques for network-implemented spam call detection
US11751036B2 (en) Emergency rich communication services

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: 20795186

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 14.12.2021)

122 Ep: pct application non-entry in european phase

Ref document number: 20795186

Country of ref document: EP

Kind code of ref document: A1