WO2015196733A1 - 网络服务提供、策略规则评估、服务组件选择方法及装置 - Google Patents

网络服务提供、策略规则评估、服务组件选择方法及装置 Download PDF

Info

Publication number
WO2015196733A1
WO2015196733A1 PCT/CN2014/092721 CN2014092721W WO2015196733A1 WO 2015196733 A1 WO2015196733 A1 WO 2015196733A1 CN 2014092721 W CN2014092721 W CN 2014092721W WO 2015196733 A1 WO2015196733 A1 WO 2015196733A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
component
service
user
instance
Prior art date
Application number
PCT/CN2014/092721
Other languages
English (en)
French (fr)
Inventor
宗在峰
吴瑟
方敏
陶峑郡
朱进国
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP14895911.7A priority Critical patent/EP3163843A4/en
Priority to US15/322,172 priority patent/US20170222889A1/en
Publication of WO2015196733A1 publication Critical patent/WO2015196733A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements

Definitions

  • the present invention relates to the field of communications, and in particular, to a network service provision, a policy rule evaluation, a service component selection method and apparatus.
  • the fifth-generation mobile communication technology (5G) mobile broadband system will become a wireless mobile communication system for the human information society after 2020. It is a multi-service and multi-technology convergence network. Through the evolution and innovation of technology, it will meet the future wide range. The ever-evolving needs of data and connected services enhance the user experience. With the increase of the bandwidth and capabilities of wireless mobile communication systems, the mobile Internet and Internet of Things applications for individuals and industries are developing rapidly, and the ecology of mobile communication related industries will undergo important changes. Wireless mobile communication technology and computer and information technology will be more closely and deeper cross-integration, integrated circuits, device technology, software technology, etc. will continue to develop rapidly, supporting the future development of 5G mobile broadband industry.
  • the 5G network requirements defined by METIS can include but are not limited to the following scenarios:
  • D2D Device to Device Communication
  • MMC Massive Machine Communication
  • Ultra Dense Network (UDN)
  • Ultra-reliable communication ULC
  • FIG. 1 is a schematic diagram of a network architecture of a fourth generation mobile communication technology (4G) evolved packet core network (EPC) according to the related art.
  • the network architecture can include the following components:
  • E-UTRAN Terrestrial Radio Access Network
  • the Mobility Management Entity is responsible for control plane mobility management, which may include, but is not limited to, user context and mobility state management, and allocation of user temporary identity identifiers;
  • a service gateway entity (Server-Single Gateway, S-GW for short), which is a user plane entity and is responsible for user plane data routing processing;
  • PPP packet data network gateway
  • P-GW packet data network gateway
  • the P-GW and the S-GW may be combined in one physical entity.
  • SGSN Serving GPRS Supporting Node
  • PCRF Policy and Charging Rule Function
  • a Home Subsriber Server (HSS) is set to store user subscription information.
  • the future 5G network is a multi-application scenario with multiple access networks that cooperate with each other.
  • Different application scenarios have different requirements for the network. Some application scenarios require high-bandwidth access, while some application scenarios require low-latency processing, and some application scenarios require higher security.
  • the service period of each application scenario is different for the network. Some application scenarios need to be able to use networks for decades or even hundreds of years, and some application scenarios may only need to be able to maintain a network for several hours. Therefore, if you want to satisfy all of the above application scenarios through only one static network, it is very difficult, and even if it can be completed, it will inevitably cost a lot. Therefore, a dynamic network with open capabilities and on-demand automated scheduling is bound to be the development trend of 5G networks in the future.
  • NFV Network Function Virtualization
  • SDN Software Defined Network
  • cloud computing has made roots It is possible to dynamically generate and schedule network elements according to requirements.
  • NFV enables telecom operators and equipment manufacturers to easily use carrier-grade equipment to implement carrier-class equipment, so that software and hardware are separated from each other, thereby accelerating new service development and reducing operators' operation and maintenance costs.
  • NFV is a platform technology that serves a variety of carrier-grade services.
  • the basic function of the NFV system is to instantiate the network prototype proposed by the OSS/BSS according to the requirements of the Operation Support System (OSS)/Service Support System (BSS), which may include: creating a virtual network element instance according to the requirements of the OSS/BSS, and establishing a virtual The connection between the network element instances and the connection between the virtual network element and other network elements, and the automatic expansion and management of the capacity of the virtual network element according to the system load, thereby saving power on the basis of satisfying the demand.
  • OSS Operation Support System
  • BSS Service Support System
  • the NFV system cannot make a decision to create or modify a network, which needs to be done by the operator's management.
  • the OSS/BSS in the current network does not have the function of automatically deploying the network.
  • the embodiment of the invention provides a network service provision, a policy rule evaluation, a service component selection method and a device, so as to at least solve the problem that the operator in the related art is difficult to customize and automatically schedule the network according to user requirements.
  • a communication network architecture is provided.
  • a communication network architecture includes: a management layer configured to acquire a user network service requirement, and create, schedule, and schedule functional components on an execution layer based on network service requirements; and an execution layer configured to provide a network for the user The service, and/or the information to be used by the management layer in the process of creating, scheduling, and scheduling the functional components is reported to the management layer, wherein the execution layer is composed of a plurality of functional components, and the functional components include at least the following One: network components, business components.
  • the management layer comprises: a network component information management module configured to provide status information of the currently running network component instance; a business component information management module configured to provide status information of the currently running business component instance; user information management a module, configured to provide user status information; a user network service orchestration and management module configured to obtain policy rule information, and to create, schedule, and schedule functional components according to policy rule information, user network service requirements, and network feature information sets, wherein
  • the network feature information set includes at least one of the following: status information of the network component instance, status information of the service component instance, and user status information.
  • the management layer further includes: a policy rule base, configured to provide policy rule information; and a policy effect evaluation module configured to evaluate the execution result of the policy rule information to determine whether the policy rule information needs to be modified.
  • a policy rule base configured to provide policy rule information
  • a policy effect evaluation module configured to evaluate the execution result of the policy rule information to determine whether the policy rule information needs to be modified.
  • the management layer further comprises: a network component library, configured to provide a network component to be generated, wherein the information provided in the network component library comprises at least one of the following: a functional description of the network component, and the network component provides a party letter Information, available license number, network component image (image); business component library, set to provide the business component to be generated, wherein the information provided in the business component library includes at least one of the following: a functional description of the business component, Business component provider information, available license quantity, business component image; user subscription library, set to manage user subscription information.
  • a network component library configured to provide a network component to be generated, wherein the information provided in the network component library comprises at least one of the following: a functional description of the network component, and the network component provides a party letter Information, available license number, network component image (image)
  • business component library set to provide the business component to be generated, wherein the information provided in the business component library includes at least one of the following: a functional description of the business component, Business component provider information, available license quantity, business
  • the execution layer comprises: a network component configured to provide an access service; and a service component configured to provide a value added service for the service data.
  • a method of providing a network service based on the above communication network architecture is provided.
  • the method for providing a network service includes: acquiring a user network service requirement, policy rule information, and a network feature information set of a currently running network, where the network feature information set includes at least one of the following: status information of the network component instance. The status information of the service component instance and the status information of the user; determining the network orchestration scheme according to the user network service requirement, the policy rule information, and the network feature information set; and providing the network service to the user by using the network orchestration scheme.
  • acquiring the network feature information set includes at least one of: acquiring state information of the network component instance from the network component information management module; obtaining state information of the service component instance from the service component information management module; and acquiring the user's information from the user information management module Status information; obtain policy rule information from the policy rule base.
  • the status information of the network component instance includes at least one of: location, load, capacity, reliability, network topology of the network component instance; and status information of the service component instance includes at least one of the following: load, capacity, capability, network The topology, the location of the service component instance; the user's state information includes at least one of the following: mobility, location, QoS, service preferences, and terminal capabilities.
  • providing the network service to the user by using a network orchestration scheme comprises one of: creating a new network component instance and/or a service component instance according to the network orchestration scheme; and the existing network component instance and/or service component according to the network orchestration scheme The instance is updated; the connection relationship between the current network component instance, and/or the business component instance, and/or the network component instance and the business component instance is configured according to the network orchestration scheme.
  • creating a new network component instance and/or business component instance according to the network orchestration scheme comprises: retrieving the network component to be generated from the network component library, and/or retrieving the business component to be generated from the business component library; request The NFV platform allocates the first virtual machine to the retrieved network component, instantiates the retrieved network component, and/or requests the NFV platform to allocate the second virtual machine to the retrieved service component, and retrieves the The business components to be instantiated.
  • the update request is sent to the NFV platform according to the network orchestration scheme, wherein the update request is used to request the NFV platform to perform an update process on the existing network component instance and/or the service component instance, and the update process includes one of the following: Network component instances and/or business component instances for capacity expansion, version upgrades of existing network component instances and/or business component instances, virtual machine migration of existing network component instances and/or business component instances.
  • the communication path between the current network component instances and/or the service component instances and/or between the network component instances and the service component instances is configured according to a network orchestration scheme, wherein the configured content includes at least the following One: configure Internet Protocol IP routing, configure link security parameters, and configure quality of service QoS parameters for the communication link.
  • an evaluation method of a policy rule based on the above communication network architecture is provided.
  • the method for evaluating a policy rule includes: acquiring a network feature information set of a currently running network, where the network feature information set includes at least one of the following: status information of a network component instance, status information of a service component instance, and a user. Status information; evaluates the currently used policy rules according to the network feature information set, and modifies the policy rules when the evaluation result does not meet the preset requirements.
  • the method further includes: pushing the modified policy rule to the user network service orchestration and management module, and triggering the user network service orchestration and management module to adjust the network deployment of the execution layer.
  • a method of selecting a service component based on the above communication network architecture is provided.
  • the method for selecting a service component includes: determining whether a terminal to be accessed is pre-configured with a component selection policy, wherein the component selection policy is used to determine a network component instance and/or a service component instance that provides a network service for the terminal. Determining a network component instance and/or a business component instance providing the network service according to the judgment result.
  • determining, according to the determination result, the network component instance and/or the service component instance for providing the network service comprises: determining, according to the determination result, that the terminal is pre-configured with the component selection policy; and selecting, according to the component selection policy, the network component instance for providing the network service for the terminal and/or Or a business component instance.
  • determining, according to the determination result, the network component instance and/or the service component instance for providing the network service comprises: determining, according to the determination result, that the terminal is not configured with a component selection policy in advance; and acquiring the network network currently running the network
  • the information collection includes: at least one of the following: status information of the network component instance, status information of the service component instance, status information of the user; and selecting a network component instance providing the network service for the terminal according to the network feature information set And/or business component instances.
  • a device for providing a network service based on the above communication network architecture is provided.
  • the network service providing apparatus includes: an obtaining module, configured to acquire a network service requirement, policy rule information, and a network feature information set of a currently running network, where the network feature information set includes at least one of the following: a network component The status information of the instance, the status information of the service component instance, and the status information of the user; the determining module is configured to determine a network orchestration plan according to the network service requirement, the policy rule information, and the network feature information set of the currently running network; the execution module is set to adopt The network orchestration scheme provides network services to users.
  • the obtaining module includes: a first obtaining unit configured to acquire state information of the network component instance from the network component information management module; and a second obtaining unit configured to acquire state information of the service component instance from the business component information management module;
  • the third obtaining unit is configured to obtain user state information from the user information management module, and the fourth obtaining unit is configured to obtain policy rule information from the policy rule base.
  • the execution module comprises: a first execution unit configured to create a new network component instance and/or a service component instance according to a network orchestration scheme; and a second execution unit configured to perform an existing network component instance according to the network orchestration scheme and / or business component instance to update; the third execution unit, set to the connection relationship between the current network component instances and / or business component instances and / or network component instances and business component instances according to the network orchestration scheme Configure it.
  • the first execution unit comprises: a retrieval subunit, configured to retrieve a network component to be generated from the network component library, and/or to retrieve a business component to be generated from the business component library; request the subunit, set to Requesting the NFV platform to allocate the first virtual machine to the retrieved network component, instantiating the retrieved network component; and/or requesting the NFV platform to allocate the second virtual machine to the retrieved service component,
  • the obtained business components are instantiated.
  • the second execution unit is configured to send an update request to the NFV platform according to the network orchestration scheme, wherein the update request is used to request the NFV platform to perform an update process on the existing network component instance and/or the service component instance, where the update process includes At least one of: capacity expansion of an existing network component instance and/or business component instance, version upgrade of an existing network component instance and/or business component instance, presence of an existing network component instance, and/or service Component instances for virtual machine migration.
  • the third execution unit is configured to configure a communication path between the current network component instances and/or between the service component instances and/or between the network component instances and the service component instances according to the network orchestration scheme, wherein The configuration includes at least one of the following: configuring Internet Protocol (IP) routing, configuring link security parameters, and configuring Quality of Service (QoS) parameters for the communication link.
  • IP Internet Protocol
  • QoS Quality of Service
  • an apparatus for evaluating a policy rule based on the above-described communication network architecture is provided.
  • the device for evaluating the policy rule includes: an obtaining module, configured to acquire a network feature information set of the currently running network, where the network feature information set includes at least one of the following: status information of the network component instance, and a service component instance. The status information and the status information of the user; the processing module is configured to evaluate the currently used policy rule according to the network feature information set, and modify the policy rule when the evaluation result does not meet the preset requirement.
  • the device further includes: a triggering module, configured to push the modified policy rule to the user network service orchestration and management module, and trigger the user network service orchestration and management module to adjust the network deployment of the execution layer.
  • a triggering module configured to push the modified policy rule to the user network service orchestration and management module, and trigger the user network service orchestration and management module to adjust the network deployment of the execution layer.
  • a selection device for a service component based on the above communication network architecture is provided.
  • the device for selecting a service component includes: a determining module, configured to determine whether the terminal to be accessed is pre-configured with a component selection policy, wherein the component selection policy is used to determine an instance of the network component that provides the network service for the terminal and And a business component instance; a determining module, configured to determine a network component instance and/or a business component instance providing the network service according to the determination result.
  • the determining module includes: a first determining unit, configured to determine, according to the determination result, that the terminal is pre-configured with a component selection policy; and the first selecting unit is configured to select, for the terminal, a network component instance that provides the network service according to the component selection policy, and/or Business component instance.
  • the determining module includes: a second determining unit, configured to determine, according to the determining result, that the terminal is not configured with a component selection policy in advance; and the acquiring unit is configured to acquire a network feature information set of the currently running network, where the network feature information set includes the following At least one of: status information of the network component instance, status information of the service component instance, status information of the user; and a second selecting unit configured to select a network component instance and/or a service component that provides the network service for the terminal according to the network feature information set Example.
  • the management layer is configured to acquire the user network service requirement, and create, arrange, and schedule the functional components on the execution layer based on the network service requirement; the execution layer is configured to provide the network service to the user, and/or
  • the information to be used by the management layer in the process of creating, scheduling, and scheduling the functional components is reported to the management layer, wherein the execution layer is formed by networking a plurality of functional components, and the functional components include at least one of the following: network components
  • the service component solves the problem that the operator in the related technology is difficult to customize and automatically schedule the network according to the user's requirements, so that the operator can customize and automatically schedule the network according to the user's needs, thereby providing a more convenient service for the user.
  • FIG. 1 is a schematic diagram of a network architecture of a 4G EPC according to the related art
  • FIG. 2 is a structural block diagram of a communication network architecture according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a communication network architecture in accordance with a preferred embodiment of the present invention.
  • FIG. 4 is a schematic diagram showing the relationship between a user network orchestration and management module and other functional modules within a management layer according to a preferred embodiment of the present invention
  • FIG. 5 is a flowchart of a method for providing a network service based on the above communication network architecture according to an embodiment of the present invention
  • FIG. 6 is a schematic diagram of a relationship between a user network orchestration and management module and an NFV virtualization platform according to a preferred embodiment of the present invention
  • FIG. 7 is a flow diagram of a user network service orchestration and management module performing policy decisions in accordance with a preferred embodiment of the present invention
  • FIG. 8 is a flowchart of a method for evaluating a policy rule based on the above-described communication network architecture according to an embodiment of the present invention
  • FIG. 9 is a schematic diagram of a policy effect evaluation process in accordance with a preferred embodiment of the present invention.
  • FIG. 10 is a flowchart of a method of selecting a service component based on the above communication network architecture according to an embodiment of the present invention
  • FIG. 11 is a flowchart of a service path selection process when a mobile terminal accesses according to a preferred embodiment of the present invention.
  • FIG. 12 is a structural block diagram of a network service providing apparatus based on the above communication network architecture according to an embodiment of the present invention.
  • FIG. 13 is a structural block diagram of a network service providing apparatus based on the above communication network architecture according to a preferred embodiment of the present invention.
  • FIG. 14 is a structural block diagram of an apparatus for evaluating a policy rule based on the above-described communication network architecture according to an embodiment of the present invention.
  • 15 is a structural block diagram of an apparatus for evaluating a policy rule based on the above-described communication network architecture according to a preferred embodiment of the present invention.
  • 16 is a structural block diagram of a selection device of a service component based on the above communication network architecture according to an embodiment of the present invention
  • 17 is a structural block diagram of a selection device of a service component based on the above-described communication network architecture, in accordance with a preferred embodiment of the present invention.
  • the communication network architecture may include: a management layer 10 configured to acquire network service requirements, and create, schedule, and schedule functional components on an execution layer based on user network service requirements; and execute layer 20, set to Providing network services to the user, and/or reporting the information to be used by the management layer in the process of creating, scheduling, and scheduling the functional components to the management layer, wherein the execution layer is composed of a plurality of functional components, and functions
  • the component includes at least one of the following: a network component, a business component.
  • the management layer is used to obtain the network service requirements of the user, and the network service resources and the network openability are scheduled according to the network service requirements; and the management layer can create functional components and pairs in the execution layer.
  • the created functional components and/or the existing functional components are arranged and managed, and the information to be used by the management in the process of scheduling the network service resources and the network openability is reported to the management layer, thereby
  • the information exchange between the execution layers to provide network services solves the problem that the operators in the related technologies are difficult to
  • the problem of user customization and automatic scheduling of the network enables the operator to customize and automatically schedule the network according to the user's needs, thereby providing more convenient service for the user.
  • FIG. 3 is a schematic diagram of a communication network architecture in accordance with a preferred embodiment of the present invention.
  • the management layer 10 may include: a network component information management module 100 configured to provide status information of a currently running network component instance; and a business component information management module 102 configured to provide a currently running business component instance Status information; user information management module 104, configured to provide user status information; user network service orchestration and management module 106, configured to obtain policy rule information, and to function components according to policy rule information, network service requirements, and network feature information sets The creating, scheduling, and scheduling, wherein the network feature information set includes at least one of the following: status information of the network component instance, status information of the business component instance, and user status information.
  • user network service requirements may include, but are not limited to, virtual operations, user-based network optimization requirements, and private network requirements.
  • the status information of the network component instance may include, but is not limited to, location, load, capacity, reliability, network topology of the network component.
  • the status information of the business component instance may include, but is not limited to, load, capacity, capability, network topology, location of the business component.
  • the user's status information may include, but is not limited to, mobility, location, quality of service (QoS), service preferences, terminal capabilities.
  • QoS quality of service
  • the network component instance and the service component instance may be shared by multiple users; or a dedicated component instance customized for a specific user, thereby forming a private network serving the user.
  • the management layer 10 may further include: a policy rule base 108, configured to provide policy rule information; and a policy effect evaluation module 110 configured to evaluate the execution result of the policy rule information to determine whether The policy rule information is modified.
  • a policy rule base 108 configured to provide policy rule information
  • a policy effect evaluation module 110 configured to evaluate the execution result of the policy rule information to determine whether The policy rule information is modified.
  • the policy effect evaluation module may adjust the policy rule according to the running status of each component instance and the overall running state of the user network, and update the policy rule base. After the policy effect evaluation module updates the policy library, the user network service orchestration and management module is triggered to reconfigure and adjust the execution layer network.
  • the management layer 10 may further include: a network component library 112 configured to provide a network component to be generated, wherein the information provided in the network component library includes at least one of the following: a functional description of the network component The network component provider information, the number of available licenses, and the network component image (image); the business component library 114 is configured to provide a business component to be generated, wherein the information provided in the business component library includes at least one of the following: The function description of the service component, the service component provider information, the available license quantity, the service component image, and the user subscription library 116 are set to manage the user subscription information.
  • a network component library 112 configured to provide a network component to be generated, wherein the information provided in the network component library includes at least one of the following: a functional description of the network component The network component provider information, the number of available licenses, and the network component image (image); the business component library 114 is configured to provide a business component to be generated, wherein the information provided in the business component library includes at least one of the following: The function
  • the execution layer 20 can include a network component 200 configured to provide access services and a service component 202 configured to provide value added services for the business data.
  • the communication network architecture shown in FIG. 3 can be divided into a management layer and an execution layer.
  • the management is mainly responsible for user service management and network operation and maintenance, while the executive layer is responsible for performing various functions related to network services.
  • the execution layer is broken down into several functional components to implement different functions.
  • the execution layer can be divided into network components and business components depending on the content of the processing.
  • the network component is mainly responsible for performing service signaling processing and service packet processing of the user network access, for example, user access management, mobility management, and the like.
  • the business component is mainly responsible for value-added processing related to user services, such as: business security, encryption, deep business identification (DPI), optimization, storage, and so on.
  • These components can be classified into control plane components and user plane components according to whether the processing object is mainly signaling or data stream.
  • These functional components can be dynamically created by NFV virtualization technology and dynamically organized into a network service system based on SDN/SON technology.
  • An end-to-end service can include: end users, networks, and services. If you want to implement automated on-demand scheduling of dynamic networks, you need a set of architectures that can organically coordinate the three. A set of telecommunications network architectures for on-demand dynamic scheduling is described in the preferred embodiment.
  • the user network service orchestration and management module Through the user network service orchestration and management module, the scheduling of network service resources and the scheduling of network openability can be realized.
  • the user network service orchestration and management module obtains user network service requirements externally, and integrates network, service and user factors, and arranges, schedules and opens network service resources and capabilities based on relevant policies.
  • the network side can include a static network component library set up to define and manage the set of network components (including functional descriptions of the components, provider information, number of available licenses, image images, etc.) that can be created and scheduled, and can also contain a A dynamic network component information management module configured to collect and classify real-time status and information of running network components and form a corresponding information base; the business aspect can be created and scheduled in addition to a static business component library set to define and manage.
  • Business components (including functional descriptions of components, provider information, available licenses, image images, etc.), and may also contain a business component information management module that is configured to collect and classify real-time business components in real time.
  • Status and information the user side can also include a static user subscription library set to manage the user subscription information and a dynamic user information management module, set to collect and analyze the user's attributes, status, location, behavior and other information and form corresponding Information library.
  • management can also include a policy rule base, which is set to manage various policies in the network, and a policy effect evaluation function to comprehensively evaluate the effect of policy execution to promote closed-loop optimization of network policies.
  • the components of the execution layer can be either the functions of traditional logical network elements in the telecommunication network or the various components redefined according to the 5G requirements.
  • Some user-side basic simple functional components can be integrated into the SDN OF switch function, and other control planes and user plane components can be lifecycle management and scheduling through NFV virtualization.
  • the deployment location of components can be scheduled according to different requirements. Some components may be deployed to the network side. Some components may be deployed to the terminal side, which may be distributed deployment of nearby users or centralized deployment.
  • the executive layer's related policies can be used to report related information on the network to the management layer for network/service/user-related analysis.
  • organization set the various needs for network service orchestration and openness.
  • the execution layer components can be divided into functional divisions:
  • Network components provide access services for users, which may include: access management, mobility management, Internet Protocol (IP) address allocation, session establishment and other control plane functions, and user data packet forwarding and other user plane functions.
  • IP Internet Protocol
  • Business components additional processing of user's business data, such as transcoding, compression, security, storage and other value-added services.
  • Network components and business components can be further divided into control plane components and user plane components.
  • access management and mobility management in the network component are control plane components, while user data packet forwarding belongs to the user plane component.
  • FIG. 4 is a schematic diagram showing the relationship between a user network orchestration and management module and other functional modules within the management layer according to a preferred embodiment of the present invention.
  • the policy rule base provides policy rule information to the user network orchestration and management module.
  • the content of the policy rule information may include, but is not limited to, information such as creating a new execution component (network component or business component) when a specific condition is satisfied, and how to configure a relationship between the execution components.
  • the rest of the policy rule information is not listed here.
  • a policy rule base is a collection of policy rules generated based on an operator configuration.
  • the policy effect evaluation module adjusts the policy rule according to the running status of each component and the overall running state of the user network, updates the policy rule base, and pushes the updated policy to the user network management service module.
  • the network component state management module is responsible for collecting state information of a running network component instance in the network, and the state information of the network component instance may include: location, load, capacity, reliability, network topology, and the like of the network component.
  • the network component status management module provides the collected network component status information to the user network orchestration and management module.
  • the business component information management module collects status information of running business component instances in the network.
  • the status information of the business component instance may include: load, capacity, capability, network topology, location of the business component, and the like.
  • the business component information management module provides the collected business component status information to the user network orchestration and management module.
  • the user information management module is responsible for collecting user information, such as user mobility, location, quality of service (QoS), service preferences, terminal capabilities, etc., and the user information management module sends the above user characteristics to the user network orchestration and management module.
  • user information such as user mobility, location, quality of service (QoS), service preferences, terminal capabilities, etc.
  • User network service requirements are network service requirements from operators themselves or from virtual operators, enterprises, organizations, etc., such as virtual operation requirements, network optimization requirements, and private network requirements such as car networking.
  • Virtual Operator A wants to lease the network of Mobile Network Operator B to provide mobile network access services.
  • the virtual operator A hopes that the mobile network operator B provides the following network services: the user capacity is 1 million, the required wireless access bandwidth is 1 Mbps per user, and the core network outlet bandwidth is 1 Tbps.
  • the user range is limited to the preset area, and the user is contracted and Network management (for example: network components, configuration of service components) is the responsibility of virtual operator A, which is only responsible for providing network infrastructure, such as network components and service components, to ensure the reliable operation of network components and service components.
  • the virtual operator A also needs to specifically describe the requirements of the network components and service components, for example, which network components and service components are required to be provided by the mobile network operator B.
  • the following service components need to be provided: Transcoding, NAT, etc. And need to provide the following network components: access control, mobility management, and so on.
  • the network service requirement usually requires sufficient communication between the user and the operator and signs the corresponding agreement.
  • the network service provider (for example, the above mobile network operator B) can provide the corresponding network service according to the protocol.
  • FIG. 5 is a flowchart of a method of providing a network service based on the above communication network architecture according to an embodiment of the present invention. As shown in FIG. 5, the method may include the following processing steps:
  • Step S502 Obtain network service requirements, policy rule information, and a network feature information set of the currently running network, where the network feature information set includes at least one of the following: status information of the network component instance, status information of the service component instance, and status of the user.
  • the network feature information set includes at least one of the following: status information of the network component instance, status information of the service component instance, and status of the user.
  • Step S504 Determine a network orchestration scheme according to the user network service requirement, the policy rule information, and the network feature information set.
  • Step S506 providing a network service to the user by using a network orchestration scheme.
  • acquiring the network feature information set may include at least one of the following:
  • Step S1 acquiring state information of the network component instance from the network component information management module
  • Step S2 Obtain status information of the service component instance from the service component information management module.
  • Step S3 acquiring state information of the user from the user information management module
  • Step S4 Obtain policy rule information from the policy rule base.
  • the status information of the network component instance may include, but is not limited to, at least one of: location, load, capacity, reliability, and network topology of the network component instance; the status information of the foregoing service component instance may include but not It is limited to at least one of the following: load, capacity, capability, network topology, location of the service component instance; the status information of the foregoing user may include, but is not limited to, at least one of the following: mobility, location, QoS, service preference, terminal capability.
  • step S506 providing a network service to the user by using a network orchestration scheme may include one of the following:
  • Step S5 Create a new network component instance and/or business component instance according to the network orchestration scheme
  • Step S6 update an existing network component instance and/or a service component instance according to a network orchestration scheme
  • Step S7 Configure a connection relationship between current network component instances and/or service component instances, and/or network component instances and business component instances according to a network orchestration scheme.
  • creating a new network component instance and/or service component instance according to the network orchestration scheme may include the following operations:
  • Step S51 retrieve the network component to be generated from the network component library, and/or retrieve the service component to be generated from the business component library;
  • Step S52 requesting the NFV platform to allocate the first virtual machine to the retrieved network component, instantiating the retrieved network component; and/or requesting the NFV platform to allocate the second virtual machine to the retrieved service component. , instantiate the retrieved business components.
  • the user network orchestration and management module when the user network orchestration and management module receives the network service requirement from the user, the user network orchestration and management module obtains the policy rule information obtained from the policy rule base, and combines the data from the currently running network.
  • the status information of the network component instance, the status information of the business component instance, and the user characteristics are determined to determine how to provide the requested network service to the user.
  • the User Network Orchestration and Management module may make a decision to generate a new network component instance and/or service component instance.
  • the user network orchestration and management module requests to create a new virtual network element instance, load the version, and configure the virtual network element instance to meet the NFV virtualization platform interface. Requirements for network component instances and business component instances.
  • an update request may be sent to the NFV platform according to the network orchestration scheme, where the update request is used to request the NFV platform to perform an update process on the existing network component instance and/or the service component instance, and the update process includes the following: One: capacity expansion of existing network component instances and/or business component instances, version upgrades of existing network component instances and/or business component instances, and existing network component instances and/or business component instances Perform a virtual machine migration.
  • the user network orchestration and management module determines that it is not necessary to create a new network component instance and a service component instance, it is only necessary to expand the existing network component instance and the service component instance, version upgrade, or virtual machine migration.
  • the user network orchestration and management module also submits the corresponding requirements to the NFV virtualization platform, and the NFV virtualization platform completes the requirements for capacity expansion, version upgrade, or virtual machine migration.
  • a communication path between the current network component instances and/or between the service component instances and/or between the network component instances and the service component instances may be configured according to a network orchestration scheme, wherein the configuration
  • the content includes at least one of the following: configuring IP routing, configuring link security parameters, and configuring QoS parameters of the communication link.
  • the user network orchestration and management module can also determine and configure.
  • the connection relationship between components For example, between the network component instance 1 and the network component instance 2, the link between the network component instance 1 and the network component instance 2 needs to be configured with the bandwidth, the quality of service to be guaranteed, and the security level to be secured.
  • the type of interface between the network component instance 1 and the network component instance 2 for example, Transmission Control Protocol (TCP)).
  • TCP Transmission Control Protocol
  • the user The network orchestration and management module also needs to configure the service chain path. For example, the path of the service chain 1 passes through the business component instance 1, the business component instance 3, and the business component instance 4.
  • FIG. 6 is a schematic diagram of a relationship between a user network orchestration and management module and an NFV virtualization platform in accordance with a preferred embodiment of the present invention.
  • the user network orchestration and management module is located in the OSS/BSS in the architecture defined by the NFV, and can be connected to the NFV Orchestrator (NFVO) through the Os-Nfvo interface.
  • the NFV virtualization platform can include: NFVO, Virtual Network Function Manager (VNFM), Virtual Infrastructure Manager (VIM), Network Function Virtualization Infrastructure (Network Function) Virtualization Infrastructure, referred to as NFVI).
  • the NFV Orchestrator of the NFV virtualization platform can dynamically scale the capacity of virtual network elements based on network load.
  • this dynamic scaling of the NFV virtualization platform is a dynamic scaling within the scope of the user network orchestration and management module, which does not adjust the network element capacity beyond the user network orchestration and management module.
  • FIG. 7 is a flow diagram of a user network service orchestration and management module performing policy decisions in accordance with a preferred embodiment of the present invention. As shown in FIG. 7, the process may include the following processing steps:
  • Step S702 The policy rule base pushes the policy rule configured by the operator to the user network service orchestration and management module.
  • Step S704 The network component information management module sends the collected status information of each network component instance that is currently running to the user network service orchestration and management module.
  • the network component information management module may send the state information of the network component instance to the user network service orchestration and management module according to the pre-configured timing.
  • Step S706 The service component information management module sends the collected service information of each service component instance that is currently running to the user network service orchestration and management module.
  • the service component information management module may send the service information of the service component instance to the user network service orchestration and management module according to the pre-configured timing.
  • Step S708 The user information management module sends the collected user status information to the user network service scheduling and management module.
  • the user information management module can send user status information to the user network service orchestration and management module according to the pre-configured timing.
  • Step S710 The user network service orchestration and management module receives the new network service requirement from the user.
  • Step S712 If the user network service orchestration and management module lacks relevant policy rule information, the user network service orchestration and management module acquires the policy rule information from the policy rule base.
  • Step S714 If the user network service orchestration and management module lacks the state information of the latest network component instance, the user network service orchestration and management module acquires the state information of the network component instance from the network component information management module.
  • Step S716 If the user network service orchestration and management module lacks the state information of the latest business component instance, the user network service orchestration and management module acquires the state information of the service component instance from the business component information management module.
  • Step S718 If the user network service orchestration and management module lacks the latest user state information, the user network service orchestration and management module acquires the user state information from the user information management module.
  • Step S720 The user network service orchestration and management module formulates a network orchestration policy according to the policy rule, the state information of the network component instance, the state information of the service component instance, and the user state information, where the method may include: creating or modifying a network component and a service component, Establish or modify connections between components, and so on.
  • Step S722 The user network service orchestration and management module sends the network orchestration policy to the NFV orchestrator, and the NFV orchestrator assists the user network service orchestration and management module to instantiate the new network component and the business component, or modify the existing network component instance. And business component instances, and configure the connection relationship between components.
  • FIG. 8 is a flowchart of a method for evaluating a policy rule based on the above-described communication network architecture according to an embodiment of the present invention. As shown in FIG. 8, the method may include the following processing steps:
  • Step S802 Acquire a network feature information set of the currently running network, where the network feature information set includes at least one of the following: status information of the network component instance, status information of the service component instance, and status information of the user;
  • Step S804 The currently used policy rule is evaluated according to the network feature information set, and the policy rule is modified when the evaluation result does not meet the preset requirement.
  • step S804 the following operations may also be included:
  • Step S8 Pushing the modified policy rule to the user network service orchestration and management module, triggering the user network service orchestration and management module to adjust the network deployment of the execution layer.
  • FIG. 9 is a schematic diagram of a policy effect evaluation process in accordance with a preferred embodiment of the present invention.
  • the policy effect evaluation module collects status information about network operations, such as component load, throughput, and service information. Whole network service orchestration and management strategy. The following is an example of the process of policy adjustment. Assume that a mobile operator has a mobile network that provides services for both human-to-human networks and the Internet of Things. With the increase of IoT terminals, a mobile network is gradually difficult to adapt and provide services for the above two types of services.
  • the policy effect evaluation module may include: status information of the network component instance and status information of the service component instance, and determines to change a previously set network policy, so the policy effect evaluation module modifies the policy library.
  • IoT service needs are served using a dedicated mobile network.
  • the policy effectiveness evaluation module can also stipulate that a specific type of Internet of Things needs to be serviced by a unique mobile network. For example, the Internet of Vehicles uses a proprietary mobile network for its special needs in real time.
  • the user network service orchestration and management module may be triggered to perform network reconfiguration and adjustment.
  • FIG. 10 is a flowchart of a method of selecting a service component based on the above-described communication network architecture according to an embodiment of the present invention. As shown in FIG. 10, the method may include the following processing steps:
  • Step S1002 determining whether the terminal to be accessed is pre-configured with a component selection policy, where the component selection policy is used to determine a network component instance and/or a service component instance that provides a network service for the terminal;
  • Step S1004 Determine, according to the determination result, a network component instance and/or a service component instance that provides a network service.
  • the network component is responsible for providing access services for the user, which may include: access management, mobility management, IP address allocation, session establishment and other control plane functions, and user data packet forwarding and other user plane functions.
  • the business component is responsible for additional processing of the user's business data, such as transcoding, compression, security, storage and other value-added services.
  • step S1004 determining, according to the determination result, that the network component instance and/or the service component instance providing the network service may include the following steps:
  • Step S9 determining, according to the determination result, that the terminal is pre-configured with a component selection policy
  • Step S10 Select a network component instance and/or a service component instance that provides a network service for the terminal according to the component selection policy.
  • determining, according to the determination result, that the network component instance and/or the service component instance providing the network service may include the following operations:
  • Step S11 determining, according to the determination result, that the terminal is not configured with a component selection policy in advance;
  • Step S12 Acquire a network feature information set of the currently running network, where the network feature information set includes at least one of the following: status information of the network component instance, status information of the service component instance, and status of the user. Information; selecting a network component instance and/or a service component instance that provides a network service for the terminal according to the network feature information set.
  • FIG. 11 is a flowchart of a service path selection process when a mobile terminal accesses according to a preferred embodiment of the present invention.
  • the mobile terminal may have pre-configured a component selection policy, for example, the mobile terminal of the Internet of Things configures the identifier of the private network to which it is connected.
  • the mobile terminal sends the network identifier of the network to be accessed to the first access point when accessing, and the first access point selects the subsequent network component instance and the service component instance according to the network identifier specified by the mobile terminal.
  • the mobile terminal also selects the first access point according to the pre-configuration.
  • a particular IoT terminal may be configured to select only specific Radio Access Technology (RAT) access, in which case the mobile terminal selects the first access point according to the configured RAT type.
  • RAT Radio Access Technology
  • the network may be based on user characteristics (eg, terminal type, location, service preferences, etc.), network status, service information, and service characteristics requested by the user (eg, throughput requirements) , mobility requirements, security requirements, latency requirements, etc.), determine the network component instances and service component instances that users serve when they access.
  • user characteristics eg, terminal type, location, service preferences, etc.
  • network status e.g., network status, service information, and service characteristics requested by the user
  • service characteristics requested by the user eg, throughput requirements
  • the process can include the following processing steps:
  • Step S1102 The mobile terminal selects the first access point according to the configuration and the information broadcasted by the network.
  • Step S1104 The mobile terminal sends an access request to the first access point.
  • Step S1106 The first access point selects a control plane network component instance of the service according to the network information specified by the mobile terminal. If the mobile terminal does not specify the network to which it is connected, the first access point may be based on user characteristics (eg, terminal type, location, service preferences, etc.), network status, service information, and service characteristics requested by the user (eg, : Throughput requirements, mobility requirements, security requirements, latency requirements, etc., determine the control plane network component instances that users serve when they access.
  • user characteristics eg, terminal type, location, service preferences, etc.
  • network status e.g, network status, service information, and service characteristics requested by the user
  • service characteristics eg, : Throughput requirements, mobility requirements, security requirements, latency requirements, etc.
  • Step S1108 The first access point sends an access request to the control plane network component instance of the selected service.
  • Step S1110 The mobile terminal performs subsequent negotiation with the control plane network component instance of the service, and the control control plane network component instance of the service selects the user plane component instance of the service and the service component instance of the service, and establishes a user plane channel. After the negotiation is completed, the mobile terminal can send service data through the user plane channel.
  • Step S1112 The mobile terminal sends the service data to the user plane network component instance through the user plane channel.
  • the user plane network component instance sends the user's business data to the control plane network component instance, and performs business data processing for the user component specified by the user.
  • Carrier O has a person-to-person communication network that is operating on its own.
  • the strategy set by Carrier O is to organize a proprietary network to serve if it receives IoT requirements.
  • the Internet of Things with different needs uses different private network services.
  • the Internet of Things requirements from Organization A and the Internet of Things requirements from Organization B will be served by different mobile networks.
  • different dedicated network services will be used.
  • Organization A also hopes that Carrier O provides Internet of Vehicles services and telemedicine IoT services, due to the two Internet of Things to the Internet.
  • the requirements are different, so Carrier O serves each other through two different private networks.
  • Carrier O will also set a more detailed network deployment strategy.
  • the mobility management component can be omitted. If the user in the network has a large amount of access to the Internet (Internet) and the throughput is large, then the network is The access point location sets an instance of a service component such as a CDN; if there is a large amount of local services in the user's demand, the network will select a network component instance and a business component instance for its nearest location.
  • Operator O has configured corresponding rules in the policy rule base to wait for the user's new network requirements.
  • Operator O receives the network service requirements from S.
  • S is the organizer of a football match, and S hopes that during the game, operator O will be able to provide enhanced coverage for his stadium.
  • the stadium will expect an audience of approximately 3,000 people during the game, with an average expected consumption of 1 Mbps per person.
  • Operator O decided to provide the above temporary service for S.
  • Operator O submits the received network service requirements to the network management layer, and finally triggers the user network service orchestration and management module to orchestrate the network to meet the network service requirements of S.
  • the user network service orchestration and management module checks the policies received from the policy rule base after receiving the above requirements.
  • the user network service orchestration and management module finds that the policy rules configured by the operator O need to re-establish new network component instances and business component instances for the new network service request.
  • the user network service orchestration and management module decides to arrange the following network component instances and business component instances: deploying user access management, low mobility management, IP address management, user plane packet forwarding, etc. in the vicinity of the stadium Example of control plane and user plane components; deploy business component instances such as compression and transcoding in the stadium to reduce the impact of large traffic on the air interface.
  • the user network service orchestration and management module determines the size of the network component instance and the business component instance and the bandwidth requirement between the component instances according to the number of viewers and the traffic demand provided by the S.
  • the user network service orchestration and management module submits the above requirements to the NFV orchestrator after making the above network orchestration decision.
  • the NFV orchestrator applies physical resources to the network component instance and the business component instance, and may include: a central processing unit (CPU), a memory, a memory, and loads a network component instance and a business component instance, and the NFV orchestrator is a component instance. The communication link between the two requests the corresponding bandwidth.
  • other functional entities of the management layer will be responsible for configuring the network component instances and business component instances to deliver the network to S for use.
  • FIG. 12 is a structural block diagram of a device for providing a network service based on the above communication network architecture according to an embodiment of the present invention.
  • the network service providing apparatus may include: an obtaining module 10 configured to acquire a network service requirement, policy rule information, and a network feature information set of a currently running network, where the network feature information set includes at least one of the following The status information of the network component, the status information of the service component, and the status information of the user; the determining module 20 is configured to determine a network orchestration scheme according to the network service requirement, the policy rule information, and the network feature information set of the currently running network; and the executing module 30, Set to use network orchestration scheme to provide users with network services.
  • the obtaining module 10 may include: a first obtaining unit 100 configured to acquire state information of a network component instance from a network component information management module; and a second obtaining unit 102 configured to manage information from the service component
  • the module acquires the status information of the service component instance.
  • the third obtaining unit 104 is configured to obtain the user state information from the user information management module.
  • the fourth obtaining unit 106 is configured to obtain the policy rule information from the policy rule base.
  • the execution module 30 may include: a first execution unit 300 configured to create a new network component instance and/or a service component instance according to a network orchestration scheme; and a second execution unit 302 configured to Updating the existing network component instance and/or business component instance according to the network orchestration scheme; the third execution unit 304 is configured to be between the current network component instances and/or the business component instances according to the network orchestration scheme and/or Or the connection relationship between the network component instance and the business component instance is configured.
  • the first execution unit 300 may include: a retrieval sub-unit (not shown) configured to retrieve a network component to be generated from the network component library, and/or to retrieve a to-be-generated from the business component library. a service component; a request subunit (not shown) configured to request the NFV platform to allocate a first virtual machine to the retrieved network component, instantiate the retrieved network component; and/or request NFV The platform allocates a second virtual machine to the retrieved business component, and instantiates the retrieved business component.
  • a retrieval sub-unit configured to retrieve a network component to be generated from the network component library, and/or to retrieve a to-be-generated from the business component library.
  • a service component configured to request the NFV platform to allocate a first virtual machine to the retrieved network component, instantiate the retrieved network component
  • request NFV The platform allocates a second virtual machine to the retrieved business component, and instantiates the retrieved business component.
  • the second execution unit 302 is configured to send an update request to the NFV platform according to the network orchestration scheme, where the update request is used to request the NFV platform to perform an update process on the existing network component instance and/or the service component instance, and the update process is performed.
  • the update request is used to request the NFV platform to perform an update process on the existing network component instance and/or the service component instance, and the update process is performed.
  • the third execution unit 304 is configured to configure a communication path between the current network component instances and/or between the service component instances and/or between the network component instances and the service component instances according to the network orchestration scheme, wherein The configuration includes at least one of the following: configuring IP routing, configuring link security parameters, and configuring QoS parameters of the communication link.
  • FIG. 14 is a structural block diagram of an apparatus for evaluating a policy rule based on the above-described communication network architecture according to an embodiment of the present invention.
  • the evaluation device of the policy rule may include: an obtaining module 40 configured to acquire a network feature information set of a currently running network, where the network feature information set includes at least one of the following: status information of the network component instance, The status information of the service component instance and the status information of the user; the processing module 50 is configured to evaluate the currently used policy rule according to the network feature information set, and modify the policy rule when the evaluation result does not meet the preset requirement.
  • the apparatus may further include: a triggering module 60 configured to push the modified policy rule to the user network service orchestration and management module, triggering the network of the user network service orchestration and management module to the execution layer Deployment to adjust.
  • a triggering module 60 configured to push the modified policy rule to the user network service orchestration and management module, triggering the network of the user network service orchestration and management module to the execution layer Deployment to adjust.
  • the selecting means of the service component may include: a determining module 70, configured to determine whether the terminal to be accessed is pre-configured with a component selection policy, wherein the component selection policy is used to determine a network that provides network services for the terminal.
  • a component selection policy is used to determine a network that provides network services for the terminal.
  • a component instance and/or a business component instance ; a determination module 80 configured to determine a network component instance and/or a business component instance providing a network service based on the determination result.
  • the determining module 80 may include: a first determining unit 800, configured to determine, according to the determining result, that the terminal is pre-configured with a component selection policy; and the first selecting unit 802 is configured to select the terminal according to the component selection policy.
  • a network component instance and/or business component instance that provides a network service.
  • the determining module 80 may include: a second determining unit 804, configured to determine, according to the determination result, that the terminal is not configured with a component selection policy in advance; and the obtaining unit 806 is configured to acquire network feature information of the currently running network.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the network service provisioning, the policy rule evaluation, the service component selection method, and the apparatus provided by the embodiments of the present invention have the following beneficial effects: the operator can customize and automatically schedule the network according to the user requirements, thereby enabling the operator to User requirements customize and automatically schedule the network to make it easier for users to serve.

Abstract

本发明公开了一种网络服务提供、策略规则评估、服务组件选择方法及装置，在上述架构中，管理层，设置为获取用户网络服务需求，并基于网络服务需求对执行层上的功能组件进行创建、编排和调度；执行层，设置为为用户提供网络服务，和/或，将管理层在对功能组件进行创建、编排和调度的过程中待使用的信息上报至管理层，其中，执行层由多个功能组件组网而成，功能组件包括以下至少之一：网络组件、业务组件。根据本发明提供的技术方案，能够使得运营商可以根据用户需求定制并自动调度网络，从而更方便地为用户提供服务。

Description

网络服务提供、策略规则评估、服务组件选择方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种网络服务提供、策略规则评估、服务组件选择方法及装置。
背景技术
当今时代，移动通信在20多年时间里得到了飞速发展，为人们的生活方式、工作方式以及社会的政治、经济等各方面都带来了巨大的影响。人类社会已经逐步进入高效的信息化时代，各个方面业务应用需求呈现爆发式增长，给未来无线移动带宽系统在频率、技术以及运营等各方面都带来了巨大的挑战。
第五代移动通信技术(5G)移动宽带系统将成为面向2020年以后人类信息社会需求的无线移动通信系统，其为一个多业务多技术融合的网络，通过技术的演进和创新，满足未来广泛的数据、连接的各种业务不断发展的需要，提升用户体验。随着无线移动通信系统带宽和能力的提升，面向个人和行业的移动互联网和物联网应用快速发展，移动通信相关产业生态将发生重要变化。无线移动通信技术与计算机及信息技术会更加紧密和更深层次地交叉融合，集成电路、器件工艺、软件技术等也将持续快速地发展，支撑未来5G移动宽带产业发展。
根据社会职责和功能、终端用户、业务应用和网络运营等对未来5G的愿景分析，5G将是能够满足不同需求不同场景的多样性网络。METIS定义的5G网络需求可以包括但不限于如下几个场景：
设备到设备通讯(Device to Device Communication，简称为D2D)；
大规模机器通讯(Massive Machine Communication，简称为MMC)；
移动的网络(Moving Network)；
超密集网络(Ultra Dense Network，简称为UDN)；
超高可靠通迅(Ultra-reliable communication，简称为URC)。
图1是根据相关技术的第四代移动通信技术(4G)演进分组核心网(EPC)的网络架构示意图。如图1所示，该网络架构可以包括如下部分：
演进的通用移动通信系统陆地无线接入网(E-UTRAN)，设置为实现所有与演进网络有关的无线功能；
移动管理实体(Mobility Management Entity，简称为MME)，负责控制面移动管理，其中，可以包括但不限于：用户上下文和移动状态管理、分配用户临时身份标识；
服务网关实体(Servering Gateway，简称为S-GW)，其为用户面实体，负责用户面数据路由处理；
分组数据网网关(Packet Data Network Gateway，简称为PDN GW或P-GW)，负责用户设备(UE)接入分组数据网(Packet Data Network，简称为PDN)的网关功能；
需要说明的是，P-GW和S-GW可能合设在一个物理实体中。
服务GPRS支持节点(Serving GPRS Supporting Node，简称为SGSN)；
计费和策略控制实体(Policy and Charging Rule Function，简称为PCRF)，设置为策略控制决定和流计费控制功能；
归属网络服务器(Home Subsriber Server，简称为HSS)设置为存储用户签约信息。
在传统网络中，为满足一项特殊的需求而部署一套专用网络将会耗费大量的人力、物力和财力。因此，运营商往往通过在现有网络的基础上添加补丁的方式来满足不同的需求。这种传统的部署方式不仅易造成新业务的部署周期延长，而且也会使得运营商的网络臃肿，各种功能都集成在一个网络中从而导致运营和维护困难、网络复杂。
未来的5G网络是一个多应用场景，多接入相互协同的网络。不同的应用场景对于网络的需求不尽相同。有些应用场景需要高带宽的接入，而有些应用场景则需要低时延的处理，还有些应用场景需要更高的安全性。而且每个应用场景对于网络的服务期限也不尽相同，有些应用场景需要能使用几十年、甚至上百年的网络，而有些应用场景可能只需要能够维持几小时的网络。因此，如果想要仅通过一个静态的网络去满足上述全部应用场景，是一件非常困难的事，而且即使能够完成也势必会为此付出巨大的代价。因此，一个能力开放、按需自动化调度的动态网络必然是未来5G网络的发展趋势。
云计算和虚拟技术的出现使得运营商可以根据不同场景和需求定制不同网络成为可能。基于虚拟机构建的移动网元可方便地根据功能进行定制，以适配不同的网络需求。网络功能虚拟化(NFV)、软件定义网络(SDN)、云计算等新技术的兴起使得根 据需求动态生成和调度网元成为可能。NFV使得电信运营商和设备制造商可以方便利用通用服务器实现电信级设备，使得软件和硬件相互分离，从而加速新业务开展，降低运营商的运维成本等。NFV是一种平台技术，可为各种电信级业务提供服务。NFV系统的基本功能是根据运营支撑系统(OSS)/业务支撑系统(BSS)的需求将OSS/BSS提出的网络原型实例化，可以包括：根据OSS/BSS的需求创建虚拟网元实例、建立虚拟网元实例之间的连接以及虚拟网元与其他网元之间的连接、根据系统负荷对虚拟网元的容量进行自动伸缩管理从而在满足需求的基础上节电等。但NFV系统无法做出创建或修改网络的决定，该决定需要由运营商管理层来完成。现网中OSS/BSS不具备自动部署网络的功能。
发明内容
本发明实施例提供了一种网络服务提供、策略规则评估、服务组件选择方法及装置，以至少解决相关技术中运营商难以根据用户需求定制并自动调度网络的问题。
根据本发明的一个方面，提供了一种通信网络架构。
根据本发明实施例的通信网络架构包括：管理层，设置为获取用户网络服务需求，并基于网络服务需求对执行层上的功能组件进行创建、编排和调度；执行层，设置为为用户提供网络服务，和/或，将管理层在对功能组件进行创建、编排和调度的过程中待使用的信息上报至管理层，其中，执行层由多个功能组件组网而成，功能组件包括以下至少之一：网络组件、业务组件。
优选地，管理层包括：网络组件信息管理模块，设置为提供当前正在运行的网络组件实例的状态信息；业务组件信息管理模块，设置为提供当前正在运行的业务组件实例的状态信息；用户信息管理模块，设置为提供用户状态信息；用户网络服务编排与管理模块，设置为获取策略规则信息，并根据策略规则信息、用户网络服务需求以及网络特征信息集合对功能组件进行创建、编排和调度，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户状态信息。
优选地，管理层还包括：策略规则库，设置为提供策略规则信息；策略效果评估模块，设置为对策略规则信息的执行结果进行评估，确定是否需要对策略规则信息进行修改。
优选地，管理层还包括：网络组件库，设置为提供待生成的网络组件，其中，网络组件库中提供的信息包括以下至少之一：网络组件的功能描述，网络组件提供方信 息，可用许可(license)数量、网络组件映像(image)；业务组件库，设置为提供待生成的业务组件，其中，业务组件库中提供的信息包括以下至少之一：业务组件的功能描述，业务组件提供方信息，可用license数量、业务组件image；用户签约库，设置为管理用户签约信息。
优选地，执行层包括：网络组件，设置为提供接入服务；业务组件，设置为为业务数据提供增值服务。
根据本发明的另一方面，提供了一种基于上述通信网络架构的网络服务的提供方法。
根据本发明实施例的网络服务的提供方法包括：获取用户网络服务需求、策略规则信息以及当前运行网络的网络特征信息集合，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；根据用户网络服务需求、策略规则信息以及网络特征信息集合确定网络编排方案；采用网络编排方案为用户提供网络服务。
优选地，获取网络特征信息集合包括以下至少之一：从网络组件信息管理模块获取网络组件实例的状态信息；从业务组件信息管理模块获取业务组件实例的状态信息；从用户信息管理模块获取用户的状态信息；从策略规则库中获取策略规则信息。
优选地，网络组件实例的状态信息包括以下至少之一：网络组件实例的位置、负荷、容量、可靠性、网络拓扑；业务组件实例的状态信息包括以下至少之一：负荷、容量、能力、网络拓扑、业务组件实例的位置；用户的状态信息包括以下至少之一：移动性、位置、QoS、业务偏好、终端能力。
优选地，采用网络编排方案为用户提供网络服务包括以下之一：根据网络编排方案创建新的网络组件实例和/或业务组件实例；根据网络编排方案对已经存在的网络组件实例和/或业务组件实例进行更新；根据网络编排方案对当前的网络组件之间实例、和/或业务组件实例之间、和/或网络组件实例与业务组件实例之间的连接关系进行配置。
优选地，根据网络编排方案创建新的网络组件实例和/或业务组件实例包括：从网络组件库调取待生成的网络组件，和/或，从业务组件库调取待生成的业务组件；请求NFV平台为调取到的网络组件分配第一虚拟机，对调取到的网络组件进行实例化处理；和/或，请求NFV平台为调取到的业务组件分配第二虚拟机，对调取到的业务组件进行实例化处理。
优选地，根据网络编排方案向NFV平台发送更新请求，其中，更新请求用于请求NFV平台对已经存在的网络组件实例和/或业务组件实例进行更新处理，更新处理包括以下之一：对已经存在的网络组件实例和/或业务组件实例进行容量扩充、对已经存在的网络组件实例和/或业务组件实例进行版本升级、对已经存在的网络组件实例和/或业务组件实例进行虚拟机迁移。
优选地，根据网络编排方案对当前的网络组件实例之间和/或业务组件实例之间和/或网络组件实例与业务组件实例之间的通讯路径进行配置，其中，配置的内容包括以下至少之一：配置互联网协议IP路由、配置链路安全参数、配置通讯链路的服务质量QoS参数。
根据本发明的又一方面，提供了一种基于上述通信网络架构的策略规则的评估方法。
根据本发明实施例的策略规则的评估方法包括：获取当前运行网络的网络特征信息集合，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；根据网络特征信息集合对当前使用的策略规则进行评估，并在评估结果未满足预设需求时，对策略规则进行修改。
优选地，在对策略规则进行修改之后，还包括：将修改后的策略规则推送至用户网络服务编排与管理模块，触发用户网络服务编排与管理模块对执行层的网络部署进行调整。
根据本发明的再一方面，提供了一种基于上述通信网络架构的服务组件的选择方法。
根据本发明实施例的服务组件的选择方法包括：判断待接入的终端是否预先配置有组件选择策略，其中，组件选择策略用于确定为终端提供网络服务的网络组件实例和/或业务组件实例；根据判断结果确定提供网络服务的网络组件实例和/或业务组件实例。
优选地，根据判断结果确定提供网络服务的网络组件实例和/或业务组件实例包括：根据判断结果确定终端预先配置有组件选择策略；按照组件选择策略为终端选取提供网络服务的网络组件实例和/或业务组件实例。
优选地，根据判断结果确定提供网络服务的网络组件实例和/或业务组件实例包括：根据判断结果确定终端预先未配置有组件选择策略；获取当前运行网络的网络特 征信息集合，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；根据网络特征信息集合为终端选取提供网络服务的网络组件实例和/或业务组件实例。
根据本发明的再一方面，提供了一种基于上述通信网络架构的网络服务的提供装置。
根据本发明实施例的网络服务的提供装置包括：获取模块，设置为获取网络服务需求、策略规则信息以及当前运行网络的网络特征信息集合，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；确定模块，设置为根据网络服务需求、策略规则信息以及当前运行网络的网络特征信息集合确定网络编排方案；执行模块，设置为采用网络编排方案为用户提供网络服务。
优选地，获取模块包括：第一获取单元，设置为从网络组件信息管理模块获取网络组件实例的状态信息；第二获取单元，设置为从业务组件信息管理模块获取业务组件实例的状态信息；第三获取单元，设置为从用户信息管理模块获取用户状态信息；第四获取单元，设置为从策略规则库中获取策略规则信息。
优选地，执行模块包括：第一执行单元，设置为根据网络编排方案创建新的网络组件实例和/或业务组件实例；第二执行单元，设置为根据网络编排方案对已经存在的网络组件实例和/或业务组件实例进行更新；第三执行单元，设置为根据网络编排方案对当前的网络组件实例之间和/或业务组件实例之间和/或网络组件实例与业务组件实例之间的连接关系进行配置。
优选地，第一执行单元包括：调取子单元，设置为从网络组件库调取待生成的网络组件，和/或，从业务组件库调取待生成的业务组件；请求子单元，设置为请求NFV平台为调取到的网络组件分配第一虚拟机，对调取到的网络组件进行实例化处理；和/或，请求NFV平台为调取到的业务组件分配第二虚拟机，对调取到的业务组件进行实例化处理。
优选地，第二执行单元，设置为根据网络编排方案向NFV平台发送更新请求，其中，更新请求用于请求NFV平台对已经存在的网络组件实例和/或业务组件实例进行更新处理，更新处理包括以下至少之一：对已经存在的网络组件实例和/或业务组件实例进行容量扩充、对已经存在的网络组件实例和/或业务组件实例进行版本升级、对已经存在的网络组件实例和/或业务组件实例进行虚拟机迁移。
优选地，第三执行单元，设置为根据网络编排方案对当前的网络组件实例之间和/或业务组件实例之间和/或网络组件实例与业务组件实例之间的通讯路径进行配置，其中，配置的内容包括以下至少之一：配置互联网协议(IP)路由、配置链路安全参数、配置通讯链路的服务质量(QoS)参数。
根据本发明的再一方面，提供了一种基于上述通信网络架构的策略规则的评估装置。
根据本发明实施例的策略规则的评估装置包括：获取模块，设置为获取当前运行网络的网络特征信息集合，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；处理模块，设置为根据网络特征信息集合对当前使用的策略规则进行评估，并在评估结果未满足预设需求时，对策略规则进行修改。
优选地，上述装置还包括：触发模块，设置为将修改后的策略规则推送至用户网络服务编排与管理模块，触发用户网络服务编排与管理模块对执行层的网络部署进行调整。
根据本发明的再一方面，提供了一种基于上述通信网络架构的服务组件的选择装置。
根据本发明实施例的服务组件的选择装置包括：判断模块，设置为判断待接入的终端是否预先配置有组件选择策略，其中，组件选择策略用于确定为终端提供网络服务的网络组件实例和/或业务组件实例；确定模块，设置为根据判断结果确定提供网络服务的网络组件实例和/或业务组件实例。
优选地，确定模块包括：第一确定单元，设置为根据判断结果确定终端预先配置有组件选择策略；第一选取单元，设置为按照组件选择策略为终端选取提供网络服务的网络组件实例和/或业务组件实例。
优选地，确定模块包括：第二确定单元，设置为根据判断结果确定终端预先未配置有组件选择策略；获取单元，设置为获取当前运行网络的网络特征信息集合，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；第二选取单元，设置为根据网络特征信息集合为终端选取提供网络服务的网络组件实例和/或业务组件实例。
通过本发明实施例，管理层，设置为获取用户网络服务需求，并基于网络服务需求对执行层上的功能组件进行创建、编排和调度；执行层，设置为为用户提供网络服务，和/或，将管理层在对功能组件进行创建、编排和调度的过程中待使用的信息上报至管理层，其中，执行层由多个功能组件组网而成，功能组件包括以下至少之一：网络组件、业务组件，解决了相关技术中运营商难以根据用户需求定制并自动调度网络的问题，能够使得运营商可以根据用户需求定制并自动调度网络，从而更方便地为用户提供服务。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据相关技术的4G EPC的网络架构示意图；
图2是根据本发明实施例的通信网络架构的结构框图；
图3是根据本发明优选实施例的通信网络架构示意图；
图4是根据本发明优选实施例的管理层内部的用户网络编排与管理模块和其他功能模块之间的关系示意图；
图5是根据本发明实施例的基于上述通信网络架构的网络服务的提供方法的流程图；
图6是根据本发明优选实施例的用户网络编排与管理模块和NFV虚拟化平台的关系的示意图；
图7是根据本发明优选实施例的用户网络服务编排与管理模块执行策略决策的流程图；
图8是根据本发明实施例的基于上述通信网络架构的策略规则的评估方法的流程图；
图9是根据本发明优选实施例的策略效果评估过程的示意图；
图10是根据本发明实施例的基于上述通信网络架构的服务组件的选择方法的流程图；
图11是根据本发明优选实施例的移动终端接入时服务路径选择过程的流程图；
图12是根据本发明实施例的基于上述通信网络架构的网络服务的提供装置的结构框图；
图13是根据本发明优选实施例的基于上述通信网络架构的网络服务的提供装置的结构框图；
图14是根据本发明实施例的基于上述通信网络架构的策略规则的评估装置的结构框图；
图15是根据本发明优选实施例的基于上述通信网络架构的策略规则的评估装置的结构框图；
图16是根据本发明实施例的基于上述通信网络架构的服务组件的选择装置的结构框图；
图17是根据本发明优选实施例的基于上述通信网络架构的服务组件的选择装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
图2是根据本发明实施例的通信网络架构的结构框图。如图2所示，该通信网络架构可以包括：管理层10，设置为获取网络服务需求，并基于用户网络服务需求对执行层上的功能组件进行创建、编排和调度；执行层20，设置为为用户提供网络服务，和/或，将管理层在对功能组件进行创建、编排和调度的过程中待使用的信息上报至管理层，其中，执行层由多个功能组件组网而成，功能组件包括以下至少之一：网络组件、业务组件。
相关技术中运营商难以根据用户需求定制并自动调度网络。采用如图2所示的架构，利用管理层获取用户的网络服务需求，并基于网络服务需求对网络服务资源以及网络可开放能力进行编排调度；而管理层可以在执行层内创建功能组件以及对创建的功能组件和/或已经存在的功能组件进行编排和管理，以及管理层在对网络服务资源以及网络可开放能力进行编排调度的过程中待使用的信息上报至管理层，从而通过管理层与执行层之间进行的提供网络服务的信息交互，解决了相关技术中运营商难以根据 用户需求定制并自动调度网络的问题，能够使得运营商可以根据用户需求定制并自动调度网络，从而更方便地为用户提供服务。
优选地，图3是根据本发明优选实施例的通信网络架构示意图。如图3所示，管理层10可以包括：网络组件信息管理模块100，设置为提供当前正在运行的网络组件实例的状态信息；业务组件信息管理模块102，设置为提供当前正在运行的业务组件实例的状态信息；用户信息管理模块104，设置为提供用户状态信息；用户网络服务编排与管理模块106，设置为获取策略规则信息，并根据策略规则信息、网络服务需求以及网络特征信息集合对功能组件进行创建、编排和调度，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户状态信息。
在优选实施例中，用户网络服务需求可以包括但不限于：虚拟运营、基于用户的网络优化需求、专用网络需求。网络组件实例的状态信息可以包括但不限于：网络组件的位置、负荷、容量、可靠性、网络拓扑。业务组件实例的状态信息可以包括但不限于：负荷、容量、能力、网络拓扑、业务组件的位置。用户的状态信息可以包括但不限于：移动性、位置、服务质量(QoS)、业务偏好、终端能力。
在优选实施过程中，上述网络组件实例和业务组件实例可以为多用户共享；亦可为特定用户定制的专用组件实例，从而组建为用户服务的专用网络。
优选地，如图3所示，管理层10还可以包括：策略规则库108，设置为提供策略规则信息；策略效果评估模块110，设置为对策略规则信息的执行结果进行评估，确定是否需要对策略规则信息进行修改。
在优选实施例中，策略效果评估模块可以根据各组件实例运行状态及用户网络的总体运行状态调整策略规则，更新策略规则库。策略效果评估模块更新策略库后触发用户网络服务编排与管理模块对执行层网络进行重配和调整。
优选地，如图3所示，管理层10还可以包括：网络组件库112，设置为提供待生成的网络组件，其中，网络组件库中提供的信息包括以下至少之一：网络组件的功能描述，网络组件提供方信息，可用许可(license)数量、网络组件映像(image)；业务组件库114，设置为提供待生成的业务组件，其中，业务组件库中提供的信息包括以下至少之一：业务组件的功能描述，业务组件提供方信息，可用license数量、业务组件image；用户签约库116，设置为管理用户签约信息。
优选地，如图3所示，执行层20可以包括：网络组件200，设置为提供接入服务；业务组件202，设置为为业务数据提供增值服务。
作为本发明的一个优选实施例，如图3所示的通信网络架构可以分为管理层和执行层。管理层主要负责用户服务管理以及网络的运营和维护，而执行层负责执行网络服务相关的各项功能。在该优选实施例中，执行层被分解为若干的功能组件来实现不同的功能。根据处理的内容不同，执行层可以分为网络组件和业务组件。网络组件主要负责进行用户网络接入的业务信令处理和业务报文处理，例如：用户接入管理、移动性管理等。业务组件主要负责进行用户业务相关的增值处理，例如：业务安全、加密、深度业务识别(DPI)、优化、存储等。这些组件能够根据处理对象是以信令为主还是以数据流为主，可以被划分到控制面组件和用户面组件的行列。这些功能组件可以通过NFV虚拟化技术进行动态创建，基于SDN/SON技术动态地组织成一个网络服务系统。
一个端到端的服务，可以包括：终端用户、网络和业务三个部分。如果想要实现动态网络的自动化按需调度，则需要一套能够将三者进行有机协同的体系架构进行支撑。在该优选实施例中描述了一套按需动态调度的电信网络架构。
该网络架构具有如下特点：
(1)管理层
通过用户网络服务编排与管理模块实现对网络服务资源的编排调度和网络可开放能力的编排调度。该用户网络服务编排与管理模块对外获取用户网络服务需求，并综合网络、业务和用户三方面的因素，基于相关策略进行网络服务资源与能力的编排，调度与开放。
为实现上述目的，管理层引入了这三方面的要素。网络方面可以包含一个静态的网络组件库设置为定义和管理可以创建和调度的网络组件(包括组件的功能描述，提供方信息，可用license数量、组件映像(image)等)集合，还可以包含一个动态的网络组件信息管理模块，设置为采集和分类分析正在运行的网络组件的实时状态和信息并形成相应信息库；业务方面除了可以包含一个静态的业务组件库设置为定义和管理可以创建和调度的业务组件(包括组件的功能描述，提供方信息，可用license数量、组件映像(image)等)集合，还可以包含一个业务组件信息管理模块，设置为采集和分类分析正在运行的业务组件的实时状态和信息；用户方面同样可以包含一个静态的用户签约库设置为用户签约信息的管理和一个动态的用户信息管理模块，设置为采集和分析用户的属性、状态、位置、行为等信息并形成相应的信息库。
此外，管理层还可以包含一个策略规则库，设置为对网络中各种策略的管理，以及一个策略效果评估功能对策略执行效果进行综合评价，以推动网络策略的闭环优化。
(2)执行层
执行层各组件既可以是电信网络中传统逻辑网元的功能，也可以是根据5G需求重新定义的各种组件。部分用户面基础性简单功能组件可以融入SDN OF交换机功能，其它控制面和用户面组件可以通过NFV虚拟化方式进行生命周期管理与调度。
组件的部署位置可以按照不同的需求来进行调度，部分组件可能会部署到网络侧，部分组件可能会部署到终端侧，可以是就近用户的分布式部署，也可以是集中式部署。
执行层各组件除通过管理层进行动态的创建、编排和管理，执行管理层的相关策略外，同时可以根据管理层需求将网络中相关的信息上报给管理层进行网络/业务/用户相关的分析和组织，设置为网络服务编排和能力开放的各种需要。
执行层组件按照功能划分可以分为：
1)网络组件：为用户提供接入服务，其中，可以包括：接入管理、移动性管理、互联网协议(IP)地址分配、会话建立等控制面功能，以及用户数据报文转发等用户面功能。
2)业务组件：对用户的业务数据进行额外处理，例如：转码、压缩、安全、存储等增值服务。
网络组件和业务组件在实现上又可以分为控制面组件和用户面组件。例如：网络组件中的接入管理和移动性管理是控制面组件，而用户数据报文转发则属于用户面组件。
作为本发明的另一个优选实施例，图4是根据本发明优选实施例的管理层内部的用户网络编排与管理模块和其他功能模块之间的关系示意图。如图4所示，策略规则库向用户网络编排与管理模块提供策略规则信息。该策略规则信息的内容可以包括但不限于：当特定条件满足时创建新的执行组件(网络组件或业务组件)以及如何配置执行组件间的关系等信息。策略规则信息的其他内容在此不一一列举。策略规则库是根据运营商配置生成的策略规则的集合。策略效果评估模块根据各组件运行状态及用户网络的总体运行状态调整策略规则，更新策略规则库，并将更新后的策略推送至用户网络管理服务模块。
网络组件状态管理模块负责收集网络中正在运行的网络组件实例的状态信息，网络组件实例的状态信息可以包括：网络组件的位置、负荷、容量、可靠性、网络拓扑等。网络组件状态管理模块将收集到的网络组件状态信息提供给用户网络编排与管理模块。
业务组件信息管理模块收集网络中正在运行的业务组件实例的状态信息。业务组件实例的状态信息可以包括：负荷、容量、能力、网络拓扑、业务组件的位置等。业务组件信息管理模块将收集到的业务组件状态信息提供给用户网络编排与管理模块。
用户信息管理模块负责收集用户的信息，例如：用户的移动性、位置、服务质量(QoS)、业务偏好、终端能力等，用户信息管理模块将上述用户特性发送至用户网络编排和管理模块。
用户网络服务需求是来自运营商自身或来自虚拟运营商、企业、机构等用户的网络服务需求，例如：虚拟运营的需求、网络优化需求、车联网等专用网络需求等。
下面以虚拟运营为例描述一个典型的用户网络服务需求：
虚拟运营商A希望租用移动网络运营商B的网络提供移动网络接入服务。虚拟运营商A希望移动网络运营商B为其提供如下网络服务：用户容量100万，所需无线接入带宽平均每用户1Mbps，核心网出口带宽1Tbps，用户范围限定在预设区域，用户签约和网络管理(例如：网络组件、服务组件的配置)由虚拟运营商A负责，移动运营商B只负责提供网络基础设施，例如：网络组件和服务组件，保障网络组件和服务组件的可靠运行。在上述示例中，虚拟运营商A还需具体描述对网络组件和服务组件的需求，例如：需要移动网络运营商B提供哪些网络组件和服务组件，例如：需要提供如下服务组件：Transcoding、NAT等以及需要提供如下网络组件：接入控制、移动性管理等。网络服务需求通常需要用户与运营商之间进行充分沟通并签署相应的协议，网络服务提供商(例如：上述移动网络运营商B)可以根据协议为用户提供相应的网络服务。
图5是根据本发明实施例的基于上述通信网络架构的网络服务的提供方法的流程图。如图5所示，该方法可以包括以下处理步骤：
步骤S502：获取网络服务需求、策略规则信息以及当前运行网络的网络特征信息集合，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；
步骤S504：根据用户网络服务需求、策略规则信息以及网络特征信息集合确定网络编排方案；
步骤S506：采用网络编排方案为用户提供网络服务。
优选地，在步骤S502中，获取网络特征信息集合可以包括以下至少之一：
步骤S1：从网络组件信息管理模块获取网络组件实例的状态信息；
步骤S2：从业务组件信息管理模块获取业务组件实例的状态信息；
步骤S3：从用户信息管理模块获取用户的状态信息；
步骤S4：从策略规则库中获取策略规则信息。
在优选实施过程中，上述网络组件实例的状态信息可以包括但不限于以下至少之一：网络组件实例的位置、负荷、容量、可靠性、网络拓扑；上述业务组件实例的状态信息可以包括但不限于以下至少之一：负荷、容量、能力、网络拓扑、业务组件实例的位置；上述用户的状态信息可以包括但不限于以下至少之一：移动性、位置、QoS、业务偏好、终端能力。
优选地，在步骤S506中，采用网络编排方案为用户提供网络服务可以包括以下之一：
步骤S5：根据网络编排方案创建新的网络组件实例和/或业务组件实例；
步骤S6：根据网络编排方案对已经存在的网络组件实例和/或业务组件实例进行更新；
步骤S7：根据网络编排方案对当前的网络组件实例之间和/或业务组件实例之间、和/或网络组件实例与业务组件实例之间的连接关系进行配置。
优选地，在步骤S5中，根据网络编排方案创建新的网络组件实例和/或业务组件实例可以包括以下操作：
步骤S51：从网络组件库调取待生成的网络组件，和/或，从业务组件库调取待生成的业务组件；
步骤S52：请求NFV平台为调取到的网络组件分配第一虚拟机，对调取到的网络组件进行实例化处理；和/或，请求NFV平台为调取到的业务组件分配第二虚拟机，对调取到的业务组件进行实例化处理。
在优选实施例中，当用户网络编排与管理模块接收来自于用户的网络服务需求时，用户网络编排与管理模块根据从策略规则库获取到的策略规则信息，结合从当前正在运行的网络中获取到的网络组件实例的状态信息、业务组件实例的状态信息、用户特性，确定如何为用户提供所请求的网络服务。例如：用户网络编排与管理模块可能会做出生成新的网络组件实例和/或服务组件实例的决定。当需要生成新的网络组件实例和服务组件实例时，用户网络编排与管理模块将向NFV虚拟化平台接口请求创建新的虚拟网元实例，加载版本并对该虚拟网元实例进行配置，以满足网络组件实例和业务组件实例的需求。
优选地，在步骤S6中，可以根据网络编排方案向NFV平台发送更新请求，其中，更新请求用于请求NFV平台对已经存在的网络组件实例和/或业务组件实例进行更新处理，更新处理包括以下之一：对已经存在的网络组件实例和/或业务组件实例进行容量扩充、对已经存在的网络组件实例和/或业务组件实例进行版本升级、对已经存在的网络组件实例和/或业务组件实例进行虚拟机迁移。
在优选实施例中，若用户网络编排与管理模块决定不需要创建新的网络组件实例和服务组件实例，只需对已有的网络组件实例和服务组件实例进行扩容、版本升级或者虚拟机迁移，用户网络编排与管理模块亦将相应的需求提交给NFV虚拟化平台，由NFV虚拟化平台完成扩容、版本升级或者虚拟机迁移的需求。
优选地，在步骤S7中，可以根据网络编排方案对当前的网络组件实例之间和/或业务组件实例之间和/或网络组件实例与业务组件实例之间的通讯路径进行配置，其中，配置的内容包括以下至少之一：配置IP路由、配置链路安全参数、配置通讯链路的QoS参数。
在优选实施例中，除了决定是否生成新的网络组件实例和业务组件实例以及是否对现有网络组件实例和业务组件实例进行扩容、升级、迁移外，用户网络编排与管理模块还能够决定和配置组件间的连接关系。例如：在网络组件实例1和网络组件实例2之间需要通过IP互联，在网络组件实例1和网络组件实例2之间的链路需要配置的带宽、需要保障的服务质量、需要保障的安全级别，在网络组件实例1和网络组件实例2之间的接口类型(例如：传输控制协议(TCP))等。当存在业务链需求时，用户 网络编排与管理模块还需要配置业务链路径，例如：业务链1的路径经过业务组件实例1、业务组件实例3和业务组件实例4。
作为本发明的再一个优选实施例，图6是根据本发明优选实施例的用户网络编排与管理模块和NFV虚拟化平台的关系的示意图。如图6所示，用户网络编排与管理模块位于NFV所定义架构中的OSS/BSS中，其可以通过Os-Nfvo接口与NFV编排器(NFV Orchestrator，简称为NFVO)连接。NFV虚拟化平台可以包括：NFVO、虚拟网络功能管理器(Virtual Network Function Manager，简称为VNFM)、虚拟化基础设施管理器(Virtual Infrastructure Manager，简称为VIM)、网络功能虚拟化基础设施(Network Function Virtualization Infrastructure，简称为NFVI)等。在NFV中，NFV虚拟化平台的NFV Orchestrator可以根据网络负荷对虚拟网元的容量进行动态伸缩。此处，需要注意的是，NFV虚拟化平台的这种动态伸缩是在用户网络编排与管理模块的需求范围内的动态伸缩，其不会将网元容量调整到超过由用户网络编排与管理模块所设定的最大范围。
下面将结合图7所示的优选实施方式对上述优选实施过程作进一步的描述。
图7是根据本发明优选实施例的用户网络服务编排与管理模块执行策略决策的流程图。如图7所示，该流程可以包括以下处理步骤：
步骤S702：策略规则库将运营商配置的策略规则推送至用户网络服务编排与管理模块。
步骤S704：网络组件信息管理模块将收集到的当前正在运行的各网络组件实例的状态信息发送至用户网络服务编排与管理模块。网络组件信息管理模块可以根据预先配置定时向用户网络服务编排与管理模块发送网络组件实例的状态信息。
步骤S706：业务组件信息管理模块将收集到的当前正在运行的各业务组件实例的业务信息发送至用户网络服务编排与管理模块。业务组件信息管理模块可以根据预先配置定时向用户网络服务编排与管理模块发送业务组件实例的业务信息。
步骤S708：用户信息管理模块将收集到的用户状态信息发送至用户网络服务编排与管理模块。用户信息管理模块可以根据预先配置定时向用户网络服务编排与管理模块发送用户状态信息。
步骤S710：用户网络服务编排与管理模块接收来自于用户的新网络服务需求。
步骤S712：若用户网络服务编排与管理模块缺少相关策略规则信息，则用户网络服务编排与管理模块向策略规则库获取策略规则信息。
步骤S714：若用户网络服务编排与管理模块缺少最新的网络组件实例的状态信息，则用户网络服务编排与管理模块向网络组件信息管理模块获取网络组件实例的状态信息。
步骤S716：若用户网络服务编排与管理模块缺少最新的业务组件实例的状态信息，则用户网络服务编排与管理模块向业务组件信息管理模块获取业务组件实例的状态信息。
步骤S718：若用户网络服务编排与管理模块缺少最新的用户状态信息，则用户网络服务编排与管理模块向用户信息管理模块获取用户状态信息。
步骤S720：用户网络服务编排与管理模块根据策略规则、网络组件实例的状态信息、业务组件实例的状态信息、用户状态信息制定网络编排策略，其中，可以包括：创建或修改网络组件和服务组件，建立或修改组件间的连接等。
步骤S722：用户网络服务编排与管理模块将网络编排策略发送至NFV编排器，由NFV编排器帮助用户网络服务编排与管理模块将新网络组件和业务组件实例化，或修改现有的网络组件实例和业务组件实例，并配置组件间的连接关系。
图8是根据本发明实施例的基于上述通信网络架构的策略规则的评估方法的流程图。如图8所示，该方法可以包括以下处理步骤：
步骤S802：获取当前运行网络的网络特征信息集合，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；
步骤S804：根据网络特征信息集合对当前使用的策略规则进行评估，并在评估结果未满足预设需求时，对策略规则进行修改。
优选地，在步骤S804，对策略规则进行修改之后，还可以包括以下操作：
步骤S8：将修改后的策略规则推送至用户网络服务编排与管理模块，触发用户网络服务编排与管理模块对执行层的网络部署进行调整。
图9是根据本发明优选实施例的策略效果评估过程的示意图。如图9所示，策略效果评估模块会收集网络运行的状态信息，例如：组件负荷、吞吐量、业务信息等调 整网络服务编排与管理策略。下面通过一个示例对策略调整的过程加以说明。假设移动运营商有一张移动网络同时为人与人通信的网络和物联网提供服务。随着物联网终端的增加，一张移动网络逐渐难以适应同时为上述两种类型的业务提供服务。策略效果评估模块根据收集到的网络信息，其中，可以包括：网络组件实例的状态信息和业务组件实例的状态信息，决定改变之前设定的一张网策略，于是策略效果评估模块修改策略库，将物联网服务需求使用专用的移动网络为其服务。策略效果评估模块还可以规定：特定类型的物联网需要采用特有的移动网络为其服务，例如：车联网由于其实时性的特殊需求采用专有移动网络为其服务。策略效果评估模块更新策略库后可能会触发用户网络服务编排与管理模块进行网络重配和调整。
图10是根据本发明实施例的基于上述通信网络架构的服务组件的选择方法的流程图。如图10所示，该方法可以包括以下处理步骤：
步骤S1002：判断待接入的终端是否预先配置有组件选择策略，其中，组件选择策略用于确定为终端提供网络服务的网络组件实例和/或业务组件实例；
步骤S1004：根据判断结果确定提供网络服务的网络组件实例和/或业务组件实例。
在优选实施过程中，网络组件负责为用户提供接入服务，其中，可以包括：接入管理、移动性管理、IP地址分配、会话建立等控制面功能以及用户数据报文转发等用户面功能。业务组件负责对用户的业务数据进行额外处理，例如：转码、压缩、安全、存储等增值服务。
优选地，在步骤S1004中，根据判断结果确定提供网络服务的网络组件实例和/或业务组件实例可以包括以下步骤：
步骤S9：根据判断结果确定终端预先配置有组件选择策略；
步骤S10：按照组件选择策略为终端选取提供网络服务的网络组件实例和/或业务组件实例。
优选地，在步骤S1004中，根据判断结果确定提供网络服务的网络组件实例和/或业务组件实例可以包括以下操作：
步骤S11：根据判断结果确定终端预先未配置有组件选择策略；
步骤S12：获取当前运行网络的网络特征信息集合，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态 信息；根据网络特征信息集合为终端选取提供网络服务的网络组件实例和/或业务组件实例。
作为本发明的再一个优选实施例，图11是根据本发明优选实施例的移动终端接入时服务路径选择过程的流程图。如图11所示，当移动终端接入时，移动终端可能已经预先配置了组件选择策略，例如：物联网的移动终端配置了其所接入的专用网络的标识。此时，移动终端在接入时将所要接入网络的网络标识发送至第一接入点，由第一接入点根据移动终端指定的网络标识选择后续的网络组件实例和业务组件实例。移动终端还会根据预先配置选择第一接入点。例如：某种特殊的物联网终端可能配置为只选择特定的无线接入技术(RAT)接入，此时移动终端会根据配置的RAT类型选择第一接入点。
当移动终端没有指定其所要接入的网络时，网络可以根据用户特性(例如：终端类型、位置、业务偏好等信息)，网络状态、业务信息以及用户所请求的业务特性(例如：吞吐量需求、移动性需求、安全性需求、时延需求等)，决定用户在接入时为其服务的网络组件实例和服务组件实例。此时，移动终端先接入到第一接入点，由第一接入点根据上述信息选择为其服务的网络组件实例和服务组件实例。
下面将通过一个示例来说明如何为移动终端选择服务的网络组件实例和业务组件实例。假设在体育馆看球赛的用户希望通过手机回看刚才的精彩进球，用户的移动终端发起网络连接请求，在该网络连接请求中携带了上述“回看”请求。网络在接收到上述请求后发现位于体育馆内的网络组件实例可提供更好的服务，因为回看视频保存在本地的服务器中。网络为其选择体育馆内的本地网络组件实例为其服务。并且，由于很多人都在使用回看功能查看精彩进球，网络决定需要对视频数据进行压缩和转码，以减轻空口负荷，因此网络为其选择相应的压缩和转码服务组件实例为其服务。
该流程可以包括以下处理步骤：
步骤S1102：移动终端根据配置以及网络广播的信息选择第一接入点。
步骤S1104：移动终端将接入请求发送至第一接入点。
步骤S1106：第一接入点根据移动终端指定的网络信息为其选择服务的控制面网络组件实例。若移动终端未指定其所接入的网络时，第一接入点可以根据用户特性(例如：终端类型、位置、业务偏好等信息)、网络状态、业务信息以及用户所请求的业务特性(例如：吞吐量需求、移动性需求、安全性需求、时延需求等)，决定用户在接入时为其服务的控制面网络组件实例。
步骤S1108：第一接入点将接入请求发送至其所选择的服务的控制面网络组件实例。
步骤S1110：移动终端与服务的控制面网络组件实例间进行后续协商，服务的控制面网络组件实例为移动终端选择服务的用户面组件实例以及业务组件实例，并建立用户面通道。协商完成后移动终端可通过用户面通道发送业务数据。
步骤S1112：移动终端通过用户面通道向用户面网络组件实例发送业务数据。用户面网络组件实例将用户的业务数据发送至控制面网络组件实例，为该用户指定的业务组件实例进行业务数据的处理。
下面将以实例的形式描述当一个新的用户需求到来时，对上述整个技术方案的实施过程作进一步的描述。
在本实例中，假设运营商O有一张自身运营的人到人通讯网络正在运行。运营商O设定的策略是如果接收到物联网需求，将组织一张专有网络为其服务。并且，不同需求的物联网采用不同的专网服务，例如：来自组织A的物联网需求与来自组织B的物联网需求将采用不同的移动网络为其服务。若虽然来自同一组织但却具有不同的物联网需求，也将采用不同的专用网络服务，例如：组织A同时希望运营商O提供车联网服务和远程医疗物联网服务，由于两种物联网对网络的需求不同，因此，运营商O通过两个不同的专用网络分别为其提供服务。除上述策略外，运营商O还会设定更加细致的网络部署策略。例如：对低移动性需求的网络，由于终端的位置不变，可以就此省略移动性管理组件；若网络中的用户存在大量访问因特网(Internet)的业务且吞吐量较大，那么网络为其在接入点位置设置CDN等业务组件实例；若用户需求中存在大量的本地业务，则网络将会为其就近选择网络组件实例和业务组件实例。运营商O在策略规则库中已经配置了相应的规则，等待用户的新网络需求。
运营商O接收到来自于S的网络服务需求。S是一场足球比赛的组织者，S希望在球赛举办期间运营商O能够为其体育场馆提供增强覆盖业务。体育场馆已经存在无线覆盖，但该无线覆盖无法满足球赛举办期间大量人潮的上网需求。因此，S希望运营商O能够提供增强的网络，其中，可以包括：观众的基本通话需求、球赛期间能够为现场观众提供精彩回放、观众间的近距离通信、社交网络直播现场状况和评论互动等。体育馆在球赛举办期间预计的观众数量将达到约3000人，平均每人预计消耗带宽1Mbps。
运营商O决定为S提供上述临时服务。运营商O将收到的网络服务需求提交给网络管理层，并最终触发用户网络服务编排和管理模块对网络进行编排以满足S的网络服务需求。
用户网络服务编排和管理模块在接收到上述需求后对从策略规则库接收到的策略进行检查。用户网络服务编排和管理模块发现，按运营商O配置的策略规则需要为该新网络服务请求重新建立新的网络组件实例和业务组件实例。根据S的需求，用户网络服务编排和管理模块决定需要安排下列网络组件实例和业务组件实例：在体育场馆就近部署用户接入管理、低移动性管理、IP地址管理、用户面报文转发等网络控制面和用户面组件实例；在体育馆就近部署压缩和转码等业务组件实例，以减少大流量对空口的冲击。同时，用户网络服务编排与管理模块还根据S提供的观众人数和流量需求决定网络组件实例和业务组件实例的规模以及组件实例间的带宽需求。
用户网络服务编排和管理模块在做出上述网络编排决定后，将上述需求提交给NFV编排器。NFV编排器为网络组件实例和业务组件实例申请物理资源，其中，可以包括：中央处理器(CPU)、内存、存储器，并加载网络组件实例和业务组件实例等，同时，NFV编排器为组件实例间的通讯链路申请相应的带宽。在网络创建完成后，管理层的其他功能实体将负责对网络组件实例和业务组件实例进行配置，从而将网络交付给S加以使用。
图12是根据本发明实施例的基于上述通信网络架构的网络服务的提供装置的结构框图。如图12所示，该网络服务的提供装置可以包括：获取模块10，设置为获取网络服务需求、策略规则信息以及当前运行网络的网络特征信息集合，其中，网络特征信息集合包括以下至少之一：网络组件的状态信息、业务组件的状态信息、用户的状态信息；确定模块20，设置为根据网络服务需求、策略规则信息以及当前运行网络的网络特征信息集合确定网络编排方案；执行模块30，设置为采用网络编排方案为用户提供网络服务。
优选地，如图13所示，获取模块10可以包括：第一获取单元100，设置为从网络组件信息管理模块获取网络组件实例的状态信息；第二获取单元102，设置为从业务组件信息管理模块获取业务组件实例的状态信息；第三获取单元104，设置为从用户信息管理模块获取用户状态信息；第四获取单元106，设置为从策略规则库中获取策略规则信息。
优选地，如图13所示，执行模块30可以包括：第一执行单元300，设置为根据网络编排方案创建新的网络组件实例和/或业务组件实例；第二执行单元302，设置为 根据网络编排方案对已经存在的网络组件实例和/或业务组件实例进行更新；第三执行单元304，设置为根据网络编排方案对当前的网络组件实例之间和/或业务组件实例之间和/或网络组件实例与业务组件实例之间的连接关系进行配置。
优选地，第一执行单元300可以包括：调取子单元(图中未示出)，设置为从网络组件库调取待生成的网络组件，和/或，从业务组件库调取待生成的业务组件；请求子单元(图中未示出)，设置为请求NFV平台为调取到的网络组件分配第一虚拟机，对调取到的网络组件进行实例化处理；和/或，请求NFV平台为调取到的业务组件分配第二虚拟机，对调取到的业务组件进行实例化处理。
优选地，第二执行单元302，设置为根据网络编排方案向NFV平台发送更新请求，其中，更新请求用于请求NFV平台对已经存在的网络组件实例和/或业务组件实例进行更新处理，更新处理包括以下至少之一：对已经存在的网络组件实例和/或业务组件实例进行容量扩充、对已经存在的网络组件实例和/或业务组件实例进行版本升级、对已经存在的网络组件实例和/或业务组件实例进行虚拟机迁移。
优选地，第三执行单元304，设置为根据网络编排方案对当前的网络组件实例之间和/或业务组件实例之间和/或网络组件实例与业务组件实例之间的通讯路径进行配置，其中，配置的内容包括以下至少之一：配置IP路由、配置链路安全参数、配置通讯链路的QoS参数。
图14是根据本发明实施例的基于上述通信网络架构的策略规则的评估装置的结构框图。如图14所示，该策略规则的评估装置可以包括：获取模块40，设置为获取当前运行网络的网络特征信息集合，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；处理模块50，设置为根据网络特征信息集合对当前使用的策略规则进行评估，并在评估结果未满足预设需求时，对策略规则进行修改。
优选地，如图15所示，上述装置还可以包括：触发模块60，设置为将修改后的策略规则推送至用户网络服务编排与管理模块，触发用户网络服务编排与管理模块对执行层的网络部署进行调整。
图16是根据本发明实施例的基于上述通信网络架构的服务组件的选择装置的结构框图。如图16所示，该服务组件的选择装置可以包括：判断模块70，设置为判断待接入的终端是否预先配置有组件选择策略，其中，组件选择策略用于确定为终端提供网络服务的网络组件实例和/或业务组件实例；确定模块80，设置为根据判断结果确定提供网络服务的网络组件实例和/或业务组件实例。
优选地，如图17所示，确定模块80可以包括：第一确定单元800，设置为根据判断结果确定终端预先配置有组件选择策略；第一选取单元802，设置为按照组件选择策略为终端选取提供网络服务的网络组件实例和/或业务组件实例。
优选地，如图17所示，确定模块80可以包括：第二确定单元804，设置为根据判断结果确定终端预先未配置有组件选择策略；获取单元806，设置为获取当前运行网络的网络特征信息集合，其中，网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；第二选取单元808，设置为根据网络特征信息集合为终端选取提供网络服务的网络组件实例和/或业务组件实例。
从以上的描述中，可以看出，上述实施例实现了如下技术效果(需要说明的是这些效果是某些优选实施例可以达到的效果)：采用本发明实施例所提供的技术方案，能够使得运营商可以根据用户需求定制并自动调度网络，从而更方便地为用户提供服务。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种网络服务提供、策略规则评估、服务组件选择方法及装置具有以下有益效果：运营商可以根据用户需求定制并自动调度网络，从而能够使得运营商可以根据用户需求定制并自动调度网络，进而更方便地为用户提供服务。

Claims (28)

  1. 一种通信网络架构，包括：
    管理层，设置为获取用户网络服务需求，并基于所述用户网络服务需求对执行层上的功能组件进行创建、编排和调度；
    执行层，设置为为用户提供网络服务，和/或，将所述管理层在对所述功能组件进行创建、编排和调度的过程中待使用的信息上报至管理层，其中，所述执行层由多个功能组件组网而成，所述功能组件包括以下至少之一：网络组件、业务组件。
  2. 根据权利要求1所述的架构，其中，所述管理层包括：
    网络组件信息管理模块，设置为提供当前正在运行的网络组件实例的状态信息；
    业务组件信息管理模块，设置为提供当前正在运行的业务组件实例的状态信息；
    用户信息管理模块，设置为提供用户状态信息；
    用户网络服务编排与管理模块，设置为获取策略规则信息，并根据所述策略规则信息、所述用户网络服务需求以及网络特征信息集合对所述功能组件进行创建、编排和调度，其中，所述网络特征信息集合包括以下至少之一：所述网络组件实例的状态信息、所述业务组件实例的状态信息、所述用户状态信息。
  3. 根据权利要求2所述的架构，其中，所述管理层还包括：
    策略规则库，设置为提供所述策略规则信息；
    策略效果评估模块，设置为对所述策略规则信息的执行结果进行评估，确定是否需要对所述策略规则信息进行修改。
  4. 根据权利要求3所述的架构，其中，所述管理层还包括：
    网络组件库，设置为提供待生成的网络组件，其中，所述网络组件库中提供的信息包括以下至少之一：网络组件的功能描述，网络组件提供方信息，可用许可license数量、网络组件映像image；
    业务组件库，设置为提供待生成的业务组件，其中，所述业务组件库中提供的信息包括以下至少之一：业务组件的功能描述，业务组件提供方信息，可用license数量、业务组件image；
    用户签约库，设置为管理用户签约信息。
  5. 根据权利要求1所述的架构，其中，所述执行层包括：
    所述网络组件，设置为提供接入服务；
    所述业务组件，设置为为业务数据提供增值服务。
  6. 一种基于权利要求1至5中任一项所述的通信网络架构的网络服务的提供方法，包括：
    获取用户网络服务需求、策略规则信息以及当前运行网络的网络特征信息集合，其中，所述网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；
    根据所述用户网络服务需求、所述策略规则信息以及所述网络特征信息集合确定网络编排方案；
    采用所述网络编排方案为用户提供网络服务。
  7. 根据权利要求6所述的方法，其中，获取所述网络特征信息集合包括以下至少之一：
    从网络组件信息管理模块获取所述网络组件实例的状态信息；
    从业务组件信息管理模块获取所述业务组件实例的状态信息；
    从用户信息管理模块获取所述用户的状态信息；
    从策略规则库中获取所述策略规则信息。
  8. 根据权利要求7所述的方法，其中，
    所述网络组件实例的状态信息包括以下至少之一：网络组件实例的位置、负荷、容量、可靠性、网络拓扑；
    所述业务组件实例的状态信息包括以下至少之一：负荷、容量、能力、网络拓扑、业务组件实例的位置；
    所述用户的状态信息包括以下至少之一：移动性、位置、QoS、业务偏好、终端能力。
  9. 根据权利要求6所述的方法，其中，采用所述网络编排方案为所述用户提供所述网络服务包括以下之一：
    根据所述网络编排方案创建新的网络组件实例和/或业务组件实例；
    根据所述网络编排方案对已经存在的网络组件实例和/或业务组件实例进行更新；
    根据所述网络编排方案对当前的网络组件实例之间、和/或业务组件实例之间、和/或网络组件实例与业务组件实例之间的连接关系进行配置。
  10. 根据权利要求9所述的方法，其中，根据所述网络编排方案创建新的网络组件实例和/或业务组件实例包括：
    从网络组件库调取待生成的网络组件，和/或，从业务组件库调取待生成的业务组件；
    请求网络功能虚拟化NFV平台为调取到的网络组件分配第一虚拟机，对所述调取到的网络组件进行实例化处理；和/或，请求所述NFV平台为调取到的业务组件分配第二虚拟机，对所述调取到的业务组件进行实例化处理。
  11. 根据权利要求9所述的方法，其中，根据所述网络编排方案向NFV平台发送更新请求，其中，所述更新请求用于请求所述NFV平台对所述已经存在的网络组件实例和/或业务组件实例进行更新处理，所述更新处理包括以下至少之一：对所述已经存在的网络组件实例和/或业务组件实例进行容量扩充、对所述已经存在的网络组件实例和/或业务组件实例进行版本升级、对所述已经存在的网络组件实例和/或业务组件实例进行虚拟机迁移。
  12. 根据权利要求9所述的方法，其中，根据所述网络编排方案对所述当前的网络组件实例之间和/或业务组件实例之间和/或网络组件实例与业务组件实例之间的通讯路径进行配置，其中，配置的内容包括以下至少之一：配置互联网协议IP路由、配置链路安全参数、配置通讯链路的服务质量QoS参数。
  13. 一种基于权利要求1至5中任一项所述的通信网络架构的策略规则的评估方法，包括：
    获取当前运行网络的网络特征信息集合，其中，所述网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；
    根据所述网络特征信息集合对当前使用的策略规则进行评估，并在评估结果未满足预设需求时，对所述策略规则进行修改。
  14. 根据权利要求13所述的方法，其中，在对所述策略规则进行修改之后，还包括：
    将修改后的策略规则推送至用户网络服务编排与管理模块，触发所述用户网络服务编排与管理模块对执行层的网络部署进行调整。
  15. 一种基于权利要求1至5中任一项所述的通信网络架构的服务组件的选择方法，包括：
    判断待接入的终端是否预先配置有组件选择策略，其中，所述组件选择策略用于确定为所述终端提供网络服务的网络组件实例和/或业务组件实例；
    根据判断结果确定所述提供网络服务的网络组件实例和/或业务组件实例。
  16. 根据权利要求15所述的方法，其中，根据判断结果确定所述提供网络服务的网络组件实例和/或业务组件实例包括：
    根据判断结果确定所述终端预先配置有所述组件选择策略；
    按照所述组件选择策略为所述终端选取所述提供网络服务的网络组件实例和/或业务组件实例。
  17. 根据权利要求15所述的方法，其中，根据判断结果确定所述提供网络服务的网络组件实例和/或业务组件实例包括：
    根据判断结果确定所述终端预先未配置有所述组件选择策略；
    获取当前运行网络的网络特征信息集合，其中，所述网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；
    根据所述网络特征信息集合为所述移动终端选取所述提供网络服务的网络组件实例和/或业务组件实例。
  18. 一种基于权利要求1至5中任一项所述的通信网络架构的网络服务的提供装置，包括：
    获取模块，设置为获取网络服务需求、策略规则信息以及当前运行网络的网络特征信息集合，其中，所述网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；
    确定模块，设置为根据所述网络服务需求、策略规则信息以及网络特征信息确定网络编排方案；
    执行模块，设置为采用所述网络编排方案为用户提供网络服务。
  19. 根据权利要求18所述的装置，其中，所述获取模块包括：
    第一获取单元，设置为从网络组件信息管理模块获取所述网络组件实例的状态信息；
    第二获取单元，设置为从业务组件信息管理模块获取所述业务组件实例的状态信息；
    第三获取单元，设置为从用户信息管理模块获取所述用户状态信息；
    第四获取单元，设置为从策略库中获取策略规则信息。
  20. 根据权利要求18所述的装置，其中，所述执行模块包括：
    第一执行单元，设置为根据所述网络编排方案创建新的网络组件实例和/或业务组件实例；
    第二执行单元，设置为根据所述网络编排方案对已经存在的网络组件实例和/或业务组件实例进行更新；
    第三执行单元，设置为根据所述网络编排方案对网络组件实例之间和/或业务组件实例之间和/或网络组件实例与业务组件实例之间的连接关系进行配置。
  21. 根据权利要求20所述的装置，其中，所述第一执行单元包括：
    调取子单元，设置为从网络组件库调取待生成的网络组件，和/或，从业务组件库调取待生成的业务组件；
    请求子单元，设置为请求网络功能虚拟化NFV平台为调取到的网络组件分配第一虚拟机，对所述调取到的网络组件进行实例化处理；和/或，请求所述NFV平台为调取到的业务组件分配第二虚拟机，对所述调取到的业务组件进行实例化处理。
  22. 根据权利要求20所述的装置，其中，所述第二执行单元，设置为根据所述网络编排方案向NFV平台发送更新请求，其中，所述更新请求用于请求所述NFV平台对所述已经存在的网络组件实例和/或业务组件实例进行更新处理，所述更新处理包括以下至少之一：对所述已经存在的网络组件实例和/或业务组件实例 进行容量扩充、对所述已经存在的网络组件实例和/或业务组件实例进行版本升级、对所述已经存在的网络组件实例和/或业务组件实例进行虚拟机迁移。
  23. 根据权利要求20所述的装置，其中，所述第三执行单元，设置为根据所述网络编排方案对所述当前的网络组件实例之间和/或业务组件实例之间和/或网络组件实例与业务组件实例之间的通讯路径进行配置，其中，配置的内容包括以下至少之一：配置互联网协议IP路由、配置链路安全参数、配置通讯链路的服务质量QoS参数。
  24. 一种基于权利要求1至5中任一项所述的通信网络架构的策略规则的评估装置，包括：
    获取模块，设置为获取当前运行网络的网络特征信息集合，其中，所述网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；
    处理模块，设置为根据所述网络特征信息集合对当前使用的策略规则进行评估，并在评估结果未满足预设需求时，对所述策略规则进行修改。
  25. 根据权利要求24所述的装置，其中，所述装置还包括：
    触发模块，设置为将修改后的策略规则推送至用户网络服务编排与管理模块，触发所述用户网络服务编排与管理模块对执行层的网络部署进行调整。
  26. 一种基于权利要求1至5中任一项所述的通信网络架构的服务组件的选择装置，包括：
    判断模块，设置为判断待接入的终端是否预先配置有组件选择策略，其中，所述组件选择策略用于确定为所述终端提供网络服务的网络组件实例和/或业务组件实例；
    确定模块，设置为根据判断结果确定所述提供网络服务的网络组件实例和/或业务组件实例。
  27. 根据权利要求26所述的装置，其中，所述确定模块包括：
    第一确定单元，设置为根据判断结果确定所述终端预先配置有所述组件选择策略；
    第一选取单元，设置为按照所述组件选择策略为所述终端选取所述提供网络服务的网络组件实例和/或业务组件实例。
  28. 根据权利要求26所述的装置，其中，所述确定模块包括：
    第二确定单元，设置为根据判断结果确定所述终端预先未配置有所述组件选择策略；
    获取单元，设置为获取当前运行网络的网络特征信息集合，其中，所述网络特征信息集合包括以下至少之一：网络组件实例的状态信息、业务组件实例的状态信息、用户的状态信息；
    第二选取单元，设置为根据所述网络特征信息集合为所述终端选取所述提供网络服务的网络组件实例和/或业务组件实例。
PCT/CN2014/092721 2014-06-27 2014-12-01 网络服务提供、策略规则评估、服务组件选择方法及装置 WO2015196733A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP14895911.7A EP3163843A4 (en) 2014-06-27 2014-12-01 Method and device for providing network service, evaluating policy rule and selecting service assembly
US15/322,172 US20170222889A1 (en) 2014-06-27 2014-12-01 Method and Device for Providing Network Service, Evaluating Policy Rule and Selecting Service Assembly

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410300829.3A CN105282195A (zh) 2014-06-27 2014-06-27 网络服务提供、策略规则评估、服务组件选择方法及装置
CN201410300829.3 2014-06-27

Publications (1)

Publication Number Publication Date
WO2015196733A1 true WO2015196733A1 (zh) 2015-12-30

Family

ID=54936654

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/092721 WO2015196733A1 (zh) 2014-06-27 2014-12-01 网络服务提供、策略规则评估、服务组件选择方法及装置

Country Status (4)

Country Link
US (1) US20170222889A1 (zh)
EP (1) EP3163843A4 (zh)
CN (1) CN105282195A (zh)
WO (1) WO2015196733A1 (zh)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106792858A (zh) * 2016-12-30 2017-05-31 南京邮电大学 一种基于软件定义的超密集无线网络体系结构及实现方法
EP3419216A4 (en) * 2016-04-28 2019-01-23 Huawei Technologies Co., Ltd. MANUFACTURING POLICY DESCRIPTOR MANUFACTURING METHOD AND DEVICE
EP3402121A4 (en) * 2016-02-06 2019-01-23 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR TRANSMITTING PRINCIPLES IN AN NFV SYSTEM
EP3468105A4 (en) * 2016-06-30 2019-06-26 Huawei Technologies Co., Ltd. METHOD AND APPARATUS FOR ARRANGING NETWORK RESOURCES
EP3507968A4 (en) * 2016-10-31 2019-08-21 Huawei Technologies Co., Ltd. SYSTEM AND METHOD FOR DIRECTIVE CONFIGURATION OF FUNCTIONS AT CONTROL LEVEL BY FUNCTIONS AT ADMINISTRATIVE LEVEL
CN114697210A (zh) * 2017-11-22 2022-07-01 华为技术有限公司 一种网络性能保障方法及装置
CN115277311A (zh) * 2022-07-15 2022-11-01 南京邮电大学 一种多模网关的软件定义框架及通信控制方法

Families Citing this family (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10116514B1 (en) * 2015-03-30 2018-10-30 Amdocs Development Limited System, method and computer program for deploying an orchestration layer for a network based on network function virtualization (NFV)
CN105450601B (zh) * 2014-08-19 2019-05-07 华为技术有限公司 共享许可证的方法和装置
US20160219076A1 (en) * 2015-01-26 2016-07-28 Sprint Communications Company L.P. Hardware trust for integrated network function virtualization (nfv) and software defined network (sdn) systems
US9742790B2 (en) * 2015-06-16 2017-08-22 Intel Corporation Technologies for secure personalization of a security monitoring virtual network function
US10185599B2 (en) * 2015-07-07 2019-01-22 Openvpn Technologies, Inc. Kernel mode accelerator
CN107027134A (zh) * 2016-02-01 2017-08-08 上海无线通信研究中心 一种用户自定义的无线通信网络方法及系统
CN107087255B (zh) * 2016-02-15 2020-01-14 中兴通讯股份有限公司 一种终端位置管理、终端移动性管理的方法及网络节点
CN105847035B (zh) * 2016-03-16 2019-04-30 中国联合网络通信集团有限公司 一种虚拟化epc系统及业务实例化方法
EP3435615B1 (en) * 2016-03-28 2021-04-14 Huawei Technologies Co., Ltd. Network service implementation method, service controller, and communication system
US10374872B2 (en) * 2016-05-24 2019-08-06 Apstra, Inc. Configuring system resources for different reference architectures
WO2018000389A1 (zh) * 2016-06-30 2018-01-04 华为技术有限公司 管理网络切片的方法及其装置
CN109417719B (zh) * 2016-07-07 2021-02-23 华为技术有限公司 一种网络资源的管理方法、装置及系统
US10268470B2 (en) * 2016-08-26 2019-04-23 Nicira, Inc. Method and system for tracking progress and providing fault tolerance in automated upgrade of a network virtualization platform
CN106506176B (zh) * 2016-10-31 2019-10-11 中国联合网络通信集团有限公司 一种策略和计费规则生成方法和系统
CN108235333A (zh) * 2016-12-22 2018-06-29 中国移动通信有限公司研究院 一种为终端提供网络服务的方法及网络设备、基站
CN108243110B (zh) * 2016-12-26 2021-09-14 华为技术有限公司 一种资源调整方法、装置和系统
CN108270577B (zh) * 2016-12-30 2020-12-22 中移（杭州）信息技术有限公司 一种基于策略与计费控制架构的策略运营方法及系统
WO2018170647A1 (zh) * 2017-03-19 2018-09-27 华为技术有限公司 一种网络切片的管理方法、单元和系统
CN107204980B (zh) * 2017-05-25 2020-08-14 深信服科技股份有限公司 一种安全服务交付方法及系统
CN109218259B (zh) * 2017-06-30 2022-03-29 中兴通讯股份有限公司 许可管理方法及装置、applm功能实体及计算机可读存储介质
CN109600814B (zh) * 2017-09-30 2021-06-22 华为技术有限公司 一种发送定位信号的方法及设备
CN111194563B (zh) * 2017-10-13 2023-03-28 瑞典爱立信有限公司 促进针对无线通信设备选择网络接入的方法
CN111226497B (zh) * 2017-10-17 2024-02-09 瑞典爱立信有限公司 通信网络中的服务注册
US10841171B2 (en) * 2018-06-14 2020-11-17 Infosys Limited Method and system for virtual network service activation
US10581983B2 (en) 2018-07-09 2020-03-03 Nec Corporation Method and system for management of mobile network slices over a federated infrastructure
EP3614732B1 (en) * 2018-08-24 2023-02-15 Swisscom AG Service policy orchestration in a communication network
CN109271235B (zh) * 2018-09-06 2023-12-19 广州力挚网络科技有限公司 一种数据库集群建立方法与装置
CN110896407B (zh) * 2018-09-13 2023-03-10 亿阳信通股份有限公司 一种nfvo组件配置管理、请求转发方法和请求处理装置
EP3637685B1 (en) * 2018-10-12 2023-10-25 Nokia Solutions and Networks Oy Orchestration multi scheduler for multi slice network
US10708124B1 (en) 2018-12-31 2020-07-07 Facebook, Inc. System and method of data communication
CN110011834B (zh) * 2019-03-11 2020-09-22 烽火通信科技股份有限公司 一种管控融合型电信网络管理方法及系统
US11494217B1 (en) * 2019-11-15 2022-11-08 Amazon Technologies, Inc. Transparent reboot interception migration to facilitate virtualization host updates
CN110958170B (zh) * 2019-11-25 2021-09-14 中国联合网络通信集团有限公司 一种网络互联方法和装置
CN111104182A (zh) * 2019-12-17 2020-05-05 深圳前海环融联易信息科技服务有限公司 基于组件化的快速编排业务的方法、装置、计算机设备及存储介质
CN110944067B (zh) * 2019-12-27 2021-07-16 华为技术有限公司 一种负载均衡方法和服务器
CN113381868A (zh) * 2020-03-09 2021-09-10 中国电信股份有限公司 网络编排方法和装置、计算机可读存储介质
CN111724649A (zh) * 2020-07-22 2020-09-29 湖南中昱智云物联科技有限公司 一种物联网教学实训平台的组件自动识别系统及其应用
CN114268659A (zh) * 2020-09-14 2022-04-01 华为云计算技术有限公司 一种服务构建方法、相关装置及计算机可读存储介质
CN112702211B (zh) * 2020-12-30 2022-06-24 浪潮云信息技术股份公司 一种基于Kubernetes的网络服务网格系统
CN112953778B (zh) * 2021-03-17 2023-04-18 北京交通大学 智融标识网络中基于意图驱动的服务编排系统和方法
CN113300881B (zh) * 2021-04-23 2022-08-05 北京邮电大学 基于5g网络的编排调度方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374338A (zh) * 2007-08-25 2009-02-25 华为技术有限公司 一种实现用户策略自助服务的方法、实体和系统
CN103607430A (zh) * 2013-10-30 2014-02-26 中兴通讯股份有限公司 一种网络处理的方法和系统及网络控制中心
CN103795805A (zh) * 2014-02-27 2014-05-14 中国科学技术大学苏州研究院 基于sdn的分布式服务器负载均衡方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9037716B2 (en) * 2009-08-19 2015-05-19 At&T Intellectual Property I, L.P. System and method to manage a policy related to a network-based service
US9838370B2 (en) * 2012-09-07 2017-12-05 Oracle International Corporation Business attribute driven sizing algorithms
JP6117943B2 (ja) * 2013-01-31 2017-04-19 ▲ホア▼▲ウェイ▼技術有限公司Ｈｕａｗｅｉ Ｔｅｃｈｎｏｌｏｇｉｅｓ Ｃｏ．，Ｌｔｄ． カスタマイズ可能なモバイルブロードバンドネットワークシステムおよびモバイルブロードバンドネットワークをカスタマイズするための方法
CN103491129B (zh) * 2013-07-05 2017-07-14 华为技术有限公司 一种业务节点配置方法、业务节点池注册器及系统
EP3687205A1 (en) * 2014-02-21 2020-07-29 Huawei Technologies Co. Ltd. Saving ue context data based on data distribution policy
US9537745B1 (en) * 2014-03-07 2017-01-03 Google Inc. Distributed virtual machine disk image deployment

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101374338A (zh) * 2007-08-25 2009-02-25 华为技术有限公司 一种实现用户策略自助服务的方法、实体和系统
CN103607430A (zh) * 2013-10-30 2014-02-26 中兴通讯股份有限公司 一种网络处理的方法和系统及网络控制中心
CN103795805A (zh) * 2014-02-27 2014-05-14 中国科学技术大学苏州研究院 基于sdn的分布式服务器负载均衡方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3163843A4 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3402121A4 (en) * 2016-02-06 2019-01-23 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR TRANSMITTING PRINCIPLES IN AN NFV SYSTEM
US10791030B2 (en) 2016-02-06 2020-09-29 Huawei Technologies Co., Ltd. Policy transmission method and apparatus in NFV system
EP3668012A1 (en) * 2016-02-06 2020-06-17 Huawei Technologies Co., Ltd. Policy transmission method and apparatus in nfv system
US10601666B2 (en) 2016-04-28 2020-03-24 Huawei Technologies Co., Ltd. Network functions virtualization management and orchestration policy descriptor management method and apparatus
EP3419216A4 (en) * 2016-04-28 2019-01-23 Huawei Technologies Co., Ltd. MANUFACTURING POLICY DESCRIPTOR MANUFACTURING METHOD AND DEVICE
EP3468105A4 (en) * 2016-06-30 2019-06-26 Huawei Technologies Co., Ltd. METHOD AND APPARATUS FOR ARRANGING NETWORK RESOURCES
EP3507968A4 (en) * 2016-10-31 2019-08-21 Huawei Technologies Co., Ltd. SYSTEM AND METHOD FOR DIRECTIVE CONFIGURATION OF FUNCTIONS AT CONTROL LEVEL BY FUNCTIONS AT ADMINISTRATIVE LEVEL
US10812395B2 (en) 2016-10-31 2020-10-20 Huawei Technologies Co., Ltd. System and method for policy configuration of control plane functions by management plane functions
CN106792858A (zh) * 2016-12-30 2017-05-31 南京邮电大学 一种基于软件定义的超密集无线网络体系结构及实现方法
CN114697210A (zh) * 2017-11-22 2022-07-01 华为技术有限公司 一种网络性能保障方法及装置
CN114697210B (zh) * 2017-11-22 2023-11-03 华为技术有限公司 一种网络性能保障方法及装置
CN115277311A (zh) * 2022-07-15 2022-11-01 南京邮电大学 一种多模网关的软件定义框架及通信控制方法
CN115277311B (zh) * 2022-07-15 2024-02-20 南京邮电大学 一种多模网关的软件定义系统及通信控制方法

Also Published As

Publication number Publication date
EP3163843A1 (en) 2017-05-03
EP3163843A4 (en) 2017-08-16
CN105282195A (zh) 2016-01-27
US20170222889A1 (en) 2017-08-03

Similar Documents

Publication Publication Date Title
WO2015196733A1 (zh) 网络服务提供、策略规则评估、服务组件选择方法及装置
US11871340B2 (en) Network slice selection
EP3229524B1 (de) Verfahren zur steuerung von funkzugangsressourcen in einem kommunikationsnetzwerk
US10129108B2 (en) System and methods for network management and orchestration for network slicing
CN107003985B (zh) 基于面向服务的网络自动创建提供定制化虚拟无线网络的系统和方法
CN107925587B (zh) 用于网络切片的方法和装置
JP4852044B2 (ja) 移動体通信網で無線リソースをプリエンプティブに管理する方法
WO2018001144A1 (zh) 基站、访问请求的响应方法、装置及系统
WO2019007345A1 (zh) 网络切片的选择方法、装置及系统、存储介质
CN109792598A (zh) 支持网络分片的漫游环境中用于终端附接和创建归属路由pdu会话的方法和设备
US20170264592A1 (en) Methods and systems for secure network service
EP3744138A1 (en) Apparatus for network slicing and slice management to support multi-slice services
CN113965938B (zh) 切片业务系统及切片业务处理方法
CN110999371B (zh) 无锚移动网络中的虚拟锚
US20220386087A1 (en) Communications Network Architecture
EP3229526B1 (de) Steuerung von kommunikationsressourcen in einem kommunikationsnetzwerk
US11888677B2 (en) Method and system for network function migration procedures for a signaling control plane
US20240089164A1 (en) Method and system for network function migration procedures for a signaling control plane
Kaloxylos et al. Network slicing
EP3229525B1 (de) Verfahren zur steuerung von funkzugangsressourcen in einem kommunikationsnetzwerk
JP2023544182A (ja) 通信ネットワーク構成及びネットワークコンポーネントの選択方法
CN115884273A (zh) 网络切片资源管理方法、装置、电子设备及存储介质
Bernardos Cano et al. An architecture for software defined wireless networking

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14895911

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2014895911

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2014895911

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 15322172

Country of ref document: US