MXPA06011645A - Method and apparatus to convey a uri for content indirection use in sip - Google Patents

Abstract

A content indirection communications method, server, device, data storage medium and computer program product, where in a method executed by the server, in response to a Session Initiation Protocol (SIP) registration request from a device, informing the device in a SIP message of the identity of an address where the device may send information that is to be referenced by a SIP content indirection operation, and allocating storage for the information. Informing the device preferably uses a SIP message Call-Info header field with. a purpose parameter set to ci-uri for indicating that the Call-Info header field contains a Uniform Resource Identifier (URI) that specifies an identity of the storage location.

Description

METHOD AND APPARATUS FOR TRANSMITTING A UNIFIED IDENTIFIER OF RESOURCES (URI) FOR USE OF DEVIATION OF CONTENT IN A SESSION INITIATION PROTOCOL (SIP) FIELD OF THE INVENTION The present invention relates in general to wireless communication systems and methods and more specifically, relates to wireless terminals and nodes of wireless networks that use a Session Initiation Protocol (SIP) or similar or exchange of equivalent messages. BACKGROUND OF THE INVENTION The session initiation protocol (SIP) - is defined in IETF RFC3261 (Rosenberg et al., June 200). In general, the SIP is an application layer control protocol (signaling) to create, modify and terminate sessions with one or more participants. Sessions may include telephone calls over the Internet, multimedia distribution and multimedia conferences. SIP invitations use elements called proxy servers to help direct requests to the user's current location, authenticate and authorize users for services, implement provider call routing policies, and provide features to users. He SIP also provides a registration function that allows users to upload their current locations for Ref .: 176370 to use proxy servers. The SIP runs over different transport protocols. In addition, a draft IETF "draft-ietf-sip-content-indirect-mech-03", entitled "Mechanism for Content Deviation in Session Initiation Protocol (SIP) Messages" (S. Olson, June 2, 2003 ), describes the mechanism for providing content diversion in SIP messages. More specifically, the purpose of the SIP is to create, modify, or terminate sessions with one or more participants, and SIP messages, such as HTTP, are composed in syntax of a start line, one or more headers, and optionally a body. Unlike HTTP, SIP nb is designed as a general-purpose data transport. There are several reasons why it would be desirable to indirectly specify the body content of the SIP message. For limited broadband applications, such as wireless cellular applications, the diversion provides a means to record the content (indirect) with metadata that can be used by the recipient to determine whether or not to retrieve the content with respect to the limited resource link . It is also possible that the size of the content to be transferred overflows intermediate signaling proxies, thus unnecessarily increasing the latency of the network. For time sensitive SIP applications, this may be unacceptable. The use of indirect content can alleviate these drawbacks by moving the content transfer out of the SIP signaling network and into a potentially separate data transfer channel. . There may also be scenarios in which the data related to the session (body) that needs to be transmitted do not reside directly in the endpoint or User Agent (UA). In such scenarios, it is desirable to have a mechanism whereby the SIP message can contain an indirect reference of the desired content. The receiving party would then use this indirect reference to retrieve the content through a transfer channel other than SIP, such as HTTP, FTP, or LDAP. In this draft the IETF is established. that the purpose of the content diversion is only to provide an alternative transport mechanism for body parts of Multiple Purpose Extensions of Internet Mail (MIME). With the exception of the transport mechanism, the diverted body parts are equivalent, and should have the same treatment. In general, MIME is originally intended to extend the mail format over the Internet to allow text messages other than US-ASCII, non-text messages, multi-part message bodies, and information other than US-ASCII in message headers. The following RFCs define MIME: RFC 2045: 'MIME Part One: Format of Internet Message Bodies; RFC 2046: MIME Part Two. Types of Media; RFC 2047: MIME Part Three: Extensions of Message Headers for Text other than ASCII; RFC 2048: MIME Part Four: Registration Procedures; and RFC 2049: MIME Part Five: Criteria and Examples of Conformance. Another draft IETF "draft-khartabil-sip-political-uri- called-info-purpose-00", • entitled "Transmission of a Uniform Resource Identifier (URI) for Sessions Policies in the Protocol of Session Initiation (SIP) "(H.Khartabil and A. Niemi, February 5, 2004) describes an extension to a call information header field to introduce a new purpose parameter value that can be used by an originator or receiver of the request to transmit a URI in which certain information of a session can be accessed. More specifically, this I? TF draft provides a "uri-policy" that can be used by a conference server to indicate the URI of the conference policy to a participating UA in that conference. The IETF draft document mentioned above "draft-ietf-sip-content-indirect-mech-03" defines the content diversion mechanism of the SIP providing an alternative transport mechanism for the MIME SIP body parts. This is done by providing a URI for the indirect content, where the URI 'is specified in a "URI" parameter of the MIME type of message body / external. However, before transmitting this URI in a SIP request or response, the SIP client needs to be informed of the URI in such a way that it can load the indirect content before the indirect content is referenced in a SIP request or response. The IETF draft document draft-ietf-sip-content-indirect-mech-03 does not define the behavior of the client or the server with respect to determining a URI to be used for content diversion. That is, what was not defined, prior to this invention, was a technique or protocol for a SIP UA to request, or be informed of, a storage location on an Application Server (AS). ) wherein the SIP UA can store information that is referenced by means of a subsequent content bypass operation. BRIEF DESCRIPTION OF THE INVENTION The foregoing and other problems are overcome, and other advantages are realized, in accordance with the present preferred embodiments of these teachings. In a first aspect thereof, the present invention provides a communication method comprising receiving a registration request for a device; and informing the device of the identity of an address so that the device sends information to be referenced by a content diversion operation. In another aspect, the present invention provides a device operable with a server, comprising a data processor that responds to a reception of a second message from the server, sent in response to the device that originates a first message, to extract of the second message an identification of a location for the device to send information to be referenced by means of a content bypass operation. In another aspect thereof, the present invention provides a method of content diversion communications, comprising - in response to a request for registration of Session Initiation Protocol (SIP) from a device, informing the device in a message of SIP of the identity of an address in which the device can send information to be referenced by means of a SIP content bypass operation; and assign a storage for the information. In another aspect thereof, the present invention provides a SIP Server comprising a data processor that responds to an occurrence of a SIP registration request made by a device to inform the device by means of a SIP message of a Identity of an address in which the device can send information to be referenced by means of a SIP content bypass operation. In another aspect of it, the present invention provides a device operable with a SIP Server comprising a data processor that responds to a reception of a SIP message from the SIP Server, sent in response to the device that originates a registration request message, to extract of the SIP message an identification of a location in which the device can send information to be referenced by means of a subsequent SIP content bypass operation. In a further aspect thereof, the present invention provides a storage means that can be read by means of a digital processor, the data storage means stores program instructions for use in a content bypass procedure in a data storage operation. SIP and comprising the operations of, in response to receiving a SIP record from a device, reserving a storage location for the device where the device can store information to be referenced by means of a bypass operation. SIP content; and informing the device of a storage location identity using a SIP Message Call Information header field with a purpose parameter set to ci-uri, to indicate that the Call Information header field contains an Identifier Uniform Resource (URI), which specifies the identity of the storage location. In another aspect of it. The present invention provides a Multimedia Messaging Service Relay / Server (MMS) for carrying out a SIP operation with a device, comprising means, which respond to the receipt of a SIP registration request from the device, to reserve a storage location for the device where the device can store information to be referenced by means of a SIP content bypass operation, and means to inform the device of an identity of the location of the device. storage using a SIP Message Call Information header field with a purpose parameter set to ci-uri, to indicate that the Information field header field Call contains a Uniform Resource Identifier (URI) that specifies the identity of the storage location. In yet another embodiment thereof, the present invention provides a means of storing data that can be read by means of a digital data processor, the storage means stores program instructions for use in a content bypass procedure in a SIP operation and comprising operations of receiving a SIP message originating from a SIP server in response to sending a registration request message to the SIP server; identifying a case in which the received SIP message comprises a header field of Call Information comprising a purpose parameter set for ci-uri, to indicate that the Call Information header field contains a Uniform Resource Identifier ( URI) that specifies the identity of a storage location that has been reserved for the device where the device can store information to be referenced by means of a SIP content bypass operation, and send information to the storage location . In still another aspect thereof, the present invention provides an operable device with a SIP Server, wherein the device comprises a data processor that operates in response to a reception of a SIP message originating from a SIP server to identify a case in which the received SIP message comprises a Call Information header field having a purpose parameter set for ci-uri, to indicate that the Call Information header field contains a Uniform Resource Identifier (URI) that specifies the identity of a storage location that has been reserved for the device where the device can store information to be referenced by means of a SIP content bypass operation; data operates additionally to send information to the -location of storage. In still another aspect thereof, the present invention provides an operable device with a Session Initiation Protocol (SIP) Server, comprising means for receiving a SIP message originating from a SIP server to indicate success / failure. of a registration request, to identify a case in which the received SIP message comprises a Call Information header field having a purpose parameter set for ci-uri, to indicate that the Call Information header field it contains a Uniform Resource Identifier (URI) that specifies the identity of a storage location that has been reserved for the device where the device can store information that will be referenced by means of an operation, of diverting SIP content; and the medium loads information corresponding to the indirect content with an HTTP PUT for the storage location specified by the URI that comprises part of the Call Information field of the SIP message. In another aspect thereof, the present invention provides a SIP server that includes a data processor that responds to an occurrence of a SIP registration request made by a device to inform the device by means of a SIP message from a identity of a storage location where the device can send information to be referenced by means of a SIP content bypass operation and, in response to the device, send the information, allocate storage and direct information to the allocated storage. In a further aspect thereof, the present invention provides a method for operating a Session Initiation Protocol (SIP) Server, comprising in response to an occurrence of a SIP registration request made by a device, sending to the device. a SIP message comprising an identity of a storage location in which the device can send information to be referenced by means of a SIP content bypass operation; and in response to the device sending the information, allocating storage and directing information to the allocated storage.

In another aspect thereof, the present invention provides an operable computation program for a SIP Server to conduct a SIP session with a device, comprising the operations of, in response to an occurrence of a SIP registration request made by the device, sending to the device a SIP message comprising an identity of a storage location in which the device can send information to be referenced by means of a SIP content bypass operation, and in response to the device sending information, allocate storage and direct information to the allocated storage. In a further aspect thereof, the present invention provides an operable computation program for a device to perform a SIP operation with a SIP server, comprising the operations of, receiving a SIP message originating from a server. SIP in response to sending a registration request message to the SIP server; identifying a case in which the received SIP message comprises a Call Information header field having a purpose parameter set for ci-uri, to indicate that the Call Information header field contains a Uniform Resource Identifier ( URI) that specifies the identity of a storage location that has been reserved for the device in which the device can store information to be referenced by means of a SIP content bypass operation, and send the information, to the storage location. In another aspect thereof, the present invention provides a method for operating a SIP Server to conduct a SIP session with a device, comprising a step for, executed in response to an occurrence of a SIP registration request made by a device, sending to the device a SIP message comprising an identity of a storage location in which the device can send information to be referenced by means of a SIP content bypass operation; and a step for, executed in response to the device to send the information, allocate storage and direct the information to the allocated storage. In yet another aspect thereof, the present invention provides a method for operating a device to perform a SIP operation with a SIP server comprising in response to the reception of a SIP message originating from a server of SIP. SIP in response to sending a registration request message to the SIP server, a step to identify a case in which the received SIP message comprises a Call Information header field having a purpose parameter set for uri, to indicate that the Call Information header field contains a Uniform Resource Identifier (URI) that specifies the identity of a storage location that has been reserved for the device on which the device can store information to be stored. referenced by means of a SIP content bypass operation; and a step to send the information to the storage location. BRIEF DESCRIPTION OF THE FIGURES The foregoing and other aspects of the embodiments in accordance with the teachings of the present invention are made more apparent in the following detailed description of the preferred embodiments, when read in conjunction with the accompanying figures, in which: Figure 1 is a diagram showing the functional architecture of an IP Multimedia System (IMS) which is a suitable embodiment in which the present invention is practiced, and specifically shows the Ut interface placed between an UE and a SIP Application Server; and Figure 2 is a message flow diagram illustrating the use of the present invention in a Multimedia Messaging Service (MMS) architecture system. DETAILED DESCRIPTION OF THE INVENTION SIP defines a Call Information header (see RFC 3261, Section 20.9, page 166). The purpose of the Call Information header field is to provide additional information about the caller or the called party depending on whether the header is used in a request or in a response. This information contains a URI, and the purpose of the URI is described by means of a "purpose" parameter. The "info" parameter describes the caller or who is called in general, for example, through a Web page. With reference to RFC 3261 on page 166, an example of the Information header is given Call as follows: Call Information: < http: // www. example.com/alicia/foto jpg >; purpose = icon, < http://www.ejemplo.com/alicia/ >; purpose = info. In accordance with one aspect of the present invention, a new "ci-uri" purpose parameter value is used by an Application Server to transmit a URI, which can be used by a SIP UA to divert content. As an example of application of the present invention in a case of generic content diversion, it is assumed that a server supports both SIP and HTTP, if it is further assumed that the content bypass mechanism uses the HTTP URI scheme. During a SIP transaction between the client and the server (for example, during a SIP registration transaction) the server transmits the HTTP URI in a Call Information header field that specifies the storage location to be used for bypass. content (see the example shown in Figure 2 and described below). In addition to the "purpose" parameter, it is preferred that the Call Information header field also contain additional parameters-, such as those defined in the document previously entitled draft-ietf-sip-content-mech-03: "expiration", "type of access "and" size ".

A non-limiting example of a call header field to carry an HTTP URI for purposes of "ci-uri" is as follows: Call Information: < http://www.example.com/the-content-indirect >; purpose = ci-uri; access type = "URL"; expiration = "unes, June 24, 2004 09:00:00 GMT"; size = 4123 When the teachings of the present invention are applied to the architecture of the Multimedia Subsystem of IP (IMS), it is possible to assume that an Application Server can function as the content bypass server. With reference to Figure 1 (obtained from document 3 GPP TSG-CN Meeting # 22, December 10-12, Maui, Hawaii, NP-030457), an Ut interface placed between the UE 2 and an Application Server is shown. SIP / OSA-SCS 3 (also referred to simply as AS 3), which in turn is connected to an S-CSCF 4 through interfaces Sh and Cx 5 and 6, respectively, and an HSS 7, as well as directly through of an ISC interface 8. The S-CSCF 4 (Call Session Control Function in Service) is an IMS element that provides the session control services for UE 2, which allows a network operator to support the services . Functions include: mobile record management, session maintenance, interaction with other servers, cargo and security. The HSS 7 (Base Subscriber Server) describes the various database functions that are required in modern mobile networks. These functions include the General Subscriber Register (HLR), the Domain Name Server (DNS), and security and network access databases. In the context of the present invention, the interface 1 between the UE 2 and the AS 3 is assumed to support HTTP, and the SIP communication is possible from the AS 3 to the UE 2 through the S-CSCF. During the SIP transaction between AS 3 and UE 2, AS 3 can transmit the "ci-uri" in the SIP Call Information header field to UE 2, thus activating UE 2 to load the indirect content to the AS 3 using HTTP in the interface Ut 1. It is understood that in this document, as well as the MMS modality described below, that the SIP Application Server and the UA or UA, which can be generically referred to here simply as devices, each contains a programmed digital data processor of a certain kind which is operable to execute the content diversion procedures related to the SIP in accordance with the present invention. For example, the UE or UA may conform to a cellular phone or personal communicator that includes a built-in processor that operates in accordance with a stored program to execute extraction of the URI from a SIP message received from the SIP Application Server, and subsequently sending the information to be stored to the address specified by the extracted URI, wherein the information is that information that is to be referenced later in a type of SIP message interaction content bypass. In general, the various modalities of the devices corresponding to the UE or UA 2 may include, but are not limited to, cell phones, personal digital assistants (PDAs) that have wireless communication capabilities,. laptops that have wireless communication capabilities, image capture devices such as digital cameras that have wireless communication capabilities, gaming devices that have wireless communication capabilities, storage appliances and music playback that have wireless communication capabilities, devices of Internet that allow the access and navigation to wireless Internet, as well as units or portable terminals or more generally devices that incorporate combinations of such functions. The teachings of the present invention can also be practiced using non-wireless devices, such as desktops and other types of equipment having a wired connection (eg, electrical wire or optical fiber) to a data communications network. Aspects of the present invention therefore also relate to a storage medium for storing computer programs for operating servers and devices in accordance with the present invention, as well as to products -of computer programs executable by servers and devices for operating according to the present invention. As such, Figure 2 shows that the UA 2 device includes a data processor (DP) 2A and a storage medium (DSM, for its acronym in English) 2B, and server 3 includes a DP 3 and a DSM 3B. The present invention can also be used in the context of a Multimedia Messaging Service (MMS) architecture. The Multimedia Messaging Service provides a mechanism to send not only text messages, such as with the Short Message Service (SMS), but also drawings, photographs, music or voice and video clips. The system operates with the "store and send" principle, with messages that are stored and possibly formatted in a Multimedia Messaging Service Center (MMSC) when they are sent between users. Reference may be made, for example, to the Permanent Reference Document of the GSM Association: IR.52, PRD IR.52, MMS Inter-Working Guidelines, Version 3.1.0, February 2003. Referring now to Figure 2, and more specifically when the present invention is applied to the MMS MM1 interface specification based on 3 GPP2 SIP, the specification is revised as follows: the third method of registering a third party between a Domestic Service Proxy (HSP) in English) 10 and the MMS Relay / Server (AS 3 in the case of MMS) is extended in such a way that the MMS Relay / Server preferably always informs the MMS UA 2 about the success / failure of the registration with the service of MMS. This allows the MMS Relay / Server to send a SIP MESSAGE request to the MMS UA 2 after each registration or re-registration cycle. When the SIP MESSAGE request is sent to the MMS UA 2, the MMS Relay / Server includes a Call Information header field that carries an HTTP URI for purposes of "ci-uri". This URI remains valid until MMS UA 2 is re-registered, uita your registration, or expires the registration of the MMS UA 2. This implies that. the MMS Relay / Server reserves an HTTP URI for each MMS UA record, with the duration equal to the duration of the record, thus allowing the MMS UA 2 to perform the content bypass at any time during its valid registration period. This procedure also eliminates the need for the MMS UA 2 to explicitly request a storage location before sending MM, since the storage location is reserved in the MMS Relay / Server after the MMS UA 2 registers with the service. , and remains available for the MMS UA 2 while it remains registered. The message exchange diagram of Figure 2 illustrates the above behavior. Note that the SIP report informing the MMS UA 2 of the successful SIP record has a Call Information header with the purpose parameter set for "ci-uri". Subsequently the MMS UA 2 performs an HTTP PUT (or some other equivalent type of pressure operation, depending on the technology) to load the information corresponding to the indirect content to the location specified by the URI found in the Call Information part of the SIP 'message received after registration. It should be noted that the URI found in the Call Information header field may not point to an actual or physical storage location reserved by HSP 10 for diverting content. Instead, HSP 10 redirects an MMS UA 2 PUT request that is directed to the URI found in the Call Information header field to an actual storage location. The redirection can be performed by the HSP 10 that responds to the HTTP PUT request with HTTP 3xx responses. One benefit that is obtained through the use of this approach is that the HSP 10 does not need to allocate physical storage locations for the US 2 MMS at the time of the registration of the MMS UA 2. Instead, the HSP 10 only needs to reserve or assign storage locations when there is a real need for storage, at the moment when the MMS UA 2 sends the HTTP PUT request.

These operations are shown in Figure 2 as the block (optional) 12, which is intended to indicate that server 3 can allocate storage, and redirect information loaded to the storage allocated in response to the HTTP PUT of device 2. By examining the flow of messages in Figure 2 in even greater detail, it can be noted that the first REGISTER transaction is between UA 2 and HSP 10. HSP 10 operates as a SIP registrar, showing normal SIP functionality. Based on this transaction, the HSP 10 generates a REGISTER request from a third party to inform the AS-3 (in this case the MMS Server Relay) of the registration status of the UA 2. From the point of view of the SIP, this is another SIP registration functionality, where AS 3 acts as a registrar and HSP 10 registers UA 2 as a third party. It can be noted that in the case of the IMS (Figure 1) the requirement is not to register the UE 2 with the AS 3, the objective is rather only to inform the AS 3 that the UE 2 has been registered with the HSP 10 (the HSP, interposed between UE 2 and AS 3, is not shown in Figure 1). Therefore the AS 3 does not actually function as a SIP registrar in the case of IMS, instead it simply stores the registration status of the UE 2, with the expiration date. In any case, based on the previous record of the third part of the HSP 10 the AS 3 generates a MESSAGE .SIP, which is addressed to the UA 2 and sent through the HSP 10 (the sending through the HSP 10 is made simply because the AS 3 does not have a direct SIP interface for the UA 2). This SIP message originated by AS 3 transmits the Call Information header field to UA 2 with the purpose parameter set for ci-uri to indicate to UA 2 (or UE 2) that the Call Information header contains a URI that specifies the address of the storage location for use in content bypass. Because all UE / ASs when registering are automatically assigned a URI for content diversion purposes, whether used or not, the use of this invention eliminates a need to provide additional signaling exchanges (possibly not standardized) where the UE / UA must specifically request the assignment of a URI. It should be noted that the assigned URI may be one that is assigned in common for all UE / UA, and as indicated above, a "real" URI pointing to the actual location (s) is only reserved when the UE / UA really needs the content diversion. Again reference is made to the document borador-khartabil-sip-política-uri-llamada-info-propósito-00. Note that this document extends the Call Information purpose parameter with a value of "uri-policy", which is used by the caller or whoever is called to transmit a URI where a certain policy related to the session can be accessed, this document does not suggest the use of the purpose parameter for diversion of SIP content in the manner that is described with respect to the embodiments of the present invention. Also, it is noted that a possible application for the diversion of SIP content is described in 3GPP2 X.P0016-312. This specification defines the behavior for a MM sending based on SIP. If the size of the MMS message does not satisfy the message size restrictions described in RFC3428 (SIP MESSAGE method), then the MMS UA uses content bypass to send the MM to an MMS Relay / Server. In order to perform this operation the MMS UA requests a storage location of the MMS Relay / Service. However, the request for a storage location by means of the MMS UA is not equivalent to the use of the Call Information header with a purpose = ci-uri procedure in accordance with the present invention. The details of the SIP protocol of the IP Multimedia Subsystem (IMS) 3GPP and the Multimedia Domain (MMD) 3GPP2 are defined in 3GPP TS 24.229 and 3GPP2 X.S0013.4. 3GPP2 X.P0016-312 is the MMS interface specification MMl based on SIP 3GPP2 (stage 3). The above description has provided by way of example and non-limiting examples a complete and informative description of the best method and apparatus currently contemplated by the inventor to carry out the invention. NeverthelessThose skilled in the art will appreciate various modifications and adaptations in view of the above description, when read together with the accompanying figures and the appended claims. As with some examples, those skilled in the art may attempt to use other similar or equivalent messaging formats and system architectures (eg, architectures other than IMS and MMS). The present invention can also be employed to ensure SIP (SIPS) operations. However, all such similar modifications of the teachings of the present invention will fall within the scope of the present invention. In addition, some of the features of the present invention could be advantageously used without the corresponding use of other features. As such, the foregoing description should be considered as merely illustrative of the principles of the present invention, and not as a limitation thereof. It is noted that in relation to this date, the best method known to the applicant to carry out the aforementioned invention, is that which is clear from the present description of the invention.

Claims (56)

1. CLAIMS Having described the invention as above, the content of the following claims is claimed as property: 1. A method of communications, characterized in that it comprises: receiving a request to register a device; and informing the device of the identity of an address so that the device sends information that is to be referenced by a content bypass operation.
2. 2. A method according to claim 1, characterized in that it additionally comprises assigning a resource for the information.
3. 3. A method according to claim 2, characterized in that the resource comprises storage.
4. 4. A method according to claim 1, characterized in that the registration request comprises a registration request of the Session Initiation Protocol.
5. 5. A method according to claim 1, characterized in that a message of Session Initiation Protocol.
6. 6. A method according to claim 2, characterized in that the assignment occurs in response to the device that sends the information.
7. 7. A method according to claim 1, characterized in that the information occurs through a user terminal interface of an Internet Protocol Multimedia system.
8. 8. A method according to claim 1, characterized in that the information occurs through a Home Service Proxy node in a Multimedia Messaging System.
9. 9. A method according to claim 1, characterized in that a call information header is used with a purpose parameter for a unified identifier of call information resources to indicate that the Call Information header contains a call information header. Uniform Resource Identifier that specifies the identity of the address.
10. 10. A method according to claim 9, characterized in that the uniform resource identifier is reserved for the device for the time during which the device is registered.
11. 11. A Session Initiation Protocol server, characterized in that it comprises a data processor that responds to an occurrence of a SIP registration request made by a device to inform the device by means of a Session Initiation Protocol message. an identity of an address where the device can send information to be referenced by a subsequent Session Initiation Protocol content bypass operation.
12. 12. A Session Initiation Protocol server according to claim 11, characterized in that the Session Initiation Protocol registration request and the Session Initiation Protocol message are passed through a user terminal interface of a user. Internet Protocol Multimedia System.
13. 13. A Session Initiation Protocol server according to claim 11, characterized in that in a Multimedia Messaging Service System the Session Initiation Protocol registration request activates a request for a third party registration that is made by means of a Home Server Proxy, and the Session Initiation Protocol message arrives at the device through the Home Server Proxy node.
14. 14. A Session Initiation Protocol server according to claim 11, characterized in that the Session Initiation Protocol message comprises a Call Information header with a purpose parameter set for a unified identifier of call information resources to indicate that the Call Information header contains a Uniform Resource Identifier that specifies the address.
15. 15. A Session Initiation Protocol server according to claim 14, characterized in that the uniform resource identifier is reserved for the device for the time during which the device is registered.
16. 16. A device operable with a server, characterized in that it comprises a data processor that responds to a reception of a second message from the server, sent in response to the device that originates a first message, to extract from the second message an identification of a location for that the device sends information that is going to be referenced by a content bypass operation.
17. 17. A device according to claim 16, characterized in that the data processor is further operable to send the information to the location.
18. 18. A device according to claim 17, characterized in that the data processor sends the information using a PUT Hypertext Transfer Protocol procedure.
19. 19. A device according to claim 17, characterized in that the server comprises a Session Initiation Protocol Server, and wherein the data processor sends the information using a procedure that is not of the Session Initiation Protocol.
20. 20. A device according to claim 17, characterized in that the server comprises a Session Initiation Protocol Server, and wherein the message is received, and the information is sent, through a user terminal interface of a System Multimedia of Internet Protocol.
21. A device according to claim 16, characterized in that the server comprises a Session Initiation Protocol Server, and wherein a Multimedia Messaging Service System that originates a Session Initiation Protocol registration activates a request for record of a third party that makes a Proxy of Domestic Server, and the message arrives at the device through the Proxy node of Domestic Server.
22. A device according to claim 16, characterized in that the data processor extracts the identification of the location of a Call Information header having a purpose parameter set for a unified identifier of call information resources to indicate that The Call Information header contains a Uniform Resource Identifier that specifies the identity of the location.
23. 23. A device according to claim 22, characterized in that the server comprises a Session Initiation Protocol Server, and wherein the device uses the information extracted for the time during which the device is registered with the Protocol Server of Initiation of Session.
24. 24. A compliance device "with claim 16, characterized in that it comprises a cellular telephone
25. 25. A data storage medium that can be read by a data processor, characterized in that the storage medium stores program instructions for use in • a procedure for diverting content in a Session Initiation Protocol operation and comprising the operations of: in response to receipt of a request for registration of Session Initiation Protocol from a device, reserving a storage location for the device wherein the device can store information to be referenced by means of a Session Initiation Protocol content bypass operation, and inform the device of an identity of the storage location using a Call Information header field of Session Initiation Protocol message with a pr parameter The default set for a unified identifier of call information resources to indicate that the Call Information header field contains a Uniform Resource Identifier that specifies the identity of the storage location.
26. 26. A data storage medium according to claim 25, characterized in that the request is received in a Multimedia Messaging Service Relay / Server, and where the reporting operation occurs through a Domestic Service Proxy.
27. 27. A data storage medium according to claim 25, characterized in that the Uniform Resource Identifier is reserved for the device for the time during which the device is registered.
28. 28. A Multimedia Messaging Service Relay / Server to perform a Session Initiation Protocol operation with a device, characterized in that it comprises: means, which respond to a request for registration of the Session Initiation Protocol of the device, to reserve a storage location for the device where the device can store information to be referenced by a Session Initiation Protocol content bypass operation; and means for informing the device of a storage location identity using a Session Initiation Protocol message Call Information header field with a set purpose parameter for a unified identifier of call information resources to indicate that the Call Information header field contains a Uniform Resource Identifier that specifies the identity of the storage location.
29. 29. A Multimedia Messaging Service relay / Server in accordance with claim 28, characterized in that the information medium is coupled to the device through a Domestic Service Proxy.
30. 30. A Multimedia Messaging Service relay / Server in accordance with claim 28, characterized in that the reservation means reserve a Uniform Resource Identifier of 'Hypertext Transfer Protocol for each device that is registered, with the duration of the reservation equal to the duration of the registration.
31. 31. A data storage medium that can be read by a digital data processor, characterized in that the data storage means stores program instructions for use in a content bypass procedure in a Session Initiation Protocol operation and comprising the operations of: receiving a Session Initiation Protocol message originating from a Session Initiation Protocol server in response to sending a registration request message to the Session Initiation Protocol server; identify a case in which the Session Initiation Protocol message comprises a Call Information header field having a purpose parameter 5. set for a unified identifier of call information resources to indicate that the header field of Call Information contains a Uniform Resource Identifier that specifies the identity of a storage location that has been reserved for the device where the device can store information that will be referenced by a Session Initiation Protocol content bypass operation; and send -information to the storage location.
32. 32. A data storage medium according to claim 31, characterized in that the sending operation comprises using a Hypertext Transfer Protocol method.
33. 33. A data storage medium according to claim 31, characterized in that the operation. to send comprises using a PUT Hypertext Transfer Protocol to load information corresponding to indirect content to the storage location specified by the Uniform Resource Identifier comprising part of the Call Information field of the Session Initiation Protocol message.
34. 34. A data storage medium according to claim 31, characterized in that at least one of the operations comprises the use of a secure session initiation protocol operation.
35. 35. An operable device with a Session Initiation Protocol Server, characterized in that it comprises a data processor that operates in response to a reception of a Session Initiation Protocol message originating from a Session Initiation Protocol server to identify a case in which the Session Initiation Protocol message comprises a Call Information header field having a purpose parameter set for a unified identifier of call information resources to indicate that the Call Information header field contains a Uniform Resource Identifier that specifies the identity of a storage location that has been reserved for the device where the device can store information to be referenced by a Session Initiation Protocol content bypass operation of data operates additionally to send r information to the storage location.
36. 36. A device according to claim 35, characterized in that the information is sent using a Hypertext Transfer Protocol procedure.
37. 37. A device according to claim 35, characterized in that the data processor uses a PUT Hypertext Transfer Protocol to load information corresponding to indirect content to the storage location specified by the Uniform Resource Identifier comprising part of the field of Call Information of the Initiation Protocol message.
38. 38. A device according to claim 35, characterized in that the data processor uses a Secure Session Initiation Protocol procedure.
39. 39. An operable device with a Session Initiation Protocol Server, characterized in that it comprises means, which respond to a reception of a Session Initiation Protocol message originating from a Session Initiation Protocol server to indicate success / failure of a registration request, to identify a case in which the Session Initiation Protocol message comprises a Call Information header field having a purpose parameter set for a unified identifier of call information resources to indicate that the Call Information header field contains a Uniform Resource Identifier that specifies the identity of a storage location that has been reserved for the device where the device can store information to be referenced by a content bypass operation Session Initiation Protocol; and means for loading information corresponding to indirect content with a PUT Hypertext Transfer Protocol to the storage location specified by the Uniform Resource Identifier comprising part of the Call Information field of the Session Initiation Protocol message.
40. 40. A device according to claim 39, characterized in that the means for charging uses a Secure Session Initiation Protocol procedure. .
41. 41. A Session Initiation Protocol server, characterized in that it comprises a data processor that responds to an occurrence of a registration request made by a device to inform the device by means of a Session Initiation Protocol message of an identity from a storage location where the device can send information that is going to be referenced by a content bypass operation Session Initiation Protocol and, in response to the device that sends the information, allocate storage and direct the information to the allocated storage.
42. 42. A Session Initiation Protocol server according to claim 41, characterized in that the Session Initiation Protocol message comprises a Call Information header with an established purpose parameter for a unified identifier of call information resources to indicate that the Call Information header field contains a Uniform Resource Identifier that specifies the identity of a storage location.
43. 43. A method for operating a Session Initiation Protocol Server, characterized in that it comprises: in response to an occurrence of a session initiation protocol registration request made by a device, sending to the device a message of Initiation Protocol of Session comprising an identity of a storage location where the device can send information to be referenced by a Session Initiation Protocol content bypass operation; and in response to the device that sends the information, allocate storage and direct the information to the allocated storage.
44. 44. A method according to claim 43, characterized in that the Session Initiation Protocol message comprises a Call Information header with an established purpose parameter for a unified identifier of call information resources to indicate that the The Call Information header contains a Uniform Resource Identifier that specifies the identity of a storage location.
45. 45. An operable computer program product for a Session Initiation Protocol Server to conduct a session initiation protocol session with a device, characterized in that it comprises the operations of: in response to an occurrence of a request for registration of a session Session Initiation Protocol made by a device, sending to the device a Session Initiation Protocol message comprising an identity of a storage location in which the device can send information to be referenced by a content bypass operation Session Initiation Protocol; and in response to the device that sends the information, allocate storage and direct the information to the allocated storage.
46. 46. A computer program product according to claim 45, characterized in that the Session Initiation Protocol message comprises a Call Information header with a purpose parameter set for a unified identifier of call information resources to indicate that the Call Information header field contains a Uniform Resource Identifier that specifies the identity of a storage location.
47. 47. An operable computer program product for a device to conduct a Session Initiation Protocol operation with a Session Initiation Protocol server, characterized in that it comprises the operations of: receiving a Session Initiation Protocol message from a Session Initiation Protocol server in response to sending a registration request message to the Session Initiation Protocol server; identify a case in which the received Session Initiation Protocol message comprises a Call Information header field having a purpose parameter set for a unified identifier of call information resources to indicate that the Information header field Call contains a Uniform Resource Identifier that specifies the identity of a storage location that has been reserved for the device where the device can store information to be referenced by a Session Initiation Protocol content bypass operation; and send information to the storage location.
48. 48. A computer program product according to claim 47, characterized in that the sending operation comprises using a Hypertext Transfer Protocol method.
49. 49. A computer program product according to claim 47, characterized in that the sending operation comprises using a PUT Hypertext Transfer Protocol method to load information corresponding to indirect content to the storage location specified by the Unified Resources comprising part of the Call Information field of the Session Initiation Protocol message.
50. 50. A computer program product according to claim 47, characterized in that at least one of the operations comprises using a Secure Session Initiation Protocol operation.
51. 51. A method for operating a Session Initiation Protocol Server to perform a Session Initiation Protocol session with a device, characterized in that it comprises: a step to execute in response to an occurrence of a Protocol registration request. of Initiation of Session made by the device, to send to the device a Session Initiation Protocol message comprising a storage media identity where the device can send information to be referenced by a Protocol content bypass operation of Initiation of Session; and a stage, executed in response to the device that sends the information, to allocate a storage and to direct the information to the allocated storage.
52. 52. A method according to claim 51, characterized in that the message of Initiation Protocol of Session comprises a Call Information header with a purpose parameter set for a unified identifier of call information resources to indicate that the Call Information header contains a Uniform Resource Identifier that specifies the identity of the storage medium.
53. 53. A method for operating a device for carrying out a Session Initiation Protocol operation with a Session Initiation Protocol server, characterized in that it comprises: in response to receipt of a Session Initiation Protocol message originating from a Session Initiation Protocol server in response to sending a registration request message to the Session Initiation Protocol server, a step to identify a case in which the received Session Initiation Protocol message comprises a header Call Information with a set purpose parameter for a unified identifier of call information resources to indicate that the Call Information header field contains a Uniform Resource Identifier that specifies the identity of the storage medium that has been reserved for the device where the device can store informs which will be referenced by means of a content diversion operation of Session Initiation Protocol; and a step to send information to the storage location.
54. 54. A method according to claim 53, characterized in that the step of sending comprises using a Hypertext Transfer Protocol method.
55. 55. A method according to claim 53, characterized in that the step to send comprises a PUT Hypertext Transfer Protocol to load information corresponding to indirect content to the storage location specified by the Uniform Resource Identifier comprising part of the field of Call information of the Session Initiation Protocol message.
56. 56. A method according to claim 53, characterized in that at least one of the steps comprises the use of a Secure Session Initiation Protocol operation.