Abstract: In an implementation of the invention, services installed on a computing device register their published name, which conforms to a structured naming convention, such as reversed domain information, with a ‘service broker’ on that device. The service broker uses a single well-known port number address. When an external client, connected to the computing device that has a service broker, wants to use a service on that computing device, it sends a message to the service broker using the well known port number. The message specifies the name of the desired server and requests that the service broker inform it of the appropriate connection point (e.g. port number) to use. There is no dependency on port numbers or unstructured and arbitrary naming conventions.

Abstract: A service creation system for a communications network of the intelligent network type has 3 different levels at which service creation activities can be carried out, these being SCE1, SCE2 and SCE3. The use of separate levels allows access to the service creation system to be kept functionally separate for users having different interests in the network. Hence, features which have to be installed at the network element level for a selected service to be available can be created in SCE1. Marketable service features, which give a view of features in that they encapsulate call handling logic thereof together with support and management descriptions of the feature, can be created in SCE2. Service packages, which permit collection of marketable service features to meet requirements of a service together with servicespecific support and management information, can be created in either of SCE2 or SCE3.

Abstract: A service creation system for a communications network of the intelligent network type has three different levels at which service creation activities can be carried out, these being SCE1, SCE2 and SCE3. The use of separate levels allows access to the service creation system to be kept functionally separate for users having different interests in the network. Hence, features which have to be installed at the network element level for a selected service to be available can be created in SCE1. Marketable service features, which give a view of features in that they encapsulate call handling logic thereof together with support and management descriptions of the feature, can be created in SCE2. Service packages, which permit collection of marketable service features to meet requirements of a service together with service-specific support and management information, can be created in either of Sce2 or SCE3.