WO2025201652A1 - Entités de réseau et procédés de commande d'un transfert d'ue entre tranches de réseau - Google Patents

Entités de réseau et procédés de commande d'un transfert d'ue entre tranches de réseau

Info

Publication number
WO2025201652A1
WO2025201652A1 PCT/EP2024/058575 EP2024058575W WO2025201652A1 WO 2025201652 A1 WO2025201652 A1 WO 2025201652A1 EP 2024058575 W EP2024058575 W EP 2024058575W WO 2025201652 A1 WO2025201652 A1 WO 2025201652A1
Authority
WO
WIPO (PCT)
Prior art keywords
ues
network
network slice
network entity
sla
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/EP2024/058575
Other languages
English (en)
Inventor
Wint Yi POE
Sayantini MAJUMDAR
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to PCT/EP2024/058575 priority Critical patent/WO2025201652A1/fr
Publication of WO2025201652A1 publication Critical patent/WO2025201652A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/13—Cell handover without a predetermined boundary, e.g. virtual cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/22—Performing reselection for specific purposes for handling the traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment
    • H04W36/385—Reselection control by fixed network equipment of the core network

Definitions

  • the present disclosure relates to wireless communications. More specifically, the present disclosure relates to network entities and methods for controlling and supporting a transfer of selected user equipments, UEs, from a network slice to a further network slice of a mobile network, in particular a 3GPP mobile network.
  • the 3GPP specification TS23.501 defines how the network detects and triggers NSR procedure by CN entities.
  • an Access and Mobility Management Function AMF detects an S-NSSAI becoming unavailable or congested together with other CN NFs, such as a Network Slice Selection Function (NSSF), Policy Control Function (PCF) and/or Operation and Management (OAM).
  • NSF Network Slice Selection Function
  • PCF Policy Control Function
  • OAM Operation and Management
  • NSSAI Network Slice Area of Service
  • NWDAF Network Data Analytics Function
  • the identified mechanisms consider that the network can detect which S-NSSAI (or UEs) is congested and can select an alternative S-NSSAI to initiate the NSR procedure.
  • the NSR being triggered by other entities, e.g., Application Function (AF).
  • AF Application Function
  • an NSR trigger may be initiated by AF to the network when a UE or group of UEs changes UE SLA temporarily, e.g., UE asks for a specific service (e.g., a higher throughput) when it needs for a specific application for a specific time period with the associated higher cost.
  • the application provider e.g., AF
  • Network triggered NSR does not allow other conditions requiring NSR events by other entities, for example, when the UE or UEs needs a temporary change of SLA with an Application provider (e.g., AF) due to its requirements.
  • an Application provider e.g., AF
  • the application provider detects that the requirements of UE or UEs (e.g., QoS or QoE) are not being fulfilled, hence, it triggers the NSR event for the specific UE or UEs.
  • the network may increase overall UE satisfaction and can improve the efficient use of available resources.
  • a 3GPP mobile network such as a 5G or 6G network.
  • 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 of the SLA, and wherein the network entity is configured to determine or to obtain from a further network entity, in particular Tracking and Evaluation Network Function, TENF, for each of the plurality of UEs monitoring data, i.e. stateful information of each of the plurality of UEs and to select, i.e. prioritize the one or more UEs of the plurality of UEs based on the monitoring data of each of the plurality of UEs.
  • TENF Tracking and Evaluation Network Function
  • the method according to the third aspect comprises: sending a Network Slice Replacement, NSR, notification message to an application function, AF, associated with an application running on the plurality of UEs, wherein the NSR notification message comprises a respective identifier of the one or more UEs, an identifier of the network slice, and/or an identifier of the further network slice.
  • NSR Network Slice Replacement
  • Figs. 6a and 6b show signalling diagrams illustrating the exchange of messages between a network entity and a further network entity according to the embodiment of figure 5 for controlling and supporting a transfer of one or more UEs from a network slice to a further network slice of the mobile network;
  • Figs. 7a and 7b show signalling diagrams illustrating the exchange of messages between a network entity and a further network entity according to the embodiment of figure 5 for controlling and supporting a transfer of one or more UEs from a network slice to a further network slice of the mobile network;
  • Figs. 8a and 8b show signalling diagrams illustrating the exchange of messages between a network entity and a further network entity according to the embodiment of figure 5 for controlling and supporting a transfer of one or more UEs from a network slice to a further network slice of the mobile network;
  • Fig. 9 shows a table illustrating information used by a network entity according to an embodiment for implementing a UE selection policy for a transfer of one or more UEs from a network slice to a further network slice of the mobile network;
  • Figs. 12a-f show tables illustrating exemplary values determined by a network entity according to an embodiment for controlling a transfer of one or more UEs from a network slice to a further network slice of a mobile network;
  • Fig. 14 is a flow diagram illustrating a method for operating a further network entity according to an embodiment for supporting a transfer of one or more UEs from a network slice to a further network slice of a mobile network.
  • a disclosure in connection with a described method may also hold true for a corresponding device or system configured to perform the method and vice versa.
  • a corresponding device may include one or a plurality of units, e.g. functional units, to perform the described one or plurality of method steps (e.g. one unit performing the one or plurality of steps, or a plurality of units each performing one or more of the plurality of steps), even if such one or more units are not explicitly described or illustrated in the figures.
  • a specific apparatus is described based on one or a plurality of units, e.g.
  • a corresponding method may include one step to perform the functionality of the one or plurality of units (e.g. one step performing the functionality of the one or plurality of units, or a plurality of steps each performing the functionality of one or more of the plurality of units), even if such one or plurality of steps are not explicitly described or illustrated in the figures. Further, it is understood that the features of the various exemplary embodiments and/or aspects described herein may be combined with each other, unless specifically noted otherwise.
  • Figure la shows a schematic diagram illustrating a portion of a mobile network 100, in particular a 3GPP mobile network 100, such as a 5G or 6G network. More specifically, figure la shows network function entities of a core network, CN, of a mobile network 100, which may further comprise a radio access network, RAN. As illustrated in figures 2a and 2b, the RAN of the mobile network 100 may comprise a plurality of base stations or access points 115a,b configured to provide communication access to a plurality of user equipments, UEs, 120a-n.
  • the CN of the mobile network 100 illustrated in figure la comprises a network entity 110a, in particular an Enforcement Network Function, ENF, 110a configured to control a transfer of one or more UEs of a plurality of UEs 120a-n from a network slice, S-NSSAI, 130a (illustrated in figures 2a and 2b) to a further network slice, Alt- S-NSSAI, 130b of the mobile network 100.
  • the network entity 110a, in particular ENF 110a is configured 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.
  • NSR Network Slice Replacement
  • the CN of the mobile network 100 illustrated in figure 1 a comprises a further network entity 110b, in particular a Tracking and Evaluation Network Function, TENF 110b configured to support the transfer of the one or more UEs of the plurality of UEs 120a-n from the network slice 130a to the further network slice 130b controlled by the network entity 110a, e.g. the ENF 110a.
  • a further network entity 110b in particular a Tracking and Evaluation Network Function, TENF 110b configured to support the transfer of the one or more UEs of the plurality of UEs 120a-n from the network slice 130a to the further network slice 130b controlled by the network entity 110a, e.g. the ENF 110a.
  • the further network entity 110b in particular TENF 110b is configured to determine a stateful evaluation of each UE of the plurality of UEs 120a-n and to provide the stateful evaluation of each UE of the plurality of UEs 120a-n as monitoring data to the network entity 110a, in particular ENF 110a for controlling the transfer of the one or more UEs of the plurality of UEs 120a-n from the network slice 130a to the further network slice 130a.
  • the network entity 110a, in particular ENF 110a, and the further network entity 110b, in particular TENF 110b may be components of a single network entity function 110.
  • Figure lb shows different processes and interactions between core network entities and AF for controlling and supporting a transfer of one or more UEs of the plurality of UEs 120a-n from the network slice 130a to the further network slice 130b of the mobile network 100.
  • the ENF 110a interacts with the TENF 110b for a stateful SLA based UE selection (step Ob) and supports NSR enforcement, i.e., determines the transfer of one or more UEs of the plurality of UEs 120a-n from the network slice 130a to the further network slice 130b (step 0c).
  • the change of the association of the one or more UEs from the network slice 130a to the further network slice 130b is notified to the AF 140 (step la). If the requirement of QoS, QoE or SLA of the one or more UEs associated with the further network slice 130b is not fulfilled or the adjustment of QoS, QoE or SLA of one or more UEs associated with the network slice 130a is required, the AF 140 may trigger a request to the ENF 110a for controlling the transfer of the one or more UEs associated with the further network slice 130b back to the (original) network slice 130a or the UEs of the plurality of UEs 120a-n from the network slice 130a to the further network slice 130b (step lb).
  • 5G The fifth-generation technology standard for mobile network
  • UE SLA includes a service (e.g., V2X service) requirements and promised SLO for the performance KPIs (SLO of guaranteed downlink throughput, guaranteed uplink throughput and service availability associated with tolerance and time window).
  • the tolerances of each SLO upholding can be defined as the percentage value with respect to the time window. For example, 1% of tolerance of service availability for the time window 30 days means that the maximum service unavailability is acceptable for 1% of 30 days (i.e., 7.2 hours) within 30 days.
  • “stateful SLA” means that a UE SLA may be evaluated based on the SLA attribute and its service level objectives (SLO), the tolerances of each SLO upholding and a specific time windows for the tolerance of each SLO upholding.
  • SLO service level objectives
  • Embodiments disclosed herein are based on a Stateful SLA Evaluation for determining the proper UE(s) selection by the network entity 110a, in particular ENF 110a during the NSR procedure.
  • each UE is evaluated and selected.
  • the plurality of UEs 120a-n are prioritized based on its stateful SLA evaluation or stateful information.
  • a UE selection policy is defined based on the prioritized UEs and an NSR scenario.
  • the UE selection policy defines the rules for the UE(s) 120a-n to be continued in the current S-NSSAI 130a and the rules for UEs 120a- n to be migrated to the Alternative S-NSSAI 130b.
  • UEs may be identified as low priority UEs, if the respective UE has no SLA breach, and UEs may be identified as high priority UEs, if the SLA is breached soon based on stateful SLA evaluation.
  • the UE selection policy may be to migrate low priority UEs to the Alternative S-NSSAI 130b in no mobility NSR scenario. In the mobility scenario, the UE selection policy may be to migrate high priority UEs to the Alternative S-NSSAI 130b.
  • the UEs can be admitted to the Alternative S-NSSAI 130b up to maximum number of allowed UEs.
  • this mechanism does not consider which UEs are admitted to the Alternative S-NSSAI 130b.
  • embodiments disclosed herein allow to select UEs to be admitted to the alternative S-NSSAI 130b in Service Area 2.
  • Embodiments disclosed herein provide a UE priority-based Network Slice Replacement (NSR) based on stateful UE SLA evaluation, for both no mobility and mobility scenarios.
  • the NSR procedure may be triggered: 1) for UEs in the no mobility scenario when the current network slice 130a is congested or overloaded; 2) for UEs in the mobility scenario, when the current network slice 130a in the new service area is unavailable to serve all incoming UEs; and 3) based on the application’s requirement.
  • the NSR may be triggered either by the network 150 or the AF 140.
  • the TENF 110b is configured to determine a stateful evaluation of each UE of the plurality of UEs 120a-n and to provide the stateful evaluation of each UE of the plurality of UEs 120a-n as monitoring data to the ENF 110a for controlling the transfer of the one or more UEs of the plurality of UEs 120a-n from the network slice 130a to the further network slice 130a.
  • the TENF 110b may be configured to monitor UE SLA information including but not limited to the parameter related to S-NSSAI, UE ID, UE SLA Attribute, SLO, Tolerance, Time window, Time instance, and Requested Service Level by UE or application function 140 and provided service level by the network.
  • the TENF 110b may be configured to monitor adaptive changes of the UE SLA information, for example, specific UE SLA information including but not limited to data volume credit limit, max. downlink/uplink throughput, guaranteed downlink/uplink throughput, E2E delay, QoS or QoE related parameters.
  • the adaptive changes of the UE SLA may be considered as temporary conditions or time (e.g., hours, days).
  • the UE(s) 120a-n may require the alternative S-NSSAI 130b to fulfil its UE SLA change, e.g., upgrading data plan or QoS requirements does not fulfil with the congested S-NSSAI 130a.
  • step 0 of figures 3a and 3b the exemplary UE 120a is registered in the S-NSSAI 130a and a PDU session is established, for instance, according to the procedure defined in TS23.502.
  • the TENF 110b monitors the UE SLA parameters per UE per S-NSSAI.
  • the monitoring and tracking of UE SLA related information for the UEs 120a-n by the TENF 110b may already have been initiated, i.e. ongoing or will be initiated when the request from ENF 110a is received.
  • step 3 of figures 3a and 3b in response to the received NSR event triggering request from CN NF 150, the ENF 110a sends a request to the TENF 110b for the (stateful) SLA evaluation of UEs running on the network slice S-NSSAI 130a.
  • step 4 of figures 3a and 3b based on the monitored UE SLA information from step 2a and the request from step 3, the TENF 110b determines the requested stateful SLA evaluation of the plurality of UEs 120a-n (further details are described below in the context of Figure 10).
  • the TENF 110b provides the requested stateful SLA evaluation, i.e. monitoring data of the plurality of UEs 120a-n of the indicated S-NSSAI 130a to the ENF 110a.
  • the ENF 110a determines the selection priority of the plurality of UEs 120a-n based on the stateful evaluation results, i.e. the monitoring data provided by TENF 110b in step 5 and applies a UE selection policy to the prioritized UEs 120a-n according to the indication of UE selection in NSR event request received in step 2a.
  • the ENF 110a provides the selected UEs of the plurality of UEs 120a-n for the Alt-S-NSSAI 130b with the mapping of each UE with its ranking or priority to the requesting CN NF 150. If multiple Alt-S-NSSAIs are provided, multiple mappings may 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 mapping of all UEs 120a-n with their corresponding ranking may be provided to the NSR triggering CN NF 150.
  • step 10 of figures 3a and 3b the AF 140 acknowledges the NSR notification message to the ENF 110a.
  • the AF 140 monitors the SLA of the migrated UEs or application requirements (e.g., QoS) running on the Alt-S-NSSAI 130b, i.e. whether the migrated UEs or the application is fulfilling SLA or QoS/QoE requirements.
  • application requirements e.g., QoS
  • the AF 140 initiates an NSR event to the ENF 110a with the input parameters including identifications of one or more UEs, the identification of current S-NSSAI (i.e., Alt-S-NSSAI) 130b, the identification of further network slice (i.e., old S-NSSAI) 130a and the indication of NSR event (e.g., SLA/QoS/QoE reason).
  • the ENF 110a may perform the NSR control procedure as defined in steps 3-8 for the one or more UEs associated with the S-NSSAI (i.e., current S-NSSAI) received in step 13.
  • Figures 4a and 4b show signalling diagrams illustrating the exchange of messages between the ENF 110a according to an embodiment, the TENF 110b according to an embodiment as well as further network entities for controlling and supporting a transfer of one or more UEs of the plurality of UEs 120a-n from the network slice 130a to the further network slice 130b of the mobile network 100.
  • the embodiment shown in figure 4b differs from the embodiment of figure 4a in that the ENF 110a is implemented as a PCF 110a and the TENF 110b is implemented as a NWDAF 110b.
  • the embodiments shown in figures 4a and 4b differ from the embodiments shown in figures 3a and 3b primarily in the NSR triggering condition by the AF 140.
  • step 0 of figures 4a and 4b the exemplary UE 120a is registered in the S-NSSAI 130a and a PDU session is established, for instance, according to the procedure defined in TS23.502.
  • step 1 of figures 4a and 4b the AF 140 monitors the UE SLA parameters per UE per S-NSSAI for the application.
  • the AF 140 determines to trigger NSR event for one or more of UEs running application on the S-NSSAI, e.g., due to SLA/QoS or QoE adjustment or requirements.
  • the AF 140 triggers NSR event to the ENF 110a with the input parameters including identifications of one or more UEs, the identification of S-NSSAI 130a, the identification of further network slice (optional) 130b, the identification of the application and the indication of NSR trigger event (e.g., SLA/QoS or QoE adjustment).
  • the input parameters including identifications of one or more UEs, the identification of S-NSSAI 130a, the identification of further network slice (optional) 130b, the identification of the application and the indication of NSR trigger event (e.g., SLA/QoS or QoE adjustment).
  • step 4 of figures 4a and 4b the ENF 110a is configured to obtain the alternative S-NSSAI information for the requested NSR event from step 3.
  • Steps 5 to 11 of the embodiments shown in figures 4a and 4b are identical to steps 3 to 9 of the embodiments shown in figures 3a and 3b.
  • the ENF 110a receives an NSR event from the NSR triggering NF 150, e.g., a 5GC NF, such as a NSSF, AMF, PCF, or NWDAF 150, or (as alreadv described in the context of the embodiment shown in figures la and lb) for the network triggering NSR event and from a 5GC NF, such as a PCF or NWDAF, for the 3 rd party (e.g., AF 140) triggering NSR event.
  • the triggering request may include an identifier of the replaced, i.e.
  • the ENF 110a in stage 5 of figure 5 determines the priority of UEs and applies UE selection policy to the prioritized UE according to the NSR scenario for selecting the one or more UEs of the plurality of UEs 120a-n to be transferred to the further S-NSSAI 130b.
  • the ENF 110a provides the selected UEs if the request from stage 1 of figure 5 includes the number of UEs to be transferred to the alternative S-NSSAI 130b together with the ranking of UEs to the NSR triggering NF 150.
  • the network e.g. a CN NF 150, detects an NSR event of the S-NSSAI 130a and determines the S-NSSAI of the S-NSSAI 130a.
  • the CN NF 150 determines to interact with the ENF 110a for UE prioritization request of UEs from the S-NSSAI 130a.
  • the ENF 110a receives the NSR event from the NSR triggering NF, e.g., CN NF 150 (or the OAM) for the network triggering NSR event.
  • the triggering request may include an identifier of the current S-NSSAI 130a, an identifier of the further, i.e. alternative S-NSSAI 130b, an indication of the number of UEs 120a-b of the current S-NSSAI 130a to be transferred to the alternative S-NSSAI 130b (e.g., in the form of a integer value or percentage value), an indication of mobility scenario, and the like.
  • the ENF 110a requests the stateful SLA information, i.e. the monitoring data of the plurality of UEs 120a-n of the current S-NSSAI 130a from the TENF 110b.
  • the request may include the S-NSSAI 130a and UE IDs.
  • the request may include the information received by the ENF 110a in step 1.1.
  • the TENF 110b monitors the UE SLA information, as will be described in more detail further below.
  • the monitoring and tracking of UE SLA related information for the UEs 120a-n by the TENF 110b may already have been initiated, i.e. ongoing or will be initiated when the request from ENF 110a is received.
  • the ENF 110a provides the selected UEs of the plurality of UEs 120a-n with the mapping of each UE with its ranking or priority to the requesting CN NF 150. If multiple S-NSSAIs are provided, multiple mappings may be provided. If the request from step 1 does not include an indication of the number of UEs to be transferred to the alternative S-NSSAI 130b, the mapping of all UEs 120a-n with their corresponding ranking may be provided to the NSR triggering CN NF 150.
  • the TENF 110b receives a request for the stateful SLA information of the UEs 120a-n of the indicated S-NSSAI 130a.
  • the request may include the S-NSSAI information and the UE IDs (similar to step 2.1 of figures 6a and 6b).
  • the TENF 110b checks that the UE IDs are in the stateful SLA table. If not, the TENF 110b creates an entry for the requested UE(s). The following steps are skipped, if the UE IDs are already created in the stateful SLA table.
  • the TENF 110b requests UE SLA information from the network entity, e.g., AF/OAM 140.
  • the TENF 110b receives the acknowledgement from the CNNFs 150.
  • step 7 of figures 7a and 7b when the event occurs, the CN NFs 150 notify the provided service level to the TENF 110b.
  • step 8 of figures 7a and 7b the notifications of the provided service level for the corresponding UE SLA parameter and corresponding UE identification is updated to the stateful SLA table.
  • the monitored provided service level (SL) of each SLA parameter is used to determine the stateful SLA information of UE as described further below.
  • Figures 8a and 8b show signalling diagrams illustrating the exchange of messages between the ENF 110a and the TENF 110b as well as further network entities for the embodiment of figure 5 for supporting the transfer of one or more UEs of the plurality of UE 120a-n from the network slice 130a to the further network slice 130b of the mobile network 100, more specifically for UE SLA adaptation monitoring and NSR event triggering.
  • the embodiment shown in figure 8b differs from the embodiment of figure 8a in that the ENF 110a is implemented as a NWDAF 110a and the TENF 110b is implemented as a NSSF 110b.
  • the TENF 110b monitors the UE SLA and determines if the negotiation of UE SLA is recommended. For example, UE’s downlink data volume has crossed a threshold (e.g., 80% of the maximum downlink data volume has been reached) or UE’s maximum downlink bit rate is not fulfilling the service’s requirement, the TENF 110b (i.e., AF) determines to negotiate or recommend using a better UE SLA scheme.
  • the TENF 110b negotiates the UE SLA adaptation with the UE 120a.
  • the UE 120a accepts the negotiation or recommended request.
  • step B.O of figures 8a and 8b based on the subscription request, the TENF 110b monitors the UE SLA related to the QoS of UEs or QoS requirement related to the indicated S-NSSAI.
  • the TENF 110b detects the subscribed event by monitoring the UE SLA adaptation.
  • step 3 of figures 8a and 8b when the event occurs, the TENF 110b notifies the NSR event to the ENF 110a.
  • stateful SLA information indicates how the services or service level requested by a respective UE 120a-n is provided by the network 100 in comparison with the stateful SLA evaluation as agreed UE SLA information.
  • the UE SLA is evaluated over a specific time periodic, e.g., monthly basis. The SLA violation and evaluation is justified by the end of each month.
  • UE SLA violation and evaluation is measured, monitored and actions are taken to avoid overall SLA violation in timely manner or in advanced, in particular, for NSR service operation procedures.
  • the UE(s) 120a-n to be migrated or to be admitted to the alternative S-NSSAI 130b are selected properly and the network 100 may improve overall UE SLA violation in NSR procedure.
  • the UE SLA information may include QoS and QoE related information.
  • QoS related UE SLA information a respective UE may be evaluated based on the QoS parameters and its requirements, the tolerances of each QoS requirement upholding and a specific time windows for the tolerance of each QoS requirement upholding.
  • QoE related UE SLA information UE is evaluated based on the QoE (e.g., MOS) performance, the tolerances of QoE requirement upholding and a specific time window for the tolerance of QoE requirement upholding.
  • a UE selection policy is identified for selecting UE/UEs to perform the enforcement actions.
  • information to identify the UE selection policy for an NSR event is provided in the table shown in figure 9.
  • the priority information indicates low or high priority UEs.
  • UE stateful evaluation results are considered. For example, a UE is identified as a low priority UE, if UE has no UE SLA breach in history, and a UE is identified as a high priority UE, if UE SLA is breached soon in order to avoid potential UE SLA violation.
  • Low or high priority UEs may be ranked so that the specific amount of UEs to be replaced or to be admitted to Alternative S_NSSAI 130b may be selected in order.
  • the NSR selection policy may be enforced. Different enforcement actions may be identified based on the NSR scenario and operator’s requirements. Examples of enforcement actions include migration of low priority UEs 120a-n to the alternative S-NSSAI 130b in the no mobility scenario and/or admission of high priority UEs 120a-n to the alternative S-NSSAI 130b in the mobility scenario.
  • the UE SLA adaptation may be initiated by the UE 120a-n to the application service provider for a specific period time or temporarily in addition to the current UE SLA.
  • Exemplary use cases include Application related subscription plan upgrade or downgrade which might be associated with cost or charging.
  • the application service provider may determine to trigger an NSR event, e.g., if the current S-NSSAI 130a of the UE/UEs 120a- n cannot fulfil the new requirement of the UE/UEs 120a-n.
  • an NSR event trigger may be initiated directly by the AF 140, if the requirement of UE SLA adaptation is decided by the Application service provider, e.g., based on UE behavior, energy saving or efficiency related decision.
  • the QoS requirement adaptation may be initiated by the application service provider, e.g., the AF 140.
  • Exemplary use cases include QoS adaptation for UE/UEs or Applications with a granularity of Network Slice level.
  • the cause of QoS adaptation may include poor radio coverage or radio quality UEs at the current S-NSSAI 130a (i.e., per Slice per App) or the need of dynamic and temporary QoS requirements per Slice per Application.
  • a Network Slice Replacement notification may be triggered to the network (5GS, 5G-A, 6G) for UEs 120a-n, e.g., temporarily.
  • the granularity can be per UE or per Slice or per Application or any combination.
  • the QoE requirement adaptation may initiated by the application service provider, e.g., the AF 140.
  • Exemplary use cases include service Experience (QoE) for an Application related to UE/UEs in an Application.
  • QoE adaptation may include poor radio coverage or radio quality UEs 120a-n at the current S-NSSAI 130a (i.e., per Slice per App).
  • a Network Slice Replacement notification due to QoE requirement adaptation per slice per application may be triggered to the network (5GS, 5G-A, 6G) for UEs, e.g., temporarily.
  • Figure 10 shows a schematic diagram illustrating processing stages implemented by the TENF 110b according to an embodiment for supporting the transfer of one or more UEs of the plurality of UEs 120a-n from the network slice 130a to the further network slice 130b of the mobile network 100. More specifically, figure 10 illustrates how the TENF 110b may determine a Stateful Evaluation Result until time instant t based on the following phases. Given the promised SLO, requested and provided SL info, tolerance and time window, the TENF 110b computes in phase 1 the provided stateful tolerance, PST, according to the algorithm illustrated in figure I la. Using the tolerance and stateful tolerance, the TENF 110b determines in phase 2 the level of prioritization of the UEs 120a-b based on a ranking system. Using the determined level of prioritization, the TENF 110b computes in phase 3 the overall Stateful Evaluation Result (SER), which may be provided as the monitoring data to the ENF 110a.
  • SER Stateful Evaluation Result
  • the level of prioritization of UEs may be determined in phase 2 of figure 10 based on a two-dimensional ranking system, wherein the first dimension (i.e. Dimension 1) is based on whether the PST has been violated or not and the second dimension (i.e. Dimension 2) is based on the type of the UE attribute.
  • the TENF 110b may determine the ranking based on the first dimension (Provided Stateful Tolerance). To this end, in an embodiment, the TENF 110b may implement the algorithm illustrated in figure 1 lb.
  • the TENF 110b may determine the ranking based on the second dimension (Attribute Type). Based on the type of UE Attribute, the ranking may be recorded.
  • An exemplary attribute ranking is illustrated in the table shown in figure 12a.
  • the UE with the highest SER has the highest priority.
  • UE attributes 1 ) Availability of CS, 2) PDB and 3) Throughput.
  • UE#1 and Attribute “Availability of CS” and arbitrary time stamp t 10/06/2020 16:20:51, according to Algorithm 1 (illustrated in figure I la).
  • the attribute ranking policy along Dimension 1 is considered as shown in the table of figure 12c.
  • the attribute ranking policy along Dimension 2 is considered as shown in the table of figure 12d. Therefore, combining the tables of figures 12c and 12d and applying Algorithm 2 shown in figure 11b, the level of prioritization of UE#1 for the current example is as shown in the table of figure 12e.
  • the Per UE Per attribute SER and Per UE SER are computed as shown in the table of figure 12f.
  • the SER per UE is computed for all other UEs and the UE with the highest SER has the highest priority.
  • the NSR notification message comprises a respective identifier of the one or more UEs of the plurality of UEs 120a-n, an identifier of the network slice 130a, and/or an identifier of the further network slice 130b.
  • the method 1300 can be performed by the network entity 110a, in particular ENF 110a.
  • the network entity 110a in particular ENF 110a.
  • further features of the method 1300 result from the functionality of the network entity 110a, in particular ENF 110a, as well as the different implementation forms and embodiments thereof described above and below.
  • Figure 14 is a flow diagram illustrating a method 1400 for operating the further network entity 110b, in particular TENF 110b, for supporting a transfer of one or more UEs of a plurality of UEs 120a-n from a network slice 130a to a further network slice 130b controlled by a network entity 110a, in particular ENF 110a, of a mobile network 100.
  • the method 1400 comprises a step 1401 of determining a stateful evaluation of each UE of the plurality of UEs 120a-n.
  • the method 1400 comprises a step 1403 of sending the stateful evaluation of each UE of the plurality of UEs 120a-n as monitoring data to the network entity 110a, in particular ENF 110a, for controlling the transfer of the one or more UEs of the plurality of UEs 120a-n from the network slice 130a to the further network slice 130b.
  • the method 1400 can be performed by the further network entity 110b, in particular TENF 110b.
  • further features of the method 1400 result from the functionality of the further network entity 110b, in particular TENF 110b, as well as the different implementation forms and embodiments thereof described above and below.
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the described embodiment of an apparatus is merely exemplary.
  • the unit division is merely a logical function division and may be another division in an actual implementation.
  • a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed.
  • the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented by using some interfaces.
  • the indirect couplings or communication connections between the apparatuses or units may be implemented in electronic, mechanical, or other forms.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne une entité (110a ; 110) de réseau, en particulier une fonction de réseau de mise en vigueur, ENF, servant à commander un transfert d'un ou de plusieurs équipements d'utilisateurs, UE, d'une pluralité d'UE (120a-n) d'une tranche (130a) de réseau à une autre tranche (130b) de réseau d'un réseau mobile (100). L'entité de réseau, en particulier ENF, (110a ; 110) est configurée pour envoyer un message de notification de remplacement de tranche de réseau, NSR, à une fonction d'application, AF, (140) associée à une application s'exécutant sur la pluralité d'UE (120a-n), le message de notification de NSR comprenant un identifiant respectif du ou des UE transférés à l'autre tranche (130b) de réseau, un identifiant de la tranche (130a) de réseau et/ou un identifiant de l'autre tranche (130b) de réseau.
PCT/EP2024/058575 2024-03-28 2024-03-28 Entités de réseau et procédés de commande d'un transfert d'ue entre tranches de réseau Pending WO2025201652A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2024/058575 WO2025201652A1 (fr) 2024-03-28 2024-03-28 Entités de réseau et procédés de commande d'un transfert d'ue entre tranches de réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2024/058575 WO2025201652A1 (fr) 2024-03-28 2024-03-28 Entités de réseau et procédés de commande d'un transfert d'ue entre tranches de réseau

Publications (1)

Publication Number Publication Date
WO2025201652A1 true WO2025201652A1 (fr) 2025-10-02

Family

ID=90717784

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2024/058575 Pending WO2025201652A1 (fr) 2024-03-28 2024-03-28 Entités de réseau et procédés de commande d'un transfert d'ue entre tranches de réseau

Country Status (1)

Country Link
WO (1) WO2025201652A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210282053A1 (en) * 2018-11-27 2021-09-09 Huawei Technologies Co., Ltd. Transfer policy determining method, and apparatus
US20220240173A1 (en) * 2019-05-15 2022-07-28 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for managing network slice for terminal device

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210282053A1 (en) * 2018-11-27 2021-09-09 Huawei Technologies Co., Ltd. Transfer policy determining method, and apparatus
US20220240173A1 (en) * 2019-05-15 2022-07-28 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for managing network slice for terminal device

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
GENADI VELEV ET AL: "KI#1: Analysis on NSSF determining the Alternative S-NSSAI", vol. SA WG2, no. Online; 20230116 - 20230120, 9 January 2023 (2023-01-09), XP052232463, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_154AHE_Electronic_2023-01/Docs/S2-2300996.zip S2-2300996_DISC_eNS_KI1_NSSF-impacts.docx> [retrieved on 20230109] *
MARCO SPINI ET AL: "Correction on PCF events", vol. SA WG2, no. Goteborg, SE; 20230821 - 20230825, 11 August 2023 (2023-08-11), XP052438756, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_158_Goteborg_2023-08/Docs/S2-2308538.zip S2-2308538 - CR1095 Correction on PCF events.docx> [retrieved on 20230811] *
SAMSUNG ELECTRONICS CO LTD: "[FS_MS_NS_Ph2] Key Issue #3: Moving media flows to other slices", vol. 3GPP SA 4, no. Berlin, Germany; 20230522 - 20230526, 21 May 2023 (2023-05-21), XP052489647, Retrieved from the Internet <URL:https://ftp.3gpp.org/Meetings_3GPP_SYNC/SA4/Docs/S4-230928.zip S4-230928.docx> [retrieved on 20230521] *

Similar Documents

Publication Publication Date Title
EP4074093B1 (fr) Procédés, systèmes et supports lisibles par ordinateur pour fournir une gestion de tranche de réseau en utilisant un mécanisme de rétroaction
US11528621B2 (en) Method and system of performance assurance with conflict management in provisioning a network slice service
US12294496B2 (en) Methods and systems for service policy orchestration in a communication network
JP7269377B2 (ja) 移動通信ネットワークのネットワークスライスインスタンスに関するネットワーク解析及び／又は予測情報を提供するためのネットワーク解析コンポーネント及び方法。
US8130655B2 (en) Systems and methods for network congestion management using radio access network congestion indicators
US8200188B2 (en) System and method for adaptive fair usage controls in wireless networks
US20220264357A1 (en) Network entities for managing distribution of slice service level agreement information in a communication network
US20240049060A1 (en) First node, third node, and methods performed thereby, for handling quality of service in a communications network
US20230040486A1 (en) Policy Determining Method and Apparatus, and System
US8738017B2 (en) Radio resource management in a radio telecommunication network
CN112104469A (zh) 数据处理方法及装置
WO2020136512A1 (fr) Priorisation d&#39;utilisateurs sur la base de revenus pendant un encombrement
Raja et al. A review of call admission control schemes in wireless cellular networks
CN113475039B (zh) 基于开放信息的网络和/或管理功能适配的装置和方法
WO2025201652A1 (fr) Entités de réseau et procédés de commande d&#39;un transfert d&#39;ue entre tranches de réseau
US12476883B2 (en) Method, apparatus and computer program for determining quality of experience of an application session class
JP2025528641A (ja) 通信ネットワークによって通信サービスを提供する方法
US12543057B2 (en) Network device inventory analytics
WO2025017363A1 (fr) Analyse de données pour la gestion d&#39;énergie
CN114510247A (zh) 多接入边缘计算设备的业务部署方法、系统和设备
EP4451635A1 (fr) Rétroaction sur un format de qos alternatif permettant un calcul de satisfaction statistique d&#39;application
EP4135413A1 (fr) Agencement de réseau de communication et procédé de sélection de composant de réseau
WO2025016599A1 (fr) Appareil, procédés et programmes informatiques prenant en charge des abonnements à des événements
WO2025074386A1 (fr) Unité d&#39;approvisionnement pour fournir des mesures d&#39;utilisation de tranche de réseau en temps réel
CN118804233A (zh) 能源信息提供方法、装置、功能实体及节点设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24716334

Country of ref document: EP

Kind code of ref document: A1