Service stratum: components and cooperation

Inside the service platform

The train is reachable on the network, yet Niko cannot call Lea. A transport path answers neither whether Lea is authorised for the service nor what her current call state is. The service stratum groups the functions providing these communication services. A service domain is an organisationally operated instance or part of this service layer. The logical architecture does not determine how many servers or suppliers are involved. [S06, clause 6.3.5]

Open diagram at full size (SVG, new tab) G10

Four cooperating functional groups

The SIP Core supports registration and session control using SIP. MCX service functions process service-specific procedures: for voice, for example, participation and floor control; for data, management of data communication. Common management functions provide the required identities, configurations and security information. Clients use these functions on the user side. [S09, clauses 5 and 6]

The table is an original diagnostic application of the architecture. It does not promise that every failure always causes exactly that symptom. Several functions may fail together or run on the same platform.

Distinguish control, media and management

Signalling controls communication. Media or user data is the content being transferred. Management maintains longer-lived information such as profiles and permissions. These three views explain why a successful SIP response alone is not a complete service test. A management error may also prevent the next call while an existing session continues; implementation-specific behaviour needs testing.

Lea therefore first signs in with her service identity. The client obtains or uses its approved profile. Service authorisation limits permitted use. During a call request, session control cooperates with the responsible MCPTT function. A later speaker change involves Floor Control, the function managing permission to speak. The media path then delivers voice data to the participants.

Boundaries of the component map

A dispatcher terminal is a workstation, not a synonym for the entire service platform. A Trackside Gateway integrates trackside applications. An Interworking Function translates defined functions to another communication system. A product called a Rail Application Server must also be classified by its actual functions. Dedicated lessons cover these elements while retaining the common map.

Check your understanding

After a profile change, Lea cannot use the service although IP packets arrive. Which two service areas do you investigate first, and why is another radio path insufficient?

Model answer

Check configuration as well as identity verification and service authorisation: does the new profile match the intended identity and permit the required services? Another radio path does not repair a shared incorrect configuration. Test this hypothesis against client and server events; the symptom alone does not establish the cause.

What to remember

The service stratum consists of cooperating functions with their own states. Relationships and procedures turn a component list into an architecture.

Your Talbahn case file

For each functional group, add an operator, a dependency and an observation point. Explicitly identify physical consolidation as an implementation choice.