WO2020135684A1 - Rcs系统间的文件传输方法、rcs互通网关、存储介质及电子装置 - Google Patents

Rcs系统间的文件传输方法、rcs互通网关、存储介质及电子装置 Download PDF

Info

Publication number
WO2020135684A1
WO2020135684A1 PCT/CN2019/129057 CN2019129057W WO2020135684A1 WO 2020135684 A1 WO2020135684 A1 WO 2020135684A1 CN 2019129057 W CN2019129057 W CN 2019129057W WO 2020135684 A1 WO2020135684 A1 WO 2020135684A1
Authority
WO
WIPO (PCT)
Prior art keywords
rcs
file
interworking gateway
transmission
called
Prior art date
Application number
PCT/CN2019/129057
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 WO2020135684A1 publication Critical patent/WO2020135684A1/zh

Links

Images

Classifications

    • 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/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • 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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • 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/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion

Definitions

  • This application relates to the field of communications, for example, to a file transmission method between RCS systems, RCS interworking gateways, storage media, and electronic devices.
  • the RCS solution is an Internet-oriented information and communication technology (Information and Communications, Technology, ICT) converged communication service. It is different from the interconnection at the network level. It is based on human-oriented application level integration and collaboration. It is a higher-level concept and a new generation. Communication and Internet technology (Internet Technology (IT) fusion business. Help operators to take advantage of telecommunications network communications and build the business of Internet ICT converged communication network with user social relationship database as the core.
  • ICT Internet Technology
  • VoIP Voice over Internet Protocol
  • IM instant messaging
  • RCS As the future development direction of communication technology, has been in full swing in the world, and as an Internet-based communication platform, RCS provides users with the experience of communicating on the Internet.
  • the business process of the RCS system includes a file transfer business process, but due to the complexity of the RCS specification, the file transfer process has two branches in the protocol, namely the Message Session Relay Protocol (Message Session Relay Protocol (MSRP) file transfer and super For text transfer protocol (HyperTextTransferProtocol, HTTP) file transfer, the older RCS system generally uses the MSRP file transfer process, and the newer RCS system generally uses the HTTP file transfer process. And RCS systems that use different file transfer processes cannot communicate with each other.
  • MSRP Message Session Relay Protocol
  • HTTP HyperTextTransferProtocol
  • Embodiments of the present application provide a file transmission method between RCS systems, an RCS interworking gateway, a storage medium, and an electronic device, to at least solve the problem that file transmission services cannot be communicated between RCS systems using different file transmission processes in the related art.
  • a file transmission method between RCS systems including: an RCS interworking gateway is respectively connected to a calling side RCS system and a called side RCS system; the RCS interworking gateway passes the first file The transmission protocol receives the transmission file from the calling-side RCS system; the RCS interworking gateway transmits the transmission file to the called-side RCS system through the second file transmission protocol.
  • an RCS interworking gateway including: an access module configured to connect the RCS interworking gateway to a calling-side RCS system and a called-side RCS system, respectively; a receiving module, It is set to receive the transfer file from the calling-side RCS system through the first file transfer protocol; the sending module is set to transfer the transfer file to the called-side RCS system through the second file transfer protocol.
  • a storage medium in which a computer program is stored, wherein the computer program is configured to execute the method in any one of the above method embodiments at runtime.
  • an electronic device including a memory and a processor, the memory stores a computer program, the processor is configured to run the computer program to perform any of the above The method in the method embodiment.
  • FIG. 1 is a schematic diagram of an RCS multi-port repeater (HUB) networking provided by an embodiment of the present application;
  • FIG. 2 is a schematic diagram of an RCS interworking gateway networking provided by an embodiment of the present application.
  • FIG. 3 is a flow chart of file transmission and interworking between RCS systems provided by an embodiment of the present application.
  • FIG. 5 is a flow chart of HTTP to MSRP file transmission and interworking provided by an embodiment of the present application
  • FIG. 7 is another flowchart of HTTP to MSRP file transmission and interworking provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of an RCS interworking gateway provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of another RCS interworking gateway provided by an embodiment of the present application.
  • Embodiments of the present application provide a method for interworking file transmission services between converged communication systems, so that file transmission services can also be communicated between RCS systems using different file transmission protocols.
  • FIG. 1 is a schematic diagram of an RCS HUB networking provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of an RCS interworking gateway networking provided by an embodiment of the present application.
  • the operator is directly connected to the RCS HUB, and uses a star-shaped networking method to achieve interoperability between RCS systems of different operators.
  • operators deploy their own RCS interworking gateways and use two-to-one interconnection to achieve interworking between RCS systems of different operators.
  • the network architecture shown in FIGS. 1 and 2 is only a schematic, and does not limit the above-mentioned architecture.
  • the network structure may also include more or fewer network elements than shown in FIG. 1 or FIG. 2.
  • the above RCS interworking gateway (IWG) or RCS HUB devices are collectively referred to as RCS interworking gateway in the following embodiments of the present application.
  • the file transmission method between RCS systems runs on the above network architecture.
  • the RCS system that initiates file transmission is the calling side RCS system
  • the RCS system that receives the file is the called side RCS system.
  • the calling-side RCS system uses the first file transfer protocol
  • the called-side RCS system uses the second file transfer protocol.
  • the method flow of this embodiment includes the following steps:
  • Step S302 the RCS interworking gateway respectively accesses the calling side RCS system and the called side RCS system.
  • Step S304 the RCS interworking gateway receives the transmission file from the calling-side RCS system through the first file transmission protocol.
  • Step S306 The RCS interworking gateway transmits the transmission file to the called RCS system through a second file transmission protocol.
  • the first file transfer protocol may be MSRP file transfer protocol or HTTP file transfer protocol.
  • the second file transfer protocol is HTTP file transfer protocol or MSRP file transfer protocol.
  • the RCS interworking gateway when the RCS interworking gateway is started, the RCS interworking gateway may be respectively connected to the RCS system as a user equipment (User Equipment, UE). Or the RCS interworking gateway serves as an application server (Application Server, AS), and uses a network node interface (Network to Network Interface, NNI) to connect with the RCS system.
  • UE User Equipment
  • AS Application Server
  • NNI Network to Network Interface
  • the RCS interworking gateways can implement protocol adaptation according to the process of the RCS system, therefore, interworking of file transfer services between RCS systems is realized.
  • the calling side uses the MSRP file transfer protocol
  • the called side uses HTTP file transfer.
  • the method of this embodiment includes the following steps:
  • the RCS interworking gateway configures the file transfer service parameters of the calling side and the called side, including the transmission protocol and file size limit, respectively.
  • the RCS interworking gateway accesses the RCS system as a UE; or the RCS interworking gateway serves as an AS and uses NNI to connect with the RCS system.
  • the calling user initiates a file transfer process, and the MSRP channel is created between the calling RCS system and the RCS interworking gateway through the Session Initial Protocol (SIP) protocol.
  • SIP Session Initial Protocol
  • the calling side RCS system transmits the file content to the RCS interworking gateway through the MSRP channel.
  • the RCS interworking gateway transmits the file to the called side RCS system through the HTTP file transmission mechanism.
  • step S4040 the following three transmission schemes can be adopted according to the calling server HTTP server networking scheme and the called party RCS system security requirements.
  • the RCS interworking gateway can transfer the file to the called RCS system through the following steps a10 to a30.
  • the RCS interworking gateway uploads the file to the file server on the called side.
  • a20 The file server on the called side returns the Uniform Resource Locator (URL) address of the file to the RCS interworking gateway.
  • URL Uniform Resource Locator
  • the RCS interworking gateway sends information such as the URL of the file to the RCS system on the called side through an HTTP file transmission message.
  • the RCS interworking gateway can transfer the file to the called party through the following steps b10 to b30 Side RCS system.
  • the RCS interworking gateway generates URL addresses for locally cached files.
  • the RCS interworking gateway sends information such as the URL of the file to the RCS system on the called side through an HTTP file transmission message.
  • the called RCS system downloads the file to the local HTTP file server and generates its own URL for the file.
  • the RCS interworking gateway can transfer the file to the called RCS system through the following steps c10 to c20.
  • the RCS interworking gateway generates URL addresses for locally cached files.
  • the RCS interworking gateway sends the information such as the URL of the file to the RCS system on the called side through an HTTP file transmission message.
  • mapping between the MSRP file transfer protocol and the HTTP file transfer protocol is shown in Table 1 and Table 2.
  • the RCS interworking gateway starts, and the RCS interworking gateway accesses the RCS system as the UE; or, the RCS interworking gateway serves as an AS and uses NNI to connect with the RCS system.
  • the calling user initiates a file transmission process, and the calling side RCS system sends the file information to the RCS interworking gateway through the RCS HTTP file transmission message.
  • the RCS interworking gateway uses HTTP protocol to download the file to the local according to the file URL.
  • the RCS interworking gateway creates an MSRP channel with the called RCS system through the SIP protocol.
  • the RCS interworking gateway sends the locally cached file content to the called side RCS system through the MSRP protocol.
  • the calling party uses HTTP and the called party uses MSRP for file transmission and interworking.
  • MSRP protocol mapping of MSRP file transmission to HTTP file transmission
  • an email system is sent to send an email notification to an RCS user terminal.
  • the interworking solution of this embodiment includes the following steps:
  • the calling terminal A initiates a file transfer process, and sends an INVITE to the calling RCS system (ie, RCS 1) to create a session.
  • RCS system ie, RCS 1
  • the calling side RCS system accepts the INVITE request and sends an INVITE request to the RCS interworking gateway (ie, IGW) to create a session.
  • RCS interworking gateway ie, IGW
  • the RCS interworking gateway returns an INVITE response to the calling-side RCS system to negotiate the MSRP media channel.
  • the calling-side RCS system returns an INVITE response to the calling-side terminal to negotiate the MSRP media channel.
  • the terminal on the calling side sends a correct response (Acknowledgement, ACK) to the RCS system on the calling side, and creates an MSRP channel.
  • ACK Acknowledgement
  • the RCS system on the calling side sends an ACK to the RCS interworking gateway and creates an MSRP channel.
  • the calling side terminal sends the file content to the calling side RCS system through the MSRP channel.
  • the calling RCS system sends the file content to the RCS interworking gateway through the MSRP channel.
  • the RCS interworking gateway sends the file URL to the called RCS system through the offline (Standalone) or chat (Chat) process.
  • the called RCS system sends the file URL to the called terminal B through the Standalone or Chat process.
  • the called terminal B returns a response to the called RCS system.
  • the called RCS system returns a response to the RCS interworking gateway.
  • the terminal on the called side downloads the file to the local via the HTTP protocol according to the file URL.
  • the calling party uses the MSRP file transfer protocol
  • the called party uses the HTTP file transfer protocol to communicate with each other.
  • the interworking solution in this embodiment may include the following steps:
  • the calling terminal (phone A) uploads the file to the calling RCS system.
  • the calling-side terminal sends the file URL to the calling-side RCS system through the Standalone or Chat process.
  • the calling side RCS system returns a response to the calling side terminal.
  • the calling side RCS system sends the file URL to the RCS interworking gateway through the Standalone or Chat process.
  • the RCS interworking gateway returns a response to the calling side RCS system.
  • the RCS interworking gateway downloads the file to the local according to the file URL through the HTTP protocol.
  • the RCS interworking gateway sends an INVITE request to the called side RCS system.
  • the called side RCS system sends an INVITE request to the called side terminal.
  • the called terminal returns an INVITE response to the called RCS system to negotiate the MSRP media channel.
  • the called RCS system returns an INVITE response to the RCS interworking gateway to negotiate the MSRP media channel.
  • the RCS interworking gateway sends an ACK request to the called RCS system and creates an MSRP channel.
  • the called side RCS system sends an ACK request to the called side terminal, and creates an MSRP channel.
  • the RCS interworking gateway sends the file content to the called terminal through the MSRP channel.
  • the calling side uses the HTTP file transfer protocol
  • the called side uses the MSRP file transfer protocol to communicate with each other.
  • the method according to the above embodiments can be implemented by means of software plus a necessary universal hardware platform, and of course, it can also be implemented by hardware.
  • the technical solution of the present application can be essentially embodied in the form of a software product, and the computer software product is stored in a storage medium (such as Read-Only Memory (ROM)/Random Access Memory (Random Access (Memory, RAM), magnetic disk, and optical disk) include instructions to enable a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to perform the method described in the embodiments of the present application.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • magnetic disk magnetic disk
  • optical disk include instructions to enable a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to perform the method described in the embodiments of the present application.
  • an RCS interworking gateway is also provided.
  • the RCS interworking gateway is used to implement the foregoing embodiments and implementation modes, and descriptions that have already been described will not be repeated.
  • the term "module” may implement a combination of software and/or hardware that performs predetermined functions.
  • FIG. 8 is a structural block diagram of an RCS interworking gateway provided by an embodiment of the present application. As shown in FIG. 8, the RCS interworking gateway 100 includes an access module 10, a receiving module 20, and a sending module 30.
  • the access module 10 is configured to connect the RCS interworking gateway to the calling-side RCS system and the called-side RCS system, respectively.
  • the receiving module 20 is configured to receive the transmission file from the calling-side RCS system through the first file transmission protocol.
  • the sending module 30 is configured to transfer the transferred file to the called side RCS system through a second file transfer protocol.
  • the first file transfer protocol may be an HTTP file transfer protocol or an MSRP file transfer protocol
  • the second file transfer protocol may be an MSRP file transfer protocol or an HTTP file transfer protocol
  • FIG. 9 is a structural block diagram of another RCS interworking gateway provided by an embodiment of the present application.
  • the receiving module 20 includes a first creating unit 201 and a first receiving unit 202.
  • the sending module 30 includes an uploading unit 301, a first sending unit 302, a cache unit 303, and a second sending unit 304.
  • the first creating unit 201 is configured to create an MSRP channel between the RCS interworking gateway and the calling-side RCS system.
  • the first receiving unit 202 is configured to receive the transmission file from the calling-side RCS system through the MSRP channel.
  • the uploading unit 301 is configured to upload the transmission file to the HTTP file server on the called side.
  • the first sending unit 302 is configured to send the URL information of the transferred file to the RCS system on the called side through an HTTP file transfer message.
  • the cache unit 303 is configured to locally cache the transmission file and generate URL address information of the transmission file.
  • the second sending unit 304 is used to send the URL information to the RCS system on the called side through an HTTP file transmission message.
  • the receiving module 20 may further include a second receiving unit 203 and a downloading unit 204.
  • the sending module 30 may further include a second creating unit 305 and a third sending unit 306.
  • the second receiving unit 203 is configured to receive the URL information of the transmission file sent by the calling-side RCS system through an HTTP file transmission message.
  • the downloading unit 204 is configured to download the transmission file locally based on the HTTP information based on the HTTP protocol.
  • the second creating unit 305 is configured to create an MSRP channel between the RCS interworking gateway and the called-side RCS system.
  • the third sending unit 306 is configured to send the transmission file to the called side RCS system through the MSRP channel.
  • the RCS interworking gateway can provide different business process adaptation solutions according to the security requirements of the RCS system, so as to achieve file transmission and interworking between different RCS systems.
  • the above modules or units can be implemented by software or hardware. For the latter, they can be implemented in the following ways, but not limited to this: the above modules or units are all located in the same processor; or, the above modules are respectively combined in any combination Located in different processors.
  • An embodiment of the present application further provides a storage medium in which a computer program is stored, wherein the computer program is configured to execute any of the steps in the above method embodiments during runtime.
  • the above storage medium may include, but is not limited to: Universal Serial Bus flash disk (Universal Serial Bus flash disk, U disk), ROM, RAM, mobile hard disk, magnetic disk or optical disk, etc.
  • Universal Serial Bus flash disk Universal Serial Bus flash disk, U disk
  • ROM Read Only Memory
  • RAM Random Access Memory
  • mobile hard disk magnetic disk or optical disk
  • etc. A medium that can store computer programs.
  • An embodiment of the present application further provides an electronic device, including a memory and a processor, where the computer program is stored in the memory, and the processor is configured to run the computer program to perform the steps in any one of the foregoing method embodiments.
  • a solution for interworking file transfer services between RCS systems using different file transfer processes can be realized, that is, terminals that support the MSRP file transfer protocol can be used to send files to terminals that use the HTTP file transfer protocol, and HTTP The terminal of the file transfer protocol sends the file to the terminal adopting the MSRP file transfer protocol.
  • the commercial cost of this solution is low, and different networking solutions can be planned according to the network characteristics of the operator, so that the operator can develop RCS at the same time more convenient and improve the user experience.
  • modules or units or steps of the present application can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, optionally, they can be used in computing
  • the device executable program code is implemented so that they can be stored in the storage device to be executed by the computing device, and in some cases, the steps shown or described can be performed in an order different from here, or They are made into multiple integrated circuit modules respectively, or multiple modules or steps in them are made into a single integrated circuit module for implementation. In this way, this application is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

本文公开了一种RCS系统间的文件传输方法、RCS互通网关、存储介质及电子装置，该方法包括：RCS互通网关分别接入到主叫侧RCS系统和被叫侧RCS系统；所述RCS互通网关通过第一文件传输协议接收来自所述主叫侧RCS系统的传输文件；所述RCS互通网关通过第二文件传输协议将所述传输文件传输至所述被叫侧RCS系统。

Description

RCS系统间的文件传输方法、RCS互通网关、存储介质及电子装置
本申请要求在2018年12月29日提交中国专利局、申请号为201811648089.7的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，例如，涉及一种融合通信(Rich Communication Suite，RCS)系统间的文件传输方法、RCS互通网关、存储介质及电子装置。
背景技术
RCS解决方案是面向互联网的信息与通信技术(Information and Communications Technology，ICT)融合通信业务，它区别于网络层面的互联互通，是以人为本的应用层面融合与协同，是更高层次的理念和新一代通信与互联网技术(Internet Technology，IT)融合的业务。帮助运营商借助电信网络通信的优势，以用户社会关系库为核心，打造互联网ICT融合通信网络的业务。通过向互联网厂家、企业开放合作融合通信的能力，整合基于互联网协议(Internet Protocol，IP)的语音传输(Voice over Internet Protocol，VoIP)、即时通讯(Instant Message，IM)通信管道到融合通信网络，沉淀用户的信息资产，提升移动互联网流量的价值，开辟新的市场空间。
RCS作为未来通信技术的发展方向，已经如火如荼地在全球范围内开始建设，作为互联网化通讯平台，RCS为用户提供了在互联网上通信的体验。RCS系统的业务流程中包含了文件传输业务流程，但是由于RCS规范的复杂性，文件传输流程在协议上有两个分支，即消息会话中继协议(Message Session Relay Protocol，MSRP)文件传输和超文本传输协议(Hyper Text Transfer Protocol，HTTP)文件传输，较早的RCS系统一般采用MSRP文件传输流程，较新的RCS系统一般采用HTTP文件传输流程。而使用不同文件传输流程的RCS系统之间，是不能互通文件传输业务的。
发明内容
本申请实施例提供了一种RCS系统间的文件传输方法、RCS互通网关、存储介质及电子装置，以至少解决相关技术中使用不同文件传输流程的RCS系统之间不能互通文件传输业务的问题。
根据本申请的一个实施例，提供了一种RCS系统间的文件传输方法，包括：RCS互通网关分别接入到主叫侧RCS系统和被叫侧RCS系统；所述RCS互通 网关通过第一文件传输协议接收来自所述主叫侧RCS系统的传输文件；所述RCS互通网关通过第二文件传输协议将所述传输文件传输至所述被叫侧RCS系统。
根据本申请的另一个实施例，提供了一种RCS互通网关，包括：接入模块，设置为将所述RCS互通网关分别接入到主叫侧RCS系统和被叫侧RCS系统；接收模块，设置为通过第一文件传输协议接收来自所述主叫侧RCS系统的传输文件；发送模块，设置为通过第二文件传输协议将所述传输文件传输至所述被叫侧RCS系统。
根据本申请的又一个实施例，还提供了一种存储介质，所述存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的方法。
根据本申请的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的方法。
附图说明
图1是本申请实施例提供的一种RCS多端口转发器(HUB)组网示意图；
图2是本申请实施例提供的一种RCS互通网关组网示意图；
图3是本申请实施例提供的一种RCS系统间文件传输互通流程图；
图4是本申请实施例提供的一种MSRP到HTTP文件传输互通流程图；
图5是本申请实施例提供的一种HTTP到MSRP文件传输互通流程图；
图6是本申请实施例提供的另一种MSRP到HTTP文件传输互通流程图；
图7是本申请实施例提供的另一种HTTP到MSRP文件传输互通流程图；
图8是本申请实施例提供的一种RCS互通网关结构示意图；
图9是本申请实施例提供的另一种RCS互通网关结构示意图。
具体实施方式
下文中将参考附图并结合实施例来说明本申请。
本文中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请实施例提供了一种融合通信系统之间的文件传输业务互通的方法， 用于使得使用不同文件传输协议的RCS系统之间，也能互通文件传输业务。
首先描述本申请方法实施例所运行的网络架构。在本申请实施例中，在RCS系统之间增加RCS互通网关(Interworking Gateway，IWG)或RCS HUB设备。图1为本申请实施例提供的一种RCS HUB组网示意图，图2为本申请实施例提供的一种RCS互通网关组网示意图。如图1所示，运营商与RCS HUB直接连接，并采用星型组网方式实现不同运营商的RCS系统之间互通。如图2所示，运营商通过自行部署RCS互通网关，并采用两两互联的网状方式实现不同运营商的RCS系统之间互通。
图1和图2所示的网络架构仅为示意，其并不对上述的架构造成限定。例如，网络结构还可包括比图1或图2中所示更多或者更少的网元。为了描述方便，上述的RCS互通网关(IWG)或RCS HUB设备在本申请下文实施例中均统称为RCS互通网关。
本申请实施例所提供的RCS系统间的文件传输的方法运行在上述的网络架构上。为了便于描述，在本实施例中，发起文件传输的RCS系统为主叫侧RCS系统，接收文件的RCS系统为被叫侧RCS系统。主叫侧RCS系统使用第一文件传输协议，被叫侧RCS系统使用第二文件传输协议。
如图3所示，本实施例的方法流程包括如下步骤：
步骤S302，RCS互通网关分别接入到主叫侧RCS系统和被叫侧RCS系统。
步骤S304，所述RCS互通网关通过第一文件传输协议接收来自所述主叫侧RCS系统的传输文件。
步骤S306，所述RCS互通网关通过第二文件传输协议将所述传输文件传输至所述被叫侧RCS系统。
在本实施例中，第一文件传输协议可以为MSRP文件传输协议或HTTP文件传输协议。对应地，所述第二文件传输协议则为HTTP文件传输协议或MSRP文件传输协议。
在本实施例中，在RCS互通网关启动时，RCS互通网关可以以用户设备(User Equipment，UE)的身份分别接入到RCS系统。或者RCS互通网关作为应用服务器(Application Server，AS)，使用网络结点接口(Network to Network Interface，NNI)与RCS系统对接。
在上述实施例中，通过在不同的RCS系统之间增加RCS互通网关，RCS互通网关可根据RCS系统的流程实现协议的适配，因此，实现了RCS系统之间文件传输业务的互通。
下面将通过本申请的另一实施例对上述的文件传输互通技术方案进行描述。
在本实施例中，主叫侧采用MSRP文件传输协议，而被叫侧采用HTTP的文件传输。如图4所示，本实施例的方法包括如下步骤：
S4010，RCS互通网关分别配置主叫侧和被叫侧的文件传输业务参数，包括传输协议、文件大小限制等。
S4020，在RCS互通网关启动时，RCS互通网关以UE的身份接入RCS系统；或RCS互通网关作为AS，使用NNI与RCS系统对接。
S4030，主叫用户发起文件传输流程，主叫侧RCS系统与RCS互通网关之间通过会话初始协议(Session Initial Protocol，SIP)协议创建MSRP通道。
S4040，主叫侧RCS系统将文件内容通过MSRP通道传送给RCS互通网关。
S4050，RCS互通网关通过HTTP文件传输机制将文件传送给被叫侧RCS系统。
在步骤S4040中，根据主叫侧HTTP服务器组网方案和被叫侧RCS系统的安全性要求可采用如下三种传送方案。
第一种方案，如果被叫侧RCS用户不能访问主叫侧RCS系统的HTTP文件服务器，则RCS互通网关可通过如下a10至a30步骤将文件传送给被叫侧RCS系统。
a10：RCS互通网关将文件上传到被叫侧文件服务器。
a20：被叫侧文件服务器将文件的统一资源定位符(Uniform Resource Rocator，URL)地址返回给RCS互通网关。
a30：RCS互通网关将文件的URL等信息通过HTTP文件传输消息发送给被叫侧RCS系统。
第二种方案，如果被叫侧RCS用户不能访问主叫侧RCS系统的HTTP文件服务器，但被叫侧RCS系统支持文件下载，则RCS互通网关可通过如下b10至b30步骤将文件传送给被叫侧RCS系统。
b10：RCS互通网关为本地缓存的文件生成URL地址。
b20：RCS互通网关将文件的URL等信息通过HTTP文件传输消息发送给被叫侧RCS系统。
b30：被叫侧RCS系统将文件下载到本地HTTP文件服务器，并为文件生成自己的URL。
第三种方案，如果被叫侧RCS用户可以访问主叫侧RCS系统的HTTP文件服务器，则RCS互通网关可通过如下步骤c10至c20将文件传送给被叫侧RCS系统。
c10：RCS互通网关为本地缓存的文件生成URL地址。
c20：RCS互通网关将文件的URL等信息通过HTTP文件传输消息发送给被叫侧RCS系统。
为了便于本实施例的理解，MSRP文件传输协议与HTTP文件传输协议之间的映射如表1和表2所示。
表1
Figure PCTCN2019129057-appb-000001
表2
Figure PCTCN2019129057-appb-000002
下面再通过另一实施例，描述主叫侧采用HTTP被叫侧采用MSRP的文件传输互通方案，步骤流程，如图5所示，包括如下步骤：
S5010，RCS互通网关启动，RCS互通网关以UE的身份接入RCS系统；或者，RCS互通网关作为AS，使用NNI与RCS系统对接。
S5020，主叫用户发起文件传输流程，主叫侧RCS系统通过RCS的HTTP文件传输消息将文件信息发送给RCS互通网关。
S5030，RCS互通网关使用HTTP协议根据文件的URL将文件下载到本地。
S5040，RCS互通网关通过SIP协议与被叫侧RCS系统创建MSRP通道。
S5050，RCS互通网关通过MSRP协议将本地缓存的文件内容发送给被叫侧RCS系统。
在实施例中，通过上述RCS互通网关的协议适配，实现了主叫侧采用HTTP被叫侧采用MSRP的文件传输互通，其中，MSRP文件传输到HTTP文件传输的协议映射可参考表1和表2。
下面提供了一个使用不同文件传输协议的RCS系统之间互通的应用实施例，在本实施例中，实现电子邮件系统发送电子邮件通知到RCS用户终端。
在本实施例中，假定主叫侧采用MSRP文件传输协议，而被叫侧采用HTTP的文件传输协议。如图6所示，本实施例的互通方案包括如下步骤：
S6010，主叫侧终端A发起文件传输流程，向主叫侧RCS系统(即，RCS 1)发送INVITE创建会话。
S6020，主叫侧RCS系统接受INVITE请求，并向RCS互通网关(即，IGW)发送INVITE请求创建会话。
S6030，RCS互通网关向主叫侧RCS系统返回INVITE响应，协商MSRP媒体通道。
S6040，主叫侧RCS系统向主叫侧终端返回INVITE响应，协商MSRP媒体通道。
S6050，主叫侧终端向主叫侧RCS系统发送正确应答(Acknowledgement，ACK)，并创建MSRP通道。
S6060，主叫侧RCS系统向RCS互通网关发送ACK，并创建MSRP通道。
S6070，主叫侧终端通过MSRP通道向主叫侧RCS系统发送文件内容。
S6080，主叫侧RCS系统通过MSRP通道向RCS互通网关发送文件内容。
S6090，RCS互通网关向被叫侧RCS系统通过脱机(Standalone)或者聊天(Chat)流程发送文件URL。
S6100，被叫侧RCS系统通过Standalone或者Chat流程向被叫侧终端B发送文件URL。
S6110，被叫侧终端B向被叫侧RCS系统返回响应。
S6120，被叫侧RCS系统向RCS互通网关返回响应。
S6130，被叫侧终端根据文件URL通过HTTP协议下载文件到本地。
在本实施例中，通过上述步骤，实现了主叫侧采用MSRP文件传输协议，而被叫侧采用HTTP的文件传输协议之间的文件传输互通。
再假定主叫侧采用HTTP文件传输协议，而被叫侧采用MSRP的文件传输些，则如图7所示，本实施例的互通方案可包括如下步骤：
S7010，主叫侧终端(电话(phone)A)将文件上传到主叫侧RCS系统。
S7020，主叫侧终端将文件URL通过Standalone或Chat流程发送给主叫侧RCS系统。
S7030，主叫侧RCS系统向主叫侧终端返回响应。
S7040，主叫侧RCS系统通过Standalone或Chat流程将文件URL发送给RCS互通网关。
S7050，RCS互通网关向主叫侧RCS系统返回响应。
S7060，RCS互通网关通过HTTP协议根据文件的URL将文件下载到本地。
S7070，RCS互通网关向被叫侧RCS系统发送INVITE请求。
S7080，被叫侧RCS系统向被叫侧终端发送INVITE请求。
S7090，被叫侧终端向被叫侧RCS系统返回INVITE响应，协商MSRP媒体通道。
S7100，被叫侧RCS系统向RCS互通网关返回INVITE响应，协商MSRP媒体通道。
S7110，RCS互通网关向被叫侧RCS系统发送ACK请求，并创建MSRP通道。
S7120，被叫侧RCS系统向被叫侧终端发送ACK请求，并创建MSRP通道。
S7130-S7140，RCS互通网关通过MSRP通道将文件内容发送给被叫侧终端。
在本实施例中，通过上述步骤，实现了主叫侧采用HTTP文件传输协议，而被叫侧采用MSRP的文件传输协议之间的文件传输互通。
通过以上的实施方式的描述，根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件。基于这样的理解，本申请的技术方案本质上可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如只读存储器(Read-Only Memory，ROM)/随机存取存储器 (Random Access Memory，RAM)、磁碟、光盘)中，包括一些指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本申请实施例所述的方法。
在本实施例中还提供了一种RCS互通网关，该RCS互通网关用于实现上述实施例及实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图8是本申请实施例提供的一种的RCS互通网关的结构框图，如图8所示，该RCS互通网关100包括接入模块10、接收模块20和发送模块30。
接入模块10设置为将所述RCS互通网关分别接入到主叫侧RCS系统和被叫侧RCS系统。接收模块20设置为通过第一文件传输协议接收来自所述主叫侧RCS系统的传输文件。发送模块30设置为通过第二文件传输协议将所述传输文件传输至所述被叫侧RCS系统。
在本实施例中第一文件传输协议可以为HTTP文件传输协议或MSRP文件传输协议，对应地，第二文件传输协议则可为MSRP文件传输协议或HTTP文件传输协议。
图9是本申请实施例提供的另一种RCS互通网关的结构框图，如图9所示，与图8所示的实施例相比，除了包括图8实施例所示的接入模块10、接收模块20和发送模块30外，在本实施例中，接收模块20包括第一创建单元201和第一接收单元202。发送模块30包括上传单元301、第一发送单元302、缓存单元303和第二发送单元304。
第一创建单元201设置为在所述RCS互通网关与所述主叫侧RCS系统之间创建MSRP通道。第一接收单元202设置为通过所述MSRP通道接收来自所述主叫侧RCS系统的所述传输文件。
上传单元301设置为将所述传输文件上传至被叫侧的HTTP文件服务器。第一发送单元302设置为将所述传输文件的URL信息通过HTTP文件传输消息发送给所述被叫侧RCS系统。缓存单元303设置为将所述传输文件本地缓存，并生成所述传输文件的URL地址信息。第二发送单元304用于将所述URL信息通过HTTP文件传输消息发送给所述被叫侧RCS系统。
在本实施例中，接收模块20还可包括第二接收单元203和下载单元204。发送模块30还可包括第二创建单元305和第三发送单元306。
第二接收单元203，设置为接收所述主叫侧RCS系统通过HTTP文件传输消息发送的所述传输文件的URL信息。下载单元204，设置为根据所述URL信 息基于HTTP协议将所述传输文件下载到本地。
第二创建单元305设置为在RCS互通网关与所述被叫侧RCS系统间创建MSRP通道。第三发送单元306设置为通过所述MSRP通道将所述传输文件发送至所述被叫侧RCS系统。
在本实施例中，RCS互通网关可以根据RCS系统的安全性要求，提供不同的业务流程适配方案，从而实现不同RCS系统间的文件传输互通。
上述模块或单元是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块或单元均位于同一处理器中；或者，上述模块以任意组合的形式分别位于不同的处理器中。
本申请的实施例还提供了一种存储介质，该存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
可选地，在本实施例中，上述存储介质可以包括但不限于：通用串行总线闪存盘(Universal Serial Bus flash disk，U盘)、ROM、RAM、移动硬盘、磁碟或者光盘等多种可以存储计算机程序的介质。
本申请的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
通过本申请上述实施例，可实现采用不同文件传输流程的RCS系统之间文件传输业务互通的方案，即支持采用MSRP文件传输协议的终端发送文件给采用HTTP文件传输协议的终端，也支持采用HTTP文件传输协议的终端发送文件给采用MSRP文件传输协议的终端。本方案商用成本低，且能根据运营商的网络特点规划不同的组网方案，使运营商在发展RCS的同时更加便捷，提升用户体验。
上述的本申请的模块或单元或步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在一些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成多个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本申请不限制于任何特定的硬件和软件结合。

Claims (20)

  1. 一种融合通信RCS系统间的文件传输方法，包括：
    RCS互通网关分别接入到主叫侧RCS系统和被叫侧RCS系统；
    所述RCS互通网关通过第一文件传输协议接收来自所述主叫侧RCS系统的传输文件；
    所述RCS互通网关通过第二文件传输协议将所述传输文件传输至所述被叫侧RCS系统。
  2. 根据权利要求1所述的方法，其中，所述RCS互通网关分别接入到主叫侧RCS系统和被叫侧RCS系统，包括：
    所述RCS互通网关以用户设备UE的身份分别接入到所述主叫侧RCS系统和所述被叫侧RCS系统；或
    所述RCS互通网关作为应用服务器，使用网络结点接口NNI分别与所述主叫侧RCS系统和所述被叫侧RCS系统对接。
  3. 根据权利要求1所述的方法，其中，所述第一文件传输协议为消息会话中继协议MSRP文件传输协议，所述第二文件传输协议为超文本传输协议HTTP文件传输协议。
  4. 根据权利要求3所述的方法，其中，所述RCS互通网关通过第一文件传输协议接收来自所述主叫侧RCS系统的传输文件，包括：
    在所述RCS互通网关与所述主叫侧RCS系统之间创建MSRP通道；
    所述RCS互通网关通过所述MSRP通道接收来自所述主叫侧RCS系统的所述传输文件。
  5. 根据权利要求4所述的方法，其中，所述RCS互通网关通过第二文件传输协议将所述传输文件传输至所述被叫侧RCS系统，包括：
    所述RCS互通网关将所述传输文件上传至被叫侧的HTTP文件服务器；
    所述RCS互通网关将所述被叫侧的HTTP文件服务器返回的所述传输文件的统一资源定位符URL信息通过HTTP文件传输消息发送给所述被叫侧RCS系统。
  6. 根据权利要求4所述的方法，其中，所述RCS互通网关通过第二文件传输协议将所述传输文件传输至所述被叫侧RCS系统，包括：
    所述RCS互通网关将所述传输文件本地缓存，并生成所述传输文件的URL地址信息；
    所述RCS互通网关将所述URL地址信息通过HTTP文件传输消息发送给所 述被叫侧RCS系统。
  7. 根据权利要求6所述的方法，在所述RCS互通网关将所述URL地址信息通过HTTP文件传输消息发送给所述被叫侧RCS系统之后，还包括：
    所述被叫侧RCS系统根据所述URL地址信息将所述传输文件下载到被叫侧的文件服务器，并为所述传输文件生成新的URL地址信息。
  8. 根据权利要求1所述的方法，其中，所述第一文件传输协议为HTTP文件传输协议，所述第二文件传输协议为MSRP文件传输协议。
  9. 根据权利要求8所述的方法，其中，所述RCS互通网关通过第一文件传输协议接收来自所述主叫侧RCS系统的传输文件，包括：
    所述RCS互通网关接收所述主叫侧RCS系统通过HTTP文件传输消息发送的所述传输文件的URL信息；
    所述RCS互通网关根据所述URL信息基于所述HTTP文件传输协议将所述传输文件下载到本地。
  10. 根据权利要求9所述的方法，其中，所述RCS互通网关通过第二文件传输协议将所述传输文件传输至所述被叫侧RCS系统，包括：
    在所述RCS互通网关与所述被叫侧RCS系统间创建MSRP通道。
    所述RCS互通网关通过所述MSRP通道将所述传输文件发送至所述被叫侧RCS系统。
  11. 一种融合通信RCS互通网关，包括：
    接入模块，设置为将所述RCS互通网关分别接入到主叫侧RCS系统和被叫侧RCS系统；
    接收模块，设置为通过第一文件传输协议接收来自所述主叫侧RCS系统的传输文件；
    发送模块，设置为通过第二文件传输协议将所述传输文件传输至所述被叫侧RCS系统。
  12. 根据权利要求11所述的互通网关，其中，所述第一文件传输协议为消息会话中继协议MSRP文件传输协议，所述第二文件传输协议为超文本传输协议HTTP文件传输协议。
  13. 根据权利要求12所述的互通网关，其中，所述接收模块包括：
    第一创建单元，设置为在所述RCS互通网关与所述主叫侧RCS系统之间创建MSRP通道；
    第一接收单元，设置为通过所述MSRP通道接收来自所述主叫侧RCS系统的所述传输文件。
  14. 根据权利要求13所述的互通网关，其中，所述发送模块包括：
    上传单元，设置为将所述传输文件上传至被叫侧的HTTP文件服务器；
    第一发送单元，设置为将所述被叫侧的HTTP文件服务器返回的所述传输文件的统一资源定位符URL信息通过HTTP文件传输消息发送给所述被叫侧RCS系统。
  15. 根据权利要求13所述的互通网关，其中，所述发送模块包括：
    缓存单元，设置为将所述传输文件本地缓存，并生成所述传输文件的URL地址信息；
    第二发送单元，设置为将所述URL地址信息通过HTTP文件传输消息发送给所述被叫侧RCS系统。
  16. 根据权利要求11所述的互通网关，其中，所述第一文件传输协议为HTTP文件传输协议，所述第二文件传输协议为MSRP文件传输协议。
  17. 根据权利要求16所述的互通网关，其中，所述接收模块包括：
    第二接收单元，设置为接收所述主叫侧RCS系统通过HTTP文件传输消息发送的所述传输文件的URL信息；
    下载单元，设置为根据所述URL信息基于所述HTTP文件传输协议将所述传输文件下载到本地。
  18. 根据权利要求16所述的互通网关，其中，所述发送模块包括：
    第二创建单元，设置为在RCS互通网关与所述被叫侧RCS系统间创建MSRP通道。
    第三发送单元，设置为通过所述MSRP通道将所述传输文件发送至所述被叫侧RCS系统。
  19. 一种存储介质，存储有计算机程序，其中，所述计算机程序被设置为运行时执行所述权利要求1至10任一项中所述的融合通信RCS系统间的文件传输方法。
  20. 一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行所述权利要求1至10任一项中所述的融合通信RCS系统间的文件传输方法。
PCT/CN2019/129057 2018-12-29 2019-12-27 Rcs系统间的文件传输方法、rcs互通网关、存储介质及电子装置 WO2020135684A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811648089.7 2018-12-29
CN201811648089.7A CN111385277A (zh) 2018-12-29 2018-12-29 Rcs系统间的文件传输方法及rcs互通网关

Publications (1)

Publication Number Publication Date
WO2020135684A1 true WO2020135684A1 (zh) 2020-07-02

Family

ID=71127758

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/129057 WO2020135684A1 (zh) 2018-12-29 2019-12-27 Rcs系统间的文件传输方法、rcs互通网关、存储介质及电子装置

Country Status (2)

Country Link
CN (1) CN111385277A (zh)
WO (1) WO2020135684A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101207577A (zh) * 2006-12-19 2008-06-25 华为技术有限公司 消息系统间的互连方法及消息互连网关
CN101374248A (zh) * 2007-08-24 2009-02-25 上海华为技术有限公司 即时消息的处理方法及装置
US8295187B1 (en) * 2004-09-30 2012-10-23 Avaya Inc. Port-centric configuration methods for converged voice applications
CN105208535A (zh) * 2014-06-19 2015-12-30 中兴通讯股份有限公司 短信息互通的方法及装置
CN106161177A (zh) * 2015-03-24 2016-11-23 中兴通讯股份有限公司 实现语音信箱系统与融合通信系统互通的方法和系统
CN108156069A (zh) * 2017-12-26 2018-06-12 中兴通讯股份有限公司 一种融合消息系统及消息处理方法

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106470222A (zh) * 2015-08-18 2017-03-01 中兴通讯股份有限公司 一种文件传输方法、装置及应用服务器
CN106487644A (zh) * 2015-08-28 2017-03-08 中国移动通信集团公司 一种通信方法和系统
US10153993B2 (en) * 2016-07-18 2018-12-11 T-Mobile Usa, Inc. RCS origination forking

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8295187B1 (en) * 2004-09-30 2012-10-23 Avaya Inc. Port-centric configuration methods for converged voice applications
CN101207577A (zh) * 2006-12-19 2008-06-25 华为技术有限公司 消息系统间的互连方法及消息互连网关
CN101374248A (zh) * 2007-08-24 2009-02-25 上海华为技术有限公司 即时消息的处理方法及装置
CN105208535A (zh) * 2014-06-19 2015-12-30 中兴通讯股份有限公司 短信息互通的方法及装置
CN106161177A (zh) * 2015-03-24 2016-11-23 中兴通讯股份有限公司 实现语音信箱系统与融合通信系统互通的方法和系统
CN108156069A (zh) * 2017-12-26 2018-06-12 中兴通讯股份有限公司 一种融合消息系统及消息处理方法

Also Published As

Publication number Publication date
CN111385277A (zh) 2020-07-07

Similar Documents

Publication Publication Date Title
US10165015B2 (en) System and method for real-time communication by using a client application communication protocol
US10476915B2 (en) Real-time communication signaling gateway
US9648052B2 (en) Real-time communications gateway
US9509745B2 (en) Java API for programming web real-time communication applications
US9331967B2 (en) Browser/HTML friendly protocol for real-time communication signaling
CN104429037B (zh) 用于连接到通信设备的方法、设备及系统
WO2016070812A1 (en) Adaptive allocation of server resources
US9648049B2 (en) System and method for extending IP multimedia subsystem to HTML5 environments
US20120246226A1 (en) System and method for sharing data from a local network to a remote device
EP1971090A1 (en) A method, system and device for transmitting ims instant messages
KR20130135953A (ko) 할당된 네트워크 어드레스를 갖는 디바이스에 액세스하기 위해 웹 프록시-서버를 이용하는 시스템 및 방법
WO2014201931A1 (zh) 资源处理方法和站点服务器
EP2518972A1 (en) System and method for device addressing
KR20120117979A (ko) 대화 중에 복수의 통신 양식을 전송하는 것
US20230031062A1 (en) Data processing method and apparatus, related device, and storage medium
US20180176157A1 (en) Conveying instant messages via http
US20170019484A1 (en) System and method for aggregating communication connections
US20140250197A1 (en) Content server, terminal, and method using http
US9191359B2 (en) Techniques for VoIP provider interconnection over the internet using a shared subscriber contact identifier translation service
WO2016201795A1 (zh) 消息发送方法及装置
JP2012085299A (ja) 遠隔ダウンロードを行う方法、システム及び持続性コンピュータ可読記憶媒体
BRPI0710719A2 (pt) método para deletar um item de uma conta de usuário em um ambiente multimìdea sip; produto de programa de computador e dispositivo eletrÈnico
US9485283B2 (en) Method and apparatus for enabling communications between users
WO2017185934A1 (zh) 一种管理设备及设备管理方法
JP2018101424A (ja) ダイレクト電子メール

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

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 08/11/2021)

122 Ep: pct application non-entry in european phase

Ref document number: 19904709

Country of ref document: EP

Kind code of ref document: A1