The service profiles will have
various public user identities associated with each one, as illustrated in Figure 7.5.
The service profile may also contain the media profile, identifying the SDP parameters
that the subscriber is allowed to request from the network. These SDP parameters
identify the media resources required to support a session, and will determine
what media services the subscriber is allowed to access in the network. There may also
be data in the service profile that identifies requests that require support from an application
server(s).
The HSS then serves as the central reference point for all charging, since it is the
user profile that determines what will be charged. The user profile is then associated
with public and private user identities (there can be multiple public user identities
associated with one user profile). The private user identity and its associated public
user identities are a permanent record within the HSS; however, the location/routing
information associated with these identities is not known until the subscriber registers
in the network.
When a subscriber registers in the network and is assigned to a Serving Call Session
Control Function (S-CSCF), the S-CSCF will query the HSS to acquire the user profile.
The user profile will in turn identify the services allowed, the media allowed, and the
public user identities associated with that subscriber.
Pages:
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355