M3UA ASP Registration

M3UA Single ASP Registration (Dynamic and Configured)

An ASP can register with the SG either dynamically by assigning a routing key to an Routing Context (RC) or by using preconfigured data. The difference between these two procedures is the method used to assign a routing key to an RC.

Dynamic Registration

If the ASP registers with the SG dynamically, then the attributes in the routing key are included in the registration message from the ASP. The following table lists these attributes.

The SG extracts the attributes from the request message sent by the ASP and locally creates an AS, assigns an RC if not provided, and returns this RC to the ASP in the registration response message.

Configured Registration

You can preconfigure the RC and routing key associated with an AS. The ASP that registers uses this configured AS. The following table lists the configured AS attributes.

For more information about creating a configured AS, refer to Configuring an M3UA Application Server.

The following figure shows the dynamic single ASP registration procedure. The configured single ASP registration procedure is identical except that the AS is already registered to the ASP.

Dynamic M3UA Single ASP Registration and Activation

M3UA Multiple ASP Registrations

As shown in the following figure, multiple ASPs can establish one or more connections to the SG. The second ASP registers a different RC with the SG. The SG then registers the routing key mapped to RC(2) with MTP3.

In case of multiple ASP registration, you also have to perform the ASP registration procedure first, and then perform the ASP activation procedure.

All Application Servers are distributed across available Routing VMs.

M3UA Multiple ASP Registration