WO2021254096A1 - 网络切片管理方法、终端及计算机可读存储介质 - Google Patents

网络切片管理方法、终端及计算机可读存储介质 Download PDF

Info

Publication number
WO2021254096A1
WO2021254096A1 PCT/CN2021/095285 CN2021095285W WO2021254096A1 WO 2021254096 A1 WO2021254096 A1 WO 2021254096A1 CN 2021095285 W CN2021095285 W CN 2021095285W WO 2021254096 A1 WO2021254096 A1 WO 2021254096A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
network
terminal
network slice
released
Prior art date
Application number
PCT/CN2021/095285
Other languages
English (en)
French (fr)
Inventor
杨海城
屠丁元
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to US17/906,215 priority Critical patent/US20230119027A1/en
Priority to EP21825243.5A priority patent/EP4109823A4/en
Publication of WO2021254096A1 publication Critical patent/WO2021254096A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H04L41/0897—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/38—Connection release triggered by timers

Definitions

  • the embodiments of the present application relate to, but are not limited to, the field of communication technologies, and in particular, to a network slice management method, a terminal, and a computer-readable storage medium.
  • network slicing allows operators to divide multiple virtual end-to-end networks in a hardware infrastructure, and each network slice achieves logical isolation in terms of terminals, access networks, transmission networks, and core networks. , Can adapt to various types of services and meet the different needs of users.
  • the 5G network uses network slicing technology to meet the differentiated requirements of users in terms of priority, billing, policy control, security, and mobility, as well as the differentiated requirements in terms of latency, reliability, and speed.
  • the terminal application 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 operation mode, the application will remain connected to the network.
  • Network slicing connection if the network slicing charging policy is to charge according to the length of use, the user will have to pay a higher cost than the actual length of use, which is not conducive to the user experience.
  • the embodiments of the present application provide a network slice management method, a terminal, and a computer-readable storage medium.
  • an embodiment of the present application provides a network slice management method, including: acquiring terminal operating information; determining, according to the terminal operating information, from the network slices accessed by the terminal application; and releasing the network slice.
  • the network slice is to be released.
  • an embodiment of the present application also provides a terminal, including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor.
  • a terminal including: a memory, a processor, and a computer program stored in the memory and capable of running on the processor.
  • the processor executes the computer program, the above-mentioned The network slice management method described in one aspect.
  • an embodiment of the present application also provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are used to execute the network slice management method described above.
  • FIG. 1 is a schematic diagram of a system architecture platform for executing a network slice management method provided by an embodiment of the present application
  • Figure 2 is a flowchart of a network slice management method provided by an embodiment of the present application.
  • FIG. 3 is a flowchart of a network slice management method provided by another embodiment of the present application.
  • FIG. 4 is a flowchart of a network slice management method provided by another embodiment of the present application.
  • FIG. 5 is a flowchart of a network slice management method provided by another embodiment of the present application.
  • FIG. 6 is a flowchart of a network slice management method provided by another embodiment of the present application.
  • FIG. 7 is a flowchart of a network slice management method provided by another embodiment of the present application.
  • FIG. 8 is a flowchart of a network slice management method provided by another embodiment of the present application.
  • FIG. 9 is a flowchart of a network slice management method provided by another embodiment of the present application.
  • FIG. 10 is a flowchart of a network slice management method provided by another embodiment of the present application.
  • the embodiments of the present application provide 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 operation information of the terminal, for example, it can monitor the operation status of the terminal application and the operation of the terminal system.
  • the terminal can determine the network slice to be released from the network slice accessed by the terminal application based on the terminal’s operating information represented by the terminal’s operating information, for example, determine that the user is not using it temporarily
  • the network slice accessed by the application is the to-be-released network slice; then, the terminal releases the to-be-released network slice to prevent the application that the user does not use temporarily still maintains access to the network slice, so that the network slice can be charged according to the length of use Avoid incurring additional costs, thereby improving the user experience.
  • FIG. 1 is a schematic diagram of a system architecture platform for executing a network slice management method provided by an embodiment of the present application.
  • 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.
  • the recording module 110 is used to record applicants and users of network slicing, such as applications applying for network slicing and applications that use network slicing;
  • the monitoring module 120 is used to monitor whether the running status of each application in the terminal changes, and also To monitor whether the operating status of the terminal system changes, etc.;
  • 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 Network slicing and network quality information of the terminal's default network.
  • the system architecture platform 100 and application scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Those skilled in the art will know that with With the evolution of the system architecture platform and the emergence of new application scenarios, the technical solutions provided in the embodiments of this application are equally applicable to similar technical problems.
  • system architecture platform 100 shown in FIG. 1 does not constitute a limitation to the embodiment of the present application, and may include more or less components than shown in the figure, or a combination of certain components, Or different component arrangements.
  • 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.
  • FIG. 2 is a flowchart of a network slice management method provided by an embodiment of the present application.
  • the network slice management method includes but is not limited to step S100, step S200, and step S300.
  • Step S100 Obtain terminal operation information.
  • the terminal when the terminal is in the 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, and the operation of releasing network slices in the subsequent steps Provide the necessary basic conditions.
  • the terminal operating information is various information that can represent the working condition of the terminal, which may include, but is not limited to, the application operating status of each application in the terminal, the terminal system status of the terminal itself, and the network quality between the terminal and the network. information.
  • each application in the terminal can apply for a corresponding network slice according to actual conditions. 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 respectively access its own network slice, or multiple applications can access a common network slice, which is not specifically limited in this embodiment.
  • the recording module in the terminal can store the applicant or user of the network slice. For example, the recording module can store the application name or application identity of the application connected to the network slice and other related information. So that the terminal can manage network slices and corresponding applications.
  • the terminal when an application applies for access to a 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 Slicing, so that the services provided by the network slicing can be used.
  • PDU Protocol Data Unit
  • Step S200 Determine the network slice to be released from the network slices accessed by the terminal application according to the terminal operating information.
  • the network slice to be released may be a network slice that does not need to be used temporarily or that does not need to be connected temporarily.
  • the network slices to be released that are not currently used or connected temporarily can be determined from the network slices accessed by the terminal application according to the terminal operating information, so that the subsequent steps can be targeted.
  • the release of network slices to be released that do not need to be used or connected temporarily so as to prevent users from maintaining access to network slices for applications that are not currently used, thereby avoiding additional costs when network slices are charged according to the length of use. Improve user experience.
  • the network slice to be released may be determined from the network slice accessed by the terminal application.
  • the terminal operating information includes the application operating status of each application in the terminal, then when the operating status of the application changes and it appears 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 pending release Network slicing.
  • the terminal operating information includes the terminal system status of the terminal itself, when the terminal system status changes and 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 pending release. Network slicing.
  • step S300 the network slice to be released is released.
  • the terminal can be The network slice management module releases the to-be-released network slice, so that additional costs can be avoided when the network slice is charged according to the length of use, and the user experience can be improved.
  • the network slices that are temporarily not used or connected 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, and the terminal can save energy.
  • the terminal can monitor the running status of each application, the running status of the terminal system, and the terminal's network connection quality and other terminal operating information Therefore, it is possible to determine the network slices to be released from the network slices accessed by the terminal application according to the working conditions of the terminal represented by the terminal operating information, and release these network slices to be released in time, so as to prevent users from not needing to use them temporarily.
  • the application still maintains access to the network slice, which can avoid additional costs when the network slice is charged according to the length of use, and improve the user experience.
  • the terminal can release in time the network slices that do not need to be used or do not need to be connected in time Therefore, the problem of high power consumption caused by the continuous connection of the terminal to the network slice can be avoided, and the terminal can save energy.
  • step S200 may include but is not limited to the following steps:
  • Step S210 When the application operating state indicates that the corresponding application enters the background operating state or is in an abnormal operating state, and when the application remains in the background operating state or is in the abnormal operating state for the first period of time, it is determined that the network slice accessed by the application is The network slice is to be released.
  • the application running state indicates that the corresponding application enters the background running state, and the application keeps the background running state for the first period of time, it means that the application entering the background running state is not the user's misoperation, but the user's failure.
  • the problem of high power consumption of the terminal caused by the continuous connection of the network slice by the application can be avoided, which can play a role in energy saving of the terminal .
  • the application running state indicates that the corresponding application is in an abnormal running state
  • the application keeps the abnormal running state for the first period of time
  • 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 application's continuous connection to the network slice can be avoided, thereby saving energy for the terminal. effect.
  • the abnormal running state of the application may include the application being frozen or the application not responding (Application Not Responding, ANR), which is not specifically limited in this embodiment.
  • ANR Application Not Responding
  • the value of the first duration can be appropriately selected according to actual conditions, which is not specifically limited in this embodiment.
  • the setting of the first duration can be achieved by setting a timer or a timer, which is also not specifically limited in this embodiment.
  • determining that the network slice accessed by the application is a network slice to be released in step S210 may include but is not limited to the following steps:
  • Step S211 Determine the network slice accessed by the application
  • Step S212 when the network slice is only accessed by the application
  • Step S213 Determine that the network slice is a network slice to be released.
  • the application when the application enters the background running state or is in an abnormal running state, and the application keeps the background running state or is in the abnormal running state for the first period of time, it is also necessary to determine whether there are other applications connected to the application. The same network slicing. 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, it is released , It will affect the normal use of other apps.
  • the application running state indicates that the corresponding application enters the background running state or is in an abnormal running state, and the application remains in the background running state or in the abnormal running state for the first period of time, all the applications accessed from the terminal In network slicing, it is determined that only the network slice accessed by the application is the network slice to be released. Therefore, when the network slice to be released is released in the subsequent steps, not only can it not affect the normal use of other applications, but it can also be used in the network slice. Avoid additional costs while charging according to the length of use, and improve the user experience.
  • the application can be switched to the terminal’s default network to avoid additional costs when the network slicing is charged according to the length of use, thereby improving the user experience .
  • step S200 may also include but is not limited to the following steps:
  • the terminal system state indicates that the terminal enters the dormant state, it is determined that all network slices accessed by the terminal application are network slices to be released.
  • the terminal system state indicates that the terminal enters the dormant state, it means 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. Therefore, each application in the terminal can be connected to it. All incoming network slices are determined to be network slices to be released, so that the network slices to be released can be released in subsequent steps, so that additional costs can be avoided when the network slices are charged according to the length of use, and the user experience can be improved.
  • the terminal since the terminal enters the sleep state, that is, the terminal enters the 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's continuous connection to the network slice can be avoided, thereby enabling To the role of terminal energy saving.
  • step S200 may also include but is not limited to the following steps:
  • the network slice corresponding to the first network quality information is determined as the network slice to be released from the network slices accessed by the terminal application.
  • the monitoring module in the terminal monitors the network quality information between the terminal and the network, for example, monitors the second network quality information between the terminal and the terminal’s default network, where the terminal defaults to The network is determined according to the standard supported by the terminal and the default standard set by the user.
  • the standard supported by the terminal includes 3G network, 4G network and 5G network, and the default standard set by the user is 4G network, then the terminal The default network is the 4G network.
  • the monitoring module will also monitor the first network quality information between the terminal and the network slice.
  • the second network quality information When the second network quality information is better than the first network quality information for a second period of time, it indicates that the connection quality between the terminal and the network slice is relatively poor. If the application is still connected to the network slice, it may affect the user experience , Which is specifically reflected in the situation of low network transmission speed, disconnection, failure to access the network, etc.
  • the network slice is a 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 users, after the network slice to be released is released, the application can be switched and connected to the terminal
  • the default network can avoid additional costs when the network slice is charged according to the length of use while ensuring the normal use of the application by the user, thereby improving the user experience.
  • both the first network quality information and the second network quality information may include, but are not limited to, performance indicators such as time delay, reliability, and speed.
  • the quality of the first network can be judged through overall analysis of various performance indicators. The degree of superiority or inferiority between the information and the second network quality information, thereby providing basic conditions for whether to perform the subsequent operation of releasing the network slice.
  • the value of the second duration can be appropriately selected according to actual conditions, which is not specifically limited in this embodiment.
  • the setting of the second duration can be achieved by setting a timer or a timer, which is also not specifically limited in this embodiment.
  • the network slice management method may further include but is not limited to the following steps:
  • the access to the network slice can be The application that releases the network slice is switched to the terminal default network, and the terminal default network is used to carry the service data of the application, thereby ensuring that the application can normally provide services to the user. It is worth noting that when the step of switching the application that accesses the network slice to be released to the default network of the terminal is performed in this embodiment, the connection management module in the terminal will reconfigure the network port and related routing for the application. This enables the application to access the default network of the terminal.
  • the step of switching the application accessing the network slice to be released to the default network of the terminal may have different execution timings. For example, it may be executed before step S300 in the above-mentioned embodiment, or may be different from step S300. S300 is executed synchronously, which is not specifically limited in this embodiment.
  • the step of switching the application accessing the network slice to be released to the terminal default network in this embodiment is performed before step S300, the network slice to be released and the terminal default network can carry the service data of the application at the same time, and when the step is performed When the to-be-released network slice is released in the S300, the normal use of the application is not affected, and the effect of seamless switching of the network carrying the service data of the application is achieved.
  • step S300 when the step of switching and accessing the application that accesses the network slice to be released to the default network of the terminal in this embodiment is performed synchronously with step S300, the application can also be kept in the process of switching the network that carries the service data of the application. Provide services to users normally, so as to avoid affecting users' experience.
  • the network slice management method may further include but is not limited to the following steps:
  • the application when the application exits the background running state, it indicates that the user is currently using the application. Therefore, the application can be re-applied for access to the network slice, so that the application can provide the user with 5G network services.
  • the application exits the abnormal running state it indicates that the application resumes normal work and can continue to provide services to users. Therefore, the application can be re-applied for access to network slices so that the application can provide users with 5G network services.
  • the network slice management module in the terminal will first apply to the network for the network slice for the application, and then the connection management module in the terminal will reconfigure the network port for the application And related routing, so that the application can access the applied network slice.
  • reapplying for access to the network slice for the application includes but not limited to the following steps:
  • Step S410 Obtain an application history table for network slicing
  • Step S420 Reapply for access to the network slice for the application according to the network slice application history table.
  • the recording module in the terminal saves the applicant or user of the network slice, for example, saves the application name or application identity of the application connected to the network slice, etc.
  • the recording module can establish a network slice application history table according to the network slices successfully accessed by the application, which not only facilitates the management of network slices, but also facilitates subsequent operations of re-applying for network slices.
  • the network slice application history table since the network slice application history table records the relevant information of the network slice that each application in the terminal has applied for access and information about the applicant or user of the network slice, it is necessary to reapply for the application.
  • the network slicing application history table maintained by the recording module can be used to reapply for network slicing for the application, thereby improving the efficiency of applying for network slicing.
  • you need to reapply for network slice access for an application you can first search the record module for the network slice application history table that the application has applied for, and then control the network slice management module according to the network slice.
  • the slice application history table is for the application to apply to the network for access to the network slice.
  • FIG. 6 is a flowchart of a network slice management method for a single application provided by a specific example of the present application.
  • the network slice management method is applied to a terminal, and the network slice management method includes the following steps:
  • Step S501 an application A accesses the network slice NS1, and establishes a PDU session between the terminal and the 5G network;
  • Step S502 notify the recording module to record the applicant or user of the network slice NS1;
  • Step S503 informing the monitoring module to monitor changes in the status of each application
  • Step S504 when the monitoring module detects that application A is switched to the background by the user;
  • Step S505 notify the network slice management module to start the timer Timer A;
  • Step S506 Determine whether the application A is switched to the foreground before the timer Timer A reaches the preset time; if not, perform step S507; if yes, perform step S509;
  • Step S507 notify the network slice management module to release the network slice NS1;
  • Step S508 Notify the connection management module to reconfigure the network port and related routing for application A, so that application A accesses the terminal's default network;
  • Step S509 notify the network slice management module to stop the timer Timer A;
  • Step S510 the processing flow this time ends.
  • FIG. 7 is a flowchart of a network slice management method for multiple applications provided by another specific example of the present application.
  • the network slice management method is applied to a terminal, and the network slice management method includes the following steps:
  • Step S601 an application A accesses the network slice NS1, and establishes a PDU session between the terminal and the 5G network;
  • Step S602 notify the recording module to record the applicant or user of the network slice NS1;
  • Step S603 Notify the monitoring module to monitor changes in the status of each application
  • Step S604 when the monitoring module detects that application A is switched to the background by the user;
  • Step S605 notify the network slice management module to start a timer Timer A;
  • Step S606 Determine whether the application A is switched to the foreground before the timer Timer A reaches the preset time; if not, perform step S607; if yes, perform step S610;
  • Step S607 it is judged whether there are other applications using the network slice NS1, if not, go to step S608; if yes, go to step S609;
  • Step S608 notify the network slice management module to release the network slice NS1;
  • step S609 the connection management module is notified to reconfigure the network port and related routing for application A, so that application A can access the default network of the terminal;
  • Step S610 notify the network slice management module to stop the timer Timer A;
  • Step S611 the processing flow this time ends.
  • FIG. 8 is a flowchart of a network slice management method for a terminal system state provided by another specific example of the present application.
  • the network slice management method is applied to a terminal, and the network slice management method includes the following steps:
  • Step S701 an application A accesses the network slice NS1, and establishes a PDU session between the terminal and the 5G network;
  • Step S702 notify the recording module to record the applicant or user of the network slice NS1;
  • Step S703 informing the monitoring module to monitor the status change of the terminal system
  • Step S704 when the monitoring module monitors that the terminal enters a dormant state
  • Step S705 notify the network slice management module to release the network slice NS1;
  • Step S706 Notify the connection management module to reconfigure the network port and related routing for application A, so that application A accesses the default network of the terminal;
  • Step S707 the processing flow this time ends.
  • FIG. 9 is a flowchart of a network slice management method for network connection quality provided by another specific example of the present application.
  • the network slice management method is applied to a terminal, and the network slice management method includes the following steps:
  • Step S801 an application A accesses the network slice NS1, and establishes a PDU session between the terminal and the 5G network;
  • Step S802 notify the recording module to record the applicant or user of the network slice NS1;
  • Step S803 informing the monitoring module to monitor the network connection quality of the network slice NS1 and the terminal default network in real time;
  • 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's default network, and continues for a period of time;
  • Step S805 notify the network slice management module to release the network slice NS1;
  • Step S806 Notify the connection management module to reconfigure the network port and related routing for application A, so that application A accesses the default network of the terminal;
  • Step S807 the processing flow this time ends.
  • FIG. 10 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 application.
  • the network slice management method is applied to a terminal, and the network slice management method Including the following steps:
  • Step S901 a certain application A re-enters the foreground
  • Step S902 Notify the recording module to look up the network slice application history table that application A has applied for access;
  • 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
  • Step S904 Notify the connection management module to configure the network port and related routing for application A, so that application A can access the corresponding network slice;
  • Step S905 the processing flow this time ends.
  • an embodiment of the present application also provides a terminal.
  • the terminal includes a memory, a processor, and a computer program stored on the memory and running on the processor.
  • the processor and the memory can be connected by a bus or in other ways.
  • the memory can be used to store non-transitory software programs and non-transitory computer-executable programs.
  • the memory may include a high-speed random access memory, and may also include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state storage devices.
  • the memory may include a memory remotely arranged with respect to the processor, and these remote memories may be connected to the processor through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
  • the terminal in this embodiment may include the system architecture platform in the embodiment shown in FIG. 1.
  • the terminal in this embodiment and the system architecture platform in the embodiment shown in FIG. 1 belong to the same invention. It is conceived that these embodiments have the same implementation principles and technical effects, which will not be described in detail here.
  • the non-transitory software programs and instructions required to implement the network slice management method of the above embodiment are stored in the memory.
  • the network slice management method in the above embodiment is executed, for example, the above-described FIG. 2 is executed.
  • 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 they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • an embodiment of the present application also provides a computer-readable storage medium that stores computer-executable instructions, and the computer-executable instructions are executed by a processor or a controller, for example, by the aforementioned
  • the execution of a processor in the terminal embodiment can make the above-mentioned processor execute the network slice management method in the above-mentioned embodiment, for example, execute the method steps S100 to S300 in FIG. 2 described above, and the method steps S210 in FIG. 3
  • the embodiments of the present application include: the terminal obtains terminal operation information, determines the network slice to be released from the network slices accessed by the terminal application according to the terminal operation information, and then releases the network slice to be released.
  • the terminal obtains terminal operation information, determines the network slice to be released from the network slices accessed by the terminal application according to the terminal operation information, and then releases the network slice to be released.
  • the terminal by obtaining terminal operating information, it is possible to monitor the operating information of the terminal, for example, the operating status of the terminal’s application, the operating status of the terminal system, and the quality of the terminal’s network connection and other related information can be monitored; and according to the terminal
  • the working status of the terminal represented by the running information can be determined from the network slices to be released from the network slices accessed by the terminal's applications.
  • the network slices accessed by the applications not used by the user are the network slices to be released; then release
  • the to-be-released network slice prevents applications that the user does not use temporarily and still maintains access to the network slice, thereby avoiding additional costs when the network slice is charged according to the length of use, thereby improving the user experience.
  • Computer storage medium includes volatile and non-volatile data implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data).
  • 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 disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or Any other medium used to store desired information and that can be accessed by a computer.
  • a communication medium usually contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种网络切片管理方法、终端及计算机可读存储介质。其中，网络切片管理方法包括：获取终端运行信息(S100)，根据终端运行信息从终端的应用所接入的网络切片中确定待释放网络切片(S200)，释放待释放网络切片(S300)。

Description

网络切片管理方法、终端及计算机可读存储介质
相关申请的交叉引用
本申请基于申请号为202010564658.0、申请日为2020年06月19日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及但不限于通信技术领域，尤其涉及一种网络切片管理方法、终端及计算机可读存储介质。
背景技术
网络切片作为5G网络的重要技术，可以让运营商在一个硬件基础设施中划分出多个虚拟的端到端网络，每个网络切片在终端、接入网、传输网以及核心网方面实现逻辑隔离，能够适配各种类型服务并满足用户的不同需求。5G网络通过网络切片技术满足了用户在优先级、计费、策略控制、安全和移动性等功能方面的差异化需求，以及在时延、可靠性、速率等性能方面的差异化需求。
为了满足用户对5G网络的使用需求，当终端的应用接入了网络切片后，只要用户不关闭该应用，即使用户暂不使用该应用而把该应用切换至后台运行模式，该应用都会保持与网络切片的连接。然而，针对上述应用场景，如果网络切片的计费策略为按照使用时长收费，则会导致用户需要付出比实际使用时长更高的费用，从而不利于用户的使用体验。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求的保护范围。
本申请实施例提供了一种网络切片管理方法、终端及计算机可读存储介质。
第一方面，本申请实施例提供了一种网络切片管理方法，包括：获取终端运行信息；根据所述终端运行信息从终端的应用所接入的网络切片中确定待释放网络切片；释放所述待释放网络切片。
第二方面，本申请实施例还提供了一种终端，包括：存储器、处理器及 存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如上第一方面所述的网络切片管理方法。
第三方面，本申请实施例还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行如上所述的网络切片管理方法。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本申请技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本申请的技术方案，并不构成对本申请技术方案的限制。
图1是本申请一个实施例提供的用于执行网络切片管理方法的系统架构平台的示意图；
图2是本申请一个实施例提供的网络切片管理方法的流程图；
图3是本申请另一实施例提供的网络切片管理方法的流程图；
图4是本申请另一实施例提供的网络切片管理方法的流程图；
图5是本申请另一实施例提供的网络切片管理方法的流程图；
图6是本申请另一实施例提供的网络切片管理方法的流程图；
图7是本申请另一实施例提供的网络切片管理方法的流程图；
图8是本申请另一实施例提供的网络切片管理方法的流程图；
图9是本申请另一实施例提供的网络切片管理方法的流程图；
图10是本申请另一实施例提供的网络切片管理方法的流程图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。
需要说明的是，虽然在装置示意图中进行了功能模块划分，在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于装置中的模块划分，或流程图中的顺序执行所示出或描述的步骤。说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请实施例提供了一种网络切片管理方法、终端及计算机可读存储介 质，终端获取自身的终端运行信息，可以监控终端的运行信息，例如可以监控终端的应用的运行状态、终端系统的运行状态以及终端的网络连接质量等相关信息；接着，终端根据终端运行信息所表现的终端的工作情况，可以从终端的应用所接入的网络切片中确定待释放网络切片，例如确定用户暂不使用的应用所接入的网络切片为待释放网络切片；然后，终端释放该待释放网络切片，避免用户暂不使用的应用仍然维持接入网络切片，从而能够在网络切片按照使用时长收费的情况下避免产生额外费用，从而提高用户的使用体验。
下面结合附图，对本申请实施例作进一步阐述。
如图1所示，图1是本申请一个实施例提供的用于执行网络切片管理方法的系统架构平台的示意图。在图1的示例中，该系统架构平台100包括记录模块110、监听模块120、网络切片管理模块130、连接管理模块140和监测模块150。其中，记录模块110用于记录网络切片的申请者及使用者，例如申请网络切片的应用和使用网络切片的应用；监听模块120既用于监听终端中各应用的运行状态是否发生变化，也用于监听终端系统的运行状态是否发生变化等；网络切片管理模块130用于申请、维持及释放网络切片；连接管理模块140用于为各应用配置相关的网口及路由；监测模块150用于监测网络切片及终端默认网络的网络质量信息。
本申请实施例描述的系统架构平台100以及应用场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域技术人员可知，随着系统架构平台的演变和新应用场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本领域技术人员可以理解的是，图1中示出的系统架构平台100的结构并不构成对本申请实施例的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
在图1所示的系统架构平台100中，记录模块110、监听模块120、网络切片管理模块130、连接管理模块140和监测模块150之间可以配合执行网络切片管理方法。
基于上述系统架构平台的结构，提出本申请的网络切片管理方法的各个实施例。
如图2所示，图2是本申请一个实施例提供的网络切片管理方法的流程图，该网络切片管理方法包括但不限于有步骤S100、步骤S200和步骤S300。
步骤S100，获取终端运行信息。
在一实施例中，当终端处于工作状态时，终端可以获取终端运行信息， 例如通过终端中的监听模块获取终端运行信息，从而可以监控终端的运行信息，为后续步骤中的释放网络切片的操作提供必要的基础条件。
在一实施例中，终端运行信息为能够表现终端的工作情况的各种信息，可以包括但不限于终端中各应用的应用运行状态、终端自身的终端系统状态和终端与网络之间的网络质量信息。
值得注意的是，在执行步骤S100之前，终端中的各应用可以根据实际情况而申请对应的网络切片。例如，当用户打开一个需要从网络获取数据信息的应用时，该应用会申请对应的网络切片。视实际情况而定，终端中的每一个应用可以分别接入专属于其的网络切片，也可以多个应用共同接入一个公共的网络切片，本实施例对此并不作具体限定。此外，当应用接入网络切片之后，终端中的记录模块可以保存网络切片的申请者或使用者，例如，记录模块可以保存接入到网络切片的应用的应用名称或应用身份标识等相关信息，以便于终端对网络切片及对应的应用进行管理。另外，当应用申请接入网络切片时，终端会与5G网络建立协议数据单元(Protocol Data Unit，PDU)会话，当终端与5G网络建立了PDU会话后，对应的应用将可以接入对应的网络切片，从而可以使用该网络切片所提供的服务。
步骤S200，根据终端运行信息从终端的应用所接入的网络切片中确定待释放网络切片。
在一实施例中，待释放网络切片可以为暂不需要使用或者暂不需要连接的网络切片。当获取到终端运行信息后，可以根据终端运行信息从终端的应用所接入的网络切片中，确定当前暂不需要使用或者暂不需要连接的待释放网络切片，从而可以在后续步骤中针对性的释放暂不需要使用或者暂不需要连接的待释放网络切片，避免用户当前暂不使用的应用仍然维持接入网络切片，从而能够在网络切片按照使用时长收费的情况下避免产生额外费用，从而提高用户的使用体验。
在一实施例中，根据终端运行信息的具体内容的不同，从终端的应用所接入的网络切片中确定待释放网络切片，可以有不同的实施方式，本实施例对此并不作具体限定。例如，当终端运行信息包括终端中各应用的应用运行状态，那么，在应用运行状态发生改变并表现为用户暂不需要使用对应的应用时，可以确定该应用所接入的网络切片为待释放网络切片。又如，当终端运行信息包括终端自身的终端系统状态，那么，在终端系统状态发生改变并表现为用户暂不需要使用终端时，可以确定终端当前所维持接入的所有网络切片均为待释放网络切片。
步骤S300，释放待释放网络切片。
在一实施例中，当从终端的应用所接入的网络切片中确定待释放网络切片后，为了避免用户暂不使用的应用仍然维持接入网络切片而导致产生额外费用，可以通过终端中的网络切片管理模块释放该待释放网络切片，从而能够在网络切片按照使用时长收费的情况下避免产生额外费用，提高用户的使用体验。此外，由于能够及时释放暂不需要使用或者暂不需要连接的网络切片，因此可以避免终端持续连接网络切片而造成的功耗大的问题，从而能够起到终端节能的作用。
在一实施例中，通过采用包括有上述步骤S100、步骤S200和步骤S300的网络切片管理方法，使得终端可以监控各个应用的运行状态、终端系统的运行状态以及终端的网络连接质量等终端运行信息，从而可以根据这些终端运行信息所表现的终端的工作情况，从终端的应用所接入的网络切片中确定待释放网络切片，并及时释放这些待释放网络切片，从而可以避免用户暂不需要使用的应用仍然维持接入网络切片，能够在网络切片按照使用时长收费的情况下避免产生额外费用，提高用户的使用体验，此外，由于终端能够及时释放暂不需要使用或者暂不需要连接的网络切片，因此可以避免终端持续连接网络切片而造成的功耗大的问题，从而能够起到终端节能的作用。
另外，在一实施例中，参照图3，当终端运行信息包括应用运行状态，步骤S200可以包括但不限于有以下步骤：
步骤S210，当应用运行状态表示为对应的应用进入后台运行状态或处于异常运行状态，且当该应用保持后台运行状态或处于异常运行状态持续第一时长，确定该应用所接入的网络切片为待释放网络切片。
在一实施例中，当应用运行状态表示为对应的应用进入后台运行状态，并且该应用保持后台运行状态持续第一时长，说明该应用进入后台运行状态并不是用户的误操作，而是用户出于目前暂不需要使用该应用的目的而将该应用切换至后台运行状态，即，用户明确表达出了目前暂不需要使用该应用的意图，因此，可以将该应用所接入的网络切片确定为待释放网络切片，以便于后续步骤中可以释放该待释放网络切片，从而能够在网络切片按照使用时长收费的情况下避免产生额外费用，提高用户的使用体验。此外，由于用户目前暂不需要使用该应用，因此，通过释放该应用所接入的网络切片，可以避免该应用持续连接网络切片而造成终端功耗大的问题，从而能够起到终端节能的作用。
在一实施例中，当应用运行状态表示为对应的应用处于异常运行状态，并且该应用保持异常运行状态持续第一时长，说明该应用处于不能在短时间内自行恢复的异常状态，该应用不能够在短时间内重新为用户提供服务，如 果该应用仍然接入网络切片，则会造成用户付出了费用而得不到相应服务的问题，因此，可以将该应用所接入的网络切片确定为待释放网络切片，以便于后续步骤中可以释放该待释放网络切片，从而能够在网络切片按照使用时长收费的情况下避免产生额外费用，提高用户的使用体验。此外，由于该应用不能够正常为用户提供服务，因此，通过释放该应用所接入的网络切片，可以避免该应用持续连接网络切片而造成终端功耗大的问题，从而能够起到终端节能的作用。
在一实施例中，应用的异常运行状态可以包括应用被冻结或者应用出现应用程序无响应(Application Not Responding，ANR)等状态，本实施例对此并不作具体限定。
在一实施例中，第一时长的取值可以根据实际情况而进行适当的选择，本实施例对此并不作具体限定。另外，第一时长的设定可以通过设置定时器或者计时器而实现，本实施例对此同样不作具体限定。
另外，在一实施例中，参照图4，步骤S210中的确定该应用所接入的网络切片为待释放网络切片，可以包括但不限于有以下步骤：
步骤S211，确定该应用所接入的网络切片；
步骤S212，当该网络切片仅有该应用接入；
步骤S213，确定该网络切片为待释放网络切片。
在一实施例中，当应用进入后台运行状态或处于异常运行状态，并且该应用保持后台运行状态或处于异常运行状态持续了第一时长，则还需要判断是否还有其他应用和该应用接入了同样的网络切片。如果还有其他应用也接入了该应用所接入的网络切片，则不能把该应用所接入的网络切片确定为待释放网络切片，如果该网络切片被确定为待释放网络切片而被释放，则会影响其他应用的正常使用。因此，在应用运行状态表示为对应的应用进入后台运行状态或处于异常运行状态，并且在该应用保持后台运行状态或处于异常运行状态持续第一时长的情况下，从终端各个应用所接入的网络切片中，确定仅有该应用接入的网络切片为待释放网络切片，所以，在后续步骤中把该待释放网络切片释放时，不仅能够不影响其他应用的正常使用，还能够在网络切片按照使用时长收费的情况下避免产生额外费用，提高用户的使用体验。
值得注意的是，在还有其他应用也接入了该应用所接入的网络切片的情况下，由于该应用保持后台运行状态或处于异常运行状态持续了第一时长，如果仍然维持该应用接入网络切片，则会造成产生额外费用的问题，因此，可以将该应用切换接入到终端的默认网络，避免在网络切片按照使用时长收费的情况下产生额外费用，从而可以提高用户的使用体验。
另外，在一实施例中，当终端运行信息包括终端系统状态，步骤S200还可以包括但不限于有以下步骤：
当终端系统状态表示为终端进入休眠状态，确定终端的应用所接入的所有网络切片均为待释放网络切片。
在一实施例中，当终端系统状态表示为终端进入休眠状态，说明用户当前暂不使用终端，即用户当前暂不需要终端中的应用为其提供服务，因此，可以将终端中各个应用所接入的所有网络切片均确定为待释放网络切片，以便于后续步骤中可以释放该待释放网络切片，从而能够在网络切片按照使用时长收费的情况下避免产生额外费用，提高用户的使用体验。此外，由于终端进入了休眠状态，即终端进入了省电模式，因此，通过释放该应用所接入的网络切片，可以避免该应用持续连接网络切片而造成终端功耗大的问题，从而能够起到终端节能的作用。
另外，在一实施例中，当终端运行信息包括与网络切片对应的第一网络质量信息和与终端默认网络对应的第二网络质量信息，步骤S200还可以包括但不限于有以下步骤：
当第二网络质量信息优于第一网络质量信息并持续第二时长，从终端的应用所接入的网络切片中确定与第一网络质量信息对应的网络切片为待释放网络切片。
在一实施例中，当终端接入网络后，终端中的监测模块会监测终端与网络之间的网络质量信息，例如监测终端与终端默认网络之间的第二网络质量信息，其中，终端默认网络根据终端所支持的制式以及用户所设定的默认制式而决定，例如，终端所支持的制式包括3G网络、4G网络和5G网络，而用户所设定的默认制式为4G网络，那么，终端默认网络即为4G网络。另外，当终端中的应用接入网络切片后，监测模块也会监测终端与网络切片之间的第一网络质量信息。当第二网络质量信息优于第一网络质量信息并持续第二时长，说明终端当前与网络切片之间的连接质量比较差，如果仍然保持应用接入网络切片，则可能会影响用户的使用体验，具体体现在网络传输速度低、掉线、访问网络失败等情况，因此，为了避免影响用户对应用的使用体验，从终端的应用所接入的网络切片中确定与第一网络质量信息对应的网络切片为待释放网络切片，以便于后续步骤中可以释放该待释放网络切片；而为了能够保证用户对应用的正常使用，在释放该待释放网络切片后，可以把该应用切换接入到终端默认网络，以在保证用户对应用的正常使用的情况下，能够在网络切片按照使用时长收费的情况下避免产生额外费用，从而提高用户的使用体验。
在一实施例中，第一网络质量信息和第二网络质量信息均可以包括但不限于有时延、可靠性和速率等性能指标，可以通过对各种性能指标的整体分析而判断第一网络质量信息和第二网络质量信息之间的优劣程度，从而为后续是否执行释放网络切片的操作提供基础条件。
在一实施例中，第二时长的取值可以根据实际情况而进行适当的选择，本实施例对此并不作具体限定。另外，第二时长的设定可以通过设置定时器或者计时器而实现，本实施例对此同样不作具体限定。
另外，在一实施例中，该网络切片管理方法还可以包括但不限于有以下步骤：
把接入待释放网络切片的应用切换接入到终端默认网络。
在一实施例中，当根据终端运行信息从终端的应用所接入的网络切片中确定待释放网络切片之后，为了避免影响接入该待释放网络切片的应用的正常使用，可以把接入待释放网络切片的应用切换接入到终端默认网络，利用终端默认网络承载该应用的业务数据，从而可以保证该应用能够正常为用户提供服务。值得注意的是，当执行本实施例中的把接入待释放网络切片的应用切换接入到终端默认网络的步骤时，终端中的连接管理模块会为该应用重新配置网口以及相关路由，使得该应用能够接入到终端默认网络。
在一实施例中，把接入待释放网络切片的应用切换接入到终端默认网络的步骤，可以有不同的执行时机，例如，可以在上述实施例中的步骤S300之前执行，也可以与步骤S300同步执行，本实施例对此并不作具体限定。当本实施例的把接入待释放网络切片的应用切换接入到终端默认网络的步骤在步骤S300之前执行，待释放网络切片和终端默认网络可以同时承载该应用的业务数据，而当执行步骤S300中的释放待释放网络切片时，能够不影响该应用的正常使用，达到无缝切换承载该应用的业务数据的网络的效果。而当本实施例的把接入待释放网络切片的应用切换接入到终端默认网络的步骤与步骤S300同步执行，也可以在切换承载该应用的业务数据的网络的过程中，保持该应用能够正常为用户提供服务，从而避免影响用户的使用体验。
另外，在一实施例中，在应用进入后台运行状态或处于异常运行状态而导致该应用所接入的网络切片被释放的情况下，该网络切片管理方法还可以包括但不限于有以下步骤：
当应用退出后台运行状态或退出异常运行状态，重新为应用申请接入网络切片。
在一实施例中，在应用退出后台运行状态的情况下，说明用户当前正在使用该应用，因此，可以重新为该应用申请接入网络切片，使得该应用能够 为用户提供5G网络服务。而在应用退出异常运行状态的情况下，说明该应用恢复正常工作，可以继续为用户提供服务，因此，可以重新为该应用申请接入网络切片，使得该应用能够为用户提供5G网络服务。
值得注意的是，当重新为应用申请接入网络切片时，终端中的网络切片管理模块会先向网络为该应用申请网络切片，然后，终端中的连接管理模块会为该应用重新配置网口以及相关路由，使得该应用能够接入到所申请到的网络切片。
另外，在一实施例中，参照图5，重新为应用申请接入网络切片，包括但不限于有以下步骤：
步骤S410，获取应用的网络切片申请历史表；
步骤S420，根据网络切片申请历史表为应用重新申请接入网络切片。
在一实施例中，当应用成功接入网络切片后，由于终端中的记录模块会保存网络切片的申请者或使用者，例如，保存接入到网络切片的应用的应用名称或应用身份标识等相关信息，因此，记录模块可以根据应用所成功接入的网络切片建立网络切片申请历史表，不仅可以便于对网络切片的管理，还可以为后续的重新申请网络切片的操作提供便利。
在一实施例中，由于网络切片申请历史表中记录有终端中各个应用曾经申请接入过的网络切片的相关信息以及网络切片的申请者或使用者等信息，因此，当需要为应用重新申请接入网络切片时，可以利用记录模块所维护的网络切片申请历史表为该应用重新申请接入网络切片，从而可以提高申请网络切片的效率。以一个具体示例进行说明，当需要为应用重新申请接入网络切片时，可以先在记录模块中查找该应用曾经申请接入过的网络切片申请历史表，接着，控制网络切片管理模块根据该网络切片申请历史表为该应用向网络申请接入网络切片。
值得注意的是，在根据网络切片申请历史表为应用重新申请接入网络切片时，可以在网络切片申请历史表中按序选择曾经接入过的网络切片的相关信息而向网络申请对应的网络切片，也可以先在网络切片申请历史表中选择合适该应用当前的传输质量要求的网络切片的相关信息，而后向网络申请对应的网络切片，本实施例对此并不作具体限定。
为了更加清楚的说明上述各个实施例中网络切片管理方法的具体步骤流程，下面以具体的示例进行说明。
示例一：
如图6所示，图6是本申请一个具体示例所提供的针对单个应用的网络切片管理方法的流程图，该网络切片管理方法应用于终端，该网络切片管理 方法包括如下步骤：
步骤S501，某应用A接入网络切片NS1，并建立终端与5G网络之间的PDU会话；
步骤S502，通知记录模块记录该网络切片NS1的申请者或使用者；
步骤S503，通知监听模块监听各应用的状态变化；
步骤S504，当监听模块监听到应用A被用户切换到后台；
步骤S505，通知网络切片管理模块启动定时器Timer A；
步骤S506，判断定时器Timer A到达预设时间前，应用A是否被切换到前台，若否，执行步骤S507；若是，执行步骤S509；
步骤S507，通知网络切片管理模块释放网络切片NS1；
步骤S508，通知连接管理模块为应用A重新配置网口及相关路由，使得应用A接入到终端默认网络；
步骤S509，通知网络切片管理模块停止定时器Timer A；
步骤S510，本次处理流程结束。
示例二：
如图7所示，图7是本申请另一个具体示例所提供的针对多个应用的网络切片管理方法的流程图，该网络切片管理方法应用于终端，该网络切片管理方法包括如下步骤：
步骤S601，某应用A接入网络切片NS1，并建立终端与5G网络之间的PDU会话；
步骤S602，通知记录模块记录该网络切片NS1的申请者或使用者；
步骤S603，通知监听模块监听各应用的状态变化；
步骤S604，当监听模块监听到应用A被用户切换到后台；
步骤S605，通知网络切片管理模块启动定时器Timer A；
步骤S606，判断定时器Timer A到达预设时间前，应用A是否被切换到前台，若否，执行步骤S607；若是，执行步骤S610；
步骤S607，判断是否有其它应用在使用网络切片NS1，若否，执行步骤S608；若是，执行步骤步骤S609；
步骤S608，通知网络切片管理模块释放网络切片NS1；
步骤S609，通知连接管理模块为应用A重新配置网口及相关路由，使得应用A接入到终端默认网络；
步骤S610，通知网络切片管理模块停止定时器Timer A；
步骤S611，本次处理流程结束。
示例三：
如图8所示，图8是本申请另一个具体示例所提供的针对终端系统状态的网络切片管理方法的流程图，该网络切片管理方法应用于终端，该网络切片管理方法包括如下步骤：
步骤S701，某应用A接入网络切片NS1，并建立终端与5G网络之间的PDU会话；
步骤S702，通知记录模块记录该网络切片NS1的申请者或使用者；
步骤S703，通知监听模块监听终端系统的状态变化；
步骤S704，当监听模块监听到终端进入休眠状态；
步骤S705，通知网络切片管理模块释放网络切片NS1；
步骤S706，通知连接管理模块为应用A重新配置网口及相关路由，使得应用A接入到终端默认网络；
步骤S707，本次处理流程结束。
示例四：
如图9所示，图9是本申请另一个具体示例所提供的针对网络连接质量的网络切片管理方法的流程图，该网络切片管理方法应用于终端，该网络切片管理方法包括如下步骤：
步骤S801，某应用A接入网络切片NS1，并建立终端与5G网络之间的PDU会话；
步骤S802，通知记录模块记录该网络切片NS1的申请者或使用者；
步骤S803，通知监测模块实时监测网络切片NS1及终端默认网络的网络连接质量；
步骤S804，当监测模块监测到网络切片NS1的网络连接质量低于终端默认网络的网络连接质量，并持续了一段时间；
步骤S805，通知网络切片管理模块释放网络切片NS1；
步骤S806，通知连接管理模块为应用A重新配置网口及相关路由，使得应用A接入到终端默认网络；
步骤S807，本次处理流程结束。
示例五：
如图10所示，图10是本申请另一个具体示例所提供的重新为应用申请接入网络切片时的网络切片管理方法的流程图，该网络切片管理方法应用于终端，该网络切片管理方法包括如下步骤：
步骤S901，某应用A重新进入前台；
步骤S902，通知记录模块查找应用A曾经申请接入过的网络切片申请历史表；
步骤S903，通知网络切片管理模块根据该网络切片申请历史表，向网络侧申请网络切片；
步骤S904，通知连接管理模块为应用A配置网口及相关路由，使得应用A接入到对应的网络切片；
步骤S905，本次处理流程结束。
另外，本申请的一个实施例还提供了一种终端，该终端包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序。
处理器和存储器可以通过总线或者其他方式连接。
存储器作为一种非暂态计算机可读存储介质，可用于存储非暂态软件程序以及非暂态性计算机可执行程序。此外，存储器可以包括高速随机存取存储器，还可以包括非暂态存储器，例如至少一个磁盘存储器件、闪存器件、或其他非暂态固态存储器件。在一些实施方式中，存储器可能包括相对于处理器远程设置的存储器，这些远程存储器可以通过网络连接至该处理器。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
需要说明的是，本实施例中的终端，可以包括有如图1所示实施例中的系统架构平台，本实施例中的终端和如图1所示实施例中的系统架构平台属于相同的发明构思，因此这些实施例具有相同的实现原理以及技术效果，此处不再详述。
实现上述实施例的网络切片管理方法所需的非暂态软件程序以及指令存储在存储器中，当被处理器执行时，执行上述实施例中的网络切片管理方法，例如，执行以上描述的图2中的方法步骤S100至S300、图3中的方法步骤S210、图4中的方法步骤S211至步骤S213、图5中的方法步骤S410至步骤S420、图6中的方法步骤S501至步骤S510、图7中的方法步骤S601至步骤S611、图8中的方法步骤S701至步骤S707、图9中的方法步骤S801至步骤S807、图10中的方法步骤S901至步骤S905。
以上所描述的装置实施例仅仅是示意性的，其中作为分离部件说明的单元可以是或者也可以不是物理上分开的，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本实施例方案的目的。
此外，本申请的一个实施例还提供了一种计算机可读存储介质，该计算机可读存储介质存储有计算机可执行指令，该计算机可执行指令被一个处理器或控制器执行，例如，被上述终端实施例中的一个处理器执行，可使得上述处理器执行上述实施例中的网络切片管理方法，例如，执行以上描述的图2 中的方法步骤S100至S300、图3中的方法步骤S210、图4中的方法步骤S211至步骤S213、图5中的方法步骤S410至步骤S420、图6中的方法步骤S501至步骤S510、图7中的方法步骤S601至步骤S611、图8中的方法步骤S701至步骤S707、图9中的方法步骤S801至步骤S807、图10中的方法步骤S901至步骤S905。
本申请实施例包括：终端获取终端运行信息，并根据终端运行信息从终端的应用所接入的网络切片中确定待释放网络切片，接着释放待释放网络切片。根据本申请实施例提供的方案，通过获取终端运行信息，可以监控终端的运行信息，例如可以监控终端的应用的运行状态、终端系统的运行状态以及终端的网络连接质量等相关信息；而根据终端运行信息所表现的终端的工作情况，可以从终端的应用所接入的网络切片中确定待释放网络切片，例如确定用户暂不使用的应用所接入的网络切片为待释放网络切片；接着释放该待释放网络切片，避免用户暂不使用的应用仍然维持接入网络切片，从而能够在网络切片按照使用时长收费的情况下避免产生额外费用，从而提高用户的使用体验。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统可以被实施为软件、固件、硬件及其适当的组合。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上是对本申请的一些实施进行了具体说明，但本申请并不局限于上述实施方式，熟悉本领域的技术人员在不违背本申请范围的前提下还可作出种种的等同变形或替换，这些等同的变形或替换均包含在本申请权利要求所限定的范围内。

Claims (10)

  1. 一种网络切片管理方法，包括：
    获取终端运行信息；
    根据所述终端运行信息从终端的应用所接入的网络切片中确定待释放网络切片；
    释放所述待释放网络切片。
  2. 根据权利要求1所述的方法，其中，所述终端运行信息包括应用运行状态，所述根据所述终端运行信息从终端的应用所接入的网络切片中确定待释放网络切片，包括：
    当所述应用运行状态表示为对应的应用进入后台运行状态或处于异常运行状态，且当所述应用保持后台运行状态或处于异常运行状态持续第一时长，确定所述应用所接入的网络切片为待释放网络切片。
  3. 根据权利要求2所述的方法，其中，所述确定所述应用所接入的网络切片为待释放网络切片，包括：
    确定所述应用所接入的网络切片；
    当所述网络切片仅有所述应用接入；
    确定所述网络切片为待释放网络切片。
  4. 根据权利要求1所述的方法，其中，所述终端运行信息包括终端系统状态，所述根据所述终端运行信息从终端的应用所接入的网络切片中确定待释放网络切片，包括：
    当所述终端系统状态表示为终端进入休眠状态，确定终端的应用所接入的所有网络切片均为待释放网络切片。
  5. 根据权利要求1所述的方法，其中，所述终端运行信息包括与网络切片对应的第一网络质量信息和与终端默认网络对应的第二网络质量信息，所述根据所述终端运行信息从终端的应用所接入的网络切片中确定待释放网络切片，包括：
    当所述第二网络质量信息优于所述第一网络质量信息并持续第二时长，从终端的应用所接入的网络切片中确定与所述第一网络质量信息对应的网络切片为待释放网络切片。
  6. 根据权利要求1至5任意一项所述的方法，其中，还包括：
    把接入所述待释放网络切片的应用切换接入到终端默认网络。
  7. 根据权利要求2或3所述的方法，其中，还包括：
    当所述应用退出后台运行状态或退出异常运行状态，重新为所述应用申请接入网络切片。
  8. 根据权利要求7所述的方法，其中，所述重新为所述应用申请接入网络切片，包括：
    获取所述应用的网络切片申请历史表；
    根据所述网络切片申请历史表为所述应用重新申请接入网络切片。
  9. 一种终端，包括：存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现如权利要求1至8中任意一项所述的方法。
  10. 一种计算机可读存储介质，存储有计算机可执行指令，其中，所述计算机可执行指令用于执行权利要求1至8中任意一项所述的方法。
PCT/CN2021/095285 2020-06-19 2021-05-21 网络切片管理方法、终端及计算机可读存储介质 WO2021254096A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/906,215 US20230119027A1 (en) 2020-06-19 2021-05-21 Network slice management method, terminal, and computer readable storage medium
EP21825243.5A EP4109823A4 (en) 2020-06-19 2021-05-21 NETWORK LAYER MANAGEMENT METHOD, TERMINAL AND COMPUTER READABLE STORAGE MEDIUM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010564658.0 2020-06-19
CN202010564658.0A CN113824578A (zh) 2020-06-19 2020-06-19 网络切片管理方法、终端及计算机可读存储介质

Publications (1)

Publication Number Publication Date
WO2021254096A1 true WO2021254096A1 (zh) 2021-12-23

Family

ID=78924533

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/095285 WO2021254096A1 (zh) 2020-06-19 2021-05-21 网络切片管理方法、终端及计算机可读存储介质

Country Status (4)

Country Link
US (1) US20230119027A1 (zh)
EP (1) EP4109823A4 (zh)
CN (1) CN113824578A (zh)
WO (1) WO2021254096A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115484167A (zh) * 2022-08-22 2022-12-16 爱浦路网络技术(南京)有限公司 通信网络中的网络切片关断方法、计算机装置及存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11792725B2 (en) * 2020-07-31 2023-10-17 Apple Inc. Network slice customer (NSC) service ID and user equipment (UE) route selection policy for network slice as a service
CN114640970B (zh) * 2022-03-21 2024-06-11 Oppo广东移动通信有限公司 网络切片的处理方法、装置、终端、存储介质及产品

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106549806A (zh) * 2016-10-26 2017-03-29 清华大学 一种网络切片管理器及其管理方法
WO2018000389A1 (zh) * 2016-06-30 2018-01-04 华为技术有限公司 管理网络切片的方法及其装置
US20180324663A1 (en) * 2017-05-04 2018-11-08 Comcast Cable Communications, Llc Communications For Network Slicing Using Resource Status Information
CN109391648A (zh) * 2017-08-04 2019-02-26 华为技术有限公司 一种应用与网络切片的关联方法、装置和通信系统

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10070344B1 (en) * 2017-07-25 2018-09-04 At&T Intellectual Property I, L.P. Method and system for managing utilization of slices in a virtual network function environment
US10621005B2 (en) * 2017-08-31 2020-04-14 Oracle International Corporation Systems and methods for providing zero down time and scalability in orchestration cloud services
US10716096B2 (en) * 2017-11-07 2020-07-14 Apple Inc. Enabling network slicing in a 5G network with CP/UP separation

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018000389A1 (zh) * 2016-06-30 2018-01-04 华为技术有限公司 管理网络切片的方法及其装置
CN106549806A (zh) * 2016-10-26 2017-03-29 清华大学 一种网络切片管理器及其管理方法
US20180324663A1 (en) * 2017-05-04 2018-11-08 Comcast Cable Communications, Llc Communications For Network Slicing Using Resource Status Information
CN109391648A (zh) * 2017-08-04 2019-02-26 华为技术有限公司 一种应用与网络切片的关联方法、装置和通信系统

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115484167A (zh) * 2022-08-22 2022-12-16 爱浦路网络技术(南京)有限公司 通信网络中的网络切片关断方法、计算机装置及存储介质
CN115484167B (zh) * 2022-08-22 2023-12-15 爱浦路网络技术(南京)有限公司 通信网络中的网络切片关断方法、计算机装置及存储介质

Also Published As

Publication number Publication date
US20230119027A1 (en) 2023-04-20
EP4109823A4 (en) 2023-08-02
EP4109823A1 (en) 2022-12-28
CN113824578A (zh) 2021-12-21

Similar Documents

Publication Publication Date Title
WO2021254096A1 (zh) 网络切片管理方法、终端及计算机可读存储介质
US11212864B2 (en) Method and device for processing non-matching between UE and network state
CN109219117B (zh) 非连续接收的通信同步方法及装置
EP2912535B1 (en) Apparatus and method for controlling operation mode in a wireless terminal
CN107078925B (zh) 一种心跳周期的设置方法及终端
WO2016161793A1 (zh) 异系统的测量方法、相关装置及测量系统
US10146294B2 (en) Method and network units for handling states
EP3262822B1 (en) Opportunistic, location-predictive, server-mediated peer-to-peer offloading
BR112020019864B1 (pt) Método e equipamento de usuário para um estabelecimento de conexão
US20220287135A1 (en) Efficient use of physical and logical resources in dual connectivity
CN112788085A (zh) 一种数据缓存方法和装置
CN102710486B (zh) S通道状态通告方法和设备
CN102497288A (zh) 一种双机备份方法和双机系统实现装置
US11528682B2 (en) Method for paging user equipment, first network device, and user equipment
EP2296333A1 (en) Isr deactivation method and mobility management unit
EP3493563B1 (en) Method and network equipment for processing signals and information
BR102012028349B1 (pt) Método para gerenciar recursos de rádio móvel para aperfeiçoamento de recepção de pacotes
EP3684115A1 (en) Method for allowing user equipment to detach from network entity
CN113950131A (zh) 用于控制辅小区中测量的方法、装置和计算机可读介质
EP3379889B1 (en) Method and terminal for controlling service connection
WO2022028597A1 (zh) 控制辅小区的方法、终端及网络侧设备
US11924759B2 (en) Determination of operational state
CN110266790B (zh) 边缘集群管理方法、装置、边缘集群及可读存储介质
US20170251355A1 (en) Method and apparatus for obtaining user equipment ue information
CN111314272B (zh) 一种任务处理方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21825243

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021825243

Country of ref document: EP

Effective date: 20220919

NENP Non-entry into the national phase

Ref country code: DE