User management method and device for network slicing and core network

Abstract

The embodiment of the invention provides a user management method and device for a network slice and a core network, and belongs to the technical field of communication, and the method comprises the steps that the core network receives network slice selection auxiliary information sent by a user terminal, and extracts a service type requested by a user from the network slice selection auxiliary information; according to the extracted user request service type, screening out a base station with the capability of supporting the user request service type from all base stations; for the network slices supporting the user request service type in the screened base station, calculating the congestion degree of the network slices according to the resource capacity; and based on the calculated network slice congestion degree, selecting a subscriber data identifier matched with the candidate subscriber data identifiers from the candidate subscriber data identifiers. According to the method, the service type support condition and the network slice congestion degree of the base station can be comprehensively considered, the appropriate base station cell is accurately matched for the user, and the service experience and the communication quality of the user are effectively improved.

Description

Technical Field

[0001] The present application relates to the field of communication technologies, and in particular, to a user management method, apparatus, and core network for network slicing. Background Art

[0002] SPID (Subscriber Profile Identifier) is a subscriber profile identifier provided by the core network for the base station, which is used to determine the priority in cell selection in the RRC (Radio Resource Control) idle state and handover in the RRC connected state. For example, when SPID = 256, the 4G network is preferentially selected. The configuration of SPID depends on the user terminal capabilities and the operator's network deployment. With the development of network slicing technology, the network can virtualize multiple independent slices to provide different types of services, and users select suitable slices through NSSAI (Network Slice Selection Assistance Information).

[0003] The limitation of the current protocol in network access is that it can only configure one SPID value for each user, which is only used to determine the priority of accessing a certain type of network, and cannot perform more refined access selection according to the specific service type required by the user or the network resource allocation situation. With the introduction of network slicing technology, different cells may provide different service types or resource allocations, resulting in the problem that even if the user preferentially accesses a certain type of network according to SPID, they may not be able to obtain an ideal service experience or even face the problem of degraded communication quality due to the lack of support for the required services or insufficient resources in the accessed cell. Summary of the Invention

[0004] The present application provides a user management method, apparatus, and core network for network slicing, aiming to solve the problems that it is difficult for users to access and adapt to cells, affecting service experience and communication quality, caused by the determination of user access or handover priority by a single SPID configuration in the scenario where the operator supports network slicing.

[0005] In a first aspect, the present application provides a user management method for network slicing, which is applied to the network side. The network side includes a base station and a core network; for each base station, when performing a network slicing operation, the base station sends a notification message to the core network, and the notification message informs the core network of the service types it supports and the resource capacity used in the network slicing process;

[0006] The method includes:

[0007] The core network receives the network slice selection assistance information sent by the user terminal, and extracts the user-requested service type from the network slice selection assistance information;

[0008] According to the extracted user-requested service type, base stations capable of supporting the user-requested service type are screened out from all base stations; for the network slices that support the user-requested service type among the screened base stations, their congestion levels are calculated according to the resource capacity;

[0009] Based on the calculated congestion levels of the network slices, a subscriber profile identifier that matches it is selected from multiple candidate subscriber profile identifiers. This subscriber profile identifier is used to guide the user to access a base station cell that can meet the requirements of the user's required service type and has a relatively low network congestion level.

[0010] In a second aspect, the present application also provides a user management device for network slices, which is applied to the network side. The network side includes base stations and a core network; for each base station, when performing network slice operations, the base station sends a notification message to the core network, and this notification message informs the core network of the service types it supports and the resource capacity used during the network slice process;

[0011] The device includes:

[0012] An extraction module, which is used for the core network to receive the network slice selection assistance information sent by the user terminal, and extract the user-requested service type from the network slice selection assistance information;

[0013] A calculation module, which is used to screen out base stations capable of supporting the user-requested service type from all base stations according to the extracted user-requested service type; for the network slices that support the user-requested service type among the screened base stations, calculate their congestion levels according to the resource capacity;

[0014] A selection module, which is used to select a subscriber profile identifier that matches it from multiple candidate subscriber profile identifiers based on the calculated congestion levels of the network slices. This subscriber profile identifier is used to guide the user to access a base station cell that can meet the requirements of the user's required service type and has a relatively low network congestion level.

[0015] In a third aspect, the present application also provides a core network, and the core network is used to execute the steps of the user management method for network slices as described in any one of the first aspects.

[0016] A user management method, device, and core network for network slicing provided by an embodiment of the present application. In the scenario where an operator supports network slicing, to solve the problem that it is difficult for a user to access an adapted cell due to determining the user access or handover priority by a single SPID configuration, which affects the service experience and communication quality, this method is applied to the network side including a base station and a core network. When performing network slicing operations, the base station sends a notification message to the core network, informing the supported service types and resource capacities. The core network receives the network slice selection assistance information of the user terminal and extracts the user-requested service type, filters out the base stations that can support this service type, then calculates the network slice congestion degree based on the resource capacities, and finally selects an appropriate subscriber profile identifier based on the congestion degree to guide the user to access a base station cell that can meet the service type requirements and has a lower network congestion degree. Its advantage lies in being able to comprehensively consider the service type support situation of the base station and the network slice congestion degree, accurately match an appropriate base station cell for the user, effectively improve the user's service experience and communication quality, and avoid unreasonable access problems caused by a single configuration. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] To more clearly illustrate the technical solutions in the embodiments of the present application or in the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0018] Figure 1 is a flowchart of the user management method for network slicing;

[0019] Figure 2 is a structural block diagram of the user management device for network slicing. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0020] In the embodiments of the present application, the term "and / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after. In the embodiments of the present application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0021] The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0022] In the existing wireless cellular network technology architecture, the core network has the function of providing the Subscriber Profile Identity (SPID) for the base station. The SPID plays a crucial role in the wireless communication process, mainly reflected in the following two aspects:

[0023] One use of the SPID: Cell selection and access in the RRC idle state.

[0024] When the user is in the Radio Resource Control (RRC) idle state, the user equipment needs to perform cell selection operations, that is, select a suitable cell from multiple available cells for residence. After completing cell selection, the user equipment will initiate a random access on the selected cell to establish a connection with the base station, so as to prepare for subsequent communication operations such as data transmission. In this process, the SPID plays a decisive role, and it can determine the priority of the user equipment to select a cell.

[0025] Another use of the SPID: Handover and radio access technology selection in the RRC connected state.

[0026] When the user is in the RRC connected state, that is, when a dedicated connection has been established between the user equipment and the base station and data transmission or other communication operations are being carried out, a handover operation may be required due to the movement of the user or the change of the network condition. During the handover process, the user equipment can select different Radio Access Technologies (RATs) according to the actual situation.

[0027] To illustrate the specific action mechanism of the SPID more clearly, take the 3GPP TS36.300 protocol as an example. This protocol stipulates that when the SPID value is 256, the user should preferentially select the carrier of E-UTRAN. Specifically, after the core network configures the subscriber profile identity with SPID = 256 for the base station, the base station will correspondingly configure the same SPID value for the user. In this configuration, when the user is in the RRC idle state, the user should preferentially select a 4G cell to initiate a random access; when the user is in the RRC connected state and a handover operation is required, the user should also preferentially select a 4G cell for handover.

[0028] The specific configuration of SPID is not arbitrary but is comprehensively influenced by various factors. On the one hand, it depends on the network mode supported by the user terminal and the type of communication service required by the user. For example, when the user terminal supports 4G communication, during the process of accessing the network, the user terminal will notify the network side of its own capability information. Based on this, the network side will configure SPID = 256 for this user so that the user can preferentially select the 4G network to initiate access or perform handover during subsequent access or handover operations. On the other hand, the configuration of SPID is also closely related to the network deployment of the operator. For example, if the network side only supports 3G network in a specific area, then when configuring SPID, only the SPID value corresponding to 3G network priority can be selected. It should be noted that according to the current protocol regulations, only one SPID value can be configured for a user at a specific moment.

[0029] With the continuous development of communication technology, in order to meet the needs of carrying out multiple vertical industries in the same network, an advanced network technology, namely network slicing technology, has emerged. Network slicing technology can logically divide the network, enabling a physical network to virtualize multiple independent logical networks, namely network slices. Strict isolation of services and resources is achieved among these network slices. Each network slice can provide a unique type of service, and all network slices use orthogonal resources, thus ensuring that there is no interference among the network slices.

[0030] Whether it is the same operator or different operators, the areas managed by different base stations under them will provide different network slices, that is, there are differences in the types of network services provided. For example, within the area managed by a certain base station 1, the service types provided include Service A, Service B, and Service C; while within the area managed by another base station 2, the service types provided are only Service A and Service B. The service types mentioned here cover various types such as enhanced mobile broadband communication (eMBB), ultra-reliable low-latency communication (URLLC), enhanced machine type communication (eMTC), and vehicle-to-everything communication (V2X).

[0031] In addition, even if different base stations provide the same type of service, the resource capacities used by the corresponding network slices are different. For example, when both base station 1 and base station 2 support Service Type A and Service Type B, the network bandwidths of the network slices of Service Type A and B in the two base stations may not be the same. This means that for a specific service type, the maximum number of users that can be accessed by base station 1 and base station 2 at the same time is different.

[0032] When a user initiates a service request, network slice selection assistance information (NSSAI) will be provided to the network side. After receiving this assistance information, the network side can determine the service type requested by the user (i.e., the user-requested service type) based on it, and select a corresponding access and mobility management function (AMF) that can provide the requested service for the user, so as to ensure that the user can obtain network services that meet their needs.

[0033] The current protocol can only configure one SPID value for the user at a specific moment. The role of the SPID value is to determine the priority of the user to access a certain network mode (such as 4G, 5G, etc.). For example, it determines which network cell of which mode the user will preferentially select to access among the cells of multiple different network modes.

[0034] With the development of network slice technology, even for different cells that support the same network mode (such as both being 5G), the service types provided may be different. For example, the area managed by 5G base station 1 provides services A, B, and C, while the area managed by 5G base station 2 only provides services A and B. Even if the service types provided by different cells are the same, the network resources occupied by each service may also be different. For example, the network slice of service A in base station 1 occupies 80% of the network resources, while the network slice of service A in base station 2 only occupies 20% of the network resources.

[0035] When a user requests a specific service (such as service C), and the network side instructs the user to preferentially access a 5G cell according to the SPID, if the user accesses a cell that does not provide this service (such as base station 2), they will not be able to obtain the required service. When a user requests a certain service (such as service A) and accesses a 5G cell according to the SPID instruction, if the network slice resources of this service in the accessed cell (such as base station 2) are less, it may enter a more congested network for the service, resulting in a decline in communication quality.

[0036] Therefore, in the case where the operator supports network slices, only configuring one SPID for the user to determine the priority of access or handover will cause the user to be unable to access a more suitable cell, affecting the user's service experience and communication quality.

[0037] To solve the problem that when an operator supports network slicing, only a single SPID configuration is used to determine the priority of user access or handover, making it difficult for users to access a cell that provides the required services and has better resources, thus affecting the user service experience and communication quality, this application provides a user management method, device, and core network for network slicing. This method solves the above problem through a user management method applied to the network side including a base station and a core network. Specifically: when the base station performs network slicing operations, it sends a notification message containing its supported service types and resource capacity to the core network. After receiving the network slice selection assistance information from the user terminal, the core network extracts the service type requested by the user, filters out the base stations that can support this service type, calculates the congestion degree of the corresponding network slice according to the resource capacity, and then selects an appropriate subscriber profile identifier to guide the user to access a base station cell that meets the service type requirements and has a lower congestion degree. The advantage of this method is that it can comprehensively consider the base station service types and network slice congestion conditions, accurately match the base station cell suitable for the user, thereby significantly improving the user service experience and communication quality, and overcoming the access irrationality drawbacks brought by a single SPID configuration.

[0038] Please refer to Figure 1 , Figure 1 is a flowchart of a user management method for network slicing. A user management method for network slicing includes:

[0039] S111, the base station sends a notification message to the core network.

[0040] When the base station performs network slicing operations, it sends a notification message to the core network. This notification message informs the core network of the various service types it supports, such as voice call service, high-speed data transmission service, low-latency and high-reliability service, etc., and at the same time informs the resource capacity used during network slicing, including but not limited to bandwidth resources, computing resources, etc.

[0041] S112, the core network receives the network slice selection assistance information sent by the user terminal.

[0042] The core network listens for and receives the network slice selection assistance information sent by the user terminal in real time. This network slice selection information contains, for example, the specific requirements and preferences of the user for network services and other related content.

[0043] S113, the core network performs service type matching, congestion degree calculation, and SPID selection.

[0044] ① Extract the service type requested by the user: The core network analyzes the received network slice selection assistance information and extracts the service type requested by the user from it.

[0045] ② Screen base stations that support the service type: Based on the extracted user-requested service type, the core network screens all base stations to find the base stations with the ability to support the user-requested service type.

[0046] ③ Calculate the congestion degree of the network slice: For the network slices that support the user-requested service type among the screened base stations, the core network calculates according to the resource capacity reported by the base stations and the preset congestion degree calculation rules. For example, the congestion degree can be determined according to the ratio between the number of preferentially accessed users that have already been supported and the resource capacity of the network slice of the base station that supports the user-requested service type; or according to the ratio between the maximum value of the number of preferentially accessed users that have already been supported and the number of users that have already accessed and the resource capacity of the network slice of the base station that supports the user-requested service type; where the number of preferentially accessed users that have already been supported refers to the number of users whose assigned subscriber profile identifier (SPID) is the same as the subscriber profile identifier assigned by the core network to the virtual network corresponding to each network slice of the base station.

[0047] ④ Select an appropriate subscriber profile identifier: Based on the calculated congestion degree of the network slice, the core network selects an appropriate subscriber profile identifier (SPID) from multiple candidate subscriber profile identifiers. Among them, the subscriber profile identifier is an identifier used to identify the specific configuration information of the user in the network, and it is associated with resource allocation, quality of service, etc. of the network slice. The selection principle is to guide the user to access the base station cell that can not only meet the requirements of the user's required service type but also has a relatively low network congestion degree. For example, preferentially select the SPID corresponding to the base station whose congestion degree is lower than the preset threshold and can provide all the service types required by the user; if there is no such base station, then select the SPID corresponding to the base station that can provide the most service types required by the user and has a relatively low congestion degree.

[0048] S114, the core network sends the SPID.

[0049] The core network sends the selected subscriber profile identifier to the corresponding base station and the end user respectively. Sending the SPID to the base station so that the base station can provide corresponding services for the user according to this identifier during the subsequent access control and resource allocation processes; sending the SPID to the end user so that the end user can carry the correct identifier information when initiating an access or handover operation, so that the network side can accurately identify and process it.

[0050] S115, the end user initiates an access or handover operation.

[0051] When the end - user needs to access the network, they initiate a random access request based on the received subscriber profile identifier; or when the current connected network environment fails to meet the requirements, such as when the signal strength weakens, network congestion occurs, service quality deteriorates, etc., a handover operation is performed to access a more suitable base station cell corresponding to the selected subscriber profile identifier, thereby ensuring that the user can obtain a high - quality network service that meets their own needs.

[0052] In some embodiments, the method further includes handling in abnormal situations, specifically including:

[0053] ① Situation of no matching base station: If no base station with the ability to support the user - requested service type is screened out in step S113, the core network will send a prompt message to the user terminal, informing the user that the current network cannot provide the required service, and guiding the user to adjust the service request or wait for network resource updates.

[0054] ② High - congestion situation: If the congestion level of the network slices of all base stations is higher than a preset acceptable threshold, the core network will adopt congestion control strategies, such as restricting new user access, performing load - balancing adjustments on existing users, etc., and at the same time send a network congestion prompt message to the user terminal, informing the user that they may need to wait for some time to obtain better service.

[0055] In some embodiments, the method further includes:

[0056] S121, the network side collects data according to a specific policy. The policy includes collecting data during a specific period, collecting data for a specific geographical area, or collecting data at periodic time intervals. The data collected includes the resource congestion level and resource utilization rate of the network slice.

[0057] Specifically, the network side will collect relevant data according to a pre - set specific policy. These policies are diverse. It can choose to collect data during a specific time period, such as during the peak or off - peak network usage period; it can also collect data for a specific geographical area, such as for some business - intensive areas or areas with weak network coverage; it can also collect data at periodic time intervals, such as collecting comprehensive data at regular intervals. The data collected mainly focuses on two indicators: the resource congestion level and resource utilization rate of the network slice. By collecting data in a targeted manner, the network side can accurately and real - time grasp the resource usage status of the network slice, providing a detailed data basis for subsequent analysis and decision - making, so as to timely discover potential network problems and optimize the allocation and management of network resources.

[0058] S122. After obtaining the resource congestion level or resource utilization rate of the network slice, the network side compares and analyzes the obtained data with a pre-set threshold, and determines whether it is necessary to recalculate the resource capacity of the network slice according to the comparison result.

[0059] Specifically, after the network side successfully obtains data such as the resource congestion level and resource utilization rate of the network slice, it will compare and analyze these actual data with the pre-set threshold. The threshold can be determined comprehensively based on various factors such as the network performance requirements, service quality standards, and past operation experience. Through the comparison, the network side can understand whether the current resource usage of the network slice exceeds or is lower than the expected range, and then determine whether it is necessary to recalculate the resource capacity of the network slice according to the comparison result. This step is a key link in network resource management. By comparing and analyzing with the threshold, abnormal situations of network slice resources can be detected in a timely manner, such as problems of excessive resource congestion or resource idle waste. Deciding whether to recalculate the resource capacity according to the judgment result helps to ensure the reasonable allocation and efficient utilization of network resources, and guarantees the quality and stability of network services.

[0060] S123. After completing the calculation of the new resource capacity of the network slice, the network side determines whether it is necessary to reconfigure the subscriber profile identifier for the user.

[0061] Specifically, after completing the calculation of the new resource capacity of the network slice, the network side needs to further evaluate whether the current subscriber profile identifier of the user is still suitable for the new resource capacity and network conditions. The subscriber profile identifier is closely related to the service configuration and resource allocation of the user in the network. Therefore, it is necessary to judge whether it is necessary to adjust the subscriber profile identifier of the user according to the new resource capacity situation. This step is to ensure that the user can still obtain services that match their own needs and network conditions when the network slice resources change. By judging whether it is necessary to reconfigure the subscriber profile identifier, the decline in user service quality caused by resource capacity changes can be avoided, and the user's network experience can be guaranteed.

[0062] S124. If it is determined through judgment that it is necessary to reconfigure the subscriber profile identifier for the user, the network side performs the operation of reconfiguring the subscriber profile identifier for the user.

[0063] Specifically, when the network side determines that it is necessary to reconfigure the subscriber profile identifier for a user, the corresponding operation process will be initiated to reconfigure the subscriber profile identifier of the user. This process involves updating and adjusting the relevant configuration information of the user in the network to make it match the new network slice resource capacity and service requirements. By performing the reconfiguration operation of the subscriber profile identifier, it can ensure that after the network slice resources change, the user can smoothly access the appropriate network resources and obtain the service quality that meets their own needs, thereby optimizing the user's network usage experience and maintaining the efficient and stable operation of the network.

[0064] The following specifically describes the present application through embodiments.

[0065] Embodiment 1:

[0066] First, the core network needs to confirm the relevant information of the network slice. During the implementation of the network slice, for each base station, when performing network slice operations, the base station needs to send a notification to the core network, informing the service types it supports and the specific resource capacity used during the network slice process. After receiving the above information from each base station, the core network will record this information in the network slice management unit inside the core network. The specific recorded content is shown in the following table:

[0067]

[0068] If a certain base station does not have the support ability for a specific service type, there is no need to report it to the core network. In this case, the core network can adopt two processing methods for this service type: First, do not record this service type in the relevant table; Second, regard the network slice configuration resource capacity corresponding to this service type as 0.

[0069] Subsequently, the user sends Network Slice Selection Assistance Information (NSSAI) to the core network. After receiving this information, the core network can clarify the service type requested by the user. It should be noted that in the NSSAI, there may be multiple Single-Network Slice Selection Assistance Information (S-NSSAI). When there are multiple S-NSSAIs, it means that after the user successfully accesses the network, they may conduct communication activities of multiple service types.

[0070] Subsequently, the core network selects the Subscriber Profile Identifier (SPID) according to the received Network Slice Selection Assistance Information (NSSAI). The selection of the SPID needs to meet the following conditions:

[0071] Condition 1: Determine the service types supported by each base station, that is, clarify the specific service types that each base station deployed in the network can support, so as to perform matching and screening subsequently.

[0072] Condition 2: Determine the resource capacity of the network slice, that is, for the network slice corresponding to each service type, determine its resource capacity. This resource capacity is an important indicator to measure the bearing capacity of the network slice.

[0073] When performing SPID selection, the specific operation process is as follows:

[0074] First, according to the service type requested by the user through NSSAI, screen out the base stations that can support the requested service type from all base stations.

[0075] Secondly, calculate the congestion degree of the network slice that supports the user-requested service type among the screened base stations. Specifically, it is determined according to the ratio between the number of preferential access users that have been supported and the resource capacity of the network slice of the base station that supports the user-requested service type. Among them, the number of preferential access users that have been supported refers to the number of users whose assigned SPID is the same as the SPID assigned to the virtual network corresponding to each network slice of the base station by the core network. The calculation formula for the congestion degree is: Congestion degree = (Number of preferential access users that have been supported / Resource capacity of the network slice of the service type) × 100%.

[0076] Finally, select the SPID based on the calculated congestion degree of the network slice, so as to determine the priority of the user to initiate random access or perform handover. Specifically, for the network slices with a congestion degree lower than the set congestion threshold, select the SPID of the base station to which the network slice with the lowest congestion degree belongs as the final selection result. It should be noted that the set congestion thresholds corresponding to different network slices can be set differently according to the actual situation.

[0077] For example, assume that there are three base stations on the access network side in this embodiment. The following are the relevant information of each base station:

[0078] Base station 1: Base station 1 provides three network slices. The service types supported by each network slice are service A, service B, and service C respectively. The resource capacity occupation ratios of each network slice are a1%, b1%, and c1% in turn. The subscriber profile identifier used by this base station is SPID1. Among the virtual networks corresponding to these three network slices respectively, the numbers of users assigned SPID1 are L1, M1, and N1.

[0079] Base Station 2: Base Station 2 also provides three network slices, and the supported service types are Service A, Service B, and Service C respectively. The resource capacity ratios used by each network slice are a2%, b2%, and c2% respectively, and the subscriber profile identifier corresponding to this base station is SPID2. In the virtual networks corresponding to these three network slices, the number of users assigned SPID2 is L2, M2, and N2 respectively.

[0080] Base Station 3: Base Station 3 provides two network slices, and the supported service types are Service A and Service B respectively. The resource capacity ratios used by each network slice are a3% and b3% respectively, and the subscriber profile identifier corresponding to this base station is SPID3. In the virtual networks corresponding to these two network slices, the number of users assigned SPID3 is L3 and M3 respectively.

[0081] In addition, congestion thresholds Y A , Y B and Y C are respectively set for Service A, Service B, and Service C.

[0082] When the core network receives the network slice selection assistance information (NSSAI) sent by a certain user, and this information indicates that the user requests a service of Service Type C, since Base Station 3 cannot provide a service of Service Type C, it cannot configure SPID3 for this user.

[0083] For Base Station 1, the calculation method of the network congestion level Y1 of the network slice providing Service Type C is: Y1 = N1 / c1. For Base Station 2, the calculation method of the network congestion level Y2 of the network slice providing Service Type C is: Y2 = N2 / c2.

[0084] By comparing the magnitudes of Y1 and Y2, select the subscriber profile identifier corresponding to the network slice with a lower congestion level. For example, when Y2 < Y1 < Y C , it indicates that the network slice providing Service Type C in Base Station 1 is relatively more congested. In this case, the core network will control the user to preferentially access the network slice providing Service Type C in Base Station 2, that is, configure SPID2 of Base Station 2 for the user.

[0085] Embodiment 2:

[0086] When performing subscriber profile identifier (SPID) selection, it includes the following steps:

[0087] Step 1: Screen the base stations that support the service type.

[0088] According to the service type requested by the user through the network slice selection assistance information (NSSAI), screen out the base stations that can support the requested service type from multiple base stations on the access network side.

[0089] Step 2: Calculate the congestion level of the network slice.

[0090] For the network slices that support the service type requested by the user among the selected base stations, the calculation method is to calculate the congestion level according to the ratio between the number of already connected users and the resource capacity of its network slice. The specific calculation formula is: Congestion level = (Number of already connected users / Resource capacity of the network slice) × 100%.

[0091] Step 3: Select the SPID based on the congestion level.

[0092] According to the calculated congestion level, determine the priority for the user to initiate random access or perform handover, and then select an appropriate SPID. For network slices with a congestion level exceeding the set threshold, select the SPID of the base station to which the network slice with the lowest congestion level belongs among these network slices. It should be noted that the set thresholds corresponding to different network slices can be set differently according to the actual situation.

[0093] For example, assume that there are three base stations on the access network side in this embodiment, and the specific situations of each base station are as follows:

[0094] Base station 1:

[0095] Network slices and service types: Provide three network slices, supporting service A, service B, and service C respectively.

[0096] Resource capacity: The resource capacity ratios used by each network slice are a1%, b1%, and c1% in sequence.

[0097] SPID and number of already connected users: The SPID used by this base station is SPID1. In the virtual networks corresponding to these three network slices, the number of already connected users assigned SPID1 is l1, m1, and n1 respectively.

[0098] Base station 2:

[0099] Network slices and service types: Also provide three network slices, and the supported service types are also service A, service B, and service C.

[0100] Resource capacity: The resource capacity ratios used by each network slice are a2%, b2%, and c2% respectively.

[0101] SPID and number of already connected users: The SPID used by this base station is SPID2. In the virtual networks corresponding to these three network slices, the number of already connected users assigned SPID2 is l2, m2, and n2 respectively.

[0102] Base station 3:

[0103] Network Slices and Service Types: Two network slices are provided, and the supported service types are Service A and Service B.

[0104] Resource Capacity: The resource capacity ratios used by each network slice are a3% and b3% respectively.

[0105] SPID and Number of Connected Users: The SPID used by this base station is SPID3. In the virtual networks corresponding to these two network slices, the number of connected users assigned SPID3 is l3 and m3 respectively.

[0106] In addition, congestion thresholds Y A , Y B and Y C are respectively set for Service A, Service B, and Service C.

[0107] When the core network receives the NSSAI sent by a certain user, and this information indicates that the user requests a service of Service Type C, since Base Station 3 cannot provide the service of Service Type C, it cannot configure SPID3 for this user.

[0108] For Base Station 1, the calculation method of the network congestion level Y1 of the network slice providing Service Type C is: Y1 = n1 / c1. For Base Station 2, the calculation method of the network congestion level Y2 of the network slice providing Service Type C is: Y2 = n2 / c2.

[0109] By comparing the magnitudes of Y1 and Y2, the SPID corresponding to the network slice with a lower congestion level is selected. For example, when Y2 < Y1 < Y C , it indicates that the network slice providing Service Type C in Base Station 1 is relatively more congested. In this case, the core network will control the user to preferentially access the network slice providing Service Type C in Base Station 2, that is, configure SPID2 of Base Station 2 for the user.

[0110] In some embodiments, the method further includes:

[0111] The core network will confirm the network slice information to determine whether the SPID needs to be updated. If the SPID needs to be updated, the updated SPID will be configured for the user.

[0112] It should be noted that the main difference between Embodiment 2 and Embodiment 1 lies in the different numbers of connected users in the base station network slices. In Embodiment 1, the numbers of connected users are L1, M1, N1 (corresponding to Base Station 1), L2, M2, N2 (corresponding to Base Station 2), and L3, M3 (corresponding to Base Station 3); while in Embodiment 2, the numbers of connected users are l1, m1, n1 (corresponding to Base Station 1), l2, m2, n2 (corresponding to Base Station 2), and l3, m3 (corresponding to Base Station 3).

[0113] Embodiment 3:

[0114] When selecting a Subscriber Profile Identifier (SPID), the following steps are included:

[0115] Step 1: Screen the base stations that support the service type.

[0116] According to the service type requested by the user through the Network Slice Selection Assistance Information (NSSAI), select the base stations that can support the requested service type from multiple base stations on the access network side.

[0117] Step 2: Calculate the congestion degree of the network slice.

[0118] For the network slice that supports the user-requested service type among the screened base stations, calculate the congestion degree of this network slice according to the ratio between the maximum value of the number of preferentially accessed users that have been supported and the number of users that have already accessed and the resource capacity of the network slice of the base station that supports the user-requested service type. Among them, the number of preferentially accessed users that have been supported refers to the number of users whose assigned SPID is the same as the SPID assigned by the core network to the virtual network corresponding to each network slice of the base station. The specific calculation formula for the congestion degree is: Congestion degree = [max(number of preferentially accessed users that have been supported, number of users that have already accessed) / resource capacity of the network slice of the service type] × 100%. Among them, max(number of preferentially accessed users that have been supported, number of users that have already accessed) represents taking the maximum value of the two values of the number of preferentially accessed users that have been supported and the number of users that have already accessed.

[0119] Step 3: Select the SPID based on the congestion degree.

[0120] According to the calculated congestion degree, determine the priority for the user to initiate random access or perform a handover, and then select a suitable SPID. For the network slices with a congestion degree exceeding the set threshold, select the SPID of the base station to which the network slice with the lowest congestion degree belongs among these network slices. It should be noted that the set thresholds corresponding to different network slices can be set differently according to the actual situation.

[0121] For example, assume that there are three base stations in total on the access network side in this embodiment. The following are the relevant information of each base station:

[0122] Base Station 1:

[0123] Network slices and service types: Provide three network slices, respectively supporting Service A, Service B, and Service C.

[0124] Resource capacity: The resource capacity usage ratios of each network slice are a1%, b1%, and c1% in sequence.

[0125] SPID and related number of users: The SPID used by this base station is SPID1. In the virtual networks corresponding to these three network slices, the numbers of users assigned SPID1 are L1, M1, and N1 respectively, and the numbers of connected users assigned SPID1 are l1, m1, and n1 respectively.

[0126] Base station 2:

[0127] Network slices and service types: Similarly, three network slices are provided, and the supported service types are Service A, Service B, and Service C.

[0128] Resource capacity: The proportions of resource capacity used by each network slice are a2%, b2%, and c2% respectively.

[0129] SPID and related number of users: The SPID used by this base station is SPID2. In the virtual networks corresponding to these three network slices, the numbers of users assigned SPID2 are L2, M2, and N2 respectively, and the numbers of connected users assigned SPID2 are l2, m2, and n2 respectively.

[0130] Base station 3:

[0131] Network slices and service types: Two network slices are provided, and the supported service types are Service A and Service B.

[0132] Resource capacity: The proportions of resource capacity used by each network slice are a3% and b3% respectively.

[0133] SPID and related number of users: The SPID used by this base station is SPID3. In the virtual networks corresponding to these two network slices, the numbers of users assigned SPID3 are L3 and M3 respectively, and the numbers of connected users assigned SPID3 are l3 and m3 respectively.

[0134] In addition, congestion thresholds Y A 、Y B and Y C .

[0135] When the core network receives the NSSAI sent by a certain user, and this information indicates that the user requests a service of service type C, since base station 3 cannot provide a service of service type C, it cannot configure SPID3 for this user.

[0136] For base station 1, the calculation method of the network congestion level Y1 of the network slice providing service type C is: Y1 = [max(N1, n1) / c1] × 100%. For base station 2, the calculation method of the network congestion level Y2 of the network slice providing service type C is: Y2 = [max(N2, n2) / c2] × 100%.

[0137] By comparing the magnitudes of Y1 and Y2, select the SPID corresponding to the network slice with a lower congestion level. For example, when Y2 < Y1 < Y C it indicates that the network slice providing service type C in base station 1 is relatively more congested. In this case, the core network will control the user to preferentially access the network slice providing service type C in base station 2, that is, configure the SPID2 of base station 2 for the user.

[0138] It should be noted that the main differences between Embodiment 3 and Embodiments 1 and 2 are as follows: Embodiment 3 introduces two different variables, namely the number of users (L1, M1, N1, etc.) to whom the SPID is allocated and the number of already connected users (l1, m1, n1, etc.), and when calculating the congestion level of the network slice, the maximum value of these two variables is used to represent the congestion level, that is, Y1 = max(N1, n1) / c1 and Y2 = max(N2, n2) / c2. While in Embodiments 1 and 2, only the number of already connected users is used to calculate the congestion level. Therefore, Embodiment 3 more comprehensively evaluates the congestion situation of the network slice by comprehensively considering the number of allocated users and the number of already connected users.

[0139] In Embodiments 1 to 3 described above, the main consideration is the case where the user requests only one single service type. In this scenario, the base station to which the user connects must have a network slice that supports the service type requested by the user. And Embodiment 4 considers the case of multiple service types.

[0140] Embodiment 4:

[0141] When the user requests two or more service types, when the core network selects and configures the SPID, it includes the following steps:

[0142] Step 1: Determine the service types supported by each base station.

[0143] Identify the two or more service types that each base station deployed on the access network side can support. This step requires sorting out and confirming the service capabilities of all base stations for subsequent matching according to the user's request.

[0144] Step 2: Determine the resource capacity of the network slices for each service type.

[0145] For each service type supported by each base station, determine the resource capacity of the network slice that supports each service type. This is an important basis for evaluating the congestion level of the network slice and whether it can meet the user's service requirements.

[0146] Step 3: Calculate the congestion level of the network slice.

[0147] According to the service type requested by the user, for each network slice in each base station that supports the corresponding service type, the congestion degree of the network slice can be determined by calculating the ratio between the number of preferentially accessed users that have already been supported and the resource capacity of the network slice in the base station that supports the service type requested by the user.

[0148] Among them, the number of preferentially accessed users that have already been supported refers to the number of users whose assigned SPID is the same as the SPID assigned by the core network to the virtual network corresponding to each network slice of the base station. The specific calculation formula for the congestion degree is: Congestion degree = (Number of preferentially accessed users that have already been supported / Resource capacity of the network slice of the service type) × 100%.

[0149] Step Four: Determine the number of service types that the network can provide.

[0150] Based on the congestion degree of each network slice, judge and determine the number of network slices that can provide corresponding services for the user. This number actually reflects the number of service types that the network can provide for the user. This step further quantifies the actual service capacity of the network to match the service requirements of the user.

[0151] Step Five: Determine the final access network and configure the SPID.

[0152] Based on the ratio between the number of service types that the network can provide for the user and the number of service types requested by the user, comprehensively evaluate and determine the network for the final user to access. After determining the appropriate access network, the core network configures the corresponding SPID for the user, thereby completing the relevant configuration of user access.

[0153] For example, assume that there are three base stations on the access network side in this embodiment. The following are the relevant information of each base station:

[0154] Base Station 1:

[0155] Network slices and service types: Provide three network slices, supporting Service A, Service B, and Service C respectively.

[0156] Resource capacity: The proportion of resource capacity used by each network slice is a1%, b1%, and c1% in sequence.

[0157] SPID and related number of users: The SPID used by Base Station 1 is SPID1. Among the virtual networks corresponding to these three network slices, the number of users assigned SPID1 is L1, M1, and N1 respectively.

[0158] Base Station 2:

[0159] Network slices and service types: Also provide three network slices, and the supported service types are Service A, Service B, and Service C.

[0160] Resource capacity: The resource capacity ratios used by each network slice are a2%, b2%, and c2% respectively.

[0161] SPID and related number of users: The SPID used by Base Station 2 is SPID2. In the virtual networks corresponding to these three network slices, the numbers of users assigned SPID2 are L2, M2, and N2 respectively.

[0162] Base Station 3:

[0163] Network slices and service types: Two network slices are provided, and the supported service types are Service A and Service B.

[0164] Resource capacity: The resource capacity ratios used by each network slice are a3% and b3% respectively.

[0165] SPID and related number of users: The SPID used by Base Station 3 is SPID3. In the virtual networks corresponding to these two network slices, the numbers of users assigned SPID3 are L3 and M3 respectively.

[0166] In addition, congestion thresholds Y A 、Y B and Y C .

[0167] When the core network receives the NSSAI (Network Slice Selection Assistance Information) sent by a certain user, and this information indicates that the user requests services of Service Type A and Service Type C, it is necessary to calculate and analyze the congestion degree of the network slices of each base station as follows:

[0168] For Base Station 1, the network congestion degrees of the network slices providing Service Type A and Service Type C are calculated by the following formulas respectively: The network congestion degree of Service Type A, Y1a = L1 / a1; The network congestion degree of Service Type C, Y1c = N1 / c1.

[0169] For Base Station 2, the network congestion degrees of the network slices providing Service Type A and Service Type C are respectively: The network congestion degree of Service Type A, Y2a = L2 / a2; The network congestion degree of Service Type C, Y2c = N2 / c2.

[0170] For Base Station 3, since it only supports Service Type A and Service B, only the network congestion degree of the network slice of Service Type A is calculated, that is, Y3a = L3 / a3.

[0171] Next, according to the calculated congestion degree and the set thresholds, discuss the selection of the base station for user access in different cases:

[0172] Scenario 1 (Some base stations cannot provide effective services): If there are some base stations where the congestion levels of network slices for certain service types requested by users exceed the corresponding thresholds, resulting in these base stations being unable to provide effective services to users; among the remaining base stations, there is a base station that can provide some of the service types requested by users, and the congestion level of the network slice of the service type it can provide is relatively the lowest among other base stations that can provide services. In this case, the core network will control the user to preferentially access the network slice of the service type that can be provided in the base station with the relatively lowest congestion level, and configure the corresponding SPID of this base station for the user.

[0173] For example, if Y1c > Y2c > Y C , and Y3a < Y A < Y2a < Y1a. In this case, base station 3 can provide one of the service types requested by users (service type A), while base stations 1 and 2 cannot provide effective services to users because the congestion level of the network slice of service type C exceeds the threshold Y C . At this time, the ratios of the number of service types that base stations 1, 2, and 3 can provide to users to the number of service types requested by users are 0, 0, and 50% respectively. Based on this, the core network will control the user to preferentially access the network slice that provides service type A in base station 3, that is, configure the SPID3 of base station 3 for the user.

[0174] Scenario 2 (Each base station can provide some services): If the congestion levels of network slices for certain service types requested by users of all base stations exceed the corresponding thresholds, but each base station can provide some of the service types requested by users. At this time, compare the congestion levels of the network slices of the service types that each base station can provide. If there is a base station whose congestion level of the network slice of the service type it can provide is relatively the lowest among other base stations, the core network will control the user to preferentially access the network slice of the service type that can be provided in this base station, and configure the corresponding SPID of this base station for the user.

[0175] For example, if Y1c > Y2c > Y C , and Y3a < Y2a < Y1a < Y A . At this time, all three base stations can provide one of the service types requested by users (service type A), that is, the ratios of the number of service types that base stations 1, 2, and 3 can provide to users to the number of service types requested by users are all 50%. However, by comparing the congestion levels of the network slices of service type A of each base station, it can be seen that the congestion level of base station 3 is the lowest. Therefore, the core network will also control the user to preferentially access the network slice that provides service type A in base station 3, and configure the SPID3 of base station 3 for the user.

[0176] In this embodiment, although Base Station 1 and Base Station 2 support all the service types requested by the user in terms of service type support, due to the excessive congestion degree of the corresponding network slices, if the user accesses, there may be significant interference between users, which may lead to a decline in the user's communication quality. This indicates that even if a certain base station cannot provide all the services requested by the user, as long as the services it can provide can ensure the service quality, this base station can also be used as a candidate base station for the user to initiate random access or perform a handover.

[0177] It should be noted that the main differences between Embodiment 4 and Embodiments 1, 2, and 3 are as follows: the number of service types requested by the user and the base station selection logic are different. In Embodiment 4, the user requests two service types (such as Service Type A and Service Type C). When calculating the congestion degree of each base station's network slice, it is calculated separately for different service types that each base station can provide, and then according to different congestion degree comparison results (such as Case 1: Y1c > Y2c > Y C and Y3a < Ya < Y2a < Y1a, or Case 2: Y1c > Y2c > Y C and Y3a < Y2a < Y1a < Ya, etc.) to determine the ratio of the number of service types that each base station can provide for the user to the number of service types requested by the user, and accordingly select the base station with the lowest congestion degree and can provide partial services (such as Base Station 3) to guide the user to access, emphasizing that even if the base station cannot provide all services but can ensure service quality, it can also be used as an access candidate; while in Embodiments 1, 2, and 3, the user mainly requests one service type, and the selection logic is mainly to compare the congestion degree among the base stations that can provide this service type to determine the access base station.

[0178] In some embodiments, the method further includes:

[0179] In some embodiments, after the core network has configured the SPID of a certain base station for the user (such as the core network has configured SPID2 of Base Station 2 for the user), during the network operation, due to various situations, the network slice accessed by the user may need to be re-adjusted. These situations mainly involve changes in user service requests, changes in base station service types, and adjustments to base station network slice configurations, etc. The core network will re-select the network slice of the base station with the lowest congestion degree for the user to access according to the congestion degree of each base station's network slice for relevant service types, and accordingly re-configure the SPID for the user, specifically as follows:

[0180] Case 1: Network slice adjustment caused by changes in user service requests.

[0181] When the user re - requests a service type through the NSSAI, the congestion level of each base station for this service type may change. The core network will detect the congestion level of the network slices supported by each base station for this service type, select the base station with the lowest congestion level and lower than the set threshold, control the user to preferentially access the network slice corresponding to this service type in this base station, and re - configure the SPID of this base station for the user.

[0182] For example, if the user re - requests service type A through the NSSAI (Network Slice Selection Assistance Information), and at this time all three base stations support service type A. After detection, the congestion level relationship of the network slices supported by the three base stations for service type A is Y3 < Y2 < Y1 < Y C (where Y1, Y2, and Y3 respectively represent the congestion levels of the network slices supported by base station 1, base station 2, and base station 3 for service type A, and Y C is the congestion threshold set for service type A). This indicates that the network slice providing service type A in base station 3 has the lowest congestion level, that is, it is the most idle. Based on this, in order to optimize the user's service experience, the core network will control the user to preferentially access the network slice providing service type A in base station 3 and re - configure the SPID3 of base station 3 for the user accordingly.

[0183] Therefore, when the user re - requests a service type as described above, the advantage of such a setting is that it can dynamically adjust the base station and network slice accessed by the user according to the user's new service request and the real - time congestion status of the network slices of each base station. For example, when the user re - requests service type A, by comparing the congestion levels of the corresponding network slices of the three base stations, the user is preferentially guided to access the relevant network slice of base station 3 with the least congestion and re - configure the SPID, ensuring that the user obtains better service quality, avoiding the decline of service experience caused by accessing a congested network slice, and effectively improving the user's satisfaction with network services.

[0184] Case 2: Network slice adjustment due to the addition of a base station service type.

[0185] If a certain base station adds support for a specific service type, making multiple base stations able to support this service type, at this time the congestion levels of the network slices of each base station for this newly added service type may be different. The core network will compare the congestion levels of the network slices supported by each base station for this service type, select the base station with the lowest congestion level and lower than the set threshold, control the user to preferentially access the network slice corresponding to this service type in this base station, and re - configure the SPID of this base station for the user.

[0186] For example, in some cases, base station 3 will re - configure the network slices and add support for service type C, making all three base stations able to support service type C. At this time, if the congestion level relationship of the network slices supported by the three base stations for service type C is Y3 < Y2 < Y1 < YC (Here, Y1, Y2, and Y3 respectively represent the congestion levels of the network slices supporting service type C in base station 1, base station 2, and base station 3, and Y C is the congestion threshold set for service type C). This means that the network slice providing service type C in base station 3 has the lowest congestion level. Therefore, the core network will control the user to preferentially access the network slice providing service type C in base station 3 and reconfigure the SPID3 of base station 3 for the user.

[0187] Therefore, when adding support for a new service type to a base station as described above, the advantage of this setting is that it can make full use of the changes in base station resources in the network to optimize user access. After base station 3 reconfigures its network slice and supports service type C, by comparing the congestion levels of the network slices supporting this service type in the three base stations, the user is allowed to access the corresponding network slice of the least congested base station 3 and the SPID is reconfigured, enabling the user to promptly enjoy the new service type while ensuring the efficiency and stability of the service, improving the utilization efficiency of network resources and the user experience.

[0188] Scenario 3: Network slice adjustment due to deletion of a base station service type.

[0189] When a certain base station reconfigures its network slice and deletes support for a specific service type, to ensure that users can continue to obtain services of this service type, the core network will select a suitable base station (such as based on factors like congestion level) among the remaining base stations supporting this service type, control the user to preferentially access the network slice corresponding to this service type in that base station, and reconfigure the SPID of that base station for the user.

[0190] For example, there is a situation where after base station 2 reconfigures its network slice, it no longer supports service type C. In this case, to ensure that users can continue to obtain services of service type C, the core network will control the user to preferentially access the network slice providing service type C in base station 1 and reconfigure the SPID1 of base station 1 for the user.

[0191] Therefore, when a base station no longer supports a service type and reconfigures its network slice, the advantage of this reconfiguration is that when the base station network slice configuration changes and the original service cannot be provided, it can quickly find a suitable alternative access solution for users. For example, when base station 2 no longer supports service type C, controlling the user to access the network slice providing this service type in base station 1 and reconfiguring the SPID ensures the continuity of user services, reduces the impact on users caused by base station configuration changes, and enhances the reliability of network services.

[0192] Scenario 4: Network slice adjustment due to adjustment of base station network slice configuration.

[0193] If a base station reconfigures network slicing, resulting in a change in the congestion level relationship of network slices for a certain service type among base stations, the core network will select the base station with the lowest congestion level and lower than the set threshold according to the adjusted congestion level, control the user to preferentially access the network slice corresponding to the service type in this base station, and reconfigure the SPID of this base station for the user.

[0194] For example, if base station 1 reconfigures network slicing, making the congestion level relationship of the network slices supporting service type C in base station 1 and base station 2 change from Y2 < Y1 < Y C to Y1 < Y2 < Y C (Y1 and Y2 are the congestion levels of the network slices supporting service type C in base station 1 and base station 2 respectively, and Y C is the congestion threshold set for service type C). This indicates that after adjustment, the network slice providing service type C in base station 2 becomes more congested compared to base station 1. Based on this, the core network will control the user to preferentially access the network slice providing service type C in base station 1 and reconfigure the SPID1 of base station 1 for the user.

[0195] Therefore, when the congestion level of the base station network slice changes as described above, the advantage of such a setting is that it can flexibly adjust the user access strategy according to the dynamic change of the congestion level of the base station network slice. After the congestion level relationship of the network slices supporting service type C in base station 1 and base station 2 changes, it guides the user to access the relevant network slice of base station 1 with a lower congestion level and reconfigures the SPID, realizing the dynamic optimal allocation of network resources, avoiding the user being in a congested network environment for a long time, and improving the overall operation efficiency and service quality of the network.

[0196] Embodiment 5:

[0197] When it comes to operations related to user access to the network, it includes the following steps:

[0198] Step 1: Calculate the congestion level of the network slice.

[0199] First, according to the service type requested by the user, for the network slice supporting this service type in a specific base station, by calculating the ratio between the number of already connected users and its resource capacity, the congestion level of this network slice is determined. The specific calculation formula is: Congestion level = (Number of already connected users / Resource capacity of the network slice of the service type) × 100%.

[0200] Step 2: Determine the number of service types that the network can provide.

[0201] Based on the congestion level calculated for each network slice, determine the number of network slices that can provide corresponding services for the user. This number represents the number of service types that this network can provide for the user.

[0202] Step 3: Determine the final access network and configure the SPID.

[0203] Based on the ratio between the number of service types that the network can provide for users and the number of service types requested by the user, determine the network for the end user to access and configure the corresponding SPID for it.

[0204] For example, assume that there are three base stations on the access network side in this embodiment. The following are the relevant information of each base station:

[0205] Base Station 1:

[0206] Network slices and service types: Provide three network slices, supporting Service A, Service B, and Service C respectively.

[0207] Resource capacity: The resource capacity ratios used by each network slice are a1%, b1%, and c1% in sequence.

[0208] SPID and the number of connected users: The SPID used by this base station is SPID1. In the virtual networks corresponding to these three network slices, the number of connected users assigned SPID1 is l1, m1, and n1 respectively.

[0209] Base Station 2:

[0210] Network slices and service types: Also provide three network slices, supporting Service A, Service B, and Service C.

[0211] Resource capacity: The resource capacity ratios used by each network slice are a2%, b2%, and c2% respectively.

[0212] SPID and the number of connected users: The SPID used by this base station is SPID2. In the virtual networks corresponding to these three network slices, the number of connected users assigned SPID2 is l2, m2, and n2 respectively.

[0213] Base Station 3:

[0214] Network slices and service types: Provide two network slices, supporting Service A and Service B.

[0215] Resource capacity: The resource capacity ratios used by each network slice are a3% and b3% respectively.

[0216] SPID and the number of connected users: The SPID used by this base station is SPID3. In the virtual networks corresponding to these two network slices, the number of connected users assigned SPID3 is l3 and m3 respectively.

[0217] At the same time, congestion thresholds Y are set for Service A, Service B, and Service C respectively.A and Y B and Y C .

[0218] When the core network receives the NSSAI (Network Slice Selection Assistance Information) sent by a certain user, and this information indicates that the user requests services of service type A and service type C, it is necessary to calculate the network slice congestion degree of each base station as follows:

[0219] For base station 1, the network congestion degrees of the network slices providing service type A and service type C are calculated by the following formulas respectively: the network congestion degree Y1a of service type A = l1 / a1; the network congestion degree Y1c of service type C = n1 / c1.

[0220] For base station 2, the network congestion degrees of the network slices providing service type A and service type C are respectively: the network congestion degree Y2a of service type A = l2 / a2; the network congestion degree Y2c of service type C = n2 / c2.

[0221] For base station 3, since it only supports service type A and service type B, only the network congestion degree of the network slice of service type A is calculated, that is, Y3a = l3 / a3.

[0222] Next, according to the calculated congestion degree and the set threshold, discuss the selection of the base station accessed by the user in different cases:

[0223] Case 1 (Some base stations cannot provide effective services): If there are some base stations, the network congestion degrees of the network slices for some service types requested by the user all exceed the corresponding thresholds, resulting in these base stations being unable to provide effective services for the user; among the remaining base stations, there is a base station that can provide some of the service types requested by the user, and the network congestion degree of the network slice of the service type that this base station can provide is the lowest compared to other base stations that can provide services. In this case, calculate the ratio of the number of service types that each base station can provide for the user to the number of service types requested by the user. For the base stations that cannot provide effective services, this ratio is 0, and for the base stations that can provide some services, this ratio is less than 100%. The core network will control the user to preferentially access the network slice of the service type that can be provided in the base station with the relatively lowest congestion degree, and configure the corresponding SPID of this base station for the user.

[0224] For example, if Y1c > Y2c > Y C , and Y3a < YA < Y2a < Y1a. In this case, base station 3 can provide one of the service types requested by the user (service type A), while for base stations 1 and 2, since the network congestion degree of the network slice of service type C exceeds the threshold Y C, it is unable to provide effective services for users. At this time, the ratios of the number of service types that Base Station 1, Base Station 2, and Base Station 3 can provide for users to the number of service types requested by the users are 0, 0, and 50% respectively. Based on this, the core network will control the user to preferentially access the network slice that provides Service Type A in Base Station 3 and configure the SPID3 of Base Station 3 for the user.

[0225] Case 2 (Each base station can provide some services): If the congestion levels of the network slices of some service types requested by the user in all base stations exceed the corresponding thresholds, but each base station can provide some of the service types requested by the user. At this time, calculate the ratio of the number of service types that each base station can provide for the user to the number of service types requested by the user. The ratios of each base station are all less than 100% and equal. Compare the congestion levels of the network slices of the service types that each base station can provide. If there is a base station with the lowest congestion level in the network slices of the service types that it can provide compared to other base stations, the core network will control the user to preferentially access the network slice that can provide the service type in this base station and configure the corresponding SPID of this base station for the user.

[0226] For example, if Y1c > Y2c > Y C , and Y3a < Y2a < Y1a < YA. At this time, all three base stations can provide one of the service types requested by the user (Service Type A), that is, the ratios of the number of service types that Base Station 1, Base Station 2, and Base Station 3 can provide for the user to the number of service types requested by the user are all 50%. However, by comparing the congestion levels of the network slices of Service Type A in each base station, it can be seen that the congestion level of Base Station 3 is the lowest. Therefore, the core network will also control the user to preferentially access the network slice that provides Service Type A in Base Station 3 and configure the SPID3 of Base Station 3 for the user.

[0227] It should be noted that the main differences between Embodiment 5 and Embodiments 1, 2, 3, and 4 are as follows: In Embodiment 5, the service types requested by the user become two (Service Type A and Service Type C), and the number of users already connected (such as Y1a = l1 / a1) is used when calculating the congestion level of the network slice, which is different from Embodiment 3 that uses the maximum value of the allocated users and the number of users already connected to calculate the congestion level; at the same time, when selecting a base station, Embodiment 5 comprehensively considers the ratio of the number of service types that each base station can provide to the number of service types requested by the user and the congestion level, and preferentially selects a base station that can provide some services and has a low congestion level, while Embodiments 1 and 2 mainly select a base station according to the congestion level for one service type, and although Embodiment 4 also has two service types, the number of allocated users is used when calculating the congestion level.

[0228] Embodiment 6:

[0229] When processing relevant operations for user access to the network, when the core network determines the congestion level of the network slice, the number of service types it can provide, and the network to which the end user connects, and performs corresponding SPID configuration, the following steps are included:

[0230] Step 1: Calculate the congestion level of the network slice.

[0231] According to the service type requested by the user, for the network slice in a specific base station that supports this service type, calculate the ratio between its resource capacity and the maximum value of the number of preferentially accessed users already supported and the number of users already connected, so as to determine the congestion level of this network slice. The specific calculation formula is: Congestion level = (Number of users already connected / Resource capacity of the network slice of the service type) × 100%. Among them, the number of users already connected used in the calculation takes the maximum value of the number of preferentially accessed users already supported and the actual number of users already connected.

[0232] Step 2: Determine the number of service types that the network can provide.

[0233] Based on the congestion level calculated for each network slice, further determine the number of network slices that can provide corresponding services for users. This number represents the number of service types that this network can provide for users.

[0234] Step 3: Determine the final access network and configure the SPID.

[0235] According to the ratio between the number of service types that the network can provide for users and the number of service types requested by the user, determine the network for the end user to access, and configure the corresponding SPID for it.

[0236] For example, assume that there are three base stations on the access network side in this embodiment. The following are the relevant information of each base station:

[0237] Base station 1:

[0238] Network slices and service types: Provide three network slices, supporting service A, service B, and service C respectively.

[0239] Resource capacity: The resource capacity occupied by each network slice is a1%, b1%, and c1% in sequence.

[0240] SPID and user number information: The SPID used by this base station is SPID1. In the virtual networks corresponding to these three network slices, the number of users assigned SPID1 is L1, M1, and N1 respectively, and the number of users already connected is l1, m1, and n1 respectively.

[0241] Base station 2:

[0242] Network slices and service types: Three network slices are also provided, and the supported service types are Service A, Service B, and Service C.

[0243] Resource capacity: The resource capacity ratios used by each network slice are a2%, b2%, and c2% respectively.

[0244] SPID and user number information: The SPID used by this base station is SPID2. In the virtual networks corresponding to these three network slices, the numbers of users assigned SPID2 are L2, M2, and N2 respectively, and the numbers of connected users are l2, m2, and n2 respectively.

[0245] Base station 3:

[0246] Network slices and service types: Two network slices are provided, and the supported service types are Service A and Service B.

[0247] Resource capacity: The resource capacity ratios used by each network slice are a3% and b3% respectively.

[0248] SPID and user number information: The SPID used by this base station is SPID3. In the virtual networks corresponding to these two network slices, the numbers of users assigned SPID3 are L3 and M3 respectively, and the numbers of connected users are l3 and m3 respectively.

[0249] At the same time, congestion thresholds Y A 、Y B and Y C .

[0250] When the core network receives the NSSAI (Network Slice Selection Assistance Information) sent by a certain user, and this information indicates that the user requests services of Service Type A and Service Type C, it is necessary to calculate the congestion degree of the network slices of each base station as follows:

[0251] For base station 1, the network congestion degrees of the network slices providing Service Type A and Service Type C are calculated by the following formulas respectively: The network congestion degree of Service Type A, Y1a = max(L1, l1) / a1; The network congestion degree of Service Type C, Y1c = max(N1, n1) / c1.

[0252] For base station 2, the network congestion degrees of the network slices providing Service Type A and Service Type C are respectively: The network congestion degree of Service Type A, Y2a = max(L2, l2) / a2; The network congestion degree of Service Type C, Y2c = max(N2, n2) / c2.

[0253] For base station 3, since it only supports service type A and service B, the network congestion level of the network slice of service type A is only calculated, that is, Y3a = max(L3, l3) / a3.

[0254] Next, based on the calculated congestion level and the set threshold, the base station selection for user access is discussed in different cases:

[0255] Case 1 (Some base stations cannot provide effective services):

[0256] For example, if Y1c > Y2c > Y C , and Y3a < Y A < Y2a < Y1a. In this case, base station 3 can provide one of the service types requested by the user (service type A), while base stations 1 and 2 cannot provide effective services for the user because the network congestion level of the network slice of service type C exceeds the threshold Y C . At this time, the ratios of the number of service types that base stations 1, 2, and 3 can provide to the user to the number of service types requested by the user are 0, 0, and 50% respectively. Based on this, the core network will control the user to preferentially access the network slice of service type A in base station 3 and configure the SPID3 of base station 3 for the user.

[0257] Case 2 (Each base station can provide partial services):

[0258] For example, if Y1c > Y2c > YC, and Y3a < Y2a < Y1a < Y A . At this time, all three base stations can provide one of the service types requested by the user (service type A), that is, the ratios of the number of service types that base stations 1, 2, and 3 can provide to the user to the number of service types requested by the user are all 50%. However, by comparing the network congestion levels of the network slices of service type A of each base station, it can be seen that the congestion level of base station 3 is the lowest. Therefore, the core network will also control the user to preferentially access the network slice of service type A in base station 3 and configure the SPID3 of base station 3 for the user.

[0259] It should be noted that the main differences between Example 6 and Examples 1, 2, 3, 4, and 5 are as follows: In Example 6, when the user requests two service types (Service Type A and Service Type C), when calculating the congestion degree of the network slice, the maximum value of the allocated user number and the connected user number is used for calculation (such as Y1a = max(L1, l1) / a1), which is different from only using the connected user number or the allocated user number for calculation in Examples 1, 2, and 5, and is also different from only using the allocated user number for calculation in Example 4; and in terms of base station selection, considering the ratio of the number of service types that each base station can provide to the number of service types requested by the user and the congestion degree, a base station that can provide some services and has a low congestion degree is preferentially selected, which is different from Example 3 in that although the maximum value is used to calculate the congestion degree, the user in Example 3 requests one service type.

[0260] In some embodiments, during the operation of the network, there are various situations that may cause the SPID of a certain user to need to be reconfigured. The specific situations are as follows:

[0261] (1) Change in the service type requested by the user.

[0262] The service type requested by the user may change, which will affect the matching situation of the network to provide services for it, and thus may require reconfiguration of the SPID.

[0263] (2) Changes in network slice-related content.

[0264] ① New service type and network slice: The network newly supports a service type, and correspondingly a new network slice will be added, which may change the service capabilities and resource allocation of the network, and thus may require reconfiguration of the user's SPID.

[0265] ② Deletion of service type and corresponding network slice: The network no longer supports a certain supported service type, and the network slice supporting this service type will be deleted, which will affect the services that the user can obtain and may cause the SPID to need to be reconfigured.

[0266] ③ Adjustment of network slice resource capacity: The network adjusts the resource capacity of the supported network slice, which will change the congestion degree and service capabilities of the network slice, and may also require reconfiguration of the user's SPID.

[0267] (3) Change in the congestion degree of the network slice.

[0268] The congestion degree of a certain network slice in the network has changed, which may affect the user's service experience and the network's service allocation strategy, so it may also require reconfiguration of the SPID.

[0269] There are two ways for the network to determine whether the user's SPID needs to be reconfigured:

[0270] Periodic determination: The network can regularly check the relevant information of the user and the network status at a certain period to determine whether the user's SPID needs to be reconfigured.

[0271] Condition-triggered determination: When specific conditions are met, the network triggers the determination of whether the user's SPID needs to be reconfigured. For example, the user resends the NSSAI to the core network, indicating that the user's service request may have changed; or the congestion level of the network slice changes by α (α is preset by the network side, which can either be an increase in the congestion level by α or a decrease in the congestion level by α); or the network newly supports a service type or deletes at least one supported service type.

[0272] It should be noted that the advantages of the above-mentioned SPID reconfiguration are that it can better meet the dynamic service needs of users, adapt to changes in their service types, and flexibly respond to the addition, deletion, and resource capacity adjustment of network slices; by dynamically adjusting the SPID according to the congestion level, it optimizes network resource allocation, avoids congestion or resource waste; the combination of periodic and condition-triggered determination improves the flexibility and efficiency of network management, reduces unnecessary operations; at the same time, it enables the network to quickly respond to changes, enhances adaptability and market competitiveness, and guarantees service quality and user experience.

[0273] The user management device for network slicing provided by the present application will be described below. The user management device for network slicing described below can be mutually referred to the user management method for network slicing described above.

[0274] Please refer to Figure 2 , Figure 2 which is the structural diagram of the user management device for network slicing. A user management device 200 for network slicing includes an extraction module 210, a calculation module 220, and a selection module 230.

[0275] Exemplarily, the extraction module 210 is configured to receive network slice selection assistance information sent from a user terminal in the core network and extract the user-requested service type from the network slice selection assistance information.

[0276] Exemplarily, the calculation module 220 is configured to screen out the base stations with the ability to support the user-requested service type from all base stations according to the extracted user-requested service type; for the network slices that support the user-requested service type among the screened base stations, calculate their congestion levels according to the resource capacity.

[0277] Exemplarily, the selection module 230 is configured to select a subscriber profile identifier adapted thereto from multiple candidate subscriber profile identifiers based on the calculated network slice congestion degree, and the subscriber profile identifier is used to guide the user to access a base station cell that can not only meet the requirements of the user's required service type but also has a relatively low network congestion degree.

[0278] Exemplarily, the user management device 200 for network slices is further configured to:

[0279] The network side collects data according to a specific policy, where the policy includes collecting during a specific period, collecting for a specific geographical area, or collecting at periodic time intervals, and the collected data includes the resource congestion degree and resource utilization rate of the network slice;

[0280] After obtaining the resource congestion degree or resource utilization rate of the network slice, the network side compares and analyzes the obtained data with a pre-set threshold, and determines whether it is necessary to recalculate the resource capacity of the network slice according to the comparison result;

[0281] After completing the calculation of the new resource capacity of the network slice, the network side determines whether it is necessary to reconfigure the subscriber profile identifier for the user;

[0282] If it is determined through judgment that it is necessary to reconfigure the subscriber profile identifier for the user, the network side performs the reconfiguration operation of the subscriber profile identifier for the user.

[0283] Exemplarily, the calculation of the congestion degree is determined according to the following rules:

[0284] Determined according to the ratio between the number of preferential access users that have been supported and the resource capacity of the network slice of the base station that supports the service type requested by the user; or

[0285] Determined according to the ratio between the maximum value of the number of preferential access users that have been supported and the number of users that have already accessed and the resource capacity of the network slice of the base station that supports the service type requested by the user;

[0286] Wherein, the number of preferential access users that have been supported refers to the number of users whose assigned subscriber profile identifier is the same as the subscriber profile identifier assigned by the core network to the virtual network corresponding to each network slice of the base station.

[0287] Exemplarily, the user management device 200 for network slices is further configured to:

[0288] When there are some base stations whose congestion levels of network slices for certain service types requested by a user all exceed the corresponding preset thresholds, resulting in these base stations being unable to provide effective services to the user; and among the remaining base stations, there is a base station that can provide some of the service types requested by the user, and the congestion level of the network slice of the service types that this base station can provide is at the lowest level compared to other base stations that can provide services;

[0289] The core network controls the user to preferentially access the network slice of the service types that can be provided in the base station with the relatively lowest congestion level, and configures the subscriber profile identifier corresponding to this base station for the user.

[0290] Exemplarily, the user management device 200 for network slices is further configured to:

[0291] If the congestion levels of network slices for certain service types requested by a user of all base stations all exceed the corresponding preset thresholds, but each base station can provide some of the service types requested by the user; then compare the congestion levels of the network slices of the service types that each base station can provide;

[0292] If there is a base station among them whose congestion level of the network slice of the service types that can be provided is at the lowest level compared to other base stations, the core network controls the user to preferentially access the network slice of the service types that can be provided in this base station, and configures the subscriber profile identifier corresponding to this base station for the user.

[0293] Exemplarily, the user management device 200 for network slices is further configured to:

[0294] When there are some base stations whose congestion levels of network slices for certain service types requested by a user all exceed the corresponding preset thresholds, resulting in these base stations being unable to provide effective services to the user; and among the remaining base stations, there is a base station that can provide some of the service types requested by the user, and the congestion level of the network slice of the service types that this base station can provide is at the lowest level compared to other base stations that can provide services;

[0295] The core network calculates the ratio of the number of service types that each base station can provide to the user to the number of service types requested by the user, where for a base station that cannot provide effective services, this ratio is 0, and for a base station that can provide some services, this ratio is less than 100%;

[0296] The core network controls the user to preferentially access the network slice of the service types that can be provided in the base station with the relatively lowest congestion level, and configures the subscriber profile identifier corresponding to this base station for the user.

[0297] Exemplarily, the user management device 200 for network slices is further configured to:

[0298] If the congestion levels of the network slices for certain service types requested by the user exceed the corresponding preset thresholds at all base stations, but each base station can provide some of the service types requested by the user; then calculate the ratio of the number of service types that each base station can provide to the user to the number of service types requested by the user, and this ratio is less than 100% and equal for each base station.

[0299] The core network compares the congestion levels of the network slices for the service types that each base station can provide; if there is a base station whose congestion level of the network slices for the service types it can provide is at the lowest level compared to other base stations, then control the user to preferentially access the network slice of this base station that can provide the service type, and configure the subscriber profile identifier corresponding to this base station for the user.

[0300] Exemplarily, the user management device 200 for network slices is further configured to:

[0301] According to the dynamic changes in the user service requests, the addition of base station service types, the deletion of base station service types, and the adjustment of base station network slice configurations, the core network re - selects the network slice of the base station with the lowest congestion level for the user to access based on the congestion levels of the network slices of each base station for the relevant service types, and re - configures the subscriber profile identifier for the user.

[0302] In some embodiments, the present application further provides a core network, and the core network is configured to execute the steps of the user management method for network slices described in the above embodiments.

[0303] Specifically, the core network first receives the supported service types and resource capacity information sent by the base station, as well as the network slice selection assistance information of the user terminal, then comprehensively matches these information for service types, calculates the congestion level, and selects a suitable subscriber profile identifier from multiple candidate SPIDs, and then distributes it to the base station and the end - user to guide the user to access the appropriate base station cell. When there are changes in base station service types and other situations, the core network can also select a suitable base station among the remaining base stations that support the corresponding service types, control the user to access and re - configure the SPID. In this way, the core network can dynamically adjust the user access strategy according to the actual network situation and user needs, avoiding the limitations of a single SPID configuration, enabling the operator to make the user access the adapted cell more smoothly in the scenario of supporting network slices, effectively improving the user service experience and communication quality, enhancing the flexibility, reliability, and adaptability of network services, and ensuring the reasonable allocation and efficient utilization of network resources.

[0304] It should be noted here that the above - mentioned device and core network provided in the embodiments of the present application can implement all the method steps implemented by the above - mentioned method embodiments, and can achieve the same technical effects. The same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.

[0305] Obviously, those skilled in the art can make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to cover these changes and modifications.

Claims

1. A user management method for network slicing, characterized in that: Applied to the network side, the network side includes a base station and a core network; For each base station, when performing a network slicing operation, the base station sends a notification message to the core network, which informs the core network of the service types it supports and the resource capacity used in the network slicing process; The method comprises: The core network receives the network slice selection auxiliary information sent by the user terminal, and extracts the user requested service type from the network slice selection auxiliary information; According to the extracted user requested service type, base stations capable of supporting the user requested service type are screened out from all base stations; for the network slices supporting the user requested service type among the screened out base stations, the congestion degree thereof is calculated according to the resource capacity; Based on the calculated congestion level of the network slice, a subscriber profile identifier that matches the congestion level is selected from multiple candidate subscriber profile identifiers. The subscriber profile identifier is used to guide the user to access a base station cell that can meet the user's required service type requirements and has a relatively low network congestion level.

2. The user management method for network slicing according to claim 1, characterized in that: The method further comprises: The network side collects data according to a specific strategy, which includes collecting data during a specific period of time, collecting data for a specific geographical area, or collecting data at periodic time intervals. The collected data includes the resource congestion level and resource utilization rate of the network slice; After obtaining the resource congestion level or resource utilization rate of the network slice, the network side compares and analyzes the obtained data with the preset threshold, and determines whether it is necessary to recalculate the resource capacity of the network slice based on the comparison result; After the calculation of the new resource capacity of the network slice is completed, the network side determines whether it is necessary to reconfigure the subscriber profile identifier for the user; If it is determined that the subscriber profile identifier needs to be reconfigured for the user, the network side performs a subscriber profile identifier reconfiguration operation for the user.

3. The user management method for network slicing according to claim 2, characterized in that: The calculation of the congestion level is determined according to the following rules: Determined according to the ratio between the number of supported priority access users and the resource capacity of the network slice of the base station supporting the service type requested by the user; or The value is determined according to a ratio between the maximum value of the number of supported priority access users and the number of already accessed users and the resource capacity of the network slice of the base station supporting the service type requested by the user; Among them, the number of priority access users that have been supported refers to the number of users whose assigned subscriber profile identifier is the same as the subscriber profile identifier assigned by the core network to the virtual network corresponding to each network slice of the base station.

4. The user management method for network slicing according to claim 1, characterized in that: For multiple user request service types, the method further includes: When there are some base stations, the congestion levels of network slices for certain service types requested by users exceed the corresponding preset thresholds, so that these base stations cannot provide effective services to users; among the remaining base stations, there are base stations that can provide some of the services requested by users, and the congestion level of network slices of the service types that can be provided by this base station is at the lowest level compared with other base stations that can provide services; The core network controls the user to preferentially access the network slice that can provide the service type in the base station with the relatively lowest congestion level, and configures the subscriber profile identifier corresponding to the base station for the user.

5. The user management method for network slicing according to claim 4, characterized in that: The method further comprises: If the congestion levels of network slices of all base stations for certain service types requested by users exceed the corresponding preset thresholds, but each base station can provide part of the service types requested by users; then the congestion levels of network slices of each base station for the service types that can be provided are compared; If there is a base station with the lowest congestion level in the network slice that can provide the service type compared with other base stations, the core network controls the user to give priority access to the network slice that can provide the service type in this base station, and configures the subscriber profile identifier corresponding to the base station for the user.

6. The user management method for network slicing according to claim 1, characterized in that: For multiple user request service types, the method further includes: When there are some base stations, the congestion levels of network slices for certain service types requested by users exceed the corresponding preset thresholds, so that these base stations cannot provide effective services to users; among the remaining base stations, there are base stations that can provide some of the services requested by users, and the congestion level of network slices of the service types that can be provided by this base station is at the lowest level compared with other base stations that can provide services; The core network calculates the ratio of the number of service types that each base station can provide to the user to the number of service types requested by the user. The ratio is 0 for base stations that cannot provide effective services, and the ratio is less than 100% for base stations that can provide partial services. The core network controls the user to preferentially access the network slice that can provide the service type in the base station with the relatively lowest congestion level, and configures the subscriber profile identifier corresponding to the base station for the user.

7. The user management method for network slicing according to claim 6, characterized in that: The method further comprises: If the congestion levels of network slices for certain service types requested by users by all base stations exceed the corresponding preset thresholds, but each base station can provide some of the services requested by the user; then the ratio of the number of service types that each base station can provide to the user to the number of service types requested by the user is calculated, and the ratios of each base station are less than 100% and equal; The core network compares the congestion levels of network slices that can provide service types for each base station; if one of the base stations has the lowest congestion level in the network slices that can provide service types compared to other base stations, the user is controlled to have priority access to the network slice that can provide service types in this base station, and the subscriber profile identifier corresponding to the base station is configured for the user.

8. The user management method for network slicing according to claim 1, characterized in that: The method further comprises: Based on the dynamic changes in user service requests, the addition of base station service types, the deletion of base station service types, and the adjustment of base station network slice configurations, the core network reselects the base station network slice with the lowest congestion for user access based on the congestion level of network slices for relevant service types at each base station, and reconfigures the subscriber profile identifier for the user.

9. A user management device for network slicing, characterized in that: Applied to the network side, the network side includes a base station and a core network; For each base station, when performing a network slicing operation, the base station sends a notification message to the core network, which informs the core network of the service types it supports and the resource capacity used in the network slicing process; The device comprises: An extraction module, configured to receive network slice selection auxiliary information sent by a user terminal in a core network, and extract a user requested service type from the network slice selection auxiliary information; A calculation module, configured to screen out base stations capable of supporting the user requested service type from all base stations according to the extracted user requested service type; and calculate the congestion degree of network slices supporting the user requested service type among the screened base stations according to the resource capacity; The selection module is used to select a subscriber profile identifier that is suitable for the calculated network slice congestion level from multiple candidate subscriber profile identifiers. The subscriber profile identifier is used to guide the user to access a base station cell that can meet the user's required service type requirements and has a relatively low network congestion level.

10. A core network, characterized in that: The core network is used to execute the steps of the user management method for network slicing as described in any one of claims 1 to 8.

Images