A method and device for reporting slice status information of multiple slice admission control functions NSACF

Abstract

The embodiment of the present application discloses a method and device for reporting slice status information of multiple slice admission control functions NSACF, which can be applied to the fifth generation (5th generation, 5G) mobile communication system, 5G new radio (new radio, NR) system, or other future new mobile communication systems and other communication systems. The method includes: subscribing the slice status information of the network slice to multiple NSACFs corresponding to the network slice through the network open function NEF; obtaining the slice status information of the network slice reported by the multiple NSACFs through the NEF. By implementing the embodiment of the present application, the slice status information of the network slice can be subscribed to the multiple NSACFs corresponding to the network slice through the NEF, and the slice status information of the network slice reported by the multiple NSACFs can be obtained and fed back to the AF or ASP, so as to avoid errors in uploading the network slice status information, thereby helping to improve the user experience.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a method and device for reporting slice status information of multiple slice admission control functions (NSACFs). Background Art

[0002] In wireless communications, network slices can provide complete network functions, such as radio access network functions, core network functions, and IP Multimedia Subsystem (IMS) functions. A network can support one or more network slices. Network slices can provide different committed services and are dedicated to users. Slices with the same service or slice but different slice identifiers may have different single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI).

[0003] The network slice admission control function (NSACF) is used to monitor the number of registered terminals (user equipment, UE) and PDU sessions (PDU sessions) of network slices that support the NSAC function.

[0004] When multiple NSACFs are deployed in the network, how the network accurately and in real time obtains the status information of these network slices, such as the current number of registered users in the slice, the number of currently activated Packet Data Unit (PDU) sessions, the current number of registered users of the slice and / or the proportion of the number of activated Packet Control Unit (PCU) sessions to the overall threshold of the slice, and effectively transmits the obtained information to the Application Function (AF) or Application Service Provider (ASP) as required to ensure the correct execution of the function and process optimization, as well as a good service experience for users, is still a problem to be solved in 5G networks. Summary of the invention

[0005] The embodiment of the present application provides a method and device for reporting slice status information of multiple slice admission control functions NSACF, which can be applied to communication systems such as the fifth generation (5G) mobile communication system, the 5G new radio (NR) system, or other future new mobile communication systems. The NEF subscribes to the slice status information of the network slice to the multiple NSACFs corresponding to the network slice, obtains the slice status information of the network slice reported by the multiple NSACFs and feeds it back to the AF or ASP, avoids errors in uploading the network slice status information, and is beneficial to improving the user experience.

[0006] In a first aspect, an embodiment of the present application provides a method for reporting slice status information of multiple slice admission control functions NSACF, which is applied to a first NSACF, and the method includes:

[0007] Subscribe the slice status information of the network slice to multiple NSACFs corresponding to the network slice through the network open function NEF;

[0008] The slice status information of the network slice reported by the multiple NSACFs is obtained through the NEF.

[0009] Optionally, also include:

[0010] Receive a first network slice status subscription request sent by an application function AF or an application service provider ASP, wherein the first network slice status subscription request includes the network slice.

[0011] Optionally, the subscribing to the slice status information of the network slice to multiple NSACFs corresponding to the network slice through the network open function NEF includes:

[0012] Send a second network slice status subscription request to the NEF, wherein the NEF sends the second network slice status subscription request to multiple NSACFs corresponding to the network slice, wherein the first NSACF belongs to the multiple NSACFs corresponding to the network slice.

[0013] Optionally, the subscribing to the slice status information of the network slice to multiple NSACFs corresponding to the network slice through the network open function NEF includes:

[0014] Send a second network slice status subscription request to the NEF, wherein the NEF sends the subscription request to a second NSACF among the multiple NSACFs corresponding to the network slice, wherein the first NSACF belongs to the multiple NSACFs corresponding to the network slice.

[0015] Optionally, also include:

[0016] Generate network slice status response information according to the status information of the network slice among the multiple NSACFs;

[0017] The network slice status response information is sent to the AF or ASP.

[0018] Optionally, the first slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

[0019] Optionally, the subscription event includes at least one of the following:

[0020] The number of terminals registered on the requested network slice;

[0021] The number of packet data unit (PDU) sessions established on the requested network slice;

[0022] The ratio of the number of terminals registered on the requested network slice to the maximum number of terminals allowed to be registered;

[0023] The ratio of the number of PDU sessions established on the requested network slice to the maximum number of PDU sessions allowed to be established;

[0024] The number of registered terminals on the requested network slice and the ratio of the number of registered terminals to the maximum number of allowed registered terminals;

[0025] The number of established PDU sessions on the requested network slice and the ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.

[0026] Optionally, the subscription event screening information includes at least one of the following:

[0027] Single network slice selection assistance information S-NSSAI of the requested network slice;

[0028] The registration area RA of the requested network slice;

[0029] A combination of the S-NSSAI of the requested network slice and the data network name DNN;

[0030] The area of ​​interest IoA of the requested network slice.

[0031] Optionally, the subscription event report mode information includes at least one of the following:

[0032] The threshold that triggers the report;

[0033] The periodic interval for triggering reporting.

[0034] Optionally, the first network slice status subscription request also includes an immediate reporting flag, wherein the immediate reporting flag is used to instruct the first NSACF to immediately send the network slice status response information upon receiving the network slice status subscription request.

[0035] Optionally, the generating network slice status response information according to the status information of the network slice among the multiple NSACFs includes:

[0036] The status information of the network slice among the multiple NSACFs is aggregated to generate the slice status response information.

[0037] Optionally, also include:

[0038] The multiple NSACFs corresponding to the network slice are determined through the network configuration or operator policy in the NEF.

[0039] Optionally, the first NSACF is a master NSACF or a proxy NSACF among multiple NSACFs corresponding to the network slice.

[0040] Optionally, the second network slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

[0041] Optionally, also include:

[0042] The network slice status response information is filtered according to the subscription event filtering information.

[0043] Optionally, also include:

[0044] Determine whether the reporting conditions are met based on the subscription event report mode information;

[0045] If the reporting conditions are met, the network slice status response information is reported.

[0046] Optionally, the receiving a slice status subscription request sent by an AF or an ASP includes:

[0047] If the AF or ASP is an untrusted AF or ASP, the slice status subscription request sent by the AF or ASP is received through NEF.

[0048] Optionally, the first NSACF is selected by the NEF.

[0049] Optionally, the first NSACF is selected by the NEF through NRF, or the first NSACF is selected by the NEF through local configuration.

[0050] In a second aspect, an embodiment of the present application provides another method for reporting slice status information of multiple slice admission control functions NSACF, which is applied to NEF, and the method includes:

[0051] Receive a first network slice status subscription request sent by the first NSACF, wherein the first network slice event slice status subscription request includes a network slice;

[0052] Subscribe slice status information of the network slice to multiple NSACFs corresponding to the network slice;

[0053] Obtain slice status information of the network slice reported by the multiple NSACFs;

[0054] The slice status information is sent to the first NSACF.

[0055] Optionally, the subscribing to the slice status information of the network slice among the multiple NSACFs corresponding to the network slice includes:

[0056] Receiving a second network slice status subscription request sent by the first NSACF;

[0057] Send the second network slice status subscription request to multiple NSACFs corresponding to the network slice, wherein the first NSACF belongs to the multiple NSACFs corresponding to the network slice.

[0058] Optionally, the subscribing to the slice status information of the network slice among the multiple NSACFs corresponding to the network slice includes:

[0059] Receiving a second network slice status subscription request sent by the first NSACF;

[0060] The subscription request is sent to a second NSACF among multiple NSACFs corresponding to the network slice, wherein the first NSACF belongs to the multiple NSACFs corresponding to the network slice.

[0061] Optionally, also include:

[0062] Generate network slice status response information according to the status information of the network slice among the multiple NSACFs;

[0063] The network slice status response information is sent to the AF or ASP.

[0064] Optionally, the first slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

[0065] Optionally, the subscription event includes at least one of the following:

[0066] The number of terminals registered on the requested network slice;

[0067] The number of packet data unit (PDU) sessions established on the requested network slice;

[0068] The ratio of the number of terminals registered on the requested network slice to the maximum number of terminals allowed to be registered;

[0069] The ratio of the number of PDU sessions established on the requested network slice to the maximum number of PDU sessions allowed to be established;

[0070] The number of registered terminals on the requested network slice and the ratio of the number of registered terminals to the maximum number of allowed registered terminals;

[0071] The number of established PDU sessions on the requested network slice and the ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.

[0072] Optionally, the subscription event screening information includes at least one of the following:

[0073] Single network slice selection assistance information S-NSSAI of the requested network slice;

[0074] The registration area RA of the requested network slice;

[0075] A combination of the S-NSSAI of the requested network slice and the data network name DNN;

[0076] The area of ​​interest IoA of the requested network slice.

[0077] Optionally, the subscription event report mode information includes at least one of the following:

[0078] The threshold that triggers the report;

[0079] The periodic interval for triggering reporting.

[0080] Optionally, the generating network slice status response information according to the status information of the network slice among the multiple NSACFs includes:

[0081] The status information of the network slice among the multiple NSACFs is aggregated to generate the slice status response information.

[0082] Optionally, the first network slice status subscription request also includes an immediate reporting flag, wherein the immediate reporting flag is used to instruct the first NSACF to immediately send the network slice status response information upon receiving the first network slice status subscription request.

[0083] Optionally, also include:

[0084] The multiple NSACFs corresponding to the network slice are determined through network configuration or operator policy.

[0085] Optionally, the first NSACF is a master NSACF or a proxy NSACF among multiple NSACFs corresponding to the network slice.

[0086] Optionally, the second network slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

[0087] Optionally, the receiving a slice status subscription request sent by an AF or an ASP includes:

[0088] If the AF or ASP is an untrusted AF or ASP, receive the slice status subscription request sent by the AF or ASP.

[0089] Optionally, also include:

[0090] The first NSACF was selected.

[0091] Optionally, the selecting and obtaining the first NSACF includes:

[0092] The first NSACF is obtained by NRF selection;

[0093] Alternatively, the first NSACF is obtained through local configuration selection.

[0094] In a third aspect, an embodiment of the present application provides another method for reporting slice status information of multiple slice admission control functions NSACF, which is applied to AF or ASP, and the method includes:

[0095] Sending a first network slice status subscription request to a first NSACF, wherein the first network slice status subscription request includes a network slice;

[0096] Receive the network slice status response information sent by the first NSACF.

[0097] Optionally, the first network slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

[0098] Optionally, the subscription event includes at least one of the following:

[0099] The number of terminals registered on the requested network slice;

[0100] The number of packet data unit (PDU) sessions established on the requested network slice;

[0101] The ratio of the number of terminals registered on the requested network slice to the maximum number of terminals allowed to be registered;

[0102] The ratio of the number of PDU sessions established on the requested network slice to the maximum number of PDU sessions allowed to be established;

[0103] The number of registered terminals on the requested network slice and the ratio of the number of registered terminals to the maximum number of allowed registered terminals;

[0104] The number of established PDU sessions on the requested network slice and the ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.

[0105] Optionally, the subscription event screening information includes at least one of the following:

[0106] Single network slice selection assistance information S-NSSAI of the requested network slice;

[0107] The registration area RA of the requested network slice;

[0108] A combination of the S-NSSAI of the requested network slice and the data network name DNN;

[0109] The area of ​​interest IoA of the requested network slice.

[0110] Optionally, the subscription event report mode information includes at least one of the following:

[0111] The threshold that triggers the report;

[0112] The periodic interval for triggering reporting.

[0113] Optionally, the first network slice status subscription request also includes an immediate reporting flag, wherein the immediate reporting flag is used to instruct the first NSACF to immediately send the network slice status response information upon receiving the first network slice status subscription request.

[0114] Optionally, the multiple NSACFs corresponding to the network slice are determined by the network configuration or operator policy in the NEF.

[0115] Optionally, the first NSACF is a master NSACF or a proxy NSACF among multiple NSACFs corresponding to the requested network slice.

[0116] Optionally, the first NSACF is selected by the NEF through NRF, or the first NSACF is selected by the NEF through local configuration.

[0117] In a fourth aspect, an embodiment of the present application provides a communication device, which has some or all of the functions of the terminal device in the method described in the first aspect above, such as the functions of the communication device may have some or all of the functions in the embodiments of the present application, or may have the functions of implementing any one of the embodiments of the present application separately. The functions may be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0118] In one implementation, the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform the corresponding functions in the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is used to couple with the transceiver module and the processing module, and store the computer programs and data necessary for the communication device.

[0119] As an example, the processing module may be a processor, the transceiver module may be a transceiver or a communication interface, and the storage module may be a memory. In one implementation, the communication device includes:

[0120] A subscription module, used to subscribe to slice status information of the network slice from multiple NSACFs corresponding to the network slice through the network open function NEF;

[0121] An acquisition module is used to obtain the slice status information of the network slice reported by the multiple NSACFs through the NEF.

[0122] In a fifth aspect, an embodiment of the present application provides another communication device, which has some or all of the functions of the network device in the method example described in the second aspect above, such as the functions of the communication device may have some or all of the functions in the embodiments of the present application, or may have the functions of implementing any one of the embodiments of the present application separately. The functions may be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above functions.

[0123] In one implementation, the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform the corresponding functions in the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is used to couple with the transceiver module and the processing module, and store the computer programs and data necessary for the communication device.

[0124] As an example, the processing module may be a processor, the transceiver module may be a transceiver or a communication interface, and the storage module may be a memory. In one implementation, the communication device includes:

[0125] A first receiving module is used to receive a first network slice status subscription request sent by the first NSACF, wherein the first network slice event slice status subscription request includes a network slice;

[0126] A first sending module, configured to subscribe slice status information of the network slice to multiple NSACFs corresponding to the network slice;

[0127] A second receiving module is used to obtain the slice status information of the network slice reported by the multiple NSACFs;

[0128] The second sending module is used to send the slice status information to the first NSACF.

[0129] In a sixth aspect, an embodiment of the present application provides another communication device, which has some or all of the functions of the network device in the method example described in the third aspect above, such as the functions of the communication device may have the functions of some or all of the embodiments in the present application, or may have the functions of implementing any one of the embodiments in the present application separately. The functions may be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above functions.

[0130] In one implementation, the structure of the communication device may include a transceiver module and a processing module, and the processing module is configured to support the communication device to perform the corresponding functions in the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is used to couple with the transceiver module and the processing module, and store the computer programs and data necessary for the communication device.

[0131] As an example, the processing module may be a processor, the transceiver module may be a transceiver or a communication interface, and the storage module may be a memory. In one implementation, the communication device includes:

[0132] A third sending module is used to send a first network slice status subscription request to the first NSACF, wherein the first network slice status subscription request includes a network slice;

[0133] The third receiving module is used to receive the network slice status response information sent by the first NSACF.

[0134] In a seventh aspect, an embodiment of the present application provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the first aspect is executed.

[0135] In an eighth aspect, an embodiment of the present application provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the second aspect is executed.

[0136] In a ninth aspect, an embodiment of the present application provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the third aspect is executed.

[0137] In the tenth aspect, an embodiment of the present application provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first aspect above.

[0138] In the eleventh aspect, an embodiment of the present application provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the second aspect above.

[0139] In the twelfth aspect, an embodiment of the present application provides a communication device, which includes a processor and a memory, in which a computer program is stored; the processor executes the computer program stored in the memory so that the communication device executes the method described in the third aspect above.

[0140] In a thirteenth aspect, an embodiment of the present application provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first aspect above.

[0141] In a fourteenth aspect, an embodiment of the present application provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the second aspect above.

[0142] In a fifteenth aspect, an embodiment of the present application provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the third aspect above.

[0143] In the sixteenth aspect, an embodiment of the present application provides a slice status information reporting system of multiple slice admission control functions NSACF, the system including the communication device described in the fourth aspect, the communication device described in the fifth aspect, and the communication device described in the sixth aspect, or the system includes the communication device described in the seventh aspect, the communication device described in the eighth aspect, and the communication device described in the ninth aspect, or the system includes the communication device described in the tenth aspect, the communication device described in the eleventh aspect, and the communication device described in the twelfth aspect, or the system includes the communication device described in the thirteenth aspect, the communication device described in the fourteenth aspect, and the communication device described in the fifteenth aspect.

[0144] In the seventeenth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for the above-mentioned terminal device, and when the instructions are executed, the terminal device executes the method described in the first aspect.

[0145] In an eighteenth aspect, an embodiment of the present invention provides a readable storage medium for storing instructions used by the above-mentioned network device. When the instructions are executed, the network device executes the method described in the above-mentioned second aspect.

[0146] In the nineteenth aspect, an embodiment of the present invention provides a readable storage medium for storing instructions used by the above-mentioned network device. When the instructions are executed, the network device executes the method described in the third aspect.

[0147] In the twentieth aspect, the present application also provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0148] In the twenty-first aspect, the present application also provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.

[0149] In the twenty-second aspect, the present application also provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the third aspect above.

[0150] In the twenty-third aspect, the present application provides a chip system, which includes at least one processor and an interface, for supporting a terminal device to implement the functions involved in the first aspect, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system also includes a memory, which is used to store computer programs and data necessary for the terminal device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0151] In the twenty-fourth aspect, the present application provides a chip system, which includes at least one processor and an interface, for supporting a network device to implement the functions involved in the second aspect, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system also includes a memory, which is used to store computer programs and data necessary for the network device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0152] In the twenty-fifth aspect, the present application provides a chip system, which includes at least one processor and an interface, for supporting the network device to implement the functions involved in the third aspect, for example, determining or processing at least one of the data and information involved in the above method. In one possible design, the chip system also includes a memory, which is used to store computer programs and data necessary for the network device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0153] In the twenty-sixth aspect, the present application provides a computer program which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0154] In the twenty-seventh aspect, the present application provides a computer program which, when executed on a computer, enables the computer to execute the method described in the second aspect above.

[0155] In the twenty-eighth aspect, the present application provides a computer program which, when executed on a computer, enables the computer to execute the method described in the third aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0156] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the background technology, the drawings required for use in the embodiments of the present application or the background technology will be described below.

[0157] Figure 1 It is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application;

[0158] Figure 2 It is a flowchart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application;

[0159] Figure 3 It is a flowchart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application;

[0160] Figure 4 It is a flowchart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application;

[0161] Figure 5 It is a flowchart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application;

[0162] Figure 6 It is a flowchart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application;

[0163] Figure 7 It is a flowchart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application;

[0164] Figure 8 It is a flowchart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application;

[0165] Fig. 9 It is a flowchart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application;

[0166] Fig.10 A schematic diagram of a slice status information reporting system for multiple slice admission control functions NSACF provided in an embodiment of the present application.

[0167] Fig.11 is a structural diagram of a communication device provided in an embodiment of the present application;

[0168] Fig.12 is a structural diagram of another communication device provided in an embodiment of the present application;

[0169] Fig.13 It is a schematic diagram of the structure of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION

[0170] To facilitate understanding, the terms involved in this application are first introduced.

[0171] 1. Network Slice Admission Control function (NSACF)

[0172] NSACF is used to monitor the number of registered terminal UEs and PDU sessions of network slices that support NSAC functions. NSACF is also configured with the access type information of S-NSSAI that performs NSAC functions (i.e., 3GPP access type, non-3GPP access type, or both access types).

[0173] Each NSACF configures the maximum number of terminal UEs allowed to access the network slice and the maximum number of PDU sessions allowed to be activated.

[0174] NSACF supports monitoring and admission control of the maximum number of terminals and the maximum number of PDU sessions within the Public Land Mobile Network (PLMN). If the number of UEs registered to the current slice exceeds a certain threshold (such as the maximum number of UEs in the slice), NSAC will reject UE registration to control the number of UEs served to not exceed the maximum number of UEs in the slice configured by the network. When the number of PDU sessions activated in the slice exceeds a certain threshold (such as the maximum number of activated sessions), NSAC will reject the activation of PDU sessions to control the current number of sessions to not exceed the maximum number of sessions configured by the network.

[0175] 2. Application Function (AF) and Application Service Provider (ASP)

[0176] The application function AF or the application service provider ASP, based on the need to ensure or improve user experience, has the need to obtain the status information of the network slice, including information such as the current number of registered users in the slice, the current number of activated PDU sessions, the current number of registered users and / or the number of activated PCU sessions in the slice, and the proportion of the overall threshold of the slice.

[0177] 3. Network Exposure Function (NEF)

[0178] NEF is located between the 5G core network and external third-party application functions (possibly also some internal AFs), and is responsible for managing the open network data. All external applications that want to access the internal data of the 5G core network must go through NEF. NEF provides corresponding security guarantees to ensure the security of external applications to the 3gpp network, and provides external application QoS customization capability opening, mobility status event subscription, AF request distribution and other functions.

[0179] 4. Network Repository Function (NRF)

[0180] NRF is used to register, manage, and detect the status of NFs, and to realize the automated management of all NFs. When each NF is started, it must register with NRF to provide services. The registration information includes NF type, address, service list, etc.

[0181] In order to better understand the slice status information reporting method of multiple slice admission control functions NSACF disclosed in an embodiment of the present application, the communication system to which the embodiment of the present application is applicable is first described below.

[0182] See also Figure 1 , Figure 1 The present invention provides a schematic diagram of the architecture of a communication system. The communication system may include but is not limited to a network device and a terminal device. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of the present application. In actual applications, two or more network devices and two or more terminal devices may be included. Figure 1 The communication system shown includes a network device 101 and a terminal device 102 as an example.

[0183] It should be noted that the technical solution of the embodiment of the present application can be applied to various communication systems. For example: the fifth generation (5th generation, 5G) mobile communication system, the 5G new radio (new radio, NR) system, or other future new mobile communication systems. It should also be noted that the side link in the embodiment of the present application can also be called a side link or a through link.

[0184] The network device 101 in the embodiment of the present application is an entity for transmitting or receiving signals on the network side. For example, the network device 101 may be an evolved NodeB (eNB), a transmission point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device. The network device provided in the embodiment of the present application may be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU may also be referred to as a control unit. The CU-DU structure may be used to split the protocol layer of the network device, such as the base station, and the functions of some protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

[0185] The terminal device 102 in the embodiment of the present application is an entity for receiving or transmitting signals on the user side, such as a mobile phone. The terminal device can also be called a terminal device (terminal), a user equipment (UE), a mobile station (MS), a mobile terminal device (MT), etc. The terminal device can be a car with communication function, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in smart city (smart city), a wireless terminal device in smart home (smart home), etc. The embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.

[0186] Network slices can provide complete network functions, such as radio access network functions, core network functions and IMS functions. A network can support one or more network slices. Network slices can provide different committed services and are dedicated to users. Slices with the same service or slice but different slice identifiers may have different single network slice selection auxiliary information S-NSSAI.

[0187] Multiple network slices deployed by a mobile network operator (MNO) can provide exactly the same functionality, but for different UE groups. Because they provide different promised services and / or are dedicated to customers, in this case, such network slices may have different S-NSSAIs for the same slice or different slice distinguishers for the same service type.

[0188] The selection of a set of network slice instances for the UE is typically triggered by the first contacted Access and Mobility Management Function (AMF) during the registration process through interaction with the Network Slice Selection Function (NSSF), and may result in a change of AMF. Per PLMN, a PDU Session belongs to one and only one specific network slice instance. Although different network slice instances may have PDU Sessions for a specific slice using the same DNN, different network slice instances do not share PDU Sessions. During the handover process, the source AMF selects the target AMF by interacting with the Network Registration Function (NRF, NF Repository Function).

[0189] The Generic Network Slice Template (NEST) is applied to network slices, which are usually supported by multiple network slice instances. The Generic Network Slice Template (GST) defines the attributes supported by network slices.

[0190] The Network Slice Admission Control function (NSACF) is used to monitor the number of registered terminal UEs and PDU sessions of network slices that support the NSAC function. NSACF also configures the access type information of the S-NSSAI that performs the NSAC function (i.e., 3GPP access type, non-3GPP access type, or both access types).

[0191] Each NSACF configures the maximum number of terminal UEs allowed to access the network slice and the maximum number of PDU sessions allowed to be activated. NSACF supports monitoring and admission control of the maximum number of terminals and the maximum number of PDU sessions within the PLMN. If the number of UEs registered to the current slice exceeds a certain threshold (such as the maximum number of UEs in the slice), the NSAC will reject UE registration to control the number of UEs served to not exceed the maximum number of UEs in the slice configured by the network. When the number of PDU sessions activated in the slice exceeds a certain threshold (such as the maximum number of activated sessions), the NSAC will reject the activation of the PDU session to control the current number of sessions to not exceed the maximum number of sessions configured by the network.

[0192] Multiple NSACFs may be deployed in the operator network. One NSACF may serve one or more S-NSSAI slices in a service area. In a service area, an S-NSSAI is processed by only one NSACF, which can be an NSACF instance or an NSACF Set. A PLMN can have one or more service areas.

[0193] The application function AF or the application service provider ASP, based on the need to ensure or improve user experience, has the need to obtain the status information of the network slice, including information such as the current number of registered users in the slice, the current number of activated PDU sessions, the current number of registered users and / or the number of activated PCU sessions in the slice, and the proportion of the overall threshold of the slice.

[0194] However, when multiple NSACFs are deployed in the network, how the network accurately and in real time obtains the status information of these network slices, such as the current number of registered users in the slice, the current number of activated PDU sessions, the proportion of the current number of registered users and / or activated PCU sessions in the slice to the overall threshold of the slice, etc., and effectively transmits the obtained information to the application function AF or application service provider ASP as needed to ensure the correct execution of the function and process optimization, as well as a good service experience for users, is still a problem to be solved in 5G networks.

[0195] It can be understood that the communication system described in the embodiment of the present application is for more clearly illustrating the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution provided in the embodiment of the present application. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

[0196] The following is a detailed introduction to the slice status information reporting method and device of multiple slice admission control functions NSACF provided by the present application in conjunction with the accompanying drawings.

[0197] See also Figure 2 , Figure 2 1 is a flow chart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application. Figure 2 As shown, the method is applied to a first NSACF, and the method may include but is not limited to the following steps:

[0198] Step 201: Subscribe to the slice status information of the network slice from multiple NSACFs corresponding to the network slice through the network open function NEF.

[0199] In the embodiment of the present application, network slicing is an on-demand networking method that allows operators to separate multiple virtual end-to-end networks on a unified infrastructure. Each network slice is logically isolated from the wireless access network bearer network to the core network to adapt to various types of applications. In a network slice, it can be divided into at least three parts: wireless network sub-slices, bearer network sub-slices, and core network sub-slices. The Network Slice Admission Control function (NSACF) is used to monitor the number of registered terminal UEs and PDU sessions of network slices that support NSAC functions. NSACF is also configured with the access type information of the S-NSSAI that performs the NSAC function.

[0200] The AF or ASP needs to subscribe to or cancel the reporting notification of network slice status information to a specific NSACF (that is, the first NSACF) in the requested network slice according to business needs, and this is achieved by sending the first network slice status subscription request to the first NSACF. The requested network slice includes multiple NSACFs. After receiving the first network slice status subscription request, the first NSACF parses the multiple NSACFs in the network slice that need to report slice status information according to the first network slice status subscription request, and subscribes to the slice status information of the network slice to the multiple NSACFs corresponding to the network slice through the NEF.

[0201] Step 202: Obtain the slice status information of the network slice reported by the multiple NSACFs through the NEF.

[0202] In an embodiment of the present application, the multiple NSACFs corresponding to the network slice report the slice status information required by the first network slice status subscription request to the NEF, and the NEF then reports the received slice status information to the first NSACF.

[0203] By implementing the embodiments of the present application, the slice status information of the network slice can be subscribed to by the NEF from multiple NSACFs corresponding to the network slice, and the slice status information of the network slice reported by the multiple NSACFs can be obtained and fed back to the AF or ASP, thereby avoiding errors in uploading the network slice status information, thereby helping to improve the user experience.

[0204] Optionally, also include:

[0205] Receive a first network slice status subscription request sent by an application function AF or an application service provider ASP, wherein the first network slice status subscription request includes the network slice.

[0206] In an embodiment of the present application, the AF or ASP subscribes to or cancels the reporting notification of network slice status information to a specific NSACF (i.e., the first NSACF) in the requested network slice according to business needs, and this is achieved by sending the first network slice status subscription request to the first NSACF. The requested network slice includes multiple NSACFs.

[0207] Optionally, the subscribing to the slice status information of the network slice to multiple NSACFs corresponding to the network slice through the network open function NEF includes:

[0208] Send a second network slice status subscription request to the NEF, wherein the NEF sends the second network slice status subscription request to multiple NSACFs corresponding to the network slice, wherein the first NSACF belongs to the multiple NSACFs corresponding to the network slice.

[0209] In an embodiment of the present application, after the first NSACF receives the first network slice status subscription request sent by the AF or ASP, it generates a second network slice status subscription request and sends it to the NEF. Then, the second network slice status subscription request is sent to multiple NSACFs corresponding to the network slice through the NEF to obtain the slice status information of multiple NSACFs corresponding to the network slice.

[0210] Optionally, the subscribing to the slice status information of the network slice to multiple NSACFs corresponding to the network slice through the network open function NEF includes:

[0211] Send a second network slice status subscription request to the NEF, wherein the NEF sends the subscription request to a second NSACF among the multiple NSACFs corresponding to the network slice, wherein the first NSACF belongs to the multiple NSACFs corresponding to the network slice.

[0212] In an embodiment of the present application, after the first NSACF receives the first network slice status subscription request sent by the AF or ASP, it generates a second network slice status subscription request and sends it to the NEF. Then, the NEF sends the second network slice status subscription request to the second NSACF among the multiple NSACFs corresponding to the network slice to obtain the slice status information of the second NSACF among the multiple NSACFs corresponding to the network slice.

[0213] In a possible embodiment, the multiple NSACFs corresponding to the network slice include a second NSACF.

[0214] In a possible embodiment, the multiple NSACFs corresponding to the network slice include multiple second NSACFs.

[0215] See also Figure 3 , Figure 3 1 is a flow chart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application. Figure 3 As shown, the method is applied to a first NSACF, and the method may include but is not limited to the following steps:

[0216] Step 301: Generate network slice status response information based on the status information of the network slice among the multiple NSACFs.

[0217] In an embodiment of the present application, after the first NSACF receives the first network slice status subscription request sent by the AF or ASP, it parses the subscription event, subscription event filtering information and subscription event reporting mode information in the first network slice status subscription request, and aggregates the status information of the requested network slice according to the first network slice status subscription request to generate status response information of the requested network slice.

[0218] Step 302: Send the network slice status response information to the AF or ASP.

[0219] In an embodiment of the present application, after generating the network slice status response information, the first NSACF sends the network slice status response information to the AF or ASP, and feeds back the status information required by the AF or ASP to the AF or ASP.

[0220] By implementing the embodiment of the present application, the first slice time subscription request sent by the AF or ASP can be received, and the corresponding status response information can be generated and fed back to the AF or ASP. In this way, network slice status information upload errors can be avoided, which is conducive to improving the user experience.

[0221] Optionally, the first slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

[0222] Optionally, the subscription event includes at least one of the following:

[0223] The number of terminals registered on the requested network slice;

[0224] The number of packet data unit (PDU) sessions established on the requested network slice;

[0225] The ratio of the number of terminals registered on the requested network slice to the maximum number of terminals allowed to be registered;

[0226] The ratio of the number of PDU sessions established on the requested network slice to the maximum number of PDU sessions allowed to be established;

[0227] The number of registered terminals on the requested network slice and the ratio of the number of registered terminals to the maximum number of allowed registered terminals;

[0228] The number of established PDU sessions on the requested network slice and the ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.

[0229] Each NSACF configures the maximum number of terminal UEs allowed to access the network slice and the maximum number of PDU sessions allowed to be activated.

[0230] NSACF supports monitoring and admission control of the maximum number of terminals and the maximum number of PDU sessions within the PLMN. If the number of UEs registered to the current slice exceeds a certain threshold (such as the maximum number of UEs in the slice), NSAC will reject UE registration to control the number of UEs served to not exceed the maximum number of UEs in the slice configured by the network. When the number of PDU sessions activated in the slice exceeds a certain threshold (such as the maximum number of activated sessions), NSAC will reject the activation of PDU sessions to control the current number of sessions to not exceed the maximum number of sessions configured by the network.

[0231] An NSACF may be deployed in the operator network. An NSACF may serve one or more S-NSSAI slices in a service area. In a service area, an S-NSSAI is processed by only one NSACF, which can be an NSACF instance or an NSACF Set. A PLMN can have one or more service areas.

[0232] The application function AF or the application service provider ASP, based on the need to ensure or improve user experience, has the need to obtain the status information of the network slice, including information such as the current number of registered users in the slice, the current number of activated PDU sessions, the current number of registered users and / or the number of activated PCU sessions in the slice, and the proportion of the overall threshold of the slice.

[0233] Optionally, the subscription event screening information includes at least one of the following:

[0234] Single network slice selection assistance information S-NSSAI of the requested network slice;

[0235] The registration area RA of the requested network slice;

[0236] A combination of the S-NSSAI of the requested network slice and the data network name DNN;

[0237] The area of ​​interest IoA of the requested network slice.

[0238] In an embodiment of the present application, the subscription event filtering information is used to define the scope that needs to be reported, such as the slice identifier S-NSSAI, the registration area RA, the combination of the slice identifier S-NSSAI and the data network name DNN, the area of ​​interest IoA, etc.

[0239] Optionally, the subscription event report mode information includes at least one of the following:

[0240] The threshold that triggers the report;

[0241] The periodic interval for triggering reporting.

[0242] In the embodiment of the present application, the subscription event reporting mode information is used to define the reporting mode, if the reporting information parameter is a threshold value that triggers reporting, when the threshold value is reached, the current threshold value is reported. If the reporting information parameter is a periodic time interval that triggers reporting, when the periodic time interval is reached, the current value is reported.

[0243] Optionally, the first network slice status subscription request also includes an immediate reporting flag, wherein the immediate reporting flag is used to instruct the first NSACF to immediately send the network slice status response information upon receiving the network slice status subscription request.

[0244] Optionally, the generating network slice status response information according to the status information of the network slice among the multiple NSACFs includes:

[0245] The status information of the network slice among the multiple NSACFs is aggregated to generate the slice status response information.

[0246] In an embodiment of the present application, after receiving the first network slice status subscription request, the first NSACF parses the subscription event, subscription event filtering information and subscription event reporting mode information in the first network slice status subscription request, and aggregates the status information of the requested network slice according to the first network slice status subscription request to generate status response information of the requested network slice.

[0247] In a possible embodiment, after receiving the second network slice status subscription request, the first NSACF sends the second network slice status subscription request to multiple NSACFs corresponding to the network slice through the NEF, and the multiple NSACFs parse the subscription events, subscription event filtering information and subscription event reporting mode information in the second network slice status subscription request, and aggregate the status information of the network slice among the multiple NSACFs according to the second network slice status subscription request to generate status response information of the requested network slice.

[0248] In a possible embodiment, after receiving the second network slice status subscription request, the first NSACF sends the second network slice status subscription request to the second NSACF among the multiple NSACFs corresponding to the network slice through the NEF, and the second NSACF among the multiple NSACFs parses the subscription event, subscription event filtering information and subscription event reporting mode information in the second network slice status subscription request, and aggregates the status information of the network slice of the second NSAC among the multiple NSACFs according to the second network slice status subscription request to generate status response information of the requested network slice.

[0249] Optionally, also include:

[0250] The multiple NSACFs corresponding to the network slice are determined through the network configuration or operator policy in the NEF.

[0251] Optionally, the first NSACF is a master NSACF or a proxy NSACF among multiple NSACFs corresponding to the network slice.

[0252] In the embodiment of the present application, NSACF-P, that is, the first NSACF, can be the master NSACF in the requested slice, or can be the proxy NSACF in the requested slice; when it is the master NSACF, other NSACFs in the slice are subordinate NSACFs; when it is the proxy NASCF, the NSACF and other NSACFs in the slice do not have a master-slave relationship.

[0253] Optionally, the second network slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

[0254] Optionally, also include:

[0255] The network slice status response information is filtered according to the subscription event filtering information.

[0256] In an embodiment of the present application, the subscription event filtering information is used to indicate the scope that needs to be reported, including one of the following items: a slice identifier S-NSSAI, a registration area RA, a combination of a slice identifier S-NSSAI and a data network name DNN, and an area of ​​interest IoA. The network slice status response information required by the AF or ASP is filtered out from the network slice status response information according to the subscription event filtering information.

[0257] See also Figure 4 , Figure 4 1 is a flow chart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application. Figure 4 As shown, the method is applied to a first NSACF, and the method may include but is not limited to the following steps:

[0258] Step 401: Determine whether a reporting condition is met according to the subscription event report mode information.

[0259] Step 402: If the reporting conditions are met, the network slice status response information is reported.

[0260] In an embodiment of the present application, the subscription event reporting mode information includes a threshold value, or a periodic report including a periodic time interval. If the reporting information parameter is a threshold value that triggers reporting, the current threshold value is reported when the threshold value is reached. If the reporting information parameter is a periodic time interval that triggers reporting, the current value is reported when the periodic time interval is reached.

[0261] Optionally, the receiving a slice status subscription request sent by an AF or an ASP includes:

[0262] If the AF or ASP is an untrusted AF or ASP, the slice status subscription request sent by the AF or ASP is received through NEF.

[0263] In the embodiment of the present application, the first NSACF sends a Nnsacf_EventExposure_Subscribe / usubsubscribe Response response message to the AF or ASP, that is, the network slice status response information. After receiving the slice event subscription request from the application function AF / application service provider ASP, the first NSACF subscribes to the reporting event of the requested slice from each NSACF of the requested slice, and after receiving the reporting information from each NSACF, reports to the requested application function AF / application service provider ASP.

[0264] When the operating policy does not open the slice identifier to the untrusted AF / ASP, and the AF / ASF is an untrusted AF / ASP. The network slice status subscription request can be sent to the NSACF via the NEF. The above-mentioned Nnsacf_EventExposure subscribe / unsubscribe Request message is replaced by the Nnef_EventExposuresubscribe / unsubscribe Request message between the AF / ASP and the NEF, and the Nnsacf_EventExposuresubscribe / unsubscribe Request message between the NEF and the NSACF.

[0265] Optionally, the first NSACF is selected by the NEF.

[0266] Optionally, the first NSACF is selected by the NEF through NRF, or the first NSACF is selected by the NEF through local configuration.

[0267] See also Figure 5 , Figure 5 1 is a flow chart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application. Figure 5 As shown, the method is applied to NEF, and the method may include but is not limited to the following steps:

[0268] Step 501: Receive a first network slice status subscription request sent by the first NSACF, wherein the first network slice event slice status subscription request includes a network slice.

[0269] In an embodiment of the present application, after the first NSACF receives the first network slice status subscription request from the application function AF / application service provider ASP, it sends the first network slice status subscription request to the NEF, the first network slice event slice status subscription request includes the network slice, and the first slice status subscription request includes at least one of the subscription event, subscription event filtering information and subscription event reporting mode information.

[0270] Step 502: Subscribe to the slice status information of the network slice to multiple NSACFs corresponding to the network slice.

[0271] In an embodiment of the present application, NEF obtains the network slice according to the first network slice status subscription request, and subscribes to the slice status information of the network slice to multiple NSACFs corresponding to the network slice.

[0272] Step 503: Obtain the slice status information of the network slice reported by the multiple NSACFs.

[0273] In an embodiment of the present application, after receiving the subscription from the NEF, the multiple NSACFs report the slice status information of the network slice to the NEF.

[0274] Step 504: Send the slice status information to the first NSACF.

[0275] In an embodiment of the present application, the NEF aggregates the slice status information and generates network slice status response information, and sends it to the first NSACF, which then sends it to the AF or ASP.

[0276] By implementing the embodiment of the present application, the first slice time subscription request sent by AF or ASP can be transmitted through NEF, or the network slice status response information sent by the first NASCF can be transmitted through NEF. In this way, network slice status information upload errors can be avoided, which is conducive to improving the user experience.

[0277] See also Figure 6 , Figure 6 1 is a flow chart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application. Figure 6 As shown, the method is applied to NEF, and the method may include but is not limited to the following steps:

[0278] Step 601: Receive a second network slice status subscription request sent by the first NSACF.

[0279] Step 602: Send the second network slice status subscription request to multiple NSACFs corresponding to the network slice, wherein the first NSACF belongs to the multiple NSACFs corresponding to the network slice.

[0280] In an embodiment of the present application, after the first NSACF receives the first network slice status subscription request sent by the AF or ASP, it generates a second network slice status subscription request and sends it to the NEF. Then, the second network slice status subscription request is sent to multiple NSACFs corresponding to the network slice through the NEF to obtain the slice status information of multiple NSACFs corresponding to the network slice.

[0281] See also Figure 7 , Figure 7 1 is a flow chart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application. Figure 7 As shown, the method is applied to NEF, and the method may include but is not limited to the following steps:

[0282] Step 701: Receive a second network slice status subscription request sent by the first NSACF.

[0283] Step 702: Send the subscription request to the second NSACF among the multiple NSACFs corresponding to the network slice, wherein the first NSACF belongs to the multiple NSACFs corresponding to the network slice.

[0284] In an embodiment of the present application, after the first NSACF receives the first network slice status subscription request sent by the AF or ASP, it generates a second network slice status subscription request and sends it to the NEF. Then, the NEF sends the second network slice status subscription request to the second NSACF among the multiple NSACFs corresponding to the network slice to obtain the slice status information of the second NSACF among the multiple NSACFs corresponding to the network slice.

[0285] See also Figure 8 , Figure 8 1 is a flow chart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application. Figure 8 As shown, the method is applied to NEF, and the method may include but is not limited to the following steps:

[0286] Step 801: Generate network slice status response information based on the status information of the network slice among the multiple NSACFs.

[0287] In an embodiment of the present application, after the first NSACF receives the first network slice status subscription request sent by the AF or ASP, it parses the subscription event, subscription event filtering information and subscription event reporting mode information in the first network slice status subscription request, and aggregates the status information of the requested network slice according to the first network slice status subscription request to generate status response information of the requested network slice.

[0288] Step 802: Send the network slice status response information to the AF or ASP.

[0289] In an embodiment of the present application, after generating the network slice status response information, the first NSACF sends the network slice status response information to the AF or ASP to feed back the status information required by the AF or ASP to the AF or ASP.

[0290] By implementing the embodiment of the present application, the first slice time subscription request sent by the AF or ASP can be received, and the corresponding status response information can be generated and fed back to the AF or ASP. In this way, network slice status information upload errors can be avoided, which is conducive to improving the user experience.

[0291] Optionally, the first slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

[0292] Optionally, the subscription event includes at least one of the following:

[0293] The number of terminals registered on the requested network slice;

[0294] The number of packet data unit (PDU) sessions established on the requested network slice;

[0295] The ratio of the number of terminals registered on the requested network slice to the maximum number of terminals allowed to be registered;

[0296] The ratio of the number of PDU sessions established on the requested network slice to the maximum number of PDU sessions allowed to be established;

[0297] The number of registered terminals on the requested network slice and the ratio of the number of registered terminals to the maximum number of allowed registered terminals;

[0298] The number of established PDU sessions on the requested network slice and the ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.

[0299] Each NSACF configures the maximum number of terminal UEs allowed to access the network slice and the maximum number of PDU sessions allowed to be activated.

[0300] NSACF supports monitoring and admission control of the maximum number of terminals and the maximum number of PDU sessions within the PLMN. If the number of UEs registered to the current slice exceeds a certain threshold (such as the maximum number of UEs in the slice), NSAC will reject UE registration to control the number of UEs served to not exceed the maximum number of UEs in the slice configured by the network. When the number of PDU sessions activated in the slice exceeds a certain threshold (such as the maximum number of activated sessions), NSAC will reject the activation of PDU sessions to control the current number of sessions to not exceed the maximum number of sessions configured by the network.

[0301] An NSACF may be deployed in the operator network. An NSACF may serve one or more S-NSSAI slices in a service area. In a service area, an S-NSSAI is processed by only one NSACF, which can be an NSACF instance or an NSACF Set. A PLMN can have one or more service areas.

[0302] The application function AF or the application service provider ASP, based on the need to ensure or improve user experience, has the need to obtain the status information of the network slice, including information such as the current number of registered users in the slice, the current number of activated PDU sessions, the current number of registered users and / or the number of activated PCU sessions in the slice, and the proportion of the overall threshold of the slice.

[0303] Optionally, the subscription event screening information includes at least one of the following:

[0304] Single network slice selection assistance information S-NSSAI of the requested network slice;

[0305] The registration area RA of the requested network slice;

[0306] A combination of the S-NSSAI of the requested network slice and the data network name DNN;

[0307] The area of ​​interest IoA of the requested network slice.

[0308] In an embodiment of the present application, the subscription event filtering information is used to define the scope that needs to be reported, such as the slice identifier S-NSSAI, the registration area RA, the combination of the slice identifier S-NSSAI and the data network name DNN, the area of ​​interest IoA, etc.

[0309] Optionally, the subscription event report mode information includes at least one of the following:

[0310] The threshold that triggers the report;

[0311] The periodic interval for triggering reporting.

[0312] In the embodiment of the present application, the subscription event reporting mode information is used to define the reporting mode, if the reporting information parameter is a threshold value that triggers reporting, when the threshold value is reached, the current threshold value is reported. If the reporting information parameter is a periodic time interval that triggers reporting, when the periodic time interval is reached, the current value is reported.

[0313] Optionally, the generating network slice status response information according to the status information of the network slice among the multiple NSACFs includes:

[0314] The status information of the network slice among the multiple NSACFs is aggregated to generate the slice status response information.

[0315] Optionally, the first network slice status subscription request also includes an immediate reporting flag, wherein the immediate reporting flag is used to instruct the first NSACF to immediately send the network slice status response information upon receiving the first network slice status subscription request.

[0316] Optionally, also include:

[0317] The multiple NSACFs corresponding to the network slice are determined through network configuration or operator policy.

[0318] Optionally, the first NSACF is a master NSACF or a proxy NSACF among multiple NSACFs corresponding to the network slice.

[0319] Optionally, the second network slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

[0320] Optionally, the receiving a slice status subscription request sent by an AF or an ASP includes:

[0321] If the AF or ASP is an untrusted AF or ASP, receive the slice status subscription request sent by the AF or ASP.

[0322] Optionally, also include:

[0323] The first NSACF was selected.

[0324] Optionally, the selecting and obtaining the first NSACF includes:

[0325] The first NSACF is obtained by NRF selection;

[0326] Alternatively, the first NSACF is obtained through local configuration selection.

[0327] See also Fig. 9 , Fig. 9 1 is a flow chart of a method for reporting slice status information of multiple slice admission control functions NSACF provided in an embodiment of the present application. Fig. 9 As shown, the method is applied to AF or ASP, and the method may include but is not limited to the following steps:

[0328] Step 901: Send a first network slice status subscription request to a first NSACF, wherein the first network slice status subscription request includes a network slice.

[0329] In an embodiment of the present application, the AF or ASP needs to subscribe to or cancel the reporting notification of network slice status information to a specific NSACF (i.e., the first NSACF) in the requested network slice according to business needs, and this is achieved by sending the first network slice status subscription request to the first NSACF. The requested network slice includes multiple NSACFs. After receiving the first network slice status subscription request, the first NSACF parses the multiple NSACFs in the network slice that need to report slice status information according to the first network slice status subscription request, and subscribes to the slice status information of the network slice to the multiple NSACFs corresponding to the network slice through the NEF. And generate network slice status response information based on the slice status information of the network slice.

[0330] Step 902: Receive network slice status response information sent by the first NSACF.

[0331] In an embodiment of the present application, in an embodiment of the present application, the first NSACF feeds back the network slice status response information to the AF or ASP. The AF or ASP can obtain the status of the network slice according to the network slice status response information.

[0332] By implementing the embodiment of the present application, the first slice time subscription request sent by AF or ASP can be transmitted through NEF, or the network slice status response information sent by the first NASCF can be transmitted through NEF. In this way, network slice status information upload errors can be avoided, which is conducive to improving the user experience.

[0333] Optionally, the first network slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

[0334] Optionally, the subscription event includes at least one of the following:

[0335] The number of terminals registered on the requested network slice;

[0336] The number of packet data unit (PDU) sessions established on the requested network slice;

[0337] The ratio of the number of terminals registered on the requested network slice to the maximum number of terminals allowed to be registered;

[0338] The ratio of the number of PDU sessions established on the requested network slice to the maximum number of PDU sessions allowed to be established;

[0339] The number of registered terminals on the requested network slice and the ratio of the number of registered terminals to the maximum number of allowed registered terminals;

[0340] The number of established PDU sessions on the requested network slice and the ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.

[0341] Optionally, the subscription event screening information includes at least one of the following:

[0342] Single network slice selection assistance information S-NSSAI of the requested network slice;

[0343] The registration area RA of the requested network slice;

[0344] A combination of the S-NSSAI of the requested network slice and the data network name DNN;

[0345] The area of ​​interest IoA of the requested network slice.

[0346] Optionally, the subscription event report mode information includes at least one of the following:

[0347] The threshold that triggers the report;

[0348] The periodic interval for triggering reporting.

[0349] Optionally, the first network slice status subscription request also includes an immediate reporting flag, wherein the immediate reporting flag is used to instruct the first NSACF to immediately send the network slice status response information upon receiving the first network slice status subscription request.

[0350] Optionally, the multiple NSACFs corresponding to the network slice are determined by the network configuration or operator policy in the NEF.

[0351] Optionally, the first NSACF is a master NSACF or a proxy NSACF among multiple NSACFs corresponding to the requested network slice.

[0352] Optionally, the first NSACF is selected by the NEF through NRF, or the first NSACF is selected by the NEF through local configuration.

[0353] In the embodiments provided by the present application, the methods provided by the embodiments of the present application are introduced from the perspectives of network equipment and terminal equipment, respectively. In order to implement the functions in the methods provided by the embodiments of the present application, the network equipment and the terminal equipment may include hardware structures and software modules, and the functions are implemented in the form of hardware structures, software modules, or hardware structures plus software modules. A certain function in the functions may be executed in the form of hardware structures, software modules, or hardware structures plus software modules.

[0354] See also Fig.10 , which is a schematic diagram of a slice status information reporting system of multiple slice admission control functions NSACF provided in an embodiment of the present application. In order to subscribe or cancel the reporting notification of the number of network slice UEs or the number of PDU sessions to NSACF-P, the AF / ASP sends a Nnsacf_EventExposure subscribe / unsubscribeRequest message to NSACF-P, which includes an event ID, event filter, and event report information.

[0355] The event ID parameter defines the subscribed event ID, that is, the number of registered terminals, or the number of established PDU sessions, or the ratio of the number of registered terminals to the maximum allowed number of registered terminals, or the ratio of the number of established PDU sessions to the maximum allowed number of established PDU sessions, or the ratio of the number of registered terminals and the number of registered terminals to the maximum allowed number of registered terminals, or the number of established PDU sessions and the ratio of the number of established PDU sessions to the maximum allowed number of established PDU sessions.

[0356] Event filter parameters define the scope of the report, such as the slice identifier S-NSSAI, the registration area RA, the combination of the slice identifier S-NSSAI and the data network name DNN, the area of ​​interest IoA, etc.

[0357] The event report information parameter defines the reporting mode, including a threshold, or a periodic report including a periodic time interval. If the report information parameter is a threshold that triggers reporting, the current threshold is reported when the threshold is reached. If the report information parameter is a periodic time interval that triggers reporting, the current value is reported when the periodic time interval is reached. The subscription request may also include an immediate report flag, indicating that the requested current value is reported immediately after receiving the request.

[0358] NSACF-P, (i.e., the first NSACF) belongs to one of the multiple NSACFs in the requested slice, and the NSACF-P can be selected by the operator configuration, or randomly discovered and selected by the AF / ASP request. NSACF-P, can be the primary NSACF (Primary) in the requested slice, or it can be the proxy NSACF (Proxy) in the requested slice; when the NSACF-P, is the primary NSACF, the other NSACFs in the slice are subordinate NSACFs; when it is a proxy NASCF, the NSACF and the other NSACFs in the slice do not have a master-slave relationship.

[0359] NSACF-P sends Nnsacf_EventExposure_Subscribe / usubsubscribeResponse response message to AF / ASP. After NSACF (Proxy / Primary) receives the slice event subscription request from the application function AF / application service provider ASP, it subscribes to the reporting event of the requested slice from each NSACF of the requested slice. After receiving the reporting information from each NSACF, it reports to the requested application function AF / application service provider ASP.

[0360] There are multiple NSACFs deployed in the PLMN that requests the slice. NSACFs perform subscription requests and notifications through NEFs and count the information of subscription events. NSACF-P sends Nnef_EventExposure subscribe / unsubscribe Request message to NEF. NEF sends subscription or unsubscription request message.

[0361] NEF sends Nnef_EventExposure_Subscribe / usubsubscribe Response message to NSACF-P.

[0362] NEF performs discovery selection of the NSACF(s) corresponding to the requested slice. NEF performs discovery selection of the NSACF via the Network Registration Function NRF or via local configuration.

[0363] If NEF has not subscribed to the reporting events of the relevant Requested S-NSSAI from the slice's NSACF(s) (such as the reporting of the number of UEs or PDU sessions in the network slice), NEF initiates a subscription request to all NSACFs that support Requested S-NSSAI and sends a Nnef_SliceEventExposure_Subscribe / Unsubscribe request message, which includes an event ID, event filter, event report information, and carries various related message parameters. NEF stores the event report information requested by NSACF-P. NEF sets the event ID and event filter information according to the content of the request message received from NSACF-P.

[0364] NEF can set the time report information as periodic report or immediate report in the subscription request to each NSACF. If the Requested S-NSSAI is performed by more than two NSACFs to control the slice admission of UE and / or session, when NEF sets the time report information as periodic report, it can obtain the relevant network status information of the requested slice more continuously and stably. If the Requested S-NSSAI is performed by two NSACFs to control the slice admission of UE and / or session, the slice network status information can be collected in real time. The event report information set by NEF is generally the same as the request received from NSACF-P. However, when two NSACFs are deployed, it can also be set to periodic report to facilitate the elastic expansion of the network and maintain the consistency of network execution strategy.

[0365] NSACF sends a Nnsacf_SliceEventExposure_Subscribe / usubsubscribe response message to NEF to confirm the subscription request.

[0366] When the subscribed report conditions are met and the report event is triggered, the NSACF sends a trigger notification to the NEF to perform reporting of the subscribed event related information.

[0367] NSACF sends a Nnsacf_SliceEventExposure_Notify message to NEF, which carries parameters such as event ID, event filter, and event report information.

[0368] Optionally, when the requested NSSAI selects multiple NSACFs to perform slice admission control for UE and / or session, NEF collects reports from all NFACFs and performs aggregation of all usage of slice S-NSSAI within the requested event filter (such as within the PLMN). When the reporting conditions are met and the report is triggered, NEF reports the usage of slice S-NSSAI within the requested event filter (such as within the entire PLMN) to NSACF-P. When the requested NSSAI selects two or a single NSACF to perform slice admission control for UE and / or session, NEF may immediately return a report notification to NSACF-P, report a statistical usage report, or perform periodic reporting to NSACF-P based on periodic subscription. Optionally, according to the operator's policy or deployment requirements, the usage aggregated by NEF may include or exclude the statistics of NSACF-P itself.

[0369] When the conditions of the event report subscribed by the AF / ASP are triggered / satisfied, the subscription report is triggered. NEF sends a notification to the NSACF-P to report the subscription-related usage and information according to the subscription requirements, such as the number of UE / Sessions in the PLMN, or the number of UE / Sessions corresponding to the combination of S-NSSAI and DNN, or the number of UE / Sessions in the RA registration area, or the number of UE / Sessions in the IoA area of ​​interest.

[0370] Optionally, if the NEF does not perform the requested usage aggregation, the NSACF will perform the aggregation of all usage of the slice S-NSSAI within the requested event filter (such as within the PLMN). Alternatively, if the NEF does not perform usage aggregation of the NSACF-P's own statistics, the NSACF-P will merge its own statistics with the usage of other NSACF(s).

[0371] NSACF-P sends a notification to AF / ASP to report the subscription-related usage and information according to the subscription requirements, such as the number of UE / Sessions in the PLMN, or the number of UE / Sessions corresponding to the combination of S-NSSAI and DNN, or the number of UE / Sessions in the RA registration area, or the number of UE / Sessions in the IoA area of ​​interest, or at the same time report the proportion of the corresponding UE / Session number to the maximum allowed number, etc.

[0372] Fig.10The system is mainly used for statistics and reporting of slice status information such as the number of UEs and sessions requested by trusted AF / ASP for slice subscription. However, the enhancement of this solution is also applicable to scenarios of untrusted AF / APP. In untrusted scenarios, AF can also execute subscription or cancellation requests through NEF and NSACF-P.

[0373] When the AF / ASP is an untrusted AF / ASP, the steps performed by the system are different as follows:

[0374] When the AF / ASF is an untrusted AF / ASP, the subscription message can be sent to the NSACF-P through the NEF. The Nnsacf_EventExposuresubscribe / unsubscribe Request message is replaced by two sets of messages: the Nnef_EventExposuresubscribe / unsubscribe Request message between the AF / ASP and the NEF, and the Nnsacf_EventExposuresubscribe / unsubscribe Request message between the NEF and the NSACF-P. Optionally, the NEF performs the discovery selection of the NSACF-P. The NEF performs the discovery selection of the NSACF-P through the network registration function NRF or through local configuration. Optionally, when the operating policy does not open the slice identifier to the untrusted AF / ASP, the NEF performs the mapping of the application or service identifier of the requesting AF / ASP to the slice identifier; when the NEF receives the subscription request from the AF / ASP, it maps the application or service identifier to the slice identifier and sends it to the NSACF.

[0375] When the AF / ASF is an untrusted AF / ASP, the subscription reporting message of NSACF-P can be sent to the AF / ASP through NEF. The Nnsacf_SliceEventExposure_Notify message is replaced by the Nnsacf_SliceEventExposure_Notify message between NSACF-P and NEF, and the Nnef_SliceEventExposure_Notify message between NEF and AF / ASP. Optionally, when the operating policy does not open the slice identifier to the untrusted AF / ASP, NEF executes the mapping of the application or service identifier of the requesting AF / ASP to the slice identifier; when NEF receives the subscription event notification from NSACF, it maps the slice identifier to the application or service identifier and sends it to the AF / ASP.

[0376] See also Fig.11 , is a structural diagram of a communication device 110 provided in an embodiment of the present application. Fig.11The communication device 110 shown may include a transceiver module 1101 and a processing module 1102. The transceiver module 1101 may include a sending module and / or a receiving module, the sending module is used to implement a sending function, the receiving module is used to implement a receiving function, and the transceiver module 1101 may implement a sending function and / or a receiving function.

[0377] The communication device 110 may be a terminal device (such as the terminal device in the aforementioned method embodiment), or a device in a terminal device, or a device that can be used in conjunction with a terminal device. Alternatively, the communication device 110 may be a network device, or a device in a network device, or a device that can be used in conjunction with a network device.

[0378] The communication device 110 is a first NSACF, comprising: a subscription module, configured to subscribe slice status information of the network slice to multiple NSACFs corresponding to the network slice through a network open function NEF;

[0379] An acquisition module is used to obtain the slice status information of the network slice reported by the multiple NSACFs through the NEF.

[0380] The communication device 110 is a NEF, comprising: a first receiving module, configured to receive a first network slice state subscription request sent by the first NSACF, wherein the first network slice event slice state subscription request includes a network slice;

[0381] A first sending module, configured to subscribe slice status information of the network slice to multiple NSACFs corresponding to the network slice;

[0382] A second receiving module is used to obtain the slice status information of the network slice reported by the multiple NSACFs;

[0383] The second sending module is used to send the slice status information to the first NSACF.

[0384] The communication device 110 is an AF or an ASP, and includes: a third sending module, configured to send a first network slice status subscription request to a first NSACF, wherein the first network slice status subscription request includes a network slice;

[0385] The third receiving module is used to receive the network slice status response information sent by the first NSACF.

[0386] See also Fig.12 , Fig.121 is a schematic diagram of the structure of another communication device 120 provided in an embodiment of the present application. The communication device 120 may be a network device, or a terminal device (such as the terminal device in the aforementioned method embodiment), or a chip, a chip system, or a processor that supports the network device to implement the aforementioned method, or a chip, a chip system, or a processor that supports the terminal device to implement the aforementioned method. The device may be used to implement the method described in the aforementioned method embodiment, and the details may refer to the description in the aforementioned method embodiment.

[0387] The communication device 120 may include one or more processors 1201. The processor 1201 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor may be used to process the communication protocol and communication data, and the central processing unit may be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute a computer program, and process the data of the computer program.

[0388] Optionally, the communication device 120 may further include one or more memories 1202, on which a computer program 1203 may be stored, and the processor 1201 executes the computer program 1203 so that the communication device 120 performs the method described in the above method embodiment. Optionally, data may also be stored in the memory 1202. The communication device 120 and the memory 1202 may be provided separately or integrated together.

[0389] Optionally, the communication device 120 may further include a transceiver 1204 and an antenna 1205. The transceiver 1204 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing a transceiver function. The transceiver 1204 may include a receiver and a transmitter, the receiver may be referred to as a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing a transmitting function.

[0390] Optionally, the communication device 120 may further include one or more interface circuits 1206. The interface circuit 1206 is used to receive code instructions and transmit them to the processor 1201. The processor 1201 runs the code instructions to enable the communication device 120 to execute the method described in the above method embodiment.

[0391] In one implementation, the processor 1201 may include a transceiver for implementing receiving and sending functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

[0392] In one implementation, the processor 1201 may store a computer program 1203, which runs on the processor 1201 and enables the communication device 120 to perform the method described in the above method embodiment. The computer program 1203 may be fixed in the processor 1201, in which case the processor 1201 may be implemented by hardware.

[0393] In one implementation, the communication device 120 may include a circuit that can implement the functions of sending or receiving or communicating in the aforementioned method embodiment. The processor and transceiver described in this application can be implemented in an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channelmetal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0394] The communication device described in the above embodiments may be a network device or a terminal device (such as the terminal device in the above method embodiment), but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited thereto. Fig.12 The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0395] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0396] (2) having a set of one or more ICs, and optionally, the IC set may also include a storage component for storing data and computer programs;

[0397] (3) ASIC, such as modem;

[0398] (4) Modules that can be embedded in other devices;

[0399] (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

[0400] (6)Others

[0401] For the case where the communication device may be a chip or a chip system, see Fig. 9 Schematic diagram of the chip structure shown. Fig.13 The chip shown includes a processor 1301 and an interface 1302. The number of the processor 1301 may be one or more, and the number of the interface 1302 may be multiple.

[0402] For the case where the chip is used to implement the functions of the terminal device in the embodiment of the present application (such as the terminal device in the aforementioned method embodiment):

[0403] Optionally, the chip further includes a memory 1303, and the memory 1303 is used to store necessary computer programs and data.

[0404] Those skilled in the art may also understand that the various illustrative logical blocks and steps listed in the embodiments of the present application may be implemented by electronic hardware, computer software, or a combination of the two. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the functions described for each specific application, but such implementation should not be understood as exceeding the scope of protection of the embodiments of the present application.

[0405] The embodiment of the present application also provides a slice status information reporting system for multiple slice admission control functions NSACF, the system comprising the aforementioned Fig.11 In the embodiment, the communication device as the terminal device (such as the terminal device in the aforementioned method embodiment) and the communication device as the network device, or the system includes the aforementioned Fig.12The communication device in the embodiment serves as a terminal device (such as the terminal device in the aforementioned method embodiment) and the communication device serves as a network device.

[0406] The present application also provides a readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0407] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0408] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0409] A person skilled in the art may understand that the various numerical numbers such as first and second involved in the present application are only used for the convenience of description and are not used to limit the scope of the embodiments of the present application, and also indicate the order of precedence.

[0410] At least one in the present application can also be described as one or more, and a plurality can be two, three, four or more, which is not limited in the present application. In the embodiments of the present application, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", etc., and there is no order of precedence or size between the technical features described by the "first", "second", "third", "A", "B", "C" and "D".

[0411] The corresponding relationships shown in each table in the present application can be configured or predefined. The values ​​of the information in each table are only examples and can be configured as other values, which are not limited by the present application. When configuring the corresponding relationship between the information and each parameter, it is not necessarily required to configure all the corresponding relationships illustrated in each table. For example, in the table in the present application, the corresponding relationships shown in some rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above table, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables can also use other names that can be understood by the communication device, and the values ​​or representations of the parameters can also be other values ​​or representations that can be understood by the communication device. When implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables.

[0412] The predefined in the present application may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0413] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0414] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0415] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for reporting slice status information of multiple slice admission control functions NSACF, characterized in that: Applied to the first NSACF, the method comprises the following steps: Subscribe slice status information of the network slice to multiple NSACFs corresponding to the network slice through the network open function NEF; the multiple NSACFs corresponding to the network slice include the first NSACF; The slice status information of the network slice reported by the multiple NSACFs is obtained through the NEF.

2. The method according to claim 1, characterized in that Also includes: Receive a first network slice status subscription request sent by an application function AF or an application service provider ASP, wherein the first network slice status subscription request includes the network slice.

3. The method according to claim 1, characterized in that: Subscribing slice status information of the network slice to multiple NSACFs corresponding to the network slice through the network open function NEF includes: Send a second network slice status subscription request to the NEF, wherein the NEF sends the second network slice status subscription request to multiple NSACFs corresponding to the network slice.

4. The method according to claim 1, characterized in that: Subscribing slice status information of the network slice to multiple NSACFs corresponding to the network slice through the network open function NEF includes: Send a second network slice status subscription request to the NEF, wherein the NEF sends the subscription request to the second NSACF among the multiple NSACFs corresponding to the network slice.

5. The method according to claim 2, characterized in that: Also includes: Generate network slice status response information according to the status information of the network slice among the multiple NSACFs; The network slice status response information is sent to the AF or ASP.

6. The method according to claim 2, characterized in that The first network slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

7. The method according to claim 6, characterized in that The subscription event includes at least one of the following: The number of terminals registered on the requested network slice; The number of packet data unit (PDU) sessions established on the requested network slice; The ratio of the number of terminals registered on the requested network slice to the maximum number of terminals allowed to be registered; The ratio of the number of PDU sessions established on the requested network slice to the maximum number of PDU sessions allowed to be established; The number of registered terminals on the requested network slice and the ratio of the number of registered terminals to the maximum number of allowed registered terminals; The number of established PDU sessions on the requested network slice and the ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.

8. The method according to claim 6, characterized in that The subscription event screening information includes at least one of the following: Single network slice selection assistance information S-NSSAI of the requested network slice; The registration area RA of the requested network slice; A combination of the S-NSSAI of the requested network slice and the data network name DNN; The area of ​​interest IoA of the requested network slice.

9. The method according to claim 6, characterized in that The subscription event report mode information includes at least one of the following: The threshold that triggers the report; The periodic interval for triggering reporting.

10. The method according to claim 5, characterized in that The first network slice status subscription request also includes an immediate reporting flag, wherein the immediate reporting flag is used to instruct the first NSACF to immediately send the network slice status response information upon receiving the network slice status subscription request.

11. The method according to claim 5, characterized in that The generating network slice status response information according to the status information of the network slice among the multiple NSACFs includes: The status information of the network slice among the multiple NSACFs is aggregated to generate the network slice status response information.

12. The method according to any one of claims 1 to 11, characterized in that: Also includes: The multiple NSACFs corresponding to the network slice are determined through the network configuration or operator policy in the NEF.

13. The method according to any one of claims 1 to 11, characterized in that: The first NSACF is the main NSACF or the proxy NSACF among the multiple NSACFs corresponding to the network slice.

14. The method according to claim 3 or 4, characterized in that The second network slice status subscription request includes at least one of subscription events, subscription event filtering information and subscription event reporting mode information.

15. The method according to claim 6, characterized in that Also includes: The network slice status response information is filtered according to the subscription event filtering information.

16. The method according to claim 6, characterized in that Also includes: Determine whether the reporting conditions are met based on the subscription event report mode information; If the reporting conditions are met, the network slice status response information is reported.

17. The method according to claim 5, characterized in that The receiving a slice status subscription request sent by an AF or an ASP includes: If the AF or ASP is an untrusted AF or ASP, the slice status subscription request sent by the AF or ASP is received through NEF.

18. The method according to claim 17, characterized in that The first NSACF is selected from the NEF.

19. The method according to claim 18, characterized in that The first NSACF is selected by the NEF through the NRF, or the first NSACF is selected by the NEF through local configuration.

20. A method for reporting slice status information of multiple slice admission control functions NSACF, characterized in that: Applied to NEF, the method comprises the following steps: Receiving a first network slice status subscription request sent by a first NSACF, wherein the first network slice status subscription request includes a network slice; Subscribe slice status information of the network slice to multiple NSACFs corresponding to the network slice; the multiple NSACFs corresponding to the network slice include the first NSACF; Obtain slice status information of the network slice reported by the multiple NSACFs; The slice status information is sent to the first NSACF.

21. The method according to claim 20, characterized in that The subscribing to slice status information of the network slice from multiple NSACFs corresponding to the network slice includes: Receiving a second network slice status subscription request sent by the first NSACF; Send the second network slice status subscription request to multiple NSACFs corresponding to the network slice.

22. The method of claim 20, wherein: The subscribing to slice status information of the network slice from multiple NSACFs corresponding to the network slice includes: Receiving a second network slice status subscription request sent by the first NSACF; Send the subscription request to the second NSACF among the multiple NSACFs corresponding to the network slice.

23. The method of claim 20, wherein: The first network slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

24. The method of claim 23, wherein: The subscription event includes at least one of the following: The number of terminals registered on the requested network slice; The number of packet data unit (PDU) sessions established on the requested network slice; The ratio of the number of terminals registered on the requested network slice to the maximum number of terminals allowed to be registered; The ratio of the number of PDU sessions established on the requested network slice to the maximum number of PDU sessions allowed to be established; The number of registered terminals on the requested network slice and the ratio of the number of registered terminals to the maximum number of allowed registered terminals; The number of established PDU sessions on the requested network slice and the ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.

25. The method of claim 23, wherein: The subscription event screening information includes at least one of the following: Single network slice selection assistance information S-NSSAI of the requested network slice; The registration area RA of the requested network slice; A combination of the S-NSSAI of the requested network slice and the data network name DNN; The area of ​​interest IoA of the requested network slice.

26. The method of claim 23, wherein: The subscription event report mode information includes at least one of the following: The threshold that triggers the report; The periodic interval for triggering reporting.

27. The method of claim 23, wherein: The first network slice status subscription request also includes an immediate reporting flag, wherein the immediate reporting flag is used to instruct the first NSACF to immediately send network slice status response information upon receiving the first network slice status subscription request.

28. The method according to any one of claims 20 to 27, characterized in that Also includes: The multiple NSACFs corresponding to the network slice are determined through network configuration or operator policy.

29. The method according to any one of claims 20 to 27, characterized in that The first NSACF is the main NSACF or the proxy NSACF among the multiple NSACFs corresponding to the network slice.

30. The method according to claim 21 or 22, characterized in that The second network slice status subscription request includes at least one of subscription events, subscription event filtering information and subscription event reporting mode information.

31. The method of claim 20, wherein: Also includes: The first NSACF was selected.

32. The method of claim 31, wherein: The selecting of obtaining the first NSACF comprises: The first NSACF is obtained by NRF selection; Alternatively, the first NSACF is obtained through local configuration selection.

33. A method for reporting slice status information of multiple slice admission control functions NSACF, characterized in that: Applied to AF or ASP, the method comprises the following steps: Sending a first network slice status subscription request to a first NSACF, wherein the first network slice status subscription request includes a network slice; the network slice corresponds to multiple NSACFs, and the first NSACF belongs to the multiple NSACFs corresponding to the network slice; Receive network slice status response information sent by the first NSACF.

34. The method of claim 33, wherein: The first network slice status subscription request includes at least one of subscription events, subscription event filtering information, and subscription event reporting mode information.

35. The method of claim 34, wherein: The subscription event includes at least one of the following: The number of terminals registered on the requested network slice; The number of packet data unit (PDU) sessions established on the requested network slice; The ratio of the number of terminals registered on the requested network slice to the maximum number of terminals allowed to be registered; The ratio of the number of PDU sessions established on the requested network slice to the maximum number of PDU sessions allowed to be established; The number of registered terminals on the requested network slice and the ratio of the number of registered terminals to the maximum number of allowed registered terminals; The number of established PDU sessions on the requested network slice and the ratio of the number of established PDU sessions to the maximum number of PDU sessions allowed to be established.

36. The method of claim 34, wherein: The subscription event screening information includes at least one of the following: Single network slice selection assistance information S-NSSAI of the requested network slice; The registration area RA of the requested network slice; A combination of the S-NSSAI of the requested network slice and the data network name DNN; The area of ​​interest IoA of the requested network slice.

37. The method of claim 34, wherein: The subscription event report mode information includes at least one of the following: The threshold that triggers the report; The periodic interval for triggering reporting.

38. The method of claim 34, wherein: The first network slice status subscription request also includes an immediate reporting flag, wherein the immediate reporting flag is used to instruct the first NSACF to immediately send the network slice status response information upon receiving the first network slice status subscription request.

39. The method according to any one of claims 33 to 38, characterized in that The multiple NSACFs corresponding to the network slice are determined by the network configuration or operator policy in the NEF.

40. The method according to any one of claims 33 to 38, characterized in that The first NSACF is the main NSACF or the proxy NSACF among the multiple NSACFs corresponding to the requested network slice.

41. The method of claim 33, wherein: The first NSACF is selected by the NEF through the NRF, or the first NSACF is selected by the NEF through local configuration.

42. A slice status information reporting device of multiple slice admission control functions NSACF, characterized in that: Applied to the first NSACF, the apparatus comprises: A subscription module, used to subscribe to slice status information of the network slice from multiple NSACFs corresponding to the network slice through a network open function NEF; the multiple NSACFs corresponding to the network slice include the first NSACF; An acquisition module is used to obtain the slice status information of the network slice reported by the multiple NSACFs through the NEF.

43. A slice status information reporting device of multiple slice admission control functions NSACF, characterized in that: Applied to NEF, the device comprises: A first receiving module is used to receive a first network slice status subscription request sent by a first NSACF, wherein the first network slice status subscription request includes a network slice; A first sending module, used to subscribe slice status information of the network slice to multiple NSACFs corresponding to the network slice; the multiple NSACFs corresponding to the network slice include the first NSACF; A second receiving module is used to obtain the slice status information of the network slice reported by the multiple NSACFs; The second sending module is used to send the slice status information to the first NSACF.

44. A slice status information reporting device of multiple slice admission control functions NSACF, characterized in that: Applied to AF or ASP, the device comprises: A third sending module is used to send a first network slice status subscription request to a first NSACF, wherein the first network slice status subscription request includes a network slice; the network slice corresponds to multiple NSACFs, and the first NSACF belongs to the multiple NSACFs corresponding to the network slice; The third receiving module is used to receive the network slice status response information sent by the first NSACF.

45. A communication device, wherein: include: Transceiver; Memory; The processor is connected to the transceiver and the memory respectively, and is configured to control the wireless signal reception and transmission of the transceiver by executing computer executable instructions on the memory, and can implement the method described in any one of claims 1-19 or 20-32 or 33-41.

46. ​​A computer storage medium, wherein: The computer storage medium stores computer executable instructions; after the computer executable instructions are executed by the processor, the method described in any one of claims 1-19 or 20-32 or 33-41 can be implemented.

Images