CN102469138A - Method and system for receiving and deleting input document - Google Patents
Method and system for receiving and deleting input document Download PDFInfo
- Publication number
- CN102469138A CN102469138A CN201010548492XA CN201010548492A CN102469138A CN 102469138 A CN102469138 A CN 102469138A CN 201010548492X A CN201010548492X A CN 201010548492XA CN 201010548492 A CN201010548492 A CN 201010548492A CN 102469138 A CN102469138 A CN 102469138A
- Authority
- CN
- China
- Prior art keywords
- message
- input file
- resource
- deletion
- server
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention relates to a method and a system for receiving and deleting an input document, and is realized on the basis of REST (Representational State Transfer) API (Application Programming Interface) provided by a telecommunication network domain. When the input document is received, the method comprises the following steps that: a client sends a request message for receiving the input document to a server by taking the input document required to be received as a used resource, and the message carries a resource URL (Uniform Resource Locator) of the resource; and after the server receives the message, the information of the input document is acquired, a response message for receiving the input document is returned to the client, and the response message carries the information of the input document; when the input document needs to be deleted, the client sends a request message for deleting the input document to the server by taking the input document required to be deleted as the used resource, and the message carries the resource URL of the resource; and after the server receives the request message for deleting the input document, the input document is deleted, and the response message for deleting the input document is returned to the client. The invention can solve the problem that a user can not invoke the telecommunication capacity to receive and delete the input document.
Description
Technical field
The present invention relates to file transfer, relate in particular to a kind of method and system that receive and delete input file.
Background technology
In the face of the evolution of information communication industrial cycle and the transition spring tide of consumer's pattern; In the face of the infiltration of the wide-scale distribution of the bone ash level innovation mode of the Internet and new media or even IT vendor, content integration person and consumer electronics manufacturer to the field of operation; Telecom operators are taking a kind of positive fusion, open attitude, make great efforts to attempt open its telecommunication capability, absorb all the useful ideas; Performance third party enterprise and individual innovation ability make abundant valued added applications; On the other hand, use the secondary distribution channel of this telecommunications service, promote the sale of basic telecommunications service.Especially terminal and software vendor are in the flames of war rise all around of market, online application shop, and operator must utilize telecommunication capability (communication service reliably; User data; Situation; Authentication; Charge etc.) make the road of a new differentiation.
Parlay tissue in 1998 is set up and is devoted to be telephone network exploitation API (API).By these API, the application of oneself can be created by the third-party institution.Parlay is organized in this respect and has done unified standardization effort, has formulated Parlay/OSA (open Software Description) API based on CORBA (common object Resource Broker framework), to the programme work in unity of aspect of the use of various telecommunication capabilities.Parlay/OSA API has also obtained ETSI (ETSI) and the common assistance of 3GPP (3G (Third Generation) Moblie partner program normal structure) in addition.In 3GPP, Parlay is by the part as open Software Description (OSA).Parlay X is the API standard criterion based on SOAP (Simple Object Access Protocol) Web service that Parlay, 3GPP and OMA (Open Mobile Alliance) issue.Parlay REST (towards the RESTful constraint of Parlay X) is the up-to-date cover API standard criterion of issuing of OMA, is intended to specify REST Web service constraint for the collection of the Parlay X Web service standard (son) among the OMA.
In Web 2.0 fields, support that the corresponding usefulness of API of AjaX (asynchronous JavaScript script and XML extensible markup language) technology is more extensive, style is REST (REpresentational StateTransfer, a presentation state-transition).REST is not a kind of new technology, neither a kind of standard, but one group of design principle; Compare with the Web service (like Parlay X) based on SOAP, REST API is lightweight more, has better developer's friendly, is convenient to exploitation and Mashup that Web uses.Therefore increasing Web service begins to adopt the design of REST style and realizes.For example, Amazon.com provides and carries out books near the Web service of REST style and search; The Web service that Yahoo provides also is REST style (wikipedia).
GSMA (global mobile system association) RCS (Futong letter external member) is based on the business packet of the rich communication function that interoperable is provided that existing IMS (IP Multimedia System) network facilities and development agreement build out; Mainly comprise business such as enhanced address book, enhanced call, enhancement mode converged message; The user can be upgraded appear (like individual picture, message, recommended links and the state) of oneself; Also can in the address list of mobile phone, see good friend's the situation that appears in real time, and realize multiple communication requirements such as note, multimedia message, chat (instant message), file transfer.RCS comprises common unified technology and the realization standard of supporting of operator, equipment vendor and mobile phone terminal manufacturer, so it not only cultivates the more consistent use habit of consumer easily, and can realize interconnecting of country variant, different operators.Follow-up phase, RCS will further introduce social networks, open REST API API, with content such as integrated application shop, the Internet.The targeted customer of RCS REST style API is typical Web developer, third party developer, service provider; Can the RCS professional ability and the IMS network capabilities of telecom operators is open through API; Be more suitable for the exploitation of application of Web 2.0Widget lightweight and Mashup, cater to Web application and development trend.
At present; The professional ability of telecom operators' note, multimedia message can have been passed through the ParlayREST2.0 consensus standard of OMA (Open Mobile Alliance) formulation and open; And the file transfer professional ability is not also formulated the corresponding protocol standard open, and the user can't call telecommunication capability and receive and the deletion input file.
Summary of the invention
In view of this, one object of the present invention is to provide a kind of method and system that receive input file, can not call the problem that telecommunication capability receives input file to solve the user.
In order to address the above problem, the invention provides a kind of method that receives input file, this method realizes based on presentation state-transition (REST) API (API) that the communication network territory provides, comprising:
Client is the resource of use with the input file that request receives, and sends to server and receives the input file request message, carries the resource unified resource position sign (URL) of said resource;
After said server is received said reception input file request message, obtain the information of said input file, return input file response message, the information of carrying said input file of receiving to said client.
Preferably
The information that comprises the action of use in the said reception input file request message; Said action is the obtaining of Hypertext Transfer Protocol(HTTP) (HTTP) (GET) action, and the resource URL of said resource comprises at least a in terminal participant's the indications of user's indications and file transfer session.
Preferably
The information of said input file comprises at least a in the following information: receive message session retransmission protocol (MSRP) path, send MSRP path, bytes range, successfully report, failure reporting, recipient user's indications, sender user's indications, file date, file content deployment, file content types and resource URL.
Preferably
Client is sent and is received before the input file request message, generates said reception input file request message by following mode:
The action that (GET) is use of obtaining with HTTP; The input file that receives with request is the resource of use; Generate message header, the resource URL of said resource comprises the terminal participant's who asks the reception input file the user's indications and/or the indications of the corresponding document transmission session that this terminal participant participates in;
Generate reception input file request message according to said message header.
Preferably
Said server receives the input file success, returns to receive before the input file response message, generates said reception input file response message by following mode:
Represent the responder of " success (OK) " to generate message header according to HTTP;
Generate the data structure of a file according to the information of said input file, as message body;
Generate reception input file response message according to said message header and message body.
Correspondingly, in the system of reception input file provided by the invention, client and server is mutual based on presentation state-transition (REST) API (API) that the communication network territory provides, and this system comprises:
Message creating apparatus in the client is used for generating reception input file request message;
Message dispensing device in the client is used for sending said reception input file request message to server;
Message sink in the server and processing unit are used to receive and resolve and handle after receiving the input file request message, obtain the information of said input file;
Message creating apparatus in the server is used for generating reception input file response message;
Message dispensing device in the server is used for returning said reception input file response message to said client.
Preferably
Message creating apparatus in the said client comprises again:
Message header generates sub-device; Be used for the action that (GET) is use of obtaining with HTTP; The input file that receives with request is the resource of use; Generate message header, the resource URL of said resource comprises the terminal participant's who asks the reception input file the user's indications and/or the indications of the corresponding document transmission session that this terminal participant participates in;
Message generates sub-device, is used for generating said reception input file request message according to said message header.
Message creating apparatus in the said server comprises again:
Message header generates sub-device, and the responder according to HTTP representes " success " generates message header;
Message body generates sub-device; Be used for according to the input file that receives reception message session retransmission protocol (MSRP) path, send at least a of MSRP path, bytes range, successfully report, failure reporting, recipient user's indications, sender user's indications, file date, file content deployment, file content types and resource URL; Generate the data structure of a file, as message body;
Message generates sub-device, is used for generating said reception input file response message according to said message header and message body.
Based on such scheme, users such as Web developer, third party developer or service provider can pass through client, use the REST API Access to call the telecommunication capability in telecom operators' network domains, server are received the relevant control of input file.
Another object of the present invention is to provide a kind of method and system of deleting input file, to solve the problem that the user can not call telecommunication capability deletion input file.
In order to address the above problem, the invention provides a kind of method of deleting input file, this method realizes based on presentation state-transition (REST) API (API) that the communication network territory provides, comprising:
Client is the resource of use with the input file of request deletion, sends deletion input file request message to server, carries the resource unified resource position sign (URL) of said resource;
Said server is deleted said input file after receiving said deletion input file request message, returns deletion input file response message to said client.
Preferably
Said deletion input file request message comprises the information of the action of use; Said action is deletion (Delete) action of Hypertext Transfer Protocol(HTTP) (HTTP), and the resource URL of said resource comprises at least a in terminal participant's the indications of user's indications and file transfer session.
Preferably
Said client is sent before the deletion input file request message, generates said deletion input file request message by following mode:
Input file with the request deletion is the resource of use; Deletion (Delete) action with HTTP is the action of use; Generate message header, the resource URL of said resource comprises the terminal participant's who asks the deletion input file the user's indications and/or the indications of the corresponding document transmission session that this terminal participant participates in;
Generate said deletion input file request message according to said message header;
The success of said server deletion input file is returned before the deletion input file response message, generates deletion input file response message by following mode:
The responder of representing " no content (No content) " according to HTTP generates message header;
Generate deletion input file response message according to said message header.
Correspondingly, in the system of deletion input file provided by the invention, client and server is mutual based on presentation state-transition (REST) API (API) that the communication network territory provides, and this system comprises:
Message creating apparatus in the client is used for generating deletion input file request message;
Message dispensing device in the client is used for sending said deletion input file request message to server;
Message sink in the server and processing unit are used for after receiving said deletion input file request message, resolving and handling, and delete said input file;
Message creating apparatus in the server is used for generating deletion input file response message;
Message dispensing device in the server is used for returning said deletion input file response message to said client.
Preferably
Message creating apparatus in the said client comprises again:
Message header generates sub-device; The input file that is used for the request deletion is the resource of use; Deletion (Delete) action with HTTP is the action of use; Generate message header, the resource URL of said resource comprises the terminal participant's who asks the deletion input file the user's indications and/or the indications of the corresponding document transmission session that this terminal participant participates in;
Message generates sub-device, is used for generating said deletion input file request message according to said message header;
Message creating apparatus in the said server comprises again:
Message header generates sub-device, is used for representing that according to HTTP the responder of " no content (No content) " generates message header;
Message generates sub-device, is used for generating said deletion input file response message according to said message header.
Based on such scheme, users such as Web developer, third party developer or service provider can pass through client, use the REST API Access to call the telecommunication capability in the communication network territory, server are deleted the relevant control of input file.
Description of drawings
Fig. 1 is the sketch map of the system configuration of the open telecommunication capability interface of the embodiment of the invention;
Fig. 2 is the flow chart that the embodiment of the invention one receives the input file method;
Fig. 3 is the flow chart of the embodiment of the invention two deletion input file methods;
Fig. 4 be between the embodiment of the invention client and server reception and the deletion input file operation chart.
Embodiment
For making the object of the invention, technical scheme and advantage clearer, hereinafter will combine accompanying drawing that embodiments of the invention are elaborated.Need to prove that under the situation of not conflicting, embodiment among the application and the characteristic among the embodiment be combination in any each other.
Embodiment one
Fig. 1 shows the system configuration of the professional telecommunication capability interface of the open file transfer of present embodiment.As shown in the figure; The communication network territory comprises IMS core net and operation layer; Operation layer comprises the miscellaneous service network equipments such as short message service server, MMS server, file transfer service server (like RCS file transfer service enabler) and other service servers; But the present invention is used for the professional server of file transfer also can be used for other multiple business simultaneously, is not limited to special-purpose server.These servers provide the REST that opens API to Web developer, third party developer, service provider etc.; User client such as Web developer, third party developer, service provider can be used REST API Access communication network territory; Call the RCS professional ability and the IMS network capabilities in communication network territory, realize the Web 2.0Widget lightweight application of telecommunication service and the exploitation of Mashup.
In the present embodiment, the application program of users such as Web developer, third party developer, service provider exploitation can be passed through client, and the REST API that uses present embodiment to provide receives the relevant control of input file to server.Client can be arranged in service provider's the network equipment, also can be arranged in end user device such as portable terminal, fixed terminal etc.The user that the present invention is suitable for also is not limited to the above-mentioned type, can be based on any file transfer participant that control authority is arranged of Internet service, WEB service.
The related definition of REST API uses in the present embodiment resource, action and data structure is following:
In the link of resource unified resource position sign, serverRoot representes server path, and apiVersion representes the API version; FileTransfer representes file transfer; Terminating representes the terminal, and TerminatingID representes terminal participant user's indications, and FileTransferSessions representes file transfer session; FileTransferSessionId representes the indications of file transfer session, and inbound representes input.
The type of data structure that above-mentioned REST API uses defines as follows:
Type of data structure Type:File file
Wherein, file content is disposed the expression suggestion and is received the processing mode of file side to this document content.Can comprise terminal participant's the user's indications and the indications of file transfer session among the resource URL of file.User's indications is as being station address.
Fig. 2 is the flow chart of present embodiment based on REST API reception input file, and this flow process may further comprise the steps:
Step S201: client is the resource of use with the input file that request receives, and sends to server and receives the input file request message, carries the resource unified resource position sign (URL) of said resource;
In the reception input file request message of present embodiment, comprise the action and the resource of use in the message header, can not carry message body.
Client can generate this message in the following manner:
The action that (GET) is use of obtaining with HTTP; The input file that receives with request is the resource of use; Generate message header, at least one in the indications of the corresponding document transmission session that user's indications that the resource URL of said resource comprises terminal participant (request receives the participant of input file) and this terminal participant participate in;
Generate reception input file request message according to said message header.
Below with a bright reception input file request message that once generates of as an exampleBSEMGVR takeN-PSVSEMOBJ.
Suppose that the terminal participant is user Peter E.Xample (SIP:user2example.com), the file transfer session indications is that { FileTransferSessionId1}, this user receives input file.
Below for receiving the example and the explanation of input file request message content:
GET
Http: // serverRoot}/apiVersion}/FileTransfer/Terminating/SIP:user2example.co m/FileTransferSessions/{FileTransferSessionId1}/inbound/ file HTTP/1.1 action+resource URL
Accept：application/xml
Host：example.com：80
In the example of some message contents that the application provides; Action, resource, data structure and partial information to defining among the REST API are described; The information that defines in other guide such as the data structure, the other guide in the message header etc. are please with reference to the regulation among preceding text and the Web.
Step S202: after said server is received said reception input file request message, obtain the information of said input file, return input file response message, the information of carrying said input file of receiving to said client.
Receive in the input file response message, message header comprises the responder of HTTP, comprises the data structure of the input file of reception in the message body.
When server receives the input file success, can generate this message in the following manner:
Represent the responder of " success (OK) " to generate message header according to HTTP;
According to the XML form; According to the reception MSRP path of the information of the input file that receives such as this input file, send at least a among MSRP path, bytes range, successfully report, failure reporting, recipient user's indications, sender user's indications, file date, file content deployment, file content types and the resource URL; Generate the data structure of a file, as message body;
Generate reception input file response message according to said message header and message body.
During below for the success of reception input file, receive the example and the explanation of input file response message content:
HTTP/1.1200OKContent-Type：multipart/form-data；boundary＝″＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝123456＝＝″；
MIME-Version：1.0
Date：Thu，04Jun?200902:51:59GMT
--＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝123456＝＝
Content-Disposition：multipart/form-data；name＝”root-fields”
Content-Type：application/xml；charset＝″utf-8″
Content-Length：nnnn
<?xnl?version＝″1.0″encoding＝″UTF-8″?>
< FileTransfer:File xmlns:FileTransfer=" urn:oma:xml:rest:FileTransfer:1 ">the beginning of file data structure
<To-Path>msrp://Peter?E.Xample.example.com:7575/u3978ae283wzd；tcp</To-Path>
<From-Path>msrp://Server.example.com:4000/VL1SmRjx0qhi；tcp</From-Path>
<Success-Report>no</Success-Report>
<Failure-Report>yes</Failure-Report>
<CPIM?to>SIP：user2example.com</CPIM?to>
<CPIM?from>SIP：user1example.com</CPIM?from>
<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-Type>image/jpeg；charset＝utf-8</CPIM?Content-Type>
<clientCorrelator>567894</clientCorrelator>
<resourceURL>Http: // { apiVersion}/FileTransfer/Terminating/SIP:user2example.co m/FileTransferSessions/{FileTransferSessionId1}/inbound/ file</resourceURL>The resource URL of file
</FileTransfer：File>
--＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝123456＝＝
GIF89a...binary?image?data...
--＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝123456＝＝--
Embodiment two
Present embodiment relates to the control that is relevant to of the REST API deletion input file that provides based on the communication network territory, based on system identical with embodiment one, the related definition of resource, action and data structure is please with reference to the explanation among the embodiment one.
Fig. 3 is the flow chart of present embodiment based on REST API deletion input file, and this flow process may further comprise the steps:
Step S301: client is the resource of use with the input file of request deletion, sends deletion input file request message to server, carries the resource unified resource position sign (URL) of said resource;
In the deletion input file request message of present embodiment, comprise the action and the resource of use in the message header, can not carry message body.
Client can generate this message in the following manner:
Input file with the request deletion is the resource of use; Deletion (Delete) action with HTTP is the action of use; Generate message header, the resource URL of said resource comprises at least one in terminal participant's (participant of request deletion input file) the indications of user's indications and file transfer session (the corresponding document transmission session of this terminal participant participation).
Generate deletion input file request message according to said message header.
Below with a bright deletion input file request message that once generates of as an exampleBSEMGVR takeN-PSVSEMOBJ.
Suppose that the terminal participant is user Peter E.Xample (SIP:user2example.com), file transfer session is that { FileTransferSessionId1}, this request is the deletion input file.
Below for deleting the example of input file request message content:
DELETE
Http: // serverRoot}/apiVersion}/FileTransfer/Terminating/SIP:user2example.co m/FileTransferSessions/{FileTransferSessionId1}/file HTTP/1.1 the resource URL of action+resource
Accept：application/xml
Host：example.com:80
Step S302: said server is deleted said input file after receiving said deletion input file request message, returns deletion input file response message to said client.
In the deletion input file response message, message header comprises the responder of HTTP, can not carry message body.
During the success of server deletion input file, can generate this message in the following manner:
The responder of representing " no content (No content) " according to HTTP generates message header;
Generate deletion input file response message according to said message header.
During below for the success of deletion input file, the example of deletion input file request message content:
HTTP/1.1204No?content
Date：Thu，04Jun?200902:51:59GMT
Fig. 4 is comprehensive the foregoing description, receives the operation chart of input file and deletion input file between the client and server.
During file transfer is carried out, the input file preservation that can upload onto the server;
Afterwards, client-requested receives input file, may further comprise the steps:
Client generates and receives the input file request message;
User end to server sends said reception input file request message;
Server is resolved and is handled after receiving and receiving the input file request message, obtains the information of said input file;
Server generates and receives the input file response message;
Server returns to said client and receives the input file response message.
Afterwards, client can be carried out the file reception according to the information of input file in the response.
Like client-requested deletion input file, may further comprise the steps:
Client generates deletion input file request message;
User end to server sends deletion input file request message;
Server is resolved and is handled after receiving deletion input file request message, the deletion input file;
Server generates deletion input file response message;
Server returns deletion input file response message to said client.
The content of above-mentioned each message and generation method see also the description in the preceding text, no longer repeat.
In the such scheme; The open telecommunication capability interface of reception and deleted file in the clear specifically document transmission process; The content of each message promptly can satisfy the professional needs of file transfer, goes for related specifications such as the related specifications among the OMA, the IEFT FTP etc. of existing open telecommunication capability again.Greatly facilitating Web developer, third party developer or service provider etc. receives and the relevant control of deleting input file server with the API of REST style neatly.
One of ordinary skill in the art will appreciate that all or part of step in the said method can instruct related hardware to accomplish through program, said program can be stored in the computer-readable recording medium, like read-only memory, disk or CD etc.Alternatively, all or part of step of the foregoing description also can use one or more integrated circuits to realize, correspondingly, each the module/unit in the foregoing description can adopt the form of hardware to realize, also can adopt the form of software function module to realize.The present invention is not restricted to the combination of the hardware and software of any particular form.
The above is merely the preferred embodiments of the present invention, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.All within spirit of the present invention and principle, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (12)
1. method that receives input file, this method realizes based on presentation state-transition (REST) API (API) that the communication network territory provides, comprising:
Client is the resource of use with the input file that request receives, and sends to server and receives the input file request message, carries the resource unified resource position sign (URL) of said resource;
After said server is received said reception input file request message, obtain the information of said input file, return input file response message, the information of carrying said input file of receiving to said client.
2. method according to claim 1 is characterized in that:
The information that comprises the action of use in the said reception input file request message; Said action is the obtaining of Hypertext Transfer Protocol(HTTP) (HTTP) (GET) action, and the resource URL of said resource comprises at least a in terminal participant's the indications of user's indications and file transfer session.
3. method according to claim 1 is characterized in that:
The information of said input file comprises at least a in the following information: receive message session retransmission protocol (MSRP) path, send MSRP path, bytes range, successfully report, failure reporting, recipient user's indications, sender user's indications, file date, file content deployment, file content types and resource URL.
4. according to claim 1 or 3 described methods, it is characterized in that client is sent and received before the input file request message, generates said reception input file request message by following mode:
The action that (GET) is use of obtaining with HTTP; The input file that receives with request is the resource of use; Generate message header, the resource URL of said resource comprises the terminal participant's who asks the reception input file the user's indications and/or the indications of the corresponding document transmission session that this terminal participant participates in;
Generate reception input file request message according to said message header.
5. method according to claim 4 is characterized in that:
Said server receives the input file success, returns to receive before the input file response message, generates said reception input file response message by following mode:
Represent the responder of " success (OK) " to generate message header according to HTTP;
Generate the data structure of a file according to the information of said input file, as message body;
Generate reception input file response message according to said message header and message body.
6. method of deleting input file, this method realizes based on presentation state-transition (REST) API (API) that the communication network territory provides, comprising:
Client is the resource of use with the input file of request deletion, sends deletion input file request message to server, carries the resource unified resource position sign (URL) of said resource;
Said server is deleted said input file after receiving said deletion input file request message, returns deletion input file response message to said client.
7. method according to claim 6 is characterized in that:
Said deletion input file request message comprises the information of the action of use; Said action is deletion (Delete) action of Hypertext Transfer Protocol(HTTP) (HTTP), and the resource URL of said resource comprises at least a in terminal participant's the indications of user's indications and file transfer session.
8. method according to claim 6 is characterized in that:
Said client is sent before the deletion input file request message, generates said deletion input file request message by following mode:
Input file with the request deletion is the resource of use; Deletion (Delete) action with HTTP is the action of use; Generate message header, the resource URL of said resource comprises the terminal participant's who asks the deletion input file the user's indications and/or the indications of the corresponding document transmission session that this terminal participant participates in;
Generate said deletion input file request message according to said message header;
The success of said server deletion input file is returned before the deletion input file response message, generates deletion input file response message by following mode:
The responder of representing " no content (No content) " according to HTTP generates message header;
Generate deletion input file response message according to said message header.
9. system that receives input file, client and server is mutual based on presentation state-transition (REST) API (API) that the communication network territory provides, and this system comprises:
Message creating apparatus in the client is used for generating reception input file request message;
Message dispensing device in the client is used for sending said reception input file request message to server;
Message sink in the server and processing unit are used to receive and resolve and handle after receiving the input file request message, obtain the information of said input file;
Message creating apparatus in the server is used for generating reception input file response message;
Message dispensing device in the server is used for returning said reception input file response message to said client.
10. system as claimed in claim 9 is characterized in that:
Message creating apparatus in the said client comprises again:
Message header generates sub-device; Be used for the action that (GET) is use of obtaining with HTTP; The input file that receives with request is the resource of use; Generate message header, the resource URL of said resource comprises the terminal participant's who asks the reception input file the user's indications and/or the indications of the corresponding document transmission session that this terminal participant participates in;
Message generates sub-device, is used for generating said reception input file request message according to said message header;
Message creating apparatus in the said server comprises again:
Message header generates sub-device, and the responder according to HTTP representes " success " generates message header;
Message body generates sub-device; Be used for according to the input file that receives reception message session retransmission protocol (MSRP) path, send at least a of MSRP path, bytes range, successfully report, failure reporting, recipient user's indications, sender user's indications, file date, file content deployment, file content types and resource URL; Generate the data structure of a file, as message body;
Message generates sub-device, is used for generating said reception input file response message according to said message header and message body.
11. a system of deleting input file, client and server is mutual based on presentation state-transition (REST) API (API) that the communication network territory provides, and this system comprises:
Message creating apparatus in the client is used for generating deletion input file request message;
Message dispensing device in the client is used for sending said deletion input file request message to server;
Message sink in the server and processing unit are used for after receiving said deletion input file request message, resolving and handling, and delete said input file;
Message creating apparatus in the server is used for generating deletion input file response message;
Message dispensing device in the server is used for returning said deletion input file response message to said client.
12. system as claimed in claim 11 is characterized in that:
Message creating apparatus in the said client comprises again:
Message header generates sub-device; The input file that is used for the request deletion is the resource of use; Deletion (Delete) action with HTTP is the action of use; Generate message header, the resource URL of said resource comprises the terminal participant's who asks the deletion input file the user's indications and/or the indications of the corresponding document transmission session that this terminal participant participates in;
Message generates sub-device, is used for generating said deletion input file request message according to said message header;
Message creating apparatus in the said server comprises again:
Message header generates sub-device, is used for representing that according to HTTP the responder of " no content (No content) " generates message header;
Message generates sub-device, is used for generating said deletion input file response message according to said message header.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010548492.XA CN102469138B (en) | 2010-11-17 | 2010-11-17 | The method and system of a kind of reception and deleting input document |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010548492.XA CN102469138B (en) | 2010-11-17 | 2010-11-17 | The method and system of a kind of reception and deleting input document |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102469138A true CN102469138A (en) | 2012-05-23 |
| CN102469138B CN102469138B (en) | 2015-09-16 |
Family
ID=46072301
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010548492.XA Active CN102469138B (en) | 2010-11-17 | 2010-11-17 | The method and system of a kind of reception and deleting input document |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102469138B (en) |
Citations (2)
| 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 | 国际商业机器公司 | The method and system that is used for the cross-domain alternation of Web application |
-
2010
- 2010-11-17 CN CN201010548492.XA patent/CN102469138B/en active Active
Patent Citations (2)
| 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 | 国际商业机器公司 | The method and system that is used for the cross-domain alternation of Web application |
Non-Patent Citations (1)
| Title |
|---|
| DAVID LOZANO等: "WIMS 2.0: Converging IMS and Web 2.0. Designing REST APIs for the", 《IEEE》, 19 September 2008 (2008-09-19), pages 18 - 24, XP031409649 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102469138B (en) | 2015-09-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9565297B2 (en) | True convergence with end to end identity management | |
| KR101274366B1 (en) | Method and apparatus for address book contact management | |
| CN100401724C (en) | Method and device for transfer immediate news | |
| US20040107143A1 (en) | Method for authorizing indirect content download | |
| US20080294729A1 (en) | Email object for open mobile alliance data synchronization usage | |
| KR100977188B1 (en) | Deleting mechanism in SIP multimedia services | |
| EP2243262B1 (en) | Systems and methods for adding media content to electronic messages | |
| CN102469042B (en) | Chat sessions sends output message and obtains the method and system of output message | |
| CN100377522C (en) | OMA download realizing method in content distributing network | |
| Salinas | Advantages and disadvantages of using presence service | |
| KR101973531B1 (en) | Method and apparatus for automatically sharing applications between multiple clients | |
| CN102045659B (en) | The polychrome exhibiting method of instant message and system | |
| CN102469041B (en) | Chat sessions starts and obtains the method and system of session list | |
| US20130091287A1 (en) | System for contact subscription invitations in a cross-domain converged address book system | |
| CN102469148B (en) | Chat sessions is accepted the invitation and is refused the method and system of invitation | |
| CN101202953B (en) | Method and system of shortcut reversion | |
| CN102469136B (en) | A kind of chat sessions increases participant and obtains the method and system of participant list | |
| CN102469135B (en) | The method and system of ends file transfer session and acquisition file transfer session information | |
| CN102469138B (en) | The method and system of a kind of reception and deleting input document | |
| EP2117217B1 (en) | Voice mail service in communications system | |
| CN102469139A (en) | Method and system for ending chatting conversation and acquiring chatting conversation information | |
| CN102469090B (en) | The method and system of startup file transmission session and the list of acquisition file transfer session | |
| CN102469147B (en) | Chat sessions obtains input message and deletes the method and system of input message | |
| CN102469137B (en) | Method and system for accepting document transmission invitation and refusing document transmission invitation | |
| CN101106538A (en) | Message notification method, system and device in session initialization protocol domain |
Legal Events
| 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 |
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. |
|
| TR01 | Transfer of patent right | ||
| 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. |
|
| CP02 | Change in the address of a patent holder |