Access control method and device of network slice and storage medium

Abstract

The application provides a network slice access control method and device and a storage medium. The method comprises the following steps: acquiring usage information of a network slice, wherein the usage information is information about terminal usage of the network slice; and controlling the terminal usage of the network slice according to the usage information. Therefore, the resource utilization rate of the network slice is improved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to an access control method, apparatus and storage medium for network slicing. Background Technology

[0002] The network slice access control function monitors and controls the number of registered terminals and Protocol Data Unit (PDU) sessions within a network slice. It specifies parameters such as the maximum number of terminals and the maximum number of PDU sessions supported by the network slice. In other words, when the number of registered terminals within a network slice reaches the maximum, new terminals will no longer be able to request registration or use the network slice. Similarly, when the number of PDU sessions within a network slice reaches the maximum, new PDU sessions cannot be established.

[0003] However, in practical applications, it has been found that these terminals that have been registered to the network slice or the PDU sessions that have been established may no longer be transmitting data, resulting in low utilization of the network slice. Summary of the Invention

[0004] This application provides a network slice access control method, apparatus, and storage medium to improve the utilization rate of network slices.

[0005] In a first aspect, this application provides a network slicing control method, applied to a first network device, comprising:

[0006] Obtain network slice usage information, wherein the usage information is information about how the terminal uses the network slice;

[0007] Based on the usage information, the terminal is controlled using the network slice.

[0008] In one implementation, obtaining network slice usage information includes:

[0009] Obtain network slice usage information from the second network device;

[0010] The second network device includes one or more of the following: User Plane Function Entity (UPF), Policy Control Function Entity (PCF), Network Data Analysis Function Entity (NWDAF), Radio Access Network (RAN), or Receive Session Management Function Entity (SMF).

[0011] In one implementation, the usage information includes one or more of the following:

[0012] The data volume of the PDU session established by the terminal using the network slice, the data transmission information of the PDU session, and the status of the PDU session;

[0013] Data volume and / or data transmission rate, wherein the data volume is used to characterize the amount of data generated by the terminal using the network slice, and the data transmission rate is used to characterize the rate at which the terminal transmits data using the network slice;

[0014] Data analysis information, which is used to characterize the information on data analysis performed by the terminal using the network slice.

[0015] In one implementation, obtaining network slice usage information includes:

[0016] Obtain usage information for network slices that meet the target time requirements.

[0017] In one implementation, the target time is determined based on one or more of the following: the load of the network slice, the data transmission information of the network slice, and the usage information of the network slice.

[0018] The data transmission information of the network slice is used to characterize information related to the data transmission performed by the network slice.

[0019] In one implementation, controlling the terminal to use the network slice based on the usage information includes:

[0020] The network slice interest parameters of the terminal are determined. The network slice interest parameters are used to characterize the terminal's preference attributes for network slices of interest. The network slice interest parameters include one or more of the following: the identifier of the network slice of interest of the terminal, the time parameter of the terminal using the network slice of interest, and the location parameter of the terminal using the network slice of interest.

[0021] The terminal's use of the network slice is controlled based on the usage information and the network slice's interest parameters.

[0022] In one implementation, controlling the terminal to use the network slice based on the usage information includes:

[0023] The feature information is determined, which includes one or more of the following: the terminal's subscription information, the terminal's priority, and the network slice's data transmission information;

[0024] Based on the usage information and the feature information, the terminal is controlled using the network slice.

[0025] In one implementation, controlling the terminal to use the network slice based on the usage information includes:

[0026] Based on the usage information, perform one or more of the following operations:

[0027] Release all or part of the PDU sessions established by the terminal using the network slice;

[0028] Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal;

[0029] Trigger a deregistration operation to stop the terminal from using the network slice.

[0030] Secondly, this application provides a network slicing control method applied to a terminal, comprising:

[0031] Monitor network slice usage information, where the usage information refers to the information about how the terminal uses the network slice;

[0032] The network slices used are controlled based on the usage information.

[0033] In one implementation, the usage information includes one or more of the following:

[0034] The data volume of the PDU session established by the terminal using the network slice, the data transmission information of the PDU session, and the status of the PDU session;

[0035] Data volume and / or data transmission rate, wherein the data volume is used to characterize the amount of data generated by the terminal using the network slice, and the data transmission rate is used to characterize the rate at which the terminal transmits data using the network slice.

[0036] In one implementation, the monitoring of network slice usage information includes:

[0037] The system receives a first message sent by a core network device. The first message includes an identifier of the network slice. The first message is used to indicate that monitoring of the usage information of the network slice corresponding to the identifier has begun.

[0038] Based on the first message, monitoring of the usage information of the network slice corresponding to the identifier is initiated.

[0039] In one implementation, the first message is sent by the core network device when the load on the network slice reaches a first preset value.

[0040] In one embodiment, the method further includes:

[0041] The system receives a second message from the core network device, the second message including the identifier of the network slice, and the second message is used to indicate to stop monitoring the usage information of the network slice corresponding to the identifier.

[0042] In one implementation, the second message is sent when the load on the network slice is less than a second preset value.

[0043] In one implementation, the monitoring of network slice usage information includes:

[0044] Receive monitoring parameters sent by the core network equipment, wherein the monitoring parameters include time parameters;

[0045] Monitor the usage information of network slices that meet the aforementioned time parameters.

[0046] In one implementation, controlling the terminal to use the network slice based on the usage information includes:

[0047] Based on the usage information, a request message is sent to the core network device, the request message being used to request one or more of the following operations:

[0048] Release all or part of the PDU sessions established by the terminal using the network slice;

[0049] Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal;

[0050] Trigger a deregistration operation to stop the terminal from using the network slice.

[0051] Thirdly, this application provides a network slicing access control device, applied to a first network device, including a memory, a transceiver, and a processor:

[0052] The memory is used to store computer programs;

[0053] The transceiver is used to send and receive data under the control of the processor;

[0054] The processor is configured to read the computer program stored in the memory and perform the following operations:

[0055] Obtain network slice usage information, wherein the usage information is information about how the terminal uses the network slice;

[0056] Based on the usage information, the terminal is controlled using the network slice.

[0057] In one implementation, the processor is specifically configured to perform the following operations:

[0058] Obtain network slice usage information from the second network device;

[0059] The second network device includes one or more of the following: User Plane Function Entity (UPF), Policy Control Function Entity (PCF), Network Data Analysis Function Entity (NWDAF), Radio Access Network (RAN), or Receive Session Management Function Entity (SMF).

[0060] In one implementation, the usage information includes one or more of the following:

[0061] The data volume of the PDU session established by the terminal using the network slice, the data transmission information of the PDU session, and the status of the PDU session;

[0062] Data volume and / or data transmission rate, wherein the data volume is used to characterize the amount of data generated by the terminal using the network slice, and the data transmission rate is used to characterize the rate at which the terminal transmits data using the network slice;

[0063] Data analysis information, which is used to characterize the information on data analysis performed by the terminal using the network slice.

[0064] In one implementation, the processor is configured to perform the following operations:

[0065] Obtain usage information for network slices that meet the target time requirements.

[0066] In one implementation, the target time is determined based on one or more of the following: the load of the network slice, the data transmission information of the network slice, and the usage information of the network slice.

[0067] The data transmission information of the network slice is used to characterize information related to the data transmission performed by the network slice.

[0068] In one implementation, the processor is configured to perform the following operations:

[0069] The network slice interest parameters of the terminal are determined. The network slice interest parameters are used to characterize the terminal's preference attributes for network slices of interest. The network slice interest parameters include one or more of the following: the identifier of the network slice of interest of the terminal, the time parameter of the terminal using the network slice of interest, and the location parameter of the terminal using the network slice of interest.

[0070] The terminal's use of the network slice is controlled based on the usage information and the network slice's interest parameters.

[0071] In one implementation, the processor is configured to perform the following operations:

[0072] The feature information is determined, which includes one or more of the following: the terminal's subscription information, the terminal's priority, and the network slice's data transmission information;

[0073] Based on the usage information and the feature information, the terminal is controlled using the network slice.

[0074] In one implementation, the processor is configured to perform one or more of the following operations:

[0075] Release all or part of the PDU sessions established by the terminal using the network slice;

[0076] Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal;

[0077] Trigger a deregistration operation to stop the terminal from using the network slice.

[0078] Fourthly, this application provides a network slicing access control device applied to a terminal, including a memory, a transceiver, and a processor:

[0079] The memory is used to store computer programs;

[0080] The transceiver is used to send and receive data under the control of the processor;

[0081] The processor is configured to read the computer program stored in the memory and perform the following operations:

[0082] Monitor network slice usage information, where the usage information refers to the information about how the terminal uses the network slice;

[0083] The network slices used are controlled based on the usage information.

[0084] In one implementation, the usage information includes one or more of the following:

[0085] The data volume of the PDU session established by the terminal using the network slice, the data transmission information of the PDU session, and the status of the PDU session;

[0086] Data volume and / or data transmission rate, wherein the data volume is used to characterize the amount of data generated by the terminal using the network slice, and the data transmission rate is used to characterize the rate at which the terminal transmits data using the network slice.

[0087] In one implementation, the processor is configured to perform the following operations:

[0088] The system receives a first message sent by a core network device. The first message includes an identifier of the network slice. The first message is used to indicate that monitoring of the usage information of the network slice corresponding to the identifier has begun.

[0089] Based on the first message, monitoring of the usage information of the network slice corresponding to the identifier is initiated.

[0090] In one implementation, the first message is sent by the core network device when the load on the network slice reaches a first preset value.

[0091] In one implementation, the processor is further configured to perform the following operations:

[0092] The system receives a second message from the core network device, the second message including the identifier of the network slice, and the second message is used to indicate to stop monitoring the usage information of the network slice corresponding to the identifier.

[0093] In one implementation, the second message is sent when the load on the network slice is less than a second preset value.

[0094] In one implementation, the processor is configured to perform the following operations:

[0095] Receive monitoring parameters sent by the core network equipment, wherein the monitoring parameters include time parameters;

[0096] Monitor the usage information of network slices that meet the aforementioned time parameters.

[0097] In one implementation, the processor is used to perform the following operations:

[0098] Based on the usage information, a request message is sent to the core network device, the request message being used to request one or more of the following operations:

[0099] Release all or part of the PDU sessions established by the terminal using the network slice;

[0100] Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal;

[0101] Trigger a deregistration operation to stop the terminal from using the network slice.

[0102] Fifthly, this application provides a network slicing access control device, applied to a first network device, comprising:

[0103] An acquisition unit is used to acquire network slice usage information, wherein the usage information is information about how the terminal uses the network slice;

[0104] A control unit is configured to control the terminal using the network slice based on the usage information.

[0105] In one embodiment, the acquisition unit is used for:

[0106] Obtain network slice usage information from the second network device;

[0107] The second network device includes one or more of the following: User Plane Function Entity (UPF), Policy Control Function Entity (PCF), Network Data Analysis Function Entity (NWDAF), Radio Access Network (RAN), or Receive Session Management Function Entity (SMF).

[0108] In one implementation, the usage information includes one or more of the following:

[0109] The data volume of the PDU session established by the terminal using the network slice, the data transmission information of the PDU session, and the status of the PDU session;

[0110] Data volume and / or data transmission rate, wherein the data volume is used to characterize the amount of data generated by the terminal using the network slice, and the data transmission rate is used to characterize the rate at which the terminal transmits data using the network slice;

[0111] Data analysis information, which is used to characterize the information on data analysis performed by the terminal using the network slice.

[0112] In one embodiment, the acquisition unit is used for:

[0113] Obtain usage information for network slices that meet the target time requirements.

[0114] In one implementation, the target time is determined based on one or more of the following: the load of the network slice, the data transmission information of the network slice, and the usage information of the network slice.

[0115] The data transmission information of the network slice is used to characterize information related to the data transmission performed by the network slice.

[0116] In one embodiment, the control unit is used to:

[0117] The network slice interest parameters of the terminal are determined. The network slice interest parameters are used to characterize the terminal's preference attributes for network slices of interest. The network slice interest parameters include one or more of the following: the identifier of the network slice of interest of the terminal, the time parameter of the terminal using the network slice of interest, and the location parameter of the terminal using the network slice of interest.

[0118] The terminal's use of the network slice is controlled based on the usage information and the network slice's interest parameters.

[0119] In one embodiment, the control unit is used to:

[0120] The feature information is determined, which includes one or more of the following: the terminal's subscription information, the terminal's priority, and the network slice's data transmission information;

[0121] Based on the usage information and the feature information, the terminal is controlled using the network slice.

[0122] In one embodiment, the control unit is used to:

[0123] Based on the usage information, perform one or more of the following operations:

[0124] Release all or part of the PDU sessions established by the terminal using the network slice;

[0125] Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal;

[0126] Trigger a deregistration operation to stop the terminal from using the network slice.

[0127] Sixthly, this application provides a network slicing access control device, applied to a terminal, comprising:

[0128] The monitoring unit is used to monitor the usage information of the network slice, wherein the usage information is the information of the terminal using the network slice;

[0129] A control unit is configured to control the network slices in use based on the usage information.

[0130] In one implementation, the usage information includes one or more of the following:

[0131] The data volume of the PDU session established by the terminal using the network slice, the data transmission information of the PDU session, and the status of the PDU session;

[0132] Data volume and / or data transmission rate, wherein the data volume is used to characterize the amount of data generated by the terminal using the network slice, and the data transmission rate is used to characterize the rate at which the terminal transmits data using the network slice.

[0133] In one embodiment, the monitoring unit is used for:

[0134] The system receives a first message sent by a core network device. The first message includes an identifier of the network slice. The first message is used to indicate that monitoring of the usage information of the network slice corresponding to the identifier has begun.

[0135] Based on the first message, monitoring of the usage information of the network slice corresponding to the identifier is initiated.

[0136] In one implementation, the first message is sent by the core network device when the load on the network slice reaches a first preset value.

[0137] In one embodiment, the monitoring unit is further configured to:

[0138] The system receives a second message from the core network device, the second message including the identifier of the network slice, and the second message is used to indicate to stop monitoring the usage information of the network slice corresponding to the identifier.

[0139] In one implementation, the second message is sent when the load on the network slice is less than a second preset value.

[0140] In one embodiment, the monitoring unit is used for:

[0141] Receive monitoring parameters sent by the core network equipment, wherein the monitoring parameters include time parameters;

[0142] Monitor the usage information of network slices that meet the aforementioned time parameters.

[0143] In one embodiment, the control unit is used to:

[0144] Based on the usage information, a request message is sent to the core network device, the request message being used to request one or more of the following operations:

[0145] Release all or part of the PDU sessions established by the terminal using the network slice;

[0146] Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal;

[0147] Trigger a deregistration operation to stop the terminal from using the network slice.

[0148] In a seventh aspect, this application provides a computer-readable storage medium storing a computer program for causing a computer to perform the methods described in the first or second aspect.

[0149] Eighthly, this application provides a computer program product comprising a computer program that, when executed by a computer or processor, implements the method described in the first or second aspect.

[0150] Ninthly, this application provides a processor-readable storage medium storing a computer program for causing a processor to perform the method described in the first or second aspect.

[0151] This application provides a network slicing access control method, apparatus, and storage medium. The method is applied to core network equipment or terminals. By acquiring network slice usage information and controlling the terminal to use network slices based on the network slice usage information, the utilization rate of network slices can be improved.

[0152] It should be understood that the description in the foregoing summary section is not intended to limit the key or essential features of the embodiments of the present invention, nor is it intended to restrict the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0153] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0154] Figure 1 A flowchart illustrating the process of NSACF controlling the number of UEs accessing network slices;

[0155] Figure 2 A flowchart illustrating the process of controlling the number of PDU sessions in a network slice for NSACF.

[0156] Figure 3a A flowchart illustrating the network slicing access control method provided in this application embodiment. Figure 1 ;

[0157] Figure 3b A flowchart illustrating the network slicing access control method provided in this application embodiment. Figure 2 ;

[0158] Figure 4 A flowchart illustrating the network slicing access control method provided in this application embodiment is shown in Figure 3.

[0159] Figure 5 A flowchart illustrating the network slicing access control method provided in this application embodiment. Figure 4 ;

[0160] Figure 6 A flowchart illustrating the network slicing access control method provided in this application embodiment. Figure 5 ;

[0161] Figure 7 A flowchart illustrating the network slicing access control method provided in this application embodiment. Figure 6 ;

[0162] Figure 8 A flowchart illustrating the network slicing access control method provided in this application embodiment. Figure 7 ;

[0163] Figure 9 A flowchart illustrating the network slicing access control method provided in this application embodiment. Figure 8 ;

[0164] Figure 10 A flowchart illustrating the network slicing access control method provided in this application embodiment. Figure 9 ;

[0165] Figure 11 A flowchart illustrating the network slicing access control method provided in this application embodiment. Figure 10 ;

[0166] Figure 12 Schematic diagram of the network slicing access control device provided in the embodiments of this application Figure 1 ;

[0167] Figure 13 Schematic diagram of the network slicing access control device provided in the embodiments of this application Figure 2 ;

[0168] Figure 14 Schematic diagram three of the network slicing access control device provided in the embodiments of this application;

[0169] Figure 15 Schematic diagram of the network slicing access control device provided in the embodiments of this application Figure 4 . Detailed Implementation

[0170] In this application, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0171] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0172] This application provides a method and apparatus for network slicing access control, which controls the terminal's use of network slices based on the terminal's network slice usage information to improve the utilization rate of network slices. The method and apparatus are based on the same concept, and since the principles by which the method and apparatus solve the problem are similar, embodiments of the apparatus and method can be referred to each other, and repeated details will not be repeated.

[0173] The technical solutions provided in this application can be applied to various systems, especially 5G systems. For example, applicable systems include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) and 5G system (5GS).

[0174] The terminal devices involved in the embodiments of this application can be devices that provide voice and / or data connectivity to users, handheld devices with wireless connectivity, or other processing devices connected to a wireless modem. The names of the terminal devices may differ in different systems; for example, in a 5G system, a terminal device can be called User Equipment (UE). Wireless terminal devices can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). Wireless terminal devices can be mobile terminal devices, such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, for example, portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile devices that exchange voice and / or data with the RAN. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0175] The following section will first introduce the Network Slice Admission Control Function (NSACF).

[0176] Network slice access control is used to monitor and control the number of registered UEs and PDU sessions within a network slice. For each network slice requiring access control, the NSACF is configured with a maximum number of UEs and a maximum number of PDU sessions. When the number of UEs within a network slice reaches the maximum, the network device will reject any new UE requesting to use the slice. Similarly, when the number of PDU sessions within a network slice reaches the maximum, new PDU session establishment requests will also be rejected. The following sections explain how the NSACF controls the number of UEs and PDU sessions within a network slice.

[0177] (a) NSACF controls the number of UEs accessing network slices

[0178] The NSACF controls (increases or decreases) the number of UEs currently registered to a network slice, ensuring it does not exceed the maximum number of UEs allowed to register to that network slice. For each network slice requiring access control, the NSACF also maintains a list of UE IDs, recording the IDs of UEs registered to that network slice. When a UE requests to register to a network slice from the Access and Mobility Management Function (AMF), and the AMF determines to register the UE to the network slice, the AMF requests the NSACF to update the UE ID list for that network slice and the number of UEs registered to that network slice. The NSACF first checks if the UE's ID already appears in the UE ID list; if not, the NSACF then checks if the maximum number of UEs has been reached. (See reference...) Figure 1 The specific process will be explained.

[0179] S101, AMF triggers the network slice UE number availability check and update process.

[0180] The triggering condition can be either the AMF determining to register the UE to a network slice, or the AMF determining to deregister the UE from a network slice. Registering the UE to a network slice involves adding the identifier of that network slice to the identifier set of network slices allowed for the UE. The identifier of the network slice is represented by Single Network Slice Selection Assistance Information (S-NSSAI), and the identifier set of network slices allowed for the UE is represented by Allowed NSSAI. Deregistering the UE from a network slice involves deleting the identifier of that network slice from the identifier set of network slices allowed for the UE.

[0181] S102, AMF sends a Network Slice UE Availability Check and Update Request (Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate_Request) message to NSACF. This request message includes the UE ID, S-NSSAI, and update tag.

[0182] The update flag includes an add flag and a decrement flag. When a UE is authorized to register to a network slice identified by S-NSSAI, and that network slice requires access control, the AMF sets the update flag to the add flag to request the NSACF to add the UE's ID to the UE ID list of that network slice and increase the number of UEs currently registered to that network slice. When a UE deregisters from a network slice identified by S-NSSAI, and that S-NSSAI requires access control, the AMF sets the update flag to the decrement flag to request the NSACF to remove the UE's ID from the UE ID list of that network slice and decrease the number of UEs currently registered to that network slice.

[0183] S103, NSACF updates the number of UEs currently registered to the network slice, that is, increases or decreases the number of UEs registered to the network slice according to the update flag provided by AMF.

[0184] In one scenario, if the update flag provided by AMF is an increment flag, then NSACF performs the following operation:

[0185] If the UE's ID is not included in the UE ID list of the network slice, and the number of UEs currently registered to the network slice has not yet reached the maximum number of UEs, NSACF adds the UE's ID to the UE ID list of the network slice and increases the number of UEs registered to the network slice.

[0186] If the UE's ID is not included in the UE ID list of the network slice, but the number of UEs currently registered to the network slice has reached the maximum number of UEs, NSACF returns a result parameter indicating that the number of UEs registered to the network slice has reached the maximum number of UEs.

[0187] If the UE's ID is already included in the UE ID list of the network slice, this scenario can occur when the UE moves across AMFs and before a UE context transfer has occurred. The network slice the UE requests to register with the new AMF is one that the UE has already registered with the old AMF. In this case, the UE's record is already in the UE ID list of the network slice (i.e., when the old AMF sends a network slice UE count availability check and update request, the NSACF adds a record to the UE ID list). At this point, the NSACF creates a new record for the UE in the UE ID list based on the network slice UE count availability check and update request sent by the new AMF, while temporarily retaining the old record. Since the two records belong to the same UE, the NSACF does not increase the number of UEs registered to the network slice. Afterwards, the old AMF sends a network slice UE count availability check and update request to the NSACF to delete the old record.

[0188] In another scenario, if the update flag provided by the AMF is a reduction flag, and the UE ID list of the network slice maintains only one record related to the UE, then the NSACF removes the UE's ID from the UE ID list of the network slice and reduces the number of UEs registered to the network slice. If the update flag provided by the AMF is a reduction flag, and the UE ID list of the network slice maintains two records related to the UE (i.e., the aforementioned scenario of UE movement across AMFs), then the NSACF deletes the old record and maintains the new record.

[0189] S104, NSACF returns the Network Slice UE Availability Check and Update Response message (Nnsacf_NumberOfUEsPerSliceAvailabilityCheckAndUpdate_Response).

[0190] For all network slices for which a UE requests registration, if any network slice has reached its maximum number of UEs, the NSACF returns the network slice's S-NSSAI and result parameters in the response message. The result parameters indicate that the number of UEs registered to the network slice identified by that S-NSSAI has reached its maximum number of UEs. If the NSACF returns "maximum number of UEs reached" for all network slices for which a UE requests registration, the AMF rejects the UE's registration request, including the identifier of the rejected network slice (rejected S-NSSAI) in the registration rejection message, and setting the rejection reason to "maximum number of UEs reached for the network slice." Otherwise, the AMF returns a registration acceptance message.

[0191] (ii) NSACF controls the number of PDU sessions per network slice

[0192] The NSACF controls (increases or decreases) the number of PDU sessions in a network slice, ensuring it does not exceed the maximum number of PDU sessions supported by that network slice. When a UE requests to establish a PDU session from the Session Management Function (SMF), and the SMF determines to establish the PDU session, the SMF needs to request the NSACF to increase the number of PDU sessions in the network slice. The NSACF then checks whether the maximum number of PDU sessions supported by that network slice has already been reached. (See reference...) Figure 2 The specific process will be explained.

[0193] S201. For network slices that require access control, the SMF triggers a network slice PDU session availability check and update process.

[0194] The triggering condition can be the start of the PDU session establishment process, or the last step of the release process of a successfully established PDU session.

[0195] S202, SMF sends a Network Slice PDU Session Availability Check and Update Request message (Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate_Request) to NSACF.

[0196] The request message carries S-NSSAI and update flags. S-NSSAI is used to identify the network slice where the number of PDU sessions needs to be updated, and update flags include add flags and remove flags.

[0197] If the above process is triggered at the beginning of the PDU session establishment process, the updated flag is incremented; if the above process is triggered in the last step of the PDU session release process, the updated flag is decremented.

[0198] S203, NSACF updates the number of PDU sessions for network slices, that is, it increases or decreases the number of PDU sessions for network slices based on the update flags provided by SMF.

[0199] If the update flag provided by SMF is an increment flag, and the maximum number of PDU sessions supported by the network slice has not yet been reached, NSACF increments the number of PDU sessions for that network slice. If the maximum number of PDU sessions supported by the network slice has been reached, NSACF returns a result parameter indicating that the maximum number of PDU sessions supported by the network slice has been reached.

[0200] If the update flag provided by SMF is a reduction flag, then NSACF reduces the number of PDU sessions for that network slice.

[0201] S204, NSACF returns the Network Slice PDU Session Availability Check and Update Response message (Nnsacf_NumberOfPDUsPerSliceAvailabilityCheckAndUpdate_Response).

[0202] During the PDU session establishment process, if NSACF returns that the maximum number of PDU sessions supported by the network slice has been reached, SMF will reject the UE's PDU session establishment request and return a rejection reason to the UE, namely that the maximum number of PDU sessions supported by the network slice has been reached.

[0203] Furthermore, if the PDU session establishment fails after NSACF increases the number of PDU sessions for a network slice, SMF will send a network slice PDU session availability check and update request message to NSACF, and set the update flag in the request message to the reduction flag.

[0204] As explained above regarding the number of UEs and PDU sessions controlled by NSACF for network slices, for a UE registered to a network slice, even if it does not use that network slice to transmit data, the UE's record is still included in the UE ID list maintained by NSACF for that network slice, and the number of UEs registered to that network slice is also included. When the number of UEs in that network slice reaches the maximum, other UEs that need to use that network slice to transmit data cannot register to that network slice. Similarly, for PDU sessions already established in a network slice, even if that PDU session does not transmit data, the number of PDU sessions in the network slice is still included. When the number of PDU sessions in that network slice reaches the maximum, if other PDU sessions need to be created in that network slice to transmit data, they cannot be created. Therefore, the current network slice control function leads to low resource utilization of network slices.

[0205] To address the aforementioned issues, this application proposes obtaining network slice usage information from network devices or UEs, and further controlling UE usage of network slices based on this information. This avoids UEs that are not using network slices occupying network slice resources for extended periods, thereby improving network slice resource utilization.

[0206] The network slicing access control method provided in this application will be described in detail below through specific embodiments. It is understood that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0207] Figure 3a A flowchart illustrating the network slicing access control method provided in this application embodiment. Figure 1This method is applied to the first network device, such as... Figure 3a As shown, the method includes:

[0208] S3001. Obtain network slice usage information.

[0209] Among them, the usage information refers to the information on network slicing used by the UE.

[0210] In this step, UE refers to a UE that has registered with a network slice. For a UE that has registered with a network slice, the usage information of the network slice is obtained, that is, the UE's usage information of the network slice. This usage information may include one or more of the following:

[0211] The data volume of the PDU session established by the UE using network slicing, the data transmission information of the PDU session, and the status of the PDU session, wherein the status of the PDU session may include the activation / deactivation status of the PDU session, the establishment status of the PDU session, etc.

[0212] Data volume and / or data transmission rate, wherein data volume is used to characterize the amount of data generated by the UE using network slices, and data transmission rate is used to characterize the rate at which the UE transmits data using network slices;

[0213] Data analysis information, which is used to characterize the information used by the UE to perform data analysis using the network slice.

[0214] The usage information can be obtained by the first network device from the second network device, wherein the second network device includes one or more of the following: User Plane Function (UPF), Policy Control Function (PCF), Network Data Analytics Function (NWDAF), Radio Access Network (RAN), or SMF.

[0215] S3002. Control the use of network slicing for the UE based on the usage information.

[0216] UE network slice usage information can indicate whether the UE uses network slices to transmit data, i.e., whether the UE generates data within a network slice. Controlling UE network slice usage can include one or more of the following: releasing all or part of the PDU sessions established by the UE using network slices; deleting the identifier of a network slice from the set of identifiers of network slices allowed for UE use; triggering a deregistration operation to stop the UE from using network slices.

[0217] Specifically, releasing PDU sessions established by a UE using a network slice reduces the number of PDU sessions for that network slice, ensuring successful establishment of other PDU sessions when needed. Removing the identifier of a network slice from the set of identifiers allowed for UE use, or triggering a deregistration operation, reduces the number of registered UEs for that network slice, ensuring successful registration for other UEs when they need to use that network slice.

[0218] In this embodiment of the application, for a UE that has been registered to a network slice, the network device can control the UE to use the network slice based on the UE's network slice usage information. Thus, if the UE's network slice usage information indicates that the UE has not generated data within the network slice, the above operation can be used to release the network slice resources occupied by the UE, so that other UEs can use the network slice to transmit data again, thereby improving the resource utilization rate of the network slice.

[0219] Figure 3b A flowchart illustrating the network slicing access control method provided in this application embodiment. Figure 2 This method is applied to UEs, such as... Figure 3b As shown, the method includes:

[0220] S3101. Monitor network slice usage information.

[0221] Among them, the usage information refers to the information on network slicing used by the UE.

[0222] In this step, UE refers to a UE that has registered with a network slice. For a UE that has registered with a network slice, the UE can actively monitor the usage information of the network slice, that is, the UE's usage information of the network slice.

[0223] The usage information may include one or more of the following:

[0224] The data volume of the PDU session established by the UE using network slicing, the data transmission information of the PDU session, and the status of the PDU session, wherein the status of the PDU session may include the activation / deactivation status of the PDU session, the establishment status of the PDU session, etc.

[0225] Data volume and / or data transmission rate, where data volume is used to characterize the amount of data generated by the UE using network slices, and data transmission rate is used to characterize the rate at which the UE transmits data using network slices.

[0226] S3102. Control the network slices used based on the usage information.

[0227] The UE's network slice usage information can indicate whether the UE uses the network slice to transmit data, that is, whether the UE generates data within the network slice. Controlling the network slice used may include one or more of the following: releasing the PDU session established by the UE using the network slice; deleting the identifier of the network slice from the identifier set of network slices allowed for UE use; triggering a deregistration operation to stop the UE from using the network slice.

[0228] Releasing the PDU sessions associated with a UE and a network slice reduces the number of PDU sessions for that network slice, ensuring successful establishment of other PDU sessions when needed. Removing a network slice from a UE's allowed network slices, or deregistering the UE from a network slice, reduces the number of registered UEs for that network slice, ensuring successful registration for other UEs when they need to use that network slice.

[0229] In this embodiment of the application, for a UE that has been registered to a network slice, the UE can monitor its network slice usage information and then control the UE to use the network slice. Thus, if the UE's network slice usage information indicates that the UE has not generated data in the network slice, the above operation can be used to release the network slice resources occupied by the UE, so that other UEs can use the network slice to transmit data again, thereby improving the resource utilization rate of the network slice.

[0230] The method described above will be further illustrated below with specific embodiments. First, regarding... Figure 3a The method applied to the first network device is described below.

[0231] In one scenario, the first network device is a core network device, such as an SMF. Correspondingly, the second network device includes one or more of the following: UPF, PCF, or NWDAF.

[0232] For example, the SMF obtains UE network slice usage information from at least one of the UPF, PCF, or NWDAF, including one or more of the following:

[0233] The SMF receives data volume information from the UPF regarding the PDU session established by the UE using network slices; the SMF receives data transmission rate information from the PCF regarding the UE using network slices; and the SMF receives data analysis information from the NWDAF regarding the UE using network slices.

[0234] The following sections will explain each of the above items.

[0235] Reference Figure 4 In a scenario where the SMF obtains data volume information of the PDU session established by the UE using network slicing from the UPF, the access control process for network slicing is as follows:

[0236] S401, SMF sends an event subscription request to UPF.

[0237] The event subscription request is used to request the UPF to monitor the amount of data in the PDU session established by the UE using network slicing, and to detect the duration for which the amount of data is 0 (i.e. no data transmission). If the duration exceeds the target time, an event notification is sent to the SMF.

[0238] S402, UPF monitors the data volume information of PDU sessions established by the UE using network slicing.

[0239] S403 If the UPF detects that the duration of no data transmission in the PDU session established by the UE using network slicing exceeds the target time, it sends an event notification to the SMF.

[0240] S404, SMF releases the PDU session established by the UE using network slicing.

[0241] S405, SMF triggers the NSAC process to NSACF.

[0242] The message sent by SMF to NSACF includes the S-NSSAI of the network slice and the update flag set to be reduced.

[0243] Reference Figure 5 In scenarios where the SMF obtains the data transmission rate of the UE using the network slice from the PCF, the access control process for the network slice is as follows:

[0244] S501, SMF sends an event subscription request to PCF.

[0245] This event subscription request is used to request the PCF to notify the SMF of the event when it detects that the UE is using a network slice with a data transmission rate of 0 for a period of time exceeding a target time.

[0246] S502, PCF monitors the data transmission rate of the UE using network slices.

[0247] When S503 and PCF detect that the UE's data transmission rate using network slices is 0 for a period exceeding the target time, they send an event notification to SMF.

[0248] S504, SMF releases the PDU session established by the UE using network slicing.

[0249] S505, SMF triggers the NSAC process to NSACF.

[0250] The message sent by SMF to NSACF includes the S-NSSAI of the network slice and the update flag set to be reduced.

[0251] Reference Figure 6 In scenarios where the SMF obtains data analysis information about the UE's use of network slices from the NWDAF, the access control process for network slices is as follows:

[0252] S601 and NWDAF determine the data analysis information.

[0253] Data analysis information may include analysis results of the data transmission rate and / or data volume of the UE using network slices, and analysis results of the data transmission rate and / or data volume of PDU sessions established by the UE using network slices. For example, the analysis results may include peak time periods, valley time periods, and time periods where the data transmission rate and / or data volume are 0 in the terminal's historical network slice usage records. For example, the data analysis information may include: the terminal's data transmission rate is 0 from 0:00 to 2:00 every day.

[0254] S602 and NWDAF send data analysis information to SMF.

[0255] S603, SMF releases the PDU session during the time period when the data transmission rate and / or data volume contained in the data analysis information are 0, according to the data analysis information.

[0256] For example, the data analysis information includes that the data transmission rate of the terminal is 0 from 0:00 to 2:00 every day. Based on this data analysis information, SMF releases PDU sessions from 0:00 to 2:00 thereafter.

[0257] S604, SMF triggers the NSAC process to NSACF.

[0258] The message sent by SMF to NSACF includes the S-NSSAI of the network slice and the update flag set to be reduced.

[0259] It should be noted that the above Figure 4 , Figure 5 and Figure 6 The methods shown can be combined, meaning that the SMF can decide to release the PDU session based on the UE’s network slice usage information sent by at least one of the UPF, PCF, or NWDAF.

[0260] In addition, the SMF can also decide to release a PDU session based on the status of the PDU session established by the UE using network slicing. The status of the PDU session can include the activation / deactivation status of the PDU session. For example, if the user plane of the PDU session is deactivated for a longer period than the target time, the SMF will release the PDU session.

[0261] In one scenario, the first network device is a core network device, which includes an AMF (Active Network Filter). Correspondingly, the second network device includes one or more of the following: RAN (Radio Router Array), SMF (Small Network Filter), or NWDAF (Network Window Filter).

[0262] For example, the AMF obtains UE network slice usage information from one or more of the RAN, SMF, or NWDAF, including one or more of the following:

[0263] The AMF receives data transmission rates of the UE using network slices from the RAN; the AMF receives the status of PDU sessions established by the UE using network slices from the SMF; and the AMF receives data analysis information of the UE using network slices from the NWDAF. The following sections will explain each of these items.

[0264] Reference Figure 7 In a scenario where the AMF obtains the data transmission rate of the UE using the network slice from the RAN, the access control process for the network slice is as follows:

[0265] S701 and AMF send an event subscription request to the RAN.

[0266] This event subscription request is used to request the RAN to notify the AMF of the event when it detects that the UE is using network slices with a data transmission rate of 0 for a period of time exceeding a target time.

[0267] S702, RAN monitors the data transmission rate of the UE using network slices.

[0268] S703 and RAN send an event notification to AMF if they detect that the data transmission rate of the UE using network slices is 0 for a period of time exceeding the target time.

[0269] S704, AMF triggers the UE configuration update process.

[0270] During the UE configuration update process, the AMF removes the S-NSSAI of the network slice from the UE's Allowed NSSAI (deregisters the UE from the network slice). During the UE configuration update process, the AMF also requests the SMF to release the PDU sessions established by the UE using the network slice.

[0271] S705, AMF triggers the NSAC process to NSACF.

[0272] The message sent by the AMF to the NSACF includes the UE ID, the S-NSSAI of the network slice, and an update flag that is set to be reduced.

[0273] S706, SMF triggers the NSAC process to NSACF.

[0274] After the SMF releases the PDU session, the SMF triggers NSAC. The message sent by the SMF to the NSACF includes the S-NSSAI of the network slice and the update flag that has been set to be reduced.

[0275] Reference Figure 8 In a scenario where the AMF obtains the state of the PDU session established by the UE using network slicing from the SMF, the access control process for network slicing is as follows:

[0276] S801, SMF sends a session management context state notification to AMF.

[0277] When the user plane of a PDU session is deactivated, the SMF sends a session management context status notification to the AMF. The session management context status notification is used to indicate that the user plane of the PDU session has been deactivated.

[0278] S802, AMF triggers the UE configuration update process.

[0279] When the duration for which the user plane of the PDU session is deactivated exceeds the target time, or when the duration for which the UE has not used the network slice to establish a PDU session exceeds the target time, the AMF triggers the UE configuration update process.

[0280] During the UE configuration update process, the AMF removes the S-NSSAI of the network slice from the UE's Allowed NSSAI (deregisters the UE from the network slice). During the UE configuration update process, the AMF also requests the SMF to release the PDU sessions established by the UE using the network slice.

[0281] S803, AMF triggers the NSAC process to NSACF.

[0282] The message sent by the AMF to the NSACF includes the UE ID, the S-NSSAI of the network slice, and an update flag that is set to be reduced.

[0283] S804, SMF triggers the NSAC process to NSACF.

[0284] After the SMF releases the PDU session, the SMF triggers NSAC. The message sent by the SMF to the NSACF includes the S-NSSAI of the network slice and the update flag that has been set to be reduced.

[0285] Reference Figure 9 In scenarios where the AMF obtains data analysis information about the UE's use of network slices from the NWDAF, the access control process for network slices is as follows:

[0286] S901 and NWDAF determine the data analysis information.

[0287] Data analysis information may include analysis results of the data transmission rate and / or data volume of the UE using network slices, and analysis results of the data transmission rate and / or data volume of PDU sessions established by the UE using network slices. For example, the analysis results may include peak time periods, valley time periods, and time periods where the rate and / or data volume are 0 in the terminal's historical network slice usage history. For example, the data analysis information may include: the terminal's data transmission rate is 0 from 0:00 to 2:00 every day.

[0288] S902 and NWDAF send data analysis information to AMF.

[0289] S903, AMF removes the S-NSSAI of the network slice from the UE's Allowed NSSAI during the period when the next data transmission rate and / or data volume is 0 (deregistering the UE from the network slice).

[0290] For example, the data analysis information includes that the data transmission rate of the terminal is 0 from 0:00 to 2:00 every day. Based on this data analysis information, AMF will register the UE from the network slice from 0:00 to 2:00 thereafter.

[0291] S904, AMF triggers the NSAC process to NSACF.

[0292] The message sent by the AMF to the NSACF includes the UE ID, the S-NSSAI of the network slice, and an update flag that is set to be reduced.

[0293] It should be noted that the above Figure 7 , Figure 8 and Figure 9 The methods shown can be combined, meaning that the AMF can decide to register the UE from the network slice based on the UE's network slice usage information sent by at least one of the RAN, SMF, or NWDAF.

[0294] Based on the above embodiments, for scenarios where the above method is applied to core network equipment (SMF or AMF), the target time involved can be determined by the core network equipment.

[0295] The core network equipment determines a target time, which can be used to indicate the availability of network slices that meet the target time requirements. This target time can be a target time period or a target moment.

[0296] Optionally, the core network equipment can determine the target time based on at least one of the following: UE usage information of the network slice, network slice load, or network slice data transmission information. The network slice data transmission information characterizes information related to data transmission performed by the network slice, and may include historical data volume and / or historical data transmission rate of the network slice. The network slice data transmission information can be the data volume and / or data transmission rate generated by all or some terminals using the network slice; or the data volume and / or data transmission rate generated by the network slice transmitting data per unit time.

[0297] Optionally, if the target time is a target time period, the core network device starts a timer with a duration equal to the target time period. During the timer's operation, the core network device obtains the UE's network slice usage information. For example, the AMF obtains the data transmission rate and / or data volume from the RAN, NWDAF, SMF, or PCF, and the SMF obtains the data transmission rate and / or data volume from the UPF, NWDAF, or PCF. After the timer expires, the core network device controls the UE's use of the network slice based on the usage information obtained during the timer's operation. For example, if it is determined that the UE has not generated data transmission during this period based on the usage information obtained during the timer's operation, the core network device releases the PDU session or deregisters the UE from the network slice.

[0298] Optionally, if the target time is the target moment, the core network device starts a timer, and the timeout time of the timer is the target moment. During the timer's operation, when the core network device obtains the UE's usage information of the network slice, after the timer reaches the target moment, the core network device controls the UE's use of the network slice based on the usage information obtained during the timer's operation. For example, if the core network device determines that the UE has not generated data transmission during this period based on the usage information obtained during the timer's operation, the core network device releases the PDU session or deregisters the UE from the network slice.

[0299] Based on the above embodiments, and for scenarios where the above method is applied to core network equipment (SMF or AMF), the method of this application embodiment may further include: determining the network slice interest parameters of the UE, wherein the network slice interest parameters are used to characterize the UE's preference attributes for network slices of interest, and the network slice interest parameters include one or more of the following: the identifier of the network slice of interest to the UE, the time parameter of the UE using the network slice of interest, and the location parameter of the UE using the network slice of interest; and the core network equipment controls the UE's use of network slices according to the usage information and the network slice interest parameters.

[0300] For example, if the network slice interest parameter of the UE indicates a specific time period for the terminal to use the network slice, then the core network device may temporarily not release the PDU session or temporarily not deregister the UE if it determines that the UE has not generated data transmission during that specific time period.

[0301] Based on any of the above embodiments, the method of this application embodiment may further include: obtaining feature information, the feature information including at least one of the following: UE subscription information, UE priority, and network slice data transmission information; and controlling the UE's use of network slices according to usage information and feature information.

[0302] The first network device can refer to the above-mentioned feature information when controlling the UE to use network slices. For example, when deciding whether to register a UE from a network slice, the AMF can refer to the UE's priority and prioritize registering UEs with lower priority. For example, when deciding whether to release a PDU session, the SMF can refer to the UE's priority and prioritize releasing the PDU sessions of UEs with lower priority.

[0303] The following are Figure 3b The method applied to the UE is illustrated below. (Refer to...) Figure 10 :

[0304] S1001, the UE sends a registration request message to the AMF.

[0305] The registration request message carries the identifier set of the network slice that the UE requests to use (Requested NSSAI).

[0306] S1002, AMF sends a registration acceptance message to UE.

[0307] The registration acceptance message carries the Allowed NSSAI determined by the AMF based on the UE's request and the UE's subscription information, and also provides the S-NSSAI(s) that need to perform NSAC in the Allowed NSSAI, that is, the network slice that needs to perform access control.

[0308] S1003, UE obtains information on the use of network slices.

[0309] The UE begins execution for network slices that require access control. Figure 3b The method shown obtains network slice usage information and controls the UE's use of network slices based on the usage information. Optionally, the UE sends a request message to the core network equipment based on the usage information. The request message requests the execution of one or more of the following: releasing the PDU session established by the terminal using the network slice; or deleting the identifier of the network slice from the identifier set of network slices allowed to be used by the terminal; or deregistering the terminal from the network slice.

[0310] The following applies to the UE. Figure 3b The process of the method shown is illustrated with examples.

[0311] In one implementation, the UE starts a timer for each network slice that requires access control. When the UE requests to establish a PDU session associated with that network slice (i.e., establish a PDU session using that network slice), the UE stops the timer and resets it to zero. When all PDU sessions established by the UE using that S-NSSAI are released, the UE starts the timer again. When the timer reaches its target time, if the UE has not yet established a PDU session associated with that S-NSSAI, the UE initiates a registration process. The Requested NSSAI in the registration request message sent by the UE to the AMF does not include the S-NSSAI of that network slice, thereby causing the AMF to remove the S-NSSAI from the Allowed NSSAI. The AMF then triggers the NSAC process, and the request message sent by the AMF to the NSACF includes the UE ID, the S-NSSAI of the network slice, and an update flag set to be reduced.

[0312] In another implementation, for a PDU session established by the UE using a network slice, when the UE finds that there is no data transmission in the PDU session, the UE starts a timer for the PDU session. When the timer reaches a target time, the UE initiates the PDU session release procedure. After the PDU session is released, the SMF triggers the NSAC procedure. The request message sent by the SMF to the NSACF includes the S-NSSAI of the network slice and the update flag set to decrease. After all PDU sessions have been released, the UE initiates the registration procedure. The Requested NSSAI in the registration request message sent by the UE to the AMF does not include the S-NSSAI of the network slice, thereby causing the AMF to remove the S-NSSAI from the Allowed NSSAI. The AMF then triggers the NSAC procedure, and the request message sent by the AMF to the NSACF includes the UE ID, the S-NSSAI of the network slice, and the update flag set to decrease.

[0313] In another implementation, for PDU sessions established by the UE using network slices, when the UE detects that there is no data transmission in all PDU sessions, the UE starts a timer. When the UE detects data transmission, the UE stops the timer and resets it to zero. If the timer reaches a target time, the UE initiates a registration process, causing the AMF to remove the S-NSSAI of the network slice from the Allowed NSSAI, and the AMF triggers the NSAC process. The request message sent by the AMF to the NSACF includes the UE ID, the S-NSSAI of the network slice, and an update flag set to be reduced.

[0314] In the aforementioned implementation, the target time reached by the UE's timer can be maintained locally by the UE or sent to the UE by the core network equipment (SMF or AMF). For example, the UE receives monitoring parameters sent by the core network equipment, which include time parameters; the UE detects the usage information of network slices that meet the time parameters. For example, the time parameter is the target time, which can be a target time period or a target moment.

[0315] Optionally, the core network device can determine the target time based on at least one of the following: UE usage information of the network slice, the load of the network slice, and the data transmission information of the network slice. The data transmission information of the network slice may include historical data volume and / or historical rate, etc. Optionally, when sending the target time to the UE, the core network device may also send the S-NSSAI and / or PDU session identifier of the network slice.

[0316] After receiving the target time, the UE starts the timer, sets the timer duration to the target time period, or sets the timeout time to the target time, and executes the method described above. During the timer's operation, the UE monitors the network slice usage information. If the UE does not generate data within the network slice, it releases the PDU session or deregisters the UE from the network slice.

[0317] Since a large number of UEs use network slices, if each UE performs the above operations to monitor network slice usage information, it will generate a large amount of signaling overhead. Therefore, this application embodiment also proposes that the core network device can decide whether to monitor the network slice usage information of all or part of the UEs using the network slice based on the network slice load.

[0318] When the load on a network slice reaches a first preset value, the core network device identifies the UEs using the network slice and sends a first message to the target UE among them. This first message includes the identifier of the network slice, i.e., the S-NSSAI of the network slice. The first message instructs the target UE to begin monitoring the usage information of the network slice corresponding to this identifier. Thus, the target UE begins performing operations on that network slice. Figure 3b The method shown is as follows: the first message is sent to the target UE by the core network device after identifying the target UE among the UEs using network slicing.

[0319] When the load on a network slice is less than a second preset value, the core network device sends a second message to the target UE. This second message includes the identifier of the network slice and instructs the target UE to stop monitoring the usage information of the network slice corresponding to that identifier. Consequently, the target UE stops performing operations on that network slice. Figure 3bThe method shown.

[0320] Reference Figure 11 Please provide an explanation.

[0321] S1101, NSACF sends a network slice UE count notification message (Nnsacf_NumberOfUEsPerSliceEACNotify) to AMF. This notification message includes the S-NSSAI of the network slice. When the number of UEs in a network slice reaches a specific value, NSACF sends this notification message to AMF to indicate that the load on the network slice has reached a first preset value.

[0322] S1102, NWDAF provides network slice load notification to AMF to indicate that the load of the network slice has reached a first preset value.

[0323] It should be noted that the execution of S1101 and S1102 has no order or dependency. AMF can obtain the load information of the network slice from NSACF and / or NWDAF.

[0324] S1103, AMF determines the target UE from the UEs using network slicing.

[0325] Based on the network slice load information obtained from NSACF and / or NWDAF, if the AMF determines that the network slice is overloaded, it will then determine which UEs are using the network slice based on the UE's Allowed NSSAI, and decide which target UEs among these UEs will begin monitoring network slice usage information. The target UEs can be all or some of the UEs using the network slice.

[0326] Optionally, the AMF obtains one or more of the following: the UE's subscription information, the UE's priority (e.g., whether the UE is a gold user, a bronze user, or the priority of the network slice), the amount of data the UE uses in the network slice, the throughput, the data transmission rate, etc., and determines the target UE from among the UEs using the network slice based on the above information.

[0327] AMF can also include the S-NSSAI of the network slice that is monitoring usage information in the UE context, or AMF can maintain a list of UE IDs that are monitoring usage information for the network slice.

[0328] S1104, AMF sends a first message (registration acceptance message or UE configuration update message) to the target UE. The first message includes S-NSSAI for starting to monitor network slices for usage information.

[0329] S1105. For these network slices, the target UE begins monitoring usage information, that is, the target UE begins executing... Figure 3b The method shown.

[0330] Similar to the above process, the AMF can determine that the network slice has a light load based on the network slice load information obtained from the NSACF and / or NWDAF. It can then send a registration acceptance message or a UE configuration update message to the UE that is monitoring the usage information of that network slice. This message includes the S-NSSAI of the network slice, instructing the UE to stop monitoring the usage information of that network slice; that is, the UE stops performing operations for that network slice. Figure 3b The method shown.

[0331] The embodiments provided in this application avoid the UE occupying the number of registered UEs or PDU sessions of a network slice when the network slice is not used, thereby improving the resource utilization of the network slice.

[0332] Figure 12 Schematic diagram of the network slicing access control device provided in the embodiments of this application Figure 1 Applied to primary network devices, such as... Figure 12 As shown, the network slicing access control device includes a memory 1201, a transceiver 1202, and a processor 1203:

[0333] Memory 1201 is used to store computer programs;

[0334] Transceiver 1202 is used to send and receive data under the control of processor 1203;

[0335] Processor 1203 is used to read the computer program stored in memory 1201 and perform the following operations:

[0336] Obtain network slice usage information, which refers to the information about how the terminal uses the network slice;

[0337] Based on usage information, network slicing is used to control the terminal.

[0338] In one implementation, the processor 1203 is specifically configured to perform the following operations:

[0339] Obtain network slice usage information from the second network device;

[0340] The second network device includes one or more of the following: User Plane Function Entity (UPF), Policy Control Function Entity (PCF), Network Data Analysis Function Entity (NWDAF), Radio Access Network (RAN), or Receive Session Management Function Entity (SMF).

[0341] In one implementation, the usage information includes one or more of the following:

[0342] The data volume of the PDU session established by the terminal using the network slice, the data transmission information of the PDU session, and the status of the PDU session;

[0343] Data volume and / or data transmission rate, wherein the data volume is used to characterize the amount of data generated by the terminal using the network slice, and the data transmission rate is used to characterize the rate at which the terminal transmits data using the network slice;

[0344] Data analysis information, which is used to characterize the information on data analysis performed by the terminal using the network slice.

[0345] In one embodiment, the processor 1203 is configured to perform the following operations:

[0346] Obtain usage information for network slices that meet the target time requirements.

[0347] In one implementation, the target time is determined based on one or more of the following: the load of the network slice, the data transmission information of the network slice, and the usage information of the network slice.

[0348] The data transmission information of the network slice is used to characterize information related to the data transmission performed by the network slice.

[0349] In one embodiment, the processor 1203 is configured to perform the following operations:

[0350] The network slice interest parameters of the terminal are determined. The network slice interest parameters are used to characterize the terminal's preference attributes for network slices of interest. The network slice interest parameters include one or more of the following: the identifier of the network slice of interest of the terminal, the time parameter of the terminal using the network slice of interest, and the location parameter of the terminal using the network slice of interest.

[0351] The terminal's use of the network slice is controlled based on the usage information and the network slice's interest parameters.

[0352] In one embodiment, the processor 1203 is configured to perform the following operations:

[0353] The feature information is determined, which includes one or more of the following: the terminal's subscription information, the terminal's priority, and the network slice's data transmission information;

[0354] Based on the usage information and the feature information, the terminal is controlled using the network slice.

[0355] In one embodiment, the processor 1203 is configured to perform one or more of the following operations:

[0356] Release all or part of the PDU sessions established by the terminal using the network slice;

[0357] Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal;

[0358] Trigger a deregistration operation to stop the terminal from using the network slice.

[0359] It should be noted that the apparatus provided in this application can implement all the method steps implemented by the first network device in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0360] Figure 13 Schematic diagram of the network slicing access control device provided in the embodiments of this application Figure 2 Applied to terminals, such as... Figure 13 As shown, the network slicing access control device includes a memory 1301, a transceiver 1302, and a processor 1303:

[0361] Memory 1301 is used to store computer programs;

[0362] Transceiver 1302 is used to send and receive data under the control of processor 1303;

[0363] Processor 1303 is used to read computer programs stored in memory 1301 and perform the following operations:

[0364] Monitor network slice usage information, where the usage information refers to the information about how the terminal uses the network slice;

[0365] The network slices used are controlled based on the usage information.

[0366] In one implementation, the usage information includes one or more of the following:

[0367] The data volume of the PDU session established by the terminal using the network slice, the data transmission information of the PDU session, and the status of the PDU session;

[0368] Data volume and / or data transmission rate, wherein the data volume is used to characterize the amount of data generated by the terminal using the network slice, and the data transmission rate is used to characterize the rate at which the terminal transmits data using the network slice.

[0369] In one embodiment, the processor 1303 is configured to perform the following operations:

[0370] The system receives a first message sent by a core network device. The first message includes an identifier of the network slice. The first message is used to indicate that monitoring of the usage information of the network slice corresponding to the identifier has begun.

[0371] Based on the first message, monitoring of the usage information of the network slice corresponding to the identifier is initiated.

[0372] In one implementation, the first message is sent by the core network device when the load on the network slice reaches a first preset value.

[0373] In one embodiment, the processor 1303 is further configured to perform the following operations:

[0374] The system receives a second message from the core network device, the second message including the identifier of the network slice, and the second message is used to indicate to stop monitoring the usage information of the network slice corresponding to the identifier.

[0375] In one implementation, the second message is sent when the load on the network slice is less than a second preset value.

[0376] In one embodiment, the processor 1303 is configured to perform the following operations:

[0377] Receive monitoring parameters sent by the core network equipment, wherein the monitoring parameters include time parameters;

[0378] Monitor the usage information of network slices that meet the aforementioned time parameters.

[0379] In one implementation, the processor 1303 is configured to perform the following operations:

[0380] Based on the usage information, a request message is sent to the core network device, the request message being used to request one or more of the following operations:

[0381] Release all or part of the PDU sessions established by the terminal using the network slice;

[0382] Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal;

[0383] Trigger a deregistration operation to stop the terminal from using the network slice.

[0384] It should be noted that the device provided in this application can implement all the method steps implemented by the terminal in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0385] Figure 14 Schematic diagram three of the network slicing access control device provided in this embodiment of the application. This device is applied to a first network device, such as… Figure 14 As shown, the network slicing access control device 1400 includes:

[0386] The acquisition unit 1401 is used to acquire network slice usage information, wherein the usage information is information about the terminal using the network slice;

[0387] Control unit 1402 is used to control the terminal using the network slice according to the usage information.

[0388] In one embodiment, the acquisition unit 1401 is used for:

[0389] Obtain network slice usage information from the second network device;

[0390] The second network device includes one or more of the following: User Plane Function Entity (UPF), Policy Control Function Entity (PCF), Network Data Analysis Function Entity (NWDAF), Radio Access Network (RAN), or Receive Session Management Function Entity (SMF).

[0391] In one implementation, the usage information includes one or more of the following:

[0392] The data volume of the PDU session established by the terminal using the network slice, the data transmission information of the PDU session, and the status of the PDU session;

[0393] Data volume and / or data transmission rate, wherein the data volume is used to characterize the amount of data generated by the terminal using the network slice, and the data transmission rate is used to characterize the rate at which the terminal transmits data using the network slice;

[0394] Data analysis information, which is used to characterize the information on data analysis performed by the terminal using the network slice.

[0395] In one embodiment, the acquisition unit 1401 is used for:

[0396] Obtain usage information for network slices that meet the target time requirements.

[0397] In one implementation, the target time is determined based on one or more of the following: the load of the network slice, the data transmission information of the network slice, and the usage information of the network slice.

[0398] The data transmission information of the network slice is used to characterize information related to the data transmission performed by the network slice.

[0399] In one embodiment, the control unit 1402 is used to:

[0400] The network slice interest parameters of the terminal are determined. The network slice interest parameters are used to characterize the terminal's preference attributes for network slices of interest. The network slice interest parameters include one or more of the following: the identifier of the network slice of interest of the terminal, the time parameter of the terminal using the network slice of interest, and the location parameter of the terminal using the network slice of interest.

[0401] The terminal's use of the network slice is controlled based on the usage information and the network slice's interest parameters.

[0402] In one embodiment, the control unit 1402 is used to:

[0403] The feature information is determined, which includes one or more of the following: the terminal's subscription information, the terminal's priority, and the network slice's data transmission information;

[0404] Based on the usage information and the feature information, the terminal is controlled using the network slice.

[0405] In one embodiment, the control unit 1402 is used to:

[0406] Based on the usage information, perform one or more of the following operations:

[0407] Release all or part of the PDU sessions established by the terminal using the network slice;

[0408] Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal;

[0409] Trigger a deregistration operation to stop the terminal from using the network slice.

[0410] It should be noted that the apparatus provided in this application can implement all the method steps implemented by the first network device in the above method embodiment and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiment will not be described in detail here.

[0411] Figure 15 Schematic diagram of the network slicing access control device provided in the embodiments of this application Figure 4 This device is used in terminals. For example... Figure 15 As shown, the network slicing access control device 1500 includes:

[0412] Monitoring unit 1501 is used to monitor network slice usage information, wherein the usage information is information about the terminal's use of the network slice;

[0413] Control unit 1502 is used to control the network slice in use based on the usage information.

[0414] In one implementation, the usage information includes one or more of the following:

[0415] The data volume of the PDU session established by the terminal using the network slice, the data transmission information of the PDU session, and the status of the PDU session;

[0416] Data volume and / or data transmission rate, wherein the data volume is used to characterize the amount of data generated by the terminal using the network slice, and the data transmission rate is used to characterize the rate at which the terminal transmits data using the network slice.

[0417] In one embodiment, the monitoring unit 1501 is used for:

[0418] The system receives a first message sent by a core network device. The first message includes an identifier of the network slice. The first message is used to indicate that monitoring of the usage information of the network slice corresponding to the identifier has begun.

[0419] Based on the first message, monitoring of the usage information of the network slice corresponding to the identifier is initiated.

[0420] In one implementation, the first message is sent by the core network device when the load on the network slice reaches a first preset value.

[0421] In one embodiment, the monitoring unit 1501 is further configured to:

[0422] The system receives a second message from the core network device, the second message including the identifier of the network slice, and the second message is used to indicate to stop monitoring the usage information of the network slice corresponding to the identifier.

[0423] In one implementation, the second message is sent when the load on the network slice is less than a second preset value.

[0424] In one embodiment, the monitoring unit 1501 is used for:

[0425] Receive monitoring parameters sent by the core network equipment, wherein the monitoring parameters include time parameters;

[0426] Monitor the usage information of network slices that meet the aforementioned time parameters.

[0427] In one embodiment, the control unit 1502 is used to:

[0428] Based on the usage information, a request message is sent to the core network device, the request message being used to request one or more of the following operations:

[0429] Release all or part of the PDU sessions established by the terminal using the network slice;

[0430] Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal;

[0431] Trigger a deregistration operation to stop the terminal from using the network slice.

[0432] It should be noted that the device provided in this application can implement all the method steps implemented by the terminal device in the above method embodiments and can achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here.

[0433] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0434] If the aforementioned integrated units are implemented as software functional units and sold or used as independent products, they can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0435] This application also provides a computer-readable storage medium storing a computer program for causing a computer to execute the method executed by the UE or core network device in the above method embodiments.

[0436] Computer-readable storage media can be any available medium or data storage device that a computer can access, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MOs), etc.), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).

[0437] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the method executed by the UE or core network device in the above method embodiments.

[0438] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0439] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0440] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0441] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0442] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for controlling network slicing, characterized in that, Applied to the first network device, including: Obtain network slice usage information, wherein the usage information is information about how the terminal uses the network slice; Based on the usage information, the terminal is controlled to use the network slice, wherein if the usage information indicates that the terminal has not generated data within the network slice, the control of the terminal to use the network slice includes at least one of the following: Release all or part of the PDU sessions established by the terminal using the network slice; Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal; Trigger a deregistration operation to stop the terminal from using the network slice.

2. The method according to claim 1, characterized in that, The acquisition of network slice usage information includes: Obtain network slice usage information from the second network device; The second network device includes one or more of the following: User Plane Function Entity (UPF), Policy Control Function Entity (PCF), Network Data Analysis Function Entity (NWDAF), Radio Access Network (RAN), or Receive Session Management Function Entity (SMF).

3. The method according to claim 2, characterized in that, The usage information includes one or more of the following: The data volume of the PDU session established by the terminal using the network slice, the data transmission information of the PDU session, and the status of the PDU session; Data volume and / or data transmission rate, wherein the data volume is used to characterize the amount of data generated by the terminal using the network slice, and the data transmission rate is used to characterize the rate at which the terminal transmits data using the network slice; Data analysis information, which is used to characterize the information on data analysis performed by the terminal using the network slice.

4. The method according to claim 1, characterized in that, The acquisition of network slice usage information includes: Obtain usage information for network slices that meet the target time requirements.

5. The method according to claim 4, characterized in that, The target time is determined based on one or more of the following: the load of the network slice, the data transmission information of the network slice, and the usage information of the network slice. The data transmission information of the network slice is used to characterize information related to the data transmission performed by the network slice.

6. The method according to claim 1, characterized in that, The step of controlling the terminal to use the network slice based on the usage information includes: The network slice interest parameters of the terminal are determined. The network slice interest parameters are used to characterize the terminal's preference attributes for network slices of interest. The network slice interest parameters include one or more of the following: the identifier of the network slice of interest of the terminal, the time parameter of the terminal using the network slice of interest, and the location parameter of the terminal using the network slice of interest. The terminal's use of the network slice is controlled based on the usage information and the network slice's interest parameters.

7. The method according to claim 1, characterized in that, The step of controlling the terminal to use the network slice based on the usage information includes: The feature information is determined, which includes one or more of the following: the terminal's subscription information, the terminal's priority, and the network slice's data transmission information; Based on the usage information and the feature information, the terminal is controlled using the network slice.

8. A method for controlling network slicing, characterized in that, Applied to terminals, including: Monitor network slice usage information, where the usage information refers to the information about how the terminal uses the network slice; Based on the usage information, the network slice in use is controlled, wherein if the usage information indicates that the terminal has not generated data within the network slice, controlling the network slice in use includes at least one of the following: Release the PDU session established by the UE using the network slice; remove the identifier of the network slice from the identifier set of network slices that the UE is allowed to use; trigger the execution of the deregistration operation so that the UE stops using the network slice.

9. The method according to claim 8, characterized in that, The usage information includes one or more of the following: The data volume of the PDU session established by the terminal using the network slice, the data transmission information of the PDU session, and the status of the PDU session; Data volume and / or data transmission rate, wherein the data volume is used to characterize the amount of data generated by the terminal using the network slice, and the data transmission rate is used to characterize the rate at which the terminal transmits data using the network slice.

10. The method according to claim 8, characterized in that, The monitoring network slice usage information includes: The system receives a first message sent by a core network device. The first message includes an identifier of the network slice. The first message is used to indicate that monitoring of the usage information of the network slice corresponding to the identifier has begun. Based on the first message, monitoring of the usage information of the network slice corresponding to the identifier is initiated.

11. The method according to claim 10, characterized in that, The first message is sent by the core network device when the load of the network slice reaches a first preset value.

12. The method according to claim 10, characterized in that, The method further includes: The system receives a second message from the core network device, the second message including the identifier of the network slice, and the second message is used to indicate to stop monitoring the usage information of the network slice corresponding to the identifier.

13. The method according to claim 12, characterized in that, The second message is sent when the load on the network slice is less than a second preset value.

14. The method according to claim 8, characterized in that, The monitoring network slice usage information includes: Receive monitoring parameters sent by the core network equipment, wherein the monitoring parameters include time parameters; Monitor the usage information of network slices that meet the aforementioned time parameters.

15. The method according to any one of claims 8-14, characterized in that, Based on the usage information, the terminal is controlled using the network slice, including: Based on the usage information, a request message is sent to the core network device, the request message being used to request one or more of the following operations: Release all or part of the PDU sessions established by the terminal using the network slice; Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal; Trigger a deregistration operation to stop the terminal from using the network slice.

16. A network slicing access control device, characterized in that, Applied to the first network device, including memory, transceiver, and processor: The memory is used to store computer programs; The transceiver is used to send and receive data under the control of the processor; The processor is configured to read the computer program stored in the memory and perform the following operations: Obtain network slice usage information, wherein the usage information is information about how the terminal uses the network slice; Based on the usage information, the terminal is controlled to use the network slice, wherein if the usage information indicates that the terminal has not generated data within the network slice, the control of the terminal to use the network slice includes at least one of the following: Release all or part of the PDU sessions established by the terminal using the network slice; Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal; Trigger a deregistration operation to stop the terminal from using the network slice.

17. The apparatus according to claim 16, characterized in that, The processor is specifically used to perform the following operations: Obtain network slice usage information from the second network device; The second network device includes one or more of the following: User Plane Function Entity (UPF), Policy Control Function Entity (PCF), Network Data Analysis Function Entity (NWDAF), Radio Access Network (RAN), or Receive Session Management Function Entity (SMF).

18. The apparatus according to claim 16 or 17, characterized in that, The processor is used to perform the following operations: The network slice interest parameters of the terminal are determined. The network slice interest parameters are used to characterize the terminal's preference attributes for network slices of interest. The network slice interest parameters include one or more of the following: the identifier of the network slice of interest of the terminal, the time parameter of the terminal using the network slice of interest, and the location parameter of the terminal using the network slice of interest. The terminal's use of the network slice is controlled based on the usage information and the network slice's interest parameters.

19. A network slicing access control device, characterized in that, Applications in terminals, including memory, transceiver, and processor: The memory is used to store computer programs; The transceiver is used to send and receive data under the control of the processor; The processor is configured to read the computer program stored in the memory and perform the following operations: Monitor network slice usage information, where the usage information refers to the information about how the terminal uses the network slice; Based on the usage information, the network slice in use is controlled, wherein if the usage information indicates that the terminal has not generated data within the network slice, controlling the network slice in use includes at least one of the following: Release the PDU session established by the UE using the network slice; remove the identifier of the network slice from the identifier set of network slices that the UE is allowed to use; trigger the execution of the deregistration operation so that the UE stops using the network slice.

20. The apparatus according to claim 19, characterized in that, The processor is used to perform the following operations: The system receives a first message sent by a core network device. The first message includes an identifier of the network slice. The first message is used to indicate that monitoring of the usage information of the network slice corresponding to the identifier has begun. Based on the first message, monitoring of the usage information of the network slice corresponding to the identifier is initiated.

21. The apparatus according to claim 20, characterized in that, The processor is also used to perform the following operations: The system receives a second message from the core network device, the second message including the identifier of the network slice, and the second message is used to indicate to stop monitoring the usage information of the network slice corresponding to the identifier.

22. A network slicing access control device, applied to a first network device, characterized in that, include: An acquisition unit is used to acquire network slice usage information, wherein the usage information is information about how the terminal uses the network slice; A control unit is configured to control the terminal's use of the network slice based on the usage information, wherein if the usage information indicates that the terminal has not generated data within the network slice, the control of the terminal's use of the network slice includes at least one of the following: Release all or part of the PDU sessions established by the terminal using the network slice; Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the terminal; Trigger a deregistration operation to stop the terminal from using the network slice.

23. A network slicing access control device, applied to a terminal, characterized in that, include: The monitoring unit is used to monitor the usage information of the network slice, wherein the usage information is the information of the terminal using the network slice; A control unit is configured to control the network slice in use based on the usage information, wherein if the usage information indicates that the terminal has not generated data within the network slice, controlling the network slice in use includes at least one of the following: Release the PDU session established by the UE using network slicing; Remove the identifier of the network slice from the set of identifiers of the network slices that are allowed to be used by the UE; trigger the execution of the deregistration operation so that the UE stops using the network slice.

24. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program for causing a computer to perform the method of any one of claims 1-15.

Images