CN102469090B - The method and system of startup file transmission session and the list of acquisition file transfer session - Google Patents
The method and system of startup file transmission session and the list of acquisition file transfer session Download PDFInfo
- Publication number
- CN102469090B CN102469090B CN201010548608.XA CN201010548608A CN102469090B CN 102469090 B CN102469090 B CN 102469090B CN 201010548608 A CN201010548608 A CN 201010548608A CN 102469090 B CN102469090 B CN 102469090B
- Authority
- CN
- China
- Prior art keywords
- participant
- file transfer
- information
- transfer session
- file
- 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.)
- Active
Links
Landscapes
- Information Transfer Between Computers (AREA)
- Computer And Data Communications (AREA)
Abstract
The method and system of a kind of startup file transmission session and the list of acquisition file transfer session, based on the REST that communication network territory provides? API, during startup file transmission session, comprise: user end to server sends startup file transmission session request message, the action portably used and the information of resource, and the information of the file transfer session of request establishment; Described server creates described file transfer session, and returns startup file transmission session response message to described client.When obtaining file transfer session list, user end to server sends and obtains file transfer session list request message, the action portably used and the information of resource; After described server receives request message, return to described client and obtain file transfer session list response message, carry the described file transfer session list information of acquisition.The present invention can solve user can not call the problem that telecommunication capability comes startup file transmission session and the list of acquisition file transfer session.
Description
Technical field
The present invention relates to file transfer, particularly relate to the method and system of a kind of startup file transmission session and acquisition session list.
Background technology
In the face of the evolution in information communication industry cycle and the transition spring tide of consumer's pattern, in the face of the bone ash level innovation mode of the Internet and the wide-scale distribution of new media or even IT vendor, content integration person and consumer electronics manufacturer are to the infiltration in the field of operation, telecom operators are taking a kind of positive fusion, open attitude, make great efforts to attempt its telecommunication capability open, absorb all the useful ideas, play third party enterprise and the innovation ability of individual, 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 when the flames of war rise all around of market, application on site shop, and operator must utilize telecommunication capability (reliable communication service; User data; Situation; Certification; Charging etc.) make the road of a new differentiation.
Within 1998, Parlay organizes establishment to be devoted to for telephone network exploitation API (API).By these API, the third-party institution can create oneself application.Parlay is organized in this respect and has done unified standardization effort, formulate Parlay/OSA (open Software Description) API based on CORBA (common object Resource Broker framework), the use of various telecommunication capability has been carried out to the uniform operational of programming aspect.Parlay/OSAAPI also obtain ETSI (ETSI) and 3GPP (3G (Third Generation) Moblie partner program normal structure) and jointly assists in addition.In 3 gpp, Parlay is treated as a part of open Software Description (OSA).ParlayX is the API standard criterion based on SOAP (Simple Object Access Protocol) Web service that Parlay, 3GPP and OMA (Open Mobile Alliance) issue.ParlayREST (RESTful towards ParlayX retrains) is the up-to-date a set of API standard criterion issued of OMA, is intended to for RESTWeb service constraints specified by ParlayXWeb service regulation (son) collection in OMA.
In Web2.0 field, support that the API of Ajax (asynchronous JavaScript script and XML extensible markup language) technology is extensive relative to Application comparison, style is REST (REpresentationalStateTransfer, presentation state-transition).REST is not a kind of new technology, neither a kind of standard, but one group of design principle; Compared with the Web service (as ParlayX) based on SOAP, RESTAPI is lightweight more, has more excellent developer's friendly, is convenient to exploitation and the Mashup of Web application.Therefore increasing Web service starts to adopt REST style Design and implementation.Such as, Amazon.com provides the Web service close to REST style to carry out library search; The Web service that Yahoo provides also is REST style (wikipedia).
GSMA (global mobile system association) RCS (rich communication suite) is the business packet providing the rich communication function of interoperable of building out based on existing IMS (IP Multimedia System) network facilities and development agreement, mainly comprise enhanced address book, enhanced call, the business such as enhancement mode converged message, make user can present (as individual picture to oneself, message, recommended links and state) upgrade, also can see that in the address list of mobile phone good friend's presents situation in real time, and realize note, multimedia message, chat (instant message), the multiple communication requirement such as file transfer.RCS comprises unified technology that operator, equipment vendor and mobile phone terminal manufacturer support jointly and realizes standard, and therefore it not only easily cultivates the more consistent use habit of consumer, and can realize country variant, the interconnecting of different operators.Follow-up phase, RCS will introduce further social networks, open RESTAPI API, with the content such as Integrated predict model shop, the Internet.The targeted customer of RCSREST style API is typical Web developer, third party developer, service provider, the RCS professional ability of telecom operators and IMS network ability can be opened by API, be more suitable for the application of Web2.0Widget lightweight and the exploitation of Mashup, cater to the development trend of Web application.
At present, it is open that the professional ability of telecom operators' note, multimedia message can pass through the ParlayREST2.0 consensus standard that OMA (Open Mobile Alliance) formulates, and Record Carrier ability does not also formulate the opening of corresponding consensus standard, user can't call telecommunication capability to realize the startup of file transfer session and to obtain session list.
Summary of the invention
In view of this, one object of the present invention is the method and system providing a kind of startup file transmission session, can not call to solve user the problem that telecommunication capability carrys out startup file transmission session.
In order to solve the problem, the invention provides a kind of method of startup file transmission session, presentation state-transition (REST) API (API) that the method provides based on communication network territory, comprise:
User end to server sends startup file transmission session request message, the action portably used and the information of resource, and the information of the file transfer session of request establishment, and described resource uniform resource locations symbol (URL) indicates;
Described server creates described file transfer session after receiving described startup file transmission session request message, and returns startup file transmission session response message to described client, carries the information of the described file transfer session created.
Preferably,
Layout (POST) action that the action of described use is HTTP, the file transfer session that the resource of described use is source participant, the resource URL of described resource comprises source participant user indications.
Preferably,
The information of the file transfer session that described request creates comprises at least one in following information: source participant information, terminal participant information, file transfer indications, file selector and file are disposed.
Preferably,
The terminal participant information of the file transfer session that described request creates comprises at least one in following information: participant addresses and participant's name; And/or
The source participant information of file transfer session that described request creates comprises at least one in following information: message session retransmission protocol (MSRP) the Client path information of participant addresses, participant's name and participant.
Preferably,
The information of the described file transfer session created comprises at least one in following information: the resource URL of the deployment of source participant information, terminal participant information, file transfer session indications, file transfer session state, file transfer indications, file selector, file and file transfer session.
Preferably,
The source participant information of the described file transfer session created comprises at least one in following information: the resource URL of participant addresses, participant's name, participant's state, participant start-up time, participant, participant's indications, the MSRP Client path information of participant and the MSRP server path information of participant; And/or
The terminal participant information of the described file transfer session created comprises at least one in following information: terminal participant addresses, terminal participant name and terminal participant state.
Preferably, client generates described startup file transmission session request message before sending startup file transmission session request message in the following manner:
Take the layout of HTTP (POST) as the action used, with the resource of the file transfer session of source participant for using, generating messages head, the resource URL of described resource comprises user's indications of the source participant of the request of initiation;
According to source participant information and the terminal participant information of the described file transfer session of request establishment, for each participant generates the data structure of a file transfer session participant information; And according to the data structure of All Files transmission session participant information generated, and at least one in the file transfer indications of described file transfer session, file selector and file deployment information, generate the data structure of a file transfer session information, as message body;
Described startup file transmission session request message is generated according to described message header and message body.
Preferably,
Described server creates the success of described file transfer session, before returning described startup file transmission session response message, generates described startup file transmission session response message in the following manner:
The resource URL of the file transfer session created is generated according to user's indications of source participant and the file transfer session indications of described file transfer session, position (Location) information represented with this resource URL is added, generating messages head represent the responder of " setting up " at HTTP after;
According to source participant information and the terminal participant information of the described file transfer session created, for each participant generates the data structure of a file transfer session participant information; And according to the data structure of All Files transmission session participant information generated, and at least one in the file transfer session state of described file transfer session, file transfer indications, file selector, file deployment and resource URL information, generate the data structure of a file transfer session information, as message body;
Startup file transmission session response message is generated according to described message header and message body.
Correspondingly, in the system of startup file transmission session provided by the invention, presentation state-transition (REST) API (API) that client and server provides based on communication network territory is mutual, and this system comprises:
Message creating apparatus in client, for generating startup file transmission session request message;
Message dispensing device in client, for sending described startup file transmission session request message to server;
Message sink in server and processing unit, for carrying out resolving and processing after receiving startup file transmission session request message, create file transfer session;
Message creating apparatus in server, for generating startup file transmission session response message;
Message dispensing device in server, for returning startup file transmission session response message to described client.
Preferably, the message creating apparatus in described client comprises again:
Message header generates sub-device, for taking the layout of HTTP (POST) as the action used, with the resource of the file transfer session of source participant for using, generating messages head, the resource URL of described resource comprises user's indications of the source participant of the request of initiation;
Message body generates sub-device, for source participant information and the terminal participant information of the described file transfer session according to request establishment, for each participant generates the data structure of a file transfer session participant information; And according to the data structure of All Files transmission session participant information generated, and at least one in the file transfer indications of described file transfer session, file selector and file deployment information, generate the data structure of a file transfer session information, as message body;
The sub-device of message generation, for generating described startup file transmission session request message according to described message header and message body.
Preferably, the message creating apparatus in described server comprises again:
Message header generates sub-device, for generating the resource URL of the file transfer session created according to user's indications of source participant and the file transfer session indications of described file transfer session, position (Location) information represented with this resource URL is added, generating messages head represent the responder of " setting up " at HTTP after;
Message body generates sub-device, for according to the source participant information of described file transfer session created and terminal participant information, for each participant generates the data structure of a file transfer session participant information; And according to the data structure of All Files transmission session participant information generated, and at least one in the file transfer session state of described file transfer session, file transfer indications, file selector, file deployment and resource URL information, generate the data structure of a file transfer session information, as message body;
The sub-device of message generation, for generating startup file transmission session response message according to described message header and message body.
Based on such scheme, the users such as Web developer, third party developer or service provider can pass through client, use RESTAPI to access the telecommunication capability called in telecommunication carrier networks territory, server are carried out to the relevant control of file transfer session startup.
In view of this, another object of the present invention is to provide a kind of method and system obtaining file transfer session list, can not call to solve user the problem that telecommunication capability obtains file transfer session list.
In order to solve the problem, the invention provides a kind of method obtaining file transfer session list, presentation state-transition (REST) API (API) that the method provides based on communication network territory, comprise:
User end to server sends and obtains file transfer session list request message, the action portably used and the information of resource, and described resource uniform resource locations symbol (URL) indicates;
After described server receives described acquisition file transfer session list request message, return to described client and obtain file transfer session list response message, carry the described file transfer session list information of acquisition.
Preferably,
Acquisition (GET) action that the described action used is HTTP, the resource URL of the described resource of use comprises source participant user indications.
Preferably,
Described file transfer session list information comprises at least one in following information: the information of one or more file transfer session, and the resource URL of described file transfer session list; Wherein, at least one in following information is comprised in the information of described file transfer session: source participant information, terminal participant information, file transfer session indications, file transfer session state, file transfer indications, file selector, file are disposed and the resource URL of file transfer session.
Preferably,
Described source participant information comprises at least one in following information: the MSRP Client path information of participant addresses, participant's name, participant's state, participant start-up time, participant's indications, participant, the MSRP server path information of participant and the resource URL of participant; And/or
Described terminal participant information comprises at least one in following information: the resource URL of participant addresses, participant's name, participant's state, participant's start-up time and terminal participant.
Preferably,
Before client sends and obtains file transfer session list request message, generate in the following manner and obtain file transfer session list request message:
Take the acquisition of HTTP (GET) action as the action used, with the resource of source participant All Files transmission session for using, generating messages head, the resource URL of described resource comprises user's indications of source participant;
Described acquisition file transfer session list request message is generated according to described message header.
Preferably,
When described server obtains the file transfer session list information success of source participant, generate the described acquisition file transfer session list response message returned in the following manner:
The response generating messages head of " success " is represented according to HTTP;
To each file transfer session of source participant, according to source participant information and the terminal participant information of this file transfer session, for each participant generates the data structure of a file transfer session participant information, then according to the data structure of the All Files transmission session participant information generated, and at least one in the file transfer session state of this file transfer session, file transfer indications, file selector, file deployment and resource URL, generate the data structure of a file transfer session information;
According to the data structure of All Files transport session information generated and the resource URL of source participant All Files transmission session, the data structure of spanned file transmission session list information, as message body;
Generate according to described message header and message body and obtain file transfer session list response message.
Correspondingly, in the system of acquisition file transfer session provided by the invention list, presentation state-transition (REST) API (API) that client and server provides based on communication network territory is mutual, and this system comprises:
Message creating apparatus in client, obtains file transfer session list request message for generating;
Message dispensing device in client, for sending described acquisition file transfer session list request message to server;
Message sink in server and processing unit, for carrying out resolving and processing after receiving acquisition file transfer session list request message, obtain the file transfer session list information of source participant;
Message creating apparatus in server, obtains file transfer session list response message for generating;
Message dispensing device in server, obtains file transfer session list response message for returning to described client.
Preferably,
Message creating apparatus in described client comprises again:
Message header generates sub-device, for taking the acquisition of HTTP (GET) action as the action used, with the resource of source participant All Files transmission session for using, generating messages head, the resource URL of described resource comprises user's indications of source participant;
The sub-device of message generation, obtains file transfer session list request message for generating according to described message header.
Message creating apparatus in described server comprises again:
Message header generates sub-device, for representing the response generating messages head of " success " according to HTTP;
Message body generates sub-device, for each file transfer session to source participant, according to source participant information and the terminal participant information of this file transfer session, for each participant generates the data structure of a file transfer session participant information, then according to the data structure of the All Files transmission session participant information generated, and at least one in the file transfer session state of this file transfer session, file transfer indications, file selector, file deployment and resource URL, generate the data structure of a file transfer session information; Then according to the data structure of All Files transport session information generated and the resource URL of source participant All Files transmission session, the data structure of spanned file transmission session list information, as message body;
The sub-device of message generation, obtains file transfer session list response message for generating according to described message header and message body.
Based on such scheme, the users such as Web developer, third party developer or service provider can pass through client, use RESTAPI to access the telecommunication capability called in communication network territory, carry out to server the relevant control obtaining file transfer session list.
Accompanying drawing explanation
Fig. 1 is the schematic diagram of the system configuration of the open telecommunication capability interface of the embodiment of the present invention;
Fig. 2 is the flow chart of the method for the embodiment of the present invention one startup file transmission session;
Fig. 3 is the flow chart that the embodiment of the present invention two obtains the method for file transfer session list;
Fig. 4 is startup file transmission session between embodiment of the present invention client and server, the operation chart obtaining file transfer session list.
Embodiment
For making the object, technical solutions and advantages of the present invention clearly understand, hereinafter will be described in detail to embodiments of the invention by reference to the accompanying drawings.It should be noted that, when not conflicting, the embodiment in the application and the feature in embodiment can combination in any mutually.
Embodiment one
Fig. 1 shows the system configuration of the open Record Carrier telecommunication capability interface of the present embodiment.As shown in the figure, 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, Record Carrier server (as RCS Record Carrier engine) and other service servers, but, the server that the present invention is used for Record Carrier also simultaneously for other multiple business, can be not limited to special server.These servers provide to Web developer, third party developer, service provider etc. the RESTAPI opened, the client of the users such as Web developer, third party developer, service provider can use RESTAPI to access communication network territory, call RCS professional ability and the IMS network ability in communication network territory, realize the Web2.0Widget lightweight application of telecommunication service and the exploitation of Mashup.
In the present embodiment, the application program of the User Exploitations such as Web developer, third party developer, service provider can pass through client, and the RESTAPI using the present embodiment to provide carries out file transfer session to server and starts relevant control.Client can be arranged in the network equipment of service provider, also can be arranged in end user device as mobile terminal, fixed terminal etc.The user that the present invention is suitable for also is not limited to the above-mentioned type, can be any file transfer participant having control authority based on Internet service, WEB service.
The resource that in the present embodiment, RESTAPI uses, the related definition of action and data structure are as follows:
In the link of resource Uniform Resource position sign, serverRoot represents server path, apiVersion represents API version, FileTransfer represents file transfer, Originating represents source, and OriginatingID represents user's indications (as being source participant addresses) of source participant (initiating the participant of request).
The type of data structure that above-mentioned RESTAPI uses is defined as follows:
The list of type of data structure Type:FileTransferSessionList file transfer session
Type of data structure Type:FileTransferSessionInformation file transfer session information
Wherein, file selector represents the file attribute of one group of file transfer session description, for selecting the file of specifying, comprises filename, file type, file size, Hash encrypted code etc.; File is disposed and is represented that suggestion receives file side to the processing mode of this file, can be show use " render " immediately, or save as annex " attachment ".User's indications { participantId} and the file transfer session indications (FileTransferSessionId) of source participant can be comprised in the resource URL of file transfer session.
Type of data structure Type:FileTransferParticipantInformation file transfer session participant information
Wherein, the resource URL of file transfer session participant (comprising source, terminal) comprises user's indications of source participant, file transfer session indications and participant's indications (participantId).
Enumerate Enumeration:FileTransferSessionStatus file transfer session state
| Enumeration enumerated value | Description describes |
| FileTransferOngoing | The FileTransfer is built and used session has been set up and has been used |
| FileTransferTerminated | The FileTransfer is terminated session terminates |
| FileTransferRequesting | During The FileTransfer is requesting session (invitation) request is carried out |
Enumerate Enumeration:FileTransferParticipantStatus file transfer session participant state
Fig. 2 is the flow chart of the present embodiment based on RESTAPI startup file transmission session, comprises the following steps:
Step S201: user end to server sends startup file transmission session request message, the action portably used and the information of resource, and the information of the file transfer session of request establishment;
In startup file transmission session request message, message header comprises action and the resource of use, and message body comprises the data structure of file transfer session information.
Client can generate this message in the following manner:
Take the layout of HTTP (POST) as the action used, with the resource of the file transfer session of source participant for using, generating messages head, described resource resource URL indicates, and this resource URL comprises user's indications of the source participant of the request of initiation;
According to XML format, the source participant information of the file transfer session created according to request is as at least one in the MSRP Client path information of address, source participant title and source participant, and terminal participant information is as at least one in terminal participant addresses and terminal participant title, for each participant generates the data structure of a file transfer session participant information;
According to XML format, according to the data structure of the All Files transmission session participant information generated, and at least one in the file transfer indications of described file transfer session, file selector and file deployment information, generate the data structure of a file transfer session information, as message body;
Startup file transmission session request message is generated according to described message header and message body.
Message body in the several message of the present embodiment, also can adopt other professional formats outside XML as java script Object Notation (JSON).
Below with the startup file transmission session request message that an example illustratively generates.
Assuming that source participant is user MaxMuster (SIP:user1example.com), this user starts new file transfer session; The MSRP Client path information of source participant is: msrp: //MaxMuster.example.com:7777/iau39soe2843z; Tcp; Terminal participant is PeterE.Xample (SIP:user2example.com).
Be below example and the explanation of startup file transmission session request message content:
POSThttp://{serverRoot}/{apiVersion}/FileTransfer/Originating/SIP：user1example.com/
FileTransferSessionsHTTP/1.1 the resource URL of resource of action+use
Content-Type：application/xml
Accept：application/xml
Content-Length：1234
Host：example.com:80
<？xmlversion＝″1.0″encoding＝″UTF-8″？>
<FileTransfer:FileTransferSessionInformatio nxmlns:FileTransfer=" urn:oma:xml:rest:FileTransfer:1 " > file
The beginning of transport session information data structure
<participant> the beginning of file transfer session participant information (source) data structure
<participantAddress>SIP：user1example.com</participantAddress>
<participantName>MaxMuster</participantName>
<MSRPClientPath>msrp://MaxMuster.example.com:7777/iau39soe2843z；tcp</MSRPClientPath>
</participant> the end of file transfer session participant information (source) data structure
<participant> the beginning of file transfer session participant information (terminal) data structure
<participantAddress>SIP：user2example.com</participantAddress>
<participantName>PeterE.Xample</participantName>
</participant> the end of file transfer session participant information (terminal) data structure
<file-transfer-id>Q6LMoGymJdh 0IKIgD6wD0jkcfgva4xvE</file-transfer-idGrea tT.GreaT.GT file transfer indications
<File-Selector>name:″Mycoolpicture.jpg″type:image/jpegsize:4092
Hash:sha-1:72:24:5F:E8:65:3D:DA:F3:71:36:2F:86:D4:71:91: 3E:E4:A2:CE:2E</File-SelectorGreatT.GreaT.G T file selector
<file-disposition>attachmentL EssT.LTssT.LTfile-disposition> file is disposed
<clientCorrelator>104567LEssT .LTssT.LT/clientCorrelator> client respective labels
</FileTransfer:FileTransferSessionInformati on> the end of file transfer session information data structure
In the example of the some message contents provided in the application, the action defined in RESTAPI, resource, data structure and partial information are described, other guide as the information defined in data structure, the other guide etc. in message header, please refer to above with the regulation in Web.
Step S202: described server creates described file transfer session after receiving described startup file transmission session request message, and returns startup file transmission session response message to described client, carries the information of the described file transfer session created.
In startup file transmission session response message, message header comprises the responder of HTTP, and message body comprises the data structure of file transfer session information.
When server creates file transfer session success, this message can be generated in the following manner:
The resource URL of the file transfer session created is generated according to user's indications of source participant and the file transfer session indications of described file transfer session, position (Location) information represented with this resource URL is added, generating messages head represent the responder of " setting up " at HTTP after;
According to XML format, according to the source participant information of the file transfer session created as source participant addresses, source participant title, source participant state, source participant start-up time, the MSRP Client path information of source participant, at least one in the information such as the MSRP server path information of source participant and the resource URL of source participant, and terminal participant information is as terminal participant addresses, at least one in the information such as terminal participant title and terminal participant state, for each participant generates the data structure of a file transfer session participant information,
According to XML format, according to the data structure of the All Files transmission session participant information generated, and the file transfer session state of described file transfer session, file transfer indications, file selector, file are disposed and at least one in the information such as resource URL, generate the data structure of a file transfer session information, as message body;
Startup file transmission session response message is generated according to described message header and message body.
Still for above-mentioned application example, assuming that the indications of the file transfer session created for FileTransferSessionId1}, the state of this file transfer session is during session request is carried out; Source participant state is that file transfer session participant connects, and source participant indications is { participantId1}; The MSRP server path information of server is msrp: //Server.example.com:4000/amFDknQZ7OIi; Tcp; The state of terminal participant is during file transfer session participant request is carried out.
Be below example and the explanation of startup file transmission session response message content:
HTTP/1.1201Created
Content-Type：application/xml
Location：
http://{serverRoot}/{apiVersion}/FileTransfer/Originating/SIP：user1example.com/FileTransferSessions/{Fil
ETransferSessionId1} the resource URL of file transfer session that created
Content-Length：1234
Date：Mon，28Jun201017:51:59GMT
<？xmlversion＝″1.0″encoding＝″UTF-8″？>
<FileTransfer:FileTransferSessionInformatio nxmlns:FileTransfer=" urn:oma:xml:rest:FileTransfer:1 " > file
The beginning of transport session information data structure
<participant> the beginning of file transfer session participant information (source) data structure
<participantAddress>SIP：user1example.com</participantAddress>
<participantName>MaxMuster</participantName>
<participantStatus>FileTransferParticipantConnected</participantStatus>
<startTime>2010-06-28T17:50:51</startTime>
<MSRPClientPath>msrp://MaxMuster.example.com:7777/iau39soe2843z；tcp</MSRPClientPath>
<MSRPServerPath>msrp://Server.example.com:4000/amFDknQZ7OIi；tcp</MSRPServerPath>
<resourceURL>
http://{serverRoot}/{apiVersion}/FileTransfer/Originating/SIP：user1example.com/FileTransferSessions/{Fil
ETransferSessionId1}/participants/{participantId1} the resource URL of source participant
</resourceURL>
</participant> the end of file transfer session participant information (source) data structure
<participant> the beginning of file transfer session participant information (terminal) data structure
<participantAddress>SIP：user2example.com</participantAddress>
<participantName>PeterE.Xample</participantName>
<participantStatus>FileTransferParticipantRequesting</participantStatus>
</participant> the end of file transfer session participant information (terminal) data structure
<FileTransferSessionStatus>Fi leTransferRequesting</FileTransferSessionSt atus> file transfer session state
<file-transfer-id>Q6LMoGymJdh 0IKIgD6wD0jkcfgva4xvE</file-transfer-idGrea tT.GreaT.GT file transfer indications
<File-Selector>name:″Mycoolpicture.jpg″type:image/jpegsize:4092
Hash:sha-1:72:24:5F:E8:65:3D:DA:F3:71:36:2F:86:D4:71:91: 3E:E4:A2:CE:2E</File-SelectorGreatT.GreaT.G T file selector
<file-disposition>attachmentL EssT.LTssT.LTfile-disposition> file is disposed
<clientCorrelator>104567LEssT .LTssT.LT/clientCorrelator> client respective labels
<resourceURL>
http://{serverRoot}/{apiVersion}/FileTransfer/Originating/SIP：user1example.com/FileTransferSessions/{Fil
ETransferSessionId1}</resourceURLGreatT.Gre aT.GT the resource URL of file transfer session that created
</FileTransfer:FileTransferSessionInformati on> the end of file transfer session information data structure
Embodiment two
The RESTAPI that the present embodiment relates to be provided based on communication network territory obtains the relevant control of file transfer session list.Based on system identical with embodiment one, the related definition of resource, action and data structure please refer to the explanation in embodiment one.
Fig. 3 is that the present embodiment obtains the flow chart of file transfer session list based on RESTAPI, comprises the following steps:
Step S301: user end to server sends and obtains file transfer session list request message, the action portably used and the information of resource, and described resource resource Uniform Resource position sign (URL) indicates;
The message header obtaining file transfer session list request message comprises action and the resource of use, does not need to carry message body.
Client can generate this message in the following manner:
Take the acquisition of HTTP (GET) action as the action used, with the resource of source participant All Files transmission session for using, generating messages head, the resource URL of described resource comprises user's indications of source participant;
Described acquisition file transfer session list request message is generated according to described message header.
Below by the acquisition file transfer session list request message that an example illustratively generates.
Assuming that source participant is user MaxMuster (SIP:user1example.com), this request is the file transfer session list obtaining this user.
Below for obtaining example and the explanation of file transfer session list request message content:
GEThttp://{serverRoot}/{apiVersion}/FileTransfer/Originating/SIP：user1example.com/
FileTransferSessionsHTTP/1.1 the resource URL of resource of action+use
Accept：application/xml
Host：example.com:80
Step S302: after described server receives described acquisition file transfer session list request message, returns to described client and obtains file transfer session list response message, carry the described file transfer session list information of acquisition.
Server returns to client and obtains file transfer session list response message.
When server obtains the file transfer session list information success of source participant, the message header obtaining file transfer session list response message comprises the responder of HTTP, and message body comprises the data structure of file transfer session list information.Can generate in the following manner:
The responder generating messages head of " success (OK) " is represented according to HTTP;
According to XML format, to each file transfer session of source participant, according to source participant information and the terminal participant information of this file transfer session, for each participant generates the data structure of a file transfer session participant information, then according to the data structure of the All Files transmission session participant information generated, and at least one in the file transfer session state of this file transfer session, file transfer indications, file selector, file deployment and resource URL, generate the data structure of a file transfer session information; Wherein, for the mode of the data structure of source participant spanned file transmission session participant information is identical with step 202, during the data structure of file transfer session participant information generated for terminal participant, can also join in this data structure by the resource URL of terminal participant start-up time and terminal participant, the resource URL of terminal participant can represent by the resource URL of described file transfer session and terminal participant indications;
According to XML format, according to the data structure of All Files transport session information generated and the resource URL of file transfer session list information, generate the data structure of a file transfer session list information, as message body;
Generate according to described message header and message body and obtain file transfer session list response message.
Assuming that, obtain user's MaxMuster (SIP:user1example.com) file transfer session list success, have 2 file transfer sessions.Wherein:
The indications of file transfer session one be FileTransferSessionId1}, state is that session has been set up and used; State as the user MaxMuster (SIP:user1example.com) of source participant is that file transfer session participant connects, and indications is { participantId1}; State as the user PeterE.Xample (SIP:user2example.com) of terminal participant is file transfer session participant initialization, and indications is { participantId2}.
The indications of file transfer session two be FileTransferSessionId2}, state is that session has been set up and used; State as the user MaxMuster (SIP:user1example.com) of source participant is that file transfer session participant connects, and indications is { participantId1}; User MaryE.Xample (SIP:user3example.com) indications as terminal participant is { participantId3}.
Time below for obtaining file transfer session list success, obtain example and the explanation of file transfer session list response message content:
HTTP/1.1200OK
Content-Type：application/xml
Content-Length：1234
Date：Mon，28Jun201017:51:59GMT
<？xmlversion＝″1.0″encoding＝″UTF-8″？>
<FileTransfer:FileTransferSessionsListxmlns: FileTransfer=" urn:oma:xml:rest:FileTransfer:1 " > file transfer meeting
The beginning of words information list data structure
<FileTransferSession> the beginning of first file transfer session information data structure
<participant> the beginning of first file transfer session participant information (source) data structure
<participantAddress>SIP：user1example.com</participantAddress>
<participantName>MaxMuster</participantName>
<participantStatus>FileTransferParticipantConnected</participantStatus>
<startTime>2010-06-28T17:50:51</startTime>
<MSRPClientPath>msrp://MaxMuster.example.com:7777/iau39soe2843z；tcp</MSRPClientPath>
<MSRPServerPath>msrp://Server.example.com:4000/amFDknQZ7OIi；tcp</MSRPServerPath>
<resourceURL>
http://{serverRoot}/{apiVersion}/FileTransfer/Originating/SIP：user1example.com/FileTransferSessions/{Fil
ETrahsferSessionId1}/participants/{participantId1} the resource URL of first file transfer session source participant
</resourceURL>
</participant> the end of first file transfer session participant information (source) data structure
<participant> the beginning of first file transfer session participant information (terminal) data structure
<participantAddress>SIP：user2example.com</participantAddress>
<participantName>PeterE.Xample</participantName>
<participantStatus>FileTransferParticipantInitial</participantStatus>
<startTime>2010-06-28T17:50:51</startTime>
<resourceURL>
http://{serverRoot}/{apiVersion}/FileTransfer/Originating/SIP：user1example.com/FileTransferSessions/{Fil
ETransferSessionId1}/participants/{participantId2} the resource URL of first file transfer session terminal participant
</resourceURL>
</participant> the end of first file transfer session participant information (terminal) data structure
<FileTransferSessionStatus>Fi leTransferOngoing</FileTransferSessionStatu s> first file transfer session state
<file-transfer-id>Q6LMoGymJdh 0IKIgD6wD0jkcfgva4xvE</file-transfer-idGrea tT.GreaT.GT first file transfer session
File transfer indications
<File-Selector>name:″Mycoolpicture.jpg″type:image/jpegsize:4092
Hash:sha-1:72:24:5F:E8:65:3D:DA:F3:71:36:2F:86:D4:71:91: 3E:E4:A2:CE:2E</File-SelectorGreatT.GreaT.G T first file
The file selector of transmission session
The file of <file-disposition>attachmentL EssT.LTssT.LTfile-disposition> first file transfer session is disposed
<clientCorrelator>104567LEssT .LTssT.LT/clientCorrelator> the client respective labels of first file transfer session
<resourceURL>http://{serverRoot}/{apiVersion}/FileTransfer/Originating/SIP：user1example.com/FileTrans
FerSessions/{FileTransferSessionId1}</resou rceURL> the resource URL of first file transfer session
</FileTransferSession> the end of first file transfer session information data structure
<FileTransferSession> the beginning of second file transfer session information data structure
<participant> the beginning of second file transfer session participant information (source) data structure
<participantAddress>SIP：user1example.eom</participantAddress>
<participantName>MaxMuster</participantName>
<participantStatus>FileTransferParticipantConnected</participantStatus>
<startTime>2010-06-28T17:50:51</startTime>
<MSRPClientPath>msrp://MaxMuster.example.eom:7778/iau56soe1343x；tcp</MSRPClientPath>
<MSRPServerPath>msrp://Server.example.eom:4010/6soe13QZ7OIi；tcp</MSRPServerPath>
<resourceURL>
http://{serverRoot}/{apiVersion}/FileTransfer/Originating/SIP：user1example.com/FileTransferSessions/{Fil
ETransferSessionId2}/participants/{participantId1} the resource URL of second file transfer session source participant
</resourceURL>
</participant> the end of second file transfer session participant information (source) data structure
<participant> the beginning of second file transfer session participant information (terminal) data structure
<participantAddress>SIP：user3example.com</participantAddress>
<participantName>MaryE.Xample</participantName>
<participantStatus>FileTransferParticipantConnected</participantStatus>
<startTime>2010-06-28T17:50:51</startTime>
<resourceURL>
http://{serverRoot}/{apiVersion}/FileTransfer/Originating/SIP：user1example.com/FileTransferSessions/{Fil
ETransferSessionId2}/participants/{participantId3} the resource URL of second file transfer session terminal participant
</resourceURL>
</participant> the end of second file transfer session participant information (terminal) data structure
<FileTransferSessionStatus>Fi leTransferOngoing</FileTransferSessionStatu s> second file transfer session state
<file-transfer-id>D0jkcfgva4x vEQ6LMoGymJdh0IKIgD6w</file-transfer-idGrea tT.GreaT.GT second file transfer session
File transfer indications
<File-Selector>name:″Myhotpicture.jpg″type:image/jpegsize:4092
Hash:sha-1:86:D4:71:91:3E:E4:A2:CE:2E:72:24:5F:E8:65:3D: DA:F3:71:36:2F:</File-SelectorGreatT.GreaT. GT second literary composition
The file selector of part transmission session
The file of <file-disposition>attachmentL EssT.LTssT.LT/file-disposition> second file transfer session is disposed
<clientCorrelator>204567LEssT .LTssT.LT/clientCorrelator> the client respective labels of second file transfer session
<resourceURL>
http://{serverRoot}/{apiVersion}/FileTransfer/Originating/SIP：user1example.com/FileTransferSessions/{Fil
ETransferSessionId2}</resourceURLGreatT.Gre aT.GT the resource URL of second file transfer session
</FileTransferSession> the end of second file transfer session information data structure
<resourceURL>http://{serverRoot}/{apiVersion}/FileTransfer/Originating/SIP：user1example.com/FileTrans
FerSessions/</resourceURL> the resource URL of file transfer session list information
</FileTransfer:FileTransferSessionsListGrea tT.GreaT.GT the end of file transfer session listing information data structure
Fig. 4 is startup file transmission session between the client and server in conjunction with above-described embodiment, the operation chart obtaining file transfer session list.
Wherein the flow process of client terminal start-up file transfer session comprises the following steps:
Client generates startup file transmission session request message;
User end to server sends described startup file transmission session request message;
Server carries out resolving and processing after receiving startup file transmission session request message, creates file transfer session;
Server generates startup file transmission session response message;
Server returns startup file transmission session response message to described client.
Afterwards, file transfer session is successfully established, and during file transfer session carries out, the flow process that source participant obtains file transfer session list by client comprises the following steps:
Client generates and obtains file transfer session list request message;
User end to server sends described acquisition file transfer session list request message;
Server carries out resolving and processing after receiving acquisition file transfer session list request message, obtains the file transfer session list information of source participant;
Server generates and obtains file transfer session list response message;
Server returns to described client and obtains file transfer session list response message.
The content of each message above-mentioned and generation method refer to description above, no longer repeat.
In such scheme, specifically illustrate the open telecommunication capability interface that file transfer session starts and obtains file transfer session list, namely the content of each message can meet the needs of Record Carrier, goes for again the related specifications of existing open telecommunication capability as the related specifications in OMA, IEFT file transfer protocol (FTP) etc.Greatly facilitate Web developer, third party developer or service provider etc. neatly with the API of REST style server to be carried out to file transfer session startup, obtains the relevant control of file transfer session list.
The all or part of step that one of ordinary skill in the art will appreciate that in said method is carried out instruction related hardware by program and is completed, and described program can be stored in computer-readable recording medium, as read-only memory, disk or CD etc.Alternatively, all or part of step of above-described embodiment also can use one or more integrated circuit to realize, and correspondingly, each module/unit in above-described embodiment can adopt the form of hardware to realize, and the form of software function module also can be adopted to realize.The present invention is not restricted to the combination of the hardware and software of any particular form.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (11)
1. a method for startup file transmission session, the presentation state-transition REST API API that the method provides based on communication network territory, comprising:
User end to server sends startup file transmission session request message, the action portably used and the information of resource, and the information of the file transfer session of request establishment, and described resource uniform resource locations symbol URL indicates;
The information of the file transfer session that described request creates comprises at least one in following information: source participant information, terminal participant information, file transfer indications, file selector and file are disposed;
The terminal participant information of the file transfer session that described request creates comprises at least one in following information: participant addresses and participant's name; The source participant information of file transfer session that described request creates comprises at least one in following information: the message session retransmission protocol MSRP Client path information of participant addresses, participant's name and participant;
Described server creates described file transfer session after receiving described startup file transmission session request message, and returns startup file transmission session response message to described client, carries the information of the described file transfer session created;
The information of the described file transfer session created comprises at least one in following information: the resource URL of the deployment of source participant information, terminal participant information, file transfer session indications, file transfer session state, file transfer indications, file selector, file and file transfer session;
The source participant information of the described file transfer session created comprises at least one in following information: the resource URL of participant addresses, participant's name, participant's state, participant start-up time, participant, participant's indications, the MSRP Client path information of participant and the MSRP server path information of participant; The terminal participant information of the described file transfer session created comprises at least one in following information: terminal participant addresses, terminal participant name and terminal participant state.
2. want the method described in 1 according to right, it is characterized in that, client generates described startup file transmission session request message before sending startup file transmission session request message in the following manner:
With the action of the layout POST of HTTP for using, with the resource of the file transfer session of source participant for using, generating messages head, the resource URL of described resource comprises user's indications of the source participant of the request of initiation;
According to source participant information and the terminal participant information of the described file transfer session of request establishment, for each participant generates the data structure of a file transfer session participant information; And according to the data structure of All Files transmission session participant information generated, and at least one in the file transfer indications of described file transfer session, file selector and file deployment information, generate the data structure of a file transfer session information, as message body;
Described startup file transmission session request message is generated according to described message header and message body.
3. method according to claim 1, is characterized in that:
Described server creates the success of described file transfer session, before returning described startup file transmission session response message, generates described startup file transmission session response message in the following manner:
The resource URL of the file transfer session created is generated according to user's indications of source participant and the file transfer session indications of described file transfer session, the position Location information represented with this resource URL is added, generating messages head represent the responder of " setting up " at HTTP after;
According to source participant information and the terminal participant information of the described file transfer session created, for each participant generates the data structure of a file transfer session participant information; And according to the data structure of All Files transmission session participant information generated, and at least one in the file transfer session state of described file transfer session, file transfer indications, file selector, file deployment and resource URL information, generate the data structure of a file transfer session information, as message body;
Startup file transmission session response message is generated according to described message header and message body.
4. obtain a method for file transfer session list, the presentation state-transition REST API API that the method provides based on communication network territory, comprising:
User end to server sends and obtains file transfer session list request message, the action portably used and the information of resource, and described resource uniform resource locations symbol URL indicates;
After described server receives described acquisition file transfer session list request message, return to described client and obtain file transfer session list response message, carry the described file transfer session list information of acquisition;
Described file transfer session list information comprises at least one in following information: the information of one or more file transfer session, and the resource URL of described file transfer session list; Wherein, at least one in following information is comprised in the information of described file transfer session: source participant information, terminal participant information, file transfer session indications, file transfer session state, file transfer indications, file selector, file are disposed and the resource URL of file transfer session;
Described source participant information comprises at least one in following information: the MSRP Client path information of participant addresses, participant's name, participant's state, participant start-up time, participant's indications, participant, the MSRP server path information of participant and the resource URL of participant; Described terminal participant information comprises at least one in following information: the resource URL of participant addresses, participant's name, participant's state, participant's start-up time and terminal participant.
5. method according to claim 4, is characterized in that, before client sends and obtains file transfer session list request message, generates in the following manner and obtains file transfer session list request message:
With the action of the acquisition GET action of HTTP for using, with the resource of source participant All Files transmission session for using, generating messages head, the resource URL of described resource comprises user's indications of source participant;
Described acquisition file transfer session list request message is generated according to described message header.
6. method according to claim 4, is characterized in that:
When described server obtains the file transfer session list information success of source participant, generate the described acquisition file transfer session list response message returned in the following manner:
The response generating messages head of " success " is represented according to HTTP;
To each file transfer session of source participant, according to source participant information and the terminal participant information of this file transfer session, for each participant generates the data structure of a file transfer session participant information, then according to the data structure of the All Files transmission session participant information generated, and at least one in the file transfer session state of this file transfer session, file transfer indications, file selector, file deployment and resource URL, generate the data structure of a file transfer session information;
According to the data structure of All Files transport session information generated and the resource URL of source participant All Files transmission session, the data structure of spanned file transmission session list information, as message body;
Generate according to described message header and message body and obtain file transfer session list response message.
7. a system for startup file transmission session, the presentation state-transition REST API API that client and server provides based on communication network territory is mutual, and this system comprises:
Message creating apparatus in client, for generating startup file transmission session request message;
Message dispensing device in client, for sending described startup file transmission session request message to server;
Message sink in server and processing unit, for carrying out resolving and processing after receiving startup file transmission session request message, create file transfer session;
Message creating apparatus in server, for generating startup file transmission session response message;
Message dispensing device in server, for returning startup file transmission session response message to described client;
The information of the file transfer session that described request creates comprises at least one in following information: source participant information, terminal participant information, file transfer indications, file selector and file are disposed;
The terminal participant information of the file transfer session that described request creates comprises at least one in following information: participant addresses and participant's name; The source participant information of file transfer session that described request creates comprises at least one in following information: the message session retransmission protocol MSRP Client path information of participant addresses, participant's name and participant;
The information of the described file transfer session created comprises at least one in following information: the resource URL of the deployment of source participant information, terminal participant information, file transfer session indications, file transfer session state, file transfer indications, file selector, file and file transfer session;
The source participant information of the described file transfer session created comprises at least one in following information: the resource URL of participant addresses, participant's name, participant's state, participant start-up time, participant, participant's indications, the MSRP Client path information of participant and the MSRP server path information of participant; The terminal participant information of the described file transfer session created comprises at least one in following information: terminal participant addresses, terminal participant name and terminal participant state.
8. system as claimed in claim 7, it is characterized in that, the message creating apparatus in described client comprises again:
Message header generates sub-device, for the action of the layout POST of HTTP for using, with the resource of the file transfer session of source participant for using, and generating messages head, the resource URL of described resource comprises user's indications of the source participant of the request of initiation;
Message body generates sub-device, for source participant information and the terminal participant information of the described file transfer session according to request establishment, for each participant generates the data structure of a file transfer session participant information; And according to the data structure of All Files transmission session participant information generated, and at least one in the file transfer indications of described file transfer session, file selector and file deployment information, generate the data structure of a file transfer session information, as message body;
The sub-device of message generation, for generating described startup file transmission session request message according to described message header and message body.
9. system as claimed in claim 7 or 8, it is characterized in that, the message creating apparatus in described server comprises again:
Message header generates sub-device, for generating the resource URL of the file transfer session created according to user's indications of source participant and the file transfer session indications of described file transfer session, the position Location information represented with this resource URL is added, generating messages head represent the responder of " setting up " at HTTP after;
Message body generates sub-device, for according to the source participant information of described file transfer session created and terminal participant information, for each participant generates the data structure of a file transfer session participant information; And according to the data structure of All Files transmission session participant information generated, and at least one in the file transfer session state of described file transfer session, file transfer indications, file selector, file deployment and resource URL information, generate the data structure of a file transfer session information, as message body;
The sub-device of message generation, for generating startup file transmission session response message according to described message header and message body.
10. obtain a system for file transfer session list, the presentation state-transition REST API API that client and server provides based on communication network territory is mutual, and this system comprises:
Message creating apparatus in client, obtains file transfer session list request message for generating;
Message dispensing device in client, for sending described acquisition file transfer session list request message to server;
Message sink in server and processing unit, for carrying out resolving and processing after receiving acquisition file transfer session list request message, obtain the file transfer session list information of source participant;
Message creating apparatus in server, obtains file transfer session list response message for generating;
Message dispensing device in server, obtains file transfer session list response message for returning to described client;
Described file transfer session list information comprises at least one in following information: the information of one or more file transfer session, and the resource URL of described file transfer session list; Wherein, at least one in following information is comprised in the information of described file transfer session: source participant information, terminal participant information, file transfer session indications, file transfer session state, file transfer indications, file selector, file are disposed and the resource URL of file transfer session;
Described source participant information comprises at least one in following information: the MSRP Client path information of participant addresses, participant's name, participant's state, participant start-up time, participant's indications, participant, the MSRP server path information of participant and the resource URL of participant; Described terminal participant information comprises at least one in following information: the resource URL of participant addresses, participant's name, participant's state, participant's start-up time and terminal participant.
11. systems as claimed in claim 10, it is characterized in that, the message creating apparatus in described client comprises again:
Message header generates sub-device, for the action of the acquisition GET action of HTTP for using, with the resource of source participant All Files transmission session for using, and generating messages head, the resource URL of described resource comprises user's indications of source participant;
The sub-device of message generation, obtains file transfer session list request message for generating according to described message header;
Message creating apparatus in described server comprises again:
Message header generates sub-device, for representing the response generating messages head of " success " according to HTTP;
Message body generates sub-device, for each file transfer session to source participant, according to source participant information and the terminal participant information of this file transfer session, for each participant generates the data structure of a file transfer session participant information, then according to the data structure of the All Files transmission session participant information generated, and at least one in the file transfer session state of this file transfer session, file transfer indications, file selector, file deployment and resource URL, generate the data structure of a file transfer session information; Then according to the data structure of All Files transport session information generated and the resource URL of source participant All Files transmission session, the data structure of spanned file transmission session list information, as message body;
The sub-device of message generation, obtains file transfer session list response message for generating according to described message header and message body.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010548608.XA CN102469090B (en) | 2010-11-17 | 2010-11-17 | The method and system of startup file transmission session and the list of acquisition file transfer session |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010548608.XA CN102469090B (en) | 2010-11-17 | 2010-11-17 | The method and system of startup file transmission session and the list of acquisition file transfer session |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102469090A CN102469090A (en) | 2012-05-23 |
| CN102469090B true CN102469090B (en) | 2016-01-20 |
Family
ID=46072264
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010548608.XA Active CN102469090B (en) | 2010-11-17 | 2010-11-17 | The method and system of startup file transmission session and the list of acquisition file transfer session |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102469090B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104753985B (en) | 2013-12-30 | 2018-12-28 | 腾讯科技（深圳）有限公司 | Session list display methods and device |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101242423A (en) * | 2007-02-09 | 2008-08-13 | 中国电信股份有限公司 | System and method for realizing open Web conference capability based on HTTP redirection technology |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP3484135A1 (en) * | 2008-04-02 | 2019-05-15 | Twilio Inc. | System and method for processing telephony sessions |
-
2010
- 2010-11-17 CN CN201010548608.XA patent/CN102469090B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101242423A (en) * | 2007-02-09 | 2008-08-13 | 中国电信股份有限公司 | System and method for realizing open Web conference capability based on HTTP redirection technology |
Non-Patent Citations (1)
| Title |
|---|
| WIMS 2.0: Converging IMS and Web 2.0. Designing REST APIs for the exposure of session-based IMS capabilities;David Lozano等;《The Second International Conference on Next Generation Mobile Applications, Services and Technologies》;20080919;正文第1-4节，附图3 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102469090A (en) | 2012-05-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Belqasmi et al. | RESTful web services for service provisioning in next-generation networks: a survey | |
| US9565297B2 (en) | True convergence with end to end identity management | |
| US7505482B2 (en) | Application services infrastructure for next generation networks | |
| JP5946467B2 (en) | Telecommunications service broker for orchestration of services in telecommunications networks | |
| CN101472242A (en) | Business polymerization system and method | |
| JP2012512448A (en) | Method and configuration for creating a virtual relationship between communication devices to publish personal data | |
| KR100977188B1 (en) | Deleting mechanism in SIP multimedia services | |
| CN102469042B (en) | Chat sessions sends output message and obtains the method and system of output message | |
| CN103155530B (en) | Merge including network-telecommunications that script command is downloaded to user terminal | |
| CN102469041B (en) | Chat sessions starts and obtains the method and system of session list | |
| WO2014029441A1 (en) | Handling a shared data object in a communication network | |
| CN102469136B (en) | A kind of chat sessions increases participant and obtains the method and system of participant list | |
| CN102469090B (en) | The method and system of startup file transmission session and the list of acquisition file transfer session | |
| CN102469148B (en) | Chat sessions is accepted the invitation and is refused the method and system of invitation | |
| CN102469135B (en) | The method and system of ends file transfer session and acquisition file transfer session information | |
| Bachmann et al. | Requirements for an extendible IMS client framework | |
| CN102469139B (en) | A kind of ending chatting conversation and the method and system of obtaining chat sessions information | |
| Tarkoma et al. | Spice: A service platform for future mobile ims services | |
| CN102469137B (en) | Method and system for accepting document transmission invitation and refusing document transmission invitation | |
| CN102469147B (en) | Chat sessions obtains input message and deletes the method and system of input message | |
| CN102469138B (en) | The method and system of a kind of reception and deleting input document | |
| Sur et al. | Extending the service bus for successful and sustainable IPTV services | |
| Blum et al. | Service creation & delivery for SME based on SOA/IMS | |
| Yoon | Service delivery platform for open IPTV convergence service creation and management | |
| Schreiner et al. | Modular exposure of next generation network services to enterprises and testbed federations |
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 |