This example demonstrates how a CSP can use Nesting of records (see Clause 5.5). The example shows the result of a LD request with as the target identifier a postalcode and a house number. Since multiple people could be a residence at this address and have one or more services at the CSP, the resulted Record Set would contain multiple SubscriberInformationRecords of the different subscribers, and multiple ServiceInformationRecords for the services of these subscribers. To ensure that that recipient of the Record Set can determine which service belongs to which subscriber, the CSP uses Nesting (see Clause 5.5).
This example demonstrates how a CSP can use Nesting of records (see Clause 5.5). The example shows the result of a
LD request with as the target identifier a postalcode and a house number. Since multiple people could be a residence
at this address and have one or more services at the CSP, the resulted Record Set would contain multiple
SubscriberInformationRecords of the different subscribers, and multiple ServiceInformationRecords for the services of
these subscribers. To ensure that that recipient of the Record Set can determine which service belongs to which subscriber,
the CSP uses Nesting (see Clause 5.5).
In this particular example John Doe and Jane Doe live at the same address. John has a telephony subscription with phone number +44 1632960124. Jane has a telephony subscription with phone number +44 1632960567, and a data access subscription.
In this particular example John Doe and Jane Doe live at the same address. John has a telephony subscription with phone
number +44 1632960124. Jane has a telephony subscription with phone number +44 1632960567, and a data access subscription.
In the CSP supplementary type schema two Nesting records are defined:
- CSPSubscriberRecordsCollectionRecord - for collecting records belonging to a subscriber
