Service slicing method, apparatus, device, storage medium, and program product

Abstract

The application provides a service slicing method, device, equipment, storage medium and program product, wherein the method comprises: obtaining a request message of a target service; analyzing the request message to obtain slicing information configured for the target service; determining a processing system in which the target service is deployed based on the slicing information; and directing the request message to the processing system. The application obtains the slicing information of the target service by analyzing the request message, obtains the slicing state of the target service, and then confirms the processing system in which the target service is deployed. When the service slicing method of the application is applied to a DSMP scenario, the request message of the target service can be directed to the DSMP system to which the target service currently belongs according to the slicing state of the target service, which can ensure that the DSMP system to which the target service is directed is consistent with the DSMP system to which the target service belongs, and if the target service needs to be authenticated, the authentication process can be normally started, thereby guaranteeing the service experience of the user.

Description

Technical Field

[0001] This application belongs to the field of mobile communication technology, specifically relating to a service cutover method, apparatus, device, storage medium, and program product. Background Technology

[0002] In the existing mobile communication network architecture, the Data Service Management Platform (DSMP) system is deployed independently in each province. With the continuous development and changes in communication networks, and the advent of the big data and cloud computing era, a new DSMP system has been deployed centrally based on cloud computing resource pools. The old DSMP systems in each province need to migrate their data services to the new DSMP system; this process is also known as cutover. To ensure a smooth transition of data services, reduce cutover risks, and protect data security, the old and new systems will run in parallel during the cutover process to ensure that the user's service experience is not affected.

[0003] Internet service providers (SPs) need to route service requests to the corresponding DSMP system through surrounding network elements, where the DSMP system authenticates the SP's services. During the cutover, SP services may involve both old and new DSMP systems. However, existing network elements can only route requests to a pre-defined DSMP system and cannot verify or determine the DSMP system to which the SP service currently belongs. This leads to a discrepancy between the DSMP system to which the SP service is routed and its original DSMP system, preventing the authentication process from starting. This reduces the user experience and increases the difficulty of data service cutover. Summary of the Invention

[0004] This application proposes a service cutover method, apparatus, equipment, storage medium, and program product, which can alleviate the technical problem of inconsistency between the DSMP system to which SP services are directed and its parent DSMP system.

[0005] The first aspect of this application proposes a service cutover method, including:

[0006] Obtain the request message for the target service;

[0007] The request message is parsed to obtain the cutover information configured for the target service;

[0008] Based on the cutover information, the processing system deployed with the target service is identified;

[0009] The request message is directed to the processing system.

[0010] In one or more optional embodiments, parsing the request message to obtain the cutover information configured for the target service includes:

[0011] Based on the request message, obtain the service configuration information of the target service;

[0012] The cutover information is extracted from the service configuration information.

[0013] In one or more alternative embodiments, determining the processing system on which the target service is deployed based on the cutover information includes:

[0014] If the cutover status included in the cutover information is "cutover in progress", then obtain the joint debugging test data from the cutover information; the joint debugging test data is used to characterize the need to prioritize the cutover of the target service to the post-cutover processing system;

[0015] The joint debugging test data is directed to the cut-out processing system;

[0016] After confirming that the cutover status of the target service has been updated to "cutover complete", the processing system that deploys the target service is determined to be the cutover processing system.

[0017] In one or more alternative embodiments, directing the request message to the processing system includes:

[0018] Obtain the routing address of the processing system;

[0019] Update the destination address in the request message to the routing address;

[0020] Send the updated request message.

[0021] In one or more optional embodiments, before parsing the request message to obtain the cutover information configured for the target service, the method further includes:

[0022] Based on the request message, it is confirmed that the target service belongs to the authentication type; the authentication type is the service that requires an authentication process.

[0023] In one or more optional embodiments, based on the request message, confirming that the target service belongs to the authentication type includes:

[0024] Based on the request message, the service type or interface type of the target service is obtained; the interface type is the interface type of the network element that transmits the request message.

[0025] If the business type is a preset business type, the target business is confirmed to be an authentication business; or, if the interface type is a preset interface type, the target business is confirmed to be an authentication business.

[0026] An embodiment of the second aspect of this application also provides a service cutover apparatus, comprising:

[0027] The acquisition module is used to acquire the request message of the target business.

[0028] The parsing module is used to parse the request message to obtain the cutover information configured for the target service;

[0029] The system confirmation module is used to determine, based on the cutover information, the processing system on which the target service is deployed;

[0030] A routing module is used to direct the request message to the processing system.

[0031] An embodiment of the third aspect of this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method described in the first aspect above.

[0032] An embodiment of the fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, the program being executed by a processor to implement the method described in the first aspect above.

[0033] An embodiment of the fifth aspect of this application provides a computer program product including computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code, wherein when the computer-readable code is run in a processor of an electronic device, the processor in the electronic device performs the method described in the first aspect above.

[0034] The technical solutions provided in this application embodiment have at least the following technical effects or advantages:

[0035] This application embodiment obtains the cutover information of the target service by parsing request messages, thus determining the cutover status of the target service, such as cutover completed, not cutover completed, or cutover in progress. Based on the different cutover statuses of the target service, the processing system for deploying the target service is then identified. Applying the service cutover method of this application embodiment to a DSMP scenario, the request messages of the target service can be redirected to the DSMP system to which the target service currently belongs, i.e., the DSMP system where the target service is deployed, based on the cutover status of the target service. This ensures that the DSMP system to which the target service is redirected is consistent with its current DSMP system. When the target service requires authentication, the authentication process can be initiated normally, ensuring a good user service experience.

[0036] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0037] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings.

[0038] In the attached diagram:

[0039] Figure 1 This invention provides a schematic flowchart of a service cutover method according to an embodiment of the present application.

[0040] Figure 2 This application shows a network diagram of a new and old DSMP system provided in one embodiment;

[0041] Figure 3 This illustration shows another schematic flowchart of the service cutover method provided in an embodiment of this application;

[0042] Figure 4 A schematic diagram of the structure of a service cutover device provided in an embodiment of this application is shown;

[0043] Figure 5 This illustration shows a schematic diagram of the structure of an electronic device according to an embodiment of this application;

[0044] Figure 6 A schematic diagram of a storage medium provided in one embodiment of this application is shown. Detailed Implementation

[0045] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely represents selected embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0046] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0047] In this document, the term "and / or" merely describes a relationship, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0048] In the existing mobile communication network architecture, the Data Service Management Platform (DSMP) system is deployed independently by province. Local SP services are authenticated by the DSMP system of their respective province, while all SP services across the network require forwarding to the DSMP system of the user's home province for authentication. However, with the continuous development and changes in communication networks, and the advent of the big data and cloud computing era, mobile communication networks have deployed new DSMP systems in a centralized manner based on cloud computing resource pools. The old DSMP systems in each province need to migrate data services to the new DSMP system; this process is also known as cutover. To ensure a smooth transition of data services, reduce cutover risks, and protect data security, the old and new systems will run in parallel during the cutover process to ensure that the user's service experience is not affected.

[0049] Service Provider (SP) services require routing requests to the corresponding DSMP system via surrounding network elements, where the DSMP system authenticates the SP service. During cutover, SP services may involve both old and new DSMP systems. However, existing network elements can only route requests to a pre-defined DSMP system and cannot verify or determine the current DSMP system to which the SP service belongs. Since the DSMP system to which the SP service belongs changes during the cutover, the DSMP system to which the SP service is redirected may differ from its actual DSMP system, leading to authentication failure, reduced user experience, and increased cutover difficulty. Modifying surrounding network elements to support multiple routing paths would be a large-scale and costly undertaking, and would also negatively impact these elements.

[0050] Based on the above research, this application provides a service cutover method. By parsing request messages, the cutover information of the target service can be obtained, and the cutover status of the target service can be obtained. The cutover status includes cutover completed, not cutover completed, and cutover in progress. According to the different cutover status of the target service, the processing system deployed by the target service can be identified, that is, the DSMP system to which the target service currently belongs. This ensures that the DSMP system to which the target service is directed is consistent with its parent DSMP system, which is conducive to completing the authentication of the target service and ensuring the user's service experience.

[0051] To facilitate understanding of this embodiment, a service cutover method disclosed in this application will first be described in detail. The execution subject of the service cutover method provided in this application embodiment is generally an electronic device with a certain computing capability. This electronic device may include, for example, a terminal device, a server, or other processing devices. The terminal device may be a user equipment (UE), mobile device, user terminal, terminal, cellular phone, cordless phone, personal digital assistant (PDA), handheld device, computing device, in-vehicle device, wearable device, etc. In some possible implementations, this service cutover method can be implemented by the processor calling computer-readable instructions stored in memory.

[0052] In the scenario where the service cutover method of this application embodiment is applied to a DSMP system, the execution subject of this application embodiment may be a device with a new DSMP system deployed, a device with an old DSMP system deployed, or a device other than a new DSMP system and an old DSMP system deployed.

[0053] In the case where the implementing entity is a device deployed with a centralized new DSMP system, see [link to relevant documentation]. Figure 2 The diagram shown illustrates the network topology of the old and new DSMP systems provided in this embodiment. The new DSMP system integrates a traffic offloading access module, which is used to acquire, parse, and redirect request packets. For example, when the cutover information parsed by the traffic offloading access module indicates that the cutover has not occurred, the request packet for the target service can be redirected to the old DSMP system in province A based on the province of origin (e.g., province A) of the user who subscribed to the target service. When the cutover information parsed by the traffic offloading access module indicates that the cutover has occurred, the request packet for the target service is redirected to the new DSMP system.

[0054] Figure 2The peripheral network elements shown, such as the converged gateway, MMS gateway, Business Operation Support System (BOSS), User Identity Module (SIMS), and SP, are used to implement different functions. For example, the converged gateway implements SMS uplink and downlink forwarding functions, the MMS gateway implements MMS uplink and downlink forwarding functions, the BOSS is responsible for synchronizing the subscription relationships and user information status changes between provinces and between the old and new DSMP systems, and the SIMS is responsible for sending SP request messages to the new DSMP system. The SP is an Internet service provider.

[0055] See Figure 1 The diagram shows a flowchart of a service cutover method provided in an embodiment of this application. The method includes steps S1 to S4:

[0056] S1: Obtain the request message for the target service.

[0057] The target service is one of the SP's services, such as ringback tones, SMS, or MMS. The request message can carry the user's subscription request, the service configuration information of the target service, etc.

[0058] S2: Parse the request message to obtain the cutover information configured for the target service.

[0059] Specifically, after the cutover process begins, administrators can configure cutover information for SP services based on the cutover status; alternatively, the executing entity can configure cutover information for SP services. This cutover information characterizes the cutover status of the SP service: completed, not completed, or in progress. For example, "completed" indicates that all relevant data for the target service has been transferred to the new DSMP system, meaning the processing system deploying the target service is the new DSMP system; "not completed" indicates that relevant data for the target service is still located in the old DSMP systems of various provinces, meaning the processing system deploying the target service is the old DSMP system; and "in progress" indicates that a portion of the relevant data for the target service has been transferred to the new DSMP system, at which point the processing system deploying the target service is the new DSMP system.

[0060] The parsing process specifically includes the following steps:

[0061] Based on the request message, the service configuration information of the target service is obtained; cutover information is extracted from the service configuration information. The service configuration information may include cutover information, service code, province identifier, etc. Preferably, in this embodiment, the cutover information may include a cutover identifier, which is used to characterize the cutover status of the target service.

[0062] S3: Based on the cutover information, identify the processing system deployed with the target business.

[0063] In cases where the cutover status in the cutover information is "cutover completed", the processing system for the target service is the processing system after the cutover, such as a centralized new DSMP system.

[0064] If the cutover status included in the cutover information is "not cutover", the processing system of the target service is the processing system before the cutover, such as the old DSMP system of each province.

[0065] When the cutover information includes a cutover status of "Cutover in Progress," the specific steps include:

[0066] S3.1 Obtain joint debugging test data from the cutover information.

[0067] Specifically, the joint debugging test data can be configured together with the cutover information. The joint debugging test data is associated with the cutover information. When the cutover status is not cutover or cutover completed, the joint debugging test data is empty. Only when the cutover status is in progress will the cutover information include joint debugging test data with actual values. The joint debugging test data is used to characterize the target service that needs to be cut over to the post-cutover processing system, such as a centralized new DSMP system.

[0068] S3.2 directs the joint debugging test data to the post-cutover processing system; the post-cutover processing system then prioritizes the cutover of the target services.

[0069] S3.3 After confirming that the cutover status of the target service has been updated from "cutover in progress" to "cutover completed", determine that the processing system for deploying the target service is the post-cutover processing system, such as a centralized new DSMP system.

[0070] This application embodiment, by setting up joint debugging test data, can prioritize the cutover of target services, shorten the cutover time, and respond to and process the target services after all the target services have been cutoverdone, such as authenticating the target services, which helps to improve authentication efficiency and user service experience.

[0071] S4: Direct the request message to the processing system. Specifically, directing the request message to the processing system includes the following steps:

[0072] The process involves obtaining the routing address of the processing system; updating the destination address in the request message to the routing address; and sending the updated request message. Specifically, when the routing address and destination address are the same, the routing address is the destination address; when they are different, the routing address is the new destination address. After the request message is directed to the processing system, the system can respond to and process the target service. For example, applying the service cutover method of this embodiment to a DSMP scenario allows the corresponding DSMP system to authenticate the target service, ensuring the normal initiation of the authentication process and guaranteeing the user's service experience.

[0073] In a preferred embodiment of this application, the following steps may be included before S2:

[0074] Based on the request message, it was confirmed that the target service belongs to the authentication category.

[0075] SP services include authentication-based services and non-authentication-based services. Authentication-based services are those that require an authentication process, such as ringback tones and SMS services. The SP service can only take effect after the authentication is successful. Non-authentication-based services, such as SIMS-side service classification and BOSS-side user information synchronization, need to be routed to both the old DSMP in each province and the centralized new DSMP for processing simultaneously, without needing to determine the cutover status.

[0076] Specific confirmation methods may include:

[0077] Method 1: Based on the request message, obtain the service type of the target service; if the service type is a preset service type, confirm that the target service belongs to the authentication type. The service type can include both authentication and non-authentication services, and can be obtained from the service configuration information. The preset service type is authentication.

[0078] Method 2: Obtain the interface type based on the request message; if the interface type is a preset interface type, confirm that the target service belongs to the authentication category. The interface type refers to the interface type of the network element transmitting the request message, which can specifically include authentication and information synchronization types. For example, the BOSS network element is used to synchronize user, SP services, and subscription relationship information; its interface type is information synchronization. Similarly, the authentication and pricing interface is used to transmit authentication results for SP information, service information, user information, and subscription relationship information; its interface type is authentication. Therefore, the interface type can be used to determine whether the target service transmitted by the network element belongs to the authentication category. Specifically, the network element transmitting the target service can be obtained from the request message, and the corresponding interface type can be obtained based on the network element.

[0079] By determining whether the target service is an authentication-type service or a non-authentication-type service, the target service can be directed to different processing paths. Accurate classification and response processing for different types of services helps reduce the impact of service cutover on surrounding network elements and reduces risks and potential problems during the cutover process.

[0080] See Figure 3 The diagram shows a flowchart of a service cutover method provided in an embodiment of this application. The method includes steps S1 to S5:

[0081] S1: Obtain the request message for the target service.

[0082] The target service is one of the SP services, and the request message includes information such as the subscription request and service process. After the user subscribes to the target service, the request message is received through transmissions of surrounding network elements.

[0083] S2: Based on the request message, confirm that the target service belongs to the authentication type.

[0084] SP services include authentication-based services and non-authentication-based services. Authentication-based services are those that require an authentication process, such as ringback tones and SMS services. The SP service can only take effect after the authentication is successful. Non-authentication-based services, such as SIMS-side service classification and BOSS-side user information synchronization, need to be routed to both the old DSMP in each province and the centralized new DSMP for processing simultaneously, without needing to determine the cutover status.

[0085] Specific confirmation methods may include:

[0086] Method 1: Based on the request message, obtain the service type of the target service; if the service type is a preset service type, confirm that the target service belongs to the authentication type. The service type can include both authentication and non-authentication services, and can be obtained from the service configuration information. The preset service type is authentication.

[0087] Method 2: Obtain the interface type based on the request message; if the interface type is a preset interface type, confirm that the target service belongs to the authentication category. The interface type refers to the interface type of the network element transmitting the request message, which can specifically include authentication and information synchronization types. For example, the BOSS network element is used to synchronize user, SP services, and subscription relationship information; its interface type is information synchronization. Similarly, the authentication and pricing interface is used to transmit authentication results information for SP information, service information, user information, and subscription relationship information; its interface type is authentication. Therefore, the interface type can be used to determine whether the target service transmitted by the network element belongs to the authentication category. Specifically, the network element transmitting the target service can be obtained from the request message, and the corresponding interface type can be obtained based on the network element.

[0088] S3: Parse the request message to obtain the cutover information configured for the target service.

[0089] The specific analysis process is as follows:

[0090] Based on the request message, obtain the service configuration information of the target service; extract cutover information from the service configuration information. The service configuration information may include cutover information, service code, province identifier, etc. The cutover information is used to characterize the cutover status of the target service, such as cutover completed, not cutover completed, or cutover in progress.

[0091] S4: Based on the cutover information, identify the processing system deployed with the target business.

[0092] In cases where the cutover status in the cutover information is "cutover completed", the processing system for the target service is the post-cutover processing system, i.e., the centralized new DSMP system.

[0093] If the cutover status included in the cutover information is "not cutover", the processing system for the target service is the processing system before the cutover, i.e., the old DSMP system of each province.

[0094] When the cutover information includes a cutover status of "Cutover in Progress," the specific steps include:

[0095] S4.1 Obtain joint debugging test data from the cutover information.

[0096] Specifically, the joint debugging test data is associated with the cutover information. Only when the cutover status is "cutover in progress" will the cutover information include the joint debugging test data. The joint debugging test data is used to characterize the need to prioritize the cutover of the target service to the post-cutover processing system, i.e., the centralized new DSMP system.

[0097] S4.2 directs the joint debugging test data to the post-cutover processing system, prioritizing the cutover of the target service.

[0098] S4.3 After confirming that the cutover status of the target service has been updated from "cutover in progress" to "cutover completed", the processing system for deploying the target service is determined to be the post-cutover processing system, i.e., the centralized new DSMP system.

[0099] S5: The request message is directed to the processing system, which then authenticates the target service.

[0100] Specifically, obtain the routing address of the processing system; update the destination address in the request message to the routing address; and send the updated request message.

[0101] The offloading access module can direct the target service to the current processing system based on the cutover status of the target service, without requiring modifications to surrounding network elements. This reduces the impact on surrounding network elements and helps improve cutover efficiency as well as the stability and flexibility of the old and new DSMP systems during service cutover.

[0102] The service cutover method provided in this application embodiment takes MMS service as the target service and the offloading access module as the execution subject as an example. The offloading access module is integrated into the new DSMP system, and specifically includes the following steps:

[0103] S1: Obtain MMS service request messages through surrounding network elements.

[0104] Specifically, after a user sends a subscription request for MMS service, surrounding network elements send the request message to the traffic distribution access module. Preferably, in this embodiment, the MMS service process can also be acquired simultaneously. This process includes relevant information about the MMS subscription, used to characterize the user's subscription progress.

[0105] S2: Based on the request message, confirm that the MMS service belongs to the authentication category. The specific confirmation process can be as follows:

[0106] Based on the request message, obtain the service configuration information for the MMS service;

[0107] Based on the service configuration information, obtain the service type of the MMS service;

[0108] If the service type is authentication-related, confirm that the MMS service belongs to the authentication-related service and execute S3.

[0109] Since MMS service is an authentication service, it can perform S3 operations. If the MMS service is a non-authentication service, there is no need to determine the cutover status. The MMS service request message is directly directed to both the new DSMP system and the old DSMP system, and the new and old DSMP systems process and respond together.

[0110] S3: Parse the obtained request message to obtain the cutover information configured for the MMS service.

[0111] Specifically, the cutover information includes a cutover identifier, which indicates the cutover status of the MMS service. After the cutover process begins, the traffic distribution module identifies the SP services based on the cutover identifier. For example, the cutover identifier for SP services already cut to the new DSMP system is set to "Cutover Completed," the cutover identifier for SP services currently being cut to the new DSMP system is set to "Cutover in Progress," and the cutover identifier for SP services not yet cut to the new DSMP system is set to null. Based on the cutover identifier field, the module determines whether each SP service is cut over and automatically handles different paths, enabling smooth batch cutover of SP services. This reduces the involvement of maintenance personnel, improves the efficiency of batch service cutover, and reduces risks and potential problems during the cutover process.

[0112] S4: Based on the cutover information, identify the DSMP system deployed with MMS services. Details are as follows:

[0113] Scenario 1: The cutover indicator shows that the cutover has been completed;

[0114] The traffic offloading module directs the MMS service request messages and service processes to the new DSMP system, which then processes and responds to them.

[0115] Scenario 2: The cutover indicator is "not cutover";

[0116] The offloading access module directs the MMS service request messages and service processes to the old DSMP systems in each province, where the old DSMP systems process and respond, and the surrounding network elements return the response results.

[0117] Scenario 2: Cutover is in progress;

[0118] When the cutover indicator is "underway", the traffic offloading access module sets up joint debugging test data for the MMS service and directs the joint debugging test data to the new DSMP system. The new DSMP system prioritizes the processing of the joint debugging test data to improve the cutover efficiency of the MMS service and ensure the user's service experience.

[0119] After the cutover flag for the MMS service is changed from "under cutover" to "already cutover", the traffic offloading access module will redirect the MMS service request messages and service processes to the new DSMP system, which will then process and respond to them.

[0120] After setting up the traffic splitting access module, it is possible to support the parallel operation of the new DSMP system and the old DSMP system. During the entire service cutover process, service requests from surrounding network elements will be guided through the traffic splitting access module. The traffic splitting access module automatically obtains the request packets and service processes of surrounding network elements, and modifies the target address of the request packets according to the cutover status of SP services. Then, it guides the modified request packets to the actual DSMP system for processing. This solves the problem that surrounding network elements cannot route request packets to the corresponding DSMP system according to the service type or cutover status of SP services. It is beneficial to solve the network-wide SP service authentication problem caused during the service cutover, effectively reduce the impact on surrounding network elements, and improve the stability and flexibility of the system during the service cutover.

[0121] This application also provides a service cutover apparatus for performing the service cutover method provided in any of the above embodiments, such as... Figure 4 As shown, the device includes:

[0122] The acquisition module 101 is used to acquire the request message of the target business.

[0123] The parsing module 102 is used to parse the request message to obtain the cutover information configured for the target service;

[0124] The system confirmation module 103 is used to determine, based on the cutover information, the processing system on which the target service is deployed;

[0125] The guiding module 104 is used to guide the request message to the processing system.

[0126] In one or more embodiments, the parsing module 102 is used to:

[0127] Based on the request message, obtain the service configuration information of the target service;

[0128] The cutover information is extracted from the service configuration information.

[0129] In one or more embodiments, the system verification module 103 is used to:

[0130] If the cutover status included in the cutover information is "cutover in progress", then obtain the joint debugging test data from the cutover information; the joint debugging test data is used to characterize the need to prioritize the cutover of the target service to the post-cutover processing system;

[0131] The joint debugging test data is directed to the cut-out processing system;

[0132] After confirming that the cutover status of the target service has been updated to "cutover complete", the processing system that deploys the target service is determined to be the cutover processing system.

[0133] In one or more embodiments, the guide module 104 is used for:

[0134] Obtain the routing address of the processing system;

[0135] Update the destination address in the request message to the routing address;

[0136] Send the updated request message.

[0137] The service cutover device is further configured to: before parsing the request message to obtain the cutover information configured for the target service, confirm, based on the request message, that the target service belongs to an authentication service; the authentication service is a service that requires an authentication process.

[0138] In one or more embodiments, confirming that the target service belongs to the authentication type includes:

[0139] Based on the request message, the service type or interface type of the target service is obtained; the interface type is the interface type of the network element that transmits the request message.

[0140] If the business type is a preset business type, the target business is confirmed to be an authentication business; or, if the interface type is a preset interface type, the target business is confirmed to be an authentication business.

[0141] The service cutover device and the service cutover method provided in this application are based on the same inventive concept and have the same beneficial effects as the methods they adopt, operate or implement.

[0142] This application also provides an electronic device for performing the above-described service cutover method. Please refer to... Figure 5 It illustrates a schematic diagram of an electronic device provided by some embodiments of this application. For example... Figure 5As shown, the electronic device 8 includes: a processor 800, a memory 801, a bus 802, and a communication interface 803. The processor 800, the communication interface 803, and the memory 801 are connected via the bus 802. The memory 801 stores a computer program that can run on the processor 800. When the processor 800 runs the computer program, it executes the service cutover method provided in any of the foregoing embodiments of this application.

[0143] The memory 801 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this device network element and at least one other network element is achieved through at least one communication interface 803 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc.

[0144] Bus 802 can be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The memory 801 is used to store programs. After receiving an execution instruction, the processor 800 executes the program. The identification method disclosed in any of the foregoing embodiments of this application can be applied to the processor 800, or implemented by the processor 800.

[0145] The processor 800 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of the processor 800 or by instructions in software form. The processor 800 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an off-the-shelf programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory 801. Processor 800 reads the information in memory 801 and, in conjunction with its hardware, completes the steps of the above method.

[0146] The electronic device provided in this application embodiment and the service cutover method provided in this application embodiment are based on the same inventive concept and have the same beneficial effects as the methods they adopt, operate or implement.

[0147] This application also provides a computer-readable storage medium corresponding to the service cutover method provided in the foregoing embodiments. Please refer to... Figure 6 The computer-readable storage medium shown is an optical disc 30, on which a computer program (i.e., a program product) is stored. When the computer program is run by a processor, it executes the service cutover method provided in any of the foregoing embodiments.

[0148] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical and magnetic storage media, which will not be elaborated here.

[0149] The computer-readable storage medium provided in the above embodiments of this application and the service cutover method provided in the embodiments of this application are based on the same inventive concept and have the same beneficial effects as the methods adopted, run or implemented by the applications stored therein.

[0150] This application also provides a computer program product that carries program code. The instructions included in the program code can be used to execute the steps of the service cutover method described in the above method embodiments. For details, please refer to the above method embodiments, which will not be repeated here.

[0151] The aforementioned computer program product can be implemented through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied in a computer storage medium; in another optional embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0152] It should be noted that numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of this application may be practiced without these specific details. In some instances, well-known structures and techniques have not been shown in detail so as not to obscure the understanding of this specification.

[0153] Similarly, it should be understood that, for the sake of brevity and to aid in understanding one or more of the various inventive aspects, in the above description of exemplary embodiments of this application, various features of this application are sometimes grouped together in a single embodiment, figure, or description thereof. However, this disclosure should not be construed as reflecting a schematic diagram in which the claimed application requires more features than expressly recited in each claim. Rather, as reflected in the following claims, inventive aspects lie in fewer than all features of a single foregoing disclosed embodiment. Therefore, the claims following the detailed description are hereby expressly incorporated into that detailed description, wherein each claim itself is a separate embodiment of this application.

[0154] Furthermore, those skilled in the art will understand that although some embodiments described herein include certain features but not others included in other embodiments, combinations of features from different embodiments are intended to be within the scope of this application and form different embodiments. For example, in the following claims, any of the claimed embodiments can be used in any combination.

[0155] The above description is merely a preferred embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A service cutover method, characterized in that, Applied to devices with a new Data Service Management Platform (DSMP) or devices with an older DSMP, wherein the devices with the new DSMP or the devices with the older DSMP integrate a traffic offloading access module, including: Obtain the request message for the target service; The request message is parsed to obtain the cutover information configured for the target service; Based on the cutover information, the processing system deployed with the target service is determined, including: If the cutover status included in the cutover information is "cutover in progress", then obtain the joint debugging test data from the cutover information; the joint debugging test data is used to characterize the need to prioritize the cutover of the target service to the post-cutover processing system; the joint debugging test data is directed to the post-cutover processing system, and the post-cutover processing system prioritizes the cutover of the target service; After confirming that the cutover status of the target service has been updated to "cutover complete", the processing system that deploys the target service is determined to be the cutover processing system. The request message is directed to the processing system.

2. The service cutover method according to claim 1, characterized in that, The request message is parsed to obtain the cutover information configured for the target service, including: Based on the request message, obtain the service configuration information of the target service; The cutover information is extracted from the service configuration information.

3. The service cutover method according to claim 1, characterized in that, Directing the request message to the processing system includes: Obtain the routing address of the processing system; Update the destination address in the request message to the routing address; Send the updated request message.

4. The service cutover method according to claim 1, characterized in that, Before parsing the request message to obtain the cutover information configured for the target service, the process also includes: Based on the request message, it is confirmed that the target service belongs to the authentication type; the authentication type is the service that requires an authentication process.

5. The service cutover method according to claim 4, characterized in that, Based on the request message, it is confirmed that the target service belongs to the authentication type, including: Based on the request message, the service type or interface type of the target service is obtained; the interface type is the interface type of the network element that transmits the request message. If the business type is a preset business type, the target business is confirmed to be an authentication business; or, if the interface type is a preset interface type, the target business is confirmed to be an authentication business.

6. A service cutover device, characterized in that, Applied to devices with a new Data Service Management Platform (DSMP) or devices with an older DSMP, wherein the devices with the new DSMP or the devices with the older DSMP integrate a traffic offloading access module, including: The acquisition module is used to acquire the request message of the target business. The parsing module is used to parse the request message to obtain the cutover information configured for the target service; The system confirmation module is used to determine, based on the cutover information, the processing system on which the target service is deployed; A routing module is used to direct the request message to the processing system; The system confirmation module is also used for: If the cutover status included in the cutover information is "cutover in progress", then obtain the joint debugging test data from the cutover information; the joint debugging test data is used to characterize the need to prioritize the cutover of the target service to the post-cutover processing system; the joint debugging test data is directed to the post-cutover processing system, and the post-cutover processing system prioritizes the cutover of the target service; After confirming that the cutover status of the target service has been updated to "cutover complete", the processing system that deploys the target service is determined to be the cutover processing system.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, The processor executes the computer program to implement the method as described in any one of claims 1-5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, The computer program is executed by a processor to implement the method as described in any one of claims 1-5.

9. A computer program product, characterized in that, Includes computer-readable code, or a non-volatile computer-readable storage medium carrying computer-readable code, wherein when the computer-readable code is run in a processor of an electronic device, the processor in the electronic device performs the method as described in any one of claims 1-5.

Images