|
1. Application Description 1) Service Description Indoor scenarios differ from outdoor ones in user characteristics, behavior patterns, and service expectations. In enterprise scenarios, users have similar behavior patterns and service requirements, and Bring Your Own Device (BYOD) is seeing tremendous popularity. The growing mobile Internet enables enterprises to provide ubiquitous access to mobile working and various differentiated services, including indoor navigation and service pushing. This means amazing opportunities for them to grow their customer bases and business profits, especially in mass market consumer sites. It allows them to make business decisions based on big data analysis for future financial gain. In line with these trends, Huawei launches its innovative Service AnchorTM solution. This solution works together with the small cell products to provide radio network controller functions for lower-powered small cells widely deployed to improve coverage and capacity performance. In this way, Service Anchor helps operators enrich the functions of their telecommunication networks and explore the indoor Blue Ocean market. Service AnchorTM helps operators typically in the following scenarios: l Mass-market consumer sites Typical examples are shopping malls, supermarkets, and transport hubs like airports, railway/bus stations, sports venues, theaters, and museums.
Users are mainly mass market consumers and a minute quantity of workers.
Service requirements include: advertisement push and indoor navigation to improve services and raise business profitability; and statistical collection and analysis of consumer behaviors to ground business decisions. l Medium and large enterprises Users consist of a dominant number of employees and a minute quantity of visitors.
Services provided by Service Anchor require the following to improve mobile efficiency in these areas: - Access to radio communication networks and enterprise networks - Access to public cloud services for self-attendance - Access to public cloud services for self-entrance - Access to public cloud services for IP PBX - Access to public cloud services for security surveillance - Other mobile working activities over cellular phones Service Anchor is a capability-open indoor radio network controller. It functions as a bridge between small cells and telecom public clouds (conventional core network equipment) and third-party app servers. Figure 1-1 Position of Service Anchor in a small cell network

Service Anchor provides the following functions: l Network capability openness: It provides an API interface to third-party app servers under the operator management to fulfill the requirements of enterprises, mass-market consumer sites, and OTT developers. l Radio network control: It is integrated with function components of access controllers (ACs) and access gateways (AGs) to increase efficiency of small cell networks. Service Anchor consists of Service Anchor hardware, Service Anchor basic software, and Service Anchor function components. Figure 1-2 Logical architecture of Service Anchor
 l Service Anchor hardware Developed on Huawei's general hardware platform, Service Anchor hardware has two hardware products: SVA3100 hardware and SVA3200 hardware, which are applicable to different application scenarios. l Service Anchor basic software − Implements device management, as well as manages loading, enabling and lifecycle of the Service Anchor function components. − Helps decouple function components from the hardware and ensure flexible deployment. l Service Anchor function component Each Service Anchor function component is optional to the Service Anchor solution and has separate functions, features, and license files, allowing customers to select optional features based on their own needs. These function components can be separately deployed and maintained, facilitating network deployment and evolution. In this release, the Service Anchor has three function components: SVA-AE, SVA-AC, and SVA-AG. Other function components will be available in future releases.
2) Documentation Description A performance counter defines the measurement items of a measurement object and can be used for network performance assessment, network optimization, and fault detection. The following concepts help you better understand a performance counter: · Counter: (also counter timer), data that must be collected for a measurement, such as number of requests and service traffic · Function subset: (also called measurement unit), a set of measurement counters with the same attribute, for example: the function subset of Ethernet port measurement refers to statistics of different types of traffic over an Ethernet port. · Function set: a set of multiple function subsets with the same attributes, for example, the function set Measurements Related to Network Layer consists of three function subsets: IP Measurement <Network.IP>, IPv6 Measurement <Network.IPv6> and Tunnel Measurement <Network.Tunnel>. · Object type: (also called measurement object) a physical entity or logical entity. · The following figure shows the relationship between the object type, function set, function subset, and counter.  For details about how to measure performance counters for SVA, see the performance counter reference. The performance counter references of all versions are described by object. The following figure shows the document structure.  2. Highlights The counter relationship is provided. The counter relationship is added to the description of the function subset. Therefore, you can conveniently query and understand counter relationships covering counters of a maximum of nine levels. 
3. Reference Documents
This post was last edited by BenLiu at 2019-09-27 15:11. |