Network slice reselection method and device, electronic device, and storage medium

Abstract

The present disclosure provides a network slice reselection method, the method comprising: receiving a message sent by a network side for a currently selected network slice, and reselecting a network slice; wherein the reason carried by the message is insufficient resources. The present disclosure also provides a network slice reselection device, an electronic device, and a computer-readable storage medium.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of wireless communications, and in particular to a network slice reselection method and apparatus, an electronic device, and a computer-readable storage medium. Background Art

[0002] 2G / 3G / 4G networks only meet a single business demand - phone calls or Internet access, and cannot meet the new business demands brought about by the explosive growth of data services.

[0003] 5G networks are oriented towards multiple connections and diversified services, and need to be able to be flexibly deployed like building blocks to facilitate the rapid launch or offline of new services and meet people's growing demand for data services. The industry generally believes that network slicing can realize 5G multi-scenario and diversified services, and is indispensable among many 5G technologies.

[0004] Network slicing technology essentially divides the operator's physical network into multiple virtual networks. Each virtual network is divided according to different service requirements, such as latency, bandwidth, security, and reliability, in order to flexibly respond to different network application scenarios.

[0005] However, network slicing congestion is still inevitable in densely populated areas. Summary of the invention

[0006] The embodiments of the present disclosure provide a network slice reselection method and device, an electronic device, and a computer-readable storage medium.

[0007] In a first aspect, an embodiment of the present disclosure provides a network slice reselection method, including:

[0008] Receive a message sent by the network side for the currently selected network slice, and reselect the network slice; wherein the reason carried in the message is insufficient resources.

[0009] In a second aspect, an embodiment of the present disclosure provides an electronic device, including:

[0010] at least one processor;

[0011] A memory having at least one program stored thereon, wherein when the at least one program is executed by the at least one processor, the at least one processor implements any one of the above-mentioned network slice reselection methods.

[0012] In a third aspect, an embodiment of the present disclosure provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, any one of the above-mentioned network slice reselection methods is implemented.

[0013] The network slice reselection method provided by the embodiment of the present disclosure, when receiving a message sent by the network side for the currently selected network slice, considers that the currently selected network slice has network congestion, and reselects the network slice, thereby alleviating the network congestion of the currently selected network slice while ensuring that the terminal continues to perform services through the reselected network slice, thereby improving user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 A flowchart of a network slice reselection method provided in an embodiment of the present disclosure;

[0015] Figure 2 A schematic diagram of the structure of single network slice selection assistance information (S-NSSAI) according to an embodiment of the present disclosure;

[0016] Figure 3 A flowchart of a network slice reselection method provided for Example 1 of an embodiment of the present disclosure;

[0017] Figure 4 A flowchart of a network slice reselection method provided for Example 2 of an embodiment of the present disclosure;

[0018] Figure 5 A flowchart of a network slice reselection method provided for Example 3 of an embodiment of the present disclosure;

[0019] Figure 6 A flowchart of a network slice reselection method provided for Example 4 of an embodiment of the present disclosure;

[0020] Figure 7 A block diagram of the composition of a network slice reselection device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0021] In order to enable technical personnel in the field to better understand the technical solution of the present disclosure, the network slice reselection method and device, electronic device, and computer-readable storage medium provided by the present disclosure are described in detail below with reference to the accompanying drawings.

[0022] Example embodiments will be described more fully below with reference to the accompanying drawings, but the example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. On the contrary, the purpose of providing these embodiments is to make the present disclosure thorough and complete and to enable those skilled in the art to fully understand the scope of the present disclosure.

[0023] In the absence of conflict, the various embodiments of the present disclosure and the various features therein may be combined with each other.

[0024] As used herein, the term "and / or" includes any and all combinations of at least one of the associated listed items.

[0025] The terms used herein are only used to describe specific embodiments and are not intended to limit the present disclosure. As used herein, the singular forms "a", "an" and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that when the terms "comprising" and / or "made of" are used in this specification, the presence of the features, wholes, steps, operations, elements and / or components is specified, but the presence or addition of at least one other feature, whole, step, operation, element, component and / or group thereof is not excluded.

[0026] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art. It will also be understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted as having an idealized or overly formal meaning unless explicitly defined as such herein.

[0027] Although the embodiment of the present disclosure is a method for processing congestion based on network slicing of 5G networks, the method for processing congestion in the embodiment of the present disclosure is also applicable to future communication networks (such as 6G, 7G, etc.), or any other communication network implemented using network slicing technology.

[0028] Figure 1 A flowchart of a network slice reselection method provided in an embodiment of the present disclosure.

[0029] First, refer to Figure 1 The present disclosure provides a network slice reselection method, which is applied to a terminal. The method includes:

[0030] Step 100: Receive a message sent by the network side for the currently selected network slice, and reselect the network slice; wherein the reason carried in the message is insufficient resources.

[0031] In some exemplary embodiments, no message is received from the network side for the currently selected network slice; or, a message is received from the network side for the currently selected network slice, and the reason carried in the message is not insufficient resources, and it is considered that there is no network congestion in the currently selected network slice, and the present process is terminated.

[0032] The network slice reselection method provided by the embodiment of the present disclosure, when receiving a message sent by the network side for the currently selected network slice, considers that the currently selected network slice has network congestion, and reselects the network slice, thereby alleviating the network congestion of the currently selected network slice while ensuring that the terminal continues to perform services through the reselected network slice, thereby improving user experience.

[0033] In some exemplary embodiments, the message includes any one of the following:

[0034] Protocol Data Unit (PDU) session establishment reject (PDU Session Establishment Reject) message, PDU session modification reject (PDU Session Modification Reject) message, PDU session release (PDU Session Release) message.

[0035] It should be noted that the PDU Session Establishment Reject message, PDU Session Modification Reject message, and PDU Session Release message are the message names in the 5G network. With the development of network technology, in future communication systems, the above messages may be messages with the same functions by other names, or other messages with the same functions. The specific names of the messages are not limited in the embodiments of the present disclosure.

[0036] In some exemplary embodiments, the selection of a network slice is achieved by matching available URSP rules in a URSP rule list.

[0037] In some exemplary embodiments, the URSP rule list includes: a URSP rule list preset by the terminal at the factory, and a URSP rule list updated from the network side. The URSP rule list updated from the network side has a higher priority than the URSP rule list preset by the terminal at the factory.

[0038] In some exemplary embodiments, the S-NSSAI of the network slice may be obtained by matching available URSP rules in a URSP rule list according to the applied network slice parameters.

[0039] In some exemplary embodiments, the network slice parameters include but are not limited to at least one of the following:

[0040] Data Network Name (DNN), application identifier, and fully qualified domain name (FQDN).

[0041] Simply put, the input parameter of the URSP rule is at least one of DNN, application identifier, FQDN, etc., and the output parameter is S-NSSAI.

[0042] In some exemplary embodiments, the S-NSSAI identifies a network slice. Figure 2 As shown, S-NSSAI includes the following two parts: Slice / Service Type (SST) and Slice Differentiator (SD).

[0043] Among them, SST represents the expected network slicing behavior in terms of functions and services. SST can be a standard value (such as enhanced mobile broadband (eMBB), ultra-reliable low latency communication (uRLLC), massive Internet of Things (MIoT)) or a non-standard value.

[0044] The length of SST is 1 byte. The value range of standard SST (the current protocol only uses three values, as shown in Table 1) is 0-127, and the operator-defined value range is 128-255. The operator-defined value is only valid in this network, and the standard value is universal in the entire network.

[0045] Among them, SD is optional information that supplements SST to distinguish multiple network slices of the same SST.

[0046] SST The value of SST feature eMBB 1 Network slicing for 5G eMBB URLLC 2 Network slicing for URLLC MloT 3 Network Slicing for MIoT

[0047] Table 1

[0048] The following describes the reselection of network slices in two cases.

[0049] Case 1: The terminal is a single-card user. In this case, there is only one URSP rule list, namely the first URSP rule list described below.

[0050] In some exemplary embodiments, after receiving the message sent by the network side for the currently selected network slice and before reselecting the network slice, the method further includes: marking the URSP rule corresponding to the currently selected network slice as unavailable; accordingly,

[0051] The reselection of the network slice includes: matching a URSP rule that is not marked as unavailable in the first URSP rule list or matching a user equipment routing selection policy rule that is marked as available, and reselecting a network slice corresponding to the matched available URSP rule.

[0052] In some exemplary embodiments, in order to ensure that the URSP rule marked as unavailable can be selected and used again by the terminal later, any of the following methods may be adopted:

[0053] Method 1: mark the URSP rule corresponding to the currently selected network slice as unavailable within a preset time; remove the mark of the user equipment routing policy rule after the preset time; or mark the user equipment routing policy rule as available after the preset time. For example, a timer can be set, and when the timer starts, the URSP rule corresponding to the currently selected network slice is marked as unavailable; when the timer times out, remove the mark of the URSP rule or mark the URSP rule as available.

[0054] Method 2: Detect whether network congestion occurs in the network slice corresponding to the URSP rule marked as unavailable; detect that network congestion does not occur in the network slice corresponding to the URSP rule marked as unavailable, and remove the identification of the URSP rule; or, mark the URSP rule as available; detect that network congestion occurs in the network slice corresponding to the URSP rule marked as unavailable, and continue to retain the identification of the URSP rule.

[0055] Case 2: The terminal is a dual-card or multi-card user. In this case, each card of the terminal corresponds to a URSP rule list, for example, the following first URSP rule list and second URSP rule list.

[0056] In some exemplary embodiments, after receiving the message sent by the network side for the currently selected network slice and before reselecting the network slice, the method further includes: marking the URSP rule corresponding to the currently selected network slice as unavailable; accordingly,

[0057] The reselection of the network slice includes: matching a URSP rule that is not identified as unavailable or an URSP rule identified as available in the first URSP rule list, and reselecting a network slice corresponding to the matched available URSP rule.

[0058] In some other exemplary embodiments, when no available URSP rule is matched in the first URSP rule list, the reselecting the network slice further includes:

[0059] Reselect the network slice corresponding to the available URSP rule in the second URSP rule list;

[0060] The first URSP rule list is a URSP rule list corresponding to a card that is currently processing services, and the second URSP rule list is a URSP rule list corresponding to a card that is not currently processing services.

[0061] Specifically, URSP rules that are not marked as unavailable or URSP rules that are marked as available can be matched in the second URSP rule list, and the network slice corresponding to the matched available URSP rule can be reselected.

[0062] That is, the terminal can traverse all URSP rule lists, and when all URSP rule lists do not match any available URSP rule, the process ends.

[0063] In some exemplary embodiments, in order to ensure that the URSP rule marked as unavailable can be selected and used again by the terminal later, any of the following methods may be adopted:

[0064] Method 1: mark the URSP rule corresponding to the currently selected network slice as unavailable within a preset time; remove the mark of the user equipment routing policy rule after the preset time; or mark the user equipment routing policy rule as available after the preset time. For example, a timer can be set, and when the timer starts, the URSP rule corresponding to the currently selected network slice is marked as unavailable; when the timer times out, remove the mark of the URSP rule or mark the URSP rule as available.

[0065] Method 2: Detect whether network congestion occurs in the network slice corresponding to the URSP rule marked as unavailable; detect that network congestion does not occur in the network slice corresponding to the URSP rule marked as unavailable, remove the identification of the URSP rule or mark the URSP rule as available; detect that network congestion occurs in the network slice corresponding to the URSP rule marked as unavailable, and continue to retain the identification of the URSP rule.

[0066] The specific implementation process of the above embodiment is described in detail below through specific examples. The examples listed are only for the convenience of explanation and are not used to limit the protection scope of the embodiments of the present disclosure.

[0067] Example 1

[0068] like Figure 3 As shown, the method includes:

[0069] Step 300: Apply for network slice A.

[0070] Step 301, determine whether the identity of the application is correct. If the identity of the application is correct, continue to step 302; if the identity of the application is incorrect, end this process.

[0071] In some exemplary embodiments, whether the identity of the application is correct may be determined based on at least one of an application identifier, an application package name, and an application signature.

[0072] Step 302: Match available USRP rules in the USRP rule list to obtain S-NSSAI.

[0073] In some exemplary embodiments, the S-NSSAI of the network slice may be obtained by matching available URSP rules in a URSP rule list according to the applied network slice parameters.

[0074] In some exemplary embodiments, the network slice parameters include but are not limited to at least one of the following:

[0075] DNN, application ID, FQDN.

[0076] Simply put, the input parameter of the URSP rule is at least one of DNN, application identifier, FQDN, etc., and the output parameter is S-NSSAI.

[0077] Step 303: Send a PDU session establishment request to the network side. The PDU session establishment request carries S-NSSAI, indicating the network slice you want to apply for.

[0078] Step 304: monitor whether a PDU Session Establishment Reject message is received from the network side, and determine whether the reason carried in the message is insufficient resources. If a PDU Session Establishment Reject message is received, and the reason carried in the message is insufficient resources, continue to execute step 305; if no PDU Session Establishment Reject message is received; or if a PDUSession Establishment Reject message is received, and the reason carried in the message is not insufficient resources, end this process.

[0079] Step 305: mark the URSP rule as "unavailable", and continue to execute step 302.

[0080] Example 2

[0081] like Figure 4 As shown, the method includes:

[0082] Step 400: The application applies for network slice A and successfully creates a PDU session.

[0083] Step 401, monitor whether a PDU Session Modification Reject or PDU Session Release message is received from the network side to the terminal, and determine whether the reason carried in the message is insufficient resource; if a PDU Session Modification Reject or PDU Session Release message is received from the network side to the terminal, and the reason carried in the message is insufficient resource, continue to execute step 402; if no PDU Session Modification Reject or PDU Session Release message is received; or, if a PDU Session Modification Reject or PDU Session Release message is received from the network side to the terminal, and the reason carried in the message is not insufficient resource, end this process.

[0084] Step 402: Mark the URSP rule corresponding to network slice A as "unavailable".

[0085] Step 403: Match available USRP rules in the USRP rule list to obtain S-NSSAI.

[0086] Step 404: Determine whether the PDU session corresponding to the network slice has been created. If the PDU session corresponding to the network slice has been created, use the existing PDU session. If the PDU session has not been created, send a PDU session establishment request to the network side. The PDU session establishment request carries S-NSSAI, indicating the network slice you wish to apply for.

[0087] Example 3

[0088] This example describes the method for handling congestion in the dual-card scenario (two subscriber identification module (SIM) cards of different operators, assuming that the data service of SIM card 1 is currently in use). When reselecting the network slice, it is found that there is an available network slice under the 5G network where SIM card 2 is located. The terminal switches the data service to SIM card 2 and creates a PDU session for the specified network slice after successfully registering on the 5G network.

[0089] like Figure 5 As shown, the method includes:

[0090] Step 500, the application applies for network slice A of SIM card 1, and the PDU session has been successfully created.

[0091] Step 501, monitor whether a PDU Session Modification Reject or PDU Session Release message is received from the network side to the terminal, and determine whether the reason carried in the message is insufficient resource; if a PDU Session Modification Reject or PDU Session Release message is received from the network side to the terminal, and the reason carried in the message is insufficient resource, continue to execute step 502; if no PDU Session Modification Reject or PDU Session Release message is received; or, if a PDU Session Modification Reject or PDU Session Release message is received from the network side to the terminal, and the reason carried in the message is not insufficient resource, end this process.

[0092] Step 502: Mark the URSP rule corresponding to network slice A of SIM card 1 as "unavailable".

[0093] Step 503: If no available USRP rule is matched in the USRP rule list of SIM card 1, then the available USRP rule is matched in the USRP rule list of SIM card 2. If network slice B or network slice C corresponding to the available USRP rule is matched, the S-NSSAI of network slice B or network slice C is obtained.

[0094] Step 504: Switch the data service from SIM card 1 to SIM card 2, and SIM card 2 is successfully registered on the 5G network.

[0095] Step 505: Send a PDU session establishment request to the network side. The PDU session establishment request carries S-NSSAI, indicating the network slice you want to apply for.

[0096] Example 4

[0097] This example describes the method for handling congestion in the dual-card scenario (two subscriber identification module (SIM) cards of different operators, assuming that the data service of SIM card 1 is currently in use). When reselecting the network slice, it is found that there are available network slices under the 5G network where SIM card 2 is located. Then, SIM card 1 of the terminal attempts to register to the 5G network of SIM card 2, and creates a PDU session for the specified network slice after SIM card 1 successfully registers to the 5G network of SIM card 2 (that is, the scenario in which SIM card 1 roams to the network of SIM card 2).

[0098] like Figure 6 As shown, the method includes:

[0099] Step 600, the application applies for network slice A of SIM card 1, and the PDU session has been successfully created.

[0100] Step 601, monitor whether a PDU Session Modification Reject or PDU Session Release message is received from the network side to the terminal, and determine whether the reason carried in the message is insufficient resource; if a PDU Session Modification Reject or PDU Session Release message is received from the network side to the terminal, and the reason carried in the message is insufficient resource, continue to execute step 602; if no PDU Session Modification Reject or PDU Session Release message is received; or, if a PDU Session Modification Reject or PDU Session Release message is received from the network side to the terminal, and the reason carried in the message is not insufficient resource, end this process.

[0101] Step 602: Mark the URSP rule corresponding to network slice A of SIM card 1 as "unavailable".

[0102] Step 603: If no available USRP rule is matched in the USRP rule list of SIM card 1, then the available USRP rule is matched in the USRP rule list of SIM card 2. If network slice B or network slice C corresponding to the available USRP rule is matched, the S-NSSAI of network slice B or network slice C is obtained.

[0103] Step 604: SIM card 1 attempts to register with the 5G network of SIM card 2, and SIM card 1 successfully registers with the 5G network of SIM card 2.

[0104] Step 605: Send a PDU session establishment request to the network side. The PDU session establishment request carries S-NSSAI, indicating the network slice you want to apply for.

[0105] In a second aspect, an embodiment of the present disclosure provides an electronic device, including:

[0106] at least one processor;

[0107] A memory having at least one program stored thereon, wherein when the at least one program is executed by at least one processor, the at least one processor implements any one of the above-mentioned network slice reselection methods.

[0108] Among them, the processor is a device with data processing capabilities, including but not limited to a central processing unit (CPU), etc.; the memory is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and flash memory (FLASH).

[0109] In some embodiments, the processor and the memory are connected to each other through a bus, and further connected to other components of the computing device.

[0110] In a third aspect, an embodiment of the present disclosure provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, any one of the above-mentioned network slice reselection methods is implemented.

[0111] Figure 7 A block diagram of the composition of a network slice reselection device provided in an embodiment of the present disclosure.

[0112] Fourthly, refer to Figure 7 , the embodiment of the present disclosure provides a network slice reselection device, including:

[0113] The congestion detection module 701 is used to monitor whether a message sent by the network side for the currently selected network slice is received, and determine whether the reason carried in the message is insufficient resources;

[0114] The network slice selection module 702 is used for the congestion detection module 701 to receive a message sent by the network side for the currently selected network slice, and the reason carried in the message is insufficient resources, and reselect the network slice.

[0115] In some exemplary embodiments, the message includes any one of the following:

[0116] Protocol data unit session establishment reject message, protocol data unit session modification reject message, protocol data unit session release message.

[0117] In some exemplary embodiments, the network slice selection module 702 is specifically configured to:

[0118] The congestion detection module 701 receives a message sent by the network side for the currently selected network slice, and the reason carried in the message is insufficient resources, and marks the user equipment routing selection policy rule corresponding to the currently selected network slice as unavailable; matches the user equipment routing selection policy rule that is not marked as unavailable in the first user equipment routing selection policy rule list or matches the user equipment routing selection policy rule that is marked as available, and reselects the network slice corresponding to the matched available user equipment routing selection policy rule.

[0119] In some exemplary embodiments, the network slice selection module 702 is specifically configured to implement the step of marking the user equipment routing selection policy rule corresponding to the currently selected network slice as unavailable in the following manner:

[0120] Marking the user equipment routing selection policy rule corresponding to the currently selected network slice as unavailable within a preset time;

[0121] The identification of the user equipment routing policy rule is removed after the preset time; or the user equipment routing policy rule is identified as available after the preset time.

[0122] In some exemplary embodiments, the network slice selection module 702 is further configured to:

[0123] Detect whether network congestion occurs in the network slice corresponding to the user equipment routing selection policy rule marked as unavailable; detect that network congestion does not occur in the network slice corresponding to the user equipment routing selection policy rule marked as unavailable, and remove the identification of the user equipment routing selection policy rule; or, mark the user equipment routing selection policy rule as available.

[0124] In some exemplary embodiments, the network slice selection module 702 is further configured to:

[0125] When no available user equipment routing selection policy rule is matched in the first user equipment routing selection policy rule list, reselecting a network slice corresponding to the available user equipment routing selection policy rule in the second user equipment routing selection policy rule list;

[0126] Among them, the first user equipment routing policy rule list is a user equipment routing policy rule list corresponding to the card that is currently processing business, and the second user equipment routing policy rule list is a user equipment routing policy rule list corresponding to the card that is not currently processing business.

[0127] The specific implementation process of the above-mentioned network slice reselection device is the same as the specific implementation process of the network slice reselection method in the aforementioned embodiment, and will not be repeated here.

[0128] It will be appreciated by those skilled in the art that all or some of the steps, systems, and functional modules / units in the methods disclosed above may be implemented as software, firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may be performed by several physical components in cooperation. Some or all physical components may be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit. Such software may be distributed on a computer-readable medium, which may include a computer storage medium (or non-transitory medium) and a communication medium (or temporary medium). As known to those skilled in the art, the term computer storage medium includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage, or any other medium that can be used to store the desired information and can be accessed by a computer. In addition, it is well known to those skilled in the art that communication media typically contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media.

[0129] Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted only in a general illustrative sense and not for limiting purposes. In some instances, it will be apparent to those skilled in the art that, unless otherwise expressly noted, features, characteristics, and / or elements described in conjunction with a particular embodiment may be used alone or in combination with features, characteristics, and / or elements described in conjunction with other embodiments. Therefore, those skilled in the art will appreciate that various changes in form and detail may be made without departing from the scope of the present disclosure as set forth in the appended claims.

Claims

1. A network slice reselection method, include: A message is received from the network side for the currently selected network slice; wherein the reason carried in the message is insufficient resources; Marking the user equipment routing selection policy rule corresponding to the currently selected network slice as unavailable; matching a user equipment routing policy rule that is not identified as unavailable in the first user equipment routing policy rule list; Reselect the network slice corresponding to the matching available user equipment routing selection policy rule.

2. The method according to claim 1, in, The marking of the user equipment routing selection policy rule corresponding to the currently selected network slice as unavailable comprises: Marking the user equipment routing selection policy rule corresponding to the currently selected network slice as unavailable within a preset time; The identification of the user equipment routing policy rule is removed after the preset time; or the user equipment routing policy rule is identified as available after the preset time.

3. According to the method of claim 1, after reselecting the network slice corresponding to the matched available user equipment routing selection policy rule, the method further include: Detect whether network congestion occurs in the network slice corresponding to the routing policy rule of the user equipment marked as unavailable; When it is detected that the network slice corresponding to the user equipment routing selection policy rule marked as unavailable has no network congestion, the marking of the user equipment routing selection policy rule is removed; or, the user equipment routing selection policy rule is marked as available.

4. According to the method of claim 1, when no available user equipment routing policy rule is matched in the first user equipment routing policy rule list, the network slice corresponding to the reselected matched available user equipment routing policy rule is also include: Reselecting a network slice corresponding to an available user equipment routing policy rule in the second user equipment routing policy rule list; Among them, the first user equipment routing policy rule list is a user equipment routing policy rule list corresponding to the card that is currently processing business, and the second user equipment routing policy rule list is a user equipment routing policy rule list corresponding to the card that is not currently processing business.

5. The method according to any one of claims 1 to 4, in, The message includes any of the following: Protocol data unit session establishment reject message, protocol data unit session modification reject message, protocol data unit session release message.

6. An electronic device, include: at least one processor; A memory having at least one program stored thereon, wherein when the at least one program is executed by the at least one processor, the at least one processor implements the network slice reselection method according to any one of claims 1-5.

7. A computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the network slice reselection method according to any one of claims 1-5 is implemented.

Images