Network slice management method, terminal and computer-readable storage medium

Abstract

The present invention provides a network slice management method, a terminal and a computer-readable storage medium. The network slice management method includes: obtaining terminal operation information, determining the network slice to be released from the network slice to which the terminal application is connected according to the terminal operation information, and releasing the network slice to be released. According to the solution provided by the embodiment of the present invention, by obtaining the terminal operation information, the operation information of the terminal can be monitored, and according to the working condition of the terminal represented by the terminal operation information, the network slice to be released can be determined from the network slice to which the terminal application is connected, and then the network slice to be released can be released, so as to avoid the application that the user is not using temporarily still maintaining access to the network slice, so as to avoid generating additional fees when the network slice is charged according to the usage time, thereby improving the user experience.

Description

Technical Field

[0001] The embodiments of the present invention relate to but are not limited to the field of communication technology, and in particular, to a network slice management method, terminal and computer-readable storage medium. Background Art

[0002] As an important technology of 5G network, network slicing allows operators to divide multiple virtual end-to-end networks in a hardware infrastructure. Each network slice realizes logical isolation in terms of terminals, access networks, transmission networks and core networks, and can adapt to various types of services and meet different needs of users. Through network slicing technology, 5G network meets the differentiated needs of users in terms of priority, billing, policy control, security and mobility, as well as differentiated needs in terms of performance such as latency, reliability and speed.

[0003] In order to meet the user's demand for 5G network use, when the terminal application is connected to the network slice, as long as the user does not close the application, even if the user does not use the application temporarily and switches the application to the background running mode, the application will remain connected to the network slice. However, for the above application scenarios, if the billing strategy of the network slice is to charge according to the usage time, the user will have to pay a higher fee than the actual usage time, which is not conducive to the user's experience. Summary of the invention

[0004] The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.

[0005] The embodiments of the present invention provide a network slice management method, a terminal and a computer-readable storage medium, which can avoid incurring additional costs when the network slice is charged according to the usage time, thereby improving the user experience.

[0006] In a first aspect, an embodiment of the present invention provides a network slice management method, including:

[0007] Get terminal operation information;

[0008] Determine the network slice to be released from the network slice accessed by the application of the terminal according to the terminal operation information;

[0009] Release the network slice to be released.

[0010] In a second aspect, an embodiment of the present invention further provides a terminal, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the network slice management method as described in the first aspect above is implemented.

[0011] In a third aspect, an embodiment of the present invention further provides a computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the network slice management method as described above.

[0012] An embodiment of the present invention includes: the terminal obtains terminal operation information, and determines the network slice to be released from the network slice accessed by the terminal application according to the terminal operation information, and then releases the network slice to be released. According to the solution provided by the embodiment of the present invention, by obtaining the terminal operation information, the operation information of the terminal can be monitored, for example, the operation status of the terminal application, the operation status of the terminal system, and the network connection quality of the terminal and other related information can be monitored; and according to the working condition of the terminal represented by the terminal operation information, the network slice to be released can be determined from the network slice accessed by the terminal application, for example, it is determined that the network slice accessed by the application that the user is not using temporarily is the network slice to be released; then the network slice to be released is released to avoid the application that the user is not using temporarily still maintaining access to the network slice, so that when the network slice is charged according to the length of use, additional fees can be avoided, thereby improving the user experience.

[0013] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings are used to provide a further understanding of the technical solution of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the technical solution of the present invention and do not constitute a limitation on the technical solution of the present invention.

[0015] Figure 1 is a schematic diagram of a system architecture platform for executing a network slice management method provided by an embodiment of the present invention;

[0016] Figure 2 is a flowchart of a network slice management method provided by an embodiment of the present invention;

[0017] Figure 3 is a flowchart of a network slice management method provided by another embodiment of the present invention;

[0018] Figure 4 is a flowchart of a network slice management method provided by another embodiment of the present invention;

[0019] Figure 5 is a flowchart of a network slice management method provided by another embodiment of the present invention;

[0020] Figure 6is a flowchart of a network slice management method provided by another embodiment of the present invention;

[0021] Figure 7 is a flowchart of a network slice management method provided by another embodiment of the present invention;

[0022] Figure 8 is a flowchart of a network slice management method provided by another embodiment of the present invention;

[0023] Fig. 9 is a flowchart of a network slice management method provided by another embodiment of the present invention;

[0024] Fig.10 It is a flowchart of a network slice management method provided by another embodiment of the present invention. DETAILED DESCRIPTION

[0025] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0026] It should be noted that, although the functional modules are divided in the device schematic diagram and the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than the module division in the device or the order in the flowchart. The terms "first", "second", etc. in the specification, claims and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0027] The present invention provides a network slice management method, a terminal and a computer-readable storage medium. The terminal obtains its own terminal operation information and can monitor the terminal operation information, for example, it can monitor the operation status of the terminal application, the operation status of the terminal system and the network connection quality of the terminal and other related information; then, the terminal can determine the network slice to be released from the network slices accessed by the terminal application according to the terminal working status represented by the terminal operation information, for example, determine that the network slice accessed by the application that the user is not using temporarily is the network slice to be released; then, the terminal releases the network slice to be released to prevent the application that the user is not using temporarily from still maintaining access to the network slice, thereby avoiding additional fees when the network slice is charged according to the usage time, thereby improving the user experience.

[0028] The embodiments of the present invention are further described below in conjunction with the accompanying drawings.

[0029] like Figure 1 As shown, Figure 1FIG. 1 is a schematic diagram of a system architecture platform for executing a network slice management method provided by an embodiment of the present invention. Figure 1 In the example of , the system architecture platform 100 includes a recording module 110, a monitoring module 120, a network slice management module 130, a connection management module 140 and a monitoring module 150. Among them, the recording module 110 is used to record the applicants and users of the network slices, such as the applications that apply for network slices and the applications that use network slices; the monitoring module 120 is used to monitor whether the running status of each application in the terminal has changed, and also to monitor whether the running status of the terminal system has changed; the network slice management module 130 is used to apply for, maintain and release network slices; the connection management module 140 is used to configure relevant network ports and routes for each application; the monitoring module 150 is used to monitor the network quality information of the network slice and the default network of the terminal.

[0030] The system architecture platform 100 and the application scenarios described in the embodiment of the present invention are intended to more clearly illustrate the technical solutions of the embodiment of the present invention, and do not constitute a limitation on the technical solutions provided by the embodiment of the present invention. Those skilled in the art will appreciate that with the evolution of the system architecture platform and the emergence of new application scenarios, the technical solutions provided by the embodiment of the present invention are equally applicable to similar technical problems.

[0031] It can be understood by those skilled in the art that Figure 1 The structure of the system architecture platform 100 shown in the figure does not constitute a limitation on the embodiments of the present invention, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0032] exist Figure 1 In the system architecture platform 100 shown, the recording module 110, the monitoring module 120, the network slice management module 130, the connection management module 140 and the monitoring module 150 can cooperate to execute the network slice management method.

[0033] Based on the structure of the above-mentioned system architecture platform, various embodiments of the network slice management method of the present invention are proposed.

[0034] like Figure 2 As shown, Figure 2 It is a flowchart of a network slice management method provided by an embodiment of the present invention. The network slice management method includes but is not limited to step S100, step S200 and step S300.

[0035] Step S100, obtaining terminal operation information.

[0036] In one embodiment, when the terminal is in a working state, the terminal can obtain terminal operation information, for example, obtain terminal operation information through a monitoring module in the terminal, so that the operation information of the terminal can be monitored to provide the necessary basic conditions for the operation of releasing the network slice in subsequent steps.

[0037] In one embodiment, the terminal operation information is various information that can represent the working status of the terminal, which may include but is not limited to the application operation status of each application in the terminal, the terminal system status of the terminal itself, and the network quality information between the terminal and the network.

[0038] It is worth noting that before executing step S100, each application in the terminal can apply for the corresponding network slice according to the actual situation. For example, when a user opens an application that needs to obtain data information from the network, the application will apply for the corresponding network slice. Depending on the actual situation, each application in the terminal can access its own network slice respectively, or multiple applications can access a common network slice together. This embodiment does not specifically limit this. In addition, after the application accesses the network slice, the recording module in the terminal can save the applicant or user of the network slice. For example, the recording module can save the application name or application identity of the application accessing the network slice and other related information, so that the terminal can manage the network slice and the corresponding application. In addition, when the application applies to access the network slice, the terminal will establish a protocol data unit (PDU) session with the 5G network. After the terminal establishes a PDU session with the 5G network, the corresponding application will be able to access the corresponding network slice, so that the services provided by the network slice can be used.

[0039] Step S200, determining the network slice to be released from the network slices accessed by the terminal application according to the terminal operation information.

[0040] In one embodiment, the network slice to be released may be a network slice that is not needed to be used or connected temporarily. After the terminal operation information is obtained, the network slice to be released that is not needed to be used or connected temporarily can be determined from the network slices accessed by the terminal application according to the terminal operation information, so that the network slice to be released that is not needed to be used or connected temporarily can be released in a targeted manner in subsequent steps, so as to avoid the application that is not currently used by the user still maintaining access to the network slice, so as to avoid generating additional fees when the network slice is charged according to the usage time, thereby improving the user's usage experience.

[0041] In one embodiment, there may be different implementations for determining the network slice to be released from the network slice accessed by the terminal application, depending on the specific content of the terminal operation information, and this embodiment does not specifically limit this. For example, when the terminal operation information includes the application operation status of each application in the terminal, then when the application operation status changes and it is manifested that the user does not need to use the corresponding application temporarily, it can be determined that the network slice accessed by the application is the network slice to be released. For another example, when the terminal operation information includes the terminal system status of the terminal itself, then when the terminal system status changes and it is manifested that the user does not need to use the terminal temporarily, it can be determined that all network slices currently maintained and accessed by the terminal are network slices to be released.

[0042] Step S300, release the network slice to be released.

[0043] In one embodiment, after determining the network slice to be released from the network slices accessed by the terminal application, in order to avoid the application that is not used by the user still maintaining access to the network slice and incurring additional fees, the network slice to be released can be released by the network slice management module in the terminal, thereby avoiding additional fees when the network slice is charged according to the usage time, thereby improving the user experience. In addition, since the network slice that is not needed to be used or connected temporarily can be released in time, the problem of high power consumption caused by the terminal's continuous connection to the network slice can be avoided, thereby achieving the effect of terminal energy saving.

[0044] In one embodiment, by adopting a network slice management method including the above-mentioned steps S100, S200 and S300, the terminal can monitor the terminal operation information such as the operation status of each application, the operation status of the terminal system and the network connection quality of the terminal, so that the network slices to be released can be determined from the network slices accessed by the terminal applications according to the working conditions of the terminal represented by these terminal operation information, and the network slices to be released can be released in time, thereby avoiding that applications that users do not need to use temporarily still maintain access to the network slices, and avoiding additional fees when the network slices are charged according to the length of use, thereby improving the user experience. In addition, since the terminal can release the network slices that are not needed to be used or connected temporarily in time, the problem of high power consumption caused by the terminal's continuous connection to the network slice can be avoided, thereby achieving the effect of terminal energy saving.

[0045] In addition, in one embodiment, referring to Figure 3 When the terminal operation information includes the application operation status, step S200 may include but is not limited to the following steps:

[0046] Step S210, when the application running status is indicated as the corresponding application entering the background running state or being in an abnormal running state, and when the application remains in the background running state or in the abnormal running state for a first period of time, it is determined that the network slice accessed by the application is a network slice to be released.

[0047] In one embodiment, when the application running state is represented as the corresponding application entering the background running state, and the application maintains the background running state for a first time period, it means that the application entering the background running state is not a user's misoperation, but the user switches the application to the background running state for the purpose of not needing to use the application at present, that is, the user clearly expresses the intention of not needing to use the application at present, therefore, the network slice accessed by the application can be determined as a network slice to be released, so that the network slice to be released can be released in subsequent steps, thereby avoiding additional costs when the network slice is charged according to the usage time, and improving the user experience. In addition, since the user does not need to use the application at present, by releasing the network slice accessed by the application, the problem of high power consumption of the terminal caused by the continuous connection of the application to the network slice can be avoided, thereby achieving the effect of terminal energy saving.

[0048] In one embodiment, when the application running state indicates that the corresponding application is in an abnormal running state, and the application maintains the abnormal running state for a first time period, it means that the application is in an abnormal state that cannot be recovered by itself in a short time, and the application cannot provide services to users again in a short time. If the application still accesses the network slice, it will cause the user to pay the fee but not get the corresponding service. Therefore, the network slice accessed by the application can be determined as a network slice to be released, so that the network slice to be released can be released in subsequent steps, thereby avoiding additional costs when the network slice is charged according to the usage time, and improving the user experience. In addition, since the application cannot provide services to users normally, by releasing the network slice accessed by the application, the problem of high power consumption of the terminal caused by the continuous connection of the application to the network slice can be avoided, thereby achieving the effect of terminal energy saving.

[0049] In one embodiment, the abnormal running state of the application may include a state where the application is frozen or the application is in an application not responding (ANR) state, etc., which is not specifically limited in this embodiment.

[0050] In one embodiment, the value of the first duration can be appropriately selected according to actual conditions, and this embodiment does not specifically limit this. In addition, the setting of the first duration can be achieved by setting a timer or a timer, and this embodiment also does not specifically limit this.

[0051] In addition, in one embodiment, referring to Figure 4 The step S210 of determining that the network slice accessed by the application is a network slice to be released may include but is not limited to the following steps:

[0052] Step S211, determining the network slice to which the application is accessed;

[0053] Step S212, when only the application accesses the network slice;

[0054] Step S213, determine that the network slice is a network slice to be released.

[0055] In one embodiment, when an application enters a background running state or is in an abnormal running state, and the application maintains the background running state or is in an abnormal running state for a first time period, it is also necessary to determine whether there are other applications that access the same network slice as the application. If there are other applications that also access the network slice accessed by the application, the network slice accessed by the application cannot be determined as a network slice to be released. If the network slice is determined to be a network slice to be released and released, it will affect the normal use of other applications. Therefore, when the application running state is represented as the corresponding application entering a background running state or an abnormal running state, and the application maintains the background running state or is in an abnormal running state for a first time period, from the network slices accessed by various applications of the terminal, it is determined that only the network slice accessed by the application is a network slice to be released. Therefore, when the network slice to be released is released in the subsequent steps, it can not only not affect the normal use of other applications, but also avoid generating additional fees when the network slice is charged according to the usage time, thereby improving the user experience.

[0056] It is worth noting that when other applications are also connected to the network slice to which the application is connected, since the application remains in the background or in an abnormal running state for the first period of time, if the application is still maintained in access to the network slice, it will cause additional costs. Therefore, the application can be switched to access the default network of the terminal to avoid additional costs when the network slice is charged according to the usage time, thereby improving the user experience.

[0057] In addition, in one embodiment, when the terminal operation information includes the terminal system status, step S200 may also include but is not limited to the following steps:

[0058] When the terminal system status indicates that the terminal has entered a sleep state, it is determined that all network slices accessed by the terminal's applications are network slices to be released.

[0059] In one embodiment, when the terminal system status is indicated as the terminal entering a dormant state, it indicates that the user is not currently using the terminal, that is, the user does not currently need the application in the terminal to provide services for him / her. Therefore, all network slices accessed by various applications in the terminal can be determined as network slices to be released, so that the network slices to be released can be released in subsequent steps, thereby avoiding additional costs when the network slices are charged according to the length of use, and improving the user experience. In addition, since the terminal has entered a dormant state, that is, the terminal has entered a power saving mode, by releasing the network slice accessed by the application, the problem of high power consumption of the terminal caused by the application continuously connecting to the network slice can be avoided, thereby achieving the effect of energy saving of the terminal.

[0060] In addition, in one embodiment, when the terminal operation information includes first network quality information corresponding to the network slice and second network quality information corresponding to the terminal default network, step S200 may also include but is not limited to the following steps:

[0061] When the second network quality information is better than the first network quality information and lasts for a second period of time, the network slice corresponding to the first network quality information is determined from the network slices accessed by the application of the terminal as the network slice to be released.

[0062] In one embodiment, after the terminal accesses the network, the monitoring module in the terminal monitors the network quality information between the terminal and the network, for example, monitoring the second network quality information between the terminal and the terminal default network, wherein the terminal default network is determined according to the standard supported by the terminal and the default standard set by the user, for example, the standards supported by the terminal include 3G network, 4G network and 5G network, and the default standard set by the user is 4G network, then the terminal default network is 4G network. In addition, when the application in the terminal accesses the network slice, the monitoring module also monitors the first network quality information between the terminal and the network slice. When the second network quality information is better than the first network quality information and lasts for a second period of time, it means that the current connection quality between the terminal and the network slice is relatively poor. If the application is still accessed to the network slice, it may affect the user's experience, which is specifically reflected in low network transmission speed, disconnection, failure to access the network, etc. Therefore, in order to avoid affecting the user's experience of using the application, the network slice corresponding to the first network quality information is determined from the network slice accessed by the application of the terminal as the network slice to be released, so that the network slice to be released can be released in subsequent steps; and in order to ensure the normal use of the application by the user, after releasing the network slice to be released, the application can be switched to the terminal default network, so as to ensure the normal use of the application by the user, and avoid incurring additional fees when the network slice is charged according to the usage time, thereby improving the user's experience.

[0063] In one embodiment, the first network quality information and the second network quality information may both include but are not limited to performance indicators such as latency, reliability, and rate. The superiority or inferiority between the first network quality information and the second network quality information may be judged by an overall analysis of various performance indicators, thereby providing a basic condition for whether to subsequently execute the operation of releasing the network slice.

[0064] In one embodiment, the value of the second duration can be appropriately selected according to actual conditions, and this embodiment does not specifically limit this. In addition, the setting of the second duration can be achieved by setting a timer or a timer, and this embodiment also does not specifically limit this.

[0065] In addition, in one embodiment, the network slice management method may also include but is not limited to the following steps:

[0066] Switch the application accessing the network slice to be released to the terminal's default network.

[0067] In one embodiment, after determining the network slice to be released from the network slices accessed by the terminal application according to the terminal operation information, in order to avoid affecting the normal use of the application accessing the network slice to be released, the application accessing the network slice to be released can be switched to the terminal default network, and the terminal default network is used to carry the business data of the application, so as to ensure that the application can provide services to users normally. It is worth noting that when the step of switching the application accessing the network slice to be released to the terminal default network in this embodiment is executed, the connection management module in the terminal will reconfigure the network port and related routes for the application, so that the application can access the terminal default network.

[0068] In one embodiment, the step of switching the application accessing the network slice to be released to the default network of the terminal may be executed at different times, for example, it may be executed before step S300 in the above embodiment, or it may be executed synchronously with step S300, and this embodiment does not specifically limit this. When the step of switching the application accessing the network slice to be released to the default network of the terminal in this embodiment is executed before step S300, the network slice to be released and the default network of the terminal may carry the business data of the application at the same time, and when the network slice to be released in step S300 is released, the normal use of the application is not affected, and the effect of seamlessly switching the network carrying the business data of the application is achieved. When the step of switching the application accessing the network slice to be released to the default network of the terminal in this embodiment is executed synchronously with step S300, the application can also be kept able to provide services to the user normally during the process of switching the network carrying the business data of the application, thereby avoiding affecting the user's experience.

[0069] In addition, in one embodiment, when the application enters the background running state or is in an abnormal running state, causing the network slice accessed by the application to be released, the network slice management method may also include but is not limited to the following steps:

[0070] When the application exits the background running state or the abnormal running state, apply for access to the network slice for the application again.

[0071] In one embodiment, when the application exits the background running state, it means that the user is currently using the application, so the application can be re-applied for access to the network slice so that the application can provide 5G network services to the user. When the application exits the abnormal running state, it means that the application resumes normal operation and can continue to provide services to the user. Therefore, the application can be re-applied for access to the network slice so that the application can provide 5G network services to the user.

[0072] It is worth noting that when re-applying for access to the network slice for the application, the network slice management module in the terminal will first apply for a network slice for the application from the network, and then the connection management module in the terminal will reconfigure the network port and related routes for the application so that the application can access the applied network slice.

[0073] In addition, in one embodiment, referring to Figure 5 , re-apply for access to the network slice for the application, including but not limited to the following steps:

[0074] Step S410, obtaining the network slice application history table of the application;

[0075] Step S420: Reapply for access to the network slice for the application according to the network slice application history table.

[0076] In one embodiment, when an application successfully accesses a network slice, since the recording module in the terminal will save the applicant or user of the network slice, for example, save relevant information such as the application name or application identity of the application accessing the network slice, the recording module can establish a network slice application history table based on the network slice to which the application successfully accesses, which can not only facilitate the management of the network slice, but also provide convenience for subsequent re-application of the network slice.

[0077] In one embodiment, since the network slice application history table records the relevant information of the network slices that each application in the terminal has applied for access to, as well as information such as the applicant or user of the network slice, when it is necessary to reapply for access to the network slice for the application, the network slice application history table maintained by the recording module can be used to reapply for access to the network slice for the application, thereby improving the efficiency of applying for network slices. To illustrate with a specific example, when it is necessary to reapply for access to the network slice for the application, the network slice application history table that the application has applied for access to can be first searched in the recording module, and then the network slice management module is controlled to apply to the network for access to the network slice for the application according to the network slice application history table.

[0078] It is worth noting that when reapplying for access to a network slice for an application according to the network slice application history table, the relevant information of the network slice that has been accessed can be selected in sequence in the network slice application history table and the corresponding network slice can be applied to the network. Alternatively, the relevant information of the network slice that is suitable for the current transmission quality requirement of the application can be selected in the network slice application history table first, and then the corresponding network slice can be applied to the network. This embodiment does not make any specific limitations on this.

[0079] In order to more clearly illustrate the specific steps and processes of the network slice management method in the above-mentioned embodiments, specific examples are given below.

[0080] Example 1:

[0081] like Figure 6 As shown, Figure 6 It is a flowchart of a network slice management method for a single application provided by a specific example of the present invention. The network slice management method is applied to a terminal, and the network slice management method includes the following steps:

[0082] Step S501: an application A accesses the network slice NS1 and establishes a PDU session between the terminal and the 5G network;

[0083] Step S502, notifying the recording module to record the applicant or user of the network slice NS1;

[0084] Step S503, notifying the monitoring module to monitor the status changes of each application;

[0085] Step S504, when the monitoring module monitors that application A is switched to the background by the user;

[0086] Step S505, notifying the network slice management module to start timer Timer A;

[0087] Step S506, determining whether application A is switched to the foreground before timer Timer A reaches a preset time, if not, executing step S507; if yes, executing step S509;

[0088] Step S507, notifying the network slice management module to release the network slice NS1;

[0089] Step S508, instructing the connection management module to reconfigure the network port and related routes for application A so that application A can access the default network of the terminal;

[0090] Step S509, notifying the network slice management module to stop timer Timer A;

[0091] Step S510, this processing flow ends.

[0092] Example 2:

[0093] like Figure 7 As shown, Figure 7 is a flowchart of a network slice management method for multiple applications provided by another specific example of the present invention, the network slice management method is applied to a terminal, and the network slice management method includes the following steps:

[0094] Step S601: an application A accesses the network slice NS1 and establishes a PDU session between the terminal and the 5G network;

[0095] Step S602, notifying the recording module to record the applicant or user of the network slice NS1;

[0096] Step S603, notifying the monitoring module to monitor the status changes of each application;

[0097] Step S604, when the monitoring module monitors that application A is switched to the background by the user;

[0098] Step S605, notifying the network slice management module to start timer Timer A;

[0099] Step S606, determining whether application A is switched to the foreground before timer Timer A reaches a preset time, if not, executing step S607; if yes, executing step S610;

[0100] Step S607, determine whether other applications are using network slice NS1, if not, execute step S608; if yes, execute step S609;

[0101] Step S608, notifying the network slice management module to release the network slice NS1;

[0102] Step S609, instructing the connection management module to reconfigure the network port and related routes for application A so that application A can access the default network of the terminal;

[0103] Step S610, notifying the network slice management module to stop timer Timer A;

[0104] Step S611, this processing flow ends.

[0105] Example 3:

[0106] like Figure 8 As shown, Figure 8 It is a flowchart of a network slice management method for a terminal system state provided by another specific example of the present invention. The network slice management method is applied to a terminal, and the network slice management method includes the following steps:

[0107] Step S701: an application A accesses the network slice NS1 and establishes a PDU session between the terminal and the 5G network;

[0108] Step S702, notifying the recording module to record the applicant or user of the network slice NS1;

[0109] Step S703, notifying the monitoring module to monitor the status change of the terminal system;

[0110] Step S704, when the monitoring module monitors that the terminal enters the sleep state;

[0111] Step S705, notifying the network slice management module to release the network slice NS1;

[0112] Step S706, instructing the connection management module to reconfigure the network port and related routes for application A so that application A can access the default network of the terminal;

[0113] Step S707, this processing flow ends.

[0114] Example 4:

[0115] like Fig. 9 As shown, Fig. 9 is a flowchart of a network slice management method for network connection quality provided by another specific example of the present invention, the network slice management method is applied to a terminal, and the network slice management method includes the following steps:

[0116] Step S801: an application A accesses the network slice NS1 and establishes a PDU session between the terminal and the 5G network;

[0117] Step S802, notifying the recording module to record the applicant or user of the network slice NS1;

[0118] Step S803, notifying the monitoring module to monitor the network connection quality of the network slice NS1 and the default network of the terminal in real time;

[0119] Step S804: When the monitoring module detects that the network connection quality of the network slice NS1 is lower than the network connection quality of the terminal default network and lasts for a period of time;

[0120] Step S805, notifying the network slice management module to release the network slice NS1;

[0121] Step S806, instructing the connection management module to reconfigure the network port and related routes for application A so that application A can access the default network of the terminal;

[0122] Step S807, this processing flow ends.

[0123] Example 5:

[0124] like Fig.10 As shown, Fig.10 It is a flowchart of a network slice management method when reapplying for access to a network slice for an application provided by another specific example of the present invention. The network slice management method is applied to a terminal, and the network slice management method includes the following steps:

[0125] Step S901, an application A reenters the foreground;

[0126] Step S902, notifying the recording module to search the network slice application history table to which application A has applied for access;

[0127] Step S903, notifying the network slice management module to apply for network slices from the network side according to the network slice application history table;

[0128] Step S904, notifying the connection management module to configure the network port and related routes for application A so that application A can access the corresponding network slice;

[0129] Step S905, this processing flow ends.

[0130] In addition, an embodiment of the present invention further provides a terminal, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor.

[0131] The processor and the memory may be connected via a bus or other means.

[0132] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0133] It should be noted that the terminal in this embodiment may include: Figure 1 The system architecture platform in the embodiment shown, the terminal in this embodiment and Figure 1 The system architecture platform in the illustrated embodiments belongs to the same inventive concept, and therefore these embodiments have the same implementation principles and technical effects, which will not be described in detail here.

[0134] The non-transient software program and instructions required to implement the network slice management method of the above embodiment are stored in the memory. When executed by the processor, the network slice management method of the above embodiment is executed, for example, the above described Figure 2 Steps S100 to S300, Figure 3 In the method step S210, Figure 4 Steps S211 to S213 of the method, Figure 5 Steps S410 to S420 of the method, Figure 6 Steps S501 to S510 of the method, Figure 7 Steps S601 to S611 of the method, Figure 8 Steps S701 to S707 of the method, Fig. 9 Steps S801 to S807 of the method, Fig.10 Method steps S901 to S905.

[0135] The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0136] In addition, an embodiment of the present invention further provides a computer-readable storage medium, which stores computer-executable instructions, which are executed by a processor or controller, for example, by a processor in the above terminal embodiment, so that the above processor can execute the network slice management method in the above embodiment, for example, execute the above described Figure 2 Steps S100 to S300, Figure 3 In the method step S210, Figure 4 Steps S211 to S213 of the method, Figure 5 Steps S410 to S420 of the method, Figure 6 Steps S501 to S510 of the method, Figure 7 Steps S601 to S611 of the method, Figure 8 Steps S701 to S707 of the method, Fig. 9 Steps S801 to S807 of the method, Fig.10 Method steps S901 to S905.

[0137] It will be appreciated by those skilled in the art that all or some of the steps and systems in the disclosed method above may be implemented as software, firmware, hardware and appropriate combinations thereof. Some physical components 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 may be implemented as hardware, or may be 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 a non-transitory medium) and a communication medium (or a 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 technologies, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that may be used to store desired information and may be accessed by a computer. Furthermore, it is well known to those skilled in the art that communication media typically embodies 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.

[0138] The above is a specific description of the preferred implementation of the present invention, but the present invention is not limited to the above-mentioned implementation mode. Technical personnel familiar with the field can also make various equivalent deformations or substitutions without violating the spirit of the present invention. These equivalent deformations or substitutions are all included in the scope defined by the claims of the present invention.

Claims

1. A network slice management method, comprising: Acquire terminal operation information, wherein the terminal operation information includes application operation status; When the application running state indicates that the corresponding application enters a background running state or is in an abnormal running state, and when the application remains in the background running state or in the abnormal running state for a first period of time, it is determined that the network slice accessed by the application is a network slice to be released; Release the network slice to be released.

2. The method according to claim 1, characterized in that The determining that the network slice accessed by the application is a network slice to be released includes: Determine the network slice to which the application is accessed; When only the application accesses the network slice; Determine that the network slice is a network slice to be released.

3. The method according to claim 1, characterized in that The terminal operation information includes a terminal system status, and the method further includes: When the terminal system status is indicated as the terminal entering a sleep state, it is determined that all network slices accessed by the terminal's applications are network slices to be released.

4. The method according to claim 1, characterized in that: The terminal operation information includes first network quality information corresponding to the network slice and second network quality information corresponding to the terminal default network, and the method further includes: When the second network quality information is better than the first network quality information and lasts for a second period of time, the network slice corresponding to the first network quality information is determined from the network slices accessed by the application of the terminal as the network slice to be released.

5. The method according to any one of claims 1 to 4, characterized in that: Also includes: Switch the application accessing the network slice to be released to the default network of the terminal.

6. The method according to claim 1 or 2, characterized in that: Also includes: When the application exits the background running state or the abnormal running state, apply for access to the network slice for the application again.

7. The method according to claim 6, characterized in that The re-applying for access to the network slice for the application includes: Obtain a network slice application history table for the application; Reapply for access to the network slice for the application according to the network slice application history table.

8. A terminal, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method according to any one of claims 1 to 7 when executing the computer program.

9. A computer-readable storage medium storing computer-executable instructions, wherein the computer-executable instructions are used to execute the method according to any one of claims 1 to 7.

Images