Selection of network slicing data rate
By comparing the accumulated throughput value of the PDU session with the maximum shard throughput value, the problem of UE being unable to determine support when acquiring a network cell is solved, effectively control of data transmission is achieved, and stable and efficient communication is ensured.
Patent Information
- Application Number
- CN202110175158.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-02-03
- Filing Date
- 2021-02-09
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2041-02-09
AI Technical Summary
When the user equipment (UE) is pre-occupied with a network cell, it is impossible to determine whether the cell supports specific network shards, resulting in the possibility of pre-occupied network shards, affecting data transmission efficiency.
By receiving and comparing the accumulated throughput value of the protocol data unit (PDU) session with the maximum shard throughput value, if it exceeds, data rate limiting is performed to ensure that data transmission is within a safe range.
Effectively control the data throughput of network shards, prevent data transmission from exceeding cell support capabilities, and ensure stable connections and efficient communication.
Smart Images

Figure CN113259914B_ABST
Abstract
Description
Background Art
[0001] A user equipment (UE) may be connected to a network including a network slice. Generally speaking, a network slice refers to a network architecture in which multiple end-to-end logical networks run on a shared physical network infrastructure. Each network slice may be configured for a specific purpose. For example, a network may include a network slice configured to provide carrier services (e.g., voice, multimedia messaging service (MMS), Internet, etc.), a network slice configured to provide machine type communication (MTC) services, a network slice configured to provide ultra-reliable low latency communication (URLLC) services, and the like. Therefore, each network slice may share network resources but facilitate different functions.
[0002] In order to establish a connection with the network and perform the full range of functions generally available to the UE via the network connection, the UE may camp on a cell of the network. In conventional cases, when the UE selects a cell to camp on, the UE does not know whether the cell supports a particular network slice. Therefore, the UE may camp on a cell that does not support the network slice that the UE is configured to utilize. Summary of the invention
[0003] Some exemplary embodiments relate to a processor configured to perform operations including: receiving a request to establish a new protocol data unit (PDU) session of a network slice for a user equipment (UE); receiving a maximum session throughput value for the new PDU session; adding the maximum session throughput value for the new PDU session to a cumulative maximum session throughput value to determine an updated cumulative maximum session throughput value; comparing the updated cumulative maximum session throughput value to a maximum slice throughput value; and when the updated cumulative maximum session throughput value exceeds the maximum slice throughput value, performing an action related to the new PDU session.
[0004] Other exemplary embodiments relate to a processor configured to perform operations including determining a maximum slice throughput value for a network slice for a user equipment (UE), determining a cumulative session throughput value for currently active protocol data unit (PDU) sessions for the network slice for the UE, comparing the cumulative session throughput value to the maximum slice throughput value, and when the cumulative session throughput value exceeds the maximum slice throughput value, throttling one of the active PDU sessions so that the cumulative session throughput value does not exceed the maximum slice throughput value. BRIEF DESCRIPTION OF THE DRAWINGS
[0005] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.
[0006] Figure 2An exemplary signaling diagram of a registration procedure for a UE to register with a network, wherein a core network imposes data rate limitations on network slices, or a radio access network (RAN) imposes data rate limitations on network slices, is shown according to various exemplary embodiments.
[0007] Figure 3 An exemplary signaling diagram for a UE to establish a protocol data unit (PDU) session for a network slice, wherein the core network includes a data rate limit for the network slice, is shown according to various exemplary embodiments.
[0008] Figure 4 Exemplary signaling methods for enabling a core network to enforce data rate limits on network slices according to various exemplary embodiments are shown.
[0009] Figure 5 An exemplary signaling diagram for a UE to establish a protocol data unit (PDU) session for a network slice where a RAN enforces data rate limits on the network slice is shown according to various exemplary embodiments.
[0010] Figure 6 Exemplary methods for enabling a RAN to enforce data rate limits on a network slice in accordance with various exemplary embodiments are shown. DETAILED DESCRIPTION
[0011] The exemplary embodiments may be further understood with reference to the following description and associated drawings, wherein similar elements have the same reference numerals. The exemplary embodiments relate to implementing a method for controlling the data throughput of a network slice. The exemplary embodiments may be used to control the data rate on a per-slice basis. The exemplary embodiments include a static method for controlling the data rate without involving a radio access network (RAN) (only involving a core network). The exemplary embodiments also include a dynamic method for controlling the data rate based on the RAN implementation data rate.
[0012] The exemplary embodiments are described with reference to a fifth generation (5G) network including network slicing. In general, network slicing refers to a network architecture in which multiple end-to-end logical networks run on a shared physical network infrastructure. Each network slice can be configured to provide a specific set of capabilities and / or features. Therefore, the physical infrastructure of a 5G network can be sliced into multiple virtual networks, each of which is configured for a different purpose.
[0013] Those skilled in the art will appreciate that 5G may support use cases such as enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Each of these types of use cases may involve a variety of different types of applications and / or services. Network slicing may be characterized by the type of use case, the type of application and / or service, or the entity providing the application and / or service via the network slicing. However, any examples in this specification that characterize network slicing in a particular manner are provided only for illustrative purposes. Throughout the specification, references to network slicing may represent any type of end-to-end logical network configured for a particular purpose and implemented on a 5G physical infrastructure.
[0014] As indicated above, network slicing can be used for a variety of different purposes. However, the configuration purposes of network slicing are beyond the scope of the exemplary embodiment. Therefore, the exemplary embodiment is not limited to any particular type of network slicing. Instead, the exemplary embodiment involves selecting a data rate on a per-slice basis.
[0015] As described above, the exemplary embodiments describe controlling the data rate of a network slice. It should be understood that the exemplary embodiments may be applied to either or both of the downlink (DL) data rate or the uplink (UL) data rate of the slice. That is, as shown in the exemplary embodiments below, the control of the data rate may be in either or both of the DL or UL.
[0016] Those skilled in the art will appreciate that 5G NR currently allows for a per-PDU session aggregate maximum bit rate ("session-AMBR") and per-UE-AMBR. An exemplary embodiment involves implementing per-network slice for per-UE AMBR. As will be described in more detail below, an exemplary embodiment may be used to determine whether and how to limit the UE's data rate for a network slice to ensure that the aggregated rate of the PDU sessions using the slices is limited to the rate defined for the network slice in either or both of the DL or UL. An exemplary embodiment may also provide a way to signal the rate limit of a network slice.
[0017] Figure 1An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 may be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a phablet, an embedded device, a wearable device, an Internet of Things (IoT) device, an eMTC device, etc. It should also be appreciated that an actual network arrangement may include any number of UEs used by any number of users. Therefore, for purposes of illustration, only an example with a single UE 110 is provided.
[0018] UE 110 may be configured to communicate with one or more networks. In the example of network configuration 100, the networks with which UE 110 may wirelessly communicate are 5G New Radio (NR) radio access networks (5G NR-RAN) 120, 122, and LTE-RAN 124. However, it should be understood that UE 110 may also communicate with other types of networks (e.g., traditional cellular networks, WLAN, etc.), and UE 110 may also communicate with the network via a wired connection. With respect to the exemplary embodiment, UE 110 may establish a connection with 5G NR-RAN 120, 5G NR-RAN 122, or LTE-RAN 124.
[0019] The 5G NR-RAN 120, 122 and LTE-RAN 124 may be part of cellular networks that may be deployed by cellular providers such as Verizon, AT&T, Sprint, T-Mobile, etc. These networks 120, 122 may include, for example, cells or base stations (NodeB, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive traffic from UEs equipped with appropriate cellular chipsets.
[0020] 5G NR-RAN 120, 122 may include an architecture capable of providing both 5G NR RAT services and LTE RAT services. For example, a next generation radio access network (NG-RAN) (not shown) may include a next generation Node B (gNB) providing 5G NR services and a next generation evolved Node B (ng-eNB) providing LTE services. The NG-RAN may be connected to at least one of an evolved packet core (EPC) or a 5G core (5GC). Therefore, reference to 5G NR-RAN 120, 122 and LTE-RAN 124 is provided only for illustrative purposes, and the exemplary embodiments may be applied to any appropriate type of RAN.
[0021] Returning to the exemplary network arrangement 100, the UE 110 may be connected to the 5G NR-RAN 120 via a next generation Node B (gNB) 120A, to the 5G NR-RAN 122 via a gNB 122A, and to the LTE-RAN 124 via an eNB 124a. Those skilled in the art will appreciate that any relevant process may be performed to connect the UE 110 to the 5G NR-RAN 120, 5G NR-RAN 122, or LTE-RAN 124. For example, as described above, the 5G NR-RAN 120 may be associated with a particular cellular provider at which the UE 110 and / or its user has agreement and credential information (e.g., stored on a SIM card). Upon detecting the presence of the 5G NR-RAN 120, the UE 110 may transmit the corresponding credential information in order to associate with the 5G NR-RAN 120. More specifically, UE 110 may be associated with a particular cell, e.g., gNB 120A of 5G NR-RAN 120. Similarly, to access 5G NR-RAN 122, UE 110 may be associated with gNB 122A, and to access LTE-RAN 124, UE 110 may be associated with eNB 124A.
[0022] In addition to the 5G NR-RANs 120, 122 and the LTE-RAN 124, the network arrangement 100 includes a cellular core network 130, the Internet 140, an IP multimedia subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 can be viewed as an interconnected collection of components that manage the operation / traffic of the cellular network. The cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 can generally be described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.
[0023] As described above, the exemplary embodiment includes a static way of controlling the data rate without involving the radio access network (RAN) (only involving the core network). The exemplary embodiment is called a static way of controlling the data rate because it is based on the maximum AMBR of the slices and the corresponding PDU session instead of the actual throughput of the slices. For example, a sliced PDU session may have an AMBR of X. However, the actual throughput of the sliced PDU session may be 1 / 2X. Because the core network 130 does not know the current actual throughput, the core network 130 will implement data throughput restrictions based on the session AMBR as a static value. Figure 2 and Figure 3 The respective signaling diagrams 200 and 300 of FIG. 4 and the method diagram 400 are used to describe an exemplary embodiment of this type. As will be described in more detail below, in this exemplary embodiment, each time a new protocol data unit (PDU) session is established for a network segment, the implementation of each segment AMBR is performed.
[0024] Figure 2 An exemplary signaling diagram of a registration process for registering UE 110 with a network is shown according to various exemplary embodiments, wherein core network 130 implements data rate restrictions on network slices, or a radio access network (RAN) implements data rate restrictions on network slices. In this exemplary embodiment, core network 130 may be considered to implement data rate restrictions.
[0025] In discussion Figure 2 Before describing the signaling in the specification, the specific components that perform the signaling will be described. Figure 2 , the first component is the UE 110 discussed above. The next component is the 5G NR-RAN 120. As described above, the UE 110 can connect to the 5G NR-RAN 120 via the gNB 120A or any other gNB associated with the 5G NR-RAN 120. In addition, as described above, the UE 110 can access the 5G NR-RAN 122 or the LTE-RAN 124. However, in this example, it can be considered that the UE 110 will be registered via the 5G NR-RAN 120.
[0026] The remaining components / functions may be considered to reside in the core network 130. However, those skilled in the art will appreciate that these components / functions may reside in other parts of the network (e.g., 5G NR-RAN 120) or may be distributed between various parts of the network. The next component is the access and mobility management function (AMF) 131. The AMF 131 is generally responsible for mobility management in the 5G NR-RAN 120. For example, the AMF 131 may be responsible for managing handovers between gNBs. The next component is the second AMF 132. Those skilled in the art will appreciate that a typical network will have multiple AMF functions, and different UEs may be assigned to different AMFs, utilizing the same AMF to reduce mobility management signaling.
[0027] The next component is the Policy Control Function (PCF) 133. PCF 133 provides policy rules for control plane functions including network segmentation, roaming, and mobility management. The next component is the Session Management Function (SMF) 134. SMF 134 may be responsible for creating, updating, and removing protocol data unit (PDU) sessions for the UE.
[0028] The next component is the Authentication Server Function (AUSF) 135. The AUSF 135 is generally responsible for subscriber authentication during registration or re-registration. The next component is the Unified Data Management (UDM) 136. The UDM 136 is generally responsible for providing data to other functions. For example, the UDM 136 may provide data to the AMF 131 and 132 and the SMF 134 to perform corresponding functions. In another example, the UDM 135 may generate an authentication vector for the AUSF 134. Those skilled in the art will appreciate that although each of these elements is referred to as a component, this does not mean that each is a discrete physical component. Instead, the functionality of each of these components may be implemented in hardware, firmware, or software by one or more network devices including a cloud-specific implementation.
[0029] The entire registration of the signaling diagram 200 will not be described, as those skilled in the art will appreciate that the signaling diagram 200 and the various signaling are similar to those described in 3GPP 23.502 version 16.3.0. Figure 4 .2.2.2.2-1: Signaling during the registration process describes the registration procedure.
[0030] Instead, this specification will focus on steps 14a-14c of the registration process, that is, there are differences between the standard registration process as described in 3GPP 23.502 and the exemplary embodiment. First, a typical registration scenario in steps 14a-14c will be described for a service such as Voice over PS (VoPS). In step 14a, AMF 131 registers with UDM 136 using Nudm_UECM_Registration so that the access will be registered. As part of this registration, AMF 131 may provide the UDM with the services supported by UE 110 (e.g., Voice over PS (VoPS)). However, AMF 131 may not have subscription information for UE 110, for example, whether the subscription associated with UE 110 supports VoPS services. If AMF 131 does not have subscription data for UE 110, then in step 14b, AMF 131 uses Nudm_SDM to retrieve various subscription data for UE 110. After receiving the subscription information, when the requested data is modified (e.g., the subscription information changes), AMF 131 can subscribe to be notified using Nudm_SDM_Subscribe (step 14c). Therefore, in this way, AMF 131 can implement the subscription information of UE 110 during operation.
[0031] In an exemplary embodiment, the same subscription implementation may be performed. For example, UDM 136 may include data rate limits for each network slice in UL and DL. During the registration process of UE 110, AMF 131 may retrieve the data rate limits for each network slice information from UDM 136. Then, when UE 110 connects to the network, AMF 131 may implement the limits, as will be described in more detail below.
[0032] Figure 3 An exemplary signaling diagram 300 is shown for enabling UE 110 to establish a protocol data unit (PDU) session for a network slice according to various exemplary embodiments, wherein core network 130 includes data rate limiting for the network slice. There are two components in signaling diagram 300 that are not included in signaling diagram 200, and these components will be briefly described before describing signaling diagram 300. Core network 130 also includes user plane function (UPF) 137. UPF 137 performs packet routing and forwarding, packet inspection, and QoS processing. Core network 130 also includes data network (DN) 138. These components are not described in further detail because they do not involve specific modifications to the PDU establishment process described with respect to signaling diagram 300.
[0033] Likewise, similar to signaling diagram 200, the entire PDU session establishment process of signaling diagram 300 will not be described, as those skilled in the art will appreciate that signaling diagram 300 and the various signaling are similar to those described in 3GPP 23.502 version 16.3.0. Figure 4 .Signalling of the PDU Session Establishment procedure described in .3.2.2.1-1 (PDU Session Establishment for Non-Roaming and Roaming UE Requests with Local Breakout).
[0034] Instead, this specification will focus on the new step 4a of the PDU session establishment process, that is, there are differences between the standard PDU session establishment process as described in 3GPP 23.502 and the exemplary embodiment. In step 4a, SMF 134 sends the session AMBR to AMF 131. That is, SMF 134 provides the session AMBR of the new PDU session being attempted to be established to AMF. AMF 131 will accumulate each session AMBR from all currently active PDU sessions and the new PDU session. Then, AMF 131 can compare the accumulated value with the data rate limit (for example, retrieved from UDM 136 during the registration process as described above). If the accumulated AMBR of all PDU sessions does not exceed the data rate limit, AMF 131 will allow the PDU session to be established. If the accumulated AMBR exceeds the data rate limit, AMF 131 will report this to SMF 134. SMF 134 can then reject the PDU session establishment or cap the session AMBR of the new PDU session so that the accumulated AMBR does not exceed the data rate limit.
[0035] Figure 4 An exemplary method 400 for enabling the core network 130 to enforce data rate limits on network slices is shown in accordance with various exemplary embodiments. Figure 1 An exemplary network arrangement 100 and Figure 2 and Figure 3 The exemplary method 400 is described in the various signaling diagrams 200 and 300 of FIG. The exemplary method 400 is described from the perspective of the AMF 131.
[0036] In 410, AMF 131 retrieves subscription information from UDM 136 during a network registration procedure performed for UE 110. As described above, UDM 136 may store subscription information including per-segment AMBR limits for each UE. In 420, AMF 131 may accumulate per-segment AMBRs for each UE for any active PDU sessions of UE 110.
[0037] In 430, the AMF 131 receives a new fragmented PDU session establishment request from the UE 110. As described above, in 440, the AMF 131 then receives the session AMBR of the new PDU session from the SMF 134. In 450, the AMF 131 then adds the session AMBR of the new PDU session to the current cumulative AMBR. In 460, the AMF 141 may then compare the cumulative AMBR (including the session AMBR of the new PDU session) with the subscription information retrieved in 410. If the cumulative AMBR does not exceed the overall per-fragment AMBR of the subscription information, the AMF 131 allows the new PDU session to be established in 470. However, if the cumulative AMBR exceeds the overall per-fragment AMBR of the subscription information, the AMF 131 will report this information to the SMF 134 in 480. The SMF 134 may then reject the new PDU session establishment or overwrite the session AMBR for the new PDU session so that the cumulative AMBR does not exceed the data rate limit.
[0038] Therefore, it can be seen from the above that Figures 2 to 4 The described exemplary embodiments provide a way for the core network to control the AMBR limit per slice per UE.
[0039] As described above, the exemplary embodiments also include a dynamic way to control the data rate based on the RAN enforced data rate. Figure 2 and Figure 5 The respective signaling diagrams 200 and 500 of , and the method diagram 600 are used to describe this type of exemplary implementation. As will be described in more detail below, in this exemplary implementation, each slice AMBR is implemented by the RAN (e.g., 5G NR-RAN 120) based on the aggregate bit rate from all non-GBR (non-guaranteed bit rate) QoS flows belonging to the network slice.
[0040] Figure 2 An exemplary signaling diagram of a registration process for UE 110 to register with a network according to various exemplary embodiments is shown, wherein core network 130 implements data rate restrictions on network slices, or a radio access network (RAN) implements data rate restrictions on network slices. In this example, it can be assumed that the RAN and specifically 5G NR-RAN 120 is implementing the data rate restrictions. It will not be described further. Figure 2 , as it is the same for this exemplary embodiment as described above for another exemplary embodiment. That is, the UDM will store subscription information associated with the UE 110 of the network slice, such as the maximum AMBR per slice for each UE associated with the UE 110. The AMF 131 will retrieve this information during the registration process.
[0041] Figure 5An exemplary signaling diagram 500 is shown for enabling UE 110 to establish a protocol data unit (PDU) session for a network slice according to various exemplary embodiments, wherein the RAN implements data rate limits for the network slice. Also, similar to signaling diagram 300, signaling diagram 500 and various signaling are similar to those described in 3GPP 23.502 Version 16.3.0 Figure 4 .3.2.2.1-1 (PDU session establishment for non-roaming and roaming UE requests with local breakout) describes the signaling of the PDU session establishment procedure. Therefore, the entire signaling will not be described, but the parts that are different from the PDU establishment procedure described in 3GPP 23.502 will be described.
[0042] When establishing a PDU session, the 5G NR-RAN 120 receives a quality of service (QoS) profile and single network slice selection assistance information (s-NSSAI) (e.g., a network slice associated with the PDU session). In an exemplary embodiment, in steps 11 and 12, the 5G NR-RAN also associates the QoS profile with the corresponding QoS flow identifier (QFI) via the s-NSSAI.
[0043] With this information, the 5G NR-RAN 120 can then implement the per-slice AMBR for the network slices. That is, the 5G NR-RAN 120 has received information corresponding to the data rate limit for each network slice of the network slice from the AMF 131 during the registration process. This enforcement mechanism of the 5G NR-RAN 120 can be considered dynamic because the PDU session will not be rejected. Instead, the PDU session is established, and the 5G NR-RAN 120 can then monitor the aggregate bit rate of the specific slice in any time measurement window. If the aggregate bit rate exceeds the subscription information, the 5G NR-RAN 120 can reduce the data rate of one or more active PDU sessions for the slice to keep the bit rate below the threshold associated with the subscribed data rate limit.
[0044] Figure 6 An exemplary method 600 for enabling a RAN to enforce data rate limits on a network slice is shown in accordance with various exemplary embodiments. Figure 1 An exemplary network arrangement 100 and Figure 2 and Figure 5 The exemplary method 600 is described with reference to the respective signaling diagrams 200 and 500 of FIG. The exemplary method 600 is described from the perspective of 5G NR-RAN 120.
[0045] In 610, the 5G NR-RAN 120 retrieves subscription information of the UE 110 associated with the network slice. As described above, during the registration process, the AMF 131 will receive the subscription information from the UDM 136. The AMF 131 may then send the subscription information to the 5G NR-RAN 120 during the registration process. The subscription information may include a per-slice data rate limit for each UE.
[0046] In 620, 5G NR-RAN 120 may monitor the throughput of a particular network slice. As described above, the slice throughput will include the cumulative throughput of all currently active slice PDU sessions of UE 110. The throughput may be measured for a defined measurement window. In this exemplary embodiment, the RAN (e.g., 5G NR-RAN) may enforce data throughput limits for a network slice because 5G NR-RAN 120 is the entity that is aware of the total throughput (UL or DL) of UE 110 for a particular slice on a real-time basis.
[0047] In 630, 5G NR-RAN 120 may compare the cumulative throughput with subscription information (e.g., the data rate limit of the network slice of UE 110). If the current slice throughput is greater than the limit, 5G NR-RAN may throttle in 640 one or more of the PDU sessions corresponding to the network slice and UE 110 to reduce the cumulative throughput to below the data rate limit of the network slice. If the current slice throughput is less than the limit, 5G NR-RAN will continue back to 620 and continue to monitor the cumulative throughput of the network slice and compare it to the limit (630) as long as the network slice remains active for UE 110.
[0048] Therefore, it can be seen from the above that Figure 2 and Figure 5 to Figure 6 The described exemplary embodiments provide a way for the RAN to control the data rate limit for each slice of each UE.
[0049] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. In other examples, the exemplary embodiments of the above methods may be embodied as a program including lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.
[0050] Although this patent application describes various combinations of various embodiments each having different features, those skilled in the art will understand that any feature of an embodiment may be combined with features of other embodiments in any manner not publicly denied or with features that are not functionally or logically inconsistent with the operation or function of the device of the embodiments disclosed in the present invention.
[0051] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.
[0052] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is intended to cover modifications and variations of the present disclosure, provided that these modifications and variations are within the scope of the appended claims and their equivalents.
Claims
1. A method comprising: receiving a request to establish a new protocol data unit (PDU) session for a network slice for a user equipment (UE); Receiving a maximum session throughput value of the new PDU session; adding the maximum session throughput value of the new PDU session to a cumulative maximum session throughput value to determine an updated cumulative maximum session throughput value; comparing the updated cumulative maximum session throughput value with the maximum shard throughput value; as well as When the updated cumulative maximum session throughput value exceeds the maximum segment throughput value, an action related to the new PDU session is performed.
2. The method according to claim 1, further comprising: Determining the maximum slice throughput value of the network slice for the UE; as well as Prior to receiving the request to establish the new PDU session, determining the cumulative maximum session throughput value of currently active PDU sessions for the network slice for the UE.
3. The method of claim 1, wherein the actions include: The new PDU session is rejected.
4. The method of claim 1, wherein the actions include: The new PDU session is established having a second maximum session throughput value lower than the maximum session throughput value. 5 . The method of claim 4 , wherein the second maximum session throughput value is set such that a sum of the second maximum session throughput value and the cumulative maximum session throughput value is less than the maximum slice throughput value.
6. The method according to claim 1, further comprising: When the updated cumulative maximum session throughput value does not exceed the maximum fragment throughput value, the new PDU session is established.
7. The method of claim 1, wherein the maximum slice throughput value is for one of a downlink (DL) to the UE or an uplink (UL) from the UE. The method according to claim 1 , wherein the method is performed by a core network.
9. The method of claim 8, wherein the method is performed by an access and mobility management function (AMF) or a policy control function (PCF) of the core network.
10. The method of claim 1, wherein the determining the maximum slice throughput value for the network slice is determined during a registration procedure of the UE.
11. A method comprising: Determine a maximum slice throughput value of a network slice for a user equipment UE; determining, for the UE, a cumulative session throughput value of a currently active protocol data unit (PDU) session of the network slice; comparing the cumulative session throughput value with the maximum shard throughput value; as well as When the cumulative session throughput value exceeds the maximum segment throughput value, one of the active PDU sessions is throttled so that the cumulative session throughput value does not exceed the maximum segment throughput value.
12. The method according to claim 11, further comprising: When the accumulated session throughput value does not exceed the maximum slice throughput value, continue to determine the accumulated session throughput value of the currently active protocol data unit (PDU) session of the network slice for the UE.
13. The method of claim 11, wherein the cumulative session throughput value is determined for a specified measurement window.
14. The method of claim 11, wherein the maximum slice throughput value is for one of a downlink (DL) to the UE or an uplink (UL) from the UE.
15. The method of claim 11, wherein the method is performed by one of: (a) a radio access network (RAN) for a downlink (DL) or uplink (UL), or (b) the UE for the UL.
16. The method of claim 11, wherein the determining the maximum slice throughput value of the network slice is determined during a sliced PDU session establishment procedure of the UE.
17. The method of claim 11, wherein the determining the maximum slice throughput value of the network slice comprises: A quality of service (QoS) profile and single network slice selection assistance information (s-NSSAI) of the network slice associated with the PDU session are received.
18. The method according to claim 17, further comprising: The QoS profile is associated with a corresponding QoS flow identifier (QFI) through the s-NSSAI.
19. The method of claim 11, wherein said throttling one of said active PDU sessions comprises throttling more than one of said active PDU sessions.
20. The method according to claim 19, further comprising: Priority is given to throttling non-guaranteed bit rate (GBR) PDU sessions.
