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

Abstract

The present disclosure provides a network slice determination method, device, electronic device and storage medium, which relate to the field of mobile communication technology. The method includes: based on a slice use request, obtaining URSP information, the URSP information includes at least one TD parameter, at least one NSSAI and at least one DNN; determining the correspondence between each TD parameter and each NSSAI and the correspondence between each DNN; determining the target NSSAI and target DNN corresponding to the target TD parameter corresponding to the application; determining the target network slice according to the target NSSAI and the target DNN. The present disclosure can select the target NSSAI and target DNN corresponding to the target TD parameter from the URSP information to ensure that the target network slice can meet the needs and improve the user experience. In addition, the network slice determination method can only be executed after sending a slice use request to ensure that the user is informed, further improving the user experience.

Description

Background Art

[0002] With the continuous development of mobile communication technology, the application of network slicing technology is becoming more and more frequent. Network slicing can provide isolated network environments for different application scenarios, so that different application scenarios can customize functions and features according to their own requirements. Therefore, it is necessary to determine the network slice to be used according to specific needs.

[0003] The transmission of TD (Traffic Descriptor) parameters in the terminal is the key to determining network slicing, that is, how the operating system obtains TD parameters, and how the operating system and Modem (modem) jointly process the matching of TD parameters and URSP (UE Route Selection Policy) information. However, the 3rd Generation Partnership Project (3GPP) does not specify the transmission mechanism of TD parameters in the terminal. Therefore, a network slicing determination method is urgently needed to define the transmission mechanism of TD parameters in the terminal, so that the terminal can use the appropriate network slice to improve the user experience.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0005] The present disclosure provides a network slice determination method, device, electronic device and storage medium, which at least to a certain extent overcome the problem that the related technology does not clearly define the transmission mechanism of TD parameters in the terminal, resulting in the terminal being unable to use the appropriate network slice and poor user experience.

[0006] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by the practice of the present disclosure.

[0007] According to one aspect of an embodiment of the present disclosure, a network slice determination method is provided, the method being performed by a slice middleware, including:

[0008] Based on the slice usage request sent by the application, obtain URSP information, where the URSP information includes at least one TD parameter, at least one NSSAI (Network Slice Selection Assistance Information) and at least one DNN (Date Network Name);

[0009] Determine the correspondence between each TD parameter and each NSSAI in the URSP information, and the correspondence between each TD parameter and each DNN;

[0010] Determine a target NSSAI and a target DNN corresponding to the target TD parameter currently corresponding to the application program, wherein the target TD parameter is included in at least one TD parameter;

[0011] According to the target NSSAI and the target DNN, the target network slice is determined.

[0012] In some embodiments of the present disclosure, determining the correspondence between each TD parameter and each NSSAI in the URSP information, and the correspondence between each TD parameter and each DNN includes:

[0013] From the URSP information, obtain various TD parameters;

[0014] Each TD parameter is analyzed to determine the NSSAI and DNN corresponding to each TD parameter, wherein any TD parameter corresponds to at least one NSSAI, and any TD parameter corresponds to at least one DNN.

[0015] In some embodiments of the present disclosure, the target NSSAI and the target DNN corresponding to the target TD parameters currently corresponding to the application are determined, including:

[0016] When the target TD parameter corresponds to multiple NSSAIs, the target NSSAI is obtained by screening from the multiple corresponding NSSAIs according to the effect indicator corresponding to the target TD parameter;

[0017] When the target TD parameter corresponds to multiple DNNs, the target DNN is obtained by screening from the multiple corresponding DNNs according to the effect index corresponding to the target TD parameter;

[0018] The effect indicator includes at least one of an application security indicator, an application reliability indicator, a delay indicator, a bandwidth indicator, a duration indicator, and an access characteristic indicator.

[0019] In some embodiments of the present disclosure, obtaining URSP information based on a slice usage request sent by an application includes:

[0020] When the application sends a slice usage request, a policy request message is sent to the modem;

[0021] Receive the URSP information returned by the modem.

[0022] In some embodiments of the present disclosure, the target TD parameter includes at least one of an application identifier corresponding to the application, a destination address information accessed by the application, a destination domain name accessed by the application, and a DNN accessed by the application.

[0023] In some embodiments of the present disclosure, the network slice determination method provided by the embodiments of the present disclosure further includes:

[0024] The target TD parameter, the target NSSAI and the target DNN are sent to the modem, wherein the modem is used to establish a PDU (Protocol Data Unit) session in the target network slice through the target TD parameter, the target NSSAI and the target DNN.

[0025] In some embodiments of the present disclosure, after the PDU session is established, the application is used to communicate through the target network slice and display an application list to the user, wherein the application list is used to display changes in network indicators after communicating using the target network slice.

[0026] According to another aspect of the present disclosure, a network slice determination device is provided, the device being applied to a slice middleware, including:

[0027] A policy information acquisition module, configured to acquire URSP information based on a slice usage request sent by an application, wherein the URSP information includes at least one TD parameter, at least one NSSAI, and at least one DNN;

[0028] A correspondence determination module, used to determine the correspondence between each TD parameter and each NSSAI in the URSP information, and the correspondence between each TD parameter and each DNN;

[0029] An information determination module, configured to determine a target NSSAI and a target DNN corresponding to a target TD parameter currently corresponding to the application program, wherein the target TD parameter is included in at least one TD parameter;

[0030] The target network slice determination module is used to determine the target network slice according to the target NSSAI and the target DNN.

[0031] In some embodiments of the present disclosure, the correspondence determination module is used to obtain each TD parameter from the URSP information; analyze each TD parameter to determine the NSSAI and DNN corresponding to each TD parameter, wherein any TD parameter corresponds to at least one NSSAI, and any TD parameter corresponds to at least one DNN.

[0032] In some embodiments of the present disclosure, the information determination module is used to, when the target TD parameter corresponds to multiple NSSAIs, filter out the target NSSAI from multiple corresponding NSSAIs through the effect indicator corresponding to the target TD parameter; when the target TD parameter corresponds to multiple DNNs, filter out the target DNN from multiple corresponding DNNs through the effect indicator corresponding to the target TD parameter; wherein the effect indicator includes at least one of an application security indicator, an application reliability indicator, a delay indicator, a bandwidth indicator, a duration indicator, and an access characteristic indicator.

[0033] In some embodiments of the present disclosure, the policy information acquisition module is used to send policy request information to the modem when the application sends a slice usage request; and receive the URSP information returned by the modem.

[0034] In some embodiments of the present disclosure, the target TD parameter includes at least one of an application identifier corresponding to the application, a destination address information accessed by the application, a destination domain name accessed by the application, and a DNN accessed by the application.

[0035] In some embodiments of the present disclosure, the network slice determination device provided by the embodiments of the present disclosure further includes:

[0036] The target TD parameter sending module is used to send the target TD parameters, the target NSSAI and the target DNN to the modem, wherein the modem is used to establish a PDU session in the target network slice through the target TD parameters, the target NSSAI and the target DNN.

[0037] In some embodiments of the present disclosure, after the PDU session is established, the application is used to communicate through the target network slice and display an application list to the user, wherein the application list is used to display changes in network indicators after communicating using the target network slice.

[0038] According to another aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the above-mentioned network slice determination method by executing the executable instructions.

[0039] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned network slice determination method is implemented.

[0040] According to another aspect of the present disclosure, a computer program product or a computer program is provided, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the network slice determination method provided in various optional ways in any embodiment of the present disclosure.

[0041] The technical solution provided by the embodiment of the present disclosure can obtain the target TD parameters and select the target NSSAI and target DNN corresponding to the target TD parameters from the URSP information. Therefore, it can be ensured that the determined target network slice can meet the needs of the application, thereby improving the user experience. In addition, the network slice determination method can only be executed after the slice usage request sent by the application, which can ensure that the user is informed, thereby further improving the user experience.

[0042] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0044] Figure 1 A schematic diagram showing a system architecture in an embodiment of the present disclosure;

[0045] Figure 2 A flow chart of a network slice determination method according to an embodiment of the present disclosure is shown;

[0046] Figure 3 A flow chart of a method for determining a correspondence between each TD parameter and each NSSAI in URSP information, and a correspondence between each TD parameter and each DNN in an embodiment of the present disclosure is shown;

[0047] Figure 4 A schematic diagram showing an application list in an embodiment of the present disclosure;

[0048] Figure 5 A schematic diagram of determining a target network slice in an embodiment of the present disclosure is shown;

[0049] Figure 6 A flow chart of a method for using a target network slice in an embodiment of the present disclosure is shown;

[0050] Figure 7 A schematic diagram of a network slice determination device in an embodiment of the present disclosure is shown;

[0051] Figure 8 A structural block diagram of an electronic device in an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0052] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that the disclosure will be more comprehensive and complete and to fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0053] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0054] Figure 1 A schematic diagram of an exemplary system architecture that can be applied to a network slice determination method or a network slice determination device according to an embodiment of the present disclosure is shown.

[0055] like Figure 1 As shown, the system architecture 100 may include a terminal device 101, a slice middleware 102, and a network 103. Among them, the terminal device 101 includes at least one application.

[0056] Exemplarily, the application in the terminal device 101 can confirm whether the user permits the application to provide network slicing services. When the user permits, the application in the terminal device 101 can send a slice usage request to the slice middleware 102.

[0057] Then, the slice middleware 102 may obtain URSP information, which includes at least one TD parameter, at least one NSSAI and at least one DNN. After that, the slice middleware 102 may determine the correspondence between each TD parameter and each NSSAI in the URSP information, and the correspondence between each TD parameter and each DNN.

[0058] Then, the slice middleware 102 can determine the target NSSAI and target DNN corresponding to the target TD parameters currently corresponding to the application in the terminal device 101, wherein the target TD parameters are included in at least one TD parameter.

[0059] Finally, the slice middleware 102 can determine the target network slice based on the target NSSAI and the target DNN.

[0060] Exemplarily, the target network slice belongs to network 103. After the slice middleware 102 determines the target network slice, the application in the terminal device 101 can use the target network slice to provide corresponding services to the user.

[0061] Optionally, network 103 can be a wired network or a wireless network. The wireless network or wired network mentioned above uses standard communication technology and / or protocol. The network is usually the Internet, but it can also be any network, including but not limited to a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a mobile, wired or wireless network, a dedicated network or any combination of a virtual private network). In some embodiments, technologies and / or formats including Hyper Text Mark-up Language (HTML), Extensible Markup Language (XML), etc. are used to represent data exchanged through the network. In addition, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), Internet Protocol Security (IPsec) can also be used to encrypt all or some links. In other embodiments, customized and / or dedicated data communication technologies can also be used to replace or supplement the above data communication technologies.

[0062] The terminal device 101 can be various electronic devices, including but not limited to smart phones, tablet computers, notebook computers, laptop computers, desktop computers, wearable devices, augmented reality devices, virtual reality devices, etc.

[0063] Optionally, the client of the application installed in different terminal devices 101 is the same, or the client of the same type of application based on different operating systems. Based on the different terminal platforms, the specific form of the client of the application can also be different, for example, the application client can be a mobile client, a PC client, etc.

[0064] Those skilled in the art will know that Figure 1 The number of terminal devices 101, slice middleware 102 and network 103 is only illustrative, and any number of terminal devices 101, slice middleware 102 and network 103 may be provided according to actual needs. The embodiments of the present disclosure are not limited to this.

[0065] The present exemplary implementation is described in detail below with reference to the accompanying drawings and embodiments.

[0066] First, a network slice determination method is provided in an embodiment of the present disclosure, which can be executed by any slice middleware with computing and processing capabilities.

[0067] Figure 2 A flow chart of a network slice determination method in an embodiment of the present disclosure is shown as follows: Figure 2 As shown, the network slice determination method provided in the embodiment of the present disclosure may include the following steps S202 to S208.

[0068] S202, based on the slice usage request sent by the application, obtain URSP information, where the URSP information includes at least one TD parameter, at least one NSSAI and at least one DNN.

[0069] The embodiments of the present disclosure do not limit the type of the application; the application may be any type of application, for example, an instant messaging application, a video playback application, a game application, etc.

[0070] The embodiments of the present disclosure do not limit the formats of URSP information, TD parameters, NSSAI and DNN. The formats of URSP information, TD parameters, NSSAI and DNN can be any format and can be read by the slice middleware.

[0071] Exemplarily, the slice middleware may be a software deployed in the operating system of the terminal device, and the slice middleware may be used to implement communication between the application in the terminal device and the modem.

[0072] In an exemplary embodiment, the application can confirm whether the user permits the application to provide network slicing services. When the user permits, the application can send a slice usage request to the slice middleware.

[0073] The disclosed embodiments do not limit the method by which an application confirms whether a user permits the application to provide network slicing services. For example, the application may display a confirmation window to the user, and when the user clicks a confirmation button in the confirmation window, the application may deem that the user permits the application to provide network slicing services. Alternatively, with the user's knowledge, the application may confirm that the user permits the application to provide network slicing services by the user double-clicking the application.

[0074] In some embodiments, URSP information is obtained based on a slice usage request sent by an application, including: when the application sends a slice usage request, sending policy request information to a modem; and receiving URSP information returned by the modem.

[0075] Exemplarily, the modem may store pre-configured URSP information, and the modem may return the URSP information to the slice middleware according to the policy request information sent by the slice middleware.

[0076] It should be noted that the URSP information returned to the slice middleware may be all or part of the URSP information stored in the modem, and the embodiments of the present disclosure are not limited to this.

[0077] The disclosed embodiments can ensure that network slicing services can be provided to applications only with the knowledge of the users, thereby improving the user experience.

[0078] S204, determining the correspondence between each TD parameter and each NSSAI in the URSP information, and the correspondence between each TD parameter and each DNN.

[0079] Exemplarily, the slice middleware can use the TD parameter as an index from the URSP rule to extract and analyze the correspondence between the TD parameter and the NSSAI and DNN respectively.

[0080] For example, Figure 3 As shown, a method for determining the correspondence between each TD parameter in URSP information and each NSSAI, and the correspondence between each TD parameter and each DNN, may include steps S2042 to S2044.

[0081] S2042: Obtain various TD parameters from the URSP information.

[0082] S2044, analyzing each TD parameter to determine the NSSAI and DNN corresponding to each TD parameter, wherein any TD parameter corresponds to at least one NSSAI, and any TD parameter corresponds to at least one DNN.

[0083] Exemplarily, if the TD parameter and NSSAI are in a one-to-one relationship and the DNN is unique, one record is saved. For example, a TD parameter in the URSP information is TD 1. TD 1 only corresponds to NSSAI 1 among multiple NSSAIs, and TD 1 only corresponds to DNN 1 among multiple DNNs. At this time, TD 1, NSSAI 1, and DNN 1 can be taken as one record.

[0084] Exemplarily, if the TD parameter and NSSAI are in a one-to-one relationship and DNN is not unique, multiple records can be saved. For example, one TD parameter in the URSP information is TD 1. TD 1 has a corresponding relationship only with NSSAI 1 among multiple NSSAIs. In addition, TD 1 has a corresponding relationship with DNN 1, DNN 2, and DNN 3 among multiple DNNs. At this time, TD 1, NSSAI 1, and DNN 1 can be used as the first record. And TD 1, NSSAI 1, and DNN 2 can be used as the second record. And TD 1, NSSAI 1, and DNN 3 can be used as the third record.

[0085] Exemplarily, if the TD parameter and NSSAI are in a one-to-many relationship and the DNN is unique, multiple records are saved. For example, a TD parameter in the URSP information is TD 1. TD 1 has a corresponding relationship with NSSAI 1, NSSAI 2, and NSSAI 3 in multiple NSSAIs. In addition, TD 1 only has a corresponding relationship with DNN 1 in multiple DNNs. At this time, TD 1, NSSAI 1, and DNN 1 can be used as the first record. And TD 1, NSSAI 2, and DNN 1 can be used as the second record. And TD1, NSSAI 3, and DNN 1 can be used as the third record.

[0086] Exemplarily, if the TD parameters and NSSAI are in a one-to-many relationship and the DNN is not unique, multiple records are saved.

[0087] Exemplarily, if the TD parameter and NSSAI are in a one-to-many relationship and the DNN is unique, multiple records are saved. For example, a TD parameter in the URSP information is TD 1. TD 1 has a corresponding relationship with NSSAI 1 and NSSAI 2 in multiple NSSAIs. In addition, TD 1 has a corresponding relationship with DNN 1 and DNN 2 in multiple DNNs. At this time, TD 1, NSSAI 1 and DNN 1 can be used as the first record, TD 1, NSSAI 2 and DNN 1 can be used as the second record, TD 1, NSSAI 1 and DNN 2 can be used as the third record, and TD 1, NSSAI 2 and DNN 2 can be used as the fourth record.

[0088] Exemplarily, if the TD parameter and NSSAI are in a many-to-one relationship and the DNN is unique, multiple records are saved. For example, the two TD parameters included in the URSP information are TD 1 and TD 2. TD 1 and TD 2 both have a corresponding relationship with NSSAI 1 in multiple NSSAIs. In addition, TD 1 and TD 2 both have a corresponding relationship with DNN 1 in multiple DNNs. At this time, TD 1, NSSAI 1 and DNN 1 can be used as the first record, and TD 2, NSSAI 1 and DNN 1 can be used as the second record.

[0089] Exemplarily, if the TD parameter and NSSAI are in a many-to-one relationship, and DNN is not unique, multiple records are saved. For example, the two TD parameters included in the URSP information are TD 1 and TD 2. TD 1 and TD 2 both have a corresponding relationship with NSSAI 1 in multiple NSSAIs. In addition, TD 1 and TD 2 both have a corresponding relationship with DNN 1 in multiple DNNs. At this time, TD 1, NSSAI 1 and DNN 1 can be used as the first record, and TD 2, NSSAI 1 and DNN 1 can be used as the second record.

[0090] S206, determining the target NSSAI and target DNN corresponding to the target TD parameters currently corresponding to the application, wherein the target TD parameters are included in at least one TD parameter.

[0091] In some embodiments, the target TD parameter may include at least one of an application identifier corresponding to the application, destination address information accessed by the application, a destination domain name accessed by the application, and a DNN accessed by the application.

[0092] In an exemplary embodiment, the slice middleware can record the application identifier corresponding to the application, and can obtain the access and access status of the application in real time, and record the destination address information accessed by the application, the destination domain name accessed by the application, and the DNN accessed by the application, thereby obtaining the target TD parameters.

[0093] Exemplarily, the application identifier corresponding to the application may be, for example, a package name, i.e., APPID (Application Identification). The destination address information may be, for example, represented by an IP triplet, and the information triplet may be, for example, <protocol, destination address, port number>. The destination domain name accessed by the application may be, for example, an FQDN (Fully Qualified Domain Name).

[0094] In some embodiments, the target NSSAI and target DNN corresponding to the target TD parameter currently corresponding to the application are determined, including: when the target TD parameter corresponds to multiple NSSAIs, the target NSSAI is screened from multiple corresponding NSSAIs through the effect indicator corresponding to the target TD parameter; when the target TD parameter corresponds to multiple DNNs, the target DNN is screened from multiple corresponding DNNs through the effect indicator corresponding to the target TD parameter.

[0095] Among them, the effect indicator may include at least one of an application security indicator, an application reliability indicator, a delay indicator, a bandwidth indicator, a duration indicator, and an access characteristic indicator.

[0096] Exemplarily, the application security index, application reliability index, delay index, bandwidth index, duration index, and access characteristic index can be determined based on the application scenario or experience, and the embodiments of the present disclosure do not limit the values ​​of the above-mentioned indicators.

[0097] It should be noted that the embodiment of the present disclosure screens the target NSSAI and the target DNN through effect indicators, so as to ensure that the target network slice determined subsequently can meet the needs of the application, thereby improving the user experience.

[0098] The disclosed embodiments do not limit the method of screening the target NSSAI and the target DNN by the effect indicators herein.

[0099] S208: Determine the target network slice based on the target NSSAI and the target DNN.

[0100] In some embodiments, the network slice determination method provided by the embodiments of the present disclosure may also include: sending the target TD parameters, the target NSSAI and the target DNN to the modem, wherein the modem is used to establish a PDU session in the target network slice through the target TD parameters, the target NSSAI and the target DNN.

[0101] In some embodiments, after the PDU session is established, the application can be used to communicate through the target network slice and display an application list to the user, which is used to display changes in network indicators after communicating using the target network slice.

[0102] In an exemplary embodiment, the slicing middleware can construct a user list and send the user list to the application. Afterwards, the application can display the application list.

[0103] For example, the change of the network indicator can be represented by bandwidth. Figure 4 As shown, the application list can show the change in bandwidth of the application before and after using the target network slice. Figure 4 It can be seen that the bandwidth after using the target network slice is much greater than the bandwidth before using the target network slice.

[0104] In some embodiments, the user can be informed of changes in network indicators after using the target network slice for communication through the application list. In addition, the application list can also include buttons for activating and deactivating the target network slice, so that the user can control the activation and deactivation of the target network slice in the application list.

[0105] For example, Figure 4 As shown, the name of the application can be displayed in the upper left corner of the application list. A button for activating and deactivating the network slice can be displayed above the application list. After pressing the button, the target network slice can be activated or deactivated.

[0106] The disclosed embodiment can enable users to understand the changes in network indicators of applications before and after using the target network slice through the application list, and can independently activate and deactivate the target network slice, further improving the user experience.

[0107] It should be noted that the embodiment of the present disclosure uses slice middleware to determine the target network slice, and avoids using, for example, SDK (Software Development Kit) to determine the target network slice. This is because there may be malicious behavior of silently using and updating the SDK without the user's knowledge. Therefore, the embodiment of the present disclosure uses slice middleware to determine the target network slice, which can ensure user information security and further improve user experience.

[0108] The method provided by the embodiment of the present disclosure can obtain the target TD parameters and select the target NSSAI and target DNN corresponding to the target TD parameters from the URSP information. Therefore, it can be ensured that the determined target network slice can meet the needs of the application, thereby improving the user experience. In addition, the network slice determination method can only be executed after the slice usage request sent by the application, which can ensure that the user is informed, thereby further improving the user experience.

[0109] In some embodiments, a schematic diagram of determining a target network slice may be as follows: Figure 5 shown.

[0110] exist Figure 5 In the terminal device, multiple applications can be included. Figure 5 For example, the terminal device includes application 1 and application 2. In addition, a slice middleware may be deployed in the operating system of the terminal device.

[0111] Taking application 1 as an example, after receiving the slice usage request sent by application 1, the slice middleware can request the modem to obtain URSP information. The URSP information includes at least one TD parameter, at least one NSSAI and at least one DNN. Then, the slice middleware can determine the correspondence between each TD parameter and each NSSAI, and the correspondence between each TD parameter and each DNN.

[0112] Then, the slice middleware can obtain the target TD parameters currently corresponding to the application 1, and determine the target NSSAI and target DNN corresponding to the target TD parameters through the slice scheduling module. After that, the slice middleware can determine the target network slice through the target NSSAI and target DNN.

[0113] Finally, the slice middleware can send the target TD parameters, target NSSAI and target DNN to the modem, and the modem can establish a PDU session in the corresponding target network slice. Figure 5 For example, the target network slice may be network slice 1 or network slice 2.

[0114] Exemplarily, after application 1 uses the target network slice, the slice middleware can build a user list and application 1 can display the user list.

[0115] Figure 6 A flow chart of a method for using a target network slice in an embodiment of the present disclosure is shown as follows: Figure 6 As shown, the method for using the target network slice provided in the embodiment of the present disclosure may include the following steps S602 to S612.

[0116] S602, the slice middleware obtains URSP information from the modem.

[0117] S604, the slice middleware extracts at least one TD parameter from the URSP information, and determines the correspondence between each TD parameter and the NSSAI and the correspondence between each TD parameter and the DNN.

[0118] S606, the slicing middleware saves the correspondence between each TD parameter and NSSAI, and the correspondence between each TD parameter and DNN.

[0119] S608, the slice middleware obtains the access and visit status of the application in real time to determine the current target TD parameters.

[0120] S610, the slice middleware enables the slice scheduling module and determines the target NSSAI and target DNN through the target TD parameters.

[0121] S612, the slice middleware sends the target TD parameters, target DNN and target NSSAI to the modem.

[0122] S614, the modem establishes a PDU session in the target network slice corresponding to the target TD parameters, target DNN and target NSSAI.

[0123] S616, the application program displays the application list in real time.

[0124] Based on the same inventive concept, a network slice determination device is also provided in the embodiments of the present disclosure, as described in the following embodiments. Since the principle of solving the problem in the embodiment of the device is similar to that in the above method embodiment, the implementation of the embodiment of the device can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0125] Figure 7 A schematic diagram of a network slice determination device in an embodiment of the present disclosure is shown. Figure 7 As shown, the device is applied to a slice middleware, including:

[0126] A policy information acquisition module 701 is used to acquire URSP information based on a slice usage request sent by an application, where the URSP information includes at least one TD parameter, at least one NSSAI and at least one DNN;

[0127] A correspondence determination module 702, configured to determine a correspondence between each TD parameter and each NSSAI in the URSP information, and a correspondence between each TD parameter and each DNN;

[0128] An information determination module 703, configured to determine a target NSSAI and a target DNN corresponding to a target TD parameter currently corresponding to the application program, wherein the target TD parameter is included in at least one TD parameter;

[0129] The target network slice determination module 704 is used to determine the target network slice according to the target NSSAI and the target DNN.

[0130] In some embodiments of the present disclosure, the correspondence determination module 702 is used to obtain each TD parameter from the URSP information; analyze each TD parameter to determine the NSSAI and DNN corresponding to each TD parameter, wherein any TD parameter corresponds to at least one NSSAI, and any TD parameter corresponds to at least one DNN.

[0131] In some embodiments of the present disclosure, the information determination module 703 is used to, when the target TD parameter corresponds to multiple NSSAIs, filter out the target NSSAI from multiple corresponding NSSAIs through the effect indicator corresponding to the target TD parameter; when the target TD parameter corresponds to multiple DNNs, filter out the target DNN from multiple corresponding DNNs through the effect indicator corresponding to the target TD parameter; wherein the effect indicator includes at least one of an application security indicator, an application reliability indicator, a delay indicator, a bandwidth indicator, a duration indicator, and an access characteristic indicator.

[0132] In some embodiments of the present disclosure, the policy information acquisition module 701 is used to send policy request information to the modem when the application sends a slice usage request; and receive the URSP information returned by the modem.

[0133] In some embodiments of the present disclosure, the target TD parameter includes at least one of an application identifier corresponding to the application, a destination address information accessed by the application, a destination domain name accessed by the application, and a DNN accessed by the application.

[0134] In some embodiments of the present disclosure, the network slice determination device provided by the embodiments of the present disclosure further includes:

[0135] The target TD parameter sending module is used to send the target TD parameters, the target NSSAI and the target DNN to the modem, wherein the modem is used to establish a PDU session in the target network slice through the target TD parameters, the target NSSAI and the target DNN.

[0136] In some embodiments of the present disclosure, after the PDU session is established, the application is used to communicate through the target network slice and display an application list to the user, wherein the application list is used to display changes in network indicators after communicating using the target network slice.

[0137] The device provided by the embodiment of the present disclosure can obtain the target TD parameters and select the target NSSAI and target DNN corresponding to the target TD parameters from the URSP information. Therefore, it can be ensured that the determined target network slice can meet the needs of the application, thereby improving the user experience. In addition, the network slice determination method can only be executed after the slice usage request sent by the application, which can ensure that the user is informed, thereby further improving the user experience.

[0138] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods or program products. Therefore, various aspects of the present disclosure may be specifically implemented in the following forms, namely: complete hardware implementation, complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as "circuits", "modules" or "systems".

[0139] Refer to the following Figure 8 The electronic device 800 according to this embodiment of the present disclosure is described. Figure 8 The electronic device 800 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0140] like Figure 8 As shown, the electronic device 800 is in the form of a general computing device. The components of the electronic device 800 may include but are not limited to: at least one processing unit 810, at least one storage unit 820, and a bus 830 connecting different system components (including the storage unit 820 and the processing unit 810).

[0141] The storage unit stores program code, which can be executed by the processing unit 810, so that the processing unit 810 executes the steps according to various exemplary embodiments of the present disclosure described in the above “Specific Implementation Methods” section of this specification.

[0142] The storage unit 820 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 8201 and / or a cache memory unit 8202 , and may further include a read-only memory unit (ROM) 8203 .

[0143] The storage unit 820 may also include a program / utility 8204 having a set (at least one) of program modules 8205, such program modules 8205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0144] Bus 830 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0145] The electronic device 800 may also communicate with one or more external devices 840 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 800, and / or communicate with any device that enables the electronic device 800 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 850. Furthermore, the electronic device 800 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 860. As shown, the network adapter 860 communicates with other modules of the electronic device 800 via a bus 830. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0146] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0147] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided, which may be a readable signal medium or a readable storage medium. A program product capable of implementing the above-mentioned method of the present disclosure is stored thereon. In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary implementations of the present disclosure described in the above “Specific Implementation Methods” section of this specification.

[0148] More specific examples of computer-readable storage media in the present disclosure may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0149] In the present disclosure, a computer readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, wherein a readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A readable signal medium may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0150] Alternatively, the program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0151] In a specific implementation, the program code for performing the operation of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0152] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0153] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0154] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0155] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure. The description and examples are to be regarded as exemplary only, and the true scope of the present disclosure is indicated by the appended claims.

Claims

1. A method for determining a network slice, characterized in that: The method is performed by the slice middleware, and includes: Based on the slice usage request sent by the application, obtain the user routing policy URSP information, wherein the URSP information includes at least one service descriptor TD parameter, at least one network slice selection auxiliary information NSSAI and at least one data network name DNN; Determine the correspondence between each TD parameter and each NSSAI in the URSP information, and the correspondence between each TD parameter and each DNN; Determine the target NSSAI and the target DNN corresponding to the target TD parameter by the target TD parameter currently corresponding to the application, wherein the target TD parameter is included in at least one TD parameter, and when the target TD parameter corresponds to multiple NSSAIs and / or multiple DNNs, select the target NSSAI and the target DNN by the effect indicator; Determine the target network slice based on the target NSSAI and the target DNN.

2. The network slice determination method according to claim 1, characterized in that: The determining the correspondence between each TD parameter and each NSSAI in the URSP information, and the correspondence between each TD parameter and each DNN, includes: Obtaining various TD parameters from the URSP information; Each TD parameter is analyzed to determine the NSSAI and DNN corresponding to each TD parameter, wherein any TD parameter corresponds to at least one NSSAI, and any TD parameter corresponds to at least one DNN.

3. The network slice determination method according to claim 2, characterized in that: The determining, by using the target TD parameters currently corresponding to the application, the target NSSAI and the target DNN corresponding to the target TD parameters, comprises: When the target TD parameter corresponds to a plurality of NSSAIs, the target NSSAI is obtained by screening from the plurality of corresponding NSSAIs according to the effect indicator corresponding to the target TD parameter; When the target TD parameter corresponds to a plurality of DNNs, the target DNN is obtained by screening from the plurality of corresponding DNNs according to the effect index corresponding to the target TD parameter; The effect indicator includes at least one of an application security indicator, an application reliability indicator, a delay indicator, a bandwidth indicator, a duration indicator, and an access characteristic indicator.

4. The network slice determination method according to any one of claims 1 to 3, characterized in that: The obtaining of user routing policy URSP information based on the slice usage request sent by the application includes: When the application sends a slice usage request, a policy request message is sent to the modem; The URSP information returned by the modem is received.

5. The network slice determination method according to any one of claims 1 to 3, characterized in that: The target TD parameter includes at least one of an application identifier corresponding to the application, a destination address information accessed by the application, a destination domain name accessed by the application, and a DNN accessed by the application.

6. The network slice determination method according to claim 1, characterized in that: The method further comprises: The target TD parameters, the target NSSAI and the target DNN are sent to the modem, wherein the modem is used to establish a protocol data unit (PDU) session in the target network slice through the target TD parameters, the target NSSAI and the target DNN.

7. The network slice determination method according to claim 6, characterized in that: After the PDU session is established, the application is used to communicate through the target network slice and display an application list to the user, wherein the application list is used to display changes in network indicators after communicating using the target network slice.

8. A network slice determination device, characterized in that: The device is applied to a slicing middleware, and includes: A policy information acquisition module, used to acquire user routing policy URSP information based on a slice usage request sent by an application, wherein the URSP information includes at least one service descriptor TD parameter, at least one network slice selection auxiliary information NSSAI and at least one data network name DNN; A correspondence determination module, used to determine the correspondence between each TD parameter and each NSSAI in the URSP information, and the correspondence between each TD parameter and each DNN; an information determination module, configured to determine a target NSSAI and a target DNN corresponding to a target TD parameter currently corresponding to the application program, wherein the target TD parameter is included in at least one TD parameter, and when the target TD parameter corresponds to a plurality of NSSAIs and / or a plurality of DNNs, the target NSSAI and the target DNN are screened by an effect indicator; The target network slice determination module is used to determine the target network slice according to the target NSSAI and the target DNN.

9. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; Wherein, the processor is configured to execute the network slice determination method described in any one of claims 1 to 7 by executing the executable instructions.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it implements the network slice determination method described in any one of claims 1 to 7.

Images