| | | | SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
|
|
subscriber
public class Identity
Identity defines a context for the Subscriber by associating an Address (e.g. SDN, or in future different types of Address) with a desired Service behaviour. Identities are provisionable and clonable.
Links:
Kernel Association Association Link
defaultDomain defines the Domain which should be applied (rather that using a DerivedAssociation) in order to manipulate Addresses and govern connection establishment for three cases:
i) HLR enabled devices for which the actual TLDN is not known until the HLR query is return. In such cases the direct assignment cannot be used since the sdnAddress (TLDN) is not known at provisioning time. As such, the defaultDomain may be specified to supercede any DerivedAssociations and may be applied to Subscriber terminated calls at the TLDN
ii) MIM enabled devices for which the actual mobile sdnAddress is registered (via MIM registration). In such cases the direct assignment cannot be used since the sdnAddress (MIM sdnAddress) is not known at provisioning time. As such, the defaultDomain may be specified to supercede any DerivedAssociations and may be applied to Subscriber terminated calls to the MIM registered Address
iii) the defaultDomain may be used to supercede DerivedAssociation (dynamic domain assignment) for calls originated from a Subscriber to a non-subscriber. Since the non-subscriber Addresses are not known at provisioning time DirectAssociations cannot be specified. Rather than applying dynamic Domain assignement via a DerivedAssociation the defaultDomain can be specified thus superceding other assignments such that it is applied to the non-subscriber/terminating leg of the call
Constraints:
- must be one of the existing Domain instances
- see Domain constraints
- may be null
Default:
- none
Clone:
- yes, shallow. The cloned Identity references the same instance of Domain as the original Identity
Associates type:
association
Client cardinality:
0..*
Client navigability:
NOT NAVIGABLE
Client visibility:
private
Supplier cardinality:
0..1
Supplier navigability:
NAVIGABLE
Supplier visibility:
private
Kernel Association determines
An Identity associates a primary (sdnAddress) and an optional secondary
Address (e.g. SDN) with a set of Service behaviours and preferences.
Currently, an Identity associates only primary and secondary SDNs with
its preferences, in future an Identity may associate multiple types of
Address with Service context. For example, Identity may be extended to
include a Subscriber email, or IM account identifier.For Release 3.5 the
Identity.sdnAddress is a RoutableNumber.
Constraints:
- the RoutableNumber must be unique across all Identity.sdnAddress and
Identity.secondarySdnAddress values
- must be unique across all service invocation numbers (personal and
global)
- may be the same as Endpoint.address (MDN==SDN case)
- see RoutableNumber constraints
Default:
Clone:
- no, the sdnAddress must be unique and must be assigned to the
clone by the provisioner
Associates type:
association
Client cardinality:
0..1
Client navigability:
NOT NAVIGABLE
Client visibility:
private
Directed.
Supplier cardinality:
1
Supplier navigability:
NAVIGABLE
Supplier visibility:
private
Kernel Association Association Link
sdnDomain represents the Domain instance to use when transforming the
Identity.sdnAddress. This attribute may be null when derived domain
association is used to locate the proper domain instance.
Constraints:
- must be a valid domain
- may be null (Derviced domain association used instead)
Default:
- none
Clone:
- no, must be reassigned based on the updated sdnAddress
Associates type:
association
Client cardinality:
1
Client navigability:
NOT NAVIGABLE
Client visibility:
private
Supplier cardinality:
1
Supplier navigability:
NAVIGABLE
Supplier visibility:
private
Kernel Association determines
An Identity associates a primary and optional secondary Addresses (e.g. SDN) with a set of Service behaviours and preferences. Currently, an Identity may associate only a single Address (SDN) with its preferences, in future an Identity may associate multiple types of Address with Service context. For example, Identity may be extended to include a Subscriber email, or IM account identifier.
For Release 3.5 the Identity.secondarySdnAddress is a RoutableNumber.
Constraints:
- the RoutableNumber must be unique across all Identity.sdnAddress and Identity.secondarySdnAddress values
- must be unique across all service invocation numbers (personal and global)
- may be the same as Endpoint.address (MDN==SDN case)
- see RoutableNumber constraints
- may be null
Default:
- none
Clone:
- no, the sdnAddress must be unique and must be assigned to the clone by the provisioner
Associates type:
association
Client cardinality:
0..1
Client navigability:
NOT NAVIGABLE
Client visibility:
private
Directed.
Supplier cardinality:
1
Supplier navigability:
NAVIGABLE
Supplier visibility:
private
Kernel Association Association Link
the address to use for transforming the secondary SDN Address. May be null
if the secondary address is null OR when derived domain association is
used to locate a proper domain instance.
Constraints:
- may be null
- if not null, must be a valid Domain
Default:
- none
Clone:
- no, must be reassigned
Associates type:
association
Client cardinality:
1
Client navigability:
NOT NAVIGABLE
Client visibility:
private
Supplier cardinality:
1
Supplier navigability:
NAVIGABLE
Supplier visibility:
private
| Field Summary |
|
|
private String |
|
|
|
|
|
|
|
|
|
private String |
|
defaultDomain defines the Domain which should be applied (rather that using a DerivedAssociation) in order to manipulate Addresses and govern connection establishment for three cases:
i) HLR enabled devices for which the actual TLDN is not known until the HLR query is return. In such cases the direct assignment cannot be used since the sdnAddress (TLDN) is not known at provisioning time. As such, the defaultDomain may be specified to supercede any DerivedAssociations and may be applied to Subscriber terminated calls at the TLDN
ii) MIM enabled devices for which the actual mobile sdnAddress is registered (via MIM registration). In such cases the direct assignment cannot be used since the sdnAddress (MIM sdnAddress) is not known at provisioning time. As such, the defaultDomain may be specified to supercede any DerivedAssociations and may be applied to Subscriber terminated calls to the MIM registered Address
iii) the defaultDomain may be used to supercede DerivedAssociation (dynamic domain assignment) for calls originated from a Subscriber to a non-subscriber. Since the non-subscriber Addresses are not known at provisioning time DirectAssociations cannot be specified. Rather than applying dynamic Domain assignement via a DerivedAssociation the defaultDomain can be specified thus superceding other assignments such that it is applied to the non-subscriber/terminating leg of the call
Constraints:
- must be one of the existing Domain instances
- see Domain constraints
- may be null
Default:
- none
Clone:
- yes, shallow. The cloned Identity references the same instance of Domain as the original Identity
Multiplicity:
1
private String name
// * vmAssociatedDevice identitfies the voicemail associated Device that is assigned to the Identity. This Device is used by the services in order to determine which voicemail associated Device to use direct calls to the Identitie's voice mailbox.
// * Constraints:
// * - may be null
// * - if not null must be a valid Device reference
// * - the specified Device must have an endpoint that is voicemailEnabled
// * - the Device.originatingIdentity == Identity
// * Default:
// * - none
// * Close:
// * - yes, must re-assign to the newly created Device
// * @clientCardinality 1
// * @supplierCardinality 0..1
//
Multiplicity:
1
An Identity associates a primary (sdnAddress) and an optional secondary
Address (e.g. SDN) with a set of Service behaviours and preferences.
Currently, an Identity associates only primary and secondary SDNs with
its preferences, in future an Identity may associate multiple types of
Address with Service context. For example, Identity may be extended to
include a Subscriber email, or IM account identifier.For Release 3.5 the
Identity.sdnAddress is a RoutableNumber.
Constraints:
- the RoutableNumber must be unique across all Identity.sdnAddress and
Identity.secondarySdnAddress values
- must be unique across all service invocation numbers (personal and
global)
- may be the same as Endpoint.address (MDN==SDN case)
- see RoutableNumber constraints
Default:
Clone:
- no, the sdnAddress must be unique and must be assigned to the
clone by the provisioner
Multiplicity:
1
sdnDomain represents the Domain instance to use when transforming the
Identity.sdnAddress. This attribute may be null when derived domain
association is used to locate the proper domain instance.
Constraints:
- must be a valid domain
- may be null (Derviced domain association used instead)
Default:
- none
Clone:
- no, must be reassigned based on the updated sdnAddress
Multiplicity:
1
private Address secondarySdnAddress
An Identity associates a primary and optional secondary Addresses (e.g. SDN) with a set of Service behaviours and preferences. Currently, an Identity may associate only a single Address (SDN) with its preferences, in future an Identity may associate multiple types of Address with Service context. For example, Identity may be extended to include a Subscriber email, or IM account identifier.
For Release 3.5 the Identity.secondarySdnAddress is a RoutableNumber.
Constraints:
- the RoutableNumber must be unique across all Identity.sdnAddress and Identity.secondarySdnAddress values
- must be unique across all service invocation numbers (personal and global)
- may be the same as Endpoint.address (MDN==SDN case)
- see RoutableNumber constraints
- may be null
Default:
- none
Clone:
- no, the sdnAddress must be unique and must be assigned to the clone by the provisioner
Multiplicity:
1
private Domain secondarySdnDomain
the address to use for transforming the secondary SDN Address. May be null
if the secondary address is null OR when derived domain association is
used to locate a proper domain instance.
Constraints:
- may be null
- if not null, must be a valid Domain
Default:
- none
Clone:
- no, must be reassigned
Multiplicity:
1
private String timezone
timezone is the name of the timezone associated with the Identity. The timezone may be applied in the application of service capabilities (e.g. McsRingingProfiles).
Constraints:
- must match one of the values specified in the supported timezones list associated with the release (TBD R3.5)
Default:
- the value described in the init_param DEFAULT_TIMEZONE attribute
Clone:
- yes, verbatim
Multiplicity:
1
| | | | SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
|
|