ognitive cycle-information collecting from context, knowledge formulating, and representation, machine Service Delivery Platforms learning and decision making, adjusting, and acting on a particular context for improvement. However, one system, such as SDP, is always a hybrid one involving with several infrastructures, including hardware, networks, protocols, and SO forth. How to divide and manage system reasonably is supposed to be the most crucial problem when implementing. 6.3.3.1 Cognitive Domains In order to collect and manage the whole system, all nodes' information should be collected and formulated as knowledge according to predefined rules. When it comes to large telecom networks, the amount of data is larger than it is imagined, not to mention real-time collecting and processing. To reverse the situation, cognitive domains can be introduced to figure out the problem. According to network, physical and logical levels, the whole system, espe- cially network environment, can be divided into several domain levels. Multilevel domains can be divided in accordance with the actual scale and overloads of tele- com networks, while topper domain can be divided into minor domains as well. All these domains are cognitive domains taking charge of information collecting, nodes and domains communication, and information transferring and computing. Within the same lever, domains are similar to peer domains and are managed by topper domains. The highest level should contain a central domain server to deploy, dispatch, and manage communications and interactions among top cognitive domains. 6.3.3.2 Cognitive Domain Design Pattern According to the principle of cognitive domain, the domain design pattern can be depicted by Figure 6.5. The whole system can be divided to several subcognitive domains, while individual cognitive domain is in charge of basic cognitive processes, mainly and especially involving with information collecting and transferring. Individual cognitive domains deploy, dispatch, and manage their own nodes. A