Network entities and methods for controlling UE network slice transfer

Abstract

A network entity (110a; 110) (especially an execution network function ENF) is disclosed for controlling the transfer of one or more user equipments (UEs) from a network slice (130a) of a mobile network (100) to another network slice (130b). The network entity (especially the ENF) (110a; 110) is used to send a network slice replacement NSR notification message to an application function AF (140) associated with an application running on the plurality of UEs (120a-n), wherein the NSR notification message includes a corresponding identifier of the one or more UEs transferring to the other network slice (130b), an identifier of the network slice (130a), and / or an identifier of the other network slice (130b).

Description

Technical Field

[0001] This invention relates to wireless communication. More specifically, this invention relates to network entities and methods for controlling and supporting the transfer of selected user equipment (UE) from one network slice of a mobile network (especially a 3GPP mobile network) to another. Background Technology

[0002] When the current network slice cannot support the required service, 5G mobile communication technology with Network Slice Replacement (NSR) capability assigns the UE to an alternative network slice (i.e., Alternate S-NSSAI) to ensure service continuity for the UE. For example, a network slice supporting the required service may become unavailable due to overload of the current network slice, i.e., congestion (which can be considered a no-mobility situation), and / or because the current network slice is unavailable in one or more new service areas that the UE is moving to (which can be considered a mobility situation).

[0003] 3GPP specification TS23.501 defines how a network detects and triggers the NSR procedure through CN entities. Specifically, the Access and Mobility Management Function (AMF), along with other CN NFs (e.g., Network Slice Selection Function (NSSF), Policy Control Function (PCF), and / or Operation and Management (OAM)), detects that S-NSSAI has become unavailable or congested. For example, based on the analysis output of OAM or Network Data Analytics Function (NWDAF), it is assumed that an alternative S-NSSAI is available in the Network Slice Area of ​​Service (NS-AoS).

[0004] The identified mechanism assumes the network can detect which S-NSSAIs (or which UEs) are congested and can select alternative S-NSSAIs to initiate an NSR procedure. On one hand, there is no option for NSR to be triggered by other entities (e.g., Application Functions (AFs)). For example, when a UE or a group of UEs temporarily changes their UE SLA—for instance, when a UE requests a specific service (e.g., higher throughput) for a specific application need within a specific time period and is willing to bear the corresponding higher cost—the AF can initiate an NSR to the network. Correspondingly, the application provider (e.g., the AF) might temporarily trigger an NSR to the network for one or more UEs. On the other hand, it assumes all UEs in the current network slice can obtain service in alternative network slices. When transferring UEs to alternative network slices, it is equally important to support mechanisms that appropriately select UEs based on UE needs and network performance (e.g., UE SLA).

[0005] Network-triggered NSR does not cover NSR events initiated by other entities or based on other conditions; for example, when one or more UEs need to temporarily change their SLA with the application provider (e.g., AF) due to their own needs, this falls into this category. Similarly, when an application provider detects that the needs (e.g., QoS or QoE) of one or more UEs are not being met, it will trigger an NSR event for one or more specific UEs.

[0006] If one or more UEs to be migrated to an alternative S-NSSAI are unknown or not considered for NSR triggered by the network, there is no mechanism to migrate which UEs to which alternative S-NSSAI. By appropriately selecting suitable UEs from the appropriate S-NSSAI, the network can improve overall UE satisfaction and the efficient utilization of available resources. Summary of the Invention

[0007] The purpose of this invention is to provide improved entities and methods for controlling and supporting the transfer of selected user equipment (UE) from one network slice of a mobile network (especially a 3GPP mobile network, such as a 5G or 6G network) to another network slice.

[0008] The foregoing and other objectives are achieved through the subject matter claimed in the independent claims. Other implementations are apparent from the dependent technical solutions, the specification, and the drawings.

[0009] According to a first aspect, a network entity (especially an Enforcement Network Function, ENF) is provided for controlling the transfer of one or more UEs from a network slice S-NSSAI of a mobile network to another network slice Alt-S-NSSAI. The network entity (especially the ENF) according to the first aspect is used to send a Network Slice Replacement (NSR) notification message to an application function (AF) associated with an application running on the plurality of UEs. The NSR notification message includes a corresponding identifier of the one or more UEs transferring to the other network slice, an identifier of the network slice, and / or an identifier of the other network slice. This enables the AF to be aware that a new S-NSSAI is associated with an application running on one or more UEs (associated with the new S-NSSAI). Therefore, the network entity according to the first aspect can be triggered by the AF to control the transfer of one or more UEs from a network slice in a mobile network to another network slice.

[0010] In another possible implementation, the AF is used to associate the one or more UEs running the application with another network slice Alt-S-NSSAI of the mobile network. Based on this, the AF can check the QoS, QoE, or SLA of one or more specific UEs associated with the other network slice Alt-S-NSSAI, and (e.g., when the QoS or SLA requirements are not met) can trigger a request to the network to control the transfer of the UE among the plurality of UEs from the network slice to the other network slice.

[0011] In another possible implementation, the network entity is configured to receive from the AF an NSR request for transferring one or more of the plurality of UEs from the network slice of the mobile network to the other network slice, wherein the NSR request includes a corresponding identifier of the one or more UEs, an identifier of the network slice, an identifier of the other network slice, an identifier of the application associated with the AF, and / or an indication of network slice replacement for the one or more UEs from the network slice. This enables the network entity to control the transfer of one or more UEs from one network slice in the mobile network to another network slice in response to a request from the AF.

[0012] In another possible implementation, in response to receiving the NSR request from the AF, the network entity selects one or more of the plurality of UEs and triggers (i.e., initiates) a transfer of the one or more of the plurality of UEs from the network slice of the mobile network to the other network slice. Therefore, the network entity selects the UE most suitable for the transfer.

[0013] In another possible implementation, the network entity (especially the ENF) is used to receive the NSR request from the AF in response to sending the NSR notification message to the AF. This enables the adjustment of the transfer of one or more UEs from one network slice in the mobile network to another network slice in response to a request from the AF.

[0014] In another possible implementation, in response to receiving the NSR request from the AF, the network entity triggers (i.e., initiates) a transfer of one or more of the plurality of UEs from the other network slice of the mobile network back to the original network slice. This enables the revocation of a transfer of one or more UEs from one network slice in the mobile network to another network slice, provided that the transfer does not produce one or more desired results.

[0015] In another possible implementation, the network entity is configured to receive an NSR request from the core network (CN) function of the mobile network for transferring one or more UEs from the network slice of the mobile network to the other network slice, wherein the NSR request includes an identifier of the network slice and / or an identifier of the other network slice. This enables the network entity to control the transfer of one or more UEs from one network slice to another network slice in response to a request from the CN NF of the mobile network.

[0016] In another possible implementation, in response to receiving the NSR request from the CN network function of the mobile network, the network entity selects one or more UEs from the plurality of UEs and triggers (i.e., initiates) a transfer of the selected one or more UEs from the network slice of the mobile network to the other network slice. Therefore, the network entity selects the UE most suitable for the transfer.

[0017] In another possible implementation, each of the plurality of UEs is associated with a Service Level Agreement (SLA), wherein each SLA defines one or more Service Level Objects (SLOs) for one or more SLA attributes, and wherein the network entity is used to determine, or obtain from another network entity (particularly the Tracking and Evaluation Network Function (TENF)) monitoring data (i.e., stateful information) of each of the plurality of UEs, and to select one or more UEs from the plurality of UEs based on the monitoring data of each of the plurality of UEs (i.e., to prioritize them). This enables the network entity to perform the selection of the UEs based on the monitoring data provided by the TENF.

[0018] In another possible implementation, the network entity selects one or more UEs from the plurality of UEs based on the monitoring data of each of the UEs (i.e., prioritizes them), wherein the monitoring data is related to the status of the SLA or SLA compliance of each of the plurality of UEs. This enables the network entity to perform the selection of the UE based on the status of the SLA compliance of each UE.

[0019] In another possible implementation, the monitoring data determined by the network entity or obtained from the other network entity includes a stateful assessment of each of the plurality of UEs. This enables the network entity to perform selection of the UE based on the stateful assessment of each UE.

[0020] In another possible implementation, the mobile network is a 3GPP network, and the network entity is a policy control function or network data analysis function of the mobile network. This allows for seamless implementation of the network entity described in the first aspect within the existing 3GPP network architecture.

[0021] According to the second aspect, another network entity (particularly a Tracking and Evaluation Network Function (TENF)) is provided to support the transfer of one or more UEs from a network slice to another network slice controlled by a network entity of a mobile network. The other network entity according to the second aspect is used to determine a stateful evaluation for each of the plurality of UEs and to send the stateful evaluation for each of the plurality of UEs as monitoring data to the network entity for controlling the transfer of the UEs from the first network slice to the other network slice. Therefore, the network entity can provide information for selecting the most suitable UE for the transfer from the first network slice to the other network slice.

[0022] In another possible implementation, the other network entity (especially TENF) is used to determine the stateful assessment of each of the plurality of UEs based on the following: one or more service level agreement (SLA) attributes, one or more associated service level objectives (SLOs) for each SLA attribute, one or more tolerances maintained by each SLO, and / or a specific time window associated with the tolerances maintained by each SLO.

[0023] According to a third aspect, a method is provided for operating a network entity (in particular, performing an Enforcement Network Function (ENF)) for controlling the transfer of one or more user equipment (UEs) from one network slice of a mobile network to another. The method according to the third aspect includes: Send a Network Slice Replacement (NSR) notification message to the application function (AF) associated with the application running on the plurality of UEs, wherein the NSR notification message includes the corresponding identifier of the one or more UEs, the identifier of the network slice and / or the identifier of another network slice.

[0024] The method described according to the third aspect can be executed by the network entity described according to the first aspect. Therefore, other features of the method described according to the third aspect arise from the functionality of the network entity described according to the first aspect, as well as the different implementations and embodiments described above and below.

[0025] According to a fourth aspect, a method is provided for operating another network entity (particularly Tracking and Evaluation Network Function (TENF)) to support the transfer of one or more user equipment (UEs) from a network slice to another network slice controlled by a network entity of a mobile network. The method according to the fourth aspect includes: Determine the stateful assessment for each of the plurality of UEs; The stateful assessment of each of the plurality of UEs is sent as monitoring data to the network entity for controlling the transfer of the UE from the network slice to the other network slice.

[0026] The method described according to the fourth aspect can be performed by another network entity described according to the third aspect. Therefore, other features of the method described according to the fourth aspect arise from the functionality of the other network entity described according to the third aspect, as well as the different implementations and embodiments described above and below.

[0027] According to a fifth aspect, a computer program product is provided, including a computer-readable storage medium for storing program code that, when executed by a computer or processor, causes the computer or processor to perform the method according to a third aspect or the method according to a fourth aspect.

[0028] Details of one or more embodiments are set forth in the accompanying drawings and the following description. Other features, objects, and advantages will be apparent from the specification, drawings, and claims. Attached Figure Description

[0029] The embodiments of the present invention will be described in more detail below with reference to the accompanying drawings, in which: Figure 1a and Figure 1b A schematic diagram of the core network of a mobile network according to one embodiment is shown. The mobile network includes a network entity and another network entity for controlling and supporting the transfer of one or more UEs from one network slice of the mobile network to another network slice. Figure 2a and Figure 2b A schematic diagram illustrating the transfer of one or more UEs from one network slice to another network slice of a mobile network controlled by a network entity, according to one embodiment; Figure 3a and Figure 3b It shows according to Figure 1a and Figure 1b The signaling diagram of message exchange between a network entity and another network entity in an embodiment, wherein the network entity and the other network entity are used to control and support the transfer of one or more UEs from a network slice of a mobile network to another network slice; Figure 4a and Figure 4b It shows according to Figure 1a and Figure 1b The signaling diagram of message exchange between a network entity and another network entity in an embodiment, wherein the network entity and the other network entity are used to control and support the transfer of one or more UEs from a network slice of a mobile network to another network slice; Figure 5 A schematic diagram of the core network of a mobile network according to another embodiment is shown, the mobile network including a network entity and another network entity for controlling and supporting the transfer of one or more UEs from one network slice of the mobile network to another network slice; Figure 6a and Figure 6b It shows according to Figure 5 The signaling diagram of message exchange between a network entity and another network entity in an embodiment, wherein the network entity and the other network entity are used to control and support the transfer of one or more UEs from a network slice of a mobile network to another network slice; Figure 7a and Figure 7b It shows according to Figure 5 The signaling diagram of message exchange between a network entity and another network entity in an embodiment, wherein the network entity and the other network entity are used to control and support the transfer of one or more UEs from a network slice of a mobile network to another network slice; Figure 8a and Figure 8b It shows according to Figure 5 The signaling diagram of message exchange between a network entity and another network entity in an embodiment, wherein the network entity and the other network entity are used to control and support the transfer of one or more UEs from a network slice of a mobile network to another network slice; Figure 9 A table showing information from a network entity according to one embodiment for implementing a UE selection strategy for transferring one or more UEs from a network slice of a mobile network to another network slice; Figure 10 A schematic diagram of a processing phase implemented by another network entity according to one embodiment is shown, the other network entity being used to support the transfer of one or more UEs from a network slice of a mobile network to another network slice; Figure 11a and Figure 11bAn algorithm implemented by a network entity according to one embodiment is shown, the network entity being used to control the transfer of one or more UEs from one network slice of a mobile network to another network slice; Figures 12a to 12f A table showing exemplary values ​​determined by a network entity according to one embodiment, the network entity being used to control the transfer of one or more UEs from one network slice of a mobile network to another network slice; Figure 13 A flowchart is shown according to one embodiment of a method for operating a network entity, the network entity being used to control the transfer of one or more UEs from one network slice of a mobile network to another network slice; Figure 14 A flowchart is shown according to one embodiment of a method for operating another network entity, the other network entity being used to support the transfer of one or more UEs from a network slice of a mobile network to another network slice.

[0030] In the following text, the same reference numerals refer to the same or at least functionally equivalent features. Detailed Implementation

[0031] In the following description, reference is made to the accompanying drawings, which form part of this invention, and which illustrate by way of description specific aspects of embodiments of the invention or aspects in which embodiments of the invention may be used. It should be understood that embodiments of the invention can be used in other aspects and include structural or logical changes not depicted in the drawings. Therefore, the following detailed description should not be construed in a limiting sense, and the scope of the invention is defined by the appended claims.

[0032] For example, it should be understood that the disclosure relating to the described method also applies to the corresponding device or system for performing the method, and vice versa. For instance, if one or more specific method steps are described, the corresponding device may include one or more units (e.g., functional units) to implement the described one or more method steps (e.g., one unit implements one or more steps, or multiple units respectively implement one or more of the one or more steps), even if such one or more units are not explicitly described or shown in the drawings. Furthermore, if a particular apparatus is described based on one or more units (e.g., functional units), the corresponding method may include a step to perform the function of one or more units (e.g., one step performs the function of one or more units, or multiple steps respectively perform the function of one or more of a plurality of units), even if such one or more steps are not explicitly described or shown in the drawings. Additionally, it should be understood that, unless otherwise stated, features of the various exemplary embodiments and / or aspects described herein can be combined with each other.

[0033] Figure 1aA schematic diagram of a portion of a mobile network 100 (specifically a 3GPP mobile network 100, such as a 5G or 6G network) is shown. More specifically, Figure 1a The network functional entities of the core network (CN) of mobile network 100 are shown. This mobile network may also include a radio access network (RAN). Figure 2a and Figure 2b As shown, the RAN of the mobile network 100 may include multiple base stations or access points 115a, 115b for providing communication access to multiple user equipment (UE) 120a-n.

[0034] As will be described in more detail below, Figure 1a The CN of the mobile network 100 shown includes network entity 110a (specifically, an Enforcement Network Function (ENF) 110a) for controlling one or more UEs among multiple UEs 120a-n from network slice S-NSSAI 130a of the mobile network 100 (such as...). Figure 2a and Figure 2b The transfer from one UE (shown) to another network slice, Alt-S-NSSAI 130b. Network entity 110a (especially ENF 110a) sends a Network Slice Replacement (NSR) notification message to an application function (AF) 140 associated with applications running on multiple UEs 120a-n. The NSR notification message includes the corresponding identifier of one or more UEs being transferred to another network slice 130b, the identifier of network slice 130a, and / or the identifier of the other network slice 130b. As will be described in more detail below, network entity 110a (especially ENF 110a) can receive triggers from AF 140 or other CN network functions 150, 151 for transferring one or more UEs from network slice S-NSSAI 130a to another network slice, Alt-S-NSSAI 130b.

[0035] As will be described in more detail below, Figure 1aThe CN of the illustrated mobile network 100 includes another network entity 110b (specifically, a Tracking and Evaluation Network Function (TENF) 110b) for supporting the transfer of one or more UEs from network slice 130a to another network slice 130b controlled by network entity 110a (e.g., ENF 110a). The other network entity 110b (specifically, TENF 110b) is used to determine a stateful evaluation for each of the multiple UEs 120a-n and provides this stateful evaluation as monitoring data to network entity 110a (specifically, ENF 110a) for controlling the transfer of one or more UEs from network slice 130a to another network slice 130a. Figure 1a As shown, in one embodiment, network entity 110a (especially ENF 110a) and another network entity 110b (especially TENF 110b) may be components of a single network entity function 110.

[0036] Figure 1bThe different processes and interactions between the core network entity and the AF are illustrated for controlling and supporting the transfer of one or more UEs (UEs) from network slice 130a to another network slice 130b of mobile network 100. As will be described in more detail below, based on a network-triggered NSR request (step 0a), ENF 110a and TENF 110b interact for UE selection based on a stateful SLA (step 0b) and support NSR implementation, i.e., determining the transfer of one or more UEs (UEs) from network slice 130a to another network slice 130b (step 0c). The AF 140 is then notified of the change in the association of one or more UEs from network slice 130a to another network slice 130b (step 1a). If the QoS, QoE, or SLA requirements of one or more UEs associated with another network slice 130b are not met, or if adjustments to the QoS, QoE, or SLA of one or more UEs associated with network slice 130a are required, AF 140 may trigger a request to ENF 110a to control the transfer of one or more UEs associated with another network slice 130b back to (original) network slice 130a, or the transfer of UEs among multiple UEs 120a-n from network slice 130a to another network slice 130b (step 1b). Based on the NSR trigger request from AF 140, ENF 110a performs NSR control (steps 2a to 2c), wherein ENF 110a may optionally obtain Alt-S-NSSAI information from the core network entity (step 2a) and perform the transfer of one or more UEs from S-NSSAI 130a to Alt-S-NSSAI 130b. Optionally, if the capacity of Alt-S-NSSAI 130b is limited, ENF 110a may perform (stateful) SLA-based UE selection (steps 2b to 2c) on the requested UE from AF 140, similar to steps 0a and 0b. Then, regardless of whether the request is successful, partially successful, or unsuccessful, ENF 110a sends an acknowledgment response to AF 140 (step 3a).

[0037] Before describing more detailed embodiments of network entity 110a (especially ENF 110a) and another network entity 110b (especially TENF 110b) below, some technical background and terminology will be introduced using one or more of the following acronyms and abbreviations: 5G fifth-generation mobile network technology standard 5G-A fifth-generation mobile network evolution technology standard 6G sixth-generation mobile network technology standard CN Core Network AN access network AF application functions SMF Session Management Function PCF strategy control function NWDAF network data analysis function NS Network Functions NS_AoS network slicing service area As used herein, a “UE SLA” is a Service Level Agreement (SLA) between a user (UE) and a service provider (e.g., a network operator or application provider). A UE SLA may include one or more UE-specific / related attributes and their service level objectives (SLOs). Examples of UE-specific or related attributes defined in the GSMA (General Network Slicing Template, version 9.0) include, for example, maximum downlink throughput per UE, maximum uplink throughput per UE, service availability, and packet delay budget (PDB). Other types of UE SLAs include information related to subscription plans, such as data volume limits (maximum downlink bit rate, maximum uplink bit rate, maximum downlink data volume, or maximum uplink data volume). Another example of a UE SLA includes service (e.g., V2X service) requirements and committed SLOs for performance KPIs (i.e., guaranteed downlink throughput, guaranteed uplink throughput, and service availability SLOs associated with tolerances and time windows). The tolerance maintained by each SLO can be defined as a percentage value relative to a time window. For example, the service availability tolerance is 1% within a 30-day time window, which means that the maximum acceptable service unavailability within 30 days is 1% of the 30 days (i.e., 7.2 hours).

[0038] As used in this article, "stateful SLA" means that a UE SLA can be evaluated based on SLA attributes and its service level objective (SLO), the tolerance maintained by each SLO, and the specific time window for the tolerance maintained by each SLO.

[0039] As used herein, “Network Slice Replacement (NSR)” is defined as a feature of 3GPP mobile networks used to replace an S-NSSAI with an alternative S-NSSAI when the S-NSSAI becomes unavailable or congested, as defined in TS23.501. The terms “network slice” and “S-NSSAI” are used interchangeably herein. The terms “another network slice,” “alternate S-NSSAI,” and “Alt-S-NSSAI” are used interchangeably herein. The terms “monitoring data,” “stateful information,” “stateful assessment,” and “stateful assessment results” are used interchangeably herein.

[0040] The embodiments disclosed herein are based on stateful SLA assessments to determine the appropriate selection of one or more UEs by network entity 110a (specifically ENF 110a) during the NSR process. In one embodiment, each UE is assessed and selected based on the history of SLAs (i.e., instances where the network provides services to UEs for agreed SLAs). As will be described in more detail below, in one embodiment, these UEs are prioritized based on stateful SLA assessments or stateful information of multiple UEs 120a-n. UE selection policies are defined based on the prioritized UEs and the NSR scenario. The UE selection policies define rules for one or more UEs 120a-n to continue using in the current S-NSSAI 130a, and rules for UEs 120a-n to migrate to an alternative S-NSSAI 130b. For example, if a UE has not violated an SLA, it can be identified as a low-priority UE; if, based on a stateful SLA assessment, it is likely to violate an SLA soon, it can be identified as a high-priority UE. In one embodiment, in a non-mobility NSR scenario, the UE selection strategy may be to migrate a low-priority UE to the alternative S-NSSAI 130b. In a mobility scenario, the UE selection strategy may be to migrate a high-priority UE to the alternative S-NSSAI 130b.

[0041] As mentioned above Figure 1a As described in the context, according to one embodiment, AF 140 can trigger NSR based on UE SLA adaptive adjustment. This enables AF 140 to trigger the NSR procedure and interact with network 100 regarding the NSR procedure when the UE adaptively adjusts the SLA. An example of UE SLA adaptive adjustment is a temporary upgrade of the data plan. Another example is a change in UE SLA requirements relative to application requirements (e.g., QoS or QoE requirements).

[0042] for Figure 2aIn the illustrated NSR event of a no-mobility scenario, when network 100 detects congestion in S-NSSAI 130a (e.g., S-NSSAI #1), an alternative S-NSSAI 130b can be selected. One or more UEs from the congested / overloaded S-NSSAI 130a need to migrate to the alternative S-NSSAI 130b. The UEs in the congested / overloaded S-NSSAI 130a are associated with UE SLAs. As will be described in more detail below, the embodiments disclosed herein enable the selection of UEs to migrate from the congested slice 130a to the alternative S-NSSAI 130b.

[0043] for Figure 2b In the mobility scenario illustrated, when network 100 detects that network slice 130a (e.g., S-NSSAI #1) is unavailable in a new service area (e.g., service area 2), it can select an alternative S-NSSAI 130b (e.g., S-NSSAI #2). For UEs in S-NSSAI #1 that have moved from service area 1 to service area 2, these UEs are assigned to S-NSSAI #2. However, alternative S-NSSAI 130b (i.e., S-NSSAI #2) cannot provide service to all incoming UEs. UEs already admitted from service area 1 to S-NSSAI #1 are associated with their UE SLA. Through the Network Slice Admission Control (NSAC) mechanism, UEs can be admitted to alternative S-NSSAI 130b until the maximum allowed number of UEs is reached. However, this mechanism does not consider which UEs are admitted to alternative S-NSSAI 130b. As will be described in more detail below, the embodiments disclosed herein enable the selection of UEs to be admitted to the alternative S-NSSAI 130b in service area 2.

[0044] The embodiments disclosed herein provide a UE-priority-based Network Slice Replacement (NSR) for both non-mobility and mobility scenarios, based on stateful UE SLA assessment. The NSR procedure can be triggered for: 1) UEs in a non-mobility scenario when the current network slice 130a is congested or overloaded; 2) UEs in a mobility scenario when the current network slice 130a in the new service area cannot provide service to all incoming UEs; and 3) based on application requirements. In one embodiment, the NSR can be triggered by network 150 or AF 140. As will be described in more detail below, in one embodiment, the UE-priority-based NSR procedure disclosed herein includes the following main elements: stateful SLA assessment, wherein the UE SLA is assessed based on SLA attributes and their SLOs, the tolerance maintained by each SLO, and a specific time window for the tolerance maintained by each SLO; and a UE selection strategy, wherein UEs are prioritized based on the stateful assessment. The UE selection strategy is defined based on the prioritized UEs and the NSR scenario. For example, if a UE does not violate the SLA, it is identified as a low-priority UE; if it is about to violate the SLA, it is identified as a high-priority UE. An example of a UE selection strategy is to migrate a low-priority UE to the alternative S-NSSAI 130b in a no-mobility NSR scenario.

[0045] As described above, TENF 110b is used to determine the stateful assessment of each of the plurality of UEs 120a-n, and provides the stateful assessment of each of the plurality of UEs 120a-n as monitoring data to ENF 110a for controlling the transfer of one or more UEs of the plurality of UEs 120a from one network slice 130a to another network slice 130a. In one embodiment, TENF 110b can be used to monitor UE SLA information, including but not limited to parameters related to S-NSSAI, UE ID, UE SLA attributes, SLO, tolerance, time window, time instance, service level requested by the UE or application function 140, and service level provided by the network.

[0046] Furthermore, in one embodiment, TENF 110b can be used to monitor adaptive changes in UE SLA information (e.g., specific UE SLA information, including but not limited to data volume credit limits, maximum downlink / uplink throughput, guaranteed downlink / uplink throughput, E2E latency, QoS or QoE related parameters). Essentially, adaptive changes in UE SLA can be considered as temporary conditions or time-related events (e.g., hours, days). However, one or more UEs 120a-n may require alternative S-NSSAI 130b to implement their UE SLA changes (e.g., upgrading data plans), or S-NSSAI 130a may occur when QoS requirements are not met and congestion occurs.

[0047] As will be described in more detail below, in one embodiment, network entity 110a (e.g., ENF 110a) is used to support UE selection policies to perform implementation actions. These actions include migrating one or more UEs to another (i.e., alternative) S-NSSAI 130b, thereby admitting the UE to the alternative S-NSSAI during the NSR procedure. In one embodiment, network entity 110a (e.g., ENF 110a) may be used to determine UE priority based on stateful assessment results (i.e., monitoring data provided by TENF 110b) and apply UE selection policies to the prioritized UEs according to the NSR scenario. In one embodiment, network entity 110a (e.g., ENF 110a) may be used to provide UE rankings to a requesting network entity to initiate an NSR procedure for one or more of a plurality of UEs 120a-n.

[0048] Figure 3a and Figure 3b A signaling diagram is shown for the exchange of messages between an ENF 110a according to one embodiment, a TENF 110b according to the same embodiment, and for controlling and supporting the transfer of one or more UEs 120a-n from network slice 130a of mobile network 100 to another network slice 130b of other network entities. Figure 3b The illustrated embodiments and Figure 3a The difference in the embodiments is that ENF 110a and TENF 110b are co-located and implemented as components of NWDAF 110.

[0049] exist Figure 3a and Figure 3b In step 0, an exemplary UE 120a is registered in S-NSSAI 130a, and a PDU session is established, for example, according to the procedure defined in TS23.502.

[0050] exist Figure 3a and Figure 3bIn step 1, TENF 110b monitors the UE SLA parameters for each UE in each S-NSSAI. TENF 110b's monitoring and tracking of UE SLA-related information for UE 120a-n may have already been initiated, i.e., is in progress or will be initiated upon receiving a request from ENF 110a.

[0051] exist Figure 3a and 3b In step 2a, the network (i.e., CN NF 150) initiates an NSR event and triggers UE selection for the NSR event to ENF 110a using input parameters, including the identifiers of one or more UEs, the identifier of S-NSSAI 130a, the identifier of another network slice (i.e., Alt-S-NSSAI) 130b, and an indication of UE selection (e.g., the percentage of the total number of UEs to be selected for Alt-S-NSSAI).

[0052] exist Figure 3a and Figure 3b In step 3, in response to the NSR event trigger request received from CN NF 150, ENF110a sends a request to TENF 110b for a (stateful) SLA assessment of the UE running on network slice S-NSSAI 130a.

[0053] exist Figure 3a and Figure 3b In step 4, based on the monitored UE SLA information from step 2a and the request from step 3, TENF 110b determines the requested stateful SLA assessments for multiple UEs 120a-n (hereinafter referred to as...). Figure 10 Further details will be described in the context of this document.

[0054] exist Figure 3a and Figure 3b In step 5, TENF 110b provides ENF 110a with the requested stateful SLA assessment (i.e., monitoring data) for multiple UEs 120a-n of the indicated S-NSSAI 130a.

[0055] exist Figure 3a and Figure 3b In step 6, ENF 110a determines the selection priority of multiple UEs 120a-n based on the stateful assessment results (i.e., the monitoring data provided by TENF 110b in step 5), and applies the UE selection policy to the priority-ordered UEs 120a-n according to the UE selection indication in the NSR event request received in step 2a.

[0056] exist Figure 3a and Figure 3b In step 7, ENF 110a provides a mapping of each UE and its ranking or priority to the requesting CN NF 150 for selected UEs among the multiple UEs 120a-n of Alt-S-NSSAI 130b. If multiple Alt-S-NSSAIs are provided, multiple mappings can be provided. If the request from step 2a does not include an indication of the number of UEs to be transferred to the alternative S-NSSAI 130b, the NSR can trigger CN NF 150 to provide a mapping of all UEs 120a-n and their corresponding rankings.

[0057] exist Figure 3a and Figure 3b In step 8, for each UE to be transferred to Alt-S-NSSAI 130b, CN NF 150 performs the NSR procedure and communicates with the alternative S-NSSAI 130b UE 120a.

[0058] exist Figure 3a and Figure 3b In step 9, independent of step 7, ENF 110a notifies AF 140 of an NSR notification message for selected UEs among the multiple UEs 120a-n of Alt-S-NSSAI 130b. This message includes the identifiers of one or more UEs migrating to Alt-S-NSSAI, and one or more identifiers of one or more associated Alt-S-NSSAIs.

[0059] exist Figure 3a and Figure 3b In step 10, AF 140 confirms the NSR notification message to ENF 110a.

[0060] exist Figure 3a and Figure 3b In step 11, AF 140 monitors the SLA of the requirements (e.g., QoS) of the migrated UE or application running on Alt-S-NSSAI 130b, i.e. whether the migrated UE or application meets the SLA or QoS / QoE requirements.

[0061] exist Figure 3a and Figure 3b In step 12, AF 140 detects that the SLA or QoS / QoE is not met and determines to trigger an NSR event to restore the original S-NSSAI 130a, thereby meeting the requirements.

[0062] exist Figure 3a and Figure 3bIn step 13, AF 140 initiates an NSR event to ENF 110a using input parameters, including the identifiers of one or more UEs, the identifier of the current S-NSSAI (i.e., Alt-S-NSSAI) 130b, the identifier of another network slice (i.e., the old S-NSSAI) 130a, and an indication of the NSR event (e.g., SLA / QoS / QoE reason).

[0063] exist Figure 3a and Figure 3b In step 14, ENF 110a may execute the NSR control procedures defined in steps 3 through 8 for one or more UEs associated with the S-NSSAI received in step 13 (i.e., the current S-NSSAI). Alternatively, ENF 110a may execute a transfer of one or more UEs from the S-NSSAI (current S-NSSAI) to the Alt-S-NSSAI (old S-NSSAI). If the capacity of the Alt-S-NSSAI is limited, the ENF may perform a UE selection based on a (stateful) SLA, similar to steps 3 through 8, for the requested UE from the AF.

[0064] Figure 4a and Figure 4b A signaling diagram is shown for message exchange between multiple UEs 120a-n, according to one embodiment, ENF 110a, according to one embodiment, TENF 110b, and other network entities for controlling and supporting the transfer of one or more UEs from network slice 130a to another network slice 130b of mobile network 100. Figure 4b The illustrated embodiments and Figure 4a The difference in the embodiments is that ENF 110a is implemented as PCF 110a, while TENF 110b is implemented as NWDAF110b. Figure 4a and Figure 4b The illustrated embodiments and Figure 3a and Figure 3b The main difference in the illustrated embodiment lies in the NSR triggering condition of AF 140. Although in Figure 3a and Figure 3b In one embodiment, AF 140 triggers an NSR event to restore the original S-NSSAI of the migrated UE, but Figure 4a and Figure 4b The embodiments involve, for example, a single NSR trigger due to an SLA adjustment.

[0065] exist Figure 4a and Figure 4b In step 0, an exemplary UE 120a is registered in S-NSSAI 130a, and a PDU session is established, for example, according to the procedure defined in TS23.502.

[0066] exist Figure 4a and Figure 4b In step 1, AF 140 monitors the UE SLA parameters for each UE for each S-NSSAI for the application.

[0067] exist Figure 4a and Figure 4b In step 2, AF 140 determines that an NSR event is triggered for one or more UEs running an application on S-NSSAI, for example, due to SLA / QoS or QoE adjustments or requirements.

[0068] exist Figure 4a and Figure 4b In step 3, AF 140 triggers an NSR event to ENF 110a using input parameters, which include the identifiers of one or more UEs, the identifier of S-NSSAI 130a, the identifier of another network slice (optional) 130b, the identifier of the application, and an indication of the NSR trigger event (e.g., SLA / QoS or QoE adjustment).

[0069] exist Figure 4a and Figure 4b In step 4, ENF 110a is used to obtain alternative S-NSSAI information for the requested NSR event from step 3.

[0070] Figure 4a and Figure 4b Steps 5 to 11 of the illustrated embodiment are Figure 3a and Figure 3b Steps 3 through 9 of the illustrated embodiment are the same.

[0071] Figure 5 The embodiment illustrates another example of an NSR procedure based on UE priority. In phase 1, ENF 110a receives an NSR event from NSR triggering NF 150 (e.g., 5GC NF, such as NSSF, AMF, PCF, or NWDAF 150); or (as in...) Figure 1a and Figure 1b(As already described in the context of the illustrated embodiments) For NSR events triggered by the network, the event is received from the 5GC NF (e.g., PCF or NWDAF); for NSR events triggered by a third party (e.g., AF 140), the event is also received from the 5GC NF. In one embodiment, the trigger request may include an identifier of the replaced (i.e., current) S-NSSAI 130a, an identifier of an alternative (i.e., another) S-NSSAI 130b, an indication (e.g., in the form of an integer or percentage value) of the number of UEs to be transferred from the current S-NSSAI 130a to the alternative S-NSSAI 130b, an indication of the mobility scenario, etc.

[0072] Based on the NSR event, ENF 110a in Figure 5 Phase 2 requests stateful SLA information (i.e., monitoring data) from TENF 110b for multiple UEs 120a-n of the indicated S-NSSAI 130a.

[0073] In response to the request from ENF 110a, in Figure 5 In phase 3, TENF 110b determines state information based on the monitored UE SLA information. Figure 5 When a request from ENF 110a is received in Phase 2, the monitoring and tracking of UE SLA-related information may have already been initiated or is in progress.

[0074] exist Figure 5 In phase 4, TENF 110b provides ENF 110a with the requested stateful SLA assessment (i.e., monitoring data / information) for multiple UEs 120a-n of the indicated S-NSSAI 130a.

[0075] Based on TENF 110b Figure 5 The state assessment results provided in Phase 4 of ENF 110a Figure 5 Phase 5 determines the priority of the UE and applies the UE selection strategy to the priority-ordered UEs according to the NSR scenario to select one or more UEs from multiple UEs 120a-n to be transferred to another S-NSSAI 130b.

[0076] exist Figure 5 Stage 6, if from Figure 5 The Phase 1 request includes the number of UEs to be transferred to the alternative S-NSSAI 130b and the ranking of the UEs, then ENF 110a triggers NSR to provide the selected UEs to NF 150.

[0077] Figure 6a and Figure 6b It shows Figure 5 The embodiment includes ENF 110a, TENF 110b, and a signaling diagram for controlling and supporting the transfer of one or more UEs among multiple UEs 120a-n from network slice 130a of mobile network 100 to another network slice 130b. Figure 6b The illustrated embodiments and Figure 6a The difference in the embodiments is that ENF 110a is implemented as NWDAF 110a, while TENF 110b is implemented as NSSF 110b.

[0078] exist Figure 6a and Figure 6b In step 0.1, an exemplary UE 120a is registered in S-NSSAI 130a, and a PDU session is established, for example, according to the procedure defined in TS23.502.

[0079] exist Figure 6a and Figure 6b In step 0.2, the network (e.g., CN NF 150) detects the NSR event of S-NSSAI 130a and determines the S-NSSAI of S-NSSAI 130a. CN NF 150 determines to interact with ENF 110a to process the UE priority request from S-NSSAI 130a.

[0080] exist Figure 6a and Figure 6b In steps 1 and 1.1, for a network-triggered NSR event, ENF 110a receives the NSR event from the NF that triggered the NSR (e.g., CN NF 150 (or OAM)). As described above, the trigger request may include the identifier of the current S-NSSAI 130a, the identifier of another (i.e., alternative) S-NSSAI 130b, an indication of the number of UEs 120a-b to be transferred from the current S-NSSAI 130a to the alternative S-NSSAI 130b (e.g., in the form of an integer value or a percentage value), an indication of the mobility scenario, etc.

[0081] exist Figure 6a and Figure 6b In step 2.1, based on the NSR event, ENF 110a requests stateful SLA information (i.e., monitoring data) of multiple UEs 120a-n currently connected to S-NSSAI 130a from TENF 110b. This request may include S-NSSAI 130a and the UE ID. Additionally, this request may include the information received by ENF 110a in step 1.1.

[0082] exist Figure 6a and Figure 6bIn step 2.2, TENF 110b monitors UE SLA information, as will be described in more detail below. TENF 110b's monitoring and tracking of UE SLA-related information for UE 120a-n may have already been initiated, that is, is in progress, or will be initiated upon receiving a request from ENF 110a.

[0083] exist Figure 6a and Figure 6b In step 2.3, based on the monitored UE SLA information, TENF 110b can determine the stateful SLA assessment for multiple UEs 120a-n, as will be described in more detail below.

[0084] exist Figure 6a and Figure 6b In step 2.4, TENF 110b provides ENF 110a with the requested stateful SLA assessment (i.e., monitoring data) for multiple UEs 120a-b of the indicated S-NSSAI 130a.

[0085] exist Figure 6a and Figure 6b In step 2.5, ENF 110a determines the selection priority of multiple UEs 120a-n based on the stateful assessment results (i.e., the monitoring data provided by TENF 110b in step 2.4), and applies the UE selection strategy to the priority-ordered UEs 120a-n according to the NSR scenario, as will be described in more detail below.

[0086] exist Figure 6a and Figure 6b In step 3.1, ENF 110a provides a mapping of each UE and its ranking or priority to the requesting CN NF 150 to selected UEs among multiple UEs 120a-n. If multiple S-NSSAIs are provided, multiple mappings can be provided. If the request from step 1 does not include an indication of the number of UEs to be transferred to alternative S-NSSAI 130b, the NSR can trigger CN NF 150 to provide a mapping of all UEs 120a-n and their corresponding rankings.

[0087] exist Figure 6a and Figure 6b In step 3.2, CN NF 150 communicates with UE 120a of alternative S-NSSAI 130b.

[0088] exist Figure 6a and Figure 6b In step 3.3, UE 120a is registered with the alternative S-NSSAI 130b, and a PDU session is established, for example, according to the procedure defined in TS23.502.

[0089] Figure 7a and Figure 7b It shows Figure 5 The embodiment includes ENF 110a, TENF 110b, and a signaling diagram for message exchange to support the transfer of one or more UEs from network slice 130a to another network slice 130b of mobile network 100. Figure 7b The illustrated embodiments and Figure 7a The difference in the embodiments is that ENF 110a is implemented as NWDAF 110a, while TENF 110b is implemented as NSSF 110b.

[0090] exist Figure 7a and Figure 7b In step 1, TENF 110b receives a request for stateful SLA information for UE 120a-n for the indicated S-NSSAI 130a. This request may include S-NSSAI information and UE ID (similar to...). Figure 6a and Figure 6b Step 2.1).

[0091] exist Figure 7a and Figure 7b In step 2, TENF 110b checks if the UE ID is in the stateful SLA table. If not, TENF 110b creates an entry for the requested one or more UEs. If the UE ID has already been created in the stateful SLA table, the following steps are skipped.

[0092] exist Figure 7a and Figure 7b In step 3, TENF 110b requests UE SLA information from a network entity (e.g., AF / OAM 140).

[0093] exist Figure 7a and Figure 7b In step 4, the network entity (e.g., AF / OAM 140) provides UE SLA information. This information may include SLA parameters with SLO, associated tolerances, and time windows.

[0094] exist Figure 7a and Figure 7b In step 5, TENF 110b subscribes to the services provided by the network to UE 120a from the corresponding CN NF (e.g., SMF, AMF). The subscription request may include the UE identifier and UE SLA parameters, such as performance KPIs and reporting information (e.g., periodic or event-based reporting).

[0095] exist Figure 7a and Figure 7bIn step 6, TENF 110b receives an acknowledgment from CN NF 150.

[0096] exist Figure 7a and Figure 7b In step 7, when an event occurs, CN NF 150 notifies TENF 110b of the service level provided.

[0097] exist Figure 7a and Figure 7b In step 8, the notification of the service level provided for the corresponding UE SLA parameters and the corresponding UE identifier is updated in the stateful SLA table.

[0098] The monitored service level (SL) for each SLA parameter is used to determine the stateful SLA information of the UE, as further described below.

[0099] Figure 8a and Figure 8b It shows Figure 5 The embodiment includes the ENF 110a, TENF 110b, and a signaling diagram for message exchange to support the transfer of one or more UEs from network slice 130a to another network slice 130b of mobile network 100 (more specifically, for UE SLA adaptive adjustment monitoring and NSR event triggering). Figure 8b The illustrated embodiments and Figure 8a The difference in the embodiments is that ENF 110a is implemented as NWDAF 110a, while TENF 110b is implemented as NSSF 110b.

[0100] exist Figure 8a and Figure 8b In step 1, TENF 110b receives NSR event subscriptions from ENF. The subscription request includes S-NSSAI, UE ID, or application ID. This request may include reporting information, such as notifications of whether UE SLA adaptive adjustment has occurred. Figure 8a and Figure 8b Three types of UE SLA adaptive adjustment are shown.

[0101] For type A, in Figure 8a and Figure 8b In step A.0, based on the subscription request, TENF 110b monitors the UE SLA and determines whether to recommend negotiating the UE SLA. For example, if the UE's downlink data volume has exceeded a threshold (e.g., reached 80% of the maximum downlink data volume), or the UE's maximum downlink bit rate does not meet service requirements, then TENF 110b (i.e., AF) determines to negotiate or recommend a better UE SLA scheme. Figure 8aand Figure 8b In step A.1, TENF 110b negotiates UESLA adaptive adjustment with UE 120a. In step A.2, UE 120a accepts the negotiation or suggestion request.

[0102] For another type B, in Figure 8a and Figure 8b In step B.0, based on the subscription request, TENF 110b monitors the UE SLA related to the UE's QoS or the QoS requirements related to the indicated S-NSSAI.

[0103] For another type C, in Figure 8a and Figure 8b In step C.0, based on the subscription request, TENF 110b monitors the UE SLA related to the UE's QoE or the QoS requirements related to the application.

[0104] exist Figure 8a and Figure 8b In step 2, TENF 110b detects subscription events by monitoring UE SLA adaptive adjustments.

[0105] exist Figure 8a and Figure 8b In step 3, when the event occurs, TENF 110b notifies ENF 110a of the NSR event.

[0106] The concept of a stateful SLA is described below. According to one embodiment, a stateful SLA is generated by TENF 100b and used by ENF 110a for UE selection (i.e., the NSR procedure). In one embodiment, stateful UE SLA information indicates to network 100 how to provide the service or service level requested by the corresponding UE 120a-n compared to a stateful SLA assessment that serves as agreed-upon UE SLA information. In one embodiment, UE SLAs are assessed within a specific time period (e.g., monthly). SLA violations and assessment status are described at the end of each month. In the proposed stateful SLA assessment, UE SLA violations and assessment status are measured, monitored, and timely or proactive measures are taken to mitigate overall SLA violations, especially during NSR service operations. Based on the stateful SLA assessment results, one or more UEs 120a-n are appropriately selected to migrate or admit to alternative S-NSSAI 130b, and network 100 can improve the overall UE SLA violation situation in the NSR procedure.

[0107] In one embodiment, stateful UE SLA information is based on historical data of UE SLA information, such as required or requested SLA information associated with one or more specific time periods and the provided SLA. Based on the collected stateful UE SLA information, stateful UE SLAs can be evaluated within a specific time window (e.g., from the beginning of each calendar month to the evaluation time). The algorithm for determining stateful SLA evaluation and some examples are described below.

[0108] In addition to UE-related performance attributes and SLOs, UE SLA information can also include QoS and QoE-related information. With QoS-related UE SLA information, the UE can be evaluated based on QoS parameters and their requirements, the tolerance for maintaining each QoS requirement, and a specific time window for maintaining each QoS requirement's tolerance. With QoE-related UE SLA information, the UE is evaluated based on QoE (e.g., MOS) performance, the tolerance for maintaining QoE requirements, and a specific time window for maintaining QoE requirements' tolerance.

[0109] In one embodiment, a UE selection strategy is identified for selecting one or more UEs to perform an action. According to one embodiment, Figure 9 The table shown provides information on the UE selection strategy used to identify NSR events. Priority information indicates whether a UE is low-priority or high-priority. To determine priority, the UE's state assessment results need to be considered. For example, if a UE has not historically violated its UE SLA, it is identified as a low-priority UE; if it is likely to violate its UE SLA soon, it is identified as a high-priority UE to avoid potential UE SLA violations. Low-priority or high-priority UEs can be ranked so that a specific number of UEs can be selected sequentially to replace or admit to the alternative S_NSSAI 130b.

[0110] Using the information defined for the NSR selection policy, the NSR selection policy can be implemented. Different implementation actions can be identified based on the NSR scenario and operator requirements. Examples of implementation actions include migrating low-priority UE 120a-n to alternative S-NSSAI 130b in a no-mobility scenario, and / or admitting high-priority UE 120a-n to alternative S-NSSAI 130b in a mobility scenario.

[0111] As described above, in addition to network-triggered NSR service operations, according to the embodiments disclosed herein, NSR events can be triggered by a third-party application service provider (e.g., AF 140). For example, a third-party application provider (e.g., AF 140) can interact with network 100 regarding NSR events when one or more of the following conditions are met: adaptive adjustment of UE SLA for one or more UEs 120a-n; adaptive adjustment of QoS requirements for one or more UEs 120a-n; and / or adaptive adjustment of QoE requirements for one or more UEs 120a-n.

[0112] In one embodiment, UE 120a-n may initiate UE SLA adaptive adjustments to the application service provider within a specific time period or temporarily, as a supplement to the current UE SLA. Exemplary use cases include application-related subscription plan upgrades or downgrades, which may be associated with costs or billing. Based on requirements from UE 120a-n, for example, if the current S-NSSAI 130a of UE 120a-n cannot meet the new requirements of UE 120a-n, the application service provider may determine to trigger an NSR event. Alternatively, if the requirement for UE SLA adaptive adjustments is determined by the application service provider (e.g., based on UE behavior, energy saving, or efficiency-related decisions), the NSR event triggering may be directly initiated by AF 140.

[0113] In another embodiment, adaptive QoS demand adjustment can be initiated by the application service provider (e.g., AF 140). Exemplary use cases include adaptive QoS adjustments at the network slice level for one or more UEs or applications. Reasons for adaptive QoS adjustments may include UEs with poor radio coverage or quality at the current S-NSSAI 130a (i.e., per slice per application), or the need for dynamic and ad-hoc QoS requirements per slice per application. For example, a network slice replacement notification may be temporarily triggered to the network (5GS, 5G-A, 6G) of UE 120a-n. The granularity can be per UE, per slice, per application, or any combination thereof.

[0114] In another embodiment, QoE demand adaptive adjustment can be initiated by an application service provider (e.g., AF 140). Exemplary use cases include the service experience (QoE) of an application associated with one or more UEs in an application. Reasons for QoE adaptive adjustment may include poor radio coverage or radio quality at the current S-NSSAI 130a (i.e., per slice of each application) for UEs 120a-n. For example, a network slice replacement notification may be temporarily triggered to the UE's network (5GS, 5G-A, 6G) due to QoE demand adaptive adjustment per slice of each application.

[0115] Figure 10 A schematic diagram of a processing phase implemented by TENF 110b according to one embodiment is shown. This TENF supports the transfer of one or more UEs from network slice 130a to another network slice 130b of mobile network 100. More specifically, Figure 10 This demonstrates how TENF 110b determines the cutoff time based on the following stages. The stateful assessment results. Given the committed SLO, the requested and provided SL information, tolerances, and time windows, TENF 110b is based on... Figure 11a The algorithm shown calculates the provided stateful tolerance (PST) in Phase 1. Using the tolerance and the stateful tolerance, TENF 110b determines the priority ranking of UE 120a-b based on the ranking system in Phase 2. Using the determined priority ranking, TENF 110b calculates the overall Stateful Evaluation Result (SER) in Phase 3, which can be provided to ENF 110a as monitoring data.

[0116] In one embodiment, a two-dimensional ranking system can be used. Figure 10 Phase 2 determines the priority ranking of UEs, where the first dimension (i.e., dimension 1) is based on whether the PST is violated, and the second dimension (i.e., dimension 2) is based on the type of UE attributes. In the first step, TENF 110b can determine the ranking based on the first dimension (the provided state tolerance). To this end, in one embodiment, TENF 110b can implement Figure 11b The algorithm is shown. In the second step, TENF 110b can determine the ranking based on the second dimension (attribute type). The ranking can be recorded based on the type of the UE attribute. Figure 12a The table shown illustrates an example of attribute ranking.

[0117] In Phase 3 (i.e., calculating the overall Stateful Evaluation Result (SER) for the UE), for a given UE ID and its attributes, its ranking along the first and second dimensions is known from Phase 2. According to one embodiment, the SER can be calculated by the TENF 110b in two steps. In the first step, the TENF 110b can calculate the SER for each attribute of each UE. In the second step, TENF 110b can calculate the SER for each UE as: SER of attribute 1 + SER of attribute 2 + ...

[0118] In this embodiment, the UE with the highest SER has the highest priority.

[0119] The following describes a simple example of calculating the overall SER using TENF 110b.

[0120] Phase 1: Calculate the provided stateful tolerance (PST) In this example, three attributes of the UE are considered: 1) CS availability; 2) PDB; 3) throughput. According to Algorithm 1 (e.g.) Figure 11a As shown), consider UE#1 and the attribute "CS availability" and arbitrary timestamps. = 10 / 06 / 2020 16:20:51.

[0121] 1.

[0122] 2.

[0123] 3. Deadline PST In this example, PST is within tolerance limits. Within the range, such as Figure 12b The table shown is shown below.

[0124] Phase 2: Determine Priority Ranking Step 1: Determine the ranking based on Dimension 1 (the provided stateful tolerance). The tolerance threshold is... .

[0125] Step 2: Determine the ranking based on dimension 2 (attribute type).

[0126] Attribute ranking strategy along dimension 1, such as Figure 12c The table below shows the attribute ranking strategy along dimension 2. Figure 12d As shown in the table below. Therefore, combined with Figure 12c and Figure 12d The table and application Figure 11b Algorithm 2 is shown, and the priority ranking of UE#1 in the current example is as follows: Figure 12e The table is shown below.

[0127] Phase 3: Calculate the overall Stateful Evaluation Result (SER) for the UE. Based on the steps described above for Phase 3, the SER for each attribute of each UE and the calculation of the SER for each UE are as follows: Figure 12f As shown in the table. The SER for each UE is calculated against all other UEs, and the UE with the highest SER has the highest priority.

[0128] Figure 13A flowchart is shown of a method 1300 for operating a network entity 110a (specifically ENF 110a) to control the transfer of one or more UEs among a plurality of UEs 120a-n from network slice 130a of mobile network 100 to another network slice 130b. Method 1300 includes step 1301: the network entity 110a (specifically ENF 110a) sends a Network Slice Replacement (NSR) notification message to an application function (AF) 140 associated with an application running on the plurality of UEs 120a-n. As described above, the NSR notification message includes a corresponding identifier for one or more UEs among the plurality of UEs 120a-n, an identifier for network slice 130a, and / or an identifier for another network slice 130b.

[0129] Method 1300 can be performed by network entity 110a (especially ENF 110a). Therefore, other features of method 1300 come from the functionality of network entity 110a (especially ENF 110a), as well as the different implementations and embodiments described above and below.

[0130] Figure 14 A flowchart is shown of a method 1400 for operating another network entity 110b (specifically TENF 110b) to support the transfer of one or more UEs among a plurality of UEs 120a-n from network slice 130a to another network slice 130b controlled by network entity 110a (specifically ENF 110a) of mobile network 100. Method 1400 includes step 1401: determining a stateful assessment for each of the plurality of UEs 120a-n. Furthermore, method 1400 includes step 1403: sending the stateful assessment for each of the plurality of UEs 120a-n as monitoring data to network entity 110a (specifically ENF 110a), which controls the transfer of one or more UEs among the plurality of UEs 120a-n from network slice 130a to another network slice 130b.

[0131] Method 1400 can be performed by another network entity 110b (especially TENF 110b). Therefore, other features of method 1400 come from the functionality of another network entity 110b (especially TENF 110b), as well as the different implementations and embodiments described above and below.

[0132] Those skilled in the art will understand that “blocks” (“units”) in the various drawings (methods and apparatuses) represent or describe the functionality of embodiments of the invention (and are not necessarily independent “units” in hardware or software), thereby equally describing the functionality or features (unit = step) of apparatus embodiments and method embodiments.

[0133] In the various embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the described embodiments of the apparatus are merely exemplary. For example, the unit division is only a logical functional division, and other division methods may be used in actual implementation. For example, multiple units or components may be merged or integrated into another system, or some features may be ignored or not performed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be implemented by using some interface. Indirect coupling or communication connection between devices or units can be implemented electronically, mechanically, or otherwise.

[0134] The units described as individual components may or may not be physically separate; the components shown as units may or may not be physical units, and may be located in the same location or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiment according to actual needs.

[0135] In addition, the functional units in the embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

Claims

1. A network entity (110a; 110), characterized by, For controlling a transfer of one or more of a plurality of user equipments, UEs, (120a-n) from a network slice (130a) to another network slice (130b) of a mobile network (100), the network entity (110a; 110) is configured to: send a notification message to an application function, AF, (140) for transferring one or more of a plurality of UEs (120a-n) from a network slice (130a) to another network slice (130b), wherein the notification message comprises respective identifiers of the one or more of the plurality of UEs (120a-n), an identifier of the network slice (130a), and / or an identifier of the another network slice (130b).

2. The network entity (110a; 110) according to claim 1, characterized by The network entity (110a; 110) is configured to receive, from the AF (140), a request for transferring one or more of a plurality of UEs (120a-n) from the network slice (130a) to the another network slice (130b) of the mobile network (100), wherein the request comprises respective identifiers of the one or more UEs to be transferred to the another network slice (130b), an identifier of the network slice (130a), an identifier of the another network slice (130b), identifiers of applications running on the plurality of UEs (120a-n) and being associated with the AF (140), and / or an indication of a network slice replacement of the one or more UEs from the network slice (130a).

3. The network entity (110a; 110) according to claim 2, characterized by In response to receiving the request from the AF (140), the network entity (110a; 110) is configured to select the one or more of the plurality of UEs (120a-n) and to trigger the transfer of the one or more of the plurality of UEs (120a-n) from the network slice (130a) to the another network slice (130b) of the mobile network (100).

4. The network entity (110a; 110) according to claim 2, characterized by The network entity (110a; 110) is configured to receive the request from the AF (140) in response to sending the notification message to the AF (140).

5. The network entity (110a; 110) according to claim 4, characterized by In response to receiving the request from the AF (140), the network entity (110a; 110) is configured to trigger the transfer of the one or more of the plurality of UEs (120a-n) from the another network slice (130b) to the network slice (130a) of the mobile network (100).

6. The network entity (110a; 110) according to claim 1, characterized by The network entity (110a; 110) is configured to receive, from a network function (150) of the mobile network (100), a request for transferring one or more of a plurality of UEs (120a-n) from a network slice (130a) to another network slice (130b) of the mobile network (100), wherein the request comprises an identifier of the network slice (130a) and / or an identifier of the another network slice (130b).

7. The network entity (110a; 110) according to claim 6, characterized by In response to receiving the request from the network function (150) of the mobile network (100), the network entity (110a; 110) is configured to select the one or more of the plurality of UEs (120a-n) and to trigger the transfer of the one or more selected UEs of the plurality of UEs (120a-n) from the network slice (130a) to the further network slice (130b) of the mobile network (100).

8. The network entity (110a; 110) according to claim 7, characterized by Each of the plurality of UEs (120a-n) is associated with a service level agreement, SLA, wherein each SLA defines one or more service level objects, SLOs, for one or more SLA attributes of the SLA, and wherein the network entity (110a; 110) is configured to determine or obtain, from a further network entity (110b), monitoring data for each of the plurality of UEs (120a-n) and to select the one or more of the plurality of UEs (120a-n) based on the monitoring data for each of the plurality of UEs (120a-n).

9. The network entity (110a; 110) according to claim 8, characterized by The network entity (110a; 110) is configured to select the one or more of the plurality of UEs (120a-n) based on the monitoring data for each of the plurality of UEs (120a-n), wherein the monitoring data relates to a status of the SLA or SLA fulfillment for each of the plurality of UEs (120a-n).

10. The network entity (110a; 110) according to claim 9, characterized by The monitoring data determined or obtained by the network entity (110) or from the further network entity (110b) comprises a stateful evaluation of each of the plurality of UEs (120a-n).

11. The network entity (110a; 110) according to any one of the preceding claims, characterized by The mobile network (100) is a 3GPP network (100), and wherein the network entity (110a; 100) is a policy control function (110a; 110) or a network data analytics function of the mobile network (100).

12. A further network entity (110b) characterized by For supporting a transfer of one or more of a plurality of user equipment, UEs (120a-n), from a network slice (130a) to a further network slice (130b) controlled by a network entity (110a) of a mobile network (100), wherein the further network entity (110b) is configured to determine a stateful evaluation of each of the plurality of UEs (120a-n) and to send the stateful evaluation of each of the plurality of UEs (120a-n) as monitoring data to the network entity (110a).

13. The further network entity (110b) according to claim 12, characterized by The further network entity (110b) is configured to determine the stateful evaluation of each of the plurality of UEs (120a-n) based on one or more service level agreement, SLA, attributes related to each of the plurality of UEs (120a-n), one or more associated service level objectives, SLOs, for each SLA attribute, one or more tolerances maintained for each SLO, and / or a specific time window associated with the tolerances maintained for each SLO.

14. A method (1300) for operating a network entity (110a; 110), characterized in that, The network entity is configured to control a transfer of one or more of a plurality of user equipments, UEs (120a-n), from a network slice (130a) to another network slice (130b) of a mobile network (100), wherein the method (1300) comprises: sending (1301) a notification message to an application function, AF (140) for transferring one or more of a plurality of UEs (120a-n) from a network slice (130a) to another network slice (130b), wherein the notification message comprises respective identifiers of the one or more of the plurality of UEs (120a-n), an identifier of the network slice (130a) and / or an identifier of the another network slice (130b).

15. A method (1400) for operating another network entity (110b), characterized by The further network entity is configured to support a transfer of one or more of a plurality of user equipments, UEs (120a-n), from a network slice (130a) to another network slice (130b) controlled by a network entity (110a) of a mobile network (100), wherein the method (1400) comprises: determining (1401) a stateful assessment for each of the plurality of UEs (120a-n); sending (1403) the stateful assessment for each of the plurality of UEs (120a-n) as monitoring data to the network entity (110a).

Images