WO2019047821A1 - 业务路由的方法、装置及存储介质 - Google Patents

业务路由的方法、装置及存储介质 Download PDF

Info

Publication number
WO2019047821A1
WO2019047821A1 PCT/CN2018/103936 CN2018103936W WO2019047821A1 WO 2019047821 A1 WO2019047821 A1 WO 2019047821A1 CN 2018103936 W CN2018103936 W CN 2018103936W WO 2019047821 A1 WO2019047821 A1 WO 2019047821A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
grayscale
vnf
upgraded
service
Prior art date
Application number
PCT/CN2018/103936
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 华为技术有限公司
Publication of WO2019047821A1 publication Critical patent/WO2019047821A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/58—Association of routers
    • H04L45/586—Association of routers of virtual routers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/30—Routing of multiclass traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/302—Route determination based on requested QoS
    • H04L45/308—Route determination based on user's profile, e.g. premium users

Definitions

  • the present application relates to the field of communications technologies, and in particular, to a method, an apparatus, and a storage medium for service routing.
  • NFV Network Function Virtualization
  • NFV's system framework mainly includes NFV management and orchestration (MANO), multiple virtual network functions (VNF), and multiple element management (EM).
  • the NFV-MANO includes NFV Orchestrator (NFVO) and VNF Manager (VNFM).
  • NFVO NFV Orchestrator
  • VNFM VNF Manager
  • the NFVO, VNFM, and EM can all be used to manage the VNF.
  • Each VNF can be configured to implement network functions of the network element in the communication network.
  • the network element can be a Call Session Control Function (CSCF) or a Home Subscriber Server (Home Subscriber Server). HSS), etc.
  • CSCF Call Session Control Function
  • HSS Home Subscriber Server
  • multiple VNFs with different network functions are usually required to cooperate with each other to implement network services.
  • the VNF is usually upgraded due to service requirements.
  • the grayscale upgrade can be used to upgrade.
  • Grayscale upgrade refers to grayscale verification while upgrading, that is, first upgrade some parts of each VNF or some VNFs of multiple VNFs with the same network function, and then perform grayscale verification. After the verification is passed, the partial upgrade and grayscale verification are continued.
  • the gray-scale verification refers to migrating the services of some users to the upgraded VNF according to a certain strategy.
  • the part of the user is referred to as a gray-scale user, and the gray-scale user performs gray-scale verification on the upgraded VNF.
  • the present application provides a service routing method, apparatus, and storage medium for solving the problem of how to perform gray scale verification in the prior art.
  • the technical solution is as follows:
  • the first aspect provides a service routing method, which is applied to a VNF, where the VNF includes different upgraded and upgraded different subsystem modules having the same function, and the method includes:
  • the service requested by the service request is routed to the upgraded subsystem module in the VNF.
  • the VNF in order to determine which users need to be selected to use the upgraded subsystem module in the VNF, when receiving a service request from the user, it is necessary for the VNF to determine whether the user is a grayscale user.
  • the VNF may determine whether the user is a grayscale user according to a grayscale policy description file sent by the grayscale policy control center.
  • the gray-scale user is determined by the front-end network element VNF when receiving the service request from the user, and the gray-scale verification is performed on the upgraded subsystem module.
  • the method further includes:
  • the determining whether the user is a grayscale user comprises:
  • Whether the user is a grayscale user is determined according to the grayscale percentage.
  • the grayscale policy control center in order to facilitate the VNF to determine which users need to be determined as grayscale users, the grayscale policy control center generally sends a grayscale policy description file to the VNF in advance to pass the grayscale policy description file. Inform the VNF of the grayscale strategy determined.
  • the VNF determines, according to the grayscale percentage, whether the user is a grayscale user.
  • the gray policy control center sends a grayscale policy description file to the VNF in advance to notify the VNF of the grayscale policy by the grayscale policy description file, and when the grayscale policy description file includes the grayscale percentage, The VNF can be caused to determine whether the user is a grayscale user based on the grayscale percentage.
  • the determining, according to the grayscale percentage, whether the user is a grayscale user includes:
  • the selected user is determined to be the grayscale user.
  • the VNF may determine the i-th user of each preset number of online users as a gray-scale user, thereby determining whether the user is a gray-scale user according to the grayscale percentage.
  • the method further includes:
  • the service request is sent to the next VNF, and the service request is used to indicate that the next VNF determines the user as the grayscale user.
  • the VNF may add a grayscale identifier to the service request and send it to the next VNF before sending the service request to the next VNF.
  • the service request is to indicate to the next VNF that the user is determined to be the grayscale user.
  • the method further includes:
  • the next VNF When the next VNF is an unupgraded VNF and there is an upgraded VNF having the same function, the next VNF redirects the service requested by the user's registration request from the unupgraded VNF. To the upgraded VNF.
  • next VNF routes the same user's service to the upgraded VNF, enabling grayscale verification of the upgraded VNF.
  • the method further includes:
  • the next VNF When the next VNF includes different subsystem modules that are not upgraded and upgraded and have the same function, the next VNF routes the service requested by the service request to the upgraded subsystem in the next VNF Module.
  • each VNF routes the same user's service to the upgraded subsystem module, and achieves coordinated grayscale verification between the VNFs.
  • the method further includes:
  • determining whether the user is a grayscale user includes:
  • the grayscale policy control center has directly specified which users belong to the grayscale user.
  • the VNF receives the service request from the user, determining whether the user is a grayscale user according to the range of users included in the grayscale policy description file.
  • the service request may carry the user identity information of the user.
  • the user identity information may include a phone number used by the user or location information currently used by the user.
  • the VNF queries whether the user identity information belongs to the user scope, and if so, determines that the user is a grayscale user. In this way, the problem that the different VNFs can cooperate in grayscale verification when communicating across different VNFs is solved.
  • the user range includes a location range, a number segment, or a list of numbers.
  • the location range refers to a range of locations where the user is located.
  • the location range may be A city; the number segment is used to indicate that one or some of the phone numbers used by the user meet certain rules.
  • the number segment may refer to the fourth to seventh digits of the telephone number being in the range of 0100 to 0112.
  • the number segment may also mean that the last digit of the telephone number is an even number, etc.; For storing the phone number of the user who belongs to the grayscale user.
  • the grayscale policy control center can directly specify and inform the VNF which users are grayscale users through the location range, the number segment or the number list, so that each VNF cooperates to implement grayscale verification.
  • an apparatus for service routing configured in a VNF, where the VNF includes different subsystem modules having the same function that are not upgraded and upgraded, and the apparatus includes:
  • a determining module configured to determine whether the user is a grayscale user when receiving a service request from a user
  • the routing module is configured to, when determining that the user is the grayscale user, route the service requested by the service request to the upgraded subsystem module in the VNF.
  • the device further includes:
  • a first receiving module configured to receive a grayscale policy description file sent by the grayscale policy control center, where the grayscale policy description file includes a grayscale percentage
  • the determining module is further configured to:
  • Whether the user is a grayscale user is determined according to the grayscale percentage.
  • the determining module is configured to:
  • the selected user is determined to be the grayscale user.
  • the device further includes:
  • Adding a module when determining that the user is the grayscale user, adding a grayscale identifier to the service request;
  • a sending module configured to send the service request to the next VNF, where the service request is used to indicate that the next VNF determines the user as the grayscale user.
  • next VNF when the next VNF is an un-upgraded VNF, and an upgraded VNF having the same function exists, the next VNF sends the service requested by the user's registration request from the un-upgraded The VNF redirects routes to the upgraded VNF.
  • next VNF sends the service request
  • the next VNF includes different subsystem modules that are not upgraded and upgraded and have the same function
  • the next VNF sends the service request
  • the requested service is routed to the upgraded subsystem modules in the next VNF.
  • the device further includes:
  • a second receiving module configured to receive a grayscale policy description file sent by the grayscale policy control center, where the grayscale policy description file includes a user range that belongs to the grayscale user;
  • the determining module is further configured to:
  • the user range includes a location range, a number segment, or a list of numbers.
  • a third aspect provides a service routing apparatus, where the structure of the service routing apparatus includes a processor and a memory, where the memory is used to store a program for supporting a service routing apparatus to perform the service routing method provided by the foregoing first aspect, And storing data involved in implementing the service routing method provided by the first aspect above.
  • the processor is configured to execute a program stored in the memory.
  • the operating device of the storage device may further include a communication bus for establishing a connection between the processor and the memory.
  • a computer readable storage medium is provided, the instructions being stored in the computer readable storage medium, when executed on a computer, causing the computer to perform the service routing method of the first aspect described above.
  • a computer program product comprising instructions for causing a computer to perform the service routing method of the first aspect described above when executed on a computer is provided.
  • the technical solution provided by the present application has the beneficial effects that the service routing method provided by the embodiment of the present invention is applied to the VNF, and the VNF includes different subsystem modules with the same function that have not been upgraded and upgraded.
  • the VNF determines whether the user is a grayscale user. If the user is a grayscale user, the user's traffic is routed to the upgraded subsystem module in the VNF. In this way, the VNF determines the grayscale user when receiving the service request from the user, and implements grayscale verification on the upgraded subsystem module.
  • FIG. 1 is a schematic diagram of an NFV system architecture, according to an exemplary embodiment
  • FIG. 2 is a schematic diagram of a system architecture, according to an exemplary embodiment
  • FIG. 3 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of a method for service routing according to an exemplary embodiment
  • FIG. 5 is a flowchart of a method for service routing according to another exemplary embodiment
  • FIG. 6 is a flowchart of a method for service routing according to another exemplary embodiment
  • FIG. 7A is a schematic structural diagram of a service routing apparatus according to an exemplary embodiment
  • FIG. 7B is a schematic structural diagram of another service routing apparatus according to an exemplary embodiment.
  • FIG. 7C is a schematic structural diagram of another service routing apparatus according to an exemplary embodiment.
  • FIG. 7D is a schematic structural diagram of another service routing apparatus according to an exemplary embodiment.
  • the embodiment of the present invention mainly implements the network communication service through the NFV system architecture. Therefore, before the detailed description of the service routing method in the embodiment of the present invention, the NFV system architecture is briefly introduced.
  • FIG. 1 is a schematic diagram of an NFV system architecture that can be applied to various types of networks, for example, to a carrier communication network or a local area network, according to an exemplary embodiment.
  • Medium is a schematic diagram of an NFV system architecture that can be applied to various types of networks, for example, to a carrier communication network or a local area network, according to an exemplary embodiment.
  • the system architecture mainly includes NFV MANO 110, NFV Infrastructure (NFVI) 120, multiple VNFs 130, multiple Element Management (EM) 140, and Operation Support System/Business. Support System, OSS/BSS) 150, etc.
  • the NFV MANO 110 further includes an NFVO 110a, one or more VNFMs 110b, and a Virtualized Infrastructure Manager (VIM) 110c.
  • VNFM Virtualized Infrastructure Manager
  • the multiple VNFs 130 are mainly used to implement the service routing method provided by the embodiments of the present invention.
  • Each VNF 130 can be configured to provide a network function of a communication network (eg, the communication network is an Intent Protocol Multimedia Subsystem (IMS)), for example, the different network elements include, but are not limited to, an agent. Proxy Call Session Control Function (P-CSCF), Interrogating Call Session Control Function (I-CSCF), Serving Call Session Control Function (S-CSCF), HSS, Application Server (AS).
  • P-CSCF Proxy Call Session Control Function
  • I-CSCF Interrogating Call Session Control Function
  • S-CSCF Serving Call Session Control Function
  • HSS HSS
  • AS Application Server
  • the S-CSCF and the I-CSCF may be implemented by using different VNFs respectively, or the S-CSCF and the I-CSCF may be combined in the same VNF. Make a limit.
  • the multiple VNFs 130 may be further divided into a front-end network element and a back-end network element, for example, in the calling session system.
  • the front-end network element may be a P-CSCF
  • the back-end network element may include an S-CSCF, an I-CSCF, an AS, and the like.
  • the front-end network element may be an I-CSCF
  • the back-end network element may include an S-CSCF, an AS, and the like.
  • the NFV MANO 110 is mainly used to perform monitoring and management of the VNF 130 and the NFVI 120, and the EM 140 is configured to manage one or more VNFs 130.
  • the NFVO 110a and the VNFM 110b included in the NFV MANO 110 and the EM 140 are mainly used to implement a grayscale policy control center, and the grayscale policy control center is mainly used to send a grayscale policy to each VNF 130. Description file.
  • the NFVO 110a, the VNFM 110b, or the EM 140 may send a grayscale policy description file to the plurality of VNFs 130, so that the plurality of VNFs 130 determine the grayscale policy, and the specific For the implementation, please refer to the embodiment shown in FIG. 4 to FIG. 6 below.
  • the above NFVI 120 mainly includes hardware resources, software resources, or a combination of the two to complete the deployment of the virtualized environment, that is, the hardware resources and the virtualization layer are used to provide virtualized resources, for example, as virtual machines and other forms.
  • the above VIM 110c is mainly used to perform functions of resource management, for example, management of allocation and operation functions of infrastructure resources.
  • the NFVI 120 and VIM 110c can be used to implement the communication network service in conjunction with the VNF 130 described above, and will not be described too much here.
  • FIG. 2 is a schematic diagram of a system architecture according to an exemplary embodiment.
  • the system architecture mainly includes a front-end network element 210 and a back-end network element 220.
  • the front-end network element 210 and the back-end network element 220 can be connected through a communication network.
  • both the front end network element 210 and the back end network element 220 can be implemented by the VNF 130 described above.
  • the front-end network element 210 and the back-end network element 220 both include different subsystem modules that are not upgraded and upgraded and have the same function.
  • the different subsystem modules include a load balancer (Load Balance). , LB), Service Processing Module (Service, SRV), Database (Data Base, DB), etc.
  • the network may also have an un-upgraded back-end network element and an upgraded back-end network element having the same network function, where the upgraded The back-end network element means that all subsystem modules it includes have been upgraded.
  • the front-end network element 210 is mainly used to determine whether the user is a gray-scale user when receiving a service request from a user, where the service request may include, but is not limited to, a registration request, a calling session request, and a called session request. . Further, the front end network element 210 can determine whether the user is a grayscale user according to the grayscale policy description file. That is, the front-end network element 210 selects which users' services are routed to the upgraded subsystem modules in the VNF according to the grayscale policy description file, to perform grayscale verification on the upgraded subsystem modules.
  • the front-end network element 210 may further add a gray-scale identifier to the service request after determining the gray-scale user, to notify the back-end network element 220 which users are gray-scale users, and thus, the back-end network element 220 may be received.
  • the service request from the user it is determined whether the service of the user needs to be routed to the upgraded subsystem module in the backend network element 220, so that each network element routes the services of the same grayscale user to the upgraded
  • the subsystem module please refer to the embodiment shown in FIG. 4 to FIG. 6 below.
  • front-end network element 210 and the back-end network element 220 may be provided by the same vendor, or may be provided by different vendors, which is not limited by the embodiment of the present invention.
  • the system architecture further includes a grayscale policy control center 230, and the grayscale policy control center 230 is mainly used to send the grayscale policy description file to the front end network element 210.
  • the grayscale policy is implemented.
  • the control center 230 may also be configured to send the grayscale policy description file to the backend network element 220.
  • the gradation policy control center 230 may be the NFVO 110a, the VNFM 110b, or the EM 140, which is not limited by the embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a computer device according to an embodiment of the present invention.
  • the VNF 130 of Figure 2 can be implemented by the computer device shown in Figure 3.
  • the computer device includes at least one processor 301, a communication bus 302, a memory 303, and at least one communication interface 304.
  • the processor 301 can be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more for controlling the execution of the program of the present application. integrated circuit.
  • CPU general purpose central processing unit
  • ASIC application-specific integrated circuit
  • Communication bus 302 can include a path for communicating information between the components described above.
  • the memory 303 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM), or other information that can store information and instructions.
  • ROM read-only memory
  • RAM random access memory
  • Type of dynamic storage device or Electro Scientific Erasable Programmable Read-Only Memory (EEPROM), Compact Disc Read-Only Memory (CD-ROM) or other optical disc storage, optical disc Storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being Any other medium accessed by the computer, but is not limited thereto.
  • Memory 303 may be present independently and coupled to processor 301 via communication bus 302. The memory 303 can also be integrated with the processor 301.
  • the communication interface 304 uses devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • devices such as any transceiver for communicating with other devices or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), and the like.
  • RAN Radio Access Network
  • WLAN Wireless Local Area Networks
  • processor 301 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG.
  • a computer device can include multiple processors, such as processor 301 and processor 305 shown in FIG. Each of these processors can be a single-CPU processor or a multi-core processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data, such as computer program instructions.
  • the computer device may further include an output device 306 and an input device 307.
  • Output device 306 is in communication with processor 301 and can display information in a variety of ways.
  • the output device 306 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. Wait.
  • Input device 307 is in communication with processor 301 and can receive user input in a variety of ways.
  • input device 307 can be a mouse, keyboard, touch screen device, or sensing device, and the like.
  • the computer device described above may be a general purpose computer device or a special purpose computer device.
  • the computer device may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, or an embedded device.
  • PDA personal digital assistant
  • Embodiments of the invention do not limit the type of computer device.
  • the memory 303 is used to store program code for executing the solution of the present application, and is controlled by the processor 301 for execution.
  • the processor 301 is configured to execute the program code 308 stored in the memory 303.
  • One or more software modules may be included in program code 308.
  • the VNF 130 shown in FIG. 2 may determine data for developing an application by the processor 301 and one or more of the program code 308 in the memory 303.
  • FIG. 4 is a flowchart of a method for service routing according to an exemplary embodiment.
  • the method of the service routing can be applied to the system shown in FIG. 2, wherein the VNF in the embodiment refers to the front-end network element in the system shown in FIG. 2, and the next one VNF refers to the backend network element in the system shown in Figure 2.
  • the method of routing the service may include the following implementation steps:
  • Step 401 The VNF receives the grayscale policy description file sent by the grayscale policy control center.
  • the grayscale policy control center in order to facilitate the VNF to determine which users need to be determined as grayscale users, the grayscale policy control center generally sends a grayscale policy description file to the VNF in advance to notify the VNF by the grayscale policy description file. Grayscale strategy.
  • the gray-scale policy description file is sent to the VNF as an example. In the actual implementation, in order to ensure that each VNF can know the gray-scale policy, the gray-scale strategy is generally used.
  • the control center may also send the grayscale policy description file to each VNF, which is not limited herein.
  • the grayscale policy description file includes different content according to the grayscale policy determined by the grayscale policy control center, and may specifically include the following situations:
  • the first case the grayscale policy description file includes the grayscale percentage.
  • the grayscale policy determined by the grayscale policy control center is a grayscale percentage. That is, the gray policy control center only informs the VNF how many users need to be determined as grayscale users, but the gray policy control center does not specify which users are specifically determined as grayscale users. At this time, the VNF needs to determine which users need to be determined as grayscale users according to the grayscale percentage. For the specific implementation, refer to the first implementation in step 402.
  • the grayscale policy description file includes the range of users belonging to the grayscale user.
  • the grayscale policy determined by the grayscale policy control center directly specifies which users are grayscale users, and delivers the specified user range belonging to the grayscale user to the VNF through the grayscale policy description file.
  • the user scope may include, but is not limited to, a location range, a number segment, or a list of numbers.
  • the location range refers to a range of locations where the user is located.
  • the location range may be A city; the number segment is used to indicate that one or some of the phone numbers used by the user meet certain rules.
  • the number segment may refer to the fourth to seventh digits of the telephone number being in the range of 0100 to 0112.
  • the number segment may also mean that the last digit of the telephone number is an even number, etc.; For storing phone numbers belonging to grayscale users.
  • the embodiment of the present invention is only described by taking the user range including a location range, a number segment, or a number list as an example.
  • the user range may further include other information, for example, the user range.
  • the user range It is also possible to include a user level, wherein the user level can be used to indicate whether the user is a VIP (Very Important Person (VIP) user, etc.; for example, the user range can also include a prepaid or postpaid user, etc., the implementation of the present invention This example does not limit this.
  • VIP Very Important Person
  • the grayscale policy control center may divide the entire grayscale upgrade into N batches, and assign different users to different batches according to different grayscale policies. . Therefore, in an actual implementation, the grayscale policy control center may further add a batch value in the grayscale policy description file, where the batch value is used to indicate the batch corresponding to the grayscale user. In this way, in the subsequent processing, if a batch has a problem with the upgraded VNF after the grayscale verification, the grayscale user corresponding to the batch value may be subjected to batch fallback processing.
  • the above N is an integer greater than 1.
  • the gray policy control center can issue all the batches of the grayscale policy description file to the VNF at one time, or the grayscale policy control center can also issue the grayscale policy description to the VNF in batches. file.
  • the grayscale policy control center needs to read the grayscale policy description files provided by different vendors before the grayscale policy description file is sent to each VNF, and presents the display on the display interface. Define edits to modify the contents and submit the save. After that, the grayscale policy control center sends the edited modified and saved grayscale policy description file to the VNF corresponding to different vendors, so that each VNF can parse the grayscale policy description file defined by itself, and obtain the gray. The gray policy indicated by the policy description file.
  • the grayscale policy description file adopts a unified and universal standard format and supports editability.
  • the grayscale policy description file may be a Hyper Text Markup Language (HTML).
  • HTML Hyper Text Markup Language
  • the content of the grayscale policy description file is the same as the API event interface triggered when the edit is modified and submitted, for example, the javascript:form.submit() interface function is uniformly called.
  • Step 402 When the VNF receives the service request from the user, determine whether the user is a grayscale user.
  • the VNF In order to determine which users need to be selected to use the upgraded subsystem module in the VNF, when receiving a service request from the user, it is necessary for the VNF to determine whether the user is a grayscale user.
  • the VNF may determine whether the user is a grayscale user according to a grayscale policy description file sent by the grayscale policy control center. Wherein, according to the content included in the grayscale policy description file, the VNF determines whether the user is a grayscale user, and the user may include the following possible implementation manners:
  • the first implementation manner when the grayscale policy description file includes a grayscale percentage, the VNF may determine whether the user is a grayscale user according to the grayscale percentage.
  • the VNF determining whether the user is a grayscale user according to the grayscale percentage may specifically include the following process: the VNF selects an i-th user from each preset number of users according to the grayscale percentage, and selects the selected one. The user determines to be a grayscale user, where i is an integer greater than one.
  • the preset number can be customized by the user according to actual needs, or can be set by default by the VNF, which is not limited by the embodiment of the present invention.
  • the VNF can select the first user from every 10 online users, and select the user. Determined as a grayscale user. That is, the first user of every 10 online users is determined to be a grayscale user.
  • the VNF may be based on the number of grayscale users currently offline, in each subsequent It is assumed that among the number of users, the number of grayscale users selected is increased to be compensated until the number of grayscale users online is substantially consistent with the above grayscale percentage.
  • the VNF selects the i-th user from each preset number of users according to the grayscale percentage, and determines the selected user as the grayscale user as an example.
  • the VNF may also determine the grayscale user by other means according to the grayscale percentage.
  • the VNF may further select a jth service from each preset number of times according to the grayscale percentage, and select the selected service as a grayscale object, and further determine the selected user corresponding to the service.
  • j is an integer greater than one.
  • the VNF may determine, according to the user scope, whether the user is a grayscale user.
  • the grayscale policy control center has directly specified which users belong to the grayscale user.
  • the VNF receives the service request from the user, determining whether the user is a grayscale user according to the range of users included in the grayscale policy description file.
  • the service request may carry the user identity information of the user.
  • the user identity information may include a phone number used by the user or location information currently used by the user.
  • the VNF queries whether the user identity information belongs to the user scope, and if so, determines that the user is a grayscale user.
  • the user range includes a number segment, and the number segment refers to the fourth to seventh digits of the phone number being between 0100-0112, and the VNF queries the phone. Whether the fourth to seventh digits of the number belong to the number segment. If the fourth to seventh digits of the telephone number belong to the number segment, the VNF determines that the user is a grayscale user, otherwise, it is determined that the user is not a grayscale user.
  • Step 403 If the VNF determines that the user is the grayscale user, routing the service requested by the service request to the upgraded subsystem module in the VNF.
  • the VNF includes different subsystem modules with the same function that have not been upgraded and upgraded. If it is determined that the user is a grayscale user, it indicates that the service requested by the user needs to be routed to the upgraded in the VNF. Subsystem module.
  • the grayscale policy description file includes the batch value
  • the batch only when it is less than or equal to the grayscale release batch to which the current grayscale upgrade task is performed, the VNF routes the service requested by the user to the upgraded subsystem module in the VNF.
  • the grayscale identifier may be set for the user or the current service.
  • the grayscale identifier may be ABTest.
  • the VNF may save the grayscale identifier in the user registration data of the DB, so that when the user initiates other services, the VNF may directly determine the user according to the stored user registration data. Whether it is a grayscale user.
  • the VNF may also save the grayscale identifier in the session data of the DB, so as to facilitate the subsequent processing of other messages of the service, directly query the session data to determine whether the service is A grayscale object to determine whether the user who initiated the service request is a grayscale user.
  • Embodiments of the invention also include the following implementation steps.
  • Step 404 When the VNF determines that the user is a grayscale user, add a grayscale identifier to the service request.
  • the VNF may add a grayscale identifier to the service request before sending the service request to the next VNF.
  • step 404 may be performed before step 403, or may be performed after the step 403, or the step may be performed.
  • the 404 can also be executed at the same time as the step 403, which is not limited by the embodiment of the present invention.
  • Step 405 The VNF sends the service request to the next VNF, where the service request is used to indicate that the next VNF determines the user as the grayscale user.
  • the service request carries a grayscale identifier. Therefore, after receiving the service request, the next VNF can determine that the user is a grayscale user based on the grayscale identifier.
  • grayscale identification may be different for different suppliers.
  • the grayscale identifier provided by the A supplier is ABTest
  • the logo may be BCTest, etc.
  • a unified grayscale identification information may be included in the grayscale policy description file, for example, the grayscale identification information is a “gradation identification parameter”, that is, the grayscale policy description.
  • the VNF corresponding to the B provider can determine that the ABTest is the grayscale identifier based on the content of the grayscale policy description file. .
  • next VNF determines that the user is a grayscale user, and routes the service requested by the user's service request to The subsystem module that has been upgraded in the next VNF.
  • next VNF when the next VNF is an unupgraded VNF, and an upgraded VNF having the same function exists, the next VNF redirects the service requested by the user's service request from the unupgraded VNF to the Upgraded VNF.
  • VNF As mentioned above, in some cases, for the next VNF, there are unupgraded VNFs and upgraded VNFs with the same functionality in the network, where the upgraded VNFs described herein refer to all included sub-ports. System modules have been upgraded. In this case, the VNF needs to be redirected by the VNF to the upgraded VNF from the upgraded VNF to perform the grayscale verification on the upgraded VNF.
  • the specific implementation process will be exemplified by the embodiment shown in FIG. 6 below.
  • the front-end network element carries the gray-scale identifier in the service request sent to the back-end network element, so that the back-end network element also determines the user as the gray-scale user, so The problem that the different VNFs can cooperate in grayscale verification when communicating across different VNFs is solved.
  • the grayscale policy control center sends the grayscale policy description file to each. VNF.
  • the grayscale policy description file includes a specific user range
  • each VNF has learned which users are grayscale users
  • the front-end network element sends a service request to the back-end network element, Does not carry a grayscale logo.
  • the gray-scale policy description file sent by the gray-scale policy control center may be directly determined to determine whether the user is grayscale. The user, as such, also solves the problem that the different VNFs can cooperate with grayscale verification when communicating across different VNFs.
  • the service routing method provided by the embodiment of the present invention is applied to a VNF, which includes different subsystem modules with the same function that have not been upgraded and upgraded.
  • VNF determines whether the user is a grayscale user. If the user is a grayscale user, the user's traffic is routed to the upgraded subsystem module in the VNF. In this way, the VNF determines the grayscale user when receiving the service request from the user, and implements grayscale verification on the upgraded subsystem module.
  • FIG. 5 is a flowchart of a method for service routing according to another exemplary embodiment.
  • the method for the service routing may be applied to the system shown in FIG. 2, and the method for routing the service may be It includes the following implementation steps:
  • Step 501 The P-CSCF receives the grayscale policy description file sent by the grayscale policy control center.
  • the gray policy description file may include a grayscale percentage, or the grayscale policy description file may further include a grayscale.
  • the user's scope of the user may include, but is not limited to, a location range, a number segment, and a list of numbers.
  • the grayscale policy description file may further include a batch value.
  • the gray-scale policy description file is sent to the P-CSCF as an example.
  • the gray-scale policy control center can actually implement the gray-scale policy.
  • the description file is sent to each VNF so that each VNF can know the grayscale policy.
  • the respective VNFs include the I/S-CSCF and the AS.
  • Step 502 When the P-CSCF receives the registration request from the user, it is determined whether the user is a grayscale user.
  • the P-CSCF determines whether the user is a grayscale user according to the received grayscale policy description file. For the specific implementation, refer to step 402 in the foregoing embodiment of FIG. 4, and details are not described herein again.
  • the P-CSCF receives the grayscale policy description file sent from the gray policy control center, and determines whether the user is a grayscale user according to the grayscale policy description file as an example.
  • the gray policy control center may send the gray policy description file to the HSS, and then The grayscale user is determined by the HSS according to the grayscale percentage, and a grayscale identifier is added to the corresponding user data.
  • the VNF downloads the user data from the HSS, it can determine whether the user is a grayscale user according to the grayscale identifier in the user data, and each VNF includes a P-CSCF.
  • the gray policy control center may further modify the user data of the corresponding user directly in the HSS after determining which users need to be determined as grayscale users, that is, different from the foregoing implementation manner,
  • the HSS is not required to determine which users are grayscale users according to the grayscale percentage, but the grayscale policy control center determines a specific grayscale user according to the grayscale percentage, and directly modifies the corresponding user in the HSS by expanding the service issuing interface.
  • User data add grayscale identification.
  • each VNF may determine whether the user is a grayscale user according to the grayscale identifier in the user data, and each VNF includes a P-CSCF.
  • Step 503 When the P-CSCF determines that the user is a grayscale user, the service requested by the user's registration request is routed to the upgraded subsystem module in the P-CSCF.
  • the grayscale policy description file includes the batch value
  • the batch only when less than or equal to the grayscale release batch to which the current grayscale upgrade task is performed, the P-CSCF routes the service requested by the user to the upgraded subsystem module in the P-CSCF.
  • the grayscale identifier may be set for the user, and then the P-CSCF saves the grayscale identifier in the user registration data of the DB, so that when the user When initiating other services (for example, session service), the P-CSCF can directly determine whether the user is a grayscale user according to the stored user registration data.
  • the P-CSCF saves the grayscale identifier in the session data of the DB, so that when the other messages (eg, response messages) of the service are subsequently processed, the P-CSCF directly determines the session data by querying the session data. Whether the service is a grayscale object, thereby determining whether the user who initiated the service request is a grayscale user.
  • the grayscale user determined here is only a grayscale user in the current service, and in the next service, the user may no longer be a grayscale user according to the determined grayscale object.
  • the embodiment of the present invention further includes the following implementation steps.
  • Step 504 When the P-CSCF determines that the user is a grayscale user, add a grayscale identifier to the registration request.
  • step 404 in the foregoing embodiment of FIG. 4, which is not described in detail herein.
  • Step 505 The P-CSCF sends the registration request to the I/S-CSCF.
  • the I/S-CSCF After receiving the registration request, the I/S-CSCF, when determining that the user is a grayscale user according to the grayscale identifier, routes the user's service to the upgraded subsystem module in the I/S-CSCF.
  • the I/S-CSCF may also save the grayscale identifier in the user registration data of the DB of the I/S-CSCF, so that the I/S-CSCF can directly pass the user when the user initiates other services. Query the user registration data of the DB to determine whether the user is a grayscale user.
  • the I/S-CSCF may also store the grayscale identifier in the user registration data of the local DB, but store the grayscale identifier through the P-CSCF. Specifically, the I/S-CSCF may carry the grayscale identifier in a specified parameter of the 200 OK message returned to the P-CSCF, so that the P-CSCF stores the specified parameter carrying the grayscale identifier in the P-CSCF.
  • DB user registration data For example, the specified parameter is the Service-route parameter.
  • the P-CSCF may carry the specified parameter in the calling session request, so that the I/S-CSCF determines whether the user is a grayscale user according to the specified parameter.
  • the I/S-CSCF may further carry the grayscale identifier in a Multimedia Authentication Request (MAR)/Service Assignment Request (SAR) message sent to the HSS, so that the HSS Save the grayscale logo.
  • MAR Multimedia Authentication Request
  • SAR Service Assignment Request
  • the I-CSCF sends a location immediate request to the HSS after receiving the called session request ( The location Request, LIR, obtains the information of the S-CSCF where the user is located.
  • the HSS when the HSS responds to the location (When the answer is LIA), the HSS returns the grayscale identifier carried in the MAR/SAR message to the HSS to the I-CSCF when the user registers, and the I-CSCF receives the I-CSCF. After the LIA response, it is found that it is a grayscale user, and the subsequent I/S-CSCF routes the user's service to the upgraded subsystem module.
  • the I/S-CSCF may continue to send the grayscale identifier to the next VNF that interacts with the I/S-CSCF.
  • the next VNF is an AS.
  • Step 506 The I/S-CSCF sends a registration request to the AS, where the registration request carries the grayscale identifier.
  • Step 507 When the AS determines that the user is a grayscale user, routing the service requested by the user to the upgraded subsystem module in the AS.
  • the AS may also save the grayscale identifier in the user registration data of the DB of the AS, so that when the user initiates other services, the AS may directly determine the user registration data of the DB. Whether the user is a grayscale user.
  • the service routing method provided by the embodiment of the present invention is applied to the VNF, and the VNF includes different subsystem modules with the same function that have not been upgraded and upgraded.
  • the VNF determines whether the user is a grayscale user. If the user is a grayscale user, the user's traffic is routed to the upgraded subsystem module in the VNF. In this way, the VNF determines the grayscale user when receiving the service request from the user, and implements grayscale verification on the upgraded subsystem module.
  • the embodiment shown in FIG. 5 is an example in which the following VNF includes different upgraded and upgraded subsystem modules having the same function as an example.
  • VNF includes different upgraded and upgraded subsystem modules having the same function as an example.
  • the front-end network element sends a service request to the next VNF, it needs to redirect the service to the upgraded VNF from the upgraded VNF.
  • the upgraded S-CSCF1 and the un-upgraded S-CSCF2 exist in the network, and the registration process is used as an example.
  • FIG. 6 is a flowchart of a method for service routing according to another exemplary embodiment.
  • the method of the service routing may be applied to the system shown in FIG. 2, and the method for routing the service may be It includes the following implementation steps:
  • Step 601 The P-CSCF receives the grayscale policy description file sent by the gray policy control center.
  • step 501 in the embodiment of FIG. 5, and details are not repeatedly described herein.
  • Step 602 When the P-CSCF receives the session request from the user, it is determined whether the user is a grayscale user.
  • step 502 in the embodiment of FIG. 5, and details are not repeatedly described herein.
  • Step 603 When the P-CSCF determines that the user is a grayscale user, the service requested by the session request is routed to the upgraded subsystem module in the P-CSCF.
  • step 503 in the embodiment of FIG. 5, and details are not described herein again.
  • Step 604 When the P-CSCF determines that the user is a grayscale user, add a grayscale identifier to the registration request.
  • Step 605 The P-CSCF sends the registration request to the I-CSCF.
  • Step 606 After receiving the registration request, the I-CSCF sends a first User Authorization Request (UAR) message to the HSS.
  • UAR User Authorization Request
  • the first UAR message is used to obtain information about the S-CSCF where the user is currently located.
  • Step 607 The HSS returns information of the S-CSCF where the user is located to the I-CSCF.
  • the HSS returns to the I-CSCF the information of the S-CSCF where the user is located as the information of the S-CSCF2.
  • the information of the S-CSCF may be used to uniquely identify an S-CSCF, for example, may be an identifier of the S-CSCF.
  • Step 608 The I-CSCF sends a registration request to the S-CSCF2 according to the information of the S-CSCF2 returned by the HSS.
  • the registration request carries a private extension parameter, and the private extension parameter is used to indicate whether the I-CSCF supports the 305 redirect message. Further, the registration request carries a grayscale identifier.
  • Step 609 When the S-CSCF2 determines that the user is a grayscale user, return a 305 redirect message to the I-CSCF, where the 305 redirect message is used to instruct the I-CSCF to register the service redirection of the user to the upgraded S-CSCF1.
  • Step 610 After receiving the 305 redirect message, the I-CSCF sends a second UAR message to the HSS again, where the second UAR message is used to indicate that the HSS allows the user to change the registration from the current S-CSCF2 to the S-CSCF1. .
  • the HSS after receiving the second UAR message, opens the reassignment pending flag switch to allow the user to change the registration to the S-CSCF1 from the current S-CSCF2.
  • Step 611 The HSS returns a User Authorization Request (UAA) message to the I-CSCF.
  • UAA User Authorization Request
  • Step 612 After receiving the UAA message, the I-CSCF sends a registration request to the S-CSCF1.
  • the registration request may carry a grayscale identifier.
  • Step 613 After receiving the registration request, the S-CSCF1 adds the grayscale identifier to the user registration data of the DB when it is determined that the user is a grayscale user.
  • the S-CSCF1 may determine that the user is a grayscale user according to the grayscale identifier carried in the registration message, or the S-CSCF1 may also use the grayscale policy description file sent by the grayscale policy control center. Make sure the user is a grayscale user. The user is determined to be a grayscale user according to the grayscale policy description file sent by the grayscale policy control center. For details, refer to the foregoing embodiment, which is not described in detail herein.
  • the P-CSCF may save the information of the newly registered S-CSCF1 of the user.
  • the P-CSCF determines that the user has registered to the upgraded S-CSCF1, a calling session request is sent to the S-CSCF1.
  • the S-CSCF1 may perform separate statistics on Key Performance Indicators (KPIs) of the user's services.
  • KPI Key Performance Indicators
  • the KPI may include, but is not limited to, a call completion rate, a response rate, and a connection duration. If the KPI statistics are normal, more grayscale users can be moved back from S-CSCF2 to S-CSCF1 to perform grayscale verification on the new version. If the KPI statistics are abnormal, the fetch and grayscale verification process can be terminated.
  • the service routing method provided by the embodiment of the present invention is applied to the VNF, and the VNF includes different subsystem modules with the same function that have not been upgraded and upgraded.
  • the VNF determines whether the user is a grayscale user. If the user is a grayscale user, the user's traffic is routed to the upgraded subsystem module in the VNF. In this way, the VNF determines the grayscale user when receiving the service request from the user, and implements grayscale verification on the upgraded subsystem module.
  • the VNF may add a grayscale identifier to the service request sent to the next VNF to notify the next VNF that the user is a grayscale user, thereby implementing collaborative grayscale verification between multiple VNFs. .
  • FIG. 7A is a schematic structural diagram of a service routing apparatus according to an exemplary embodiment.
  • the apparatus is configured in a VNF, and the apparatus includes:
  • the determining module 710 is configured to perform step 402 in the above embodiment of FIG. 4, step 502 in the embodiment of FIG. 5 or step 602 in the embodiment of FIG. 6;
  • the routing module 720 is configured to perform step 403 in the foregoing embodiment of FIG. 4, step 503 in the embodiment of FIG. 5, or step 603 in the embodiment of FIG.
  • the apparatus further includes:
  • the first receiving module 730 is configured to perform step 401 in the foregoing embodiment of FIG. 4, step 501 in the embodiment of FIG. 5, or step 601 in the embodiment of FIG.
  • the determining module 710 is configured to determine, according to the grayscale percentage, whether the user is a grayscale user.
  • the determining module 710 is configured to:
  • the selected user is determined to be the grayscale user.
  • the apparatus further includes:
  • the adding module 740 is configured to perform step 404 in the foregoing embodiment of FIG. 4, step 504 in the embodiment of FIG. 5, or step 604 in the embodiment of FIG. 6;
  • the sending module 750 is configured to perform step 405 in the foregoing embodiment of FIG. 4, step 505 in the embodiment of FIG. 5, or step 605 in the embodiment of FIG.
  • the apparatus further includes:
  • the second receiving module 760 is configured to perform step 401 in the foregoing embodiment of FIG. 4, step 501 in the embodiment of FIG. 5, or step 601 in the embodiment of FIG.
  • the service routing method provided by the embodiment of the present invention is applied to the VNF, and the VNF includes different subsystem modules with the same function that have not been upgraded and upgraded.
  • the VNF determines whether the user is a grayscale user. If the user is a grayscale user, the user's traffic is routed to the upgraded subsystem module in the VNF. In this way, the VNF determines the grayscale user when receiving the service request from the user, and implements grayscale verification on the upgraded subsystem module.
  • the VNF may add a grayscale identifier to the service request sent to the next VNF to notify the next VNF that the user is a grayscale user, thereby implementing collaborative grayscale verification between multiple VNFs. .
  • the service routing method provided by the embodiment of the present invention is applied to a VNF, where the VNF includes different subsystem modules with the same function that have not been upgraded and upgraded.
  • the VNF determines whether the user is a grayscale user. If the user is a grayscale user, the user's traffic is routed to the upgraded subsystem module in the VNF. In this way, the VNF determines the grayscale user when receiving the service request from the user, and implements grayscale verification on the upgraded subsystem module.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a digital versatile disc (DVD)), or a semiconductor medium (for example, a solid state disk (SSD)). )Wait.
  • a magnetic medium for example, a floppy disk, a hard disk, a magnetic tape
  • an optical medium for example, a digital versatile disc (DVD)
  • DVD digital versatile disc
  • SSD solid state disk
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种业务路由的方法、装置及存储介质，属于通信技术领域。该方法应用于VNF中，该VNF包括未升级以及已升级的具有相同功能的不同子系统模块，该方法包括：当接收到来自用户的业务请求时，确定该用户是否为灰度用户，若确定该用户为该灰度用户，则将该业务请求所请求的业务路由至该VNF中已升级的子系统模块。如此，由该VNF在接收到来自用户的业务请求时确定灰度用户，实现了对已升级的子系统模块进行灰度验证。

Description

业务路由的方法、装置及存储介质
本申请要求于2017年9月7日提交中国专利局、申请号为201710799280.0、发明名称为“业务路由的方法、装置及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，特别涉及一种业务路由的方法、装置及存储介质。
背景技术
近年来，随着通信技术的快速发展，网络功能虚拟化(Network Function Virtualization，NFV)技术在电信领域中得到了广泛的应用。该NFV技术是指通过通用的硬件平台来承载软件，并通过该软件实现多种电信网络功能，例如，实现呼叫会话功能等，从而避免电信网络功能对专用物理设备(如，机框、机架、专用服务器)的依赖。
NFV的系统框架中主要包括NFV管理与编排(MANagement and Orchestration，MANO)、多个虚拟网络功能(Virtualized Network Fucntion，VNF)、多个网元管理(Element Management，EM)等，该NFV-MANO包括NFV编排器(NFV Orchestrator，NFVO)和VNF管理器(VNF Manager，VNFM)。该NFVO、VNFM和EM均可以用于管理VNF。其中，每个VNF均可以通过配置来实现通信网络中网元所具备的网络功能，譬如，该网元可以为呼叫会话控制功能(Call Session Control Function，CSCF)、归属签约用户服务器(Home Subscriber Server，HSS)等，在实际应用中，通常需要多个具有不同网络功能的VNF相互协同来实现网络服务。
在实际应用场景中，由于业务需求等原因，通常需要对VNF进行升级，为了保证系统的稳定性，一般可以采用灰度升级的方式进行升级。灰度升级是指边升级边进行灰度验证，也即是，先对各个VNF中的部分单元或对具有相同网络功能的多个VNF中的部分VNF进行升级，之后进行灰度验证，当灰度验证通过后，再继续进行部分升级和灰度验证。其中，灰度验证是指按照一定的策略将部分用户的业务迁移至升级后的VNF上，这里将该部分用户称为灰度用户，以通过灰度用户对升级后的VNF进行灰度验证，当确认升级后的VNF的业务运行情况符合预期需求时，确定灰度验证通过。其中，当多个不同VNF之间协同通信进行业务处理时，如何实现灰度验证成为亟需解决的问题。
发明内容
本申请提供了一种业务路由方法、装置及存储介质，用于解决现有技术的如何进行灰度验证的问题。所述技术方案如下：
第一方面，提供了一种业务路由方法，应用于VNF中，所述VNF包括未升级以及已升级的具有相同功能的不同子系统模块，所述方法包括：
当接收到来自用户的业务请求时，确定所述用户是否为灰度用户；
若确定所述用户为所述灰度用户，则将所述业务请求所请求的业务路由至所述VNF中已 升级的子系统模块。
在本发明实施例中，为了确定需要选择哪些用户使用VNF中已升级的子系统模块，当接收到来自用户的业务请求时，需要由该VNF确定该用户是否为灰度用户。在实际实现中，该VNF可以根据灰度策略控制中心下发的灰度策略描述文件，确定该用户是否为灰度用户。
上述由该前端网元VNF在接收到来自用户的业务请求时确定灰度用户，实现了对已升级的子系统模块进行灰度验证。
可选地，所述确定所述用户是否为灰度用户之前，还包括：
接收灰度策略控制中心下发的灰度策略描述文件，所述灰度策略描述文件包括灰度百分比；
相应地，所述确定所述用户是否为灰度用户，包括：
根据所述灰度百分比确定所述用户是否为灰度用户。
也即是，在具体实现中，为了便于VNF确定需要将哪些用户确定为灰度用户，一般由灰度策略控制中心预先向该VNF下发灰度策略描述文件，以通过该灰度策略描述文件告知VNF所确定的灰度策略。在一种可能的实现方式中，若该灰度策略描述文件包括灰度百分比，则该VNF根据该灰度百分比确定所述用户是否为灰度用户。
如此，灰度策略控制中心预先向该VNF下发灰度策略描述文件，以通过该灰度策略描述文件告知VNF所确定的灰度策略，并且，当该灰度策略描述文件包括灰度百分比，可以使得该VNF能够根据所述灰度百分比确定所述用户是否为灰度用户。
可选地，所述根据所述灰度百分比确定所述用户是否为灰度用户，包括：
根据所述灰度百分比，从每预设数量个用户中选择第i个用户，所述i为大于1的整数；
将所选择的用户确定为所述灰度用户。
即在具体实现中，VNF可以将每预设数量个上线用户中的第i个用户确定为灰度用户，从而实现根据所述灰度百分比确定所述用户是否为灰度用户。
可选地，所述确定用户是否为灰度用户之后，还包括：
当确定所述用户为所述灰度用户时，在所述业务请求中添加灰度标识；
向下一个VNF发送所述业务请求，所述业务请求用于指示所述下一个VNF将所述用户确定为所述灰度用户。
在实际应用场景中，通常需要多个VNF之间交互才能实现网络通信。在这里，为了通知下一个VNF当前进行业务请求的用户被确定为灰度用户，VNF在向下一个VNF发送该业务请求之前，可以在该业务请求中添加灰度标识，并向下一个VNF发送该业务请求，以指示下一个VNF将该用户确定为该灰度用户。如此，解决了跨不同VNF进行通信时该不同VNF能够协同进行灰度验证的问题。
可选地，所述向下一个VNF发送所述业务请求之后，还包括：
当所述下一个VNF是未升级的VNF，且存在具有相同功能的已升级的VNF时，所述下一个VNF将所述用户的注册请求所请求的业务从所述未升级的VNF重定向路由至所述已升级的VNF。
如此，下一个VNF将相同的用户的业务路由至已升级的VNF中，实现了对已升级的VNF进行灰度验证。
可选地，所述向下一个VNF发送所述业务请求之后，还包括：
当所述下一个VNF包括未升级以及已升级且具有相同功能的不同子系统模块时，所述下一个VNF将所述业务请求所请求的业务路由至所述下一个VNF中已升级的子系统模块。
如此，各个VNF均将相同的用户的业务路由至已升级的子系统模块中，实现了各个VNF之间的协同灰度验证。
可选地，所述确定所述用户是否为灰度用户之前，还包括：
接收灰度策略控制中心下发的灰度策略描述文件，所述灰度策略描述文件包括属于灰度用户的用户范围；相应地，所述确定所述用户是否为灰度用户，包括：
基于所述用户范围，确定所述用户是否为所述灰度用户。
在该种实现方式中，灰度策略控制中心已经直接指定了哪些用户属于灰度用户。在具体实现中，当VNF接收到来自用户的业务请求时，根据该灰度策略描述文件包括的用户范围确定该用户是否为灰度用户。譬如，该业务请求可以携带用户的用户身份信息，例如，该用户身份信息可以包括该用户所使用的电话号码或用户当前所处的位置信息等。之后，该VNF查询该用户身份信息是否属于该用户范围，如果属于，则确定该用户为灰度用户。如此，解决了跨不同VNF进行通信时该不同VNF能够协同进行灰度验证的问题。
可选地，所述用户范围包括位置范围、号段或号码列表。
其中，该位置范围是指用户所处的位置的范围，例如，该位置范围可以为A城市；该号段用于表示用户所使用的电话号码中某一位或某几位符合一定的规则，例如，该号段可以是指电话号码的第四位至第七位处于0100至0112范围内，再如，该号段还可以是指电话号码的最后一位为偶数等；该号码列表可以用于存储属于灰度用户的用户的电话号码。
如此，灰度策略控制中心通过该位置范围、号段或号码列表，可以直接指定并告知VNF哪些用户为灰度用户，使得各个VNF协同实现灰度验证。
第二方面，提供了一种业务路由的装置，配置于VNF中，所述VNF包括未升级以及已升级的具有相同功能的不同子系统模块，所述装置包括：
确定模块，用于当接收到来自用户的业务请求时，确定所述用户是否为灰度用户；
路由模块，用于当确定所述用户为所述灰度用户时，将所述业务请求所请求的业务路由至所述VNF中已升级的子系统模块。
可选地，所述装置还包括：
第一接收模块，用于接收灰度策略控制中心下发的灰度策略描述文件，所述灰度策略描述文件包括灰度百分比；
相应地，所述确定模块还用于：
根据所述灰度百分比确定所述用户是否为灰度用户。
可选地，所述确定模块用于：
根据所述灰度百分比，从每预设数量个用户中选择第i个用户，所述i为大于1的整数；
将所选择的用户确定为所述灰度用户。
可选地，所述装置还包括：
添加模块，用于当确定所述用户为所述灰度用户时，在所述业务请求中添加灰度标识；
发送模块，用于向下一个VNF发送所述业务请求，所述业务请求用于指示所述下一个VNF将所述用户确定为所述灰度用户。
可选地，当所述下一个VNF是未升级的VNF，且存在具有相同功能的已升级的VNF时，所述下一个VNF将所述用户的注册请求所请求的业务从所述未升级的VNF重定向路由至所述已升级的VNF。
可选地，所述向下一个VNF发送所述业务请求之后，当所述下一个VNF包括未升级以及已升级且具有相同功能的不同子系统模块时，所述下一个VNF将所述业务请求所请求的业务路由至所述下一个VNF中已升级的子系统模块。
可选地，所述装置还包括：
第二接收模块，用于接收灰度策略控制中心下发的灰度策略描述文件，所述灰度策略描述文件包括属于灰度用户的用户范围；
相应地，所述确定模块还用于：
基于所述用户范围，确定所述用户是否为所述灰度用户。
可选地，所述用户范围包括位置范围、号段或号码列表。
第三方面，提供了一种业务路由装置，所述业务路由装置的结构中包括处理器和存储器，所述存储器用于存储支持业务路由装置执行上述第一方面所提供的业务路由方法的程序，以及存储用于实现上述第一方面所提供的业务路由方法所涉及的数据。所述处理器被配置为用于执行所述存储器中存储的程序。所述存储设备的操作装置还可以包括通信总线，该通信总线用于该处理器与存储器之间建立连接。
第四方面，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面所述的业务路由方法。
第五方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的业务路由方法。
上述第二方面、第三方面、第四方面和第五方面所获得的技术效果与第一方面中对应的技术手段获得的技术效果近似，在这里不再赘述。
本申请提供的技术方案带来的有益效果是：本发明实施例提供的业务路由方法应用于VNF中，该VNF包括未升级以及已升级的具有相同功能的不同子系统模块。当接收到来自用户的业务请求时，为了确定是否选择将该用户的业务路由到该VNF中已升级的子系统模块，该VNF确定该用户是否为灰度用户。如果该用户是灰度用户，则将该用户的业务路由到该VNF中已升级的子系统模块。如此，由该VNF在接收到来自用户的业务请求时确定灰度用户，实现了对已升级的子系统模块进行灰度验证。
附图说明
图1是根据一示例性实施例示出的一种NFV系统架构的示意图；
图2是根据一示例性实施例示出的一种系统架构的示意图；
图3是本发明实施例提供的一种计算机设备的结构示意图；
图4是本根据一示例性实施例示出的一种业务路由的方法流程图；
图5是本根据另一示例性实施例示出的一种业务路由的方法流程图；
图6是本根据另一示例性实施例示出的一种业务路由的方法流程图；
图7A是根据一示例性实施例示出的一种业务路由装置的结构示意图；
图7B是根据一示例性实施例示出的另一种业务路由装置的结构示意图；
图7C是根据一示例性实施例示出的另一种业务路由装置的结构示意图；
图7D是根据一示例性实施例示出的另一种业务路由装置的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
本发明实施例主要是通过NFV系统架构来实现网络通信服务，因此，在对本发明实施例所涉及的业务路由的方法进行详细介绍之前，先对NFV系统架构进行简单的介绍。
请参考图1，该图1是根据一示例性实施例示出的一种NFV系统架构的示意图，该NFV系统架构能够应用于各种类型的网络中，譬如，可以应用于运营商通信网络或局域网络中等。
该系统架构主要包括有NFV MANO 110、NFV基础设施层(NFV Infrastructure，NFVI)120、多个VNF 130、多个网元管理(Element Management，EM)140以及业务支持管理系统(Operation Support System/Business Support System，OSS/BSS)150等。其中，该NFV MANO 110还包括有NFVO 110a、一个或者多个VNFM 110b以及虚拟化基础设施管理器(Virtualized Infrastructure Manager，VIM)110c。
其中，该多个VNF 130主要用于实现本发明实施例所提供的业务路由的方法。每个VNF 130均可以经过配置以提供通信网络(如，通信网络为IP多媒体系统(Intent Protocol Multimedia Subsystem，IMS))中不同网元具备的网络功能，譬如，该不同网元包括但不限于代理呼叫会话控制功能(Proxy Call Session Control Function，P-CSCF)、访问呼叫会话控制功能(Interrogating Call Session Control Function，I-CSCF)、服务呼叫会话控制功能(Serving Call Session Control Function，S-CSCF)、HSS、应用服务器(Application Server，AS)。在实际实现中，该S-CSCF和该I-CSCF可以分别通过不同的VNF来实现，或者，该S-CSCF和该I-CSCF也可以合设于同一VNF中，本发明实施例对此不做限定。
进一步地，根据各个VNF 130在通信网络中部署的位置以及所属的系统类型不同，这里还可以将该多个VNF 130分为前端网元和后端网元，例如，在主叫会话系统中，该前端网元可以为P-CSCF，后端网元可以包括S-CSCF、I-CSCF以及AS等。再如，在被叫会话系统中，该前端网元可以为I-CSCF，后端网元可以包括S-CSCF、AS等。
其中，上述NFV MANO 110主要用于执行对VNF130和NFVI 120的监视和管理，上述EM 140经过配置可以用于对一个或者多个VNF 130进行管理。在本发明实施例中，该NFV MANO 110中包括的NFVO 110a和VNFM 110b以及上述EM 140主要用于实现灰度策略控制中心，该灰度 策略控制中心主要用于向各个VNF 130发送灰度策略描述文件。也即是，在本发明实施例中，可以由该NFVO 110a、VNFM 110b或EM 140向该多个VNF 130发送灰度策略描述文件，以便于该多个VNF 130来确定灰度策略，其具体实现请参见如下图4至图6所示的实施例。
另外，上述NFVI 120主要包括硬件资源、软件资源或者两者的组合，以完成虚拟化环境的部署，即硬件资源和虚拟化层用于提供虚拟化的资源，例如，作为虚拟机和其它形式的虚拟容器，用于VNF 130。上述VIM 110c主要用于执行资源管理的功能，例如，管理基础设施资源的分配和操作功能。总之，该NFVI 120和VIM 110c可以用于配合上述VNF 130来实现通信网络服务，这里不再做过多的介绍。
接下来，对本发明实施例涉及的系统架构进行简单介绍。
请参考图2，该图2是根据一示例性实施例示出的一种系统架构的示意图。该系统架构中主要包括前端网元210和后端网元220，该前端网元210与该后端网元220可以通过通信网络实现连接。如前文所述，该前端网元210和该后端网元220均可以通过上述VNF 130来实现。
在实际应用场景中，该前端网元210和该后端网元220均包括有未升级以及已升级且具有相同功能的不同子系统模块，例如，该不同子系统模块包括负载均衡器(Load Balance，LB)、服务处理模块(Service，SRV)、数据库(Data Base，DB)等。
另外，在一种可能的实现方式中，对于后端网元220，网络中还可能同时存在未升级的后端网元和具有相同网络功能且已升级的后端网元，其中，该已升级的后端网元是指其所包括的所有子系统模块均已升级。
其中，前端网元210主要用于在接收到来自用户的业务请求时，确定该用户是否为灰度用户，其中，该业务请求可以包括但不限于注册请求、主叫会话请求和被叫会话请求。进一步地，该前端网元210可以根据灰度策略描述文件，确定该用户是否为灰度用户。也即是，该前端网元210根据灰度策略描述文件，选择将哪些用户的业务路由至VNF中已升级的子系统模块，以对升级后的子系统模块进行灰度验证。
另外，该前端网元210还可以在确定灰度用户后，在业务请求中添加灰度标识，以通知后端网元220哪些用户是灰度用户，如此，可以使得后端网元220在接收到来自该用户的业务请求时，确定是否需要将该用户的业务路由到后端网元220中已升级的子系统模块中，从而保证各个网元将同一灰度用户的业务均路由至已升级的子系统模块中，其具体实现请参见如下图4至图6所示的实施例。
需要说明的是，在实际应用场景中，该前端网元210和后端网元220可以是同一个供应商提供的，也可以是由不同供应商提供的，本发明实施例对此不作限定。
进一步地，该系统架构中还包括灰度策略控制中心230，该灰度策略控制中心230主要用于向前端网元210发送上述灰度策略描述文件，当然，在实际实现中，该灰度策略控制中心230还可能用于向后端网元220发送上述灰度策略描述文件。如前文所述，在实际实现中，该灰度策略控制中心230可以为上述NFVO 110a、VNFM 110b或EM 140，本发明实施例对此不做限定。
图3是本发明实施例提供的一种计算机设备的结构示意图。图2中的VNF 130可以通过图3所示的计算机设备来实现。参见图3，该计算机设备包括至少一个处理器301，通信总线302，存储器303以及至少一个通信接口304。
处理器301可以是一个通用中央处理器(Central Processing Unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信总线302可包括一通路，在上述组件之间传送信息。
存储器303可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其它类型的静态存储设备，随机存取存储器(random access memory，RAM))或者可存储信息和指令的其它类型的动态存储设备，也可以是电可擦可编程只读存储器(Electrically Erasable Programmable Read-Only Memory，EEPROM)、只读光盘(Compact Disc Read-Only Memory，CD-ROM)或其它光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其它磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其它介质，但不限于此。存储器303可以是独立存在，通过通信总线302与处理器301相连接。存储器303也可以和处理器301集成在一起。
通信接口304，使用任何收发器一类的装置，用于与其它设备或通信网络通信，如以太网，无线接入网(RAN)，无线局域网(Wireless Local Area Networks，WLAN)等。
在具体实现中，作为一种实施例，处理器301可以包括一个或多个CPU，例如图3中所示的CPU0和CPU1。
在具体实现中，作为一种实施例，计算机设备可以包括多个处理器，例如图3中所示的处理器301和处理器305。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中，作为一种实施例，计算机设备还可以包括输出设备306和输入设备307。输出设备306和处理器301通信，可以以多种方式来显示信息。例如，输出设备306可以是液晶显示器(liquid crystal display，LCD),发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备307和处理器301通信，可以以多种方式接收用户的输入。例如，输入设备307可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的计算机设备可以是一个通用计算机设备或者是一个专用计算机设备。在具体实现中，计算机设备可以是台式机、便携式电脑、网络服务器、掌上电脑(Personal Digital Assistant，PDA)、移动手机、平板电脑、无线终端设备、通信设备或者嵌入式设备。本发明实施例不限定计算机设备的类型。
其中，存储器303用于存储执行本申请方案的程序代码，并由处理器301来控制执行。处理器301用于执行存储器303中存储的程序代码308。程序代码308中可以包括一个或多个软件模块。图2中所示的VNF 130可以通过处理器301以及存储器303中的程序代码308中的一个或多个软件模块，来确定用于开发应用的数据。
接下来，对本发明实施例涉及的业务处理的方法进行详细介绍，具体请参见如下图4至图6所示的几个实施例。
图4是根据一示例性实施例示出的一种业务路由的方法流程图。请参考图4，该业务路由的方法可以应用于上述图2所示的系统中，其中，该实施例中所述的VNF是指图2所示系统中的前端网元，所述的下一个VNF是指图2所示系统中的后端网元。该业务路由的方法可以包括如下几个实现步骤：
步骤401：VNF接收灰度策略控制中心下发的灰度策略描述文件。
在实际实现中，为了便于VNF确定需要将哪些用户确定为灰度用户，一般由灰度策略控制中心预先向该VNF下发灰度策略描述文件，以通过该灰度策略描述文件告知VNF所确定的灰度策略。
需要说明的是，这里仅是以该灰度策略控制中心向VNF下发灰度策略描述文件为例进行说明，在实际实现中，为了保证各个VNF均可以获知灰度策略，通常该灰度策略控制中心还可以将该灰度策略描述文件下发给各个VNF，这里对此不做限定。
在实际应用场景中，根据灰度策略控制中心所确定的灰度策略不同，该灰度策略描述文件包括的内容也不同，具体可以包括如下几种情况：
第一种情况：该灰度策略描述文件包括灰度百分比。
在该种情况下，灰度策略控制中心确定的灰度策略是灰度百分比的方式。即灰度策略控制中心仅通知VNF需要将多少用户确定为灰度用户，但灰度策略控制中心没有指定具体是将哪些用户确定为灰度用户。此时，需要由该VNF根据该灰度百分比来确定需要将哪些用户确定为灰度用户，其具体实现请参见如下步骤402中的第一种实现方式。
第二种情况：该灰度策略描述文件包括属于灰度用户的用户范围。
在该种情况下，灰度策略控制中心确定的灰度策略是直接指定哪些用户为灰度用户，并将所指定的属于灰度用户的用户范围通过灰度策略描述文件下发给VNF。
其中，该用户范围可以包括但不限于位置范围、号段或号码列表。其中，该位置范围是指用户所处的位置的范围，例如，该位置范围可以为A城市；该号段用于表示用户所使用的电话号码中某一位或某几位符合一定的规则，例如，该号段可以是指电话号码的第四位至第七位处于0100至0112范围内，再如，该号段还可以是指电话号码的最后一位为偶数等；该号码列表可以用于存储属于灰度用户的电话号码。
需要说明的是，本发明实施例仅是以该用户范围包括位置范围、号段或号码列表为例进行说明，在另一实施例中，该用户范围还可能包括其它信息，例如，该用户范围还可能包括用户等级，其中，该用户等级可以用于指示用户是否为贵宾(Very Important Person，VIP)用户等；再如，该用户范围还可以包括预付费或后付费的用户等，本发明实施例对此不做限定。
进一步地，由于在对VNF进行灰度升级的过程中，灰度策略控制中心可能将整个灰度升级划分为N个批次，并根据不同的灰度策略将不同用户归属到不同的批次上。因此，在实际实现中，该灰度策略控制中心还可以在灰度策略描述文件中添加批次值，该批次值用于指示本次确定为灰度用户所对应的批次。如此，在后续处理过程中，如果某批次在灰度验证后发 现升级后的VNF存在问题，也可对该批次值对应的灰度用户进行分批回退处理。其中，上述N为大于1的整数。
在实际实现中，该灰度策略控制中心可以一次性向VNF下发所有批次的灰度策略描述文件，或者，该灰度策略控制中心也可以分批次逐步地向VNF下发灰度策略描述文件。
还需要说明的是，如前文所述，由于各个VNF可能来自不同的供应商，而不同供应商对灰度策略描述文件所定义的语义可能不同。并且，在实际实现中，由于该灰度策略控制中心在向各个VNF下发灰度策略描述文件之前，需要读取不同供应商各自提供的灰度策略描述文件，并在显示界面上呈现，自定义编辑修改其中的内容后提交保存。之后，灰度策略控制中心将被编辑修改并保存后的灰度策略描述文件下发给不同供应商所对应的VNF，以便于各个VNF可以解析自己所定义的灰度策略描述文件，获取该灰度策略描述文件所指示的灰度策略。由此可见，为了保证该灰度策略控制中心能够管理不同VNF所提供的、有各自不同语义的灰度策略描述文件，以使得各个VNF对灰度策略描述文件中所包括内容的理解协同一致，需要对该灰度策略描述文件本身的属性进行统一规定。
为此，在本发明实施例中，该灰度策略描述文件采用统一、普遍的标准格式且支持可编辑，例如，该灰度策略描述文件可以为超文本标记语言(Hyper Text Markup Language，HTML)格式，且该灰度策略描述文件的文件名、及其在软件包中存放的目录位置通常需要固定统一。另外，该灰度策略描述文件的内容在被编辑修改后提交保存时所触发的API事件接口相同，例如，均统一调用javascript:form.submit()接口函数。
步骤402：当VNF接收到来自用户的业务请求时，确定该用户是否为灰度用户。
为了确定需要选择哪些用户使用VNF中已升级的子系统模块，当接收到来自用户的业务请求时，需要由该VNF确定该用户是否为灰度用户。
在实际实现中，该VNF可以根据灰度策略控制中心下发的灰度策略描述文件，确定该用户是否为灰度用户。其中，根据该灰度策略描述文件包括的内容不同，该VNF确定该用户是否为灰度用户可以包括如下几种可能的实现方式：
第一种实现方式：当该灰度策略描述文件包括灰度百分比时，该VNF可以根据该灰度百分比确定该用户是否为灰度用户。
进一步地，该VNF根据灰度百分比确定该用户是否为灰度用户具体可以包括如下过程：该VNF根据该灰度百分比，从每预设数量个用户中选择第i个用户，并将所选择的用户确定为灰度用户，其中，该i为大于1的整数。
其中，该预设数量可以由用户根据实际需求自定义设置，也可以由该VNF默认设置，本发明实施例对此不做限定。
例如，若预设数量为10，上述灰度百分比为10％，i为1，则在具体实现中，该VNF可以从每10个上线的用户中选择第一个用户，并将选择的该用户确定为灰度用户。也即是，将每10个上线用户中的第一个用户确定为灰度用户。
需要说明的是，在实际实现中，可能由于用户关机或被注销等原因，导致一些灰度用户下线，此时，该VNF可以根据当前下线的灰度用户的数量，在后续的每预设数量个用户中，增加被选取作为灰度用户的个数进行补偿，直到在线的灰度用户的数量与上述灰度百分比基本对应一致。
另外，上述是以VNF根据该灰度百分比从每预设数量个用户中选择第i个用户，并将所选择的用户确定为灰度用户为例进行说明。在实际实现中，该VNF还可以根据该灰度百分比，通过其它方式确定灰度用户。譬如，该VNF还可以根据该灰度百分比，从每预设数量次业务中选择第j个业务，并将选择的该业务作为灰度对象，进一步地，将所选择的该业务对应的用户确定为灰度用户。其中，该j为大于1的整数。
第二种实现方式：当该灰度策略描述文件包括属于灰度用户的用户范围时，该VNF可以根据该用户范围，确定该用户是否为灰度用户。
在该种实现方式中，灰度策略控制中心已经直接指定了哪些用户属于灰度用户。在具体实现中，当VNF接收到来自用户的业务请求时，根据该灰度策略描述文件包括的用户范围确定该用户是否为灰度用户。譬如，该业务请求可以携带用户的用户身份信息，例如，该用户身份信息可以包括该用户所使用的电话号码或用户当前所处的位置信息等。之后，该VNF查询该用户身份信息是否属于该用户范围，如果属于，则确定该用户为灰度用户。
例如，假设该业务请求携带的用户身份信息为电话号码，上述用户范围包括号段，该号段是指电话号码的第四位至第七位处于0100-0112之间，则该VNF查询该电话号码的第四位至第七位是否属于该号段。如果该电话号码的第四位至第七位属于该号段，则该VNF确定该用户为灰度用户，否则，确定该用户不是灰度用户。
步骤403：若该VNF确定该用户为该灰度用户，则将该业务请求所请求的业务路由至该VNF中已升级的子系统模块。
如前文所述，该VNF包括未升级以及已升级的具有相同功能的不同子系统模块，如果确定该用户为灰度用户，则说明需要将该用户所请求的业务路由至该VNF中已升级的子系统模块。
进一步地，若灰度策略描述文件中包括批次值，则在确定用户是否为灰度用户之余，还需要判断该批次值是否小于或等于当前灰度升级任务所进行到的灰度发布批次，只有当小于或等于当前灰度升级任务所进行到的灰度发布批次时，该VNF才将该用户所请求的业务路由至该VNF中已升级的子系统模块。
进一步地，该VNF确定该用户为灰度用户时，可以为该用户或本次业务设置灰度标识，例如，该灰度标识可以为ABTest，进一步地，该ABTest对应的值可以为上述批次值，例如，当ABTest＝1时，说明上述批次值为1。
在一种可能的实现方式中，该VNF可以将该灰度标识保存在DB的用户注册数据中，以便于后续该用户发起其它业务时，该VNF可以直接根据存储的用户注册数据，确定该用户是否为灰度用户。
在另一种可能的实现方式中，该VNF还可以将该灰度标识保存在DB的会话数据中，以便于后续处理该业务的其它消息时，直接通过查询该会话数据，确定该业务是否为灰度对象，从而确定发起该业务请求的该用户是否为灰度用户。
进一步地，如果确定该用户为灰度用户，则为了保证其他各个VNF对该用户都统一识别为灰度用户，以使得各个VNF均将该用户的业务路由到升级后的子系统模块中，本发明实施例还包括如下实现步骤。
步骤404：当该VNF确定该用户为灰度用户时，在该业务请求中添加灰度标识。
不难理解，在实际应用场景中，通常需要多个VNF之间交互才能实现网络通信。在这里，为了通知下一个VNF当前进行业务请求的用户被确定为灰度用户，VNF在向下一个VNF发送该业务请求之前，可以在该业务请求中添加灰度标识。
需要说明的是，在实际实现中，上述步骤403和步骤404之间没有先后执行顺序，也即是，该步骤404可以在步骤403之前执行，也可以在该步骤403之后执行，或者，该步骤404还可以与该步骤403同时执行，本发明实施例对此不做限定。
步骤405：该VNF向下一个VNF发送该业务请求，该业务请求用于指示该下一个VNF将该用户确定为该灰度用户。
如步骤404所述，该业务请求中携带有灰度标识，如此，下一个VNF接收到该业务请求后，基于该灰度标识，即可确定该用户为灰度用户。
需要说明书的是，由于各个VNF可能来自不同的供应商，考虑到不同供应商对灰度标识的定义可能不一样，例如，A供应商提供的灰度标识为ABTest，B供应商提供的灰度标识可能为BCTest等。在该种情况下，为了提高VNF的兼容性，可以在灰度策略描述文件中包含统一的灰度标识信息，例如，该灰度标识信息为“灰度标识参数”，即该灰度策略描述文件实际包括的内容可以为：灰度标识参数＝ABTest：BCTest。如此，即使A供应商对应的VNF发送给B供应商对应的VNF的业务请求中携带的是ABTest，B供应商对应的VNF也可以基于灰度策略描述文件的内容，确定该ABTest是灰度标识。
进一步地，若该下一个VNF包括未升级以及已升级的具有相同功能的不同子系统模块，则该下一个VNF确定该用户为灰度用户后，将该用户的业务请求所请求的业务路由至该下一个VNF中已升级的子系统模块。
进一步地，当该下一个VNF是未升级的VNF，且存在具有相同功能的已升级的VNF时，该下一个VNF将该用户的业务请求所请求的业务从未升级的VNF重定向路由至该已升级的VNF。
如前文所述，在一些情况下，对于下一个VNF，该网络中存在未升级的VNF和具有相同功能的已升级的VNF，其中，这里所述的已升级的VNF是指所包括的所有子系统模块均已升级。在该种情况下，需要由该VNF将灰度用户的业务从未升级的VNF重定向路由到已升级的VNF，以对已升级的VNF进行灰度验证。其具体实现过程将通过如下图6所示的实施例进行举例说明。
值得一提的是，在上述实现过程中，前端网元通过在发送给后端网元的业务请求中携带灰度标识，使得后端网元将该用户也同样确定为灰度用户，如此，解决了跨不同VNF进行通信时该不同VNF能够协同进行灰度验证的问题。
需要说明的是，上述实施例仅是以在业务请求中携带灰度标识为例进行说明，在实际实现中，如前文所述，由于灰度策略控制中心将灰度策略描述文件下发给各个VNF，此时，该灰度策略描述文件中包括的是具体的用户范围时，由于各个VNF已经获知哪些用户是灰度用户，因此，前端网元向后端网元发送业务请求时，也可以不携带灰度标识。在该种情况下，对于后端网元来说，当接收到来自前端网元发送的业务请求时，可以直接根据灰度策略控制中心下发的灰度策略描述文件，确定用户是否为灰度用户，如此，同样解决了跨不同VNF进行通信时该不同VNF能够协同进行灰度验证的问题。
本发明实施例提供的业务路由方法应用于VNF中，该VNF包括未升级以及已升级的具有 相同功能的不同子系统模块。当接收到来自用户的业务请求时，为了确定是否选择将该用户的业务路由到该VNF中已升级的子系统模块，该VNF确定该用户是否为灰度用户。如果该用户是灰度用户，则将该用户的业务路由到该VNF中已升级的子系统模块。如此，由该VNF在接收到来自用户的业务请求时确定灰度用户，实现了对已升级的子系统模块进行灰度验证。
为了便于理解，接下来，以上述系统应用于IMS网络中，且前端网元为P-CSCF，后端网元包括I/S-CSCF和AS为例，结合注册流程对本发明实施例涉及的业务路由的方法进行举例介绍。其中，该I/S-CSCF是指I-CSCF和S-CSCF合设后的VNF，本实施例是以下一个VNF中包括未升级以及已升级的具有相同功能的不同子系统模块为例。请参考图5，该图5是根据另一示例性实施例示出的一种业务路由的方法流程图，该业务路由的方法可以应用于上述图2所示的系统中，该业务路由的方法可以包括如下几个实现步骤：
步骤501：P-CSCF接收来自灰度策略控制中心下发的灰度策略描述文件。
如图4实施例的步骤401所述，根据灰度策略控制中心确定的灰度策略不同，该灰度策略描述文件可以包括灰度百分比，或者，该灰度策略描述文件还可以包括属于灰度用户的用户范围。其中，该用户范围可以包括但不限于位置范围、号段和号码列表。进一步地，该灰度策略描述文件还可以包括批次值。
需要说明的是，这里仅是以该灰度策略控制中心将灰度策略描述文件下发给P-CSCF为例进行说明，在实际实现中，该灰度策略控制中心实际上可以将灰度策略描述文件下发给各个VNF，以使得各个VNF均可以获知灰度策略，例如，该各个VNF包括I/S-CSCF和AS。
步骤502：当P-CSCF接收到来自用户的注册请求时，确定该用户是否为灰度用户。
在具体实现中，该P-CSCF根据所接收的灰度策略描述文件确定该用户是否为灰度用户，其具体实现可以参见上述图4实施例中的步骤402，这里不再重复赘述。
需要说明的是，这里仅是以该P-CSCF接收来自灰度策略控制中心下发的灰度策略描述文件，并根据该灰度策略描述文件确定该用户是否为灰度用户为例进行说明。在另一种可能的实施例中，当灰度策略控制中心确定的灰度策略为灰度百分比的方式时，该灰度策略控制中心可以将该灰度策略描述文件下发至HSS中，之后，由该HSS根据该灰度百分比确定灰度用户，并在对应的用户数据中添加灰度标识。如此，各个VNF从该HSS中下载用户数据后，可以根据该用户数据中的灰度标识，确定该用户是否为灰度用户，该各个VNF包括P-CSCF。
进一步地，该灰度策略控制中心还可以在确定需要将哪些用户确定为灰度用户后，直接在该HSS中修改对应用户的用户数据，也即是，与上述实现方式不同的是，还可以不需要HSS根据灰度百分比确定哪些用户是灰度用户，而是由该灰度策略控制中心根据该灰度百分比确定具体的灰度用户，并通过扩展业务发放接口直接修改该HSS中对应用户的用户数据，添加灰度标识。同理，在该种情况下，各个VNF从该HSS中下载用户数据后，可以根据该用户数据中的灰度标识，确定该用户是否为灰度用户，该各个VNF包括P-CSCF。
步骤503：当该P-CSCF确定该用户为灰度用户时，将该用户的注册请求所请求的业务路由至该P-CSCF中已升级的子系统模块。
进一步地，若灰度策略描述文件中包括批次值，则在确定用户是否为灰度用户之余，还需要判断该批次值是否小于或等于当前灰度升级任务所进行到的灰度发布批次，只有当小于 或等于当前灰度升级任务所进行到的灰度发布批次时，该P-CSCF才将该用户所请求的业务路由至该P-CSCF中已升级的子系统模块。
进一步地，该P-CSCF确定该用户为灰度用户时，可以为该用户设置灰度标识，之后，该P-CSCF将该灰度标识保存在DB的用户注册数据中，如此，当该用户发起其它业务(如，会话业务)时，该P-CSCF可以直接根据存储的用户注册数据，确定该用户是否为灰度用户。或者，该P-CSCF将该灰度标识保存在DB的会话数据中，如此，以便于后续处理该业务的其它消息(如，响应消息)时，该P-CSCF直接通过查询该会话数据，确定该业务是否为灰度对象，从而确定发起该业务请求的该用户是否为灰度用户。
需要说明的是，这里所确定的灰度用户仅是在本次业务中为灰度用户，而在下一次业务中，可能根据确定的灰度对象不同，该用户不再是灰度用户。
进一步地，如果确定该用户为灰度用户，则为了保证其他各个网元对该用户都统一识别为灰度用户，以使得各个网元均将该用户的业务路由到升级后的子系统模块中，本发明实施例还包括如下实现步骤。
步骤504：当该P-CSCF确定该用户为灰度用户时，在该注册请求中添加灰度标识。
其具体实现可参见上述图4实施例中的步骤404，这里不再详细介绍。
步骤505：该P-CSCF向I/S-CSCF发送该注册请求。
该I/S-CSCF接收到该注册请求后，当根据该灰度标识确定该用户为灰度用户时，将该用户的业务路由至该I/S-CSCF中已升级的子系统模块中。
进一步地，该I/S-CSCF还可以将该灰度标识保存在该I/S-CSCF的DB的用户注册数据中，以便于该用户发起其它业务时，该I/S-CSCF可以直接通过查询该DB的用户注册数据，即可确定该用户是否为灰度用户。
进一步地，该I/S-CSCF也可以不在本地的DB的用户注册数据中存储该灰度标识，而是通过P-CSCF存储该灰度标识。具体地，该I/S-CSCF可以在返回给P-CSCF的200OK消息的指定参数中携带该灰度标识，以使得该P-CSCF将携带该灰度标识的指定参数存储在P-CSCF的DB的用户注册数据中。例如，该指定参数为Service-route参数。
如此，在后续的会话业务中，该P-CSCF可以在主叫会话请求中携带上述指定参数，以使得该I/S-CSCF根据该指定参数，来确定该用户是否为灰度用户。
进一步地，该I/S-CSCF还可以在发给HSS的多媒体鉴权请求(Multimedia Authentication Request，MAR)/服务分配请求(Server Assignment Request，SAR)消息中携带该灰度标识，以使得该HSS对该灰度标识进行保存。如此，对于被叫系统中的I-CSCF，由于该I-CSCF中没有存储被叫用户的灰度标识，因此，该I-CSCF在接收到被叫会话请求后，给HSS发送位置立即请求(Location Immediate Request，LIR)，获取用户所在的S-CSCF的信息。相应地，该HSS在发送给VNF的位置立即答应(Location Immediate Answer，LIA)响应时，将用户注册时在MAR/SAR消息中携带给HSS的灰度标识返回给I-CSCF，I-CSCF收到LIA响应后，发现是灰度用户，则后续I/S-CSCF将该用户的业务路由至升级后的子系统模块。
进一步地，该I/S-CSCF还可以继续将该灰度标识发送给与该I/S-CSCF交互的下一个VNF，譬如，该下一个VNF为AS，其具体实现请参见如下步骤。
步骤506：该I/S-CSCF向AS发送注册请求，该注册请求中携带上述灰度标识。
步骤507：当该AS确定该用户为灰度用户时，将该用户所请求的业务路由至该AS中已升级的子系统模块。
进一步地，该AS还可以将该灰度标识保存在该AS的DB的用户注册数据中，以便于该用户发起其它业务时，该AS可以直接通过查询该DB的用户注册数据，即可确定该用户是否为灰度用户。
本发明实施例提供的业务路由方法应用于VNF中，该VNF包括未升级以及已升级的具有相同功能的不同子系统模块。当接收到来自用户的业务请求时，为了确定是否选择将该用户的业务路由到该VNF中已升级的子系统模块，该VNF确定该用户是否为灰度用户。如果该用户是灰度用户，则将该用户的业务路由到该VNF中已升级的子系统模块。如此，由该VNF在接收到来自用户的业务请求时确定灰度用户，实现了对已升级的子系统模块进行灰度验证。
图5所示的实施例是以下一个VNF中包括未升级以及已升级的具有相同功能的不同子系统模块为例进行说明。如前文所述，在实际实现中，该网络中还可能存在未升级的VNF以及具有相同功能且已升级的VNF。在该种情况下，前端网元在向下一个VNF发送业务请求时，需要将该业务从未升级的VNF重定向路由至已升级的VNF。为例便于理解，接下里，以网络中同时存在已升级的S-CSCF1和未升级的S-CSCF2，并结合注册流程进行举例说明。
请参考图6，该图6是根据另一示例性实施例示出的一种业务路由的方法流程图，该业务路由的方法可以应用于上述图2所示的系统中，该业务路由的方法可以包括如下几个实现步骤：
步骤601：P-CSCF接收来自灰度策略控制中心下发的灰度策略描述文件。
其具体实现可以参见图5实施例中的步骤501，这里不再重复赘述。
步骤602：当该P-CSCF接收到来自用户的会话请求时，确定该用户是否为灰度用户。
其具体实现可以参见图5实施例中的步骤502，这里不再重复赘述。
步骤603：当该P-CSCF确定该用户为灰度用户时，将该会话请求所请求的业务路由到该P-CSCF中已升级的子系统模块。
其具体实现可以参见图5实施例中的步骤503，这里不再重复赘述。
步骤604；当该P-CSCF确定该用户为灰度用户时，在该注册请求中添加灰度标识。
步骤605：该P-CSCF向I-CSCF发送该注册请求。
步骤606：该I-CSCF接收到该注册请求后，给HSS发送第一用户鉴权请求(User Authorization Request，UAR)消息。
该第一UAR消息用于获取用户当前所在的S-CSCF的信息。
步骤607：该HSS给I-CSCF返回用户所在的S-CSCF的信息。
在实际实现中，在对S-CSCF1进行升级前，先将用户从未升级的S-CSCF1迁移注册至S-CSCF2，之后，对该S-CSCF1进行升级。因此，在这里，HSS给I-CSCF返回用户所在的S-CSCF的信息为S-CSCF2的信息。
其中，S-CSCF的信息可以用于唯一标识一个S-CSCF，例如，可以为S-CSCF的标识等。
步骤608：I-CSCF根据HSS返回的S-CSCF2的信息，向S-CSCF2发送注册请求。
其中，该注册请求中携带私有扩展参数，该私有扩展参数用于指示该I-CSCF是否支持 305重定向消息。进一步地，该注册请求中携带灰度标识。
步骤609：当该S-CSCF2确定该用户为灰度用户时，向I-CSCF返回305重定向消息，该305重定向消息用于指示I-CSCF将该用户的业务重定向注册至已升级的S-CSCF1。
步骤610：I-CSCF接收到该305重定向消息后，再次给HSS发送第二UAR消息，其中，该第二UAR消息用于指示HSS允许该用户从当前的S-CSCF2更改注册到S-CSCF1。
在实际实现中，HSS接收到该第二UAR消息后，打开reassignment pending flag开关，以允许该用户从当前的S-CSCF2更改注册到S-CSCF1。
步骤611：HSS向I-CSCF返回用户鉴权响应(User Authorization Request，UAA)消息。
步骤612：I-CSCF接收该UAA消息后，向S-CSCF1发送注册请求。
在一种可能的实现方式中，该注册请求中可以携带灰度标识。
步骤613：S-CSCF1接收该注册请求后，当确定该用户为灰度用户时，在DB的用户注册数据中添加该灰度标识。
在实际实现中，该S-CSCF1可以根据上述注册消息携带的灰度标识确定该用户为灰度用户，或者，该S-CSCF1也可以根据灰度策略控制中心下发的灰度策略描述文件，确定该用户为灰度用户。其中，根据灰度策略控制中心下发的灰度策略描述文件，确定该用户为灰度用户可以参见上述实施例，这里不再详细介绍。
进一步地，当执行完注册流程，并且注册成功后，P-CSCF可以保存该用户新注册的S-CSCF1的信息。如此，当该用户发起主叫会话请求时，如果该P-CSCF确定该用户已注册到升级后的S-CSCF1，则向该S-CSCF1发送主叫会话请求。
进一步地，该S-CSCF1接收该主叫会话请求并确定该用户为灰度用户后，可对该用户的业务的关键绩效指标(Key Performance Indicators，KPI)进行单独统计。其中，该KPI可以包括但不限于呼叫接通率、应答率、接续时长。如果KPI统计正常，则可以将更多的灰度用户从S-CSCF2迁回至S-CSCF1，以对新版本进行灰度验证，如果KPI统计异常，则可以终止回迁和灰度验证过程。
本发明实施例提供的业务路由方法应用于VNF中，该VNF包括未升级以及已升级的具有相同功能的不同子系统模块。当接收到来自用户的业务请求时，为了确定是否选择将该用户的业务路由到该VNF中已升级的子系统模块，该VNF确定该用户是否为灰度用户。如果该用户是灰度用户，则将该用户的业务路由到该VNF中已升级的子系统模块。如此，由该VNF在接收到来自用户的业务请求时确定灰度用户，实现了对已升级的子系统模块进行灰度验证。另外，该VNF确定灰度用户后，可以在发送给下一个VNF的业务请求中添加灰度标识，以通知下一个VNF该用户为灰度用户，从而实现多个VNF之间的协同灰度验证。
参见图7A，该图7A是根据一示例性实施例示出的一种业务路由装置的结构示意图，该装置配置于VNF中，该装置包括：
确定模块710，用于执行上述图4实施例中的步骤402、图5实施例中的步骤502或图6实施例中的步骤602；
路由模块720，用于执行上述图4实施例中的步骤403、图5实施例中的步骤503或图6实施例中的步骤603。
可选地，请参考图7B，该装置还包括：
第一接收模块730，用于执行上述图4实施例中的步骤401、图5实施例中的步骤501或图6实施例中的步骤601。
相应地，该确定模块710用于根据所述灰度百分比确定所述用户是否为灰度用户。
可选地，确定模块710用于：
根据所述灰度百分比，从每预设数量个用户中选择第i个用户，所述i为大于1的整数；
将所选择的用户确定为所述灰度用户。
可选地，请参考图7C，该装置还包括：
添加模块740，用于执行上述图4实施例中的步骤404、图5实施例中的步骤504或图6实施例中的步骤604；
发送模块750，用于执行上述图4实施例中的步骤405、图5实施例中的步骤505或图6实施例中的步骤605。
可选地，请参考图7D，该装置还包括：
第二接收模块760，用于执行上述图4实施例中的步骤401、图5实施例中的步骤501或图6实施例中的步骤601。
本发明实施例提供的业务路由方法应用于VNF中，该VNF包括未升级以及已升级的具有相同功能的不同子系统模块。当接收到来自用户的业务请求时，为了确定是否选择将该用户的业务路由到该VNF中已升级的子系统模块，该VNF确定该用户是否为灰度用户。如果该用户是灰度用户，则将该用户的业务路由到该VNF中已升级的子系统模块。如此，由该VNF在接收到来自用户的业务请求时确定灰度用户，实现了对已升级的子系统模块进行灰度验证。另外，该VNF确定灰度用户后，可以在发送给下一个VNF的业务请求中添加灰度标识，以通知下一个VNF该用户为灰度用户，从而实现多个VNF之间的协同灰度验证。
综上所述，本发明实施例提供的业务路由方法应用于VNF中，该VNF包括未升级以及已升级的具有相同功能的不同子系统模块。当接收到来自用户的业务请求时，为了确定是否选择将该用户的业务路由到该VNF中已升级的子系统模块，该VNF确定该用户是否为灰度用户。如果该用户是灰度用户，则将该用户的业务路由到该VNF中已升级的子系统模块。如此，由该VNF在接收到来自用户的业务请求时确定灰度用户，实现了对已升级的子系统模块进行灰度验证。
需要说明的是：上述实施例提供的业务路由装置在实现业务路由方法时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的业务路由装置与业务路由方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意结合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包 括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如：同轴电缆、光纤、数据用户线(Digital Subscriber Line，DSL))或无线(例如：红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如：软盘、硬盘、磁带)、光介质(例如：数字通用光盘(Digital Versatile Disc，DVD))、或者半导体介质(例如：固态硬盘(Solid State Disk，SSD))等。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述为本申请提供的实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (17)

  1. 一种业务路由的方法，应用于虚拟网络功能VNF中，其特征在于，所述VNF包括未升级以及已升级的具有相同功能的不同子系统模块，所述方法包括：
    当接收到来自用户的业务请求时，确定所述用户是否为灰度用户；
    若确定所述用户为所述灰度用户，则将所述业务请求所请求的业务路由至所述VNF中已升级的子系统模块。
  2. 如权利要求1所述的方法，其特征在于，所述确定所述用户是否为灰度用户之前，还包括：
    接收灰度策略控制中心下发的灰度策略描述文件，所述灰度策略描述文件包括灰度百分比；
    相应地，所述确定所述用户是否为灰度用户，包括：
    根据所述灰度百分比确定所述用户是否为灰度用户。
  3. 如权利要求2所述的方法，其特征在于，所述根据所述灰度百分比确定所述用户是否为灰度用户，包括：
    根据所述灰度百分比，从每预设数量个用户中选择第i个用户，所述i为大于1的整数；
    将所选择的用户确定为所述灰度用户。
  4. 如权利要求2所述的方法，其特征在于，所述确定用户是否为灰度用户之后，还包括：
    当确定所述用户为所述灰度用户时，在所述业务请求中添加灰度标识；
    向下一个VNF发送所述业务请求，所述业务请求用于指示所述下一个VNF将所述用户确定为所述灰度用户。
  5. 如权利要求4所述的方法，其特征在于，所述向下一个VNF发送所述业务请求之后，还包括：
    当所述下一个VNF是未升级的VNF，且存在具有相同功能的已升级的VNF时，所述下一个VNF将所述用户的注册请求所请求的业务从所述未升级的VNF重定向路由至所述已升级的VNF。
  6. 如权利要求4所述的方法，其特征在于，所述向下一个VNF发送所述业务请求之后，还包括：
    当所述下一个VNF包括未升级以及已升级且具有相同功能的不同子系统模块时，所述下一个VNF将所述业务请求所请求的业务路由至所述下一个VNF中已升级的子系统模块。
  7. 如权利要求1所述的方法，其特征在于，所述确定所述用户是否为灰度用户之前，还包括：
    接收灰度策略控制中心下发的灰度策略描述文件，所述灰度策略描述文件包括属于灰度用户的用户范围；
    相应地，所述确定所述用户是否为灰度用户，包括：
    基于所述用户范围，确定所述用户是否为所述灰度用户。
  8. 如权利要求7所述的方法，其特征在于，所述用户范围包括位置范围、号段或号码列表。
  9. 一种业务路由的装置，配置于VNF中，其特征在于，所述VNF包括未升级以及已升级的具有相同功能的不同子系统模块，所述装置包括：
    确定模块，用于当接收到来自用户的业务请求时，确定所述用户是否为灰度用户；
    路由模块，用于当确定所述用户为所述灰度用户时，将所述业务请求所请求的业务路由至所述VNF中已升级的子系统模块。
  10. 如权利要求9所述的装置，其特征在于，所述装置还包括：
    第一接收模块，用于接收灰度策略控制中心下发的灰度策略描述文件，所述灰度策略描述文件包括灰度百分比；
    相应地，所述确定模块还用于：
    根据所述灰度百分比确定所述用户是否为灰度用户。
  11. 如权利要求10所述的装置，其特征在于，所述确定模块用于：
    根据所述灰度百分比，从每预设数量个用户中选择第i个用户，所述i为大于1的整数；
    将所选择的用户确定为所述灰度用户。
  12. 如权利要求10所述的装置，其特征在于，所述装置还包括：
    添加模块，用于当确定所述用户为所述灰度用户时，在所述业务请求中添加灰度标识；
    发送模块，用于向下一个VNF发送所述业务请求，所述业务请求用于指示所述下一个VNF将所述用户确定为所述灰度用户。
  13. 如权利要求12所述的装置，其特征在于，当所述下一个VNF是未升级的VNF，且存在具有相同功能的已升级的VNF时，所述下一个VNF将所述用户的注册请求所请求的业务从所述未升级的VNF重定向路由至所述已升级的VNF。
  14. 如权利要求12所述的装置，其特征在于，所述向下一个VNF发送所述业务请求之后，当所述下一个VNF包括未升级以及已升级且具有相同功能的不同子系统模块时，所述下一个VNF将所述业务请求所请求的业务路由至所述下一个VNF中已升级的子系统模块。
  15. 如权利要求9所述的装置，其特征在于，所述装置还包括：
    第二接收模块，用于接收灰度策略控制中心下发的灰度策略描述文件，所述灰度策略描述文件包括属于灰度用户的用户范围；
    相应地，所述确定模块还用于：
    基于所述用户范围，确定所述用户是否为所述灰度用户。
  16. 如权利要求15所述的装置，其特征在于，所述用户范围包括位置范围、号段或号码列表。
  17. 一种计算机可读存储介质，所述计算机可读存储介质上存储有指令，其特征在于，所述指令被处理器执行时实现权利要求1-8所述的任一项方法的步骤。
PCT/CN2018/103936 2017-09-07 2018-09-04 业务路由的方法、装置及存储介质 WO2019047821A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710799280.0A CN109474522B (zh) 2017-09-07 2017-09-07 业务路由的方法、装置及存储介质
CN201710799280.0 2017-09-07

Publications (1)

Publication Number Publication Date
WO2019047821A1 true WO2019047821A1 (zh) 2019-03-14

Family

ID=65634628

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/103936 WO2019047821A1 (zh) 2017-09-07 2018-09-04 业务路由的方法、装置及存储介质

Country Status (2)

Country Link
CN (1) CN109474522B (zh)
WO (1) WO2019047821A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110609701A (zh) * 2019-08-29 2019-12-24 凡普数字技术有限公司 提供服务的方法、装置和存储介质
CN111506329A (zh) * 2020-04-21 2020-08-07 北京思特奇信息技术股份有限公司 一种升级方法、系统和电子设备
CN113495747A (zh) * 2020-04-07 2021-10-12 北京京东振世信息技术有限公司 一种灰度发布方法和装置

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111404979B (zh) * 2019-09-29 2023-04-07 杭州海康威视系统技术有限公司 业务请求处理的方法、装置及计算机可读存储介质
CN110798524A (zh) * 2019-10-31 2020-02-14 成都知道创宇信息技术有限公司 页面访问方法、装置、电子设备和存储介质
CN113127023B (zh) * 2019-12-31 2024-04-09 华为技术有限公司 业务升级的方法、装置和系统
CN111290867A (zh) * 2020-02-27 2020-06-16 北京三快在线科技有限公司 流量调度方法、业务服务器、存储介质及流量调度系统
CN111786885B (zh) * 2020-06-23 2022-07-05 中国工商银行股份有限公司 分布式全链路灰度路由方法及装置
CN111930420B (zh) * 2020-07-30 2023-07-07 中国工商银行股份有限公司 无侵入式通用代码级灰度路由系统及方法
CN113381938B (zh) * 2021-06-30 2022-12-06 北京字节跳动网络技术有限公司 数据包发送方法、装置、存储介质及电子设备
CN113726551B (zh) * 2021-07-22 2022-12-20 新华三信息安全技术有限公司 配置方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150063166A1 (en) * 2013-08-27 2015-03-05 Futurewei Technologies, Inc. System and Method for Mobile Network Function Virtualization
CN105099789A (zh) * 2015-09-02 2015-11-25 华为技术有限公司 一种网元升级方法及设备
CN106161173A (zh) * 2015-04-15 2016-11-23 中兴通讯股份有限公司 一种实现虚拟网络功能部署规格配置的方法及装置
CN106385330A (zh) * 2016-09-07 2017-02-08 中国联合网络通信集团有限公司 一种网络功能虚拟化编排器的实现方法及装置

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100407638C (zh) * 2004-04-14 2008-07-30 华为技术有限公司 一种软件升级及回退方法
KR101979362B1 (ko) * 2014-01-29 2019-08-28 후아웨이 테크놀러지 컴퍼니 리미티드 가상화된 네트워크 기능을 업그레이드하는 방법 및 네트워크 기능 가상화 오케스트레이터

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150063166A1 (en) * 2013-08-27 2015-03-05 Futurewei Technologies, Inc. System and Method for Mobile Network Function Virtualization
CN106161173A (zh) * 2015-04-15 2016-11-23 中兴通讯股份有限公司 一种实现虚拟网络功能部署规格配置的方法及装置
CN105099789A (zh) * 2015-09-02 2015-11-25 华为技术有限公司 一种网元升级方法及设备
CN106385330A (zh) * 2016-09-07 2017-02-08 中国联合网络通信集团有限公司 一种网络功能虚拟化编排器的实现方法及装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110609701A (zh) * 2019-08-29 2019-12-24 凡普数字技术有限公司 提供服务的方法、装置和存储介质
CN113495747A (zh) * 2020-04-07 2021-10-12 北京京东振世信息技术有限公司 一种灰度发布方法和装置
CN113495747B (zh) * 2020-04-07 2023-09-26 北京京东振世信息技术有限公司 一种灰度发布方法和装置
CN111506329A (zh) * 2020-04-21 2020-08-07 北京思特奇信息技术股份有限公司 一种升级方法、系统和电子设备

Also Published As

Publication number Publication date
CN109474522B (zh) 2021-02-23
CN109474522A (zh) 2019-03-15

Similar Documents

Publication Publication Date Title
WO2019047821A1 (zh) 业务路由的方法、装置及存储介质
CN111052711B (zh) 发现由网络存储库功能提供的服务的方法
WO2018024059A1 (zh) 一种虚拟化网络中业务部署的方法和装置
US11175796B2 (en) Menu management method, server, and system
US9348409B2 (en) System, method and apparatus for controlling multiple applications and services on a digital electronic device
US8458703B2 (en) Application requesting management function based on metadata for managing enabler or dependency
CN105812171B (zh) 一种虚拟化的网络功能vnf控制方法和设备
US10291486B2 (en) System and method for supporting implicit versioning in a transactional middleware machine environment
US11778455B2 (en) Subscriber identity management method, device, and system
US20120005586A1 (en) Method and apparatus for dynamic network device start up
US9952888B2 (en) Method and system to dynamically instantiate virtual repository for any services
WO2019024679A1 (zh) 网络功能的升级方法及升级管理实体
CN110505318B (zh) 统一资源定位符寻址方法及装置、网络系统
CN109522055B (zh) 基于分布式服务调用的连接预热方法及系统
TWI668634B (zh) 基於軟體容器提供雲端服務之系統及方法
US11093309B1 (en) Communication hub for information technology (IT) services
US9860736B1 (en) Providing network resource access based on a purpose identifier
US9609457B2 (en) Mobile application procurement and configuration options for VOIP service
JP2019049942A (ja) 新旧システムの並行稼働に伴う移行負担・リスクを軽減するシステム移行方法、移行システム及びプログラム
US11757976B2 (en) Unified application management for heterogeneous application delivery
US10509638B1 (en) Method and system for deploying third party device services through an enclosed appliance interface using containers
EP4190122A1 (en) Apparatus and methods for coordination of analytics information accessing in communication networks
WO2018120222A1 (zh) 一种管理vnffg的方法、装置和系统
JP6243294B2 (ja) 通信システム、制御装置及びデータベースアクセス方法
JP4283595B2 (ja) 情報処理装置、オブジェクト管理方法、オブジェクト管理プログラム及び記録媒体

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18854176

Country of ref document: EP

Kind code of ref document: A1