This will ensure that the method is received by any proxies along the way.
The actual content of this method could be identified in a message header, in which
case the parameters within the message header would be processed by the various
proxies in the path accordingly. As an alternative, the content could also be carried in
the message body, as would be the case for a picture file.
If the content is in the message body, then the endpoint must know how to handle the
message body. This obviously would be identified in the CONTENT-TYPE header. One
of the options could simply be to render the content to the display of the subscriber??™s
device (again as would be the case for a picture file).
Invite The next most used method is the INVITE. This is used to establish a session
within the IMS. Think of the INVITE as an invitation to another user to join in a conversation
(or an e-mail, or an instant message, or whatever type of session is being set up).
The INVITE, of course, must then carry details about the session being established,
as outlined in Chapter 5. The INVITE can also be sent to application servers providing
services such as Blackberry service (for e-mail) or Web browsing. Anytime a device
needs to establish a connection (virtual, of course), the INVITE is the method used to
establish that connection.
Message The MESSAGE method was added by the 3GPP to support text messaging
in the IMS.
Pages:
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150