CN102469137A - Method and system for accepting document transmission invitation and refusing document transmission invitation - Google Patents
Method and system for accepting document transmission invitation and refusing document transmission invitation Download PDFInfo
- Publication number
- CN102469137A CN102469137A CN2010105482661A CN201010548266A CN102469137A CN 102469137 A CN102469137 A CN 102469137A CN 2010105482661 A CN2010105482661 A CN 2010105482661A CN 201010548266 A CN201010548266 A CN 201010548266A CN 102469137 A CN102469137 A CN 102469137A
- Authority
- CN
- China
- Prior art keywords
- message
- file transfer
- invitation
- participant
- action
- 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
Abstract
The invention relates to a method and system for accepting a document transmission invitation and refusing the document transmission invitation, which are realized on the basis of REST API provided by a telecommunication network domain. When the document transmission invitation needs to be refused, a client end sends a message for refusing the document transmission invitation to a server, wherein the message is carried with used action and resource information and information indicating refusing the invitation; and after receiving the message for refusing the document transmission invitation, the server returns a response message for refusing the document transmission invitation to the client end. When the document transmission invitation needs to be accepted, the client end sends a message for accepting the document transmission invitation to the server, wherein the message is carried with used action and resource information and information indicating invitation acceptation; and after receiving the message for accepting the document transmission invitation, the server returns a response message for accepting the document transmission invitation to the client end. According to the invention, the problem that a user cannot call the capability of the telecommunication to realize control on accepting the document transmission invitation and refusing the document transmission invitation is solved.
Description
Technical field
The present invention relates to file transfer, relate in particular to a kind of method and system that file transfer is invited and the refusal file transfer is invited of accepting.
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 State Transfer, 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 realize accepting the relevant control that file transfer invitation was invited and refused to file transfer.
Summary of the invention
In view of this, one object of the present invention is to provide a kind of method and system that file transfer is invited of accepting, and can not call telecommunication capability to solve the user, and the problem of the relevant control of file transfer invitation is accepted in realization.
In order to address the above problem, the invention provides a kind of method that file transfer is invited of accepting, this method realizes based on presentation state-transition (REST) API (API) that the communication network territory provides, comprising:
User end to server sends and accepts the file transfer invitation message, and the action that portably uses and the information of resource reach the information that expression is accepted the invitation, and said resource indicates with unified resource position sign (URL);
Said server receive said accept the file transfer invitation message after, return to said client and to accept file transfer invitation response message.
Preferably
The said action of using is layout (POST) action of HTTP or sets (PUT) 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 invitation.
Preferably
At least a in said message session retransmission protocol (MSRP) the client routing information of accepting participant addresses, participant's name, participant's state and participant that the file transfer invitation message also comprises the terminal participant who is invited.
Preferably
Client is sent and is accepted before the file transfer invitation message, generates the said file transfer invitation message of accepting by following mode:
Layout (POST) action or setting (PUT) action with HTTP are the action of use; Invite the resource that is fed back to use with file transfer; Generate message header, the resource URL of said resource comprises the terminal participant's who is invited user's indications and/or the indications that file transfer is invited;
Parameter value according to expression " accepting the invitation " generates invitation feedback data structure, as message body;
Generate the said file transfer invitation message of accepting according to said message header and message body.
Preferably
Generate before the said invitation feedback data structure; First at least a according in the terminal participant's who is invited participant addresses, participant's name, participant's state and participant's message session retransmission protocol (MSRP) the client routing information, the data structure of spanned file transmission session participant information;
When generating said invitation feedback data structure, also the data structure of said file transfer session participant information and the indications of corresponding file transfer session are write said invitation feedback data structure.
Preferably
When the terminal participant accepted file transfer and invites successfully, said server returns to be accepted before the file transfer invitation response message, generates in the following manner and accepts file transfer invitation response message:
Represent the responder of " no content (No Content) " according to HTTP, generate message header;
Accept file transfer invitation response message according to said message header generation.
Correspondingly, the present invention also provides a kind of system that file transfer is invited that accepts, and 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 and accepts the file transfer invitation message;
Message dispensing device in the client is used for accepting the file transfer invitation message to the server transmission;
Message sink in the server and processing unit are used for resolving and handling after accepting the file transfer invitation message receiving;
Message creating apparatus in the server is used for generating and accepts file transfer invitation response message;
Message dispensing device in the server is used for returning the said file transfer invitation response message of accepting to said client.
Preferably
Message creating apparatus in the said client comprises again:
Message header generates sub-device; Being used for layout (POST) action with HTTP or setting (PUT) action is the action of use; Invite the resource that is fed back to use with file transfer; Generate message header, the resource URL of said resource comprises the terminal participant's who is invited user's indications and/or the indications that file transfer is invited;
Message body generates sub-device; Be used at least a according to by the terminal participant's that invited participant addresses, participant's name, participant's state and participant's message session retransmission protocol (MSRP) client routing information, the data structure of spanned file transmission session participant information; And, generates an invitation feedback data structure, as message body according to the data structure of said file transfer session participant information, parameter value that expression " is accepted the invitation " and the indications of corresponding file transfer session;
Generate the said file transfer invitation message of accepting according to said message header and message body;
Message creating apparatus in the said server comprises again:
Message header generates sub-device, is used for representing according to HTTP the responder of " no content (No Content) ", generates message header;
Message generates sub-device, is used for accepting file transfer invitation response message according to said message header generation.
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, accept the relevant control that file transfer is invited.
In view of this, another object of the present invention is to provide a kind of method and system that file transfer is invited of refusing, and can not call telecommunication capability to solve the user, realizes the problem of the relevant control that the refusal file transfer is invited.
In order to address the above problem, the invention provides a kind of method that file transfer is invited of refusing, this method realizes based on presentation state-transition (REST) API (API) that the communication network territory provides, comprising:
User end to server sends refusal file transfer invitation message, the action that portably uses and the information of resource, and represent the information that refusal is invited, said resource indicates with unified resource position sign (URL);
After said server is received said refusal file transfer invitation message, return refusal file transfer invitation response message to said client.
Preferably
The said action of using is layout (POST) action of HTTP or sets (PUT) action or deletion (DELETE) 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 invitation.
Preferably
Client is sent before the refusal file transfer invitation message, generates said refusal file transfer invitation message by following mode:
Moving or set (PUT) action or delete (DELETE) action with the layout (POST) of HTTP is the action of use; Invite the resource that is fed back to use with file transfer; Generate message header, the resource URL of said resource comprises the terminal participant's who is invited user's indications and/or the indications that file transfer is invited;
The feedback data structure is invited in one of indications generation according to the parameter value of representing " refusal is invited " and corresponding file transfer session, as message body;
Generate said refusal file transfer invitation message according to said message header and message body.
Preferably
When the terminal participant refused file transfer and invites successfully, said server returned before the refusal file transfer invitation response message, generated refusal file transfer invitation response message in the following manner:
Represent the responder of " no content (No Content) " according to HTTP, generate message header;
Generate refusal file transfer invitation response message according to said message header.
Correspondingly, the present invention also provides a kind of system that file transfer is invited of refusing, and client and server is mutual based on presentation state-transition (REST) API (API) that the communication network territory provides, and comprising:
Message creating apparatus in the client is used for generating refusal file transfer invitation message;
Message dispensing device in the client is used for sending refusal file transfer invitation message to server;
Message sink in the server and processing unit are used for after receiving refusal file transfer invitation message, resolving and handling;
Message creating apparatus in the server is used for generating refusal file transfer invitation response message;
Message dispensing device in the server is used for returning refusal file transfer invitation response message to said client.
Preferably
Message creating apparatus in the said client comprises again:
Message header generates sub-device; Being used for layout (POST) action with HTTP or setting (PUT) action or delete (DELETE) action is the action of use; Invite the resource that is fed back to use with file transfer; Generate message header, the resource URL of said resource comprises the terminal participant's who is invited user's indications and/or the indications that file transfer is invited;
Message body generates sub-device, is used for inviting the feedback data structure according to one of the indications generation of the parameter value of representing " refusal is invited " and corresponding file transfer session, as message body;
Message generates sub-device, is used for generating said refusal file transfer invitation message according to said message header and message body;
Message creating apparatus in the said server comprises again:
Message header generates sub-device, is used for representing according to HTTP the responder of " no content (No Content) ", generates message header;
Message generates sub-device, is used for generating refusal file transfer invitation 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, refuse the relevant control that file transfer is invited.
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 accepts the flow chart of the method for file transfer invitation for the embodiment of the invention one;
Fig. 3 is the flow chart of the method for the embodiment of the invention two refusal file transfer invitations;
Accept the sketch map that file transfer is invited, the refusal file transfer is invited associative operation between the client and server that Fig. 4 is invited for the embodiment of the invention.
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 accepts the relevant control that file transfer is invited 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.
In the literary composition, accept file transfer and invite (Accept FileTransfer Request) also can be called to accept file transfer requests, the refusal file transfer invites (Decline FileTransfer Request) also can be called the refusal file transfer requests.
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; ApiVersion representes the API version, and FileTransfer representes file transfer, and Terminating representes terminal (by invited party); TerminatingID representes user's indications of terminal participant, as adopting the terminal participant addresses.{ FileTransferRequest Id} representes file transfer invitation indications.
The type of data structure that above-mentioned REST API uses defines as follows:
Type of data structure Type:Requestfeedback invites feedback
Type of data structure Type:FileTransferParticipantInformation file transfer session participant information
Wherein, File transfer session participant's (comprising source end, terminal) resource URL can the include file transmission session resource URL and participant's indications (participantId) expression, the resource URL of file transfer session can comprise participant user's indications and file transfer session indications.
Enumerate Enumeration:FileTransferParticipantStatus file transfer session participant state
Fig. 2 accepts the flow chart that file transfer is invited for present embodiment based on REST API, may further comprise the steps:
Step S201: user end to server sends and accepts the file transfer invitation message, and the action that portably uses and the information of resource reach the information that expression is accepted the invitation, and said resource indicates with resource unified resource position sign (URL);
Accepting in the file transfer invitation message of present embodiment comprises the action and the resource of use in the message header, comprise in the message body inviting the feedback data structure.
Client can generate this message in the following manner:
Layout (POST) action or setting (PUT) action with HTTP are the action of use; Invite the resource that is fed back to use with file transfer; Generate message header, the resource URL of said resource comprises at least one in the terminal participant's who is invited the indications of user's indications and file transfer invitation;
According to the XML form, invite the feedback data structure according to the parameter value generation of expression " accepting the invitation ", as message body;
Accept the file transfer invitation message according to said message header and message body generation.
Alternatively; When generating message body; Earlier according to the XML form; At least a according to by in the file transfer session terminal participant's that invited participant addresses, participant's name, participant's state, participant's MSRP (message session retransmission protocol) the client routing information, the data structure of spanned file transmission session participant information generates the data structure that writes this document transmission session participant information when inviting the feedback data structure.Invite the feedback data structure can also write the file transfer session indications of inviting the file transfer that adds.
The message body that each embodiment relates to also can be adopted XML outer other professional formats such as java script object symbol (JSON).
Below with as an exampleBSEMGVR takeN-PSVSEMOBJ bright once generate accept the file transfer invitation message.
Suppose that the terminal participant is user Peter E.Xample (SIP:user2example.com), this user accepts file transfer and invites.
Below for accepting the example and the explanation of file transfer invitation message content:
POST
http://{serverRoot}/{apiVersion}/FileTransfer/Terminating/SIP:user2example.com/FileTransferRequests/{Fi
LeTransferRequestIdl}/feedback HTTP/1.1 the HTTP URL of action+resource
Content-Type：application/xml
Accept：application/xml
Host：example.com:80
<?xml?version＝″1.0″encoding＝″UTF-8″?>
< FileTransfer:Requestfeedback xmlns:FileTransfer=" urn:oma:xml:rest:FileTransfer:1 ">invite feedback data structure
Beginning
<acceptRequest>True</AcceptRequest>Represent the parameter value of whether accepting the invitation
<fileTransferSessionID>{ FileTransferSessionId1}</FileTransferSessionID>The file transfer session indications
< Invitee>invitee's the beginning of file transfer session participant information data structure
<participantAddress>SIP:user2example.com</participantAddress>
<participantName>Peter?E.Xample</participantName>
<participantStatus>FileTransferParticipantAcceptRequest</participantStatus>
<MSRPClientPath>msrp://Peter?E.Xample.example.com:7575/u3978ae283wzd；tcp
</MSRPClientPath>
</Invitee>Invitee's the beginning of file transfer session participant information data structure</FileTransfer:Requestfeedback>Invite the end of feedback data structure
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: said server receive said accept the file transfer invitation message after, return to said client and to accept file transfer invitation response message.
Accept in the file transfer invitation response message, message header comprises the responder of HTTP, can not carry message body.
When the terminal participant accepted file transfer and invites successfully, server can generate this message in the following manner:
Represent the responder of " no content (No Content) " according to HTTP, generate message header;
Accept file transfer invitation response message according to said message header generation.
Below when accepting file transfer and invite successfully, accept the example and the explanation of file transfer invitation response message content:
HTTP/1.1204?No?Content
Date：Mon，28Jun?2010?17:51:59?GMT
Embodiment two
The relevant control that the REST API refusal file transfer that present embodiment relates to be provided based on the communication network territory is invited.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 that present embodiment is invited based on REST API refusal file transfer, may further comprise the steps:
Step S301: user end to server sends refusal file transfer invitation message, the action that portably uses and the information of resource, and represent the information that refusal is invited, said resource indicates with resource unified resource position sign (URL);
The message header of refusal file transfer invitation message comprises the action and the resource of use, comprises in the message body and invites the feedback data structure.
Client can generate this message in the following manner:
Moving or set (PUT) action or delete (DELETE) action with the layout (POST) of HTTP is the action of use; Invite the resource that is fed back to use with file transfer; Generate message header, the resource URL of said resource comprises at least one in the terminal participant's who is invited the indications of user's indications and file transfer invitation;
At least a according in the indications of the parameter value of expression " refusal invite " and corresponding file transfer session generates an invitation feedback data structure, as message body;
Generate said refusal file transfer invitation message according to said message header and message body.
Below with a bright refusal file transfer invitation message that once generates of as an exampleBSEMGVR takeN-PSVSEMOBJ.
Suppose that the terminal participant is user Peter E.Xample (SIP:user2example.com), this user asks refusal to be invited.
Below for refusing the example and the explanation of file transfer invitation message content:
POST
http://{serverRoot}/{apiVersion}/FileTransfer/Terminating/SIP:user2example.com/FileTransferRequests/{Fi
LeTransferRequestId1}/feedback HTTP/1.1 the resource URL of action+resource
Content-Type：application/xml
Accept：application/xml
Host：example.com:80
<?xml?version＝″1.0″encoding＝″UTF-8″?>
< FileTransfer:Requestfeedback xmlns:FileTransfer=" urn:oma:xml:rest:FileTransfer:1 ">invite feedback data structure
Beginning
<acceptRequest>False</AcceptRequest>Represent the parameter value of whether accepting the invitation
<fileTransferSessionID>{ FileTransferSessionId1}</FileTransferSessionID>The file transfer session indications
</FileTransfer:Requestfeedback>Invite the end of feedback data structure
Step S302: after said server is received said refusal file transfer invitation message, return refusal file transfer invitation response message to said client.
When the terminal participant refused file transfer and invites successfully, the message header of refusal file transfer invitation response message comprised the responder of HTTP, can not carry message body.
This message can generate in the following manner:
The responder of representing " no content (No Content) " according to HTTP generates message header;
Generate refusal file transfer invitation response message according to said message header.
Fig. 4 is comprehensive the foregoing description, accepts the operation chart that file transfer is invited, the refusal file transfer is invited between the client and server.
File transfer starts, during file transfer is invited (source end participant has sent invitation);
Afterwards, client is accepted file transfer and is invited, and may further comprise the steps:
Client generates accepts the file transfer invitation message;
User end to server sends accepts the file transfer invitation message;
Server receives and accepts to resolve and handle after the file transfer invitation message, as, start and set up file transfer;
Server generates accepts file transfer invitation response message;
Server returns to client and accepts file transfer invitation response message.
Perhaps, client refusal file transfer is invited, and may further comprise the steps:
Client generates refusal file transfer invitation message;
User end to server sends refusal file transfer invitation message;
Server is resolved and is handled after receiving refusal file transfer invitation message, as, notification source end participant;
Server generates refusal file transfer invitation response message;
Server returns refusal file transfer invitation response message to 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 that file transfer is invited is invited and refused to the clear specifically file transfer of accepting; 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 facilitate Web developer, third party developer or service provider etc. and neatly server is accepted the relevant control that file transfer is invited and the refusal file transfer is invited with the API of REST style.
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 (14)
1. accept the method that file transfer is invited for one kind, this method realizes based on presentation state-transition (REST) API (API) that the communication network territory provides, comprising:
User end to server sends and accepts the file transfer invitation message, the action that portably uses and the information of resource, and said resource indicates with unified resource position sign (URL);
Said server receive said accept the file transfer invitation message after, return to said client and to accept file transfer invitation response message.
2. method according to claim 1 is characterized in that:
The said action of using is layout (POST) action of HTTP or sets (PUT) 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 invitation.
3. method according to claim 1 and 2 is characterized in that:
At least a in said message session retransmission protocol (MSRP) the client routing information of accepting participant addresses, participant's name, participant's state and participant that the file transfer invitation message also comprises the terminal participant who is invited.
4. method according to claim 1 is characterized in that, client is sent and accepted before the file transfer invitation message, generates the said file transfer invitation message of accepting by following mode:
Layout (POST) action or setting (PUT) action with HTTP are the action of use; Invite the resource that is fed back to use with file transfer; Generate message header, the resource URL of said resource comprises the terminal participant's who is invited user's indications and/or the indications that file transfer is invited;
Parameter value according to expression " accepting the invitation " generates invitation feedback data structure, as message body;
Generate the said file transfer invitation message of accepting according to said message header and message body.
5. method according to claim 4 is characterized in that:
Generate before the said invitation feedback data structure; First at least a according in the terminal participant's who is invited participant addresses, participant's name, participant's state and participant's message session retransmission protocol (MSRP) the client routing information, the data structure of spanned file transmission session participant information;
When generating said invitation feedback data structure, also the data structure of said file transfer session participant information and the indications of corresponding file transfer session are write said invitation feedback data structure.
6. according to claim 1 or 4 or 5 described methods, it is characterized in that:
When the terminal participant accepted file transfer and invites successfully, said server returns to be accepted before the file transfer invitation response message, generates in the following manner and accepts file transfer invitation response message:
Represent the responder of " no content (No Content) " according to HTTP, generate message header;
Accept file transfer invitation response message according to said message header generation.
7. refuse the method that file transfer is invited for one kind, this method realizes based on presentation state-transition (REST) API (API) that the communication network territory provides, comprising:
User end to server sends refusal file transfer invitation message, the action that portably uses and the information of resource, and said resource indicates with unified resource position sign (URL);
After said server is received said refusal file transfer invitation message, return refusal file transfer invitation response message to said client.
8. method according to claim 7 is characterized in that:
The said action of using is layout (POST) action of HTTP or sets (PUT) action or deletion (DELETE) 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 invitation.
9. method according to claim 7 is characterized in that, client is sent before the refusal file transfer invitation message, generates said refusal file transfer invitation message by following mode:
Moving or set (PUT) action or delete (DELETE) action with the layout (POST) of HTTP is the action of use; Invite the resource that is fed back to use with file transfer; Generate message header, the resource URL of said resource comprises the terminal participant's who is invited user's indications and/or the indications that file transfer is invited;
The feedback data structure is invited in one of indications generation according to the parameter value of representing " refusal is invited " and corresponding file transfer session, as message body;
Generate said refusal file transfer invitation message according to said message header and message body.
10. according to claim 7 or 9 described methods, it is characterized in that:
When the terminal participant refused file transfer and invites successfully, said server returned before the refusal file transfer invitation response message, generated refusal file transfer invitation response message in the following manner:
Represent the responder of " no content (No Content) " according to HTTP, generate message header;
Generate refusal file transfer invitation response message according to said message header.
11. accept the system that file transfer is invited for one kind, client and server is mutual based on presentation state-transition (REST) API (API) that the communication network territory provides, this system comprises:
Message creating apparatus in the client is used for generating and accepts the file transfer invitation message;
Message dispensing device in the client is used for accepting the file transfer invitation message to the server transmission;
Message sink in the server and processing unit are used for resolving and handling after accepting the file transfer invitation message receiving;
Message creating apparatus in the server is used for generating and accepts file transfer invitation response message;
Message dispensing device in the server is used for returning the said file transfer invitation response message of accepting 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; Being used for layout (POST) action with HTTP or setting (PUT) action is the action of use; Invite the resource that is fed back to use with file transfer; Generate message header, the resource URL of said resource comprises the terminal participant's who is invited user's indications and/or the indications that file transfer is invited;
Message body generates sub-device; Be used at least a according to by the terminal participant's that invited participant addresses, participant's name, participant's state and participant's message session retransmission protocol (MSRP) client routing information, the data structure of spanned file transmission session participant information; And, generates an invitation feedback data structure, as message body according to the data structure of said file transfer session participant information, parameter value that expression " is accepted the invitation " and the indications of corresponding file transfer session;
Generate the said file transfer invitation message of accepting according to said message header and message body;
Message creating apparatus in the said server comprises again:
Message header generates sub-device, is used for representing according to HTTP the responder of " no content (No Content) ", generates message header;
Message generates sub-device, is used for accepting file transfer invitation response message according to said message header generation.
13. refuse the system that file transfer is invited for one kind, client and server is mutual based on presentation state-transition (REST) API (API) that the communication network territory provides, and comprising:
Message creating apparatus in the client is used for generating refusal file transfer invitation message;
Message dispensing device in the client is used for sending refusal file transfer invitation message to server;
Message sink in the server and processing unit are used for after receiving refusal file transfer invitation message, resolving and handling;
Message creating apparatus in the server is used for generating refusal file transfer invitation response message;
Message dispensing device in the server is used for returning refusal file transfer invitation response message to said client.
14. system as claimed in claim 13 is characterized in that:
Message creating apparatus in the said client comprises again:
Message header generates sub-device; Being used for layout (POST) action with HTTP or setting (PUT) action or delete (DELETE) action is the action of use; Invite the resource that is fed back to use with file transfer; Generate message header, the resource URL of said resource comprises the terminal participant's who is invited user's indications and/or the indications that file transfer is invited;
Message body generates sub-device, is used for inviting the feedback data structure according to one of the indications generation of the parameter value of representing " refusal is invited " and corresponding file transfer session, as message body;
Message generates sub-device, is used for generating said refusal file transfer invitation message according to said message header and message body;
Message creating apparatus in the said server comprises again:
Message header generates sub-device, is used for representing according to HTTP the responder of " no content (No Content) ", generates message header;
Message generates sub-device, is used for generating refusal file transfer invitation response message according to said message header.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010548266.1A CN102469137B (en) | 2010-11-17 | 2010-11-17 | Method and system for accepting document transmission invitation and refusing document transmission invitation |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010548266.1A CN102469137B (en) | 2010-11-17 | 2010-11-17 | Method and system for accepting document transmission invitation and refusing document transmission invitation |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102469137A true CN102469137A (en) | 2012-05-23 |
| CN102469137B CN102469137B (en) | 2015-07-22 |
Family
ID=46072300
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010548266.1A Active CN102469137B (en) | 2010-11-17 | 2010-11-17 | Method and system for accepting document transmission invitation and refusing document transmission invitation |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102469137B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090252159A1 (en) * | 2008-04-02 | 2009-10-08 | Jeffrey Lawson | 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 CN201010548266.1A patent/CN102469137B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20090252159A1 (en) * | 2008-04-02 | 2009-10-08 | Jeffrey Lawson | 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 exposure of session-based IMS capabilities", 《IEEE》, 19 September 2008 (2008-09-19), pages 18 - 24, XP031409649 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102469137B (en) | 2015-07-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9722888B2 (en) | System and method of using diameter based signaling to activate and deactivate subscriber centric, visually rendered, services | |
| CN103379096A (en) | Internet and operator network service sharing method, service side and webpage gateway | |
| KR100977188B1 (en) | Deleting mechanism in SIP multimedia services | |
| CN102469042B (en) | Chat sessions sends output message and obtains the method and system of output message | |
| Sunaga et al. | Service delivery platform architecture for the next-generation network | |
| US9571563B2 (en) | Handling a shared data object in a communication network | |
| CN102137107A (en) | Method and system for realizing set-top box subscriber state | |
| CN102469041B (en) | Chat sessions starts and obtains the method and system of session list | |
| CN102469148B (en) | Chat sessions is accepted the invitation and is refused the method and system of invitation | |
| US20130091287A1 (en) | System for contact subscription invitations in a cross-domain converged address book system | |
| CN102469136A (en) | Method and system for adding participants and obtaining participant list of chat conversation | |
| CN102469139A (en) | Method and system for ending chatting conversation and acquiring chatting conversation information | |
| CN102469135B (en) | The method and system of ends file transfer session and acquisition file transfer session information | |
| CN102469137B (en) | Method and system for accepting document transmission invitation and refusing document transmission invitation | |
| CN102469090B (en) | The method and system of startup file transmission session and the list of acquisition file transfer session | |
| Henry et al. | Rich communication suite | |
| CN102469147B (en) | Chat sessions obtains input message and deletes the method and system of input message | |
| Blum et al. | Service creation & delivery for SME based on SOA/IMS | |
| CN102469138B (en) | The method and system of a kind of reception and deleting input document | |
| Lee et al. | ROA based web service provisioning methodology for telco and its implementation | |
| Menkens | Towards a context aware mobile community application platform | |
| Cho et al. | The IMS/SDP structure and implementation of presence service | |
| Sheng et al. | Personalized service creation and provision for the mobile web | |
| Moro et al. | Wims 2.0: enabling telecom networks assets in the future internet of services | |
| Cho et al. | An implementation of the SDP using common service enablers |
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: 20201203 Address after: 253300 west side of Sanba South Road, Wucheng County, Dezhou City, Shandong Province Patentee after: Shandong dewu Protection Engineering Co.,Ltd. Address before: Unit 2414-2416, main building, no.371, Wushan Road, Tianhe District, Guangzhou City, Guangdong Province Patentee before: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd. Effective date of registration: 20201203 Address after: Unit 2414-2416, main building, no.371, Wushan Road, Tianhe District, Guangzhou City, Guangdong Province Patentee after: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION 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 |