WO2017036288A1 - 一种网元升级方法及设备 - Google Patents

一种网元升级方法及设备 Download PDF

Info

Publication number
WO2017036288A1
WO2017036288A1 PCT/CN2016/094416 CN2016094416W WO2017036288A1 WO 2017036288 A1 WO2017036288 A1 WO 2017036288A1 CN 2016094416 W CN2016094416 W CN 2016094416W WO 2017036288 A1 WO2017036288 A1 WO 2017036288A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
message
slb
service
service message
Prior art date
Application number
PCT/CN2016/094416
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 EP16840717.9A priority Critical patent/EP3337097B1/en
Publication of WO2017036288A1 publication Critical patent/WO2017036288A1/zh
Priority to US15/909,587 priority patent/US10601656B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0813Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4641Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4641Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H04L12/4675Dynamic sharing of VLAN information amongst network nodes
    • H04L12/4683Dynamic sharing of VLAN information amongst network nodes characterized by the protocol used
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/085Retrieval of network configuration; Tracking network configuration history
    • H04L41/0859Retrieval of network configuration; Tracking network configuration history by keeping history of different configuration generations or by rolling back to previous configuration versions
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0894Policy-based network configuration management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0895Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/50Testing arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1001Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45562Creating, deleting, cloning virtual machine instances
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/455Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533Hypervisors; Virtual machine monitors
    • G06F9/45558Hypervisor-specific management and integration aspects
    • G06F2009/45595Network integration; Enabling network access in virtual machine instances

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a network element upgrade method and device.
  • the core network needs to be connected with various surrounding networks and devices. All network services need to be controlled or transited through the core network elements, and the network services provided by them are irreplaceable. Therefore, when the network element of the core network needs to be upgraded, not only the system upgrade of the network service is required, but also the network service needs to be processed normally, that is, the core network is required to be upgraded without loss, and the service is uninterrupted during the system upgrade, or only Can tolerate short-lived terminals (such as within 10s).
  • the core network element is generally upgraded in a non-destructive manner by dividing the process in the network element into two planes.
  • the standby plane is upgraded to the new version.
  • the standby plane does not process the service.
  • the original active plane is switched, and all services are switched from the original primary plane to the original plane (new active plane). Then upgrade the original main plane.
  • the upgrade process only when the service is switched from the primary plane to the new version of the standby plane will result in a very short service interruption (the theoretical service interruption time is about 10s), thus achieving a non-destructive upgrade.
  • the inventor has found that the above-mentioned non-destructive upgrade method has the following problems: the configuration and networking of the existing network devices vary widely, and the actual live network scenario cannot be simulated during the development phase. Many problems of the new version of the network element are only on the day of the upgrade. In order to discover, therefore, when upgrading, the network element switches all services to the new version, and once the new version is upgraded, it will affect the overall situation.
  • the present invention provides a network element upgrade method and device to solve the problem that the network element will switch all the services to the new version after the existing upgrade process, and once the new version is upgraded, the problem will be affected.
  • an embodiment of the present invention provides a network element upgrade method, where the method includes:
  • the network load balancer SLB receives the distribution policy delivered by the network element management system EMS;
  • the SLB forwards, according to the distribution policy, a part of the service messages sent by the external network element to the first network element, and forwards the remaining part of the service message to the second network element;
  • the SLB forwards, to the foregoing, all the multiple received service messages sent by the external network element according to the distribution policy.
  • the distribution policy is used to control a proportion of service messages forwarded to the first network element and the second network element; the second network element has the same configuration attribute and connection configuration as the first network element.
  • the second network element and the first network element are in different virtual local area networks, and the version of the second network element is not lower than the first network element.
  • the service message includes: a user identifier of a user that initiates a service message; and the SLB sends the received external network element according to the distribution policy. And forwarding a part of the service message to the first network element, and forwarding the remaining part of the service message to the second network element, specifically:
  • the SLB determines that the message type of the service message is a session initiation protocol SIP message, forwarding the service message according to the user identifier included in the SIP message, and the distribution identifier and the whitelist in the distribution policy.
  • the distribution identifier is used to: forward all the multiple service messages received by the SLB to the first network element, or All the service messages received by the SLB are forwarded to the second network element, or are not determined to forward the plurality of service messages received by the SLB to which of the first network element and the second network element.
  • the whitelist is used to store at least one user identifier;
  • the SLB determines that the service message is an IP link message, according to the quintuple information included in the IP link message, and the quintuple attribute of the logical link in the distribution policy and the virtual local area network identification VLAN ID Corresponding relationship, forwarding the service message to the first network element or the second network element;
  • the quintuple information includes: an IP address of the external network element, a port number of the external network element, an IP address of the first network element, a port number of the first network element, and a transmission protocol.
  • Type the quintuple attribute of the logical link includes: a source IP address, a source port number, a destination IP address, a destination port number, and a transport protocol type.
  • the SLB is configured according to a user identifier included in the SIP message, and a distribution identifier and a whitelist in the distribution policy.
  • the forwarding, the forwarding of the service message to the second network element or the first network element specifically includes:
  • the distribution identifier indicates that the plurality of service messages received by the SLB are not forwarded to the second network element and the network element of the first network element, querying the whitelist list, if If the user identifier of the service message is included in the whitelist, the service message is forwarded to the second network element; if the user identifier of the service message is not included in the whitelist, Forwarding the service message to the first network element;
  • the service message is forwarded to the first network element.
  • the SLB is based on The quintuple information included in the IP link message, and the correspondence between the quintuple attribute of the logical link and the virtual local area network identifier VLAN ID in the distribution policy, forwarding the service message to the second network element Or the first network element specifically includes:
  • a first virtual local area network identifier VLAN ID corresponding to the service message where the first VLAN ID is used to identify the first virtual a local area network, where the first virtual local area network includes: the first network element or the second network element;
  • the EMS is received at the SLB Before the delivery policy is delivered, the method further includes:
  • the SLB sends a synchronization request message to the first network element, where the synchronization request message is used to request to obtain interface information of the first network element, where the interface information of the first network element includes: The IP address and port number of the SIP server of the network element, and the configuration information of the logical link between the first network element and the first network element;
  • the SLB receives and stores the interface information of the first network element, and sets an external interface attribute of the SLB according to the received interface information of the first network element, where the interface attribute includes: an IP address and a port. number;
  • the SLB determines that the message type of each of the plurality of service messages that are received includes:
  • the method further includes:
  • the SLB receives the first service message sent by the first network element or the second network element, the source port number in the first service message is modified, and the modified source port number is modified.
  • Corresponding relationship between the source port number and the virtual local area network identifier VLAN ID of the network element that sends the first service message is recorded in the first relationship table;
  • a response message including: a destination port number, where the destination port number is: the modified source port number;
  • the first service message is a non-IP link message, and includes: a source IP address, a source port number, a destination IP address, and a destination port number.
  • the implementation may be implemented by combining any one of the first aspect to the fifth implementation manner of the first aspect, where the preset condition is one or more of the following Happening:
  • the success rate of the test case of all service messages on the second network element is greater than or equal to a preset threshold.
  • the embodiment of the present invention provides a network element upgrade method, which is applied to a network element management system (EMS), and includes:
  • the EMS creates a second network element, where the second network element is the same as the configuration attribute and the connection configuration of the first network element, and the second network element and the first network element are in different virtual local area network identification VLANs. Within the ID, and the version of the second network element is not lower than the first network element;
  • the SLB Sending, by the EMS, a distribution policy to the SLB, so that the SLB, according to the distribution policy, will receive a message type of each of the plurality of service messages; and when the service message on the second network element After the processing result meets the preset condition, the SLB forwards all the multiple received service messages sent by the external network element to the second network element according to the distribution policy.
  • the creating, by the EMS, the second network element specifically includes:
  • the EMS commands the VIM to create a virtual machine of the first network element
  • the EMS embeds the first network element virtual machine image file into the created virtual machine to form the second network element.
  • the method further includes:
  • the EMS reduces the virtual machine resources of the first network element according to the reduced number of service messages processed on the first network element;
  • the EMS After the SLB forwards the multiple received service messages to the second network element, the EMS revokes the first network element and releases the virtual machine resources in the first network element.
  • the processing result of the service message on the second network element is satisfied.
  • the preset condition includes: all the service messages on the second network element are successfully called; or
  • the success rate of the test case of all service messages on the second network element is greater than or equal to a preset threshold.
  • an embodiment of the present invention provides a network load balancer SLB, including:
  • a receiving unit configured to receive a distribution policy delivered by the EMS of the network element management system
  • a distribution unit configured to forward, according to the distribution policy received by the receiving unit, a part of the received service messages sent by the external network element to the first network element, and forward the remaining part of the service message to the Second network element;
  • the distribution policy is used to control a proportion of service messages forwarded to the first network element and the second network element; the second network element has the same configuration attribute and connection configuration as the first network element The second network element and the first network element The version of the second network element is not lower than the first network element.
  • the service message includes: a user identifier of a user who initiates a service message; and the distribution unit is specifically configured to:
  • the message type of the service message is a session initiation protocol SIP message, forwarding the service message to the user identifier according to the user identifier included in the SIP message, and a distribution identifier and a whitelist in the distribution policy.
  • a first network element or the second network element where the distribution identifier is used to: forward all the multiple service messages received by the SLB to the first network element, or receive the SLB All of the plurality of service messages are forwarded to the second network element, or are inactive to forward the plurality of service messages received by the SLB to which of the first network element and the second network element;
  • the whitelist list is used to store at least one user identifier;
  • the service message is an IP link message, according to the quintuple information included in the IP link message, and the correspondence between the quintuple attribute of the logical link and the virtual local area network identification VLAN ID in the distribution policy Transmitting the service message to the first network element or the second network element;
  • the quintuple information includes: an IP address of the external network element, a port number of the external network element, an IP address of the first network element, a port number of the first network element, and a transmission protocol.
  • Type the quintuple attribute of the logical link includes: a source IP address, a source port number, a destination IP address, a destination port number, and a transport protocol type.
  • the distribution unit in combination with the first implementation manner of the third aspect, is specifically configured to:
  • the distribution identifier indicates that the plurality of service messages received by the SLB are not forwarded to the second network element and the network element of the first network element, querying the whitelist list, if If the user identifier of the service message is included in the whitelist, the service message is forwarded to the second network element; if the user identifier of the service message is not included in the whitelist, Forwarding the service message to the first network element;
  • the service message is forwarded to the first network element.
  • the distribution unit in combination with the first implementation manner of the third aspect, is specifically configured to:
  • a first virtual local area network identifier VLAN ID corresponding to the service message where the first VLAN ID is used to identify the first virtual a local area network, where the first virtual local area network includes: the first network element or the second network element;
  • the SLB further includes:
  • the interface information of the first network element includes: an IP address and a port number of the SIP server of the first network element, and configuration information of a logical link that the first network element communicates with the first network element;
  • the receiving unit is further configured to receive and store interface information sent by the first network element
  • the distribution unit is configured to set an external interface attribute of the SLB according to the received interface information of the first network element, where the interface attribute includes: an IP address and a port number;
  • the receiving unit is further configured to receive the first service message sent by the first network element or the second network element;
  • the distribution unit is further configured to: modify the source port number in the first service message, and modify the source port number, the source port number, and the network element that sends the first service message Corresponding relationship between the VLAN IDs of the virtual local area network identifiers is recorded in the first relationship table;
  • a response message including: a destination port number, where the destination port number is: the modified source port number;
  • the first service message is a non-IP link message, and includes: a source IP address, a source port number, a destination IP address, and a destination port number.
  • the implementation may be implemented by combining any one of the third aspect to the fifth implementation manner of the third aspect, where the preset condition is one or more of the following Happening:
  • the success rate of the test case of all service messages on the second network element is greater than or equal to a preset threshold.
  • an embodiment of the present invention provides a network element management system (EMS), including:
  • a creating unit configured to create a second network element, where the second network element is the same as the configuration attribute and the connection configuration of the first network element, where the second network element and the first network element are in different virtual local area networks
  • the version of the second network element is not lower than the first network element
  • a sending unit configured to send a distribution policy to the SLB, so that the SLB, according to the distribution policy, will receive a message type of each of the plurality of service messages; and when the service on the second network element After the processing result of the message meets the preset condition, the SLB forwards all the multiple received service messages sent by the external network element to the second network element according to the distribution policy.
  • the creating unit is specifically configured to:
  • the first network element virtual machine image file is embedded in the created virtual machine to form the second network element.
  • the creating unit is further configured to:
  • the first network element is revoked, and the virtual machine resources in the first network element are released.
  • the processing result of the service message on the second network element is satisfied.
  • the preset condition includes: all the service messages on the second network element are successfully called; or
  • the success rate of the test case of all service messages on the second network element is greater than or equal to a preset threshold.
  • the embodiment of the present invention provides a method for upgrading a network element, including: a SLB receiving a distribution policy delivered by an EMS, and receiving, according to the distribution policy, part of a plurality of service messages sent by an external network element.
  • the service message is forwarded to the first network element, and the remaining part of the service message is forwarded to the second network element.
  • the SLB is configured according to the distribution policy. All the plurality of service messages sent by the external network element that are subsequently received are forwarded to the second network element. In this way, during the NE upgrade process, the SLB first forwards some of the messages in the service message to the second network element for trial operation.
  • the subsequent multiple services are received. All the messages are forwarded to the second network element, which reduces the risk of the overall service being damaged due to the switchover of all services to the new network element during the NE upgrade process.
  • the existing network element system architecture is not changed. Only a new SLB module is added outside the network element to shield the internal structure of the network element. By adding an instance of the network element internally, and controlling the message flow between the old and new network elements. The switching ensures that the system reliability is not reduced during the upgrade and meets the high reliability requirements of the carrier class.
  • FIG. 1 is a schematic diagram of an existing NFV architecture
  • FIG. 2 is a schematic diagram of a system architecture according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of a network upgrade method according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a distribution policy according to an embodiment of the present invention.
  • FIG. 5 is a flowchart of a network upgrade method according to an embodiment of the present invention.
  • FIG. 6 is a structural diagram of an SLB according to an embodiment of the present invention.
  • FIG. 6A is a structural diagram of an SLB according to an embodiment of the present invention.
  • FIG. 7 is a structural diagram of an EMS according to an embodiment of the present invention.
  • FIG. 8 is a structural diagram of an SLB according to an embodiment of the present invention.
  • FIG. 9 is a structural diagram of an EMS according to an embodiment of the present invention.
  • the network element upgrade method provided by the embodiment of the present invention can be applied not only to the scenario of upgrading the network element of the cloud computing platform or the non-cloud computing platform, but also to the network element of the cloud computing platform or the non-cloud computing platform.
  • the scenario of the cutover and the disaster recovery is not limited in the embodiment of the present invention.
  • the present invention is only described by the scenario in which the network element is upgraded on the cloud computing platform.
  • the implementation of the network element cutover and disaster recovery switching scenario is described.
  • the method is the same as the method for upgrading the network element described in the embodiment of the present invention, and details are not described herein again.
  • the NFV architecture may include: an operations support system (OSS), at least one element management system (EMS), and the following virtual function nodes: virtualized network functions (virtualized network Function, VNF), NFV infrastructure (NFVI), NFV Management and Orchestration (NFV MANO).
  • OSS represents the operator's respective operational support equipment, and is responsible for network management services such as alarm, traffic statistics, configuration management, network planning, etc. of different domains of the operator (such as fixed network domain or mobile network domain).
  • EMS must provide five basic functional errors, configuration, accounting, performance, and security (Faul t, Configuration, Accounting, Performance and Security, FCAPS) for network management.
  • FCAPS Configuration, Accounting, Performance and Security
  • EMS usually has the following functions: topology management, system backup and Recovery, system monitoring, log management, northbound interface, command terminal.
  • VNF For the virtualized function device of the physical network element in the core network, the NFVI virtualizes the hardware resource to be a virtual resource that can be dynamically requested to be provided to the VNF, so that the VNF has the same function as the physical network element, and the VNF is performed by the EMS.
  • NFV MANO plays an important role in overall control and coordination in the NFV architecture, including: NFV Orchestrator (NFVO), Virtual Network Function Management (VNF Manager, VNFM), and Virtual Infrastructure Management ( Virtualised Infrastructure Manager (VIM) three parts, when there are software and hardware resources, NFV MANO will coordinate, verify and authorize related resource requests, and manage the life cycle of VNF, such as instantiation, flexible organization, update, Query, terminate VNF, etc.
  • NFV MANO is also responsible for policy management of network services, collection and transfer of related events, and configuration of infrastructure-related resources, such as adding resources to virtual machines, improving energy efficiency, and resources. Return and so on.
  • the basic principle of the embodiment of the present invention is to add a network load balancer (SLB) to the NFV architecture, where the SLB has the following functions: responsible for transmitting the signaling message of the external network to the virtualization of the physical network element.
  • the function device VNF1 or VNF1', and the request message sent by VNF1 and VNF1' to the outside of the network are mapped by Network Address Translate (NAT) to ensure that the response message can be returned to the message requesting end.
  • NAT Network Address Translate
  • the VNF1 virtualized by the physical NE is mirrored to form VNF1' as the standby virtual NE, and the system is upgraded to VNF1'. Then, the SLB receives the packet according to the default distribution policy.
  • FIG. 2 is a schematic diagram of a system architecture according to an embodiment of the present invention.
  • an SLB is set between VNF1 and VNF1' after the other network element and the physical network element are virtualized, and the SLB and the EMS are provided.
  • the EMS sends a distribution policy to the SLB, and controls the service message sent by the SLB to the VNF1 or VNF1'.
  • FIG. 3 is a flowchart of a method for upgrading a network element according to an embodiment of the present invention. As shown in FIG. 3, the method may include:
  • Step 101 The SLB receives the distribution policy delivered by the EMS of the network element management system.
  • the distribution policy is configured by the administrator to be sent to the SLB by using the EMS, and may be used to: control the SLB to forward the multiple service messages received by the SLB to the first network element and the second network element. proportion.
  • Step 102 The SLB forwards a part of the received service messages sent by the external network element to the first network element according to the distribution policy, and forwards the remaining part of the service message to the second network element.
  • the multiple service messages received by the SLB are: the external network element receives and prepares to send to the first network element.
  • the plurality of service messages sent by the at least one user may include M service messages, where M is an integer greater than 1, and each service message includes: a user identifier of a user who initiates the service message.
  • the external network element and the first network element may be virtual network elements; under the network element upgrade of the non-cloud computing platform, the external network element and the first network element may be Physical network element.
  • the second network element may be referred to as a backup network element of the first network element, and is automatically generated by the EMS, and has the same configuration attribute and connection attribute as the first network element, and the second network element and
  • the first network element is in a different local area network, and is isolated by a virtual local area network (VLAN) or a virtual eXtensible LAN (VXLAN), and does not sense each other.
  • the second network element has the same configuration attribute and the connection attribute as the first network element. Therefore, in the network element lossless upgrade process, the service message to be sent to the first network element is not perceived. A network element switches to the second network element.
  • Step 103 After the processing result of the service message on the second network element meets the preset condition, the SLB forwards the multiple received multiple service messages sent by the external network element to the subsequent distribution policy according to the distribution policy.
  • the second network element After the processing result of the service message on the second network element meets the preset condition, the SLB forwards the multiple received multiple service messages sent by the external network element to the subsequent distribution policy according to the distribution policy. The second network element.
  • the preset conditions may be set as needed, and the comparison between the embodiments of the present invention is not limited, and the comparison of the embodiments of the present invention is not limited. If the processing result of the service message on the second network element meets the preset condition, it indicates that the second network element can perform the same service processing as the first network element, that is, all the service information of the first network element can be forwarded; If the processing result of the service message on the second network element does not meet the preset condition, it indicates that the processing capability of the second network element is still weak, and the service processing cannot be performed in the same manner as the first network element, that is, the service message of the first network element cannot be used. All forwarded.
  • the preset condition may be one or more of the following situations: the success of all service message calls on the second network element, and the success rate of test cases of all service messages on the second network element are greater than Equal to the preset threshold;
  • the successful call of all the service messages on the second network element indicates that the second network element can accurately receive the service message sent by the other network element; the test case is compiled by the technician and used for The program for testing whether the service message is successfully called may test the call of the service message on the second network element in the software environment; the preset threshold may be set as needed, and preferably, the white balance may be set to succeed. rate.
  • the system administrator monitors the running status of the multiple service messages on the second network element in real time, and if the preset condition is met, The second network element is upgraded normally. If the preset condition is not met, it indicates that there is a problem with the upgrade on the second network element, and it needs to be corrected.
  • the subsequent multiple service messages may also be: the external network element receives and prepares to send to the first network.
  • the foregoing step 102 may be repeatedly performed, and part of the service message is continuously forwarded to the second network element for trial operation, where each time forwarded to The number of the service messages of the second network element may be equal or may be in an increasing trend.
  • the comparison of the embodiments of the present invention is not limited.
  • the SLB first forwards some of the messages in the service message to the second network element for trial operation. After the operation on the second network element is normal, the subsequent multiple services are received. All the messages are forwarded to the second network element, which reduces the risk of the overall service being damaged due to the switchover of all services to the new network element during the NE upgrade process.
  • the service message sent by the user may be of a plurality of types, such as: a Session Initiation Protocol (SIP) message, or an Internet Protocol (IP) link message.
  • SIP Session Initiation Protocol
  • IP Internet Protocol
  • different distribution policies may be correspondingly configured for different types of service messages, that is, the distribution policies delivered by the EMS need to include: different service messages and policies for distributing the service messages.
  • the SLB forwards a part of the service messages sent by the received external network element to the first network element according to the distribution policy, and forwards the remaining part of the service message to the second network. Yuan detailed introduction:
  • the SLB determines that the message type of the service message is a session initiation protocol SIP message, forwarding the service message according to the user identifier included in the SIP message, and the distribution identifier and the whitelist in the distribution policy.
  • the distribution identifier is used to: forward all the multiple service messages received by the SLB to the first network element, or All the service messages received by the SLB are forwarded to the second network element, or are not determined to forward the plurality of service messages received by the SLB to which of the first network element and the second network element.
  • the whitelist is used to store at least one user identifier;
  • the SLB determines that the service message is an IP link message, according to the quintuple information included in the IP link message, and the quintuple attribute of the logical link in the distribution policy and the virtual local area network identification VLAN ID Corresponding relationship, forwarding the service message to the first network element or the second network element;
  • the quintuple information includes: an IP address of the external network element, a port number of the external network element, an IP address of the first network element, a port number of the first network element, and a transmission protocol.
  • Type the quintuple attribute of the logical link includes: a source IP address, a source port number, a destination IP address, a destination port number, and a transport protocol type;
  • the SLB determines that the service message is not a SIP message and an IP link message, forwarding the service message to the second network element.
  • the method may further include:
  • the SLB sends a synchronization request message to the first network element, where the synchronization request message is used to request to obtain interface information of the first network element, where the interface information of the first network element includes: The IP address and port number of the SIP server of the network element, and the configuration information of the logical link between the first network element and the first network element;
  • the SLB receives and stores the interface information sent by the first network element, and sets an external interface attribute of the SLB according to the received interface information of the first network element, where the interface attribute includes: an IP address and The port number;
  • the SLB determining the message type of the service message may specifically include:
  • the interface information included in the service message is matched with the interface message of the first network element, and the message type of the service message is determined.
  • the SIP message has the following characteristics: the IP address and the port number of the SIP server are included, wherein the port number is agreed by the communication parties in advance and is fixed. For example, the default port number disclosed by the industry is 5060.
  • the IP link message has the following characteristics: the source and destination terminals that communicate with each other communicate with a fixed IP address + port number, and know each other's IP address and port number, and adopt a fixed transmission protocol type, wherein The transmission protocol type may be: SCTP, TCP, UDP, etc., so that the interface information included in the service message is matched with the interface message of the first network element, and the message type of the service message is specifically determined to include:
  • the service message may be determined to be a SIP message.
  • the service message may be determined to be an IP link message.
  • the SLB After receiving the interface information sent by the first network element, the SLB compares the timestamp of receiving the interface information with the timestamp of the locally cached interface information, if the interface is obtained from the first network element. The timestamp of the information is later than the timestamp of the locally stored information, and the locally stored interface information is replaced with the newly acquired interface information.
  • the first network element when the user sends a configuration command to the first network element to add or modify the external interface of the first network element, the first network element also sends a change notification message to the SLB in real time, and the SLB updates the local interface after receiving the change notification message.
  • Information and information such as distribution policies.
  • the "source” and the “destination” in the source IP address, the source port number, the destination IP address, and the destination port number are determined according to the initiation and reception of the service message, usually
  • the IP address and port number of the end of the service message are called the source IP address and the port number.
  • the IP address and port number of the end that receives the service message are called the destination IP address and the destination port number.
  • the SIP forwards the service message to the second network element according to a user identifier included in the SIP message, and a distribution identifier and a whitelist in the distribution policy.
  • the first network element may include:
  • Step 1021 The SLB queries the distribution identifier. If it is determined that the distribution identifier indicates that the plurality of service messages received by the SLB are forwarded to the second network element and the network element of the first network element, Go to step 1022;
  • step 1023 is performed;
  • step 1024 is performed.
  • Step 1022 Query the whitelist list, determine whether the user identifier of the service message is included in the whitelist, and if the user identifier of the service message is included in the whitelist, perform step 1024; If the user identifier of the service message is not included in the whitelist, step 1025 is performed.
  • Step 1023 Forward the service message to the second network element.
  • Step 1024 Forward the service message to the first network element.
  • the distribution identifier may be a numeric symbol or other form of the symbol; the comparison of the embodiments of the present invention is not limited.
  • the distribution identifier “0” may be used to: forward all the plurality of service messages received by the SLB to the second network element and the network in the first network element, and use the distribution identifier “1”. Representing that all the service messages received by the SLB are forwarded to the second network element, and the distribution identifier “2” is used to: forward all the multiple service messages received by the SLB to the first network yuan.
  • the following table 1 includes a distribution identifier and a whitelist list.
  • the service identifier included in the service message is user 2, it is determined to forward the service message to the second network element; if the service message includes the user identifier as user 4, Then, it is determined that the service message is forwarded to the first network element.
  • the distribution identifier included in the distribution policy may be set to be used to indicate that the service message is forwarded to the identification information of the second network element, so that the SLB is configured according to the distribution policy. All subsequent received multiple service messages are distributed to the second network element.
  • the SLB forwards the service message according to the quintuple information included in the IP link message and the correspondence between the quintuple attribute of the logical link and the virtual local area network identifier VLAN ID in the distribution policy.
  • the second network element or the first network element may include:
  • a first virtual local area network identifier VLAN ID corresponding to the service message where the first VLAN ID is used to identify the first virtual a local area network, where the first virtual local area network includes: the first network element or the second network element;
  • the mapping between the logical link and the VLAN ID of the virtual local area network is used to control the number of logical links that are forwarded to the second network element, and may be set as required.
  • a user specifies a user whitelist on the EMS during the upgrade process
  • the system compares the number of whitelisted users with the total number of users in the site, and the total number of logical links that the first network element connects to the neighboring NEs. And converting the number of logical links into the second network element that needs to be distributed to the new version, and transmitting the distribution policy modification component of the corresponding number of logical links to the second network element.
  • the first network element and the surrounding network element are connected to each other for a total of four links, and if it is desired to distribute the calls of 2,500 users to the new version of the second network element.
  • the SLB forwards the service message of one of the logical links to the second network element, and the service messages of the remaining three logical links are still forwarded to the first network element.
  • the identifier of the virtual local area network where the first network element is located is: VLAN 1
  • the identifier of the virtual local area network where the second network element is located is: VLAN 2
  • the IP address is: 20.20.10.2/24
  • the four ports are included.
  • the port numbers are: 01, 02, 03, and 04; the IP address of the first NE is 10.10.1.1/24, and the port numbers of the four ports are: 0A, 0B, 0C, 0D, and the first
  • the type of the transmission protocol between the network elements is: TCP; the following four logical links for transmitting service messages can be formed between the external network element and the first network element: 20.20.10.2/24, 01, 10.10.1.1/24, 0A, TCP; 20.20.10.2/24, 02, 10.10.1.1/24, 0B, TCP; 20.20.10.2/24, 03, 10.10.1.1/24, 0C, TCP; 20.20.10.2/24, 04, 10.10.
  • the second network element may also form four logical links as described above. At this time, if the service message sent on the logical link 20.20.10.2/24, 04, 10.10.1.1/24, and 0D is forwarded to the second network element, the partial service message sent to the first network element is switched to For the second network element, the correspondence shown in Table 2 below needs to be set in advance.
  • the service message is forwarded to the first network. If the quintuple attribute included in the received service message is: 20.20.10.2/24, 04, 10.10.1.1/24, 0D, TCP, according to Table 2, the service message is forwarded to the second network element. .
  • all the logical links may be set to correspond to the identifier VLAN ID of the virtual local area network where the second network element is located, so that the SLB forwards all subsequent received IP link messages to The second network element.
  • the embodiment of the present invention provides that the SLB can also forward the service message sent by the internal network element of the system to the external network element, and return the original path to the sending end after receiving the response message sent by the external network element, as follows:
  • the SLB modifies the source port number in the first service message, and the modified The correspondence between the source port number and the virtual port identifier VLAN ID of the source port number and the network element that sends the first service message is recorded in the first relationship table;
  • a response message including: a destination port number, where the destination port number is: the modified source port number;
  • the first service message is a non-IP link message, and includes: a source IP address, a source port number, a destination IP address, and a destination port number.
  • the IP link message can be returned to the original path of the response message without performing port modification or port mapping. Therefore, the present invention implements
  • the first service message is only a non-IP link message, and may include: a SIP message, and other messages except SIP and IP link messages.
  • the first network element is in the VLAN 1 and the second network element is in the VLAN 2, and the two have the same port 1002.
  • the message that the source port of the first network element is 1002 can be modified to the port number 31002.
  • the message that the source port is 1002 sent by the second network element is modified to be the port number 21002, and is recorded in Table 3.
  • the SLB receives the message with the destination port number 21002, according to Table 3, it will be known: The message is sent to the port 1002 of the second network element in the VLAN 2. If the SLB receives the message with the destination port number 31002, the message is sent to the port 1002 of the first network element in the VLAN 1 according to Table 3. on.
  • Modified port number Modify the port number VLAN ID 21002 1002 VLAN2 31002 1002 VLAN1
  • the embodiment of the present invention provides a method for upgrading a network element, including: a SLB receiving a distribution policy delivered by an EMS, and receiving, according to the distribution policy, part of a plurality of service messages sent by an external network element.
  • the service message is forwarded to the first network element, and the remaining part of the service message is forwarded to the second network element.
  • the SLB is configured according to the distribution policy. All the plurality of service messages sent by the external network element that are subsequently received are forwarded to the second network element. In this way, during the NE upgrade process, the SLB first forwards some of the messages in the service message to the second network element for trial operation.
  • the subsequent multiple services are received. All the messages are forwarded to the second network element, which reduces the risk of the overall service being damaged due to the switchover of all services to the new network element during the NE upgrade process.
  • the existing network element system architecture is not changed. Only a new SLB module is added outside the network element to shield the internal structure of the network element. By adding an instance of the network element internally, and controlling the message flow between the old and new network elements. The switching ensures that the system reliability is not reduced during the upgrade and meets the high reliability requirements of the carrier class.
  • FIG. 5 is a flowchart of another method for upgrading a network element according to an embodiment of the present invention. As shown in FIG. 5, the method may include the following steps:
  • Step 201 The EMS creates a second network element.
  • the second network element is the same as the configuration attribute and the connection configuration of the first network element, and the second network element and the first network element are in different virtual local area networks, and are isolated by using VLANs to avoid IP conflicts. And the version of the second network element is not lower than the first network element. At the same time, the entire change is not perceived in the process of creating the second network element. It is also unnecessary to add interface data to the second network element.
  • the creating, by the EMS, the second network element may include:
  • the EMS commands the VIM to create a virtual machine of the first network element
  • the EMS embeds the first network element virtual machine image file into the created virtual machine to form the second network element.
  • Step 202 The EMS sends a distribution policy to the SLB, and the SLB forwards some of the received service messages sent by the external network element to the first network element according to the distribution policy, and the remaining part of the service is sent.
  • the message is forwarded to the second network element; and after the processing result of the service message on the second network element meets the preset condition, the SLB sends the subsequently received external network element according to the distribution policy. All service messages are forwarded to the second network element.
  • the distribution policy is configured by the administrator to be sent to the SLB by using the EMS, and may be used to: control the SLB to forward the multiple service messages received by the SLB to the first network element and the second network element. proportion.
  • the newly created second network element is a minimum function set of the first network element, and when the service message distribution to the second network element is gradually increased, the second The NE is automatically activated through the elastic expansion function.
  • the capacity of the first network element is automatically reduced due to the decrease of the traffic volume. Therefore, the virtual machine that is retracted by the first network element can be moved to the second network element for use. Consumption of infrastructure resources; as follows:
  • the EMS reduces the virtual machine resources of the first network element according to the reduced number of service messages processed on the first network element;
  • the EMS After the SLB forwards the received multiple service messages to the second network element, the EMS revokes the first network element and releases the virtual machine resources in the first network element.
  • the embodiment of the present invention provides a network element upgrade method, where the EMS creates a second network element, where the second network element has the same configuration attribute and connection configuration as the first network element, and the second The network element and the first network element are in different virtual local area networks, and the version of the second network element is not lower than the first network element; and the distribution policy is sent to the SLB, so that the SLB is distributed according to the a policy, the message type of each of the plurality of service messages to be received; and after the processing result of the service message on the second network element meets a preset condition, the SLB according to the distribution policy The subsequently received multiple service messages sent by the external network element are all forwarded to the second network element.
  • the SLB first forwards some of the messages in the service message to the second network element for trial operation. After the operation on the second network element is normal, the subsequent multiple services are received. All the messages are forwarded to the second network element, which reduces the risk of the overall service being damaged due to the switchover of all services to the new network element during the NE upgrade process.
  • FIG. 6 is a structural diagram of a network load balancer SLB60 according to an embodiment of the present invention. As shown in FIG. 6, the SLB 60 may include:
  • the receiving unit 601 is configured to receive a distribution policy delivered by the network element management system EMS.
  • the distribution policy is configured by the administrator to be sent to the SLB by using the EMS, and may be used to: control the SLB to forward the multiple service messages received by the SLB to the first network element and the second network element. proportion.
  • the distribution unit 602 is configured to forward, according to the distribution policy, a part of the received service messages sent by the external network element to the first network element, and forward the remaining part of the service message to the second network element. ;
  • the multiple service messages received by the receiving unit 601 are: multiple service messages sent by the at least one user that the external network element receives and is ready to send to the first network element, for example, may include M service messages.
  • M is an integer greater than 1, and each service message includes: a user identifier of a user who initiates the service message.
  • the external network element and the first network element may be virtual network elements; under the network element upgrade of the non-cloud computing platform, the external network element and the first network element may be Physical network element.
  • the second network element may be referred to as a backup network element of the first network element, and is automatically generated by the EMS, and has the same configuration attribute and connection attribute as the first network element, and the second network element and
  • the first network element is in a different local area network, and is isolated by a virtual local area network (VLAN) or a virtual eXtensible LAN (VXLAN), and does not sense each other.
  • the second network element has the same configuration attribute and the connection attribute as the first network element. Therefore, in the network element lossless upgrade process, the service message to be sent to the first network element is not perceived. A network element switches to the second network element.
  • the second network element may be referred to as a backup network element of the first network element, and is automatically generated by the EMS, and has the same configuration attribute and connection attribute as the first network element, and the second network element and The first network element is in a different local area network, and is isolated by a virtual local area network (VLAN), and does not sense each other.
  • the second network element has the same configuration attribute and the connection attribute as the first network element. Therefore, in the network element lossless upgrade process, the service message to be sent to the first network element is not perceived. A network element switches to the second network element.
  • the preset conditions may be set as needed, and the comparison between the embodiments of the present invention is not limited, and the comparison of the embodiments of the present invention is not limited. If the processing result of the service message on the second network element meets the preset condition, it indicates that the second network element can perform the same service processing as the first network element, that is, all the service information of the first network element can be forwarded; If the processing result of the service message on the second network element does not meet the preset condition, it indicates that the processing capability of the second network element is still weak, and the service processing cannot be performed in the same manner as the first network element, that is, the service message of the first network element cannot be used. All forwarded.
  • the system administrator monitors the running status of the multiple service messages on the second network element in real time, and if the preset condition is met, The second network element is upgraded normally. If the preset condition is not met, it indicates that there is a problem with the upgrade on the second network element, and it needs to be corrected.
  • part of the service message may be continuously forwarded to the second network element for trial operation, where the service is forwarded to the second network element each time.
  • the number of the messages may be equal or may be in an increasing trend. The comparison of the embodiments of the present invention is not limited.
  • the service message sent by the user may be of a plurality of types, such as: a Session Initiation Protocol (SIP) message, or an Internet Protocol (IP) link message.
  • SIP Session Initiation Protocol
  • IP Internet Protocol
  • different distribution policies may be correspondingly configured for different types of service messages, that is, the distribution policies delivered by the EMS need to include: different service messages and policies for distributing the service messages.
  • the distribution unit is specifically configured to:
  • the message type of the service message is a session initiation protocol SIP message, forwarding the service message to the user identifier according to the user identifier included in the SIP message, and a distribution identifier and a whitelist in the distribution policy.
  • a second network element or the first network element where the distribution identifier is used to: forward all the multiple service messages received by the SLB to the first network element, or receive the SLB All of the plurality of service messages are forwarded to the second network element, or are inactive to forward the plurality of service messages received by the SLB to which of the first network element and the second network element;
  • the whitelist list is used to store at least one user identifier;
  • the service message is an IP link message, according to the quintuple information included in the IP link message, and the correspondence between the quintuple attribute of the logical link and the virtual local area network identification VLAN ID in the distribution policy Forwarding the service message to the second network element or the first network element;
  • the quintuple information includes: an IP address of the external network element, a port number of the external network element, an IP address of the first network element, a port number of the first network element, and a transmission protocol.
  • Type the quintuple attribute of the logical link includes: a source IP address, a source port number, a destination IP address, a destination port number, and a transport protocol type;
  • the service message is not a SIP message and an IP link message, forwarding the service message to the second network element.
  • the SLB 60 may further include:
  • the sending unit 603 is configured to send a synchronization request message to the first network element before the receiving unit 601 receives all the multiple service messages received by the sent SLB, where the synchronization request message is used to request the acquisition
  • the interface information of the first network element where the interface information of the first network element includes: an IP address and a port number of the SIP server end of the first network element, and a communication between the first network element and the first network element Configuration information of the logical link;
  • the receiving unit 601 is further configured to receive and store interface information sent by the first network element.
  • the distribution unit is configured to set an external interface attribute of the SLB according to the received interface information of the first network element, where the interface attribute includes: an IP address and a port number; and the service message is included
  • the interface information is matched with the interface message sent by the first network element, and the message type of the service message is determined.
  • the receiving unit 601 After receiving the interface information sent by the first network element, the receiving unit 601 compares the timestamp of receiving the interface information with the timestamp of the locally cached interface information, if obtained from the first network element. The timestamp of the interface information is later than the timestamp of the locally stored information, and the locally stored interface information is replaced with the newly acquired interface information. At the same time, when the user sends a configuration command to the first network element to add or modify the external interface of the first network element, the first network element also sends a change notification message to the SLB in real time, and the SLB updates the local interface after receiving the change notification message. Information and information such as distribution policies.
  • distribution unit 602 is specifically configured to:
  • the distribution identifier is determined to be: if it is determined that the distribution identifier indicates that the plurality of service messages received by the SLB are forwarded to the second network element and the network element of the first network element, Querying the whitelist list, if the user identifier of the service message is included in the whitelist, forwarding the service message to the second network element; if the user identifier of the service message is not included in In the whitelist, forwarding the service message to the first network element;
  • the service message is forwarded to the first network element.
  • the distribution identifier may be a numeric symbol or other form of the symbol; the comparison of the embodiments of the present invention is not limited.
  • the distribution identifier “0” may be used to: forward all the plurality of service messages received by the SLB to the second network element and the network in the first network element, and use the distribution identifier “1”. Representing that all the service messages received by the SLB are forwarded to the second network element, and the distribution identifier “2” is used to: forward all the multiple service messages received by the SLB to the first network yuan.
  • distribution unit 602 is specifically configured to:
  • a first virtual local area network identifier VLAN ID corresponding to the service message where the first VLAN ID is used to identify the first virtual a local area network, where the first virtual local area network includes: the first network element or the second network element;
  • the mapping between the logical link and the VLAN ID of the virtual local area network is used to control the number of logical links that are forwarded to the second network element, and may be set as required.
  • a user specifies a user whitelist on the EMS during the upgrade process
  • the system compares the number of whitelisted users with the total number of users in the site, and the total number of logical links that the first network element connects to the neighboring NEs. And converting the number of logical links into the second network element that needs to be distributed to the new version, and transmitting the distribution policy modification component of the corresponding number of logical links to the second network element.
  • the first network element and the surrounding network element are connected to each other for a total of four links, and if it is desired to distribute the calls of 2,500 users to the new version of the second network element.
  • the SLB forwards the service message of one of the logical links to the second network element, and the service messages of the remaining three logical links are still forwarded to the first network element.
  • the embodiment of the present invention provides that, in order to forward the service message sent by the internal network element of the system to the external network element, after receiving the response message sent by the external network element, the original path is returned to the sending end, and the receiving unit 601 further Used for:
  • the distribution unit 602 is further configured to modify the source port number in the first service message, and modify the source port number, the source port number, and the network element that sends the first service message.
  • the mapping relationship between the VLAN IDs of the virtual local area network identifiers is recorded in the first relationship table.
  • the receiving unit 601 is further configured to receive a response message that is sent by the external network element, where the response message includes: a destination port number, where the destination port number is: the modified source port number;
  • the distribution unit 602 is further configured to query, in the first relationship table, a port number corresponding to the destination port number and a virtual local area network identifier VLAN ID;
  • the first service message is a non-IP link message, and includes: a source IP address, a source port number, a destination IP address, and a destination port number.
  • the IP link message can be returned to the original path of the response message without performing port modification or port mapping. Therefore, the present invention implements
  • the first service message is only a non-IP link message, and may include: a SIP message, and other messages except SIP and IP link messages.
  • the first network element is in the VLAN 1 and the second network element is in the VLAN 2, and the two have the same port 1002.
  • the message that the source port of the first network element is 1002 can be modified to the port number 31002.
  • the message that the source port is 1002 sent by the second network element is modified to be the port number 21002, and is recorded in Table 3.
  • the SLB receives the message with the destination port number 21002, according to Table 3, it will be known: The message is sent to the port 1002 of the second network element in the VLAN 2. If the SLB receives the message with the destination port number 31002, the message is sent to the port 1002 of the first network element in the VLAN 1 according to Table 3. on.
  • an embodiment of the present invention provides an SLB, which receives a distribution policy delivered by an EMS, and forwards a part of the service messages sent by the external network element to the first one according to the distribution policy.
  • the network element forwards the remaining part of the service message to the second network element; after the processing result of the service message on the second network element meets the preset condition, the SLB receives the subsequent received according to the distribution policy.
  • a plurality of service messages sent by the external network element are all forwarded to the second network element. In this way, during the NE upgrade process, the SLB first forwards some of the messages in the service message to the second network element for trial operation. After the operation on the second network element is normal, the subsequent multiple services are received.
  • All the messages are forwarded to the second network element, which reduces the risk of the overall service being damaged due to the switchover of all services to the new network element during the NE upgrade process.
  • the existing network element system architecture is not changed. Only a new SLB module is added outside the network element to shield the internal structure of the network element. By adding an instance of the network element internally, and controlling the message flow between the old and new network elements. The switching ensures that the system reliability is not reduced during the upgrade and meets the high reliability requirements of the carrier class.
  • FIG. 7 is a structural diagram of a network element management system EMS 70 according to an embodiment of the present invention. As shown in FIG. 7, the EMS may include:
  • the creating unit 701 is configured to create a second network element, where the second network element is the same as the configuration attribute and the connection configuration of the first network element, and the second network element is different from the first network element.
  • the version of the second network element is not lower than the first network element.
  • the second network element is the same as the configuration attribute and the connection configuration of the first network element, and the second network element and the first network element are in different virtual local area networks, and are isolated by using VLANs to avoid IP conflicts. And the version of the second network element is not lower than the first network element. At the same time, the entire change is not perceived in the process of creating the second network element. It is also unnecessary to add interface data to the second network element.
  • the sending unit 702 is configured to send a distribution policy to the SLB, so that the SLB selects, according to the distribution policy, a message type of each of the plurality of service messages received; and when the second network element is After the processing result of the service message meets the preset condition, the SLB forwards all the multiple received service messages sent by the external network element to the second network element according to the distribution policy.
  • the distribution policy is configured by the administrator to be sent to the SLB by using the EMS, and may be used to: control the SLB to forward the multiple service messages received by the SLB to the first network element and the second network element. proportion.
  • creating unit 701 is specifically configured to:
  • the first network element virtual machine image file is embedded in the created virtual machine to form the second network element.
  • the newly created second network element is a minimum function set of the first network element, and when the service message distribution to the second network element is gradually increased, the second The NE expands the capacity automatically through the elastic expansion function.
  • the first network element automatically shrinks the capacity due to the decrease in traffic. In this way, the virtual machine that is retracted by the first network element can be moved to the second network element. In this way, the consumption of infrastructure resources can be reduced; the specific implementation is as follows:
  • the creating unit 701 is further configured to reduce virtual machine resources of the first network element according to the reduced number of service messages processed on the first network element;
  • the first network element is revoked, and the virtual machine resources in the first network element are released.
  • the embodiment of the present invention provides a network element upgrade EMS, which is configured to create a second network element, where the second network element and the first network element have the same configuration attribute and connection configuration, and the second network element is The first network element is in a different virtual local area network, and the version of the second network element is not lower than the first network element; a distribution policy is sent to the SLB, so that the SLB according to the distribution policy a message type of each of the plurality of service messages received; and after the processing result of the service message on the second network element meets a preset condition, the SLB receives the subsequent message according to the distribution policy. All of the plurality of service messages sent by the external network element are forwarded to the second network element.
  • the SLB first forwards some of the messages in the service message to the second network element for trial operation. After the operation on the second network element is normal, the subsequent multiple services are received. All the messages are forwarded to the second network element, which reduces the risk of the overall service being damaged due to the switchover of all services to the new network element during the NE upgrade process.
  • FIG. 8 is a structural diagram of a network load balancer SLB80 according to an embodiment of the present invention.
  • the SLB 80 may include: a communication unit 801, a processor 802, a memory 803, and at least one communication bus. 804, for implementing connection and mutual communication between these devices;
  • the communication unit 801 is configured to perform data transmission with an external network element.
  • the processor 802 may be a central processing unit (English: central processing unit, referred to as CPU).
  • the memory 803 may be a volatile memory (English: volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM); or non-volatile memory (English: non-volatile memory), for example Read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive, abbreviation :SSD); or a combination of the above types of memory and providing instructions and data to the processor 802.
  • volatile memory such as random access memory (English: random-access memory, abbreviation: RAM); or non-volatile memory (English: non-volatile memory), for example Read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive, abbreviation :SSD); or a combination
  • the communication unit 801 is configured to receive a distribution policy delivered by the network element management system EMS.
  • the distribution policy is configured by the administrator to be sent to the SLB by using the EMS, and may be used to: control the SLB to forward the multiple service messages received by the SLB to the first network element and the second network element. proportion.
  • the processor 802 is configured to forward, according to the distribution policy, a part of the received service messages sent by the external network element to the first network element, and forward the remaining part of the service message to the second network element. ;
  • the plurality of service messages received by the communication unit 801 are: a plurality of service messages sent by the at least one user that are received by the external network element and are ready to be sent to the first network element, for example, may include M service messages.
  • M is an integer greater than 1, and each service message includes: a user identifier of a user who initiates the service message.
  • the external network element and the first network element may be virtual network elements;
  • the external network element and the first network element may be physical network elements.
  • the second network element may be referred to as a backup network element of the first network element, and is automatically generated by the EMS, and has the same configuration attribute and connection attribute as the first network element, and the second network element and
  • the first network element is in a different local area network, and is isolated by a virtual local area network (VLAN) or a virtual eXtensible LAN (VXLAN), and does not sense each other.
  • the second network element has the same configuration attribute and the connection attribute as the first network element. Therefore, in the network element lossless upgrade process, the service message to be sent to the first network element is not perceived. A network element switches to the second network element.
  • the second network element may be referred to as a backup network element of the first network element, and is automatically generated by the EMS, and has the same configuration attribute and connection attribute as the first network element, and the second network element and The first network element is in a different local area network, and is isolated by a virtual local area network (VLAN), and does not sense each other.
  • the second network element has the same configuration attribute and the connection attribute as the first network element. Therefore, in the network element lossless upgrade process, the service message to be sent to the first network element is not perceived. A network element switches to the second network element.
  • the preset conditions may be set as needed, and the comparison between the embodiments of the present invention is not limited, and the comparison of the embodiments of the present invention is not limited. If the processing result of the service message on the second network element meets the preset condition, it indicates that the second network element can perform the same service processing as the first network element, that is, all the service information of the first network element can be forwarded; If the processing result of the service message on the second network element does not meet the preset condition, it indicates that the processing capability of the second network element is still weak, and the service processing cannot be performed in the same manner as the first network element, that is, the service message of the first network element cannot be used. All forwarded.
  • the system administrator monitors the running status of the multiple service messages on the second network element in real time, and if the preset condition is met, The second network element is upgraded normally. If the preset condition is not met, it indicates that there is a problem with the upgrade on the second network element, and it needs to be corrected.
  • part of the service message may be continuously forwarded to the second network element for trial operation, where the service is forwarded to the second network element each time.
  • the number of the messages may be equal or may be in an increasing trend. The comparison of the embodiments of the present invention is not limited.
  • the service message sent by the user may be of a plurality of types, such as: a Session Initiation Protocol (SIP) message, or an Internet Protocol (IP) link message.
  • SIP Session Initiation Protocol
  • IP Internet Protocol
  • different distribution policies may be correspondingly configured for different types of service messages, that is, the distribution policies delivered by the EMS need to include: different service messages and policies for distributing the service messages.
  • the distribution unit is specifically configured to:
  • the message type of the service message is a session initiation protocol SIP message, forwarding the service message to the user identifier according to the user identifier included in the SIP message, and a distribution identifier and a whitelist in the distribution policy.
  • a second network element or the first network element where the distribution identifier is used to: forward all the multiple service messages received by the SLB to the first network element, or receive the SLB All of the plurality of service messages are forwarded to the second network element, or are inactive to forward the plurality of service messages received by the SLB to which of the first network element and the second network element;
  • the whitelist list is used to store at least one user identifier;
  • the service message is an IP link message, according to the quintuple information included in the IP link message, and the correspondence between the quintuple attribute of the logical link and the virtual local area network identification VLAN ID in the distribution policy Forwarding the service message to the second network element or the first network element;
  • the quintuple information includes: an IP address of the external network element, a port number of the external network element, an IP address of the first network element, a port number of the first network element, and a transmission protocol.
  • Type the quintuple attribute of the logical link includes: a source IP address, a source port number, a destination IP address, a destination port number, and a transport protocol type;
  • the service message is not a SIP message and an IP link message, forwarding the service message to the second network element.
  • the communication unit 801 is further configured to:
  • the communication unit 801 Before the communication unit 801 receives all the multiple service messages received by the sent SLB, sends a synchronization request message to the first network element, where the synchronization request message is used to request to acquire the first network element.
  • the interface information, the interface information of the first network element includes: an IP address and a port number of the SIP server end of the first network element, and configuration information of the logical link that the first network element communicates with the first network element ;
  • the communication unit 801 is further configured to receive and store interface information sent by the first network element.
  • the distribution unit is configured to set an external interface attribute of the SLB according to the received interface information of the first network element, where the interface attribute includes: an IP address and a port number; and the service message is included
  • the interface information is matched with the interface message sent by the first network element, and the message type of the service message is determined.
  • the communication unit 801 After receiving the interface information sent by the first network element, the communication unit 801 compares the timestamp of receiving the interface information with the timestamp of the locally cached interface information, and obtains the timestamp from the first network element. The timestamp of the interface information is later than the timestamp of the locally stored information, and the locally stored interface information is replaced with the newly acquired interface information.
  • the first network element when the user sends a configuration command to the first network element to add or modify the external interface of the first network element, the first network element also sends a change notification message to the SLB in real time, and the SLB updates the local interface after receiving the change notification message.
  • Information and information such as distribution policies.
  • processor 802 is specifically configured to:
  • the distribution identifier is determined to be: if it is determined that the distribution identifier indicates that the plurality of service messages received by the SLB are forwarded to the second network element and the network element of the first network element, Querying the whitelist list, if the user identifier of the service message is included in the whitelist, forwarding the service message to the second network element; if the user identifier of the service message is not included in In the whitelist, forwarding the service message to the first network element;
  • the service message is forwarded to the first network element.
  • the distribution identifier may be a numeric symbol or other form of the symbol; the comparison of the embodiments of the present invention is not limited.
  • the distribution identifier “0” may be used to: forward all the plurality of service messages received by the SLB to the second network element and the network in the first network element, and use the distribution identifier “1”. Representing that all the service messages received by the SLB are forwarded to the second network element, and the distribution identifier “2” is used to: forward all the multiple service messages received by the SLB to the first network yuan.
  • processor 802 is specifically configured to:
  • a first virtual local area network identifier VLAN ID corresponding to the service message where the first VLAN ID is used to identify the first virtual a local area network, where the first virtual local area network includes: the first network element or the second network element;
  • the mapping between the logical link and the VLAN ID of the virtual local area network is used to control the number of logical links that are forwarded to the second network element, and may be set as required.
  • a user specifies a user whitelist on the EMS during the upgrade process
  • the system compares the number of whitelisted users with the total number of users in the site, and the total number of logical links that the first network element connects to the neighboring NEs. And converting the number of logical links into the second network element that needs to be distributed to the new version, and transmitting the distribution policy modification component of the corresponding number of logical links to the second network element.
  • the first network element and the surrounding network element are connected to each other for a total of four links, and if it is desired to distribute the calls of 2,500 users to the new version of the second network element.
  • the SLB forwards the service message of one of the logical links to the second network element, and the service messages of the remaining three logical links are still forwarded to the first network element.
  • the embodiment of the present invention provides that, in order to forward the service message sent by the internal network element of the system to the external network element, after receiving the response message sent by the external network element, the original path is returned to the sending end, and the communication unit 801 further Used for:
  • the processor 802 is further configured to modify a source port number in the first service message, and modify the source port number, the source port number, and a network element that sends the first service message.
  • the mapping relationship between the VLAN IDs of the virtual local area network identifiers is recorded in the first relationship table.
  • the communication unit 801 is further configured to receive a response message that is sent by the external network element, where the response message includes: a destination port number, where the destination port number is: the modified source port number;
  • the processor 802 is further configured to query, in the first relationship table, a port number corresponding to the destination port number and a virtual local area network identifier VLAN ID;
  • the first service message is a non-IP link message, and includes: a source IP address, a source port number, a destination IP address, and a destination port number.
  • the IP link message can be returned to the original path of the response message without performing port modification or port mapping. Therefore, the present invention implements
  • the first service message is only a non-IP link message, and may include: a SIP message, and other messages except SIP and IP link messages.
  • the first network element is in the VLAN 1 and the second network element is in the VLAN 2, and the two have the same port 1002.
  • the message that the source port of the first network element is 1002 can be modified to the port number 31002.
  • the message that the source port is 1002 sent by the second network element is modified to be the port number 21002, and is recorded in Table 3.
  • the SLB receives the message with the destination port number 21002, according to Table 3, it will be known: The message is sent to the port 1002 of the second network element in the VLAN 2. If the SLB receives the message with the destination port number 31002, the message is sent to the port 1002 of the first network element in the VLAN 1 according to Table 3. on.
  • an embodiment of the present invention provides an SLB, which receives a distribution policy delivered by an EMS, and forwards a part of the service messages sent by the external network element to the first one according to the distribution policy.
  • the network element forwards the remaining part of the service message to the second network element; after the processing result of the service message on the second network element meets the preset condition, the SLB receives the subsequent received according to the distribution policy.
  • a plurality of service messages sent by the external network element are all forwarded to the second network element. In this way, during the NE upgrade process, the SLB first forwards some of the messages in the service message to the second network element for trial operation. After the operation on the second network element is normal, the subsequent multiple services are received.
  • All the messages are forwarded to the second network element, which reduces the risk of the overall service being damaged due to the switchover of all services to the new network element during the NE upgrade process.
  • the existing network element system architecture is not changed, but an additional SLB module is added outside the network element to block the network element.
  • the system reliability is not reduced during the upgrade, and the carrier-class high reliability requirements are met.
  • FIG. 9 is a structural diagram of a network element management system EMS90 according to an embodiment of the present invention.
  • the EMS 90 may include: a processor 901, a communication unit 902, a memory 903, and at least one communication bus 904. To achieve the connection and mutual communication between these devices;
  • the communication unit 902 is configured to perform data transmission with an external network element.
  • the processor 901 may be a central processing unit (English: central processing unit, referred to as CPU).
  • the memory 903 may be a volatile memory (English: volatile memory), such as random access memory (English: random-access memory, abbreviation: RAM); or non-volatile memory (English: non-volatile memory), for example Read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive, abbreviation :SSD); or a combination of the above kinds of memories, and provides instructions and data to the processor 901.
  • volatile memory such as random access memory (English: random-access memory, abbreviation: RAM); or non-volatile memory (English: non-volatile memory), for example Read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive, abbreviation :SSD); or a
  • the processor 901 is configured to create a second network element, where the second network element is the same as the configuration attribute and the connection configuration of the first network element, and the second network element is different from the first network element.
  • the version of the second network element is not lower than the first network element.
  • the second network element is the same as the configuration attribute and the connection configuration of the first network element, and the second network element and the first network element are in different virtual local area networks, and are isolated by using VLANs to avoid IP conflicts. And the version of the second network element is not lower than the first network element. At the same time, the entire change is not perceived in the process of creating the second network element. It is also unnecessary to add interface data to the second network element.
  • the communication unit 902 is configured to send a distribution policy to the SLB, so that the SLB, according to the distribution policy, will receive a message type of each of the plurality of service messages, and on the second network element After the processing result of the service message meets the preset condition, the SLB forwards all the multiple received service messages sent by the external network element to the second network element according to the distribution policy.
  • the distribution policy is configured by the administrator to be sent to the SLB by using the EMS, and may be used to: control the SLB to forward the multiple service messages received by the SLB to the first network element and the second network element. proportion.
  • processor 901 is specifically configured to:
  • the first network element virtual machine image file is embedded in the created virtual machine to form the second network element.
  • the newly created second network element is a minimum function set of the first network element, and when the service message distribution to the second network element is gradually increased, the second The NE expands the capacity automatically through the elastic expansion function.
  • the first network element automatically shrinks the capacity due to the decrease in traffic. In this way, the virtual machine that is retracted by the first network element can be moved to the second network element. In this way, the consumption of infrastructure resources can be reduced; the specific implementation is as follows:
  • the processor 901 is further configured to reduce virtual machine resources of the first network element according to the reduced number of service messages processed on the first network element;
  • the first network element is revoked, and the virtual machine resources in the first network element are released.
  • the embodiment of the present invention provides a network element upgrade EMS, which is configured to create a second network element, where the second network element and the first network element have the same configuration attribute and connection configuration, and the second network element is The first network element is in a different virtual local area network, and the version of the second network element is not lower than the first network element; a distribution policy is sent to the SLB, so that the SLB according to the distribution policy a message type of each of the plurality of service messages received; and after the processing result of the service message on the second network element meets a preset condition, the SLB receives the subsequent message according to the distribution policy. All of the plurality of service messages sent by the external network element are forwarded to the second network element.
  • the SLB first forwards some of the messages in the service message to the second network element for trial operation. After the operation on the second network element is normal, the subsequent multiple services are received. All the messages are forwarded to the second network element, which reduces the risk of the overall service being damaged due to the switchover of all services to the new network element during the NE upgrade process.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • the units described as separate devices may or may not be physically separated, and the devices displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
  • each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.
  • the above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium.
  • the above software functional unit is stored in a storage medium and includes a plurality of instructions for causing a computer device ( Part of the steps of the method described in various embodiments of the present invention are a personal computer, server, or network device.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, and the program code can be stored. Medium.
  • the storage medium may include a read only memory, a random access memory, a magnetic disk or an optical disk, or the like.

Abstract

本发明公开了一种网元升级方法及设备,涉及通信技术领域,以解决现有升级过程中,网元将所有业务切换到新版本,一旦新版本升级有问题则会影响全局的问题。本发明提供的网元升级方法包括:SLB接收网元管理系统EMS下发的分发策略,根据所述分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。

Description

一种网元升级方法及设备
本申请要求于2015年9月2日提交中国专利局、申请号为201510556227.9、发明名称为“一种网元升级方法及设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域,尤其涉及一种网元升级方法及设备。
背景技术
核心网作为整个通信网络控制的核心,需要和周边各种网络及设备进行对接,所有的网络业务都需要通过核心网网元进行控制处理或中转,其提供的网络服务是不可替代的。因此,当核心网网元需要进行升级时,不仅需要对正在处理网络业务的系统升级,而且还需要正常处理网络业务,即要求核心网做到无损升级,在系统升级期间业务不间断,或只能容忍短暂的终端(如10s内)。
现有技术中,通常采用如下方法对核心网网元进行无损升级:先将网元中的进程划分为主备2个平面。升级时先将备平面升级为新版本(备平面不处理业务),备平面升级后和原主用平面进行状态倒换,并将全部业务从原主平面切换到原备平面(新主用平面),然后再升级原主平面。升级过程中只有将业务从主平面切换到升级到新版本的备平面时会产生非常短时间的业务中断(理论上业务中断时间约为10s),从而实现无损升级。
但是,在实现本发明的过程中,发明人发现上述无损升级方法存在如下问题:现网设备配置及组网千差万别,研发阶段无法模拟实际现网场景,新版本网元的很多问题只有在升级当天才能发现,因此,升级时,网元将所有业务切换到新版本,一旦新版本升级有问题则会影响全局。
发明内容
为解决上述问题,本发明提供网元升级方法及设备,以解决现有升级过程中,网元将所有业务切换到新版本后,一旦新版本升级有问题则会影响全局的问题。
本发明的实施例采用如下技术方案:
第一方面,本发明实施例提供一种网元升级方法,所述方法包括:
网络负载均衡器SLB接收网元管理系统EMS下发的分发策略;
所述SLB根据所述分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;
当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元;
其中,所述分发策略用于控制转发至所述第一网元和所述第二网元的业务消息的比例;所述第二网元与所述第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,且所述第二网元的版本不低于所述第一网元。
在第一方面的第一种可实现方式中,结合第一方面,所述业务消息包含:发起业务消息的用户的用户标识;所述SLB根据所述分发策略,将接收到的外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元具体包括:
所述SLB判断接收到的多个业务消息中每个业务消息的消息类型;
若所述SLB确定所述业务消息的消息类型为会话初始协议SIP消息,则根据所述SIP消息包含的用户标识、以及所述分发策略中的分发标识和白名单列表,将所述业务消息转发至所述第一网元或所述第二网元,其中,所述分发标识用于表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元、或将所述SLB接收到的多个业务消息全部转发至所述第二网元、或不确定将所述SLB接收到的多个业务消息转发至所述第一网元和所述第二网元中哪个网元;所述白名单列表用于存储至少一个用户标识;
若所述SLB确定所述业务消息为IP链路消息,则根据所述IP链路消息包含的五元组信息、以及所述分发策略中逻辑链路的五元组属性与虚拟局域网标识VLAN ID的对应关系,将所述业务消息转发至所述第一网元或所述第二网元;
其中,所述五元组信息包含:所述外部网元的IP地址、所述外部网元的端口号、所述第一网元的IP地址、所述第一网元的端口号、传输协议类型;所述逻辑链路的五元组属性包含:源IP地址、源端口号、目的IP地址、目的端口号、传输协议类型。
在第一方面的第二种可实现方式中,结合第一方面的第一种可实现方式,所述SLB根据所述SIP消息包含的用户标识、以及所述分发策略中的分发标识和白名单列表,将所述业务消息转发至所述第二网元或所述第一网元具体包括:
所述SLB查询分发标识;
若确定所述分发标识表示:不确定将所述SLB接收到的多个业务消息转发至所述第二网元和所述第一网元中哪个网元,则查询所述白名单列表,若所述业务消息的用户标识包含在所述白名单列表中,则将所述业务消息转发至所述第二网元;若所述业务消息的用户标识未包含在所述白名单列表中,则将所述业务消息转发至所述第一网元;
若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第二网元,则将所述业务消息转发至所述第二网元;
若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元,则将所述业务消息转发至所述第一网元。
在第一方面的第三种可实现方式中,结合第一方面的第一种可实现方式,所述SLB根据 所述IP链路消息包含的五元组信息、以及所述分发策略中逻辑链路的五元组属性与虚拟局域网标识VLAN ID的对应关系,将所述业务消息转发至所述第二网元或所述第一网元具体包括:
根据所述分发策略中逻辑链路与虚拟局域网标识VLAN ID的对应关系,确定与所述业务消息相对应的第一虚拟局域网标识VLAN ID;其中,所述第一VLAN ID用于标识第一虚拟局域网,所述第一虚拟局域网包含:所述第一网元或所述第二网元;
根据网元、以及所述网元所处的虚拟局域网的虚拟局域网标识VLAN ID之间的对应关系,将所述业务消息转发至与所述第一VLAN ID相对应的网元上。
在第一方面的第四种可实现方式中,结合第一方面的第一种可实现方式至第一方面的第三种可实现方式中的任一种可实现方式,在所述SLB接收EMS下发的分发策略之前,所述方法还包括:
所述SLB向所述第一网元发送同步请求消息,其中,所述同步请求消息用于请求获取所述第一网元的接口信息,所述第一网元的接口信息包含:所述第一网元的SIP服务端的IP地址及端口号,以及所述第一网元与所述间进行通信的逻辑链路的配置信息;
所述SLB接收并存储所述第一网元的接口信息,并根据接收的所述第一网元的接口信息设定所述SLB自身对外的接口属性,所述接口属性包含:IP地址及端口号;
相应的,所述SLB判断接收到的多个业务消息中每个业务消息的消息类型具体包括:
根据所述业务消息包含的接口信息、所述第一网元的接口消息,判断所述业务消息的消息类型。
在第一方面的第五种可实现方式中,结合第一方面,所述方法还包括:
若所述SLB接收到所述第一网元或所述第二网元发送的第一业务消息,则将所述第一业务消息中的源端口号进行修改,并将修改后的源端口号、以及所述源端口号和发送所述第一业务消息的网元所在的虚拟局域网标识VLAN ID的对应关系记录在第一关系表中;
将包含修改后的源端口号的第一业务消息转发至所述外部网元;
接收所述外部网元回复的响应消息,其中,所述响应消息包含:目的端口号,所述目的端口号为:所述修改后的源端口号;
查询所述第一关系表中,获取与所述目的端口号相对应的端口号和虚拟局域网标识VLAN ID;
将所述响应消息发送至所述虚拟局域网标识VLAN ID标识的虚拟局域网中的网元的所述端口号上;
其中,所述第一业务消息为非IP链路消息,包含:源IP地址、源端口号、目的IP地址、目的端口号。
在第一方面的第六种可实现方式中,结合第一方面至第一方面的第五种可实现方式中的任一种可实现方式,所述预设条件为下述一种或多种情况:
所述第二网元上所有业务消息呼叫成功;
所述第二网元上所有业务消息的测试用例的成功率大于等于预设阈值。
第二方面,本发明实施例提供一种网元升级方法,应用于网元管理系统EMS,包括:
所述EMS创建第二网元,其中,所述第二网元与第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网标识VLAN ID内,且所述第二网元的版本不低于所述第一网元;
所述EMS向SLB发送分发策略,以使得所述SLB根据所述分发策略,将接收到的多个业务消息中每个业务消息的消息类型;并当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。
在第二方面的第一种可实现方式中,结合第二方面,所述EMS创建第二网元具体包括:
所述EMS通过虚拟网络功能管理者VNFM命令所述第一网元所在的虚拟基础设施管理者VIM创建所述第一网元的虚拟机镜像文件;
所述EMS命令所述VIM创建所述第一网元的虚拟机;
所述EMS将所述第一网元虚拟机镜像文件植入创建的虚拟机内,形成所述第二网元。
在第二方面的第二种可实现方式中,结合第二方面或第二方面的第一种可实现方式,所述方法还包括:
所述EMS根据所述第一网元上处理的业务消息减少的数量,减少所述第一网元的虚拟机资源;
直至所述SLB将后续接收到的多个业务消息全部转发至所述第二网元之后,所述EMS撤销所述第一网元,释放所述第一网元中的虚拟机资源。
在第二方面的第三种可实现方式中,结合第二方面至第二方面的第二种可实现方式中的任一种实现方式,所述第二网元上的业务消息的处理结果满足预设条件包括:所述第二网元上所有业务消息呼叫成功;或者
所述第二网元上所有业务消息的测试用例的成功率大于等于预设阈值。
第三方面,本发明实施例提供一种网络负载均衡器SLB,包括:
接收单元,用于接收网元管理系统EMS下发的分发策略;
分发单元,用于根据所述接收单元接收到的分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;
以及,当所述第二网元上的业务消息的处理结果满足预设条件后,根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元;
其中,所述分发策略用于控制转发至所述第一网元和所述第二网元的业务消息的比例;所述第二网元与所述第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处 于不同的虚拟局域网内,且所述第二网元的版本不低于所述第一网元。
在第三方面的第一种可实现方式中,结合第三方面,所述业务消息包含:发起业务消息的用户的用户标识;所述分发单元具体用于:
判断接收到的多个业务消息中每个业务消息的消息类型;
若确定所述业务消息的消息类型为会话初始协议SIP消息,则根据所述SIP消息包含的用户标识、以及所述分发策略中的分发标识和白名单列表,将所述业务消息转发至所述第一网元或所述第二网元,其中,所述分发标识用于表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元、或将所述SLB接收到的多个业务消息全部转发至所述第二网元、或不确定将所述SLB接收到的多个业务消息转发至所述第一网元和所述第二网元中哪个网元;所述白名单列表用于存储至少一个用户标识;
若确定所述业务消息为IP链路消息,则根据所述IP链路消息包含的五元组信息、以及所述分发策略中逻辑链路的五元组属性与虚拟局域网标识VLAN ID的对应关系,将所述业务消息转发至所述第一网元或所述第二网元;
其中,所述五元组信息包含:所述外部网元的IP地址、所述外部网元的端口号、所述第一网元的IP地址、所述第一网元的端口号、传输协议类型;所述逻辑链路的五元组属性包含:源IP地址、源端口号、目的IP地址、目的端口号、传输协议类型。
在第三方面的第二种可实现方式中,结合第三方面的第一种可实现方式,所述分发单元具体用于:
查询分发标识;
若确定所述分发标识表示:不确定将所述SLB接收到的多个业务消息转发至所述第二网元和所述第一网元中哪个网元,则查询所述白名单列表,若所述业务消息的用户标识包含在所述白名单列表中,则将所述业务消息转发至所述第二网元;若所述业务消息的用户标识未包含在所述白名单列表中,则将所述业务消息转发至所述第一网元;
若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第二网元,则将所述业务消息转发至所述第二网元;
若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元,则将所述业务消息转发至所述第一网元。
在第三方面的第三种可实现方式中,结合第三方面的第一种可实现方式,所述分发单元具体用于:
根据所述分发策略中逻辑链路与虚拟局域网标识VLAN ID的对应关系,确定与所述业务消息相对应的第一虚拟局域网标识VLAN ID;其中,所述第一VLAN ID用于标识第一虚拟局域网,所述第一虚拟局域网包含:所述第一网元或所述第二网元;
根据网元、以及所述网元所处的虚拟局域网的虚拟局域网标识VLAN ID之间的对应关系,将所述业务消息转发至与所述第一VLAN ID相对应的网元上。
在第三方面的第四种可实现方式中,结合第三方面的第一种可实现方式至第三方面的第三种可实现方式中的任一种可实现方式,所述SLB还包括:
发送单元,用于在所述接收单元接收EMS下发的分发策略之前,向所述第一网元发送同步请求消息,其中,所述同步请求消息用于请求获取所述第一网元的接口信息,所述第一网元的接口信息包含:所述第一网元的SIP服务端的IP地址及端口号,以及所述第一网元与所述间进行通信的逻辑链路的配置信息;
所述接收单元,还用于接收并存储所述第一网元发送的接口信息;
所述分发单元,具体用于根据接收的所述第一网元的接口信息设定所述SLB自身对外的接口属性,所述接口属性包含:IP地址及端口号;
根据所述业务消息包含的接口信息、所述第一网元的接口消息,判断所述业务消息的消息类型。
在第三方面的第五种可实现方式中,结合第三方面,所述接收单元,还用于接收到所述第一网元或所述第二网元发送的第一业务消息;
所述分发单元,还用于将所述第一业务消息中的源端口号进行修改,并将修改后的源端口号、以及所述源端口号和发送所述第一业务消息的网元所在的虚拟局域网标识VLAN ID的对应关系记录在第一关系表中;
将包含修改后的源端口号的第一业务消息转发至所述外部网元;
接收所述外部网元回复的响应消息,其中,所述响应消息包含:目的端口号,所述目的端口号为:所述修改后的源端口号;
查询所述第一关系表中,获取与所述目的端口号相对应的端口号和虚拟局域网标识VLAN ID;
将所述响应消息发送至所述虚拟局域网标识VLAN ID标识的虚拟局域网中的网元的所述端口号上;
其中,所述第一业务消息为非IP链路消息,包含:源IP地址、源端口号、目的IP地址、目的端口号。
在第三方面的第六种可实现方式中,结合第三方面至第三方面的第五种可实现方式中的任一种可实现方式,所述预设条件为下述一种或多种情况:
所述第二网元上所有业务消息呼叫成功;
所述第二网元上所有业务消息的测试用例的成功率大于等于预设阈值。
第四方面,本发明实施例提供一种网元管理系统EMS,包括:
创建单元,用于创建第二网元,其中,所述第二网元与第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,且所述第二网元的版本不低于所述第一网元;
发送单元,用于向SLB发送分发策略,以使得所述SLB根据所述分发策略,将接收到的多个业务消息中每个业务消息的消息类型;并当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。
在第四方面的第一种可实现方式中,结合第四方面,所述创建单元具体用于:
通过虚拟网络功能管理者VNFM命令所述第一网元所在的虚拟基础设施管理者VIM创建所述第一网元的虚拟机镜像文件;
命令所述VIM创建所述第一网元的虚拟机;
将所述第一网元虚拟机镜像文件植入创建的虚拟机内,形成所述第二网元。
在第四方面的第二种可实现方式中,结合第四方面或第四方面的第一种可实现方式,所述创建单元,还用于:
根据所述第一网元上处理的业务消息减少的数量,减少所述第一网元的虚拟机资源;
直至所述SLB将后续接收到的多个业务消息全部转发至所述第二网元之后,撤销所述第一网元,释放所述第一网元中的虚拟机资源。
在第四方面的第三种可实现方式中,结合第四方面至第四方面的第二种可实现方式中的任一种实现方式,所述第二网元上的业务消息的处理结果满足预设条件包括:所述第二网元上所有业务消息呼叫成功;或者
所述第二网元上所有业务消息的测试用例的成功率大于等于预设阈值。
由上可知,本发明实施例提供一种网元升级方法,包括:SLB接收EMS下发的分发策略,根据所述分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。如此,在网元升级过程中,通过SLB先将业务消息中的部分消息转发至第二网元进行试运行,当第二网元上的运行情况正常后,再将后续接收到的多个业务消息全部转发至第二网元,降低了网元升级过程中,全部业务切换至新网元,造成的整体业务受损的风险。同时,不改变现有网元系统架构,只是在网元外部增加新增了一个SLB模块,屏蔽了网元内部结构,通过在内部新增网元实例,并控制消息流在新老网元间的切换,保持了升级期间系统可靠性不降低,满足了电信级高可靠的要求。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些 附图获得其他的附图。
图1为现有NFV架构的示意图;
图2为本发明实施例提供的一种系统架构的示意图;
图3为本发明实施例提供的一种网络升级方法的流程图;
图4本发明实施例提供的一种分发策略的流程图;
图5为本发明实施例提供的一种网络升级方法的流程图;
图6为本发明实施例提供的一种SLB的结构图;
图6A为本发明实施例提供的一种SLB的结构图;
图7为本发明实施例提供的一种EMS的结构图;
图8为本发明实施例提供的一种SLB的结构图;
图9为本发明实施例提供的一种EMS的结构图。
具体实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
需要说明的是,本发明实施例提供的网元升级方法,不仅可以应用于云计算平台或非云计算平台下网元升级的场景,还可以应用于云计算平台或非云计算平台下网元割接、容灾倒换的场景,本发明实施例对比不进行限定,本发明仅以云计算平台下网元升级的场景为例进行说明;其中,网元割接、容灾倒换场景下的实施方法与本发明实施例描述的网元升级的方法相同,在此不再赘述。
云计算平台下,广大电信运营商和厂商将核心网中的网元进行虚拟化构建,采用如图1所示的网络功能虚拟化(network function virtualization,NFV)标准定义的网络系统架构作为电信设备云化架构,所述NFV架构可包括:营运支持设备(operations support system,OSS)、至少一个网元管理系统(element management system,EMS)以及以下几大虚拟功能节点:虚拟化网络功能(virtualized network function,VNF)、网络功能虚拟化基础建设(NFV infrastructure,NFVI)、网络功能虚拟化管理与协调流程(NFV Management and Orchestration,NFV MANO)。其中,OSS代表营运商各自的营运支持设备,负责营运商不同域(如固定网络域或移动网络域)的告警、话务统计、配置管理、网络规划等网络管理业务,在为用户提供各式便利服务的同时,根据用户自身的营运业务模式与计费原则进行公共资源的协调配置。EMS须提供网络管理的五种基本功能错误、配置、计帐、性能和安全(Faul t,Configuration,Accounting,Performance and Security,FCAPS),此外,EMS通常还具备以下功能:拓扑管理、系统备份与恢复、系统监控、日志管理、北向接口、命令终端。VNF 为核心网中物理网元的虚拟化功能设备,由NFVI将硬件资源虚拟化为成为可动态请求使用的虚拟资源提供给VNF,使VNF与物理网元具有相同功能,且VNF由EMS对其进行操作和管理;NFV MANO为NFV架构中进行整体控管与协调的重要角色,包括:虚拟网络功能调度(NFV Orchestrator,NFVO)、虚拟网络功能管理(VNF Manager,VNFM)及虚拟化基础建设管理(Virtualised Infrastructure Manager,VIM)三个部分,当有软件及硬件资源的需求时,NFV MANO将协调、验证与授权相关资源的请求,同时负责管理VNF的生命周期,如实例化、弹性组织、更新、查询、终止VNF等,此外,NFV MANO也负责网络服务的策略管理(Policy Management)、关联事件的收集与转送、以及基础建设相关资源的配置,如为虚拟机添增资源、提升能源效率、资源归还等。
本发明实施例的基本原理是:在NFV架构中增加一网络负载均衡器(Software Load Balancer,SLB),其中,SLB具有如下功能:负责将外部网络的信令消息发送给物理网元的虚拟化功能设备VNF1或VNF1’,以及将VNF1及VNF1’发送到网络外部的请求消息进行网络地址映射(Network Address Translate,NAT)映射,保证回应消息能原路返回到消息请求端。当需要进行网元升级时,先将物理网元虚拟后的VNF1进行镜像映射,形成VNF1’作为备用虚拟网元,同时并对VNF1’完成系统升级,然后,由SLB根据预设分发策略将接收到外部其他网元发送的业务消息从VNF1网元逐步分发到VNF1’网元上,完成网元的无损升级过程,避免直接将全部业务消息转发至新网元上,造成的全局受影响的问题。例如,图2为本发明实施例提供的一种系统架构的示意图,如图2所示,在其他网元与物理网元虚拟后的VNF1和VNF1’之间设置有SLB,且该SLB与EMS相连接,由EMS向SLB下发分发策略,控制SLB发送给VNF1或VNF1’的业务消息,如此,在不改变现有网元系统架构的情况下,在网元外部增加新增了一个SLB模块,屏蔽了网元内部结构,通过在内部新增网元实例,并控制消息流在新老实例间切换,保持了升级期间系统可靠性不降低。下面通过具体实施例对本发明提供的网元升级方法进行详细介绍:
实施例一
图3为本发明实施例提供的一种网元升级方法的流程图,如图3所示,所述方法可以包括:
步骤101:SLB接收网元管理系统EMS下发的分发策略。
其中,所述分发策略由管理员根据需要制定且通过EMS发送至SLB,可以用于:控制所述SLB将所述SLB接收到的多个业务消息转发至第一网元和第二网元的比例。
步骤102:SLB根据所述分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元。
其中,所述SLB接收到的多个业务消息为:所述外部网元接收到、准备发送至第一网元 的至少一个用户发出的多个业务消息,如:可以包含M个业务消息,所述M为大于1的整数,每个业务消息包含:发起所述业务消息的用户的用户标识。
在云计算平台的网元升级场景下,所述外部网元和所述第一网元可以为虚拟网元;在非云计算平台的网元升级下,外部网元和第一网元可以为物理网元。
需要说明的是,本发明实施例中的术语“第一”、“第二”、“另一”等指示的系统或元件或事物为基于实施例描述的具有一定功能的系统或元件或事物,仅是为了便于描述本发明和简化描述,而不是指示或暗示所指的系统或元件或事物必须有此命名,因此不能理解为对本发明的限制。
其中,所述第二网元可以被称为所述第一网元的备用网元,由EMS自动生成,且与所述第一网元具有相同的配置属性和连接属性,第二网元和第一网元处于不同的局域网内,通过虚拟局域网(Virtual Local Area Network,VLAN)或虚拟扩展局域网(Virtual eXtensible LAN,VXLAN)进行网络隔离,彼此不感知对方。由于,第二网元与第一网元具有相同的配置属性和连接属性,因此,对于而言,在网元无损升级过程中,不会感知到准备发送至第一网元的业务消息从第一网元切换至第二网元。
步骤103:当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。
其中,预设条件可以根据需要进行设定,本发明实施例对比不进行限定,本发明实施例对比不进行限定。若第二网元上的业务消息的处理结果满足预设条件,则表示第二网元可以同第一网元一样进行业务处理,即可以将第一网元的业务消息全部转发过来;若第二网元上的业务消息的处理结果不满足预设条件,则表示第二网元的处理能力还是很弱,不能同第一网元一样进行业务处理,即不能将第一网元的业务消息全部转发过来。
可选的,所述预设条件可以为下述一种或多种情况:所述第二网元上所有业务消息呼叫成功、所述第二网元上所有业务消息的测试用例的成功率大于等于预设阈值;
其中,所述第二网元上所有业务消息呼叫成功表示:所述第二网元能够准确地接收到对方网元发送的业务消息;测试用例(Test Case)是由技术人员编译的、用于测试业务消息是否呼叫成功的程序,可以在软件环境下对第二网元上业务消息的呼叫进行测试;所述预设阈值可以根据需要进行设置,优选的,可以设置为百分之白的成功率。
可选的,当SLB将多个业务消息转发至第二网元运行后,系统管理员会实时监测所述多个业务消息在第二网元上的运行情况,若满足预设条件,则表示第二网元正常升级;若不满足预设条件,则表示第二网元上的升级存在问题,需要对其进行修正。
其中,所述后续的多个业务消息同样可以为:所述外部网元接收到、准备发送至第一网 元的至少一个用户发出的业务消息,包含至少一个业务消息。
需要说明的是,在第二网元上的业务运行情况没有满足预设条件之前,可以重复执行上述步骤102,不断将部分业务消息转发至第二网元进行试运行,其中,每次转发至第二网元的业务消息的个数可以相等,也可以呈递增趋势,本发明实施例对比不进行限定。
如此,在网元升级过程中,通过SLB先将业务消息中的部分消息转发至第二网元进行试运行,当第二网元上的运行情况正常后,再将后续接收到的多个业务消息全部转发至第二网元,降低了网元升级过程中,全部业务切换至新网元,造成的整体业务受损的风险。
可选的,因用户发出的业务消息可以有多种类型,如可以为:会话初始协议(Session Initiation Protocol,SIP)消息,还可以为:网络协议(Internet Protocol,IP)链路消息,所以,本发明实施例中,为了便于业务消息的分发,针对不同类型的业务消息,可以对应制定不同的分发策略,即EMS下发的分发策略中需包含:不同业务消息与分发该业务消息的策略的对应关系。下面对上述步骤102中,SLB如何根据分发策略将将接收到的外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元进行详细介绍:
所述SLB判断接收到的多个业务消息中每个业务消息的消息类型;
若所述SLB确定所述业务消息的消息类型为会话初始协议SIP消息,则根据所述SIP消息包含的用户标识、以及所述分发策略中的分发标识和白名单列表,将所述业务消息转发至所述第一网元或所述第二网元,其中,所述分发标识用于表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元、或将所述SLB接收到的多个业务消息全部转发至所述第二网元、或不确定将所述SLB接收到的多个业务消息转发至所述第一网元和所述第二网元中哪个网元;所述白名单列表用于存储至少一个用户标识;
若所述SLB确定所述业务消息为IP链路消息,则根据所述IP链路消息包含的五元组信息、以及所述分发策略中逻辑链路的五元组属性与虚拟局域网标识VLAN ID的对应关系,将所述业务消息转发至所述第一网元或所述第二网元;
其中,所述五元组信息包含:所述外部网元的IP地址、所述外部网元的端口号、所述第一网元的IP地址、所述第一网元的端口号、传输协议类型;所述逻辑链路的五元组属性包含:源IP地址、源端口号、目的IP地址、目的端口号、传输协议类型;
若所述SLB确定所述业务消息不是SIP消息和IP链路消息,则将所述业务消息转发至所述第二网元。
其中,为了便于所述SLB判断所述业务消息的消息类型,在所述SLB接收发送的SLB接收到的多个业务消息全部之前,所述方法还可以包括:
所述SLB向所述第一网元发送同步请求消息,其中,所述同步请求消息用于请求获取所述第一网元的接口信息,所述第一网元的接口信息包含:所述第一网元的SIP服务端的IP地址及端口号,以及所述第一网元与所述间进行通信的逻辑链路的配置信息;
所述SLB接收并存储所述第一网元发送的接口信息,并根据接收的所述第一网元的接口信息设定所述SLB自身对外的接口属性,所述接口属性包含:IP地址及端口号;
相应的,所述SLB判断所述业务消息的消息类型具体可以包括:
将所述业务消息包含的接口信息与所述第一网元的接口消息进行匹配,判断所述业务消息的消息类型。
由于遵循通信协议规定,SIP消息具有如下特征:包含SIP服务器端的IP地址和端口号,其中端口号是通信双方提前约定好,并且是固定不变的,如:业界公开的默认端口号为5060。IP链路消息具有如下特征:互相通信的源端及目的端两个主机采用固定的IP地址+端口号进行通信,且彼此知道对端的IP地址及端口号,并且采用固定的传输协议类型,其中,传输协议类型可以为:SCTP、TCP、UDP等等,所以,将所述业务消息包含的接口信息与所述第一网元的接口消息进行匹配,判断所述业务消息的消息类型具体包括:
若接收到的业务消息包含固定的端口号,则可以确定所述业务消息为SIP消息;
若接收到的业务消息包含五元组信息,则可以确定所述业务消息为IP链路消息。
其中,在所述SLB接收到所述第一网元发送的接口信息后,会将接收到接口信息的时间戳与本地缓存的接口信息的时间戳进行比较,若从第一网元获取的接口信息的时间戳晚于本地存储信息的时间戳,则用新获取的接口信息替换本地存储的接口信息。同时,当用户在第一网元下发配置命令增加或修改第一网元的外部接口时,第一网元还会实时发送变更通知消息给SLB,SLB收到变更通知消息后更新本地的接口信息和分发策略等信息。
需要说明的是,本发明实施例中,源IP地址、源端口号、目的IP地址、目的端口号中的“源”和“目的”是根据业务消息的发起和接收情况而定的,通常情况下,将发送业务消息的一端的IP地址和端口号称之为源IP地址和端口号,将接收业务消息的一端的IP地址和端口号称之为目的IP地址和目的端口号。
具体的,如图4所示,所述SIP根据所述SIP消息包含的用户标识、以及所述分发策略中的分发标识和白名单列表,将所述业务消息转发至所述第二网元或所述第一网元可以包括:
步骤1021:SLB查询分发标识;若确定所述分发标识表示:不确定将所述SLB接收到的多个业务消息转发至所述第二网元和所述第一网元中哪个网元,则执行步骤1022;
若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第二网元,则执行步骤1023;
若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元,则执行步骤1024。
步骤1022:查询所述白名单列表,判断所述业务消息的用户标识是否包含在所述白名单列表中,若所述业务消息的用户标识包含在所述白名单列表中,则执行步骤1024;若所述业务消息的用户标识未包含在所述白名单列表中,则执行步骤1025。
步骤1023:将所述业务消息转发至所述第二网元。
步骤1024:将所述业务消息转发至所述第一网元。
其中,所述分发标识可以为数字符号或其他形式的符号;本发明实施例对比不进行限定。例如,可以用分发标识“0”表示:不确定将所述SLB接收到的多个业务消息全部转发至所述第二网元和所述第一网元中哪个网,用分发标识“1”表示:将所述SLB接收到的多个业务消息全部转发至所述第二网元,用分发标识“2”表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元。
例如,下表1包含分发标识以及白名单列表,此时,若业务消息包含的用户标识为用户2,则确定将业务消息转发至第二网元;若业务消息包含的用户标识为用户4,则确定将业务消息转发至第一网元。
表1
Figure PCTCN2016094416-appb-000001
相对应的,在后续步骤103的分发策略中,可以将分发策略包含的分发标识设置为用于表示:将所述业务消息转发至所述第二网元的标识信息,以便SLB根据分发策略,将后续接收到的多个业务消息全部分发至第二网元。
具体的,所述SLB根据所述IP链路消息包含的五元组信息、以及所述分发策略中逻辑链路的五元组属性与虚拟局域网标识VLAN ID的对应关系,将所述业务消息转发至所述第二网元或所述第一网元可以包括:
根据所述分发策略中逻辑链路与虚拟局域网标识VLAN ID的对应关系,确定与所述业务消息相对应的第一虚拟局域网标识VLAN ID;其中,所述第一VLAN ID用于标识第一虚拟局域网,所述第一虚拟局域网包含:所述第一网元或所述第二网元;
根据网元、以及所述网元所处的虚拟局域网的虚拟局域网标识VLAN ID之间的对应关系,将所述业务消息转发至与所述第一VLAN ID相对应的网元上。
其中,所述逻辑链路与虚拟局域网标识VLAN ID的对应关系用于控制转发至第二网元上的逻辑链路的个数,可以根据需要设置,本发明实施例对比不进行限定。当网元在升级过程中,用户在EMS上指定用户白名单时,系统根据白名单用户数与该局点总用户数的比例,并根据第一网元与周边网元对接的逻辑链路总数,换算成需要分发到新版本的第二网元的逻辑链路数,并将对应数量的逻辑链路的分发策略修改成分发到第二网元。例如:若第一网元的用户容量是10000,第一网元和周边网元(如)对接一共有四条链路,若希望将其中的2500个用户的呼叫分发到新版本的第二网元,则SLB会将其中的一条逻辑链路的业务消息转发第二网元,其余三条逻辑链路的业务消息仍然转发到第一网元上。
例如,若第一网元所处的虚拟局域网的标识为:VLAN1,第二网元所处的虚拟局域网的标识为:VLAN2,的IP地址为:20.20.10.2/24,包含的4个端口的端口号分别为:01、02、03、04;第一网元的IP地址为:10.10.1.1/24,包含的4个端口的端口号分别为:0A、0B、0C、0D,与第一网元间的传输协议类型为:TCP;则外部网元和第一网元间可以形成以下用于传输业务消息的四个逻辑链路:20.20.10.2/24、01、10.10.1.1/24、0A、TCP;20.20.10.2/24、02、10.10.1.1/24、0B、TCP;20.20.10.2/24、03、10.10.1.1/24、0C、TCP;20.20.10.2/24、04、10.10.1.1/24、0D、TCP;由于第二网元与第一网元的配置属性和连接属性相同,则第二网元也可以与间形成如上所述的四个逻辑链路。此时,若将逻辑链路20.20.10.2/24、04、10.10.1.1/24、0D上发送的业务消息转发至第二网元,以实现将发送至第一网元的部分业务消息切换至第二网元,需要预先设置如下表2所示的对应关系。
此时,若接收到的业务消息包含的五元组属性为:20.20.10.2/24、03、10.10.1.1/24、0C、TCP,则根据表2可知:将该业务消息转发至第一网元;若接收到的业务消息包含的五元组属性为:20.20.10.2/24、04、10.10.1.1/24、0D、TCP,则根据表2可知:将该业务消息转发至第二网元。
表2
逻辑链路 VLAN ID
20.20.10.2/24、01、10.10.1.1/24、0A、TCP VLAN1
20.20.10.2/24、02、10.10.1.1/24、0B、TCP VLAN1
20.20.10.2/24、03、10.10.1.1/24、0C、TCP VLAN1
20.20.10.2/24、04、10.10.1.1/24、0D、TCP VLAN2
相对应的,在后续的分发策略中,可以将逻辑链路全部设置为与第二网元所处的虚拟局域网的标识VLAN ID相对应,以使得SLB将后续接收到IP链路消息全部转发至第二网元。
进一步的,本发明实施例提供,SLB还可以将系统内部网元发送的业务消息转发至外部网元,在接收到外部网元发送的响应消息后原路返回至发送端,具体如下:
若所述SLB接收到所述第一网元或所述第二网元发送的第一业务消息,则所述SLB将所述第一业务消息中的源端口号进行修改,并将修改后的源端口号、以及所述源端口号和发送所述第一业务消息的网元所在的虚拟局域网标识VLAN ID的对应关系记录在第一关系表中;
将包含修改后的源端口号的第一业务消息转发至所述外部网元;
接收所述外部网元回复的响应消息,其中,所述响应消息包含:目的端口号,所述目的端口号为:所述修改后的源端口号;
查询所述第一关系表中,获取与所述目的端口号相对应的端口号和虚拟局域网标识VLAN ID;
将所述响应消息发送至所述虚拟局域网标识VLAN ID标识的虚拟局域网中的网元的所述端口号上;
其中,所述第一业务消息为非IP链路消息,包含:源IP地址、源端口号、目的IP地址、目的端口号。
需要说明的是,由于一条逻辑链路可以唯一确认通信双方,因此对于IP链路消息,在不进行端口修改、端口映射的方法下,也可以实现响应消息的原路返回,因此,本发明实施例中,所述第一业务消息仅为:非IP链路消息,可以包括:SIP消息、以及除SIP和IP链路消息之外的其他消息。
例如,第一网元处于VLAN1内,第二网元处于VLAN2中,二者具有共同的端口1002,此时,可以将第一网元的发出的源端口为1002的消息修改为端口号为31002,将第二网元发出的源端口为1002的消息修改为端口号为21002,并记录在表3中,若SLB接收到发送的目的端口号为21002的消息,则根据表3可知:将该消息发送至VLAN2内的第二网元的1002端口上,若SLB接收到发送的目的端口号为31002的消息,则根据表3可知:将该消息发送至VLAN1内的第一网元的1002端口上。
表3
修改后端口号 修改前端口号 VLAN ID
21002 1002 VLAN2
31002 1002 VLAN1
由上可知,本发明实施例提供一种网元升级方法,包括:SLB接收EMS下发的分发策略,根据所述分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。如此,在网元升级过程中,通过SLB先将业务消息中的部分消息转发至第二网元进行试运行,当第二网元上的运行情况正常后,再将后续接收到的多个业务消息全部转发至第二网元,降低了网元升级过程中,全部业务切换至新网元,造成的整体业务受损的风险。同时,不改变现有网元系统架构,只是在网元外部增加新增了一个SLB模块,屏蔽了网元内部结构,通过在内部新增网元实例,并控制消息流在新老网元间的切换,保持了升级期间系统可靠性不降低,满足了电信级高可靠的要求。
实施例二
图5为本发明实施例提供的另一种网元升级方法的流程图,如图5所示,所述方法可以包括以下步骤:
步骤201:EMS创建第二网元。
其中,所述第二网元与第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,通过VLAN隔离,避免产生IP冲突,且所述第二网元的版本不低于所述第一网元。同时,在创建第二网元的过程中,并不感知整个变化。也不需要在上增加与第二网元的接口数据。
具体的,所述EMS创建第二网元可以包括:
所述EMS通过虚拟网络功能管理者VNFM命令所述第一网元所在的虚拟基础设施管理者VIM创建所述第一网元的虚拟机镜像文件;
所述EMS命令所述VIM创建所述第一网元的虚拟机;
所述EMS将所述第一网元虚拟机镜像文件植入创建的虚拟机内,形成所述第二网元。
步骤202:EMS向SLB发送分发策略,所述SLB根据所述分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;并当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。
其中,所述分发策略由管理员根据需要制定且通过EMS发送至SLB,可以用于:控制所述SLB将所述SLB接收到的多个业务消息转发至第一网元和第二网元的比例。
进一步的,为了提高资源的利用率,本发明实施例中,新创建的第二网元是第一网元的最小功能集,当逐步加大对第二网元的业务消息分发时,第二网元通过弹性伸缩功能完成自动 扩容,而第一网元由于业务量的下降,会自动完成缩容,如此,可以将第一网元缩容而释放的虚拟机挪到第二网元下使用,通过这种方式可以降低对基础设施资源的消耗;具体如下:
所述EMS根据所述第一网元上处理的业务消息减少的数量,减少所述第一网元的虚拟机资源;
直至所述SLB将接收到的多个业务消息全部转发至所述第二网元之后,所述EMS撤销所述第一网元,释放所述第一网元中的虚拟机资源。
由上可知,本发明实施例提供一种网元升级方法,所述EMS创建第二网元,其中,所述第二网元与第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,且所述第二网元的版本不低于所述第一网元;向SLB发送分发策略,以使得所述SLB根据所述分发策略,将接收到的多个业务消息中每个业务消息的消息类型;并当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。如此,在网元升级过程中,通过SLB先将业务消息中的部分消息转发至第二网元进行试运行,当第二网元上的运行情况正常后,再将后续接收到的多个业务消息全部转发至第二网元,降低了网元升级过程中,全部业务切换至新网元,造成的整体业务受损的风险。
实施例三
图6为本发明实施例提供的一种网络负载均衡器SLB60的结构图,如图6所示,所述SLB60可以包括:
接收单元601,用于接收网元管理系统EMS下发的分发策略。
其中,所述分发策略由管理员根据需要制定且通过EMS发送至SLB,可以用于:控制所述SLB将所述SLB接收到的多个业务消息转发至第一网元和第二网元的比例。
分发单元602,用于根据所述分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;
以及,当所述第二网元上的业务消息的处理结果满足预设条件后,根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。
其中,接收单元601接收到的多个业务消息为:所述外部网元接收到、准备发送至第一网元的至少一个用户发出的多个业务消息,如:可以包含M个业务消息,所述M为大于1的整数,每个业务消息包含:发起所述业务消息的用户的用户标识。
在云计算平台的网元升级场景下,所述外部网元和所述第一网元可以为虚拟网元;在非云计算平台的网元升级下,外部网元和第一网元可以为物理网元。
需要说明的是,本发明实施例中的术语“第一”、“第二”、“另一”等指示的系统或元件或事物为基于实施例描述的具有一定功能的系统或元件或事物,仅是为了便于描述本发明和简化描述,而不是指示或暗示所指的系统或元件或事物必须有此命名,因此不能理解为对本发明的限制。
其中,所述第二网元可以被称为所述第一网元的备用网元,由EMS自动生成,且与所述第一网元具有相同的配置属性和连接属性,第二网元和第一网元处于不同的局域网内,通过虚拟局域网(Virtual Local Area Network,VLAN)或虚拟扩展局域网(Virtual eXtensible LAN,VXLAN)进行网络隔离,彼此不感知对方。由于,第二网元与第一网元具有相同的配置属性和连接属性,因此,对于而言,在网元无损升级过程中,不会感知到准备发送至第一网元的业务消息从第一网元切换至第二网元。
其中,所述第二网元可以被称为所述第一网元的备用网元,由EMS自动生成,且与所述第一网元具有相同的配置属性和连接属性,第二网元和第一网元处于不同的局域网内,通过虚拟局域网(Virtual Local Area Network,VLAN)进行网络隔离,彼此不感知对方。由于,第二网元与第一网元具有相同的配置属性和连接属性,因此,对于而言,在网元无损升级过程中,不会感知到准备发送至第一网元的业务消息从第一网元切换至第二网元。
其中,预设条件可以根据需要进行设定,本发明实施例对比不进行限定,本发明实施例对比不进行限定。若第二网元上的业务消息的处理结果满足预设条件,则表示第二网元可以同第一网元一样进行业务处理,即可以将第一网元的业务消息全部转发过来;若第二网元上的业务消息的处理结果不满足预设条件,则表示第二网元的处理能力还是很弱,不能同第一网元一样进行业务处理,即不能将第一网元的业务消息全部转发过来。
可选的,当SLB将多个业务消息转发至第二网元运行后,系统管理员会实时监测所述多个业务消息在第二网元上的运行情况,若满足预设条件,则表示第二网元正常升级;若不满足预设条件,则表示第二网元上的升级存在问题,需要对其进行修正。
需要说明的是,在第二网元上的业务运行情况没有满足预设条件之前,可以不断将部分业务消息转发至第二网元进行试运行,其中,每次转发至第二网元的业务消息的个数可以相等,也可以呈递增趋势,本发明实施例对比不进行限定。
可选的,因用户发出的业务消息可以有多种类型,如可以为:会话初始协议(Session Initiation Protocol,SIP)消息,还可以为:网络协议(Internet Protocol,IP)链路消息,所以,本发明实施例中,为了便于业务消息的分发,针对不同类型的业务消息,可以对应制定不同的分发策略,即EMS下发的分发策略中需包含:不同业务消息与分发该业务消息的策略的对应关系。所述分发单元具体用于:
判断接收到的多个业务消息中每个业务消息的消息类型;
若确定所述业务消息的消息类型为会话初始协议SIP消息,则根据所述SIP消息包含的用户标识、以及所述分发策略中的分发标识和白名单列表,将所述业务消息转发至所述第二网元或所述第一网元;其中,所述分发标识用于表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元、或将所述SLB接收到的多个业务消息全部转发至所述第二网元、或不确定将所述SLB接收到的多个业务消息转发至所述第一网元和所述第二网元中哪个网元;所述白名单列表用于存储至少一个用户标识;
若确定所述业务消息为IP链路消息,则根据所述IP链路消息包含的五元组信息、以及所述分发策略中逻辑链路的五元组属性与虚拟局域网标识VLAN ID的对应关系,将所述业务消息转发至所述第二网元或所述第一网元;
其中,所述五元组信息包含:所述外部网元的IP地址、所述外部网元的端口号、所述第一网元的IP地址、所述第一网元的端口号、传输协议类型;所述逻辑链路的五元组属性包含:源IP地址、源端口号、目的IP地址、目的端口号、传输协议类型;
若确定所述业务消息不是SIP消息和IP链路消息,则将所述业务消息转发至所述第二网元。
其中,为了便于所述分发单元判断所述业务消息的消息类型,如图6A所示,所述SLB60还可以包括:
发送单元603,用于在所述接收单元601接收发送的SLB接收到的多个业务消息全部之前,向所述第一网元发送同步请求消息,其中,所述同步请求消息用于请求获取所述第一网元的接口信息,所述第一网元的接口信息包含:所述第一网元的SIP服务端的IP地址及端口号,以及所述第一网元与所述间进行通信的逻辑链路的配置信息;
所述接收单元601,还用于接收并存储所述第一网元发送的接口信息。
所述分发单元,具体用于根据接收的所述第一网元的接口信息设定所述SLB自身对外的接口属性,所述接口属性包含:IP地址及端口号;将所述业务消息包含的接口信息与所述第一网元发送的接口消息进行匹配,判断所述业务消息的消息类型。
其中,在所述接收单元601接收到所述第一网元发送的接口信息后,会将接收到接口信息的时间戳与本地缓存的接口信息的时间戳进行比较,若从第一网元获取的接口信息的时间戳晚于本地存储信息的时间戳,则用新获取的接口信息替换本地存储的接口信息。同时,当用户在第一网元下发配置命令增加或修改第一网元的外部接口时,第一网元还会实时发送变更通知消息给SLB,SLB收到变更通知消息后更新本地的接口信息和分发策略等信息。
进一步的,所述分发单元602具体用于:
查询分发标识;
若确定所述分发标识表示:若确定所述分发标识表示:不确定将所述SLB接收到的多个业务消息转发至所述第二网元和所述第一网元中哪个网元,则查询所述白名单列表,若所述业务消息的用户标识包含在所述白名单列表中,则将所述业务消息转发至所述第二网元;若所述业务消息的用户标识未包含在所述白名单列表中,则将所述业务消息转发至所述第一网元;
若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第二网元,则将所述业务消息转发至所述第二网元;
若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元,则将所述业务消息转发至所述第一网元。
其中,所述分发标识可以为数字符号或其他形式的符号;本发明实施例对比不进行限定。例如,可以用分发标识“0”表示:不确定将所述SLB接收到的多个业务消息全部转发至所述第二网元和所述第一网元中哪个网,用分发标识“1”表示:将所述SLB接收到的多个业务消息全部转发至所述第二网元,用分发标识“2”表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元。
进一步的,所述分发单元602具体用于:
根据所述分发策略中逻辑链路与虚拟局域网标识VLAN ID的对应关系,确定与所述业务消息相对应的第一虚拟局域网标识VLAN ID;其中,所述第一VLAN ID用于标识第一虚拟局域网,所述第一虚拟局域网包含:所述第一网元或所述第二网元;
根据网元、以及所述网元所处的虚拟局域网的虚拟局域网标识VLAN ID之间的对应关系,将所述业务消息转发至与所述第一VLAN ID相对应的网元上。
其中,所述逻辑链路与虚拟局域网标识VLAN ID的对应关系用于控制转发至第二网元上的逻辑链路的个数,可以根据需要设置,本发明实施例对比不进行限定。当网元在升级过程中,用户在EMS上指定用户白名单时,系统根据白名单用户数与该局点总用户数的比例,并根据第一网元与周边网元对接的逻辑链路总数,换算成需要分发到新版本的第二网元的逻辑链路数,并将对应数量的逻辑链路的分发策略修改成分发到第二网元。例如:若第一网元的用户容量是10000,第一网元和周边网元(如)对接一共有四条链路,若希望将其中的2500个用户的呼叫分发到新版本的第二网元,则SLB会将其中的一条逻辑链路的业务消息转发第二网元,其余三条逻辑链路的业务消息仍然转发到第一网元上。
进一步的,本发明实施例提供,为了将系统内部网元发送的业务消息转发至外部网元,在接收到外部网元发送的响应消息后原路返回至发送端,所述接收单元601,还用于:
接收到所述第一网元或所述第二网元发送的第一业务消息;
所述分发单元602,还用于将所述第一业务消息中的源端口号进行修改,并将修改后的源端口号、以及所述源端口号和发送所述第一业务消息的网元所在的虚拟局域网标识VLAN ID的对应关系记录在第一关系表中;
将包含修改后的源端口号的第一业务消息转发至所述外部网元;
所述接收单元601,还用于接收所述外部网元回复的响应消息,其中,所述响应消息包含:目的端口号,所述目的端口号为:所述修改后的源端口号;
所述分发单元602,还用于查询所述第一关系表中,获取与所述目的端口号相对应的端口号和虚拟局域网标识VLAN ID;
将所述响应消息发送至所述虚拟局域网标识VLAN ID标识的虚拟局域网中的网元的所述端口号上;
其中,所述第一业务消息为非IP链路消息,包含:源IP地址、源端口号、目的IP地址、目的端口号。
需要说明的是,由于一条逻辑链路可以唯一确认通信双方,因此对于IP链路消息,在不进行端口修改、端口映射的方法下,也可以实现响应消息的原路返回,因此,本发明实施例中,所述第一业务消息仅为:非IP链路消息,可以包括:SIP消息、以及除SIP和IP链路消息之外的其他消息。
例如,第一网元处于VLAN1内,第二网元处于VLAN2中,二者具有共同的端口1002,此时,可以将第一网元的发出的源端口为1002的消息修改为端口号为31002,将第二网元发出的源端口为1002的消息修改为端口号为21002,并记录在表3中,若SLB接收到发送的目的端口号为21002的消息,则根据表3可知:将该消息发送至VLAN2内的第二网元的1002端口上,若SLB接收到发送的目的端口号为31002的消息,则根据表3可知:将该消息发送至VLAN1内的第一网元的1002端口上。
由上可知,本发明实施例提供一种SLB,接收EMS下发的分发策略,根据所述分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。如此,在网元升级过程中,通过SLB先将业务消息中的部分消息转发至第二网元进行试运行,当第二网元上的运行情况正常后,再将后续接收到的多个业务消息全部转发至第二网元,降低了网元升级过程中,全部业务切换至新网元,造成的整体业务受损的风险。同时,不改变现有网元系统架构,只是在网元外部增加新增了一个SLB模块,屏蔽了网元内部结构,通过在内部新增网元实例,并控制消息流在新老网元间的切换,保持了升级期间系统可靠性不降低,满足了电信级高可靠的要求。
实施例四
图7为本发明实施例提供的一种网元管理系统EMS70的结构图,如图7所示,所述EMS可以包括:
创建单元701,用于创建第二网元,其中,所述第二网元与第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,且所述第二网元的版本不低于所述第一网元。
其中,所述第二网元与第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,通过VLAN隔离,避免产生IP冲突,且所述第二网元的版本不低于所述第一网元。同时,在创建第二网元的过程中,并不感知整个变化。也不需要在上增加与第二网元的接口数据。
发送单元702,用于向SLB发送分发策略,以使得所述SLB根据所述分发策略,将接收到的多个业务消息中每个业务消息的消息类型;并当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。
其中,所述分发策略由管理员根据需要制定且通过EMS发送至SLB,可以用于:控制所述SLB将所述SLB接收到的多个业务消息转发至第一网元和第二网元的比例。
进一步的,所述创建单元701具体用于:
通过虚拟网络功能管理者VNFM命令所述第一网元所在的虚拟基础设施管理者VIM创建所述第一网元的虚拟机镜像文件;
命令所述VIM创建所述第一网元的虚拟机;
将所述第一网元虚拟机镜像文件植入创建的虚拟机内,形成所述第二网元。
进一步的,为了提高资源的利用率,本发明实施例中,新创建的第二网元是第一网元的最小功能集,当逐步加大对第二网元的业务消息分发时,第二网元通过弹性伸缩功能完成自动扩容,而第一网元由于业务量的下降,会自动完成缩容,如此,可以将第一网元缩容而释放的虚拟机挪到第二网元下使用,通过这种方式可以降低对基础设施资源的消耗;具体实现如下:
所述创建单元701,还用于根据所述第一网元上处理的业务消息减少的数量,减少所述第一网元的虚拟机资源;
直至所述SLB将接收到的多个业务消息全部转发至所述第二网元之后,撤销所述第一网元,释放所述第一网元中的虚拟机资源。
由上可知,本发明实施例提供一种网元升级EMS,创建第二网元,其中,所述第二网元与第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,且所述第二网元的版本不低于所述第一网元;向SLB发送分发策略,以使得所述SLB根据所述分发策略,将接收到的多个业务消息中每个业务消息的消息类型;并当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。如此,在网元升级过程中,通过SLB先将业务消息中的部分消息转发至第二网元进行试运行,当第二网元上的运行情况正常后,再将后续接收到的多个业务消息全部转发至第二网元,降低了网元升级过程中,全部业务切换至新网元,造成的整体业务受损的风险。
实施例五
图8为本发明实施例提供的一种网络负载均衡器SLB80的结构图,如图8所示,所述SLB80可以包括:可以包括:通信单元801,处理器802、存储器803、至少一个通信总线804,用于实现这些装置之间的连接和相互通信;
通信单元801,用于与外部网元之间进行数据传输。
处理器802可能是一个中央处理器(英文:central processing unit,简称为CPU)。
存储器803,可以是易失性存储器(英文:volatile memory),例如随机存取存储器(英文:random-access memory,缩写:RAM);或者非易失性存储器(英文:non-volatile memory),例如只读存储器(英文:read-only memory,缩写:ROM),快闪存储器(英文:flash memory),硬盘(英文:hard disk drive,缩写:HDD)或固态硬盘(英文:solid-state drive,缩写:SSD);或者上述种类的存储器的组合,并向处理器802提供指令和数据。
通信单元801,用于接收网元管理系统EMS下发的分发策略。
其中,所述分发策略由管理员根据需要制定且通过EMS发送至SLB,可以用于:控制所述SLB将所述SLB接收到的多个业务消息转发至第一网元和第二网元的比例。
处理器802,用于根据所述分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;
以及,当所述第二网元上的业务消息的处理结果满足预设条件后,根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。
其中,通信单元801接收到的多个业务消息为:所述外部网元接收到、准备发送至第一网元的至少一个用户发出的多个业务消息,如:可以包含M个业务消息,所述M为大于1的整数,每个业务消息包含:发起所述业务消息的用户的用户标识。
在云计算平台的网元升级场景下,所述外部网元和所述第一网元可以为虚拟网元;在非 云计算平台的网元升级下,外部网元和第一网元可以为物理网元。
需要说明的是,本发明实施例中的术语“第一”、“第二”、“另一”等指示的系统或元件或事物为基于实施例描述的具有一定功能的系统或元件或事物,仅是为了便于描述本发明和简化描述,而不是指示或暗示所指的系统或元件或事物必须有此命名,因此不能理解为对本发明的限制。
其中,所述第二网元可以被称为所述第一网元的备用网元,由EMS自动生成,且与所述第一网元具有相同的配置属性和连接属性,第二网元和第一网元处于不同的局域网内,通过虚拟局域网(Virtual Local Area Network,VLAN)或虚拟扩展局域网(Virtual eXtensible LAN,VXLAN)进行网络隔离,彼此不感知对方。由于,第二网元与第一网元具有相同的配置属性和连接属性,因此,对于而言,在网元无损升级过程中,不会感知到准备发送至第一网元的业务消息从第一网元切换至第二网元。
其中,所述第二网元可以被称为所述第一网元的备用网元,由EMS自动生成,且与所述第一网元具有相同的配置属性和连接属性,第二网元和第一网元处于不同的局域网内,通过虚拟局域网(Virtual Local Area Network,VLAN)进行网络隔离,彼此不感知对方。由于,第二网元与第一网元具有相同的配置属性和连接属性,因此,对于而言,在网元无损升级过程中,不会感知到准备发送至第一网元的业务消息从第一网元切换至第二网元。
其中,预设条件可以根据需要进行设定,本发明实施例对比不进行限定,本发明实施例对比不进行限定。若第二网元上的业务消息的处理结果满足预设条件,则表示第二网元可以同第一网元一样进行业务处理,即可以将第一网元的业务消息全部转发过来;若第二网元上的业务消息的处理结果不满足预设条件,则表示第二网元的处理能力还是很弱,不能同第一网元一样进行业务处理,即不能将第一网元的业务消息全部转发过来。
可选的,当SLB将多个业务消息转发至第二网元运行后,系统管理员会实时监测所述多个业务消息在第二网元上的运行情况,若满足预设条件,则表示第二网元正常升级;若不满足预设条件,则表示第二网元上的升级存在问题,需要对其进行修正。
需要说明的是,在第二网元上的业务运行情况没有满足预设条件之前,可以不断将部分业务消息转发至第二网元进行试运行,其中,每次转发至第二网元的业务消息的个数可以相等,也可以呈递增趋势,本发明实施例对比不进行限定。
可选的,因用户发出的业务消息可以有多种类型,如可以为:会话初始协议(Session Initiation Protocol,SIP)消息,还可以为:网络协议(Internet Protocol,IP)链路消息,所以,本发明实施例中,为了便于业务消息的分发,针对不同类型的业务消息,可以对应制定不同的分发策略,即EMS下发的分发策略中需包含:不同业务消息与分发该业务消息的策略的对应关系。所述分发单元具体用于:
判断接收到的多个业务消息中每个业务消息的消息类型;
若确定所述业务消息的消息类型为会话初始协议SIP消息,则根据所述SIP消息包含的用户标识、以及所述分发策略中的分发标识和白名单列表,将所述业务消息转发至所述第二网元或所述第一网元;其中,所述分发标识用于表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元、或将所述SLB接收到的多个业务消息全部转发至所述第二网元、或不确定将所述SLB接收到的多个业务消息转发至所述第一网元和所述第二网元中哪个网元;所述白名单列表用于存储至少一个用户标识;
若确定所述业务消息为IP链路消息,则根据所述IP链路消息包含的五元组信息、以及所述分发策略中逻辑链路的五元组属性与虚拟局域网标识VLAN ID的对应关系,将所述业务消息转发至所述第二网元或所述第一网元;
其中,所述五元组信息包含:所述外部网元的IP地址、所述外部网元的端口号、所述第一网元的IP地址、所述第一网元的端口号、传输协议类型;所述逻辑链路的五元组属性包含:源IP地址、源端口号、目的IP地址、目的端口号、传输协议类型;
若确定所述业务消息不是SIP消息和IP链路消息,则将所述业务消息转发至所述第二网元。
其中,为了便于所述分发单元判断所述业务消息的消息类型,所述通信单元801,还用于:
在所述通信单元801接收发送的SLB接收到的多个业务消息全部之前,向所述第一网元发送同步请求消息,其中,所述同步请求消息用于请求获取所述第一网元的接口信息,所述第一网元的接口信息包含:所述第一网元的SIP服务端的IP地址及端口号,以及所述第一网元与所述间进行通信的逻辑链路的配置信息;
所述通信单元801,还用于接收并存储所述第一网元发送的接口信息。
所述分发单元,具体用于根据接收的所述第一网元的接口信息设定所述SLB自身对外的接口属性,所述接口属性包含:IP地址及端口号;将所述业务消息包含的接口信息与所述第一网元发送的接口消息进行匹配,判断所述业务消息的消息类型。
其中,在所述通信单元801接收到所述第一网元发送的接口信息后,会将接收到接口信息的时间戳与本地缓存的接口信息的时间戳进行比较,若从第一网元获取的接口信息的时间戳晚于本地存储信息的时间戳,则用新获取的接口信息替换本地存储的接口信息。同时,当用户在第一网元下发配置命令增加或修改第一网元的外部接口时,第一网元还会实时发送变更通知消息给SLB,SLB收到变更通知消息后更新本地的接口信息和分发策略等信息。
进一步的,所述处理器802具体用于:
查询分发标识;
若确定所述分发标识表示:若确定所述分发标识表示:不确定将所述SLB接收到的多个业务消息转发至所述第二网元和所述第一网元中哪个网元,则查询所述白名单列表,若所述业务消息的用户标识包含在所述白名单列表中,则将所述业务消息转发至所述第二网元;若所述业务消息的用户标识未包含在所述白名单列表中,则将所述业务消息转发至所述第一网元;
若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第二网元,则将所述业务消息转发至所述第二网元;
若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元,则将所述业务消息转发至所述第一网元。
其中,所述分发标识可以为数字符号或其他形式的符号;本发明实施例对比不进行限定。例如,可以用分发标识“0”表示:不确定将所述SLB接收到的多个业务消息全部转发至所述第二网元和所述第一网元中哪个网,用分发标识“1”表示:将所述SLB接收到的多个业务消息全部转发至所述第二网元,用分发标识“2”表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元。
进一步的,所述处理器802具体用于:
根据所述分发策略中逻辑链路与虚拟局域网标识VLAN ID的对应关系,确定与所述业务消息相对应的第一虚拟局域网标识VLAN ID;其中,所述第一VLAN ID用于标识第一虚拟局域网,所述第一虚拟局域网包含:所述第一网元或所述第二网元;
根据网元、以及所述网元所处的虚拟局域网的虚拟局域网标识VLAN ID之间的对应关系,将所述业务消息转发至与所述第一VLAN ID相对应的网元上。
其中,所述逻辑链路与虚拟局域网标识VLAN ID的对应关系用于控制转发至第二网元上的逻辑链路的个数,可以根据需要设置,本发明实施例对比不进行限定。当网元在升级过程中,用户在EMS上指定用户白名单时,系统根据白名单用户数与该局点总用户数的比例,并根据第一网元与周边网元对接的逻辑链路总数,换算成需要分发到新版本的第二网元的逻辑链路数,并将对应数量的逻辑链路的分发策略修改成分发到第二网元。例如:若第一网元的用户容量是10000,第一网元和周边网元(如)对接一共有四条链路,若希望将其中的2500个用户的呼叫分发到新版本的第二网元,则SLB会将其中的一条逻辑链路的业务消息转发第二网元,其余三条逻辑链路的业务消息仍然转发到第一网元上。
进一步的,本发明实施例提供,为了将系统内部网元发送的业务消息转发至外部网元,在接收到外部网元发送的响应消息后原路返回至发送端,所述通信单元801,还用于:
接收到所述第一网元或所述第二网元发送的第一业务消息;
所述处理器802,还用于将所述第一业务消息中的源端口号进行修改,并将修改后的源端口号、以及所述源端口号和发送所述第一业务消息的网元所在的虚拟局域网标识VLAN ID的对应关系记录在第一关系表中;
将包含修改后的源端口号的第一业务消息转发至所述外部网元;
所述通信单元801,还用于接收所述外部网元回复的响应消息,其中,所述响应消息包含:目的端口号,所述目的端口号为:所述修改后的源端口号;
所述处理器802,还用于查询所述第一关系表中,获取与所述目的端口号相对应的端口号和虚拟局域网标识VLAN ID;
将所述响应消息发送至所述虚拟局域网标识VLAN ID标识的虚拟局域网中的网元的所述端口号上;
其中,所述第一业务消息为非IP链路消息,包含:源IP地址、源端口号、目的IP地址、目的端口号。
需要说明的是,由于一条逻辑链路可以唯一确认通信双方,因此对于IP链路消息,在不进行端口修改、端口映射的方法下,也可以实现响应消息的原路返回,因此,本发明实施例中,所述第一业务消息仅为:非IP链路消息,可以包括:SIP消息、以及除SIP和IP链路消息之外的其他消息。
例如,第一网元处于VLAN1内,第二网元处于VLAN2中,二者具有共同的端口1002,此时,可以将第一网元的发出的源端口为1002的消息修改为端口号为31002,将第二网元发出的源端口为1002的消息修改为端口号为21002,并记录在表3中,若SLB接收到发送的目的端口号为21002的消息,则根据表3可知:将该消息发送至VLAN2内的第二网元的1002端口上,若SLB接收到发送的目的端口号为31002的消息,则根据表3可知:将该消息发送至VLAN1内的第一网元的1002端口上。
由上可知,本发明实施例提供一种SLB,接收EMS下发的分发策略,根据所述分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。如此,在网元升级过程中,通过SLB先将业务消息中的部分消息转发至第二网元进行试运行,当第二网元上的运行情况正常后,再将后续接收到的多个业务消息全部转发至第二网元,降低了网元升级过程中,全部业务切换至新网元,造成的整体业务受损的风险。同时,不改变现有网元系统架构,只是在网元外部增加新增了一个SLB模块,屏蔽了网元内 部结构,通过在内部新增网元实例,并控制消息流在新老网元间的切换,保持了升级期间系统可靠性不降低,满足了电信级高可靠的要求。
实施例六
图9为本发明实施例提供的一种网元管理系统EMS90的结构图,如图9所示,所述EMS90可以包括:处理器901、通信单元902、存储器903、至少一个通信总线904,用于实现这些装置之间的连接和相互通信;
通信单元902,用于与外部网元之间进行数据传输。
处理器901可能是一个中央处理器(英文:central processing unit,简称为CPU)。
存储器903,可以是易失性存储器(英文:volatile memory),例如随机存取存储器(英文:random-access memory,缩写:RAM);或者非易失性存储器(英文:non-volatile memory),例如只读存储器(英文:read-only memory,缩写:ROM),快闪存储器(英文:flash memory),硬盘(英文:hard disk drive,缩写:HDD)或固态硬盘(英文:solid-state drive,缩写:SSD);或者上述种类的存储器的组合,并向处理器901提供指令和数据。
处理器901,用于创建第二网元,其中,所述第二网元与第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,且所述第二网元的版本不低于所述第一网元。
其中,所述第二网元与第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,通过VLAN隔离,避免产生IP冲突,且所述第二网元的版本不低于所述第一网元。同时,在创建第二网元的过程中,并不感知整个变化。也不需要在上增加与第二网元的接口数据。
通信单元902,用于向SLB发送分发策略,以使得所述SLB根据所述分发策略,将接收到的多个业务消息中每个业务消息的消息类型;并当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。
其中,所述分发策略由管理员根据需要制定且通过EMS发送至SLB,可以用于:控制所述SLB将所述SLB接收到的多个业务消息转发至第一网元和第二网元的比例。
进一步的,所述处理器901具体用于:
通过虚拟网络功能管理者VNFM命令所述第一网元所在的虚拟基础设施管理者VIM创建所述第一网元的虚拟机镜像文件;
命令所述VIM创建所述第一网元的虚拟机;
将所述第一网元虚拟机镜像文件植入创建的虚拟机内,形成所述第二网元。
进一步的,为了提高资源的利用率,本发明实施例中,新创建的第二网元是第一网元的最小功能集,当逐步加大对第二网元的业务消息分发时,第二网元通过弹性伸缩功能完成自动扩容,而第一网元由于业务量的下降,会自动完成缩容,如此,可以将第一网元缩容而释放的虚拟机挪到第二网元下使用,通过这种方式可以降低对基础设施资源的消耗;具体实现如下:
所述处理器901,还用于根据所述第一网元上处理的业务消息减少的数量,减少所述第一网元的虚拟机资源;
直至所述SLB将接收到的多个业务消息全部转发至所述第二网元之后,撤销所述第一网元,释放所述第一网元中的虚拟机资源。
由上可知,本发明实施例提供一种网元升级EMS,创建第二网元,其中,所述第二网元与第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,且所述第二网元的版本不低于所述第一网元;向SLB发送分发策略,以使得所述SLB根据所述分发策略,将接收到的多个业务消息中每个业务消息的消息类型;并当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。如此,在网元升级过程中,通过SLB先将业务消息中的部分消息转发至第二网元进行试运行,当第二网元上的运行情况正常后,再将后续接收到的多个业务消息全部转发至第二网元,降低了网元升级过程中,全部业务切换至新网元,造成的整体业务受损的风险。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统,设备和方法,可以通过其它的方式实现。例如,以上所描述的设备实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离设备说明的单元可以是或者也可以不是物理上分开的,作为单元显示的设备可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本发明各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理包括,也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现,也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元,可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可 以是个人计算机,服务器,或者网络设备等)执行本发明各个实施例所述方法的部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,简称ROM)、随机存取存储器(Random Access Memory,简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件(例如处理器)来完成,该程序可以存储于一计算机可读存储介质中,存储介质可以包括:只读存储器、随机存储器、磁盘或光盘等。
最后应说明的是:以上实施例仅用以说明本发明的技术方案,而非对其限制;尽管参照前述实施例对本发明进行了详细的说明,本领域的普通技术人员应当理解:其依然可以对前述各实施例所记载的技术方案进行修改,或者对其中部分技术特征进行等同替换;而这些修改或者替换,并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (22)

  1. 一种网元升级方法,其特征在于,所述方法包括:
    网络负载均衡器SLB接收网元管理系统EMS下发的分发策略;
    所述SLB根据所述分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;
    当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元;
    其中,所述分发策略用于控制转发至所述第一网元和所述第二网元的业务消息的比例;所述第二网元与所述第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,且所述第二网元的版本不低于所述第一网元。
  2. 根据权利要求1所述的方法,其特征在于,所述业务消息包含:发起业务消息的用户的用户标识;所述SLB根据所述分发策略,将接收到的外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元具体包括:
    所述SLB判断接收到的多个业务消息中每个业务消息的消息类型;
    若所述SLB确定所述业务消息的消息类型为会话初始协议SIP消息,则根据所述SIP消息包含的用户标识、以及所述分发策略中的分发标识和白名单列表,将所述业务消息转发至所述第一网元或所述第二网元,其中,所述分发标识用于表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元、或将所述SLB接收到的多个业务消息全部转发至所述第二网元、或不确定将所述SLB接收到的多个业务消息转发至所述第一网元和所述第二网元中哪个网元;所述白名单列表用于存储至少一个用户标识;
    若所述SLB确定所述业务消息为IP链路消息,则根据所述IP链路消息包含的五元组信息、以及所述分发策略中逻辑链路的五元组属性与虚拟局域网标识VLAN ID的对应关系,将所述业务消息转发至所述第一网元或所述第二网元;
    其中,所述五元组信息包含:所述外部网元的IP地址、所述外部网元的端口号、所述第一网元的IP地址、所述第一网元的端口号、传输协议类型;所述逻辑链路的五元组属性包含:源IP地址、源端口号、目的IP地址、目的端口号、传输协议类型。
  3. 根据权利要求2所述的方法,其特征在于,所述SLB根据所述SIP消息包含的用户标识、以及所述分发策略中的分发标识和白名单列表,将所述业务消息转发至所述第二网元或所述第一网元具体包括:
    所述SLB查询分发标识;
    若确定所述分发标识表示:不确定将所述SLB接收到的多个业务消息转发至所述第二网元和所述第一网元中哪个网元,则查询所述白名单列表,若所述业务消息的用户标识包含在所述白名单列表中,则将所述业务消息转发至所述第二网元;若所述业务消息的用户标识未包含在所述白名单列表中,则将所述业务消息转发至所述第一网元;
    若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第二网元,则将所述业务消息转发至所述第二网元;
    若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元,则将所述业务消息转发至所述第一网元。
  4. 根据权利要求2所述的方法,其特征在于,所述SLB根据所述IP链路消息包含的五元组信息、以及所述分发策略中逻辑链路的五元组属性与虚拟局域网标识VLAN ID的对应关系,将所述业务消息转发至所述第二网元或所述第一网元具体包括:
    根据所述分发策略中逻辑链路与虚拟局域网标识VLAN ID的对应关系,确定与所述业务消息相对应的第一虚拟局域网标识VLAN ID;其中,所述第一VLAN ID用于标识第一虚拟局域网,所述第一虚拟局域网包含:所述第一网元或所述第二网元;
    根据网元、以及所述网元所处的虚拟局域网的虚拟局域网标识VLAN ID之间的对应关系,将所述业务消息转发至与所述第一VLAN ID相对应的网元上。
  5. 根据权利要求2-4任一项所述的方法,其特征在于,在所述SLB接收EMS下发的分发策略之前,所述方法还包括:
    所述SLB向所述第一网元发送同步请求消息,其中,所述同步请求消息用于请求获取所述第一网元的接口信息,所述第一网元的接口信息包含:所述第一网元的SIP服务端的IP地址及端口号,以及所述第一网元与所述间进行通信的逻辑链路的配置信息;
    所述SLB接收并存储所述第一网元的接口信息,并根据接收的所述第一网元的接口信息设定所述SLB自身对外的接口属性,所述接口属性包含:IP地址及端口号;
    相应的,所述SLB判断接收到的多个业务消息中每个业务消息的消息类型具体包括:
    根据所述业务消息包含的接口信息、所述第一网元的接口消息,判断所述业务消息的消息类型。
  6. 根据权利要求1所述的方法,其特征在于,所述方法还包括:
    若所述SLB接收到所述第一网元或所述第二网元发送的第一业务消息,则将所述第一业务消息中的源端口号进行修改,并将修改后的源端口号、以及所述源端口号和发送所述第一 业务消息的网元所在的虚拟局域网标识VLAN ID的对应关系记录在第一关系表中;
    将包含修改后的源端口号的第一业务消息转发至所述外部网元;
    接收所述外部网元回复的响应消息,其中,所述响应消息包含:目的端口号,所述目的端口号为:所述修改后的源端口号;
    查询所述第一关系表中,获取与所述目的端口号相对应的端口号和虚拟局域网标识VLANID;
    将所述响应消息发送至所述虚拟局域网标识VLAN ID标识的虚拟局域网中的网元的所述端口号上;
    其中,所述第一业务消息为非IP链路消息,包含:源IP地址、源端口号、目的IP地址、目的端口号。
  7. 根据权利要求1-6任一项所述的方法,其特征在于,所述第二网元上的业务消息的处理结果满足预设条件包括:所述第二网元上所有业务消息呼叫成功;或者
    所述第二网元上所有业务消息的测试用例的成功率大于等于预设阈值。
  8. 一种网元升级方法,应用于网元管理系统EMS,其特征在于,包括:
    所述EMS创建第二网元,其中,所述第二网元与第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网标识VLAN ID内,且所述第二网元的版本不低于所述第一网元;
    所述EMS向SLB发送分发策略;
    所述SLB根据所述分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;并当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。
  9. 根据权利要求8所述的方法,其特征在于,所述EMS创建第二网元具体包括:
    所述EMS通过虚拟网络功能管理者VNFM命令所述第一网元所在的虚拟基础设施管理者VIM创建所述第一网元的虚拟机镜像文件;
    所述EMS命令所述VIM创建所述第一网元的虚拟机;
    所述EMS将所述第一网元虚拟机镜像文件植入创建的虚拟机内,形成所述第二网元。
  10. 根据权利要求8或9所述的方法,其特征在于,所述方法还包括:
    所述EMS根据所述第一网元上处理的业务消息减少的数量,减少所述第一网元的虚拟机资 源;
    直至所述SLB将后续接收到的多个业务消息全部转发至所述第二网元之后,所述EMS撤销所述第一网元,释放所述第一网元中的虚拟机资源。
  11. 根据权利要求8-10任一项所述的方法,其特征在于,所述第二网元上的业务消息的处理结果满足预设条件包括:所述第二网元上所有业务消息呼叫成功;或者
    所述第二网元上所有业务消息的测试用例的成功率大于等于预设阈值。
  12. 一种网络负载均衡器SLB,其特征在于,包括:
    接收单元,用于接收网元管理系统EMS下发的分发策略;
    分发单元,用于根据所述接收单元接收到的分发策略,将接收到的由外部网元发送的多个业务消息中的一部分业务消息转发至第一网元,将剩余部分的业务消息转发至第二网元;
    以及,当所述第二网元上的业务消息的处理结果满足预设条件后,根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元;
    其中,所述分发策略用于控制转发至所述第一网元和所述第二网元的业务消息的比例;所述第二网元与所述第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,且所述第二网元的版本不低于所述第一网元。
  13. 根据权利要求12所述的SLB,其特征在于,所述业务消息包含:发起业务消息的用户的用户标识;所述分发单元具体用于:
    判断接收到的多个业务消息中每个业务消息的消息类型;
    若确定所述业务消息的消息类型为会话初始协议SIP消息,则根据所述SIP消息包含的用户标识、以及所述分发策略中的分发标识和白名单列表,将所述业务消息转发至所述第一网元或所述第二网元,其中,所述分发标识用于表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元、或将所述SLB接收到的多个业务消息全部转发至所述第二网元、或不确定将所述SLB接收到的多个业务消息转发至所述第一网元和所述第二网元中哪个网元;所述白名单列表用于存储至少一个用户标识;
    若确定所述业务消息为IP链路消息,则根据所述IP链路消息包含的五元组信息、以及所述分发策略中逻辑链路的五元组属性与虚拟局域网标识VLAN ID的对应关系,将所述业务消息转发至所述第一网元或所述第二网元;
    其中,所述五元组信息包含:所述外部网元的IP地址、所述外部网元的端口号、所述第一网元的IP地址、所述第一网元的端口号、传输协议类型;所述逻辑链路的五元组属性包含:源IP地址、源端口号、目的IP地址、目的端口号、传输协议类型。
  14. 根据权利要求13所述的SLB,其特征在于,所述分发单元具体用于:
    查询分发标识;
    若确定所述分发标识表示:不确定将所述SLB接收到的多个业务消息转发至所述第二网元和所述第一网元中哪个网元,则查询所述白名单列表,若所述业务消息的用户标识包含在所述白名单列表中,则将所述业务消息转发至所述第二网元;若所述业务消息的用户标识未包含在所述白名单列表中,则将所述业务消息转发至所述第一网元;
    若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第二网元,则将所述业务消息转发至所述第二网元;
    若确定所述分发标识表示:将所述SLB接收到的多个业务消息全部转发至所述第一网元,则将所述业务消息转发至所述第一网元。
  15. 根据权利要求13所述的SLB,其特征在于,所述分发单元具体用于:
    根据所述分发策略中逻辑链路与虚拟局域网标识VLAN ID的对应关系,确定与所述业务消息相对应的第一虚拟局域网标识VLAN ID;其中,所述第一VLAN ID用于标识第一虚拟局域网,所述第一虚拟局域网包含:所述第一网元或所述第二网元;
    根据网元、以及所述网元所处的虚拟局域网的虚拟局域网标识VLAN ID之间的对应关系,将所述业务消息转发至与所述第一VLAN ID相对应的网元上。
  16. 根据权利要求12-15任一项所述的SLB,其特征在于,所述SLB还包括:
    发送单元,用于在所述接收单元接收EMS下发的分发策略之前,向所述第一网元发送同步请求消息,其中,所述同步请求消息用于请求获取所述第一网元的接口信息,所述第一网元的接口信息包含:所述第一网元的SIP服务端的IP地址及端口号,以及所述第一网元与所述间进行通信的逻辑链路的配置信息;
    所述接收单元,还用于接收并存储所述第一网元发送的接口信息;
    所述分发单元,具体用于根据接收的所述第一网元的接口信息设定所述SLB自身对外的接口属性,所述接口属性包含:IP地址及端口号;
    根据所述业务消息包含的接口信息、所述第一网元的接口消息,判断所述业务消息的消息类型。
  17. 根据权利要求12所述的SLB,其特征在于,
    所述接收单元,还用于接收到所述第一网元或所述第二网元发送的第一业务消息;
    所述分发单元,还用于将所述第一业务消息中的源端口号进行修改,并将修改后的源端口号、以及所述源端口号和发送所述第一业务消息的网元所在的虚拟局域网标识VLAN ID的 对应关系记录在第一关系表中;
    将包含修改后的源端口号的第一业务消息转发至所述外部网元;
    接收所述外部网元回复的响应消息,其中,所述响应消息包含:目的端口号,所述目的端口号为:所述修改后的源端口号;
    查询所述第一关系表中,获取与所述目的端口号相对应的端口号和虚拟局域网标识VLANID;
    将所述响应消息发送至所述虚拟局域网标识VLAN ID标识的虚拟局域网中的网元的所述端口号上;
    其中,所述第一业务消息为非IP链路消息,包含:源IP地址、源端口号、目的IP地址、目的端口号。
  18. 根据权利要求12-17任一项所述的SLB,其特征在于,所述预设条件为下述一种或多种情况:
    所述第二网元上所有业务消息呼叫成功;
    所述第二网元上所有业务消息的测试用例的成功率大于等于预设阈值。
  19. 一种网元管理系统EMS,其特征在于,包括:
    创建单元,用于创建第二网元,其中,所述第二网元与第一网元的配置属性和连接配置相同,所述第二网元与所述第一网元处于不同的虚拟局域网内,且所述第二网元的版本不低于所述第一网元;
    发送单元,用于向SLB发送分发策略,以使得所述SLB根据所述分发策略,将接收到的多个业务消息中每个业务消息的消息类型;并当所述第二网元上的业务消息的处理结果满足预设条件后,所述SLB根据所述分发策略,将后续接收到的由外部网元发送的多个业务消息全部转发至所述第二网元。
  20. 根据权利要求19所述的EMS,其特征在于,所述创建单元具体用于:
    通过虚拟网络功能管理者VNFM命令所述第一网元所在的虚拟基础设施管理者VIM创建所述第一网元的虚拟机镜像文件;
    命令所述VIM创建所述第一网元的虚拟机;
    将所述第一网元虚拟机镜像文件植入创建的虚拟机内,形成所述第二网元。
  21. 根据权利要求19或20所述的EMS,其特征在于,所述创建单元,还用于:
    根据所述第一网元上处理的业务消息减少的数量,减少所述第一网元的虚拟机资源;
    直至所述SLB将后续接收到的多个业务消息全部转发至所述第二网元之后,撤销所述第一网元,释放所述第一网元中的虚拟机资源。
  22. 根据权利要求19-21任一项所述的EMS,其特征在于,所述第二网元上的业务消息的处理结果满足预设条件包括:所述第二网元上所有业务消息呼叫成功;或者
    所述第二网元上所有业务消息的测试用例的成功率大于等于预设阈值。
PCT/CN2016/094416 2015-09-02 2016-08-10 一种网元升级方法及设备 WO2017036288A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP16840717.9A EP3337097B1 (en) 2015-09-02 2016-08-10 Network element upgrading method and device
US15/909,587 US10601656B2 (en) 2015-09-02 2018-03-01 Network element upgrade method and device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510556227.9 2015-09-02
CN201510556227.9A CN105099789B (zh) 2015-09-02 2015-09-02 一种网元升级方法及设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/909,587 Continuation US10601656B2 (en) 2015-09-02 2018-03-01 Network element upgrade method and device

Publications (1)

Publication Number Publication Date
WO2017036288A1 true WO2017036288A1 (zh) 2017-03-09

Family

ID=54579405

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/094416 WO2017036288A1 (zh) 2015-09-02 2016-08-10 一种网元升级方法及设备

Country Status (4)

Country Link
US (1) US10601656B2 (zh)
EP (1) EP3337097B1 (zh)
CN (1) CN105099789B (zh)
WO (1) WO2017036288A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107528847A (zh) * 2017-09-01 2017-12-29 天津赞普科技股份有限公司 一种基于mac分流的保护方法
CN110690990A (zh) * 2019-09-02 2020-01-14 视联动力信息技术股份有限公司 一种服务器升级的方法及装置、电子设备、存储介质

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105099789B (zh) * 2015-09-02 2018-03-16 华为技术有限公司 一种网元升级方法及设备
US11418383B2 (en) * 2016-01-08 2022-08-16 Apple Inc. Techniques for instantiation and termination of virtualized network functions
WO2017185303A1 (zh) * 2016-04-28 2017-11-02 华为技术有限公司 一种nfv mano策略描述符的管理方法及装置
CN106231613B (zh) * 2016-07-27 2020-02-14 华为技术有限公司 一种分发策略生成方法、装置及网络优化系统
CN107770067B (zh) * 2016-08-23 2021-05-11 中兴通讯股份有限公司 消息发送方法和装置
US10439882B2 (en) * 2016-11-15 2019-10-08 T-Mobile Usa, Inc. Virtualized networking application and infrastructure
CN108287746B (zh) * 2017-01-09 2021-04-16 大唐移动通信设备有限公司 一种对epc网元的虚拟资源扩容或缩容的方法及装置
CN109474522B (zh) * 2017-09-07 2021-02-23 华为技术有限公司 业务路由的方法、装置及存储介质
US10742532B2 (en) 2017-12-18 2020-08-11 Futurewei Technologies, Inc. Non-intrusive mechanism to measure network function packet processing delay
EP3729725A1 (en) * 2017-12-21 2020-10-28 Telefonaktiebolaget Lm Ericsson (Publ) Agent, server, core network node and methods therein for handling an event of a network service deployed in a cloud environment
CN110018877B (zh) * 2018-01-08 2021-09-28 普天信息技术有限公司 按照亲和性原则快速实例化vnf的方法及装置
CN111385181B (zh) * 2018-12-29 2021-05-04 华为技术有限公司 一种实例化方法及装置
CN111443985A (zh) * 2019-01-17 2020-07-24 华为技术有限公司 实例化虚拟网络功能的方法及设备
CN110022357A (zh) * 2019-03-11 2019-07-16 潘洪安 数据访问方法及数据访问装置
CN110572284B (zh) * 2019-08-30 2022-05-13 华为云计算技术有限公司 一种虚拟网元的升级方法、装置及系统
CN111404979B (zh) * 2019-09-29 2023-04-07 杭州海康威视系统技术有限公司 业务请求处理的方法、装置及计算机可读存储介质
CN110880988B (zh) * 2019-11-14 2024-04-16 国家电网有限公司 网管系统升级方法及装置
CN111147520B (zh) * 2019-12-31 2022-02-25 奇安信科技集团股份有限公司 由防火墙执行的信息处理方法和装置
CN111756776B (zh) * 2020-07-28 2023-03-24 支付宝(杭州)信息技术有限公司 服务器、报文分配设备、程序交接系统以及程序交接的方法
CN113542019B (zh) * 2021-06-30 2023-12-29 新华三大数据技术有限公司 转控分离分布式cp的升级方法及系统

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101801029A (zh) * 2009-02-06 2010-08-11 华为技术有限公司 小区管理方法、装置和系统
US20120047244A1 (en) * 2009-05-07 2012-02-23 Zte Corporation Distributed Network Management System, Network Element Management Server, and Data Configuration Management Method
CN103889002A (zh) * 2012-12-20 2014-06-25 中兴通讯股份有限公司 流控方法及装置、移动节点、接入网关
CN103997414A (zh) * 2013-02-18 2014-08-20 华为技术有限公司 生成配置信息的方法和网络控制单元
CN104320812A (zh) * 2014-10-13 2015-01-28 中国联合网络通信集团有限公司 一种联合传输的方法、装置及系统
CN105099789A (zh) * 2015-09-02 2015-11-25 华为技术有限公司 一种网元升级方法及设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8458467B2 (en) * 2005-06-21 2013-06-04 Cisco Technology, Inc. Method and apparatus for adaptive application message payload content transformation in a network infrastructure element
CN100583820C (zh) * 2006-09-11 2010-01-20 思华科技(上海)有限公司 内容分发网络的路由系统及方法
ES2344318T3 (es) * 2006-10-16 2010-08-24 Fundacio Privada Centre Tecnologic De Telecomunicacions De Catalunya Procedimiento para el despliegue, repliegue y control logicos de una red ip objetivo.
CN101170452A (zh) * 2007-11-30 2008-04-30 中国电信股份有限公司 增强管理能力的内容分发网络业务提供点系统及所属网络
CN101222424B (zh) * 2007-12-24 2011-02-09 中国电信股份有限公司 内容分发网络和该网络中基于内容的调度方法
CN101820606B (zh) * 2010-04-21 2014-04-09 中兴通讯股份有限公司 认证授权计费服务器及其消息处理方法
US9571507B2 (en) * 2012-10-21 2017-02-14 Mcafee, Inc. Providing a virtual security appliance architecture to a virtual cloud infrastructure
US8929856B1 (en) * 2014-02-07 2015-01-06 Cassidian Communications, Inc. Emergency services routing proxy cluster management
US9935882B2 (en) * 2015-05-13 2018-04-03 Cisco Technology, Inc. Configuration of network elements for automated policy-based routing

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101801029A (zh) * 2009-02-06 2010-08-11 华为技术有限公司 小区管理方法、装置和系统
US20120047244A1 (en) * 2009-05-07 2012-02-23 Zte Corporation Distributed Network Management System, Network Element Management Server, and Data Configuration Management Method
CN103889002A (zh) * 2012-12-20 2014-06-25 中兴通讯股份有限公司 流控方法及装置、移动节点、接入网关
CN103997414A (zh) * 2013-02-18 2014-08-20 华为技术有限公司 生成配置信息的方法和网络控制单元
CN104320812A (zh) * 2014-10-13 2015-01-28 中国联合网络通信集团有限公司 一种联合传输的方法、装置及系统
CN105099789A (zh) * 2015-09-02 2015-11-25 华为技术有限公司 一种网元升级方法及设备

Non-Patent Citations (1)

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

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107528847A (zh) * 2017-09-01 2017-12-29 天津赞普科技股份有限公司 一种基于mac分流的保护方法
CN107528847B (zh) * 2017-09-01 2020-10-27 天津赞普科技股份有限公司 一种基于mac分流的保护方法
CN110690990A (zh) * 2019-09-02 2020-01-14 视联动力信息技术股份有限公司 一种服务器升级的方法及装置、电子设备、存储介质
CN110690990B (zh) * 2019-09-02 2022-06-21 视联动力信息技术股份有限公司 一种服务器升级的方法及装置、电子设备、存储介质

Also Published As

Publication number Publication date
CN105099789A (zh) 2015-11-25
US20180191561A1 (en) 2018-07-05
EP3337097A4 (en) 2018-06-20
EP3337097A1 (en) 2018-06-20
US10601656B2 (en) 2020-03-24
EP3337097B1 (en) 2020-05-06
CN105099789B (zh) 2018-03-16

Similar Documents

Publication Publication Date Title
WO2017036288A1 (zh) 一种网元升级方法及设备
US11895154B2 (en) Method and system for virtual machine aware policy management
US8774054B2 (en) Network policy configuration method, management device, and network management center device
US10063470B2 (en) Data center network system based on software-defined network and packet forwarding method, address resolution method, routing controller thereof
US9999030B2 (en) Resource provisioning method
US10644952B2 (en) VNF failover method and apparatus
US20210326167A1 (en) Vnf service instantiation method and apparatus
WO2016107418A1 (zh) 云化网络通信路径的分配方法、装置及系统
EP3373518B1 (en) Service configuration method and device for network service
WO2015172362A1 (zh) 一种网络功能虚拟化网络系统、数据处理方法及装置
US11218956B2 (en) Network management method and system
US20140068045A1 (en) Network system and virtual node migration method
WO2016054922A1 (zh) 决策协调方法、执行装置和决策协调器
CN110572439B (zh) 一种基于元数据服务和虚拟转发网桥的云监控方法
WO2018010555A1 (zh) 一种北向接口lte业务自动配置方法、北向接口装置及存储介质
US10462048B2 (en) Virtual cluster establishment method and network device
KR20170114923A (ko) 네트워크 슬라이스를 이용한 통신 방법 및 통신 장치
WO2017162030A1 (zh) 一种虚拟网络的生成方法和装置
WO2020057445A1 (zh) 一种通信系统、方法及装置
US20230156828A1 (en) Session establishment method and apparatus, system, and computer storage medium
US20220350637A1 (en) Virtual machine deployment method and related apparatus
US20220286409A1 (en) Method and apparatus for configuring quality of service policy for service, and computing device
WO2020181733A1 (zh) 一种基于vpc的多数据中心互通方法及相关设备
EP4191907A1 (en) Vnf instantiation method and apparatus
US20190028880A1 (en) Method for accessing context data by network service component, apparatus, and system

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: 16840717

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2016840717

Country of ref document: EP