The trend of NGN (Next Generation Network) has pushed the cyber world towards a revolution.The deployment of such NGN raises the issue of development of the so-called Next Generation Service (NGS).Among the main characteristics of, and challenging issues raised by the NGS, we can mention heterogeneity, mobility and user centric paradigms.Our work which is in the context of NGN/NGS and is conducted partially within the French ANR/VERSO/UBIS project.
With the rise of the applications based on the Internet, as well as the B2B/B2C and the development of Cloud Services, service integration and performance requirements continue to increase. It is difficult to meet the needs through a single specific service. So the dynamic service composition attracts the attention of academics and business in the last few years. However, there are several problems to solve in the process of composing dynamic services. First of all, we cannot easily integrate the WSs from the different suppliers because of the heterogeneity of the environment and the autonomy of WS. Secondly, due to the dynamic nature of the operation and process treatment, coding in a fixed form is no longer applicable. Thirdly, because of the user mobility and their diverse needs, we need a mechanism to dynamically discover, select and combine the WSs in the inter-organization and cross-platform.
With the development of the Cloud Computing and the occurrence of the increasingly diverse WSs, as well as the democratization of mobile terminal (Smartphones, Tablet), more and more users would like to perform a sequence of operation automatically according to their logic which refers to use a series of individual existing WS.
Therefore, it is appropriate for us to conceive architecture to provide the service composition such a benefit with the development of SOA. One of the key issues is the semantic web: it allows not only solving the problem of mismatching between the web services; it also allows automatically identifying the functional equivalent service entities. Of which the latter is very useful to answer another key question that is the adaptation to the context (or ubiquity), which is to be able to replace a service entity by another functionally equivalent one...
