A method, network device and storage medium allowing NSSAI determination

Abstract

The embodiment of the present invention provides a method, network device and storage medium for determining allowed NSSAI, which obtains and analyzes the historical service access data of the target user to the target service through NWDAF, thereby obtaining the access time analysis result of the target user to the target service, and then sends the access time analysis result to the slice determination network element. The slice determination network element can determine the target user's access time habits to the target service based on the access time analysis result, thereby predicting when the target user may need to access the target service and when the target user may not need to access the target service, and then determine whether to use the NSSAI of the target network slice as the Allowed NSSAI of the target user based on the prediction result. While ensuring the user's service access needs, it can also take into account the satisfaction of the SLA of the target network slice, which is conducive to optimizing the service access experience of the network slice user.

Description

Technical Field

[0001] The embodiments of the present invention relate to but are not limited to the field of communications. Specifically, they relate to but are not limited to a method, a network device and a storage medium for allowing NSSAI (Network Slice Selection Assistance Information) to be determined. Background Art

[0002] 5G networks support a variety of scenarios, and different scenarios have different requirements for network functions and performance. Network slicing allows operators to divide multiple virtual logical end-to-end networks on demand on the same hardware infrastructure. Each network slice is logically isolated and adapts to the different feature requirements of various types of services.

[0003] At present, the network side determines the Allowed NSSAI (allowed network slice selection auxiliary information) for the user based on the user's Requested NSSAI (requested network slice selection auxiliary information) and Subscribed NSSAI (subscribed network slice selection auxiliary information), as well as local static policies, by AMF (Access and Mobility Management function) or NSSF (Network Slice Selection Function). Based on the Allowed NSSAI decided by the network side, the user activates the PDU Session (PDU session) of the corresponding network slice, thereby using the network slice to access the AF (Application Function). However, in some cases, the maximum number of users and / or the maximum number of sessions that can be accessed by the network slice may exceed the SLA (Service Level Agreement) of the network slice, affecting the user experience. Summary of the invention

[0004] The method for determining whether to allow NSSAI, the network device, and the storage medium provided in the embodiments of the present invention mainly solve the technical problem of how to ensure the SLA of the network slice when determining whether to allow NSSAI for the user.

[0005] To solve the above technical problem, an embodiment of the present invention provides a method for allowing NSSAI determination, including:

[0006] Obtain historical service access data of the target user accessing the target service, where the target service is the service on the target network slice;

[0007] Determine the access time analysis result of the target user for accessing the target service based on the historical service access data of the target user;

[0008] The target user's access time analysis result for the target service is sent to the slice determination network element. The access time analysis result is used by the slice determination network element to determine the allowed NSSAI for the target user in combination with the service level agreement SLA of the target network slice.

[0009] An embodiment of the present invention further provides a method for allowing NSSAI determination, including:

[0010] Receive the access time analysis result of the target user accessing the target service sent by NWDAF (Network Data Analytics Function), where the access time analysis result is obtained by NWDAF analyzing and processing the historical service access data of the target user accessing the target service, and the target service is the service on the target network slice;

[0011] Based on the access time analysis results and the SLA of the target network slice, NSSAI is allowed for the target user.

[0012] An embodiment of the present invention further provides a network device, the network device comprising a processor, a memory and a communication bus;

[0013] The communication bus is used to realize the connection and communication between the processor and the memory;

[0014] The processor is used to execute one or more programs stored in the memory to implement the steps of the first method for allowing NSSAI determination; or, the processor is used to execute one or more programs stored in the memory to implement the steps of the second method for allowing NSSAI determination.

[0015] An embodiment of the present invention also provides a storage medium, which stores at least one of a first NSSAI-allowed determination program and a second NSSAI-allowed determination program. The first NSSAI-allowed determination program can be executed by one or more processors to implement the steps of the first NSSAI-allowed determination method mentioned above; the second NSSAI-allowed determination program can be executed by one or more processors to implement the steps of the second NSSAI-allowed determination method mentioned above.

[0016] The method, network device and storage medium for determining the allowed NSSAI provided by the embodiment of the present invention obtain the historical service access data of the target user to the target service through NWDAF, and analyze and process the historical service access data to obtain the access time analysis result of the target user to the target service. Then, the target user's access time analysis result to the target service is sent to the slice determination network element, so that the slice determination network element determines the allowed NSSAI (i.e., allowed NSSAI) for the target user according to the access time analysis result and the SLA of the target network slice after receiving the access time analysis result sent by NWDAF. Based on the access time analysis result provided by NWDAF, the slice determination network element can determine the target user's access time habits to the target service, thereby predicting the time when the target user may need to access the target service and the time when the target user may not need to access the target service, and then determine whether to use the NSSAI of the target network slice as the Allowed NSSAI of the target user according to the prediction result. While ensuring the user's service access needs, it can also take into account the satisfaction of the SLA of the target network slice, which is conducive to optimizing the service access experience of the network slice user.

[0017] Other features and corresponding beneficial effects of the present invention are described in the latter part of the specification, and it should be understood that at least part of the beneficial effects become obvious from the description in the specification of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 A flow chart of a method for allowing NSSAI determination provided in Embodiment 1 of the present invention;

[0019] Figure 2 This is a schematic diagram of the architecture of a 5G network provided in Embodiment 1 of the present invention;

[0020] Figure 3 A schematic diagram of the NWDAF operation shown in the first embodiment of the present invention;

[0021] Figure 4 A flow chart of a method for determining NSSAI provided in Embodiment 2 of the present invention;

[0022] Figure 5 A flow chart of the method for allowing NSSAI determination provided in Example 1 of Embodiment 3 of the present invention;

[0023] Figure 6 A flow chart of a method for allowing NSSAI determination provided in Example 2 of Embodiment 3 of the present invention;

[0024] Figure 7 A schematic diagram of a hardware structure of a network device provided in Embodiment 4 of the present invention;

[0025] Figure 8 A schematic diagram of a system allowing NSSAI determination provided in Embodiment 4 of the present invention. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical solution and advantages of the present invention more clearly understood, the following is a further detailed description of the embodiments of the present invention through specific implementation methods combined with the accompanying drawings. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0027] Embodiment 1:

[0028] In order to solve the problem in the related art that when NSSF or AMF determines Allowed NSSAI for a user, the number of users and / or sessions accessing the network slice may exceed the SLA of the network slice, thereby affecting the user service access experience on the network slice, this embodiment provides a method for determining Allowed NSSAI. Figure 1 An interactive flow chart showing the method for allowing NSSAI determination is shown:

[0029] S102: NWDAF obtains historical service access data of the target user accessing the target service.

[0030] NWDAF is a core network control plane entity, which is responsible for obtaining user information and network information from other NFs (Network Functions), AFs (Application Functions), OAMs (Operation Administration and Maintenance), etc., and generating analysis data after processing the obtained information, and providing the analysis data to the NFs, AFs or OAMs that have subscribed to it. Among them, user information includes dynamic information such as user mobility information, user access services, and static information such as user contract information. Network information includes dynamic information such as NF load and static information such as network deployment.

[0031] In this embodiment, the information obtained by NWDAF includes data reflecting the target user's access to the target service. Since these data can reflect the target user's past access to the target service, they are called historical service access data. The so-called target service refers to the service on the target network slice. The historical service access data of the target user to the target service obtained by NWDAF is actually data that can reflect the target user's use of the target network slice to access the service.

[0032] In some examples of this embodiment, NWDAF can directly obtain the historical service access data of the target user accessing the target service from at least one of AF, OAM and other core network elements, where the other core network elements refer to other core network elements other than NWDAF, such as SMF (Session Management function), UPF (User plane function), etc. In one example of this embodiment, NWDAF can send a data acquisition request to at least one of AF, OAM and other core network elements, and then receive the historical service access data of the target user accessing the target service sent by the corresponding network device.

[0033] In some other examples of this embodiment, NWDAF can also obtain the historical business access data of the target user on at least one of the AF, OAM and other core network elements in an indirect manner. In these examples, the data storage platform can first complete data collection from at least part of the AF, OAM and other core network elements, and then NWDAF, NWDAF obtains the historical business access data of the target user from the data storage platform.

[0034] S104: NWDAF determines an access time analysis result of the target user accessing the target service according to the historical service access data of the target user.

[0035] After the NWDAF obtains the historical service access data of the target user, it can process and analyze the obtained historical service access data to obtain the access time analysis result of the target user's access to the target service. It can be understood that in this embodiment, the access time analysis result can at least reflect the time habit of the target user to access the target service. For example, the NWDAF performs statistics based on the obtained historical access data to determine the time period when the target user most frequently accesses the target service in a day, and / or, calculates the time period when the target user usually does not access the target service in a day.

[0036] In some examples of this embodiment, the access time analysis results obtained by NWDAF based on the historical business access data of the target user include at least one of the time classification identification of the target user, the actual time when the target user's category accesses the target business, and the predicted time when the target user's category accesses the target business.

[0037] For example, in one example, the access time analysis result only includes the time classification identifier of the target user. The so-called time classification identifier is the identification information assigned to each category after the users are classified according to the time period when each user accesses the target service. The time classification identifier can uniquely identify a category in all categories. In these examples, the network element that needs to use the access time analysis result, such as the slice determination network element in this embodiment, pre-agrees with the NWDAF on the correspondence between each time classification identifier and the target service access time period. In this way, when the slice determination network element obtains the access time analysis result of the target user from the NWDAF, according to the time classification identifier carried in the access time analysis result, the time when the target user accesses the target service can be determined by querying the pre-set correspondence. It can be understood that the correspondence pre-agreement between the slice determination network element and the NWDAF can store the time classification identifier and the actual time when the user of the category corresponding to the time classification identifier accesses the target service, or the time classification identifier and the predicted time when the user of the category corresponding to the NWDAF accesses the target service.

[0038] In another example of the present embodiment, the access time analysis result only includes the actual time when the target user's classification performs target service access. It is understandable that, since users usually maintain their personal habits when performing service access, when the access time analysis result includes the actual time when the target user's classification performs target service access, the actual time is basically equivalent to the time when the target user's classification performs target service access in the future, that is, the predicted time when the target user's classification performs target service access. For example, a target user always plays games between 21:00-23:00 in the evening for a period of time in the past, so the target user is also very likely to have a demand for accessing game services between 21:00-23:00 in the future. Similarly, a class of users basically accessed game services around 21:00-23:00 in the evening for a period of time in the past, so this type of user also basically has a demand for accessing game services between 21:00-23:00 in the future.

[0039] In another example of this embodiment, the access time analysis result only includes the predicted time for the target user's category to access the target service.

[0040] In addition, in some examples of this embodiment, the access time analysis results also include the time classification identifier of the target user's access to the target service, the actual time when the target user's category accesses the target service, and the predicted time when the target user's category accesses the target service.

[0041] S106: NWDAF sends the target user's access time analysis result to the target service to the slice determination network element.

[0042] In this embodiment, after the NWDAF obtains the target user's access time analysis result to the target service, it will send the access time analysis result to the slice determination network element. In some examples of this embodiment, the slice determination network element can be AMF, which is a core network control plane entity and is mainly responsible for user mobility management, including registration and temporary identity allocation; maintaining idle (IDLE) and connected (CONNECT) states and state migration; switching in the CONNECT state; triggering paging in the user IDLE state and other functions.

[0043] In some other examples of this embodiment, the slice determination network element may be NSSF. NSSF is also a core network control plane entity responsible for selecting a target NSI (Network Slice Instance).

[0044] S108: The slice determination network element determines that NSSAI is allowed for the target user based on the access time analysis results and the SLA of the target network slice.

[0045] After the slice determination network element receives the access time analysis result sent by NWDAF, it can determine the Allowed NSSAI for the target user based on the access time analysis result and the SLA of the target network slice. In some examples of this embodiment, if it is determined based on the access time analysis result of the target user that the target user currently has a need to access the target service, the slice determination network element can use the target network slice as the network slice currently allowed by the target user, and determine the NSSAI of the target network slice as the Allowed NSSAI of the target user. Conversely, if it is inferred based on the access time analysis result of the target user that the target user has no recent need to access the target service, the NSSAI of the target network slice may not be used as the current Allowed NSSAI of the target user.

[0046] In some examples of this embodiment, when the slice determination network element determines the Allowed NSSAI for the target user, it will also make a selection based on the Requested NSSAI and Subscribed NSSAI of the target user. For example, in some examples of this embodiment, if the Requested NSSAI of user A includes the NSSAI of network slice a, and user A has previously signed a contract for network slice a, in this case, the slice determination network element can further determine whether to use network slice a as the Allowed NSSAI of the user based on the access time analysis result of the service on network slice a by user A. If the NSSAI of network slice a is not included in the Requested NSSAI of user A, or the NSSAI of network slice a is not included in the Subscribed NSSAI of user A, the slice determination network element does not need to make a judgment based on the access time analysis result of the service on network slice a by user A, and the slice determination network element does not even need to obtain the access time analysis result of user A from the NWDAF.

[0047] It can be understood that, under normal circumstances, NWDAF analyzes and processes the historical service access data of the requesting user according to the request of the slice determination network element to obtain the access time analysis result of the user. For example, in some examples of this embodiment, when the slice determination network element needs to determine the Allowed NSSAI for a certain user, the user is the target user, and the slice determination network element can send an analysis request for the user to NWDAF. In the analysis request, the slice determination network element can carry the identification information of the target user and the type of analysis data to be requested. After receiving the analysis request, NWDAF obtains the historical service access data of the target user according to the identification information and analysis data type information in the analysis request, and then processes these data to obtain the access time analysis result of the target user and send it to the slice determination network element. In these examples, after NWDAF returns the access time analysis result of the target user to the target service to the slice determination network element, it is equivalent to having responded to the analysis request of the network slice selection network, and an analysis request process of the slice determination network element ends. If the slice determination network element wants to obtain the access time analysis result of the same target user to the same target service next time, the slice determination network element needs to resend the analysis request for the target user to NWDAF.

[0048] In some other examples of this embodiment, the slice determination network element can subscribe to the target user's access time analysis result for the target service from NWDAF. In these examples, the slice determination network element can carry the identification information of the target user in the subscription request, and the information characterizing that the subscribed analysis data type is the access time analysis result. In these examples, after receiving the analysis request, NWDAF will also obtain the historical service access data of the target user for the target service, and then process these data to obtain the target user's access time analysis result for the target service, and send it to the slice determination network element. However, unlike the aforementioned example, NWDAF will periodically or irregularly re-acquire the target user's historical service access data for the target service in the subsequent process, and then re-analyze and process to obtain a better access time analysis result in real time, and send the new access time analysis result to the slice determination network element. It can be seen that in this solution in which the slice determination network element subscribes to the target user's access time analysis result from NWDAF, as long as the slice determination network element does not cancel its subscription to the target user from NWDAF, the slice determination network element can receive the real-time access time analysis result of the target user from NWDAF regularly or irregularly. In this way, the access time analysis results obtained by the slice determination network element are constantly adjusted according to the recent access habits of the target user, and are more in line with the recent access time habits of the target user. The slice determination network element uses this real-time access time analysis result as the basis for helping the target user determine the Allowed NSSAI, which helps to improve the accuracy of the Allowed NSSAI determination, better maintain user experience, and meet the SLA of network slicing.

[0049] The method for determining allowed NSSAI provided in an embodiment of the present invention determines Allowed NSSAI for a target user by combining the SLA of the network slice with the NWDAF analysis result of the target user's access time to the target service. On the one hand, when the target user has a need to access the target service, the network slice corresponding to the target service can be added to the Allowed NSSAI of the target user to meet the user's needs. On the other hand, when it is predicted that the target user temporarily has no need to access the target service, the network slice corresponding to the target service is not added to the Allowed NSSAI of the target user, thereby ensuring the SLA of the network slice corresponding to the target service.

[0050] Embodiment 2:

[0051] In order to enable those skilled in the art to understand the advantages and details of the solutions provided in the foregoing embodiments more clearly, this embodiment will continue to explain the method for allowing NSSAI to be determined. In this embodiment, it is assumed that the method for allowing NSSAI to be determined is applied to a 5G network. Figure 2 A brief description of the 5G network architecture:

[0052] The 5G network includes: UE (User Equipment) 201, RAN (Radio Access Network) 202, AMF 203, AUSF (Authentication Server Function) 204, UDM (Unified Data Management) 205, SMF 206, UPF 207, PCF (Policy Control Functionality) 208, NEF (Network Exposure Function) 209, NRF (NF Repository Function) 210, and NSSF 211.

[0053] UE 201 mainly accesses the 5G network and obtains services through the wireless air interface. UE 201 interacts with the base station through the air interface, and interacts with the AMF 203 of the core network through NAS (Non-Access Stratum, non-access layer signaling).

[0054] RAN 202 is responsible for air interface resource scheduling for terminals to access the network and air interface connection management.

[0055] AMF 203, the core network control plane entity, is mainly responsible for user mobility management, including registration and temporary identity allocation; maintaining idle and connected states and state migration; user switching in the CONNECT state; triggering paging in the IDLE state, etc.

[0056] AUSF 204, a core network control plane entity, is mainly responsible for user authentication and authorization to ensure that the user is a legitimate user.

[0057] UDM 205, a core network control plane entity, belongs to the user server and permanently stores the user's subscription data.

[0058] SMF 206, a core network control plane entity, is mainly responsible for maintaining PDU Sessions, allocating user IP addresses, and has QoS (Quality of Service) control and billing functions; it caches downlink data packets received when UE 201 is in IDLE state, and notifies AMF 203 to page users, etc.

[0059] UPF 207, a core network user plane functional entity, is responsible for forwarding user data packets and also collects statistics on user data packets for billing and other functions.

[0060] PCF 208, core network control plane entity, is responsible for access and mobility management policies, UE policies, session management policies and charging rules. This functional entity mainly generates access and mobility management policies, UE routing policies, QoS rules and charging rules for user data transmission based on service information, user subscription information and operator configuration information.

[0061] NEF 209, the core network control plane entity, is responsible for opening up mobile network capabilities to the outside world.

[0062] NRF 210, the core network control plane entity, is responsible for dynamic registration of service capabilities of network functions and network function discovery.

[0063] NSSF 211, the core network control plane entity, is responsible for the selection of the target NSI.

[0064] Compared with previous mobile networks, 5G networks have introduced network slicing, restructured the network, and adopted a service-oriented architecture to provide users with richer services. In addition, 5G networks have also introduced NWDAF to enable more automated management and more flexible use of 5G networks. Figure 3 Explain the work of NWDAF:

[0065] NWDAF 30 is an entity in the core network control plane, responsible for obtaining raw data such as user and network information from AF, OAM, RAN or other 5GC NFs, processing the raw data, generating analysis data, and providing the analysis data to the AF, OAM, RAN3 or other 5GC NFs that have subscribed to it. User information includes dynamic information such as user mobility information, services accessed by users, and static information such as contracts. Network information includes dynamic information such as NF load and static information such as network deployment.

[0066] AF provides service or user related information to NWDAF directly or through NEF, and can also subscribe service or user related information from NWDAF. OAM collects various statistical information of the network and provides it to NWDAF, and can also subscribe service or user related information from NWDAF.

[0067] It is understood by those skilled in the art that the method for allowing NSSAI determination can also be applied to other network systems. The following takes the method for allowing NSSAI determination to be applied to a 5G network system as an example for explanation. Figure 4 Shown is a flow chart that allows NSSAI to determine:

[0068] S402: The slice determination network element sends a subscription request to the NWDAF.

[0069] In this embodiment, the subscription request sent by the slice determination network element to the NWDAF includes subscription type information and identification information of the target user, wherein the subscription type information is used to characterize that the slice determination network element requests to subscribe to the access time analysis result of the target service. Therefore, the entire subscription request is used to request NWDAF to subscribe to the access time analysis result of the target user to the target service. The identification information of the target user may include but is not limited to at least one of a SUPI (Subscription Permanent Identifier) ​​list and an Interval Group ID (Interval Group ID).

[0070] S404: NWDAF determines the target user and target service according to the subscription request.

[0071] After receiving the subscription request, the NWDAF may determine the target user according to the identification information of the target user in the subscription request, and determine the target service according to the subscription type information.

[0072] S406: NWDAF obtains historical service access data of the target user accessing the target service.

[0073] In this embodiment, NWDAF can directly obtain the historical service access data of the target user to the target service from at least one of AF, OAM and other core network elements. For example, NWDAF obtains the historical service access data of the target user from SMF, UPF and OAM network elements.

[0074] However, in some other examples of this embodiment, NWDAF can also obtain the historical business access data of the target user from the data storage platform, and the data storage platform can collect data on AF, OAM and each core network element in advance, so that NWDAF can obtain data on AF, OAM or other core network elements indirectly.

[0075] In some examples of this embodiment, the historical service access data acquired by NWDAF includes information that can reflect the services accessed by the target user and the time information of accessing the services. In some other examples of this embodiment, the historical service access data may also include other information such as the location information of the target user when accessing the service and the number of accessed sessions.

[0076] S408: NWDAF determines the access time analysis result of the target user accessing the target service according to the historical service access data of the target user.

[0077] After NWDAF obtains the historical service access data of the target user, it can process and analyze the obtained historical service access data to obtain the access time analysis result of the target user's access to the target service. In this embodiment, the access time analysis result also includes the time classification identification of the target user's access to the target service, the actual time when the target user's category accesses the target service, and the predicted time when the target user's category accesses the target service. However, it can be understood that in some other examples, the access time analysis result obtained by NWDAF may also include only one or two of the above-mentioned information.

[0078] S410: NWDAF sends the target user's access time analysis result to the target service to the slice determination network element.

[0079] The slice determination network element can be AMF or NSSF. However, if the slice determination network element is NSSF, AMF needs to request the target user's Allowed NSSAI from NSSF after receiving the target user's registration request. When AMF requests the target user's Allowed NSSAI from NSSF, AMF can carry the target user's identification information to NSSF to indicate to NSSF which user's Allowed NSSAI currently needs to be requested. The identification information of the target user here includes but is not limited to at least one of SUPI, PEI (Permanent Equipment Identifier), and GPSI (Generic Public Subscription Identifier).

[0080] S412: The slice determination network element determines that NSSAI is allowed for the target user based on the access time analysis results and the SLA of the target network slice.

[0081] After the slice determination network element receives the access time analysis result, if it determines the Allowed NSSAI for the target user based on the access time analysis result of the target user, the Requested NSSAI and Subscribed NSSAI of the target user, the static policy on the network side, and the SLA of the target network slice:

[0082] If the target user's Requested NSSAI and Subscribed NSSAI both include the target network slice, and the target user's access time analysis result determines that the target user currently has a need to access the target service, the target network slice is used as the target user's currently allowed network slice, and the NSSAI of the target network slice is determined as the target user's Allowed NSSAI. Conversely, if any of the following situations occurs, the NSSAI of the target network slice does not need to be used as the target user's current Allowed NSSAI:

[0083] The target user's Requested NSSAI does not include the target network slice;

[0084] The target user’s Subscribed NSSAI does not include the target network slice;

[0085] According to the target user's access time analysis results, it is inferred that the target user has no need to access the target service recently.

[0086] It is understandable that if the target user's Requested NSSAI and Subscribed NSSAI both include the target network slice, then in the relevant technology, it is necessary to select the NSSAI of the target network slice as the current Allowed NSSAI of the target user. However, in this embodiment, because it is inferred based on the access time analysis results of the target user that the target user has no recent need to access the target service, the slice determination network element does not need to use the NSSAI of the target network slice as the current Allowed NSSAI of the target user. This can reduce one access user of the target network slice, thereby "making room" for other users who currently have real access needs to the target network slice, avoiding indiscriminate access of users with and without needs to the target network slice, resulting in the occurrence of the target network slice SLA not being met. While ensuring the user's business needs, the SLA of the target network slice is taken into account, which is conducive to optimizing the business access experience of network slice users.

[0087] Embodiment three:

[0088] The following two examples further illustrate the above-mentioned solution for allowing NSSAI determination:

[0089] Example 1 - Slice determines the network element as NSSF:

[0090] Please combine the following Figure 5 :

[0091] S502: NSSF sends a subscription request to NWDAF.

[0092] In this embodiment, the subscription request carries information such as the type of analysis data to be subscribed (the time analysis result of the target user's access to the target service) and the subscribed target user (the SUPI list or Interval GroupID of the target user).

[0093] S504: NWDAF sends a subscription response to NSSF.

[0094] S506: NWDAF obtains historical service access data of the target user accessing the target service from SMF, UPF, and AF.

[0095] It is understandable that NWDAF can obtain historical business access data from SMF, UPF, AF, etc. directly or indirectly through a data storage platform, etc. to obtain historical business access data of target users at SMF, UPF, AF, etc.

[0096] S508: NWDAF determines the access time analysis result of the target user accessing the target service based on the historical service access data.

[0097] The generated access time analysis results include the time classification information of the target users, the actual time when the users of each time classification access the target service, and the predicted time when the users of each time classification access the target service.

[0098] S510: NWDAF sends the access time analysis result to NSSF.

[0099] S512: NSSF returns an analysis result response message.

[0100] S514: NSSF saves the access time analysis result of the target user.

[0101] S516: The target user initiates a registration request.

[0102] S518: AMF sends a user network slice request message to NSSF.

[0103] The user network slice request message carries the target user's Requested NSSAI, Subscribed NSSAI, and the target user's currently accessed TA (Tracking Area), SUPI and other information.

[0104] S520: NSSF determines the Allowed NSSAI for the target user according to the root access time analysis result, the local static policy, the RequestedNSSAI and the Subscribed NSSAI of the target user.

[0105] S522: NSSF sends the target user’s Allowed NSSAI to AMF.

[0106] S524: AMF delivers the Allowed NSSAI and other information to the target user in the registration acceptance message.

[0107] Example 2 - Slice determines the network element as AMF:

[0108] Please combine Figure 6 :

[0109] S602: AMF sends a subscription request to NWDAF.

[0110] In this embodiment, the subscription request carries information such as the type of analysis data to be subscribed (the time analysis result of the target user's access to the target service) and the subscribed target user (the SUPI list or Interval GroupID of the target user).

[0111] S604: NWDAF sends a subscription response to AMF.

[0112] S606: NWDAF obtains historical service access data of the target user accessing the target service from SMF, UPF, and AF.

[0113] It is understandable that NWDAF can obtain historical business access data from SMF, UPF, AF, etc. directly or indirectly through a data storage platform, etc. to obtain historical business access data of target users at SMF, UPF, AF, etc.

[0114] S608: NWDAF determines the access time analysis result of the target user accessing the target service based on the historical service access data.

[0115] The generated access time analysis results include the time classification information of the target users, the actual time when the users of each time classification access the target service, and the predicted time when the users of each time classification access the target service.

[0116] S610: NWDAF sends the access time analysis result to AMF.

[0117] S612: AMF returns an analysis result response message.

[0118] S614: AMF saves the access time analysis result of the target user.

[0119] S616: The target user initiates a registration request.

[0120] S618: AMF determines the Allowed NSSAI for the target user based on the root access time analysis results, local static policy, and the target user's RequestedNSSAI and Subscribed NSSAI.

[0121] S620: AMF delivers the Allowed NSSAI and other information to the target user in the registration acceptance message.

[0122] The method for determining allowed NSSAI provided in this embodiment enables the network side to timely update the user's Allowed NSSAI based on information such as dynamic changes in the user's access to services, thereby ensuring the user's service experience while also meeting the SLA of the network slice.

[0123] Embodiment 4:

[0124] The present embodiment provides a storage medium, which includes volatile or non-volatile, removable or non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, computer program modules or other data). The storage medium includes, but is not limited to, RAM (Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable read only memory), flash memory or other memory technology, CD-ROM (Compact Disc Read-Only Memory), digital versatile disk (DVD) or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device, or any other medium that can be used to store the desired information and can be accessed by a computer.

[0125] The storage medium may store one or more computer programs that can be read, compiled and executed by one or more processors. In the present embodiment, the storage medium may store at least one of a first allowed NSSAI determination program and a second allowed NSSAI determination program. The first allowed NSSAI determination program may be executed by one or more processors to implement the process on the NWDAF side in any one of the allowed NSSAI determination methods described in the aforementioned embodiments. The second allowed NSSAI determination program may be executed by one or more processors to implement the process on the network element side of the slice determination in any one of the allowed NSSAI determination methods described in the aforementioned embodiments.

[0126] This embodiment also provides a computer program product, including a computer readable device, on which the computer program shown above is stored. In this embodiment, the computer readable device may include the computer readable storage medium shown above. For example, the computer program product includes a network device, such as Figure 7 As shown: the network device 7 includes a processor 71, a memory 72, and a communication bus 73 for connecting the processor 71 and the memory 72, wherein the memory 72 may be the aforementioned storage medium storing at least one of the first allowed NSSAI determination program and the second allowed NSSAI determination program. In some examples, the processor 71 may read the first allowed NSSAI determination program, compile and execute the process of implementing the allowed NSSAI determination method NWDAF side described in the aforementioned embodiment:

[0127] The processor 71 obtains the historical service access data of the target user for accessing the target service, where the target service is the service on the target network slice. Then the processor 71 determines the access time analysis result of the target user for accessing the target service according to the historical service access data of the target user, and sends the access time analysis result of the target user for the target service to the slice determination network element, and the access time analysis result is used by the slice determination network element to determine the allowed NSSAI for the target user in combination with the service level agreement SLA of the target network slice.

[0128] In some examples of this embodiment, the slice determination network element includes at least one of an access and mobility management function AMF and a network slice selection function NSSF.

[0129] In some examples of this embodiment, the access time analysis result includes at least one of the time classification identifier of the target user's access to the target service, the actual time when the target user's category accesses the target service, and the predicted time when the target user's category accesses the target service.

[0130] In some examples of this embodiment, when the processor 71 obtains the historical service access data of the target user accessing the target service, the historical service access data of the target user accessing the target service sent by at least one of the AF, the OAM and other core network elements may be received, and the other core network elements are other core network elements except the NWDAF;

[0131] Alternatively, in some other examples of this embodiment, the processor 71 obtains historical service access data of the target user accessing the target service from the data storage platform.

[0132] Before obtaining the historical service access data of the target user accessing the target service, the processor 71 may also first receive a subscription request sent by the slice determination network element, and determine the target user and the target service according to the subscription request. The subscription request includes the identification information and subscription type information of the target user, and the subscription type information is used to characterize that the data type subscribed by the slice determination network element is the access time analysis result of the target service.

[0133] In some other examples of this embodiment, the processor 71 may read the second allowed NSSAI determination program, compile and execute the process of slice determination network element side of the allowed NSSAI determination method described in the aforementioned embodiment:

[0134] The processor 71 receives the access time analysis result of the target user accessing the target service sent by the NWDAF, and the access time analysis result is obtained by the NWDAF analyzing and processing the historical service access data of the target user accessing the target service, and the target service is the service on the target network slice. Then, the processor 71 determines to allow NSSAI for the target user according to the access time analysis result and the SLA of the target network slice.

[0135] In some examples, before the processor 71 receives the access time analysis result of the target user accessing the target service sent by NWDAF, it will first send a subscription request including subscription type information and target user identification information to NWDAF. The subscription type information is used to characterize that the analysis data subscribed by the slice-determined network element is the access time analysis result.

[0136] When the processor 71 determines the allowed NSSAI for the target user based on the access time analysis result and the SLA of the target network slice, if the access time analysis result indicates that the target user currently has a need to access the target service, the NSSAI of the target network slice is used as the allowed NSSAI of the target user; if the access time analysis result indicates that the target user currently has no need to access the target service, the NSSAI of the target network slice is not used as the allowed NSSAI of the target user, so as to ensure that the access to the target network slice meets the SLA of the target network slice.

[0137] For details of the method for allowing NSSAI determination to be implemented by the network device 7, please refer to the introduction of the aforementioned embodiment, which will not be repeated here.

[0138] This embodiment also provides a system that allows NSSAI to determine the system. Figure 8 The NSSAI determination system 8 includes an NWDAF 81 and a slice determination network element 82, wherein the NWDAF 81 can be Figure 7The processor 71 executes the first NSSAI determination program to implement the network device that allows the NSSAI determination method. The slice determination network element 82 can be Figure 7 The processor 71 executes the second NSSAI determination program to implement a network device that allows the NSSAI determination method, and the slice determination network element 82 can be NSSF or AMF.

[0139] The storage medium and network device provided in this embodiment obtain the historical service access data of the target user to the target service through NWDAF, and analyze and process the historical service access data to obtain the access time analysis result of the target user to the target service. Then, the access time analysis result of the target user to the target service is sent to the slice determination network element, so that the slice determination network element determines the allowed NSSAI (i.e., allowed NSSAI) for the target user according to the access time analysis result and the SLA of the target network slice after receiving the access time analysis result sent by NWDAF. Based on the access time analysis result provided by NWDAF, the slice determination network element can determine the target user's access time habits to the target service, thereby predicting when the target user may need to access the target service and when he may not need to access the target service, and then determine whether to use the NSSAI of the target network slice as the Allowed NSSAI of the target user according to the prediction result. While ensuring the user's service access needs, it can also take into account the satisfaction of the SLA of the target network slice, which is conducive to optimizing the service access experience of the network slice user.

[0140] It can be seen that those skilled in the art should understand that all or some of the steps, systems, and functional modules / units in the above disclosed methods can be implemented as software (which can be implemented with computer program code executable by a computing device), firmware, hardware, and appropriate combinations thereof. In hardware implementations, the division between the functional modules / units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component can have multiple functions, or a function or step can be performed by several physical components in cooperation. Some or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or implemented as hardware, or implemented as an integrated circuit, such as an application-specific integrated circuit.

[0141] In addition, it is well known to those skilled in the art that communication media generally contain computer readable instructions, data structures, computer program modules or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery media. Therefore, the present invention is not limited to any specific hardware and software combination.

[0142] The above contents are further detailed descriptions of the embodiments of the present invention in combination with specific implementation methods, and it cannot be determined that the specific implementation of the present invention is limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as falling within the protection scope of the present invention.

Claims

1. A method for determining network slice selection auxiliary information NSSAI, comprising: Obtain historical service access data of a target user accessing a target service, where the target service is a service on a target network slice; Determine an access time analysis result of the target user's access to the target service according to the target user's historical service access data, wherein the access time analysis result includes at least one of a time classification identifier of the target user's access to the target service, an actual time when the target user's category accesses the target service, and a predicted time when the target user's category accesses the target service; The access time analysis result of the target user to the target service is sent to the slice determination network element, and the access time analysis result is used by the slice determination network element to determine the allowed NSSAI for the target user in combination with the service level agreement SLA of the target network slice.

2. The method for determining network slice selection auxiliary information NSSAI according to claim 1, characterized in that: The slice determination network element includes at least one of an access and mobility management function AMF and a network slice selection function NSSF.

3. The method for determining network slice selection auxiliary information NSSAI according to claim 1, characterized in that: The acquiring of historical service access data of the target user accessing the target service includes: Receiving historical service access data of the target user accessing the target service sent by at least one of AF, OAM and other core network elements, wherein the other core network elements are other core network elements except NWDAF; or, Acquire historical service access data of the target user accessing the target service from the data storage platform.

4. The method for determining network slice selection auxiliary information NSSAI according to any one of claims 1 to 3, characterized in that: Before acquiring the historical service access data of the target user accessing the target service, the method further includes: Receive a subscription request sent by the slice determination network element, where the subscription request includes identification information of a target user and subscription type information, where the subscription type information is used to characterize that the data type subscribed by the slice determination network element is an access time analysis result of a target service; A target user and a target service are determined according to the subscription request.

5. A method for allowing NSSAI determination, comprising: Receive an access time analysis result of a target user accessing a target service sent by a network data analysis function NWDAF, where the access time analysis result is obtained by the NWDAF analyzing and processing historical service access data of the target user accessing the target service, where the target service is a service on a target network slice, and the access time analysis result includes at least one of a time classification identifier for the target user to access the target service, an actual time for the target user's category to access the target service, and a predicted time for the target user's category to access the target service; Determine that NSSAI is allowed for the target user based on the access time analysis result and the SLA of the target network slice.

6. The method for determining allowed NSSAI according to claim 5, wherein: Before receiving the access time analysis result of the target user accessing the target service sent by the network data analysis function NWDAF, the method further includes: A subscription request including subscription type information and target user identification information is sent to the NWDAF, where the subscription type information is used to characterize that the analysis data subscribed to by the slice-determined network element is an access time analysis result.

7. The method for determining allowed NSSAI according to claim 5 or 6, characterized in that: The determining, according to the access time analysis result and the SLA of the target network slice, to allow NSSAI for the target user comprises: If the access time analysis result indicates that the target user currently has a need to access the target service, the NSSAI of the target network slice is used as the allowed NSSAI of the target user; If the access time analysis result indicates that the target user currently has no need to access the target service, the NSSAI of the target network slice will not be used as the allowed NSSAI of the target user to ensure that the access to the target network slice meets the SLA of the target network slice.

8. A network device, comprising a processor, a memory and a communication bus; The communication bus is used to realize the connection and communication between the processor and the memory; The processor is used to execute one or more programs stored in the memory to implement the steps of the method for determining allowed network slice selection auxiliary information NSSAI as described in any one of claims 1 to 4; or, the processor is used to execute one or more programs stored in the memory to implement the steps of the method for determining allowed NSSAI as described in any one of claims 5 to 7.

9. A storage medium, characterized in that: The storage medium stores at least one of a first allowed NSSAI determination program and a second allowed NSSAI determination program, and the first allowed NSSAI determination program can be executed by one or more processors to implement the steps of the allowed network slice selection auxiliary information NSSAI determination method as described in any one of claims 1 to 4; the second allowed NSSAI determination program can be executed by one or more processors to implement the steps of the allowed NSSAI determination method as described in any one of claims 5 to 7.

Images