技术领域technical field
本发明涉及文件传输，尤其涉及一种接收和删除输入文件的方法及系统。The invention relates to file transmission, in particular to a method and system for receiving and deleting input files.
背景技术Background technique
面对信息通信产业周期的演进以及消费者模式的变迁大潮，面对互联网的骨灰级创新模式以及新媒体的广泛传播、甚至是IT厂商、内容整合者与消费电子厂商向运营领域的渗透，电信运营商正在采取一种积极的融合、开放的态度，努力尝试开放其电信能力，集思广益，发挥第三方企业与个人的创新能力，打造丰富的增值应用；另一方面，借用这种电信服务的二次分发渠道，促进基本电信服务的销售。尤其是终端与软件厂商在在线应用商店市场烽烟四起之时，运营商必须要利用电信能力(可靠的通信服务；用户数据；情境；认证；计费等)打造一条新的差异化的道路。In the face of the evolution of the information and communication industry cycle and the changing tide of consumer models, the hardcore innovation model of the Internet and the widespread dissemination of new media, and even the penetration of IT manufacturers, content integrators and consumer electronics manufacturers into the operating field, telecommunications Operators are adopting an active integration and open attitude, trying to open up their telecommunication capabilities, brainstorming, giving full play to the innovation capabilities of third-party companies and individuals, and creating rich value-added applications; on the other hand, borrowing the second secondary distribution channels to facilitate the sale of basic telecommunication services. Especially when terminal and software vendors are booming in the online application store market, operators must use telecommunication capabilities (reliable communication services; user data; context; authentication; billing, etc.) to create a new road of differentiation.
1998年Parlay组织成立致力于为电话网络开发API(应用编程接口)。借助这些API，第三方机构可以创建自己的应用。Parlay组织在这方面做了统一的标准化工作，制定了基于CORBA(公共对象资源代理架构)的Parlay/OSA(开放服务架构)API，对各种电信能力的使用进行编程方面的统一工作。另外Parlay/OSA API也获得了ETSI(欧洲电信标准协会)与3GPP(第三代移动通信合作伙伴计划标准组织)共同协助。在3GPP中，Parlay被当成开放服务架构(OSA)的一部分。Parlay X是Parlay、3GPP和OMA(开放移动联盟)颁发的基于SOAP(简单对象访问协议)Web服务的API标准规范。Parlay REST(面向Parlay X的RESTful约束)，是OMA最新颁发的一套API标准规范，旨在为OMA中的Parlay X Web服务规范(子)集指定REST Web服务约束。In 1998, the Parlay organization was established to develop an API (Application Programming Interface) for the telephone network. With these APIs, third-party organizations can create their own applications. The Parlay organization has done a unified standardization work in this regard, formulated the Parlay/OSA (Open Service Architecture) API based on CORBA (Common Object Resource Agent Architecture), and unified the programming aspects of the use of various telecommunication capabilities. In addition, Parlay/OSA API has also been assisted by ETSI (European Telecommunications Standards Institute) and 3GPP (Third Generation Partnership Project Standards Organization). In 3GPP, Parlay is regarded as a part of Open Service Architecture (OSA). Parlay X is an API standard specification based on SOAP (Simple Object Access Protocol) Web services issued by Parlay, 3GPP and OMA (Open Mobile Alliance). Parlay REST (RESTful constraints for Parlay X) is a set of API standard specifications recently issued by OMA, which aims to specify REST Web service constraints for the Parlay X Web service specification (sub)set in OMA.
在Web 2.0领域，支持AjaX(异步JavaScript脚本和XML可扩展标签语言)技术的API相对应用比较广泛，风格为REST(REpresentational StateTransfer，表象化状态转变)。REST不是一种新技术，也不是一种标准，而是一组设计原则；与基于SOAP的Web服务(如Parlay X)相比，REST API更加轻量级，具有更优良的开发者友好性，便于Web应用的开发和Mashup。因此越来越多的Web服务开始采用REST风格设计和实现。例如，Amazon.com提供接近REST风格的Web服务进行图书查找；雅虎提供的Web服务也是REST风格的(维基百科)。In the field of Web 2.0, APIs that support AjaX (Asynchronous JavaScript Scripting and XML Extensible Tag Language) technology are relatively widely used, and the style is REST (REpresentational State Transfer, representational state change). REST is not a new technology, nor a standard, but a set of design principles; compared with SOAP-based web services (such as Parlay X), REST API is more lightweight and has better developer friendliness. Facilitate the development and Mashup of Web applications. Therefore, more and more Web services are designed and implemented in REST style. For example, Amazon.com provides a nearly REST-style Web service for book search; Yahoo provides a Web service that is also REST-style (Wikipedia).
GSMA(全球移动系统协会)RCS(富通信套件)是基于现有IMS(IP多媒体子系统)网络设施和开发协议搭建出来的提供可互操作的丰富通信功能的业务包，主要包括增强型地址簿、增强型呼叫、增强型融合消息等业务，使用户可以对自己的呈现(如个人图片、留言、推荐链接以及状态)进行更新，也可以在手机的通讯录中实时看到好友的呈现情况，并实现短信、彩信、聊天(即时消息)、文件传输等多种通信需求。RCS是包括运营商、设备商和手机终端厂商共同支持的统一的技术及实现标准，因此它不但容易培养消费者较为一致的使用习惯，而且可以实现不同国家、不同运营商的互联互通。后续阶段，RCS将进一步引入社交网络、开放式REST API应用编程接口、与互联网集成应用商店等内容。RCS REST风格API的目标用户是典型的Web开发商、第三方开发者、业务提供商，通过API可以将电信运营商的RCS业务能力和IMS网络能力开放，更适合Web 2.0Widget轻量级应用与Mashup的开发，迎合Web应用的发展趋势。GSMA (Global Mobile Systems Association) RCS (Rich Communication Suite) is a service package that provides interoperable and rich communication functions based on the existing IMS (IP Multimedia Subsystem) network facilities and development protocols, mainly including enhanced address book , Enhanced Call, Enhanced Converged Message and other services, so that users can update their own presentation (such as personal pictures, messages, recommended links, and status), and can also see the presence of friends in real time in the phone's address book. And to achieve SMS, MMS, chat (instant message), file transfer and other communication needs. RCS is a unified technology and implementation standard supported by operators, equipment manufacturers and mobile phone terminal manufacturers. Therefore, it is not only easy to cultivate consumers' consistent usage habits, but also can realize the interconnection of different countries and different operators. In the subsequent stage, RCS will further introduce content such as social networks, open REST API application programming interfaces, and integrated application stores with the Internet. The target users of the RCS REST style API are typical Web developers, third-party developers, and service providers. Through the API, the RCS service capabilities and IMS network capabilities of telecom operators can be opened, which is more suitable for Web 2.0 Widget lightweight applications and The development of Mashup caters to the development trend of Web applications.
目前，电信运营商短信、彩信的业务能力已经可以通过OMA(开放移动联盟)制定的ParlayREST2.0协议标准开放，而文件传输业务能力还没有制定相应的协议标准开放，用户还不能够调用电信能力在接收和删除输入文件。At present, the service capabilities of SMS and MMS of telecom operators can be released through the ParlayREST2.0 protocol standard developed by OMA (Open Mobile Alliance), but the file transfer service capability has not yet been developed and the corresponding protocol standard is opened, and users are not yet able to invoke telecom capabilities. Input files are received and deleted.
发明内容Contents of the invention
有鉴于此，本发明的一个目的在于提供一种接收输入文件的方法及系统，以解决用户不能调用电信能力接收输入文件的问题。In view of this, an object of the present invention is to provide a method and system for receiving input files, so as to solve the problem that users cannot invoke telecommunication capabilities to receive input files.
为了解决上述问题，本发明提供了一种接收输入文件的方法，该方法基于电信网络域提供的表象化状态转变(REST)应用编程接口(API)实现，包括：In order to solve the above-mentioned problem, the present invention provides a kind of method of receiving input file, and this method realizes based on the Representational State Transition (REST) Application Programming Interface (API) provided by the telecommunications network domain, comprising:
客户端以请求接收的输入文件为使用的资源，向服务器发送接收输入文件请求消息，携带所述资源的资源统一资源位置符(URL)；The client uses the input file requested to be received as the resource used, and sends a request message for receiving the input file to the server, carrying the resource uniform resource locator (URL) of the resource;
所述服务器收到所述接收输入文件请求消息后，获取所述输入文件的信息，向所述客户端返回接收输入文件响应消息，携带所述输入文件的信息。The server obtains the information of the input file after receiving the request message for receiving the input file, and returns a response message of receiving the input file to the client, carrying the information of the input file.
较佳地preferably
所述接收输入文件请求消息中包含使用的动作的信息，所述动作是超文本转换协议(HTTP)的获取(GET)动作，所述资源的资源URL包含终端参与者的用户标示符及文件传输会话的标示符中的至少一种。The received input file request message includes the information of the action used, the action is a hypertext transfer protocol (HTTP) acquisition (GET) action, and the resource URL of the resource includes the user identifier of the terminal participant and the file transfer At least one of session identifiers.
较佳地preferably
所述输入文件的信息包括以下信息中的至少一种：接收消息会话转播协议(MSRP)路径、发送MSRP路径、字节范围、成功报告、失败报告、接收者用户标示符、发送者用户标示符、文件日期、文件内容部署、文件内容类型和资源URL。The information of the input file includes at least one of the following information: receiving message session relay protocol (MSRP) path, sending MSRP path, byte range, success report, failure report, receiver user identifier, sender user identifier , file date, file content deployment, file content type, and resource URL.
较佳地preferably
客户端发送接收输入文件请求消息之前，按以下方式生成所述接收输入文件请求消息：Before the client sends the receive input file request message, the receive input file request message is generated in the following manner:
以HTTP的获取(GET)为使用的动作，以请求接收的输入文件为使用的资源，生成消息头，所述资源的资源URL包含请求接收输入文件的终端参与者的用户标示符和/或该终端参与者参与的相应文件传输会话的标示符；The HTTP acquisition (GET) is used as an action, and the input file requested to be received is used as a resource to generate a message header. The resource URL of the resource includes the user identifier of the terminal participant requesting to receive the input file and/or the the identifier of the corresponding file transfer session in which the end participant participated;
根据所述消息头生成接收输入文件请求消息。A request message for receiving an input file is generated according to the message header.
较佳地preferably
所述服务器接收输入文件成功，返回接收输入文件响应消息之前，按以下方式生成所述接收输入文件响应消息：The server receives the input file successfully, and before returning the response message of receiving the input file, generates the response message of receiving the input file in the following manner:
根据HTTP表示“成功(OK)”的响应符，生成消息头；Generate a message header according to the HTTP response indicating "success (OK)";
根据所述输入文件的信息生成一个文件的数据结构，作为消息体；generating a data structure of a file as a message body according to the information of the input file;
根据所述消息头和消息体生成接收输入文件响应消息。A response message for receiving an input file is generated according to the message header and the message body.
相应地，本发明提供的接收输入文件的系统中，客户端和服务器基于电信网络域提供的表象化状态转变(REST)应用编程接口(API)交互，该系统包括：Correspondingly, in the system for receiving input files provided by the present invention, the client and the server interact based on the Representational State Transition (REST) application programming interface (API) provided by the telecommunications network domain, and the system includes:
客户端中的消息生成装置，用于生成接收输入文件请求消息；A message generating device in the client, configured to generate a request message for receiving an input file;
客户端中的消息发送装置，用于向服务器发送所述接收输入文件请求消息；A message sending device in the client, configured to send the request message for receiving an input file to the server;
服务器中的消息接收和处理装置，用于收到接收输入文件请求消息后进行解析和处理，获取所述输入文件的信息；The message receiving and processing device in the server is used for parsing and processing after receiving the input file request message, and obtaining the information of the input file;
服务器中的消息生成装置，用于生成接收输入文件响应消息；A message generating device in the server, configured to generate a response message for receiving an input file;
服务器中的消息发送装置，用于向所述客户端返回所述接收输入文件响应消息。The message sending device in the server is used to return the response message of receiving the input file to the client.
较佳地preferably
所述客户端中的消息生成装置又包括：The message generation device in the client further includes:
消息头生成子装置，用于以HTTP的获取(GET)为使用的动作，以请求接收的输入文件为使用的资源，生成消息头，所述资源的资源URL包含请求接收输入文件的终端参与者的用户标示符和/或该终端参与者参与的相应文件传输会话的标示符；The message header generation sub-device is used to use the HTTP acquisition (GET) as the action, and use the input file that is requested to be received as the resource used to generate a message header. The resource URL of the resource includes the terminal participant who requests to receive the input file and/or the identifier of the corresponding file transfer session in which the End Participant participated;
消息生成子装置，用于根据所述消息头生成所述接收输入文件请求消息。The message generation sub-device is configured to generate the request message for receiving an input file according to the message header.
所述服务器中的消息生成装置又包括：The message generation device in the server further includes:
消息头生成子装置，根据HTTP表示“成功”的响应符，生成消息头；The message header generation sub-device generates a message header according to the HTTP response symbol representing "success";
消息体生成子装置，用于根据接收的输入文件的接收消息会话转播协议(MSRP)路径、发送MSRP路径、字节范围、成功报告、失败报告、接收者用户标示符、发送者用户标示符、文件日期、文件内容部署、文件内容类型和资源URL中的至少一种，生成一个文件的数据结构，作为消息体；Message body generating sub-means for receiving message session relay protocol (MSRP) path, sending MSRP path, byte range, success report, failure report, receiver user identifier, sender user identifier, At least one of file date, file content deployment, file content type, and resource URL to generate a file data structure as a message body;
消息生成子装置，用于根据所述消息头和消息体生成所述接收输入文件响应消息。The message generation sub-device is configured to generate the response message for receiving an input file according to the message header and the message body.
基于上述方案，Web开发商、第三方开发者或业务提供商等用户可以通过客户端，使用REST API访问调用电信运营商网络域中的电信能力，对服务器进行接收输入文件的相关控制。Based on the above scheme, users such as Web developers, third-party developers, or service providers can access and call the telecommunications capabilities in the telecom operator's network domain through the client using the REST API, and control the server to receive input files.
本发明的另一个目的在于提供一种删除输入文件的方法及系统，以解决用户不能调用电信能力删除输入文件的问题。Another object of the present invention is to provide a method and system for deleting an input file, so as to solve the problem that the user cannot invoke the telecommunication capability to delete the input file.
为了解决上述问题，本发明提供了一种删除输入文件的方法，该方法基于电信网络域提供的表象化状态转变(REST)应用编程接口(API)实现，包括：In order to solve the problems referred to above, the present invention provides a kind of method of deleting input file, and this method realizes based on the Representational State Transition (REST) application programming interface (API) that telecommunication network domain provides, comprising:
客户端以请求删除的输入文件为使用的资源，向服务器发送删除输入文件请求消息，携带所述资源的资源统一资源位置符(URL)；The client uses the input file requested to be deleted as the resource used, and sends a delete input file request message to the server, carrying the resource uniform resource locator (URL) of the resource;
所述服务器收到所述删除输入文件请求消息后，删除所述输入文件，向所述客户端返回删除输入文件响应消息。After receiving the delete input file request message, the server deletes the input file, and returns a delete input file response message to the client.
较佳地preferably
所述删除输入文件请求消息包含使用的动作的信息，所述动作为超文本转换协议(HTTP)的删除(Delete)动作，所述资源的资源URL包含终端参与者的用户标示符和文件传输会话的标示符中的至少一种。The delete input file request message includes the information of the action used, the action is the delete (Delete) action of the hypertext transfer protocol (HTTP), and the resource URL of the resource includes the user identifier and the file transfer session of the terminal participant At least one of the identifiers for .
较佳地preferably
所述客户端发送删除输入文件请求消息之前，按以下方式生成所述删除输入文件请求消息：Before the client sends the delete input file request message, the delete input file request message is generated in the following manner:
以请求删除的输入文件为使用的资源，以HTTP的删除(Delete)动作为使用的动作，生成消息头，所述资源的资源URL包含请求删除输入文件的终端参与者的用户标示符和/或该终端参与者参与的相应文件传输会话的标示符；The input file requested to be deleted is used as the resource used, and the delete (Delete) action of HTTP is used as the action used to generate a message header. The resource URL of the resource includes the user identifier and/or of the terminal participant requesting to delete the input file the identifier of the corresponding file transfer session in which the end participant participated;
根据所述消息头生成所述删除输入文件请求消息；generating the request message for deleting an input file according to the message header;
所述服务器删除输入文件成功，返回删除输入文件响应消息之前，按以下方式生成删除输入文件响应消息：The server deletes the input file successfully, and before returning the delete input file response message, generates the delete input file response message in the following manner:
根据HTTP表示“无内容(No content)”的响应符生成消息头；Generate a message header according to the HTTP response indicating "No content";
根据所述消息头生成删除输入文件响应消息。A delete input file response message is generated according to the message header.
相应地，本发明提供的删除输入文件的系统中，客户端和服务器基于电信网络域提供的表象化状态转变(REST)应用编程接口(API)交互，该系统包括：Correspondingly, in the system for deleting input files provided by the present invention, the client and the server interact based on the Representational State Transition (REST) application programming interface (API) provided by the telecommunications network domain, and the system includes:
客户端中的消息生成装置，用于生成删除输入文件请求消息；The message generating device in the client is used to generate a request message for deleting an input file;
客户端中的消息发送装置，用于向服务器发送所述删除输入文件请求消息；A message sending device in the client, configured to send the request message for deleting the input file to the server;
服务器中的消息接收和处理装置，用于在收到所述删除输入文件请求消息后进行解析和处理，删除所述输入文件；The message receiving and processing device in the server is used for parsing and processing after receiving the request message for deleting the input file, and deleting the input file;
服务器中的消息生成装置，用于生成删除输入文件响应消息；A message generating device in the server, configured to generate a response message for deleting an input file;
服务器中的消息发送装置，用于向所述客户端返回所述删除输入文件响应消息。The message sending means in the server is used to return the delete input file response message to the client.
较佳地preferably
所述客户端中的消息生成装置又包括：The message generation device in the client further includes:
消息头生成子装置，用于以请求删除的输入文件为使用的资源，以HTTP的删除(Delete)动作为使用的动作，生成消息头，所述资源的资源URL包含请求删除输入文件的终端参与者的用户标示符和/或该终端参与者参与的相应文件传输会话的标示符；The message header generation sub-means are used to use the input file requested to be deleted as the resource used, and the delete (Delete) action of HTTP as the action used to generate the message header. The resource URL of the resource includes the terminal participation request to delete the input file the user identifier of the end participant and/or the identifier of the corresponding file transfer session in which the end participant participated;
消息生成子装置，用于根据所述消息头生成所述删除输入文件请求消息；A message generation sub-device, configured to generate the request message for deleting an input file according to the message header;
所述服务器中的消息生成装置又包括：The message generation device in the server further includes:
消息头生成子装置，用于根据HTTP表示“无内容(No content)”的响应符生成消息头；The message header generates sub-means for generating a message header according to the HTTP response symbol representing "no content (No content)";
消息生成子装置，用于根据所述消息头生成所述删除输入文件响应消息。The message generation sub-device is configured to generate the delete input file response message according to the message header.
基于上述方案，Web开发商、第三方开发者或业务提供商等用户可以通过客户端，使用REST API访问调用电信网络域中的电信能力，对服务器进行删除输入文件的相关控制。Based on the above solution, users such as Web developers, third-party developers, or service providers can use the REST API to access and call the telecommunications capabilities in the telecommunications network domain through the client, and control the deletion of input files on the server.
附图说明Description of drawings
图1为本发明实施例开放电信能力接口的系统结构的示意图；FIG. 1 is a schematic diagram of a system structure of an open telecommunication capability interface according to an embodiment of the present invention;
图2为本发明实施例一接收输入文件方法的流程图；2 is a flowchart of a method for receiving an input file according to Embodiment 1 of the present invention;
图3为本发明实施例二删除输入文件方法的流程图；Fig. 3 is a flowchart of a method for deleting an input file according to Embodiment 2 of the present invention;
图4为本发明实施例客户端和服务器之间的接收和删除输入文件的操作示意图。Fig. 4 is a schematic diagram of an operation of receiving and deleting an input file between a client and a server according to an embodiment of the present invention.
具体实施方式Detailed ways
为使本发明的目的、技术方案和优点更加清楚明白，下文中将结合附图对本发明的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。In order to make the purpose, technical solution and advantages of the present invention more clear, the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined arbitrarily with each other.
实施例一Embodiment one
图1示出了本实施例开放文件传输业务电信能力接口的系统结构。如图所示，电信网络域包含IMS核心网和业务层，业务层包含短信业务服务器、彩信业务服务器、文件传输业务服务器(如RCS文件传输业务引擎)以及其他业务服务器等各种业务网络设备，但是，本发明用于文件传输业务的服务器也可以同时用于其他多种业务，并不局限于专用的服务器。这些服务器向Web开发商、第三方开发者、业务提供商等提供开放的REST API，Web开发商、第三方开发者、业务提供商等用户的客户端可以使用REST API访问电信网络域，调用电信网络域的RCS业务能力和IMS网络能力，实现电信业务的Web 2.0Widget轻量级应用与Mashup的开发。FIG. 1 shows the system structure of the telecommunications capability interface of the open file transfer service in this embodiment. As shown in the figure, the telecom network domain includes the IMS core network and the service layer, and the service layer includes SMS service servers, MMS service servers, file transfer service servers (such as RCS file transfer service engines) and other service servers and other service network devices. However, the server used for the file transfer service of the present invention can also be used for other multiple services at the same time, and is not limited to a dedicated server. These servers provide open REST APIs to Web developers, third-party developers, service providers, etc. Clients of users such as Web developers, third-party developers, and service providers can use REST APIs to access telecom network domains and call telecom The RCS business capability and IMS network capability of the network domain enable the development of Web 2.0 Widget lightweight applications and Mashups for telecom services.
本实施例中，Web开发商、第三方开发者、业务提供商等用户开发的应用程序可以通过客户端，使用本实施例提供的REST API对服务器进行接收输入文件的相关控制。客户端可以位于业务提供商的网络设备中，也可以位于终端用户设备如移动终端、固定终端等中。本发明适用的用户也不限于上述类型，可以是基于互联网服务、WEB服务的任何有控制权限的文件传输参与者。In this embodiment, applications developed by users such as Web developers, third-party developers, and service providers can use the REST API provided by this embodiment to control the server to receive input files through the client. The client can be located in the network equipment of the service provider, or in the terminal user equipment such as mobile terminal, fixed terminal and so on. The applicable users of the present invention are not limited to the above-mentioned types, and can be any file transfer participants with control authority based on Internet services and WEB services.
本实施例中REST API使用的资源、动作和数据结构的相关定义如下：The relevant definitions of resources, actions and data structures used by the REST API in this embodiment are as follows:
资源统一资源位置符链接中，serverRoot表示服务器路径，apiVersion表示API版本，FileTransfer表示文件传输，Terminating表示终端，TerminatingID表示终端参与者用户标示符，FileTransferSessions表示文件传输会话，FileTransferSessionId表示文件传输会话的标示符，inbound表示输入。In the resource uniform resource location link, serverRoot indicates the server path, apiVersion indicates the API version, FileTransfer indicates the file transfer, Terminating indicates the terminal, TerminatingID indicates the user identifier of the terminal participant, FileTransferSessions indicates the file transfer session, and FileTransferSessionId indicates the identifier of the file transfer session , inbound means input.
上述REST API使用的数据结构类型定义如下：The data structure types used by the above REST API are defined as follows:
数据结构类型Type：File文件Data structure type Type: File file
其中，文件内容部署表示建议接收文件方对该文件内容的处理方式。文件的资源URL中可以包含终端参与者的用户标示符和文件传输会话的标示符。用户标示符如可以为用户地址。Wherein, the deployment of the file content indicates the method of processing the content of the file suggested by the party receiving the file. The resource URL of the file may include the user identifier of the terminal participant and the identifier of the file transfer session. The user identifier may be, for example, a user address.
图2为本实施例基于REST API接收输入文件的流程图，该流程包括以下步骤：Fig. 2 is the flow chart of receiving input file based on REST API in the present embodiment, and this flow process comprises the following steps:
步骤S201：客户端以请求接收的输入文件为使用的资源，向服务器发送接收输入文件请求消息，携带所述资源的资源统一资源位置符(URL)；Step S201: The client uses the input file requested to be received as the resource used, and sends a request message for receiving the input file to the server, carrying the resource uniform resource locator (URL) of the resource;
本实施例的接收输入文件请求消息中，消息头中包括使用的动作和资源，可以不携带消息体。In the received input file request message of this embodiment, the message header includes the used action and resources, and the message body may not be carried.
客户端可以通过以下方式生成该消息：A client can generate this message in the following ways:
以HTTP的获取(GET)为使用的动作，以请求接收的输入文件为使用的资源，生成消息头，所述资源的资源URL包含终端参与者(请求接收输入文件的参与者)的用户标示符和该终端参与者参与的相应文件传输会话的标示符中的至少一个；Use HTTP acquisition (GET) as the action used, and use the input file requested to be received as the resource used to generate a message header. The resource URL of the resource includes the user identifier of the terminal participant (the participant who requests to receive the input file) and at least one of the identifiers of the corresponding file transfer session in which the end participant participates;
根据所述消息头生成接收输入文件请求消息。A request message for receiving an input file is generated according to the message header.
下面用一个示例来说明一下生成的接收输入文件请求消息。The following uses an example to illustrate the generated receive input file request message.
假定终端参与者为用户Peter E.Xample(SIP：user2example.com)，文件传输会话标示符为{FileTransferSessionId1}，该用户接收输入文件。Assume that the terminal participant is user Peter E.Xample (SIP: user2example.com), the file transfer session identifier is {FileTransferSessionId1}, and the user receives the input file.
以下为接收输入文件请求消息内容的示例及说明：The following are examples and descriptions of receiving input file request message content:
GETGET
http://{serverRoot}/{apiVersion}/FileTransfer/Terminating/SIP：user2example.com/FileTransferSessions/{FileTransferSessionId1}/inbound/file HTTP/1.1\\动作+资源URLhttp://{serverRoot}/{apiVersion}/FileTransfer/Terminating/SIP: user2example.com/FileTransferSessions/{FileTransferSessionId1}/inbound/file HTTP/1.1\\action+resource URL
Accept：application/xmlAccept: application/xml
Host：example.com：80Host: example.com:80
在本申请给出的若干消息内容的示例中，对REST API中定义的动作、资源、数据结构和部分信息作了说明，其他内容如数据结构中定义的信息，消息头中的其他内容等，请参照上文和Web中的规定。In the examples of message content given in this application, the actions, resources, data structures and some information defined in the REST API are explained. Other content such as the information defined in the data structure and other content in the message header, etc., Please refer to the regulations above and on the Web.
步骤S202：所述服务器收到所述接收输入文件请求消息后，获取所述输入文件的信息，向所述客户端返回接收输入文件响应消息，携带所述输入文件的信息。Step S202: After receiving the request message for receiving the input file, the server obtains the information of the input file, and returns a response message of receiving the input file to the client, carrying the information of the input file.
接收输入文件响应消息中，消息头包括HTTP的响应符，消息体中包括接收的输入文件的数据结构。In the response message of receiving the input file, the message header includes an HTTP response symbol, and the message body includes the data structure of the received input file.
服务器接收输入文件成功时，可以通过以下方式来生成该消息：When the server successfully receives the input file, the message can be generated in the following ways:
根据HTTP表示“成功(OK)”的响应符，生成消息头；Generate a message header according to the HTTP response indicating "success (OK)";
按照XML格式，根据接收的输入文件的信息如该输入文件的接收MSRP路径、发送MSRP路径、字节范围、成功报告、失败报告、接收者用户标示符、发送者用户标示符、文件日期、文件内容部署、文件内容类型和资源URL中的至少一种，生成一个文件的数据结构，作为消息体；According to the XML format, according to the information of the input file received, such as the receiving MSRP path, sending MSRP path, byte range, success report, failure report, receiver user identifier, sender user identifier, file date, file At least one of content deployment, file content type, and resource URL to generate a file data structure as a message body;
根据所述消息头和消息体生成接收输入文件响应消息。A response message for receiving an input file is generated according to the message header and the message body.
以下为接收输入文件成功时，接收输入文件响应消息内容的示例和说明：The following is an example and description of the content of the response message for receiving the input file when the input file is received successfully:
HTTP/1.1200OKContent-Type：multipart/form-data；boundary＝″＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝123456＝＝″；HTTP/1.1200 OKContent-Type: multipart/form-data; boundary="================123456==";
MIME-Version：1.0MIME-Version: 1.0
Date：Thu，04Jun 200902:51:59GMTDate: Thu, 04Jun 2009 02:51:59GMT
--＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝123456＝＝--================ 123456==
Content-Disposition：multipart/form-data；name＝”root-fields”Content-Disposition: multipart/form-data; name="root-fields"
Content-Type：application/xml；charset＝″utf-8″Content-Type: application/xml; charset="utf-8"
Content-Length：nnnnContent-Length: nnnn
<？xnl version＝″1.0″encoding＝″UTF-8″？><? xnl version="1.0" encoding="UTF-8"? >
<FileTransfer：File xmlns：FileTransfer＝″urn:oma:xml:rest:FileTransfer：1″>\\文件数据结构的开始<FileTransfer:File xmlns:FileTransfer=″urn:oma:xml:rest:FileTransfer:1″>\\The beginning of the file data structure
<To-Path>msrp://Peter E.Xample.example.com:7575/u3978ae283wzd；tcp</To-Path><To-Path>msrp://Peter E.Xample.example.com:7575/u3978ae283wzd;tcp</To-Path>
<From-Path>msrp://Server.example.com:4000/VL1SmRjx0qhi；tcp</From-Path> <From-Path>msrp://Server.example.com:4000/VL1SmRjx0qhi; tcp</From-Path>
<Success-Report>no</Success-Report><Success-Report>no</Success-Report>
<Failure-Report>yes</Failure-Report><Failure-Report>yes</Failure-Report>
<CPIM to>SIP：user2example.com</CPIM to><CPIM to>SIP: user2example.com</CPIM to>
<CPIM from>SIP：user1example.com</CPIM from><CPIM from>SIP: user1example.com</CPIM from>
<CPIM DateTime>2010-05-15T15:02:31-03:00</CPIM DateTime><CPIM DateTime>2010-05-15T15:02:31-03:00</CPIM DateTime>
<CPIM Content-Disposition>attachement；filename＝″My cool picture.jpg″；creation-date＝″Mon，15May201015:01:31+0300″；size＝4092</CPIM Content-Disposition><CPIM Content-Disposition>attachement; filename = "My cool picture.jpg"; creation-date = "Mon, 15May201015:01:31+0300"; size = 4092</CPIM Content-Disposition>
<CPIM Content-Type>image/jpeg；charset＝utf-8</CPIM Content-Type><CPIM Content-Type>image/jpeg; charset=utf-8</CPIM Content-Type>
<clientCorrelator>567894</clientCorrelator><clientCorrelator>567894</clientCorrelator>
<resourceURL>http://{apiVersion}/FileTransfer/Terminating/SIP：user2example.com/FileTransferSessions/{FileTransferSessionId1}/inbound/file</resourceURL>\\文件的资源URL<resourceURL>http://{apiVersion}/FileTransfer/Terminating/SIP: user2example.com/FileTransferSessions/{FileTransferSessionId1}/inbound/file</resourceURL>\\The resource URL of the file
</FileTransfer：File></FileTransfer:File>
--＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝123456＝＝--================ 123456==
GIF89a...binary image data...GIF89a...binary image data...
--＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝123456＝＝----================123456==--
实施例二Embodiment two
本实施例涉及基于电信网络域提供的REST API删除输入文件的相关于控制，所基于的系统与实施例一相同，资源、动作和数据结构的相关定义请参照实施例一中的说明。This embodiment involves the related control of deleting input files based on the REST API provided by the telecommunications network domain. The system based on it is the same as that of Embodiment 1. For the relevant definitions of resources, actions, and data structures, please refer to the description in Embodiment 1.
图3为本实施例基于REST API删除输入文件的流程图，该流程包括以下步骤：Fig. 3 is the flowchart of deleting input file based on REST API in the present embodiment, and this flow process comprises the following steps:
步骤S301：客户端以请求删除的输入文件为使用的资源，向服务器发送删除输入文件请求消息，携带所述资源的资源统一资源位置符(URL)；Step S301: the client uses the input file requested to be deleted as the resource used, and sends a delete input file request message to the server, carrying the resource uniform resource locator (URL) of the resource;
本实施例的删除输入文件请求消息中，消息头中包括使用的动作和资源，可以不携带消息体。In the delete input file request message in this embodiment, the message header includes the used action and resources, and the message body may not be carried.
客户端可以通过以下方式生成该消息：A client can generate this message in the following ways:
以请求删除的输入文件为使用的资源，以HTTP的删除(Delete)动作为使用的动作，生成消息头，所述资源的资源URL包含终端参与者(请求删除输入文件的参与者)的用户标示符和文件传输会话(该终端参与者参与的相应文件传输会话)的标示符中的至少一个。The input file requested to be deleted is used as the resource, and the HTTP delete (Delete) action is used as the action used to generate a message header. The resource URL of the resource includes the user identifier of the terminal participant (the participant who requests to delete the input file) at least one of an identifier and an identifier of a file transfer session (the corresponding file transfer session in which the end participant participates).
根据所述消息头生成删除输入文件请求消息。A delete input file request message is generated according to the message header.
下面用一个示例来说明一下生成的删除输入文件请求消息。Let's use an example to illustrate the generated delete input file request message.
假定终端参与者为用户Peter E.Xample(SIP：user2example.com)，文件传输会话为{FileTransferSessionId1}，该请求为删除输入文件。Assume that the terminal participant is user Peter E.Xample (SIP: user2example.com), the file transfer session is {FileTransferSessionId1}, and the request is to delete the input file.
以下为删除输入文件请求消息内容的示例：The following is an example of the content of a delete input file request message:
DELETEDELETE
http://{serverRoot}/{apiVersion}/FileTransfer/Terminating/SIP：user2example.com/FileTransferSessions/{FileTransferSessionId1}/file HTTP/1.1\\动作+资源的资源URLhttp://{serverRoot}/{apiVersion}/FileTransfer/Terminating/SIP:user2example.com/FileTransferSessions/{FileTransferSessionId1}/file HTTP/1.1\\action+resource URL
Accept：application/xmlAccept: application/xml
Host：example.com:80Host: example.com:80
步骤S302：所述服务器收到所述删除输入文件请求消息后，删除所述输入文件，向所述客户端返回删除输入文件响应消息。Step S302: After receiving the delete input file request message, the server deletes the input file, and returns a delete input file response message to the client.
删除输入文件响应消息中，消息头包括HTTP的响应符，可以不携带消息体。In the delete input file response message, the message header includes the HTTP response symbol, and the message body does not need to be carried.
服务器删除输入文件成功时，可以通过以下方式来生成该消息：When the server successfully deletes the input file, it can generate this message in the following ways:
根据HTTP表示“无内容(No content)”的响应符生成消息头；Generate a message header according to the HTTP response indicating "No content";
根据所述消息头生成删除输入文件响应消息。A delete input file response message is generated according to the message header.
以下为删除输入文件成功时，删除输入文件请求消息内容的示例：The following is an example of the delete input file request message content when the delete input file is successful:
HTTP/1.1204No contentHTTP/1.1204 No content
Date：Thu，04Jun 200902:51:59GMTDate: Thu, 04Jun 2009 02:51:59GMT
图4为综合上述实施例的，客户端和服务器之间接收输入文件和删除输入文件的操作示意图。Fig. 4 is a schematic diagram of the operations of receiving and deleting input files between the client and the server according to the above-mentioned embodiments.
文件传输进行中，输入文件可以上传至服务器保存；When the file transfer is in progress, the input file can be uploaded to the server for storage;
之后，客户端请求接收输入文件，包括以下步骤：Afterwards, the client request receives the input file, including the following steps:
客户端生成接收输入文件请求消息；The client generates a receive input file request message;
客户端向服务器发送所述接收输入文件请求消息；The client sends the request message for receiving an input file to the server;
服务器收到接收输入文件请求消息后进行解析和处理，获取所述输入文件的信息；After receiving the input file request message, the server performs parsing and processing to obtain the information of the input file;
服务器生成接收输入文件响应消息；The server generates a receive input file response message;
服务器向所述客户端返回接收输入文件响应消息。The server returns a response message of receiving the input file to the client.
之后，客户端可以根据响应中输入文件的信息进行文件接收。After that, the client can receive the file according to the information of the input file in the response.
如客户端请求删除输入文件，包括以下步骤：If the client requests to delete the input file, it includes the following steps:
客户端生成删除输入文件请求消息；The client generates a delete input file request message;
客户端向服务器发送删除输入文件请求消息；The client sends a delete input file request message to the server;
服务器收到删除输入文件请求消息后进行解析和处理，删除输入文件；After the server receives the delete input file request message, it parses and processes it, and deletes the input file;
服务器生成删除输入文件响应消息；The server generates a delete input file response message;
服务器向所述客户端返回删除输入文件响应消息。The server returns a delete input file response message to the client.
上述各个消息的内容和生成方法请参见上文中的描述，不再重复。For the content and generation method of each of the above messages, please refer to the description above, and will not be repeated here.
上述方案中，具体说明了文件传输过程中接收和删除文件的开放电信能力接口，各个消息的内容即可以满足文件传输业务的需要，又可以适用于现有的开放电信能力的相关规范如OMA中的相关规范、IEFT文件传输协议等。大大方便了Web开发商、第三方开发者或业务提供商等以REST风格的API灵活地对服务器进行接收和删除输入文件的相关控制。In the above solution, the open telecommunication capability interface for receiving and deleting files during the file transfer process is specified. The content of each message can meet the needs of the file transfer service, and can also be applied to the existing related specifications of the open telecommunication capability, such as in OMA. related specifications, IEFT file transfer protocol, etc. It greatly facilitates Web developers, third-party developers or service providers to flexibly control the server to receive and delete input files with a REST-style API.
本领域普通技术人员可以理解上述方法中的全部或部分步骤可通过程序来指令相关硬件完成，所述程序可以存储于计算机可读存储介质中，如只读存储器、磁盘或光盘等。可选地，上述实施例的全部或部分步骤也可以使用一个或多个集成电路来实现，相应地，上述实施例中的各模块/单元可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。本发明不限制于任何特定形式的硬件和软件的结合。Those skilled in the art can understand that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a magnetic disk or an optical disk, and the like. Optionally, all or part of the steps in the above embodiments can also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiments can be implemented in the form of hardware, or can be implemented in the form of software function modules. The form is realized. The present invention is not limited to any specific combination of hardware and software.
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010548492.XACN102469138B (en) | 2010-11-17 | 2010-11-17 | The method and system of a kind of reception and deleting input document |
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010548492.XACN102469138B (en) | 2010-11-17 | 2010-11-17 | The method and system of a kind of reception and deleting input document |
| Publication Number | Publication Date |
|---|---|
| CN102469138A CN102469138A (en) | 2012-05-23 |
| CN102469138Btrue CN102469138B (en) | 2015-09-16 |
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010548492.XAActiveCN102469138B (en) | 2010-11-17 | 2010-11-17 | The method and system of a kind of reception and deleting input document |
| Country | Link |
|---|---|
| CN (1) | CN102469138B (en) |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009124223A1 (en)* | 2008-04-02 | 2009-10-08 | Twilio Inc. | System and method for processing telephony sessions |
| CN101615179A (en)* | 2008-06-25 | 2009-12-30 | 国际商业机器公司 | Method and system for cross-domain interaction of web applications |
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009124223A1 (en)* | 2008-04-02 | 2009-10-08 | Twilio Inc. | System and method for processing telephony sessions |
| CN101615179A (en)* | 2008-06-25 | 2009-12-30 | 国际商业机器公司 | Method and system for cross-domain interaction of web applications |
| Title |
|---|
| WIMS 2.0: Converging IMS and Web 2.0. Designing REST APIs for the;David Lozano等;《IEEE》;20080919;18-24* |
| Publication number | Publication date |
|---|---|
| CN102469138A (en) | 2012-05-23 |
| Publication | Publication Date | Title |
|---|---|---|
| Belqasmi et al. | RESTful web services for service provisioning in next-generation networks: a survey | |
| KR101054787B1 (en) | Method, system, and apparatus for sending IMS instant messages | |
| US20080294729A1 (en) | Email object for open mobile alliance data synchronization usage | |
| KR20070004920A (en) | Method and apparatus for transmitting JRI for bypassing content of SPI | |
| JP2012512448A (en) | Method and configuration for creating a virtual relationship between communication devices to publish personal data | |
| KR100977188B1 (en) | Deletion Mechanism in SPI Multimedia Service | |
| CN107786415B (en) | Service processing method and related equipment and system | |
| CN103379096A (en) | Internet and operator network service sharing method, service side and webpage gateway | |
| TW200937215A (en) | Dynamic, subscriber driven charging models for media distribution | |
| US9288241B2 (en) | Web-telco convergence comprising downloading script commands to user terminals | |
| CN102469042B (en) | Chat sessions sends output message and obtains the method and system of output message | |
| CN102469041B (en) | Chat sessions starts and obtains the method and system of session list | |
| CN103718168B (en) | For activating mobile device to initiate the system and method for communication | |
| CN101202953B (en) | Quick reply method and system thereof | |
| CN102469136B (en) | A kind of chat sessions increases participant and obtains the method and system of participant list | |
| CN103339898A (en) | Method and system for providing an enhanced event notification in a universal plug and play home network environment | |
| CN102469138B (en) | The method and system of a kind of reception and deleting input document | |
| CN102469148B (en) | Chat sessions is accepted the invitation and is refused the method and system of invitation | |
| CN102469090B (en) | The method and system of startup file transmission session and the list of acquisition file transfer session | |
| CN101834880B (en) | System and method for realizing service of converging address books | |
| KR20080034072A (en) | Method of transmitting heterogeneous message using SIP-based transmission message and user device therefor | |
| CN102469137B (en) | Method and system for accepting document transmission invitation and refusing document transmission invitation | |
| CN102469135B (en) | The method and system of ends file transfer session and acquisition file transfer session information | |
| CN102469147B (en) | Chat sessions obtains input message and deletes the method and system of input message | |
| KR100603002B1 (en) | Personal Information Transmission Method Using Next Generation Broadband Network Environment |
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right | Effective date of registration:20201127 Address after:215500 No.13, Caotang Road, Changshu, Suzhou, Jiangsu Province Patentee after:Changshu intellectual property operation center Co.,Ltd. Address before:518057 Nanshan District Guangdong high tech Industrial Park, South Road, science and technology, ZTE building, Ministry of Justice Patentee before:ZTE Corp. | |
| CP02 | Change in the address of a patent holder | ||
| CP02 | Change in the address of a patent holder | Address after:215500 5th floor, building 4, 68 Lianfeng Road, Changfu street, Changshu City, Suzhou City, Jiangsu Province Patentee after:Changshu intellectual property operation center Co.,Ltd. Address before:No.13 caodang Road, Changshu City, Suzhou City, Jiangsu Province Patentee before:Changshu intellectual property operation center Co.,Ltd. |