TSAS — Section 4.2 Access

· The get_segment method in TSAS loosely maps to the obtainInterface(WithCallback) methods in Parlay. However the former method permits the invoker to provide & obtain multiple interface references while the latter methods permit the invoker to provide & obtain at most one interface reference.
· The TSAS list_segments & release_segment methods have no equivalent in Parlay.
· [Figure 4.4, the first method invocation in the sequence diagram should be list_available_services, per the description that follows.]
· In TSAS, a service property does not contain a mode parameter.
· 4.2.1 Access interface, list_available_services: This method has no direct equivalent in Parlay. It has some similarities with the Parlay methods: IpDiscovery.listSubscribedServices (without the desired_properties filter) and IpDiscovery.discoverService (without the Service Type and "maximum # of matches" constraints).
· 4.2.1 Access interface, start_session, end_session: These TSAS methods have no equivalent in Parlay.
· 4.2.1 Access interface: TSAS does not support the Parlay accessCheck, terminateServiceAgreement and terminateAccess methods.
· 4.2.1 Access interface, sign_service_agreement: One of the return parameters (session_info) is a superset of the information returned by the corresponding parameter of the Parlay method; i.e. the latter returns at most one interface reference, no SessionID and no SessionProperty information.

Actions: no alignment with Parlay