WO2021136233A1 - 业务升级的方法、装置和*** - Google Patents

业务升级的方法、装置和*** Download PDF

Info

Publication number
WO2021136233A1
WO2021136233A1 PCT/CN2020/140629 CN2020140629W WO2021136233A1 WO 2021136233 A1 WO2021136233 A1 WO 2021136233A1 CN 2020140629 W CN2020140629 W CN 2020140629W WO 2021136233 A1 WO2021136233 A1 WO 2021136233A1
Authority
WO
WIPO (PCT)
Prior art keywords
gray
node
service
scale
upgrade
Prior art date
Application number
PCT/CN2020/140629
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 EP20911063.4A priority Critical patent/EP4050850A4/en
Publication of WO2021136233A1 publication Critical patent/WO2021136233A1/zh
Priority to US17/852,930 priority patent/US20220326940A1/en

Links

Images

Classifications

    • 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
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G06F8/656—Updates while running
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0826—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for reduction of network costs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0836—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability to enhance reliability, e.g. reduce downtime
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects

Definitions

  • the present invention relates to wireless communication technology, in particular to a method, device and system for service upgrade.
  • the embodiment of the present invention provides a method, device and system for service upgrade, which are used to reduce the cost of service upgrade and improve service reliability.
  • an embodiment of the present application provides a service upgrade method, the method includes: adding a first node to a first device, the first device is used for storing service-related data, and the first node is used for grayscale upgrade The first service; the first device configures the gray-scale rule, the first device identifies gray-scale users according to the gray-scale rules, and the gray-scale users are used to test the first service; the first device sends the gray-scale rules to the second device, and the The device is a front-end device of the first device; the first node performs a grayscale upgrade of the first service.
  • the first device and the second device can synchronize the gray-scale rules, identify the gray-scale users, and make the gray-scale users the first
  • the business test can cover the first device and the second device, realize the grayscale upgrade back-to-end test coverage, increase the possibility of finding problems in the grayscale upgrade stage, reduce the possibility of business upgrade failure and rollback, and reduce the business upgrade cost.
  • the first device includes at least one second node, and the second node is used to store or manage user data; after the first node performs the gray-scale upgrade of the first service, the gray-scale user Test of the first service; after the test is passed, at least one second node performs a rolling upgrade of the first service. After the grayscale upgrade is successful, the rolling upgrade can reduce the number of users that are simultaneously affected during the upgrade process and improve service reliability.
  • the method further includes: deleting the above-mentioned first node from the first device.
  • the data of the grayscale user is copied to the above-mentioned first node.
  • the first node before deleting the first node from the first device, the first node synchronizes the data of the gray-scale user in the first node to the original node, where the original node is The data of the gray-scale user is copied to the node where the data of the gray-scale user is located before the first node.
  • the above-mentioned first node is a DID container or a PID container.
  • the first device identifying the gray user according to the gray rule includes: the load balancing (LB) node of the first device recognizes the gray user according to the gray rule.
  • LB load balancing
  • the first device is a unified data repository (UDR).
  • UDR unified data repository
  • the second device is a unified data management network element (UDM); or, the second device is a policy control function network element (PCF).
  • UDM unified data management network element
  • PCF policy control function network element
  • an embodiment of the present application provides a service upgrade method, the method includes: a second device receives a gray scale rule from a first device; wherein the first device is used to store service data, and the second device is the first device The front-end device; the second device identifies the gray user according to the gray rule, and the gray user is used to test the first service of the gray upgrade.
  • the first device and the second device can synchronize the grayscale rules, identify grayscale users, so that the first service test of the grayscale users can cover the first device and the second device, and realize the grayscale upgrade backend End-to-end test coverage improves the possibility of finding problems during the grayscale upgrade stage, reduces the possibility of rollbacks due to business upgrade failures, and reduces the cost of business upgrades.
  • the second device is a gray user accessing a high-version application (application, APP), and the high-version APP obtains the data of the first service from the first device.
  • APP high-version application
  • the second device identifying the gray user according to the gray rule includes: the load balancing (LB) node of the second device recognizes the gray user according to the gray rule.
  • LB load balancing
  • the first device is a unified data repository (UDR).
  • UDR unified data repository
  • the second device is a unified data management network element (UDM); or, the second device is a policy control function network element (PCF).
  • UDM unified data management network element
  • PCF policy control function network element
  • an embodiment of the present application provides a communication device for implementing the communication device of the first aspect.
  • the communication device of the third aspect includes corresponding modules, units, or means for realizing the above-mentioned functions.
  • the modules, units, or means can be realized by hardware, software, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the above-mentioned functions.
  • an embodiment of the present application provides a communication device for implementing the communication device of the second aspect.
  • the communication device of the fourth aspect includes corresponding modules, units, or means for realizing the above-mentioned functions, and the modules, units, or means can be realized by hardware, software, or by hardware executing corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the above-mentioned functions.
  • an embodiment of the present application provides a communication device, including a processor, the processor is configured to read instructions from a memory, and execute the instructions to implement the method of the first aspect.
  • the communication device includes the memory.
  • the communication device may be a chip.
  • an embodiment of the present application provides a communication device, including a processor, the processor is configured to read instructions from a memory, and execute the instructions to implement the method of the second aspect.
  • the communication device includes the memory.
  • the communication device may be a chip.
  • an embodiment of the present application provides a computer-readable storage medium, including instructions, characterized in that, when the instructions are executed on a communication device, the communication device is caused to implement any of the foregoing methods.
  • an embodiment of the present application provides a computer program product, including instructions, characterized in that, when the instructions are executed on a communication device, the communication device is caused to implement any of the foregoing methods.
  • an embodiment of the present application provides a communication system, including the third aspect or the fifth aspect.
  • it further includes the communication device of the fourth aspect or the sixth aspect.
  • the gray-scale upgrade and verification of the first service can be carried out by fewer gray-scale users, and the back-to-end test coverage of the gray-scale upgrade can be realized, which improves the possibility of finding problems during the gray-scale upgrade stage and reduces
  • the possibility of rollbacks due to business upgrade failures reduces the cost of business upgrades; after successful gray-scale upgrades, rolling upgrades can reduce the number of users that are simultaneously affected during the upgrade process and improve business reliability.
  • FIG. 1 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 2 is a schematic flowchart of a service upgrade method provided by an embodiment of the application
  • FIG. 3 is a schematic flowchart of another service upgrade method provided by an embodiment of the application.
  • FIG. 4 is a schematic flowchart of another service upgrade method provided by an embodiment of this application.
  • FIG. 5 is a schematic structural diagram of a communication device provided by an embodiment of this application.
  • FIG. 6 is a schematic structural diagram of another communication device provided by an embodiment of the application.
  • modules in this application is only a logical division In actual applications, there may be other divisions when implementing. For example, multiple modules may be combined or integrated in another system, or some features may be ignored or not implemented.
  • the displayed or discussed mutual The coupling or direct coupling or communication connection may be through some interfaces, and the indirect coupling or communication connection between the modules may be electrical or other similar forms, which are not limited in this application.
  • the modules or sub-modules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed to multiple circuit modules, and some or all of them may be selected according to actual needs. Module to achieve the purpose of this application program.
  • FIG. 1 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device includes a service node (front end, FE) and a data node (back end, BE).
  • FE is used for business processing
  • BE is used to store user data or business data
  • BE can provide data storage, data management, and data service functions for FE
  • data can be read through BE Take and store.
  • the FE may include a load balancing (LB) node, and the LB node is used to perform load balancing processing; the FE may be deployed with an application (application, APP), and the APP is used to process services.
  • the BE may include an LB node, and multiple service provisioning gateway (provisioning gateway, PGW) containers, routing switch unit (routing switch unit, RSU) containers, and DID (Docker in docker) containers.
  • provisioning gateway, PGW provisioning gateway
  • routing switch unit routing switch unit
  • RSU routing switch unit
  • DID Docker in docker
  • the PGW container is used for business processing
  • the RSU container is used for storing user data
  • the DID container can be used for business processing and storing user data.
  • the aforementioned container may also be another container or virtual machine used to store or manage data, which is not limited in the embodiment of the present application.
  • the above-mentioned communication device may be a device entity that integrates the above-mentioned FE and the above-mentioned BE; the above-mentioned communication device may also be composed of distributed deployment of FE and BE.
  • the above FE part may be a UDM network element, the above FE part may also be a PCF network element; the above BE part may be a UDR network element.
  • UDM network element is a kind of network element used for data management. This network element is mainly used to generate authentication parameters, store and manage the ID of the permanent user in the system, and manage the user's service network element registration management, such as AMF and SMF that currently provide services for terminal devices.
  • the PCF network element is a network element used for policy control. This network element is mainly used to provide a unified policy framework to manage network behaviors, provide policy rules to the control layer network functions, and be responsible for obtaining user subscription information related to policy decisions.
  • UDR network element is a network element used for unified data storage. This network element is mainly used for storing and retrieving contract data, policy data, and public architecture data; providing relevant data to UDM network elements or PCF network elements.
  • the embodiment of the present application provides a method for service upgrade, which is used to reduce the cost of service upgrade and improve the success rate of service upgrade.
  • Fig. 2 is a schematic flowchart of a service upgrade method provided by an embodiment of the present application.
  • This method is used to upgrade the first service.
  • This method adds a virtual machine or container for grayscale upgrade to the BE part; the method also synchronizes the grayscale rules in the FE part and the BE part, so that the grayscale users can perform the grayscale upgrade in the FE part and the BE part together.
  • the entire process of business upgrade can be verified; this method performs a rolling upgrade after the above verification is passed, reducing the range of users affected by the upgrade process.
  • Grayscale upgrade involved in this method is a service upgrade method that can smoothly transition.
  • Grayscale upgrade can also be called grayscale release or canary release.
  • AB test is a grayscale upgrade method. Some users continue to use A and some users start to use B. If users have no objections to B, then gradually expand the scope and migrate all users to B. Some users who start using B can be understood as gray users. Through the grayscale upgrade, problems can be found and adjusted in the initial stage of business upgrade.
  • the rolling upgrade involved in this method is to upgrade one or more nodes each time, and then add the upgraded nodes to the production environment, and continue to execute the process until all nodes in the production environment are upgraded.
  • Rolling upgrade can also be called rolling release.
  • the method includes:
  • the DID container is used to perform the grayscale upgrade of the first service.
  • a PGW module a data service gateway (DSG) module, a data routing unit (DRU) module, and a data service unit (DSU) module are deployed in the DID container.
  • the PGW module can be used for business processing
  • the DSG module can be used for message forwarding
  • the DRU module can be used to store routing data
  • the DSU module can be used to store user data.
  • the service data of the current version of the first service and the gray-scale user data are stored in the newly added DID container.
  • the gray user is the user used to perform the gray upgrade test.
  • the service data and gray-scale user data of the current version of the first service can be copied from the PGW container and the RSU container of the above BE to the newly added DID container.
  • real users who use the above services can be invited to participate in the test, and real users who agree to participate in the test are regarded as gray-scale users.
  • a test user may be set for the foregoing service, and the test user may be used to perform service testing.
  • the test user may be maintained by a developer or a tester, and the foregoing test user may be a gray-scale user.
  • the DID container may also be other virtual machines or containers that can be used for grayscale upgrade, such as a PID container, which is not limited in the embodiment of the present application.
  • the BE in S101 can add a pair of DID containers or a pair of PID containers to avoid service interruption when one of the DID containers or one of the PID containers fails.
  • S101 may be executed at any time before S104, which is not limited in the embodiment of the present application.
  • the gray scale rule includes the information of gray scale users.
  • the BE part can identify gray-scale users according to gray-scale rules.
  • the local maintenance terminal configures and issues grayscale rules;
  • the local portal can be a server or a server-side system in BE, and can be used to provide portal services, client authentication and other functions.
  • the grayscale rule may include one or more hash values, and one hash value may be used to identify a grayscale user.
  • FE can identify gray-scale users according to gray-scale rules.
  • the LB node of BE sends the aforementioned gray scale rule to the LB node of FE.
  • the BE sends the gray-scale rule to the FE through the synchronization interface between the BE and the FE.
  • BE imports grayscale rules.
  • BE copies the current version of the service data and grayscale user data of the first service from the PGW container and RSU container to the newly added DID container, upgrades the first service in the newly added DID container, and updates the newly added Business data and gray-scale user data in the DID container.
  • the FE is deployed with the current version of the application (application, APP) 1.0 of the first service and the upgraded version of APP2.0 of the first service.
  • the gray user accesses the first service through the LB node of the FE; after the LB node of the FE part recognizes the gray user according to the above gray rule, the gray user is shunted to APP2.0; APP2.0 performs service processing And send the service request to the LB node of the BE part; after the LB node of the BE part identifies the gray user corresponding to the service request according to the gray rule, it forwards the service request to the above-mentioned new DID container for processing; after the processing is completed, the DID container
  • the response message is fed back to the LB node of the BE, the LB node of the BE part feeds back the response message to APP2.0, and the APP2.0 feeds back the response message to the LB node of the FE part; gray users can judge whether the upgraded first service is passed according to the response message test.
  • the gray-scale test passing may mean that all gray-scale users have passed the S105 test; or, it may also be that all gray-scale users who have participated in the service test of S105 have passed the test, which is not limited in the embodiment of the present application.
  • the rolling upgrade of the BE part may specifically be to upgrade one or more PGW containers, and after the upgrade is successful, upgrade one or more RSU containers.
  • a rollback is performed.
  • the DID container is deleted from the BE.
  • the gray-scale upgrade and verification of the first service is carried out by fewer gray-scale users, which increases the possibility of finding problems during the gray-scale upgrade stage, reduces the possibility of rollbacks due to service upgrade failures, and reduces The cost of business upgrades; after the successful grayscale upgrade, rolling upgrades are used to reduce the number of users that are simultaneously affected during the upgrade process and improve service reliability.
  • the FE part and the BE part can synchronize the grayscale rules to identify grayscale users, so that the first service test of the grayscale users can cover the FE part and the BE part, and realize the grayscale upgrade back-end to End-to-end test coverage improves the possibility of problems found in the gray-scale test phase, reduces the possibility of problems in the subsequent rolling upgrade phase, reduces the possibility of rollbacks, and reduces the cost of business upgrades.
  • Fig. 3 is a schematic flowchart of a service upgrade method provided by an embodiment of the present application. This method is used to upgrade the first service. As shown in Figure 3, the method includes:
  • the first device is used to store and manage service-related data, and the first node is used to upgrade the first service in gray scale.
  • the first device may be the BE in FIG. 2 described above.
  • the first node may be the newly added DID container or PID container in S101. For details, please refer to the content of S101.
  • S202 The first device configures a gray scale rule.
  • the first device identifies a gray-scale user according to the gray-scale rule, and the gray-scale user is used to test the first service.
  • the gray-scale user is used to test the first service.
  • S203 The first device sends the gray scale rule to the second device.
  • the second device is the front-end device of the first device.
  • the front-end device can be understood as the user accessing the service through the first device, and the second device provides the data required by the service for the first device.
  • the second device may be the FE in FIG. 2 described above. For details, please refer to the content of S103.
  • S204 The first node performs a grayscale upgrade of the first service.
  • the first device includes at least one second node, the second node is used to store or manage user data, and after the first node performs the grayscale upgrade of the first service, it performs a test of the grayscale user's first service; After the test is passed, at least one second node performs a rolling upgrade of the first service.
  • the second node may be the PGW container, RSU container, or non-newly added DID container in FIG. 2 above.
  • the above process please refer to the content of S105 and S106.
  • the data of the gray user is copied to the first node.
  • the data of the gray user is copied to the first node.
  • the first node before deleting the first node from the first device, the first node synchronizes the data of the gray user in the first node to the original node, and the data of the gray user in the original node is copied to the gray user before the first node The node where the data is located.
  • the first node synchronizes the data of the gray user in the first node to the original node, and the data of the gray user in the original node is copied to the gray user before the first node The node where the data is located.
  • the content of S107 please refer to the content of S107.
  • the first device identifying a gray-scale user according to the foregoing gray-scale rule includes: a load balancing (LB) node of the first device recognizes a gray-scale user according to the foregoing gray-scale rule.
  • LB load balancing
  • the first device is a unified data repository (UDR).
  • UDR unified data repository
  • the second device is a unified data management network element (unified data management, UDM); or, the second device is a policy control function (PCF) network element.
  • UDM unified data management
  • PCF policy control function
  • the gray-scale rules in the first device and the second device can synchronize the gray-scale rules in the first device and the second device to identify gray-scale users, so that the first service test of the gray-scale users can cover the first device and the second device, and realize the gray-scale upgrade back-to-end test Coverage, increase the possibility of finding problems in the gray-scale test phase, reduce the possibility of problems in the subsequent rolling upgrade phase, reduce the possibility of rollbacks, and thereby reduce the cost of business upgrades.
  • Fig. 4 is a schematic flowchart of a service upgrade method provided by an embodiment of the present application. This method is used to upgrade the first service. As shown in Figure 4, the method includes:
  • S301 The second device receives the grayscale rule from the first device.
  • the first device is used to store and manage business data
  • the second device is a front-end device of the first device.
  • the first device may be the BE in FIG. 2 described above.
  • the second device may be the FE in FIG. 2 described above.
  • the second device identifies a gray-scale user according to the gray-scale rule.
  • the gray user is used to test the first service of gray upgrade.
  • the gray user is used to test the first service of gray upgrade.
  • the second device is a gray user accessing a high-version application (application, APP), and the high-version APP obtains the data of the first service from the first device.
  • application application, APP
  • the high-version APP obtains the data of the first service from the first device.
  • APP high-version application
  • the second device identifying the gray-scale user according to the gray-scale rule includes: a load balancing (LB) node of the second device identifies the gray-scale user according to the gray-scale rule.
  • LB load balancing
  • the first device is a unified data repository (UDR).
  • UDR unified data repository
  • the second device is a unified data management network element (unified data management, UDM); or, the second device is a policy control function (PCF) network element.
  • UDM unified data management
  • PCF policy control function
  • the grayscale rules can be synchronized in the first device and the second device, and grayscale users can be identified, so that the first service test of the grayscale users can cover the first device and the second device, and the grayscale upgrade can be achieved.
  • End-to-end test coverage improves the possibility of problems found in the gray-scale test phase, reduces the possibility of problems in the subsequent rolling upgrade phase, reduces the possibility of rollbacks, and reduces the cost of business upgrades.
  • FIG. 5 is a schematic structural diagram of a communication device 500 provided by an embodiment of the application.
  • the communication device 500 includes one or more processors 501, a communication line 502, and at least one communication interface (in FIG. 5, the communication interface 503 and one processor 501 are taken as an example for illustration), optional
  • the memory 504 may also be included.
  • the processor 501 may be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more programs for controlling the execution of the program of this application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 502 is used to connect different components.
  • the communication interface 503 may be a transceiver module used to communicate with other equipment or communication devices or communication networks, such as Ethernet.
  • the above-mentioned transceiver module may be a network card or an optical fiber switching device.
  • the communication interface 503 may also be a transceiver circuit located in the processor 501 to implement signal input and signal output of the processor.
  • the memory 504 may be a device having a storage function.
  • it can be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), or other types that can store information and instructions
  • Dynamic storage devices can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical disk 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 can be used to carry or store desired program codes in the form of instructions or data structures and can be stored by a computer Any other media taken, but not limited to this.
  • EEPROM electrically erasable programmable read-only memory
  • CD-ROM compact disc read-only memory
  • 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 can
  • the memory may exist independently, and is connected to the processor through the communication line 502.
  • the memory can also be integrated with the processor.
  • the memory 504 is used to store computer-executed instructions for executing the solution of the present application, and the processor 501 controls the execution.
  • the processor 501 is configured to execute computer-executable instructions stored in the memory 504.
  • the computer execution instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
  • the processor 501 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 5.
  • the communication device 500 may include multiple processors, such as the processor 501 and the processor 505 in FIG. 5.
  • processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
  • the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, computer program instructions).
  • the aforementioned communication device 500 may be a general-purpose device or a dedicated device.
  • the communication device 500 may be a network server, an embedded device, or a device having a similar structure in FIG. 5.
  • the embodiment of the present application does not limit the type of the communication device 500.
  • the FE in FIG. 2 may be the communication device as shown in FIG. 5.
  • the processor 501 in FIG. 5 can support the apparatus 500 to perform the functions performed by the FE in FIG. 2.
  • the processor 501 may perform the function of identifying gray-scale users according to gray-scale rules in S103.
  • the communication interface 503 in FIG. 5 can support the device 500 to communicate with other devices.
  • the communication interface 503 may support the device 500 to perform the communication process in S103 in FIG. 2.
  • the BE in FIG. 2 may be the communication device as shown in FIG. 5.
  • the processor 501 in FIG. 5 can support the apparatus 500 to perform the functions performed by the BE in FIG. 2.
  • the processor 501 may perform the function of performing grayscale upgrade in S104, and the processor 501 may also perform the function of performing rolling upgrade in S106.
  • the communication interface 503 in FIG. 5 can support the device 500 to communicate with other devices.
  • the communication interface 503 may support the device 500 to perform the communication process in S103 in FIG. 2.
  • the FE and BE in FIG. 2 may be integrated in the communication device shown in FIG. 5.
  • the processor 501 in FIG. 5 may support the device 500 to perform the functions performed by the FE in FIG. 2, and the processor 505 in FIG. 5 may support the device 500 to perform the functions performed by the BE in FIG. 2.
  • the communication interface 503 in FIG. 5 can support the device 500 to communicate with other devices.
  • Fig. 6 shows a communication device provided by an embodiment of the present application.
  • the embodiments of the present application may divide the communication device into functional units according to the foregoing method embodiments.
  • each functional unit may be divided corresponding to each function, or two or more units may be integrated into one processing module.
  • the above-mentioned integrated unit can be realized in the form of hardware or software function module. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and there may be other division methods in actual implementation.
  • FIG. 6 is a schematic structural diagram of a communication device 600 provided by an embodiment of this application.
  • the communication device 600 includes a processing unit 601 and a transceiver unit 602.
  • the FE in FIG. 2 may be the communication device shown in FIG. 6.
  • the processing unit 601 in FIG. 6 can support the device 600 to perform the functions performed by the FE in FIG. 2.
  • the processing unit 601 may perform the function of identifying gray-scale users according to gray-scale rules in S103.
  • the transceiving unit 602 in FIG. 6 can support the device 600 to communicate with other devices.
  • the transceiving unit 602 may support the device 600 to perform the communication process in S103 in FIG. 2.
  • the BE in FIG. 2 may be the communication device shown in FIG. 6.
  • the processing unit 601 in FIG. 6 can support the apparatus 600 to perform the functions performed by the BE in FIG. 2.
  • the processing unit 601 may perform the function of performing grayscale upgrade in S104, and the processing unit 601 may also perform the function of performing rolling upgrade in S106.
  • the transceiving unit 602 in FIG. 6 can support the device 600 to communicate with other devices.
  • the transceiving unit 602 may support the device 600 to perform the communication process in S103 in FIG. 2.
  • the FE and BE in FIG. 2 may be integrated in the communication device shown in FIG. 6.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

一种业务升级的方法、装置和***，其中，数据节点和业务节点同步灰度规则并进行业务的灰度升级，实现灰度升级后端到端的测试覆盖，提高灰度升级阶段发现问题的可能性，降低业务升级失败而回滚的可能性，降低业务升级的成本。在灰度升级成功之后通过滚动升级减少业务升级的过程中同时影响的用户数量，提高业务可靠性。

Description

业务升级的方法、装置和***
本申请要求于2019年12月31日提交中国专利局、申请号为201911410720.4、申请名称为“业务升级的方法、装置和***”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及无线通信技术，特别涉及一种业务升级的方法、装置和***。
背景技术
丰富的业务和多样化的用户需求，如超高清视频、VR/AR、无人驾驶、IoT等，吸引着众多运营商和用户。产品能否快速交付、快速升级上线新业务成为重要的关注点。现有的无损升级(在升级过程中将整个***划分为两个平面，先升级0平面再升级1平面)可以保证在升级过程中业务不中断，但无法对升级过程中的错误提前识别，升级一旦出问题，影响整局所有用户，整个升级流程必须全部回退。除此之外，现有的升级方式无法支撑新业务快速部署上线验证，新业务必须全量升级后才能验证。
发明内容
本发明实施例提供了一种业务升级的方法、装置和***，用于降低业务升级的成本，提高业务可靠性。
第一方面，本申请实施例提供一种业务升级的方法，该方法包括：在第一装置中新增第一节点，第一装置用于存储业务相关的数据，第一节点用于灰度升级第一业务；第一装置配置灰度规则，第一装置根据该灰度规则识别灰度用户，灰度用户用于测试第一业务；第一装置向第二装置发送该灰度规则，第二装置为第一装置的前端装置；第一节点进行第一业务的灰度升级。
根据第一方面的方法，通过较少的灰度用户进行第一业务的灰度升级和验证，第一装置和第二装置能够同步灰度规则，识别灰度用户，使灰度用户的第一业务测试能够覆盖第一装置和第二装置，实现灰度升级后端到端的测试覆盖，提高在灰度升级阶段发现问题的可能性，降低业务升级失败而回滚的可能性，降低业务升级的成本。
作为一种可选的设计，第一装置包括至少一个第二节点，所述第二节点用于存储或者管理用户数据；上述第一节点进行第一业务的灰度升级之后，进行灰度用户的第一业务的测试；测试通过后，至少一个第二节点进行第一业务的滚动升级。在灰度升级成功之后通过滚动升级能够减少升级的过程中同时影响的用户数量，提高业务可靠性。
作为一种可选的设计，还包括：从第一装置中删除上述第一节点。
作为一种可选的设计，第一节点进行第一业务的灰度升级之前，将灰度用户的数据拷 贝至上述第一节点。
作为一种可选的设计，第一节点从所述第一装置中删除所述第一节点之前，将所述第一节点中所述灰度用户的数据同步至原节点，所述原节点为所述灰度用户的数据拷贝至所述第一节点前所述灰度用户的数据所在的节点。
作为一种可选的设计，上述第一节点为DID容器、或者PID容器。
作为一种可选的设计，第一装置根据灰度规则识别灰度用户包括：第一装置的负载均衡(load balancing,LB)节点根据灰度规则识别灰度用户。
作为一种可选的设计，第一装置为统一数据存储库(unified data repository,UDR)。
作为一种可选的设计，第二装置为统一数据管理网元(unified data management,UDM)；或者，第二装置为策略控制功能网元(policy control function,PCF)。
第二方面，本申请实施例提供一种业务升级的方法，该方法包括：第二装置从第一装置接收灰度规则；其中，第一装置用于存储业务数据，第二装置为第一装置的前端装置；第二装置根据灰度规则识别灰度用户，灰度用户用于测试灰度升级的第一业务。
根据第二方面的方法，第一装置和第二装置能够同步灰度规则，识别灰度用户，使灰度用户的第一业务测试能够覆盖第一装置和第二装置，实现灰度升级后端到端的测试覆盖，提高在灰度升级阶段发现问题的可能性，降低业务升级失败而回滚的可能性，降低业务升级的成本。
作为一种可选的设计，第二装置为灰度用户接入高版本应用(application,APP)，高版本APP从第一装置获取第一业务的数据。
作为一种可选的设计，第二装置根据灰度规则识别灰度用户包括：第二装置的负载均衡(load balancing,LB)节点根据灰度规则识别灰度用户。
作为一种可选的设计，第一装置为统一数据存储库(unified data repository,UDR)。
作为一种可选的设计，第二装置为统一数据管理网元(unified data management,UDM)；或者，第二装置为策略控制功能网元(policy control function,PCF)。
第三方面，本申请实施例提供一种通信装置，用于实现第一方面的通信装置。第三方面的通信装置包括实现上述功能相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
第四方面，本申请实施例提供一种通信装置，用于实现第二方面的通信装置。第四方面的通信装置包括实现上述功能相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的模块或单元。
第五方面，本申请实施例提供一种通信装置，包括处理器，所述处理器用于从存储器读取指令，运行所述指令以实现第一方面的方法。可选的，该通信装置包括该存储器。可选的，该通信装置可以是芯片。
第六方面，本申请实施例提供一种通信装置，包括处理器，所述处理器用于从存储器读取指令，运行所述指令以实现第二方面的方法。可选的，该通信装置包括该存储器。可选的，该通信装置可以是芯片。
第七方面，本申请实施例提供一种计算机可读存储介质，包括指令，其特征在于，当 所述指令在通信装置上执行时，使得所述通信装置实现上述任一种方法。
第八方面，本申请实施例提供一种计算机程序产品，包括指令，其特征在于，当所述指令在通信装置上执行时，使得所述通信装置实现上述任一种方法。
第九方面，本申请实施例提供一种通信***，包括第三方面、或者第五方面。可选的，还包括第四方面或者第六方面的通信装置。
通过本申请的方案，通过较少的灰度用户进行第一业务的灰度升级和验证，而且能够实现灰度升级后端到端的测试覆盖，提高在灰度升级阶段发现问题的可能性，降低业务升级失败而回滚的可能性，降低业务升级的成本；在灰度升级成功之后通过滚动升级减少升级的过程中同时影响的用户数量，提高业务可靠性。
附图说明
图1为本申请实施例提供的一种通信设备的结构示意图；
图2为本申请实施例提供的一种业务升级方法的流程示意图；
图3为本申请实施例提供的另一种业务升级方法的流程示意图；
图4为本申请实施例提供的又一种业务升级方法的流程示意图；
图5为本申请实施例提供的一种通信装置的结构示意图；
图6为本申请实施例提供的又一种通信装置的结构示意图。
具体实施方式
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整的描述。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或模块的过程、方法、***、产品或设备不必限于清楚地列出的那些步骤或模块，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或模块，本申请中所出现的模块的划分，仅仅是一种逻辑上的划分，实际应用中实现时可以有另外的划分方式，例如多个模块可以结合成或集成在另一个***中，或一些特征可以忽略，或不执行，另外，所显示的或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，模块之间的间接耦合或通信连接可以是电性或其他类似的形式，本申请中均不作限定。并且，作为分离部件说明的模块或子模块可以是也可以不是物理上的分离，可以是也可以不是物理模块，或者可以分布到多个电路模块中，可以根据实际的需要选择其中的部分或全部模块来实现本申请方案的目的。
如图1所示，图1示出了本申请实施例提供的一种通信设备的结构示意图，该通信设备包括：业务节点(front end,FE)和数据节点(back end,BE)。
具体的，FE用于进行业务处理，BE用于存储用户数据或者业务数据；BE可以为FE提供数据存储、数据管理、数据服务的功能；FE处理业务的过程中，可以通过BE进行数 据的读取、存储。
其中，该FE可以包括负载均衡(load balancing,LB)节点，该LB节点用于进行负载均衡处理；该FE可以部署有应用(application,APP)，APP用于处理业务。该BE可以包括LB节点，和多个业务发放网关(provisioning gateway,PGW)容器、路由交换单元(routing switch unit,RSU)容器、DID(Docker in docker)容器。其中，PGW容器用于进行业务处理；RSU容器用于存储用户数据；DID容器可以用于进行业务处理和存储用户数据。上述容器还可以是其他用于存储或者管理数据的容器或者虚拟机，本申请实施例对此不作限定。
可以理解的是，上述通信设备可以是一个设备实体，该设备实体集成了上述FE和上述BE；上述通信设备还可以由分布式部署的FE和BE组成。
以5G为例，上述FE部分可以是UDM网元，上述FE部分还可以是PCF网元；上述BE部分可以是UDR网元。
UDM网元是一种用于数据管理的网元。该网元主要用于产生鉴权参数、存储和管理***中永久性用户的ID、用户的服务网元注册管理，例如当前为终端设备提供业务的AMF、SMF。
PCF网元是一种用于策略控制的网元。该网元主要用于提供统一的策略框架以管理网络行为，提供策略规则给控制层网络功能，同时负责获取与策略决策相关的用户签约信息。
UDR网元是一种用于统一数据存储的网元。该网元主要用于存储和检索签约数据、策略数据和公共架构数据；向UDM网元、或者PCF网元提供相关数据。
为了实现产品快速交付、快速升级上线新业务的需求，上述通信设备需要在业务不中断的同时进行业务升级。现有的升级方式需要新业务全量升级之后才能验证，在升级的过程中出现问题需要整个升级流程全部回退，业务升级的成本和失败率较高。鉴于此，本申请实施例提供一种业务升级的方法，用于降低业务升级的成本并提高业务升级的成功率。
下面将结合图2至图4对本申请实施例提供的业务升级方法进行具体阐述。
图2是本申请实施例提供的一种业务升级方法的流程示意图。该方法用于对第一业务进行升级。该方法在BE部分新增用于灰度升级的虚拟机或者容器；该方法还在FE部分和BE部分同步灰度规则，使灰度用户能够在FE部分和BE部分协同进行灰度升级，从而能够对业务升级进行全流程验证；该方法在上述验证通过后，进行滚动升级，减少升级过程影响的用户范围。
该方法涉及的灰度升级是一种能够平滑过渡的业务升级方式。灰度升级也可以称为灰度发布或者金丝雀发布。AB test就是一种灰度升级方式，让一部分用户继续用A，一部分用户开始用B，如果用户对B没有什么反对意见，那么逐步扩大范围，把所有用户都迁移到B上面来。一部分开始用B的用户可以理解为灰度用户。通过灰度升级可以在业务升级的初始阶段发现、调整问题。
该方法涉及的滚动升级是每次对一个或多个节点进行业务升级，然后将升级完成的节点加入生产环境，不断执行该过程，直至生产环境中的节点都完成升级。滚动升级也可以称为滚动发布。
如图2所示，该方法包括：
S101：在BE中新增DID容器。
其中，DID容器用于进行第一业务的灰度升级。可选的，在DID容器中部署PGW模 块、数据业务网关(data service gateway,DSG)模块、数据路由单元(data routing unit,DRU)模块、数据服务单元(data service unit,DSU)模块。其中，PGW模块可以用于进行业务处理，DSG模块可以用于进行消息转发，DRU模块可以用于存储路由数据，DSU模块可以用于存储用户数据
具体的，在新增的DID容器中保存第一业务的当前版本的业务数据和灰度用户数据。其中，灰度用户是用于进行灰度升级测试的用户。作为一种可选的实现方式，可以从上述BE的PGW容器和RSU容器中将第一业务的当前版本的业务数据和灰度用户数据拷贝至新增的DID容器中。作为一种示例，可以邀请使用上述业务的真实用户参加测试，将同意参加测试的真实用户作为灰度用户。作为另一种示例，可以针对上述业务设置测试用户，该测试用户用于进行业务测试，该测试用户可以由开发人员或者测试人员维护，将上述测试用户作为灰度用户。
可选的，DID容器也可以是其他能够用于进行灰度升级的虚拟机或者容器，例如PID容器，本申请实施例对此不做限定。
可选的，S101中BE可以新增一对DID容器或者一对PID容器，以避免其中一个DID容器或者其中一个PID容器发生故障时出现业务中断。
可选的，S101可以在S104之前的任一时刻执行，本申请实施例对此不作限定。
S102：BE配置灰度规则。
其中，灰度规则包括灰度用户的信息。BE部分可以根据灰度规则识别灰度用户。
可选的，本地维护终端(本地portal)配置并下发灰度规则；其中，本地portal可以是BE中的服务器或者服务器端***，可以用于提供门户服务、客户端身份验证等功能。
可选的，灰度规则可以包括一个或多个哈希值，一个哈希值可以用于标识一个灰度用户。
S103：BE向FE发送灰度规则。
FE可以根据灰度规则识别灰度用户。
在一种可能的实现方式中，BE的LB节点向FE的LB节点发送上述灰度规则。
在一种可能的实现方式中，BE通过BE和FE间的同步接口向FE发送灰度规则。
S104：BE新增的DID容器进行灰度升级。
具体的，BE导入灰度规则。BE从PGW容器和RSU容器中将第一业务的当前版本的业务数据和灰度用户数据拷贝至新增的DID容器中，在新增的DID容器中对第一业务进行升级，更新新增的DID容器中的业务数据和灰度用户数据。
S105：进行灰度用户的业务测试。
具体的，FE部署有上述第一业务的当前版本的应用(application,APP)1.0和第一业务的升级版本的APP2.0。
具体的，灰度用户通过FE的LB节点接入第一业务；FE部分的LB节点根据上述灰度规则识别出灰度用户后，将灰度用户分流到APP2.0；APP2.0进行业务处理并发送业务请求至BE部分的LB节点；BE部分的LB节点根据灰度规则识别出业务请求对应的灰度用户后，将业务请求转发至上述新增的DID容器处理；处理完成后，DID容器向BE的LB节点反馈响应消息，BE部分的LB节点向APP2.0反馈响应消息，APP2.0向FE部分的LB节点反馈响应消息；灰度用户可以根据响应消息判断升级的第一业务是否通过测试。
S106：BE进行滚动升级。
具体的，灰度测试通过之后，对BE的其他容器或者虚拟机进行滚动升级。
其中，灰度测试通过可以是所有灰度用户通过了S105的测试；或者，也可以是灰度用户中已参与S105的业务测试的用户均通过了测试，本申请实施例对此不作限定。
作为一种可能的实现方式，BE部分的滚动升级具体可以是对一个或多个PGW容器进行升级，在升级成功之后，对一个或多个RSU容器进行升级。
可选的，在滚动升级过程中，若一个或多个容器升级失败，则进行回滚。
S107：从BE删除新增的DID容器。
具体的，将DID容器中灰度用户的数据同步到灰度用户被拷贝到DID容器之前所在的RSU容器或PGW容器之后，从BE删除DID容器。
通过上述S101，S104和S106，通过较少的灰度用户进行第一业务的灰度升级和验证，提高在灰度升级阶段发现问题的可能性，降低业务升级失败而回滚的可能性，降低业务升级的成本；在灰度升级成功之后通过滚动升级减少升级的过程中同时影响的用户数量，提高业务可靠性。
同时，通过上述S102，S103和S105，FE部分和BE部分能够同步灰度规则，识别灰度用户，使灰度用户的第一业务测试能够覆盖FE部分和BE部分，实现灰度升级后端到端的测试覆盖，提高在灰度测试阶段发现问题的可能性，降低后续滚动升级阶段出现问题的可能性，降低回滚可能性，从而降低业务升级的成本。
图3是本申请实施例提供的一种业务升级方法的流程示意图。该方法用于对第一业务进行升级。如图3所示，该方法包括：
S201：在第一装置中新增第一节点。
其中，该第一装置用于存储和管理业务相关的数据，该第一节点用于灰度升级第一业务。第一装置可以是上述图2中的BE。第一节点可以是上述S101中新增的DID容器或者PID容器。具体可参考S101的内容。
S202：第一装置配置灰度规则。
其中，第一装置根据该灰度规则识别灰度用户，灰度用户用于测试第一业务。具体可参考S102的内容。
S203：第一装置向第二装置发送该灰度规则。
其中，第二装置为第一装置的前端装置。前端装置可以理解为用户通过第一装置接入业务，第二装置为第一装置提供业务所需的数据。第二装置可以是上述图2中的FE。具体可参考S103的内容。
S204：第一节点进行第一业务的灰度升级。
具体可参考S104的内容。
可选的，第一装置包括至少一个第二节点，该第二节点用于存储或者管理用户数据，第一节点进行第一业务的灰度升级之后，进行灰度用户的第一业务的测试；测试通过后，至少一个第二节点进行第一业务的滚动升级。其中，第二节点可以是上述图2中的PGW容器、RSU容器、非新增的DID容器。上述过程具体可参考S105和S106的内容。
可选的，从第一装置中删除第一节点。具体可参考S107的内容。
可选的，在第一节点进行第一业务的灰度升级之前，将灰度用户的数据拷贝至第一节点。 具体可参考S104的内容。
可选的，第一节点从第一装置中删除第一节点之前，将第一节点中灰度用户的数据同步至原节点，原节点为灰度用户的数据拷贝至第一节点前灰度用户的数据所在的节点。具体可参考S107的内容。
可选的，第一装置根据上述灰度规则识别灰度用户包括：第一装置的负载均衡(load balancing,LB)节点根据上述灰度规则识别灰度用户。具体可参考S102的内容。
可选的，第一装置为统一数据存储库(unified data repository,UDR)。具体可参考对图1中BE的介绍。
可选的，第二装置为统一数据管理网元(unified data management,UDM)；或者，第二装置为策略控制功能网元(policy control function,PCF)。具体可参考对图1中FE的介绍。
基于上述方法，可以通过较少的灰度用户进行第一业务的灰度升级和验证，提高在灰度升级阶段发现问题的可能性，降低业务升级失败而回滚的可能性，降低业务升级的成本；在灰度升级成功之后通过滚动升级减少升级的过程中同时影响的用户数量，提高业务可靠性。同时，能够在第一装置和第二装置中同步灰度规则，识别灰度用户，使灰度用户的第一业务测试能够覆盖第一装置和第二装置，实现灰度升级后端到端的测试覆盖，提高在灰度测试阶段发现问题的可能性，降低后续滚动升级阶段出现问题的可能性，降低回滚可能性，从而降低业务升级的成本。
图4是本申请实施例提供的一种业务升级方法的流程示意图。该方法用于对第一业务进行升级。如图4所示，该方法包括：
S301：第二装置从第一装置接收灰度规则。
其中，第一装置用于存储和管理业务数据，第二装置为第一装置的前端装置。第一装置可以是上述图2中的BE。第二装置可以是上述图2中的FE。
S302：第二装置根据灰度规则识别灰度用户。
其中，灰度用户用于测试灰度升级的第一业务。具体可参考S104的内容。
可选的，第二装置为灰度用户接入高版本应用(application,APP)，高版本APP从第一装置获取第一业务的数据。具体可参考S105的内容。
可选的，第二装置根据灰度规则识别灰度用户包括：第二装置的负载均衡(load balancing,LB)节点根据所述灰度规则识别灰度用户。具体可参考S103的内容。
可选的，第一装置为统一数据存储库(unified data repository,UDR)。具体可参考对图1中BE的介绍。
可选的，第二装置为统一数据管理网元(unified data management,UDM)；或者，第二装置为策略控制功能网元(policy control function,PCF)。具体可参考对图1中FE的介绍。
基于上述方法，能够在第一装置和第二装置中同步灰度规则，识别灰度用户，使灰度用户的第一业务测试能够覆盖第一装置和第二装置，实现灰度升级后端到端的测试覆盖，提高在灰度测试阶段发现问题的可能性，降低后续滚动升级阶段出现问题的可能性，降低回滚可能性，从而降低业务升级的成本。
图5所示为本申请实施例提供的通信装置500的结构示意图。该通信装置500包括一个或多个处理器501，通信线路502，以及至少一个通信接口(图5中仅是示例性的以包括通信接口503，以及一个处理器501为例进行说明)，可选的还可以包括存储器504。
处理器501可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路502用于连接不同组件。
通信接口503，可以是收发模块用于与其他设备或通信装置或通信网络，如以太网等。例如，上述收发模块可以是网卡，光纤交换装置。可选的，通信接口503也可以是位于处理器501内的收发电路，用以实现处理器的信号输入和信号输出。
存储器504可以是具有存储功能的装置。例如可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路502与处理器相连接。存储器也可以和处理器集成在一起。其中，存储器504用于存储执行本申请方案的计算机执行指令，并由处理器501来控制执行。处理器501用于执行存储器504中存储的计算机执行指令。本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器501可以包括一个或多个CPU，例如图5中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信装置500可以包括多个处理器，例如图5中的处理器501和处理器505。这些处理器中的每一个可以是一个单核(single-CPU)处理器，也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
上述的通信装置500可以是一个通用装置或者是一个专用装置。例如通信装置500可以是网络服务器、嵌入式设备或具有图5中类似结构的设备。本申请实施例不限定通信装置500的类型。
可选的，图2中的FE可以是如图5所示的通信装置。图5中的处理器501可以支持装置500执行图2中由FE完成的功能。例如，处理器501可以执行S103中根据灰度规则识别灰度用户的功能。图5中的通信接口503可以支持装置500与其他装置进行通信。例如，通信接口503可以支持装置500执行图2中S103中的通信过程。
可选的，图2中的BE可以是如图5所示的通信装置。图5中的处理器501可以支持装置500执行图2中由BE完成的功能。例如，处理器501可以执行S104中进行灰度升级的功能，处理器501还可以执行S106中进行滚动升级的功能。图5中的通信接口503可以支持装置500与其他装置进行通信。例如，通信接口503可以支持装置500执行图2中S103中的通信过程。
可选的，图2中的FE和BE可以集成在图5所示的通信装置中。图5中的处理器501可以支持装置500执行图2中由FE完成的功能，图5中的处理器505可以支持装置500执 行图2中由BE完成的功能。图5中的通信接口503可以支持装置500与其他装置进行通信。
可以理解的是，以上各个实施例中，由FE或者BE实现的方法和/或步骤，也可以由实现上述FE或者BE功能的芯片***实现。
图6所示是本申请实施例提供的一种通信装置。本申请实施例可以根据上述方法实施例中对通信装置进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的单元集成在一个处理模块中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图6所示为本申请实施例提供的通信装置600的结构示意图。该通信装置600包括处理单元601和收发单元602。
可选的，图2中的FE可以是图6所示的通信装置。图6中的处理单元601可以支持装置600执行图2中由FE完成的功能。例如，处理单元601可以执行S103中根据灰度规则识别灰度用户的功能。图6中的收发单元602可以支持装置600与其他装置进行通信。例如，收发单元602可以支持装置600执行图2中S103中的通信过程。
可选的，图2中的BE可以是图6所示的通信装置。图6中的处理单元601可以支持装置600执行图2中由BE完成的功能。例如，处理单元601可以执行S104中进行灰度升级的功能，处理单元601还可以执行S106中进行滚动升级的功能。图6中的收发单元602可以支持装置600与其他装置进行通信。例如，收发单元602可以支持装置600执行图2中S103中的通信过程。
可选的，图2中的FE和BE可以集成在图6所示的通信装置中。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。上述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。

Claims (18)

  1. 一种业务升级的方法，其特征在于，包括：
    在第一装置中新增第一节点，所述第一装置用于存储和管理业务相关的数据，所述第一节点用于灰度升级第一业务；
    所述第一装置配置灰度规则，所述第一装置根据所述灰度规则识别灰度用户，所述灰度用户用于测试所述第一业务；
    所述第一装置向第二装置发送所述灰度规则，所述第二装置为所述第一装置的前端装置；
    所述第一节点进行所述第一业务的灰度升级。
  2. 根据权利要求1所述的方法，其特征在于，
    所述第一装置包括至少一个第二节点，所述第二节点用于存储或者管理用户数据；
    所述第一节点进行所述第一业务的灰度升级之后，进行所述灰度用户的所述第一业务的测试；所述测试通过后，所述至少一个第二节点进行所述第一业务的滚动升级。
  3. 根据权利要求1或2所述的方法，其特征在于，还包括：从所述第一装置中删除所述第一节点。
  4. 根据权利要求1-3任一所述的方法，其特征在于，所述第一节点进行所述第一业务的灰度升级之前，将所述灰度用户的数据拷贝至所述第一节点。
  5. 根据权利要求4所述的方法，其特征在于，所述第一节点从所述第一装置中删除所述第一节点之前，将所述第一节点中所述灰度用户的数据同步至原节点，所述原节点为所述灰度用户的数据拷贝至所述第一节点前所述灰度用户的数据所在的节点。
  6. 根据权利要求1-5任一所述的方法，其特征在于，所述第一节点为DID容器、或者PID容器。
  7. 根据权利要求1-6任一所述的方法，其特征在于，所述第一装置根据所述灰度规则识别灰度用户包括：所述第一装置的负载均衡(load balancing,LB)节点根据所述灰度规则识别灰度用户。
  8. 根据权利要求1-7任一所述的方法，其特征在于，所述第一装置为统一数据存储库(unified data repository,UDR)。
  9. 根据权利要求1-8任一所述的方法，其特征在于，所述第二装置为统一数据管理网元(unified data management,UDM)；或者，所述第二装置为策略控制功能网元(policy control function,PCF)。
  10. 一种业务升级的方法，其特征在于，包括：
    第二装置从第一装置接收灰度规则；其中，所述第一装置用于存储和管理业务数据，所述第二装置为所述第一装置的前端装置；
    所述第二装置根据所述灰度规则识别灰度用户，所述灰度用户用于测试灰度升级的第一业务。
  11. 根据权利要求10所述的方法，其特征在于，还包括：
    所述第二装置为所述灰度用户接入高版本应用(application,APP)，所述高版本APP从所述第一装置获取所述第一业务的数据。
  12. 根据权利要求10或11所述的方法，其特征在于，所述第二装置根据所述灰度规则识别灰度用户包括：所述第二装置的负载均衡(load balancing,LB)节点根据所述灰度规则识别灰度用户。
  13. 根据权利要求10-12任一所述的方法，其特征在于，所述第一装置为统一数据存储库(unified data repository,UDR)。
  14. 根据权利要求10-13任一所述的方法，其特征在于，所述第二装置为统一数据管理网元(unified data management,UDM)；或者，所述第二装置为策略控制功能网元(policy control function,PCF)。
  15. 一种通信装置，包括处理器，其特征在于，
    所述处理器用于从存储器读取指令，运行所述指令以实现如权利要求1-9任一所述的方法。
  16. 一种通信装置，包括处理器，其特征在于，
    所述处理器用于从存储器读取指令，运行所述指令以实现如权利要求10-14任一所述的方法。
  17. 一种通信***，其特征在于，包括如权利要求15所述的通信装置和如权利要求16所述的通信装置。
  18. 一种计算机可读存储介质，包括指令，其特征在于，当所述指令在通信装置上执行时，使得所述通信装置实现如权利要求1-14任一所述的方法。
PCT/CN2020/140629 2019-12-31 2020-12-29 业务升级的方法、装置和*** WO2021136233A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20911063.4A EP4050850A4 (en) 2019-12-31 2020-12-29 SERVICE ENHANCEMENT METHOD, DEVICE AND SYSTEM
US17/852,930 US20220326940A1 (en) 2019-12-31 2022-06-29 Service Upgrade Method, Apparatus, and System

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911410720.4A CN113127023B (zh) 2019-12-31 2019-12-31 业务升级的方法、装置和***
CN201911410720.4 2019-12-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/852,930 Continuation US20220326940A1 (en) 2019-12-31 2022-06-29 Service Upgrade Method, Apparatus, and System

Publications (1)

Publication Number Publication Date
WO2021136233A1 true WO2021136233A1 (zh) 2021-07-08

Family

ID=76687114

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/140629 WO2021136233A1 (zh) 2019-12-31 2020-12-29 业务升级的方法、装置和***

Country Status (4)

Country Link
US (1) US20220326940A1 (zh)
EP (1) EP4050850A4 (zh)
CN (1) CN113127023B (zh)
WO (1) WO2021136233A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117170718A (zh) * 2023-11-02 2023-12-05 绿城科技产业服务集团有限公司 基于微服务架构的灰度发布方法、装置及电子设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115499317B (zh) * 2022-11-15 2023-04-07 阿里云计算有限公司 灰度验证方法、电子设备和可读存储介质
CN116578335B (zh) * 2023-07-13 2023-10-03 建信金融科技有限责任公司 灰度发布***、方法、设备、介质及产品

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106789202A (zh) * 2016-12-08 2017-05-31 努比亚技术有限公司 业务管理装置及方法
US20180219971A1 (en) * 2015-09-25 2018-08-02 Huawei Technologies Co., Ltd. Service Processing Method and Device
CN108595207A (zh) * 2018-03-23 2018-09-28 深圳乐信软件技术有限公司 一种灰度发布方法、规则引擎、***、终端和存储介质
CN109474522A (zh) * 2017-09-07 2019-03-15 华为技术有限公司 业务路由的方法、装置及存储介质
CN110365502A (zh) * 2018-03-26 2019-10-22 华为技术有限公司 一种服务升级管理的方法、装置及存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1776634A1 (en) * 2004-08-14 2007-04-25 Telefonaktiebolaget LM Ericsson (publ) Method for sofware program synchronization
US9886258B2 (en) * 2014-08-12 2018-02-06 Xiaomi Inc. Method and device for grayscale-upgrading
JP2017004120A (ja) * 2015-06-05 2017-01-05 キヤノン株式会社 システム、サーバーシステム、方法、およびプログラム
CN105893084B (zh) * 2016-03-29 2019-04-30 青岛海信移动通信技术股份有限公司 版本升级方法及终端设备
CN108319468B (zh) * 2017-01-16 2021-10-15 北京京东尚科信息技术有限公司 灰度发布方法、装置、***及电子设备
US10581891B1 (en) * 2017-11-27 2020-03-03 Lacework Inc. Using graph-based models to identify datacenter anomalies
CN110162382B (zh) * 2019-04-09 2023-12-15 平安科技（深圳）有限公司 基于容器的灰度发布方法、装置、计算机设备及存储介质
US11573780B2 (en) * 2019-08-16 2023-02-07 Red Hat, Inc. Automated generation of status chains for software updates

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180219971A1 (en) * 2015-09-25 2018-08-02 Huawei Technologies Co., Ltd. Service Processing Method and Device
CN106789202A (zh) * 2016-12-08 2017-05-31 努比亚技术有限公司 业务管理装置及方法
CN109474522A (zh) * 2017-09-07 2019-03-15 华为技术有限公司 业务路由的方法、装置及存储介质
CN108595207A (zh) * 2018-03-23 2018-09-28 深圳乐信软件技术有限公司 一种灰度发布方法、规则引擎、***、终端和存储介质
CN110365502A (zh) * 2018-03-26 2019-10-22 华为技术有限公司 一种服务升级管理的方法、装置及存储介质

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117170718A (zh) * 2023-11-02 2023-12-05 绿城科技产业服务集团有限公司 基于微服务架构的灰度发布方法、装置及电子设备
CN117170718B (zh) * 2023-11-02 2024-02-02 绿城科技产业服务集团有限公司 基于微服务架构的灰度发布方法、装置及电子设备

Also Published As

Publication number Publication date
CN113127023A (zh) 2021-07-16
CN113127023B (zh) 2024-04-09
EP4050850A4 (en) 2022-12-28
US20220326940A1 (en) 2022-10-13
EP4050850A1 (en) 2022-08-31

Similar Documents

Publication Publication Date Title
WO2021136233A1 (zh) 业务升级的方法、装置和***
CN110365502B (zh) 一种服务升级管理的方法、装置及存储介质
US9893940B1 (en) Topologically aware network device configuration
US11263612B2 (en) Systems and methods for point of sale data synchronization
WO2016155394A1 (zh) 一种虚拟网络功能间链路建立方法及装置
WO2019184164A1 (zh) 自动部署Kubernetes从节点的方法、装置、终端设备及可读存储介质
WO2017066931A1 (zh) 网络功能虚拟化架构中证书的管理方法及装置
CN106911648B (zh) 一种环境隔离方法及设备
WO2016058412A1 (zh) 一种实现虚拟网络功能部署的方法、装置及存储介质
WO2022134797A1 (zh) 一种数据分片存储方法、装置、计算机设备和存储介质
CN109104368B (zh) 一种请求连接方法、装置、服务器及计算机可读存储介质
US8600960B2 (en) Processing proposed changes to data
US20220360494A1 (en) Assisted and context-driven network changes
WO2020104988A1 (en) Fast session restoration for latency sensitive middleboxes
US20220394785A1 (en) System and Method of Managing PNF Connectivity in a Network Slice Instance
CN110855488A (zh) 一种虚拟机接入方法及装置
US11030220B2 (en) Global table management operations for multi-region replicated tables
CN112667601A (zh) 区块链标识的管理方法、终端设备及计算机可读存储介质
CN113760461B (zh) 一种版本升级方法及计算机可读存储介质
CN111464646A (zh) 信息处理方法、装置、电子设备和介质
CN103139243A (zh) 一种基于星型分布式***的文件同步方法
CN109804365A (zh) 弹性地理数据库复制方法
CN106254411A (zh) 用于提供服务的***、服务器***及方法
CN104104701A (zh) 在线服务的配置更新的方法和***
CN114650281A (zh) 基于复杂网络的文件下载方法、装置、设备及存储介质

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020911063

Country of ref document: EP

Effective date: 20220523

NENP Non-entry into the national phase

Ref country code: DE