Patent Application
20240196263
The present disclosure relates to a cellular communications system and, more specifically, to handling and enforcement of a maximum bit rate for a network slice.
The Third Generation Partnership Project (3GPP) study item on enhancements for network slicing phase 2 is documented in 3GPP Technical Report (TR) 23.700-40 v. 17.0.0. Key Issue #3 defined a new Quality of Service (QOS) parameter called “Maximum UL/DL throughput per UE” and proposed to study how to define this QoS parameter, where this QoS parameter should be enforced, how to signal this QoS parameter to the enforcement point, and any impacts on subscription data.
The conclusions to this Key Issue said:
The conclusions indicate that the S-MBR, also referred as UE-Slice-MBR, can be enforced both (a) at the RAN and (b) the PCF, where the PCF ensures that the QoS parameters for the PDU sessions of a UE in a network slice do not exceed the S-MBR.
Systems and methods for handling of heterogeneous support for Slice Maximum Bit Rate (S-MBR) enforcement are disclosed. In one embodiment, a method performed in a core network of a cellular communications system comprises, at an Access and Mobility Management Function (AMF), obtaining information about whether a Radio Access Network (RAN) node supports S-MBR enforcement and sending, to a Session Management Function (SMF), a message that comprises an indication of whether the RAN node supports S-MBR enforcement. The method further comprises, at the SMF, sending, to a Policy and Control Function (PCF), a message that comprises an indication of whether the RAN node supports S-MBR enforcement. The method further comprises, at the PCF, receiving, from the SMF, the message that comprises the indication of whether the RAN node supports S-MBR enforcement, making a determination of whether to apply a mechanism to enforce S-MBR for Protocol Data Unit (PDU) session of a wireless communication device on a network slice based on whether the RAN node supports S-MBR enforcement as indicated by the received message, and operating in accordance with the determination. In this manner, heterogeneous support for S-MBR in the RAN is handled.
Embodiments of a method performed by a core network node in a core network of a cellular communications system are also disclosed. In one embodiment, a method performed by a core network node in a core network of a cellular communications system comprises obtaining information that indicates whether a RAN node supports S-MBR enforcement and making a determination of whether to apply a mechanism to enforce an S-MBR for one or more PDU sessions of a wireless communication device on a network slice in the core network based on whether the RAN node supports S-MBR enforcement as indicated by the obtained information. The method further comprises operating in accordance with the determination.
In one embodiment, the core network node is a PCF, an AMF, or an SMF.
In one embodiment, the obtained information comprises information that indicates that that RAN node supports S-MBR enforcement, making the determination comprises making the determination to not apply the mechanism to enforce S-MBR in the core network, and operating in accordance with the determination comprises operating such that the mechanism to enforce S-MBR in the core network is not applied.
In one embodiment, the obtained information comprises information that indicates that that RAN node does not support S-MBR enforcement, making the determination comprises making the determination to apply the mechanism to enforce S-MBR in the core network, and operating in accordance with the determination comprises operating such that the mechanism to enforce S-MBR in the core network is applied.
In one embodiment, the core network node is a PCF. In one embodiment, obtaining the information comprises receiving a message that comprises information that indicates whether the RAN node supports S-MBR enforcement. In one embodiment, receiving the message comprises receiving the message from an AMF. In one embodiment, the message received at the PCF comprises information that indicates that that RAN node supports S-MBR enforcement, making the determination comprises making the determination to not apply the mechanism to enforce S-MBR at the PCF, and operating in accordance with the determination comprises refraining from applying the mechanism to enforce S-MBR at the PCF. In another embodiment, the message received at the PCF comprises information that indicates that that RAN node does not support S-MBR enforcement, making the determination comprises making the determination to apply the mechanism to enforce S-MBR at the PCF, and operating in accordance with the determination comprises applying the mechanism to enforce S-MBR at the PCF.
Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node for hosting a core network function of a core network of a cellular communications system is adapted to obtain information that indicates whether a RAN node supports S-MBR enforcement, make a determination of whether to apply a mechanism to enforce an S-MBR for one or more PDU sessions of a wireless communication device on a network slice in the core network based on whether the RAN node supports S-MBR enforcement as indicated by the obtained information, and operate in accordance with the determination.
In one embodiment, a network node for hosting a core network function of a core network of a cellular communications system comprises processing circuitry configured to cause the network node to obtain information that indicates whether a RAN node supports S-MBR enforcement, make a determination of whether to apply a mechanism to enforce an S-MBR for one or more PDU sessions of a wireless communication device on a network slice in the core network based on whether the RAN node supports S-MBR enforcement as indicated by the obtained information, and operate in accordance with the determination.
Embodiments of a method performed by an AMF in a core network of a cellular communications system are also disclosed. In one embodiment, a method performed by an AMF in a core network of a cellular communications system comprises obtaining information about whether a RAN node supports S-MBR enforcement and sending, to a SMF, a message that comprises an indication of whether the RAN node supports S-MBR enforcement.
In one embodiment, obtaining the information about whether the RAN node supports S-MBR enforcement comprises receiving the information about whether the RAN node supports S-MBR enforcement from another network node. In one embodiment, the other network node is an Operations and Management (OAM) node.
In one embodiment, obtaining the information about whether the RAN node supports S-MBR enforcement comprises receiving, from the RAN node, a message that indicates failure of a procedure where S-MBR is included. In one embodiment, the message that indicates failure of a procedure where S-MBR is included in an initial context setup failure message.
In one embodiment, obtaining the information about whether the RAN node supports S-MBR enforcement comprises receiving, from the RAN node, an indication that the RAN node supports S-MBR enforcement. In one embodiment, receiving the indication from the RAN node comprises receiving the S-MBR that is associated with a specific network slice that can be enforced or some other kind of ‘ack’ in an appropriate message. In another embodiment, receiving the indication from the RAN node comprises receiving the indication during a NG-setup procedure.
In one embodiment, the message sent from the AMF to the SMF that comprises the indication of whether the RAN node supports S-MBR enforcement is a Nsmf_PDUSession_CreateSMContext Request message.
Corresponding embodiments of a network node for hosting an AMF are also disclosed. In one embodiment, a network node for hosting an AMF of a core network of a cellular communications is adapted to obtain information about whether a RAN node supports S-MBR enforcement and send, to a SMF, a message that comprises an indication of whether the RAN node supports S-MBR enforcement.
In one embodiment, a network node for hosting an AMF of a core network of a cellular communications comprises processing circuitry configured to cause the network node to obtain information about whether a RAN node supports S-MBR enforcement and send, to a SMF, a message that comprises an indication of whether the RAN node supports S-MBR enforcement.
In another embodiment, a method performed in a cellular communications system comprises, at a core network node in a core network of the cellular communications system, sending a message to a RAN node in a RAN of the cellular communications system, the message comprising S-MBR information for one or more network slices. The method further comprises, at a RAN node in a RAN of the cellular communications system, receiving the message comprising the S-MBR information for one or more network slices from the core network node and sending a response to the core network node, the response comprising information that explicitly or implicitly indicates whether the RAN node supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node.
In one embodiment, a method performed by a core network node in a core network of a cellular communications system comprises sending a message to a RAN node in a RAN of the cellular communications system, the message comprising slice-maximum bit rate, S-MBR, information for one or more network slices. The method further comprises receiving a response from the RAN node, the response comprising information that explicitly or implicitly indicates whether the RAN node supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node.
In one embodiment, the message is a message associated to signaling or updating of a UE context of an associated UE.
In one embodiment, the message is a message associated to signaling of a PDU session modification.
In one embodiment, the message is an Initial UE Context Setup Request message and the response is an Initial UE Context Setup Failure message. In one embodiment, the S-MBR information comprises one or more S-MBR values for one or more network slices for which PDU sessions with an active user plane are established at the RAN node. In one embodiment, the S-MBR information comprises one or more S-MBR values for one or more network slices that do not have an active user plane connection established at the RAN node.
In one embodiment, the information comprised in the response comprises information that indicates whether the RAN node supports S-MBR enforcement, information that indicates whether S-MBR enforcement is feasible at the RAN node for a particular network slice, or both.
In one embodiment, the information comprised in the response comprises information that indicates whether the RAN node supports S-MBR enforcement, information that indicates whether S-MBR enforcement is feasible at the RAN node for a particular PDU session, or both.
In one embodiment, the information comprised in the response comprises, for each PDU session of one or more PDU sessions for which an active user plane is established at the RAN node, information that indicates whether the RAN node supports S-MBR enforcement, information that indicates whether S-MBR enforcement is feasible at the RAN node for the PDU session, or both.
In one embodiment, the information comprised in the response comprises a slice maximum bit rate enforcement indicator.
In one embodiment, the response is a NGAP message.
In one embodiment, the response is a PDU session response setup response, a PDU session resource modify response, a PDU session resource notify, an initial UE context setup response, or a handover request acknowledge.
In one embodiment, the method further comprises performing one or more actions based on the information comprised in the response.
In one embodiment, the core network node is an AMF.
Corresponding embodiments of a network node are also disclosed. In one embodiment, a network node for hosting a core network function of a core network of a cellular communications system is adapted to send a message to a RAN node in a RAN of the cellular communications system, the message comprising S-MBR information for one or more network slices. The network node is further adapted to receive a response from the RAN node, the response comprising information that explicitly or implicitly indicates whether the RAN node supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node.
In one embodiment, a network node for hosting a core network function of a core network of a cellular communications system comprises processing circuitry configured to cause the network node to send a message to a RAN node in a RAN of the cellular communications system, the message comprising S-MBR information for one or more network slices. The network node is further adapted to receive a response from the RAN node, the response comprising information that explicitly or implicitly indicates whether the RAN node supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node.
In one embodiment, a method performed by a RAN node in a RAN of a cellular communications system comprises receiving a message from a core network node in a core network of the cellular communications system, the message comprising S-MBR information for one or more network slices. The method further comprises sending a response to the core network node, the response comprising information that explicitly or implicitly indicates whether the RAN node supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node.
In one embodiment, the message is a message associated to signaling or updating of a UE context of an associated UE.
In one embodiment, the message is a message associated to signaling of a PDU session modification.
In one embodiment, the message is an Initial UE Context Setup Request message and the response is an Initial UE Context Setup Failure message. In one embodiment, the S-MBR information comprises one or more S-MBR values for one or more network slices for which PDU sessions with an active user plane are established at the RAN node. In one embodiment, the S-MBR information comprises one or more S-MBR values for one or more network slices that do not have an active user plane connection established at the RAN node.
In one embodiment, the information comprised in the response comprises information that indicates whether the RAN node supports S-MBR enforcement, information that indicates whether S-MBR enforcement is feasible at the RAN node for a particular network slice, or both.
In one embodiment, the information comprised in the response comprises information that indicates whether the RAN node supports S-MBR enforcement, information that indicates whether S-MBR enforcement is feasible at the RAN node for a particular PDU session, or both.
In one embodiment, the information comprised in the response comprises, for each PDU session of one or more PDU sessions for which an active user plane is established at the RAN node, information that indicates whether the RAN node supports S-MBR enforcement, information that indicates whether S-MBR enforcement is feasible at the RAN node for the PDU session, or both.
In one embodiment, the information comprised in the response comprises a slice maximum bit rate enforcement indicator.
In one embodiment, the response is a NGAP message.
In one embodiment, the response is a PDU session response setup response, a PDU session resource modify response, a PDU session resource notify, an initial UE context setup response, or a handover request acknowledge.
In one embodiment, the core network node is an AMF.
Corresponding embodiments of a RAN node for a RAN of a cellular communications system are also disclosed. In one embodiment, a RAN node or a RAN of a cellular communications system is adapted to receive a message from a core network node in a core network of the cellular communications system, the message comprising S-MBR information for one or more network slices. The RAN node is further adapted to send a response to the core network node, the response comprising information that explicitly or implicitly indicates whether the RAN node supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node.
In one embodiment, a RAN node or a RAN of a cellular communications system comprise processing circuitry configured to cause the RAN node to receive a message from a core network node in a core network of the cellular communications system, the message comprising S-MBR information for one or more network slices. The processing circuitry is further configured to cause the RAN node to send a response to the core network node, the response comprising information that explicitly or implicitly indicates whether the RAN node supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node.
The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.
The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.
Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.
Radio Node: As used herein, a “radio node” is either a radio access node or a wireless communication device.
Radio Access Node or RAN Node: As used herein, a “radio access node” or “radio network node” or “radio access network node” or “RAN node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.
Core Network Node: As used herein, a “core network node” is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.
Communication Device: As used herein, a “communication device” is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.
Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (IoT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.
Network Node: As used herein, a “network node” is any node that is either part of the RAN or the core network of a cellular communications network/system.
Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.
Note that, in the description herein, reference may be made to the term “cell”; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.
There currently exist certain challenge(s). As discussed above, the conclusions to Key Issue #3 in the 3GPP study item on enhancements for network slicing phase 2 is documented in 3GPP Technical Report (TR) 23.700-40 v. 17.0.0 indicate that the Slice Maximum Bit Rate (S-MBR) can be enforced both (a) at the RAN and (b) the PCF, where the PCF ensures that the Quality of Service (QOS) parameters for the Protocol Data Unit (PDU) sessions of a UE in a network slice do not exceed the S-MBR. Thus, there are two mechanisms to enforce the S-MBR; however, there is no way to control which mechanism should be used for a given UE. Thus, it may happen that either none of the mechanisms are enforced or both are enforced for the same UE.
Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. Systems and methods are disclosed herein for determining which mechanism to apply to enforce the S-MBR for a UE. In one embodiment, the mechanism to apply to enforce the S-MBR for a UE is determined as follows:
The following alternatives can be used to determine if the RAN (e.g., a RAN node or base station such as a gNB associated to the UE) supports S-MBR enforcement:
In one embodiment, the AMF notifies the SMF and the PCF on the S-MBR support of the RAN. The SMF checks if the S-MBR enforcement is supported and, if so, the SMF selects the same PCF for all PDU sessions of a UE in the same S-NSSAI.
In one embodiment, the PCF checks the S-MBR support of the RAN, then if S-MBR is not supported in RAN, the PCF ensures that the QoS parameters for the PDU sessions of a UE in a Slice does not exceed the S-MBR for the UE.
Certain embodiments may provide the technical advantage of enabling the control of the S-MBR per UE if the RAN does not support the enforcement of the S-MBR per UE.
The base stations 102 and the low power nodes 106 provide service to wireless communication devices 112-1 through 112-5 in the corresponding cells 104 and 108. The wireless communication devices 112-1 through 112-5 are generally referred to herein collectively as wireless communication devices 112 and individually as wireless communication device 112. In the following description, the wireless communication devices 112 are oftentimes UEs and as such sometimes referred to herein as UEs 112, but the present disclosure is not limited thereto.
Seen from the access side the 5G network architecture shown in
Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE 112 and AMF 200. The reference points for connecting between the AN 102 and AMF 200 and between the AN 102 and UPF 214 are defined as N2 and N3, respectively. There is a reference point, N11, between the AMF 200 and SMF 208, which implies that the SMF 208 is at least partly controlled by the AMF 200. N4 is used by the SMF 208 and UPF 214 so that the UPF 214 can be set using the control signal generated by the SMF 208, and the UPF 214 can report its state to the SMF 208. N9 is the reference point for the connection between different UPFs 214, and N14 is the reference point connecting between different AMFs 200, respectively. N15 and N7 are defined since the PCF 210 applies policy to the AMF 200 and SMF 208, respectively. N12 is required for the AMF 200 to perform authentication of the UE 112. N8 and N10 are defined because the subscription data of the UE 112 is required for the AMF 200 and SMF 208.
The 5GC network aims at separating UP and CP. The UP carries user traffic while the CP carries signaling in the network. In
The core 5G network architecture is composed of modularized functions. For example, the AMF 200 and SMF 208 are independent functions in the CP. Separated AMF 200 and SMF 208 allow independent evolution and scaling. Other CP functions like the PCF 210 and AUSF 204 can be separated as shown in
Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs.
Some properties of the NFs shown in
An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.
For the PDU session establishment for home routed scenarios, the AMF 200 reports RAN support of S-MBR to the V-SMF, and then the V-SMF reports this information to the H-SMF.
This can also be a capability of the Public Land Mobile Network (PLMN) in non-roaming. Then, the RAN support for S-MBR can be reported by the SMF 208 to the PCF 210 or a capability of the Visited PLMN (VPLMN) when roaming. Then, it is reported by the V-SMF to the H-SMF.
While not necessary for understanding embodiments of the present disclosure, for additional details of the steps and aspects of the procedure of
In one example embodiment, the SMF services are extended as follows where the extensions are indicated with underlined text:
In one example embodiment, the PCF services are extended as follows where the extensions are indicated by underlined text:
In case the RAN capabilities to support S-MBR change in the PDU session due to, e.g., mobility, the Nsmf and Npcf service operations for Update will transfer the S-MBR support/feasibility, i.e., Slice Maximum Bit Rate Enforcement Indicator, to the PCF 210.
An alternative method is that the AMF receives the Slice Maximum Bit Rate Enforcement Indicator from NG-RAN indicating whether the S-MBR enforcement is not supported or not feasible or supported and not feasible or supported and feasible. The AMF then decides to request the PCF to enforce the Slice MBR, if the indication from RAN is that S-MBR enforcement cannot be carried out at the RAN. This requires the AMF to send, in the Nsmf_PDUSession_CreateSMContext service operation (e.g., in step 3 of the process of
The PCF 210 determines whether a mechanism for enforcing the S-MBR of the UE 112 is to be performed by the PCF 210 based on whether the RAN node associated to the UE 112 supports S-MBR enforcement, as indicated by the received message or step 500 (step 502). The PCF 210 then operates in accordance with the determination made in step 502 (step 504). More specifically, if the RAN supports (and is thus able to perform) S-MBR enforcement, the PCF 210 does not apply the mechanism to enforce the S-MBR for the UE 112 (e.g., the PCF 210 does not monitor the QoS parameters of all PDU sessions of the UE 112 in the network slice are within the limits of the S-MBR for the UE 112). However, if the RAN does not support S-MBR enforcement, the PCF 210 applies the mechanism to enforce the S-MBR for the UE 112 (e.g., the PCF 210 monitors the QoS parameters of all PDU sessions of the UE 112 in the network slice are within the limits of the S-MBR for the UE 112).
Note that while the PCF 210 is described here as the core network node that determines whether to apply a mechanism(s) to enforce the S-MBR in the core network or in the RAN in the example embodiments described herein, this decision may alternatively be made by some other network node such as, e.g., the AMF 200 or the SMF 208. This other network node may, e.g., then inform, instruct, or configure the PCF 210 to enforce the S-MBR.
The following text described option #2 described in the Summary section above (i.e., the option where Legacy (non-supporting) gNB triggers failure of the procedure where S-MBR is included, the response message informs the AMF that it happened due to unknown IE).
The Initial Context Setup Request message is sent by the AMF 200 to the NG-RAN node (e.g., the base station 102 or gNB) to request the setup of a UE context. In one example embodiment, the Initial Context Setup Request message includes the new Information Element (IE) S-MBR that is not supported by the NG-RAN node, as shown below as a revision to Section 9.2.2.1 of 3GPP TS 38.413V 16.7.0.
In this embodiment, the S-MBR signaled from the core network (CN) to the RAN is intended to refer only to network slices for which PDU Sessions with an active user plane are established at the RAN. Namely, PDU Sessions to which user plane (UP) resources have been allocated.
In another embodiment, the S-MBR may be signaled to the RAN for network slices that do not have an active UP connection at the RAN. For example, the S-MBR may be signaled for network slices included in the list of slices configured for the UE, also known as Configured NSSAI, or for network slices included in the list of slices allowed for the UE, also known as Allowed NSSAI.
S-MBR List
0 . . . 1
YES
reject
>S-MBR Value
1 . . .
List Item
<MaxNumberofS-MBRvalues>
>>S-NSSAI
M
9.3.1.24
>>S-MBR Value
M
9.3.1.x
In the Initial UE Context Setup Request message, the S-MBR IE can be encoded with Criticality set to ‘YES’ and Assigned criticality set to ‘reject’. In this case, a NG-RAN node that does not support that IE will respond to the AMF 200 with an Initial Context Setup Failure message indicating in the Criticality Diagnostics that the reason for failure is due to unknown new IE S-MBR.
The Initial Context Setup Failure message is sent by the NG-RAN node (e.g., the base station 102 or gNB) to the AMF 200 to indicate that the setup of the UE context was unsuccessful. In one example embodiment, the Initial Context Setup Request message includes the following information, as defined in Section 9.2.2.3 of 3GPP TS 38.413V 16.7.0:
In one embodiment, the UE-Slice MBR IE defines the rate limit per UE per slice as specified in 3GPP 23.501. In one example embodiment, this is expressed as the following addition to 3GPP TS 38.413V 16.7.0:
It should be noted that addition of the S-MBR information in the Initial Context Setup Request as described above with respect to
An alternative embodiment concerning how the RAN (e.g., RAN nodes such as, e.g., a base station 102) can inform the AMF 200 about the fact that the S-MBR associated to a given S-NSSAI and/or PDU Session cannot be enforced is explained below with respect to
As illustrated in
After receiving an S-MBR for an S-NSSAI, the RAN node is able to reply to the AMF 200 with information indicating that the S-MBR enforcement is supported/not-supported and/or that S-MBR enforcement is feasible/not-feasible (step 902). The latter is achieved by allowing the RAN node to signal, for each PDU Session for which an active user plane is established, an information element (IE) expressing that enforcement of the S-MBR is supported or not-supported or feasible or not feasible or supported but not feasible. The AMF 200 may then perform one or more actions based on the received IE from the RAN node (step 904). As discussed below in further detail, the RAN node may, in some embodiments, subsequently send information to the AMF that indicates an update for whether S-MBR enforcement is supported/non-supported at the RAN node and/or that S-MBR enforcement is feasible/not-feasible at the RAN node (step 906). For example, if the RAN node indicates that S-MBR enforcement is supported and feasible in step 902 but subsequently something changes such that S-MBR enforcement is no longer supported and/or no longer feasible, the information sent in step Y906 would indicate that S-MBR enforcement is no longer supported and/or no longer feasible.
An example of how the IE of step 902 (and optionally of step 906) from the RAN node can be encoded is shown below:
In the example above, it is assumed that, if the IE is not received by the AMF, the RAN node does not support the S-MBR enforcement indicator IE and the functionality associated to it. On the contrary, if the IE is received by the AMF, then the AMF can learn that
In an alternative example, the IE above may only include values “not-feasible, not-supported”, with the understanding that, if the AMF does not receive the IE, it means that the RAN is able to enforce the S-MBR. The latter may need to be complemented with a configuration at the AMF (e.g., from the OAM system) indicating whether a RAN node supports the S-MBR enforcement indicator IE and its functionality. With such configuration, the AMF would be able to distinguish between cases when the RAN does not signal the Slice Maximum Bit Rate Enforcement Indicator because the S-MBR could be enforced and cases when cases when the RAN does not signal the Slice Maximum Bit Rate Enforcement Indicator because the IE and its functionality is supported.
Examples of how the RAN may signal (e.g., in step 902) an indication of supported/not-supported/feasible/not-feasible S-MBR enforcement to the AMF are described below.
In one example, it is assumed that the Slice Maximum Bit Rate Enforcement Indicator IE described above is included as part of relevant NGAP messages from RAN to AMF. This IE may be added in messages from RAN to the AMF where successful establishment of user plane resources for a PDU session is signaled. Such messages are described in the example modified sections of 3GPP TS 38.413V 16.7.0 below. If the Slice Maximum Bit Rate Enforcement Indicator IE is included in one of the messages indicated below, the AMF, if supported, deduces that enforcement of the slice maximum bit rate is not possible for the concerned PDU Session and S-NSSAI and it may use this information to determine whether alternative slice maximum bit rate methods can be enabled, i.e., via PCF.
>>Slice
O
9.3.1.y
Maximum Bit
Rate
Enforcement
Indicator
>>Slice
O
9.3.1.y
Maximum Bit
Rate
Enforcement
Indicator
When RAN replies to CN/AMF that enforcement of S-MBR is not feasible (e.g., in step 902 of the process of
>>Slice
O
9.3.1.y
Maximum Bit
Rate
Enforcement
Indicator
>>Slice
O
9.3.1.y
Maximum Bit
Rate
Enforcement
Indicator
>>Slice
O
9.3.1.y
Maximum Bit
Rate
Enforcement
Indicator
In another example, the RAN may signal to the AMF a list of S-NSSAIs for which an active use plane is in place for the UE and for each of such S-NSSAIs the RAN may signal to the AMF an indication of whether enforcement of the S-MBR is supported/not-supported/feasible/not-feasible.
In this example, functions 1110 of the network node 1000 described herein (e.g., one or more functions of a base station 102 or 106 or a network node that implements all or part of the functionality of the base station 102 or gNB or one or more functions of a network node that implements all or a part of the functionality of a NF such as, e.g., the AMF 200, SMF 208, or PCF 210, as described herein) are implemented at the one or more processing nodes 1100 or distributed across the one or more processing nodes 1100 and the control system 1002 and/or the radio unit(s) 1010 in any desired manner. In some particular embodiments, some or all of the functions 1110 of the network node 1000 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 1100. Notably, in some embodiments, the control system 1002 may not be included, in which case the radio unit(s) 1010 communicate directly with the processing node(s) 1100 via an appropriate network interface(s).
In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the network node 1000 or a node (e.g., a processing node 1100) implementing one or more of the functions 1110 of the network node 1000 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).
Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).
Some example embodiments of the present disclosure are as follows:
Embodiment 1: A method performed in a core network (110) of a cellular communications system (100), the method comprising:
Embodiment 2: The method of embodiment 1 wherein:
Embodiment 3: The method of embodiment 1 wherein:
Embodiment 4: The method of any of embodiments 1 to 3 wherein, at the AMF (200), obtaining (
Embodiment 5: The method of embodiment 4 wherein the other network node is an Operations and Management, OAM, node.
Embodiment 6: The method of any of embodiments 1 to 3 wherein, at the AMF (200), obtaining (
Embodiment 7: The method of embodiment 6 wherein the message that indicates failure of a procedure where S-MBR is included in an initial context setup failure message.
Embodiment 8: The method of any of embodiments 1 to 3 wherein, at the AMF (200), obtaining (
Embodiment 9: The method of embodiment 8 wherein receiving the indication from the RAN node (102) comprises receiving the S-MBR that is associated with a specific S-NSSAI that can be enforced or some other kind of ‘ack’ in an appropriate message.
Embodiment 10: The method of embodiment 8 wherein receiving the indication from the RAN node (102) comprises receiving the indication during a NG-setup procedure.
Embodiment 11: The method of any of embodiments 1 to 10 wherein the message sent from the AMF (200) to the SMF (208) that comprises the indication of whether the RAN node (102) supports S-MBR enforcement is a Nsmf_PDUSession_CreateSMContext Request message.
Embodiment 12: The method of embodiment 11 further comprising, at the SMF (208), selecting (
Embodiment 13: A method performed by an Access and Mobility Management Function, AMF, (200) in a core network (110) of a cellular communications system (100), the method comprising: obtaining (
Embodiment 14: The method of embodiment 13 wherein obtaining (
Embodiment 15: The method of embodiment 14 wherein the other network node is an Operations and Management, OAM, node.
Embodiment 16: The method of embodiment 13 wherein obtaining (
Embodiment 17: The method of embodiment 16 wherein the message that indicates failure of a procedure where S-MBR is included in an initial context setup failure message.
Embodiment 18: The method of embodiment 13 wherein obtaining (
Embodiment 19: The method of embodiment 18 wherein receiving the indication from the RAN node (102) comprises receiving the S-MBR that is associated with a specific S-NSSAI that can be enforced or some other kind of ‘ack’ in an appropriate message.
Embodiment 20: The method of embodiment 18 wherein receiving the indication from the RAN node (102) comprises receiving the indication during a NG-setup procedure.
Embodiment 21: The method of any of embodiments 13 to 20 wherein the message sent from the AMF (200) to the SMF (208) that comprises the indication of whether the RAN node (102) supports S-MBR enforcement is a Nsmf_PDUSession_CreateSMContext Request message.
Embodiment 22: A method performed by a Policy and Control Function, PCF, (210) in a core network (110) of a cellular communications system (100), the method comprising: receiving (
Embodiment 23: The method of embodiment 22 wherein: the message received at the PCF (210) comprises information that indicates that that RAN node (102) supports S-MBR enforcement; making (602) the determination at the PCF (210) comprises making (602) the determination to not apply the mechanism to enforce S-MBR at the PCF (210); and operating (604) in accordance with the determination comprises refraining from applying the mechanism to enforce S-MBR at the PCF (210).
Embodiment 24: The method of embodiment 22 wherein: the message received at the PCF (210) comprises information that indicates that that RAN node (102) does not support S-MBR enforcement; making (602) the determination at the PCF (210) comprises making (602) the determination to apply the mechanism to enforce S-MBR at the PCF (210); and operating (604) in accordance with the determination comprises applying the mechanism to enforce S-MBR at the PCF (210).
Embodiment 25: A network node (1000) adapted to perform the method of any of embodiments 13 to 24.
Embodiment 26: A network node (1000) comprising processing circuitry (704; 804) configured to cause the network node (1000) to perform the method of any of embodiments 13 to 24.
Embodiment 27: A method performed in a cellular communications system (100), the method comprising:
Embodiment 28: The method of embodiment 27 wherein the message is a message associated to signaling or updating of a UE context of an associated UE.
Embodiment 29: The method of embodiment 27 wherein the message is a message associated to signaling of a PDU session modification.
Embodiment 30: The method of embodiment 27 further comprising, at the RAN node (102), sending (602; 902) a response to the core network node (200), the response comprising information that explicitly or implicitly indicates whether the RAN node (102) supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node (102).
Embodiment 31: The method of embodiment 30 wherein the message is an Initial UE Context Setup Request message and the response is an Initial UE Context Setup Failure message.
Embodiment 32: The method of embodiment 31 wherein the S-MBR information comprises S-MBR value(s) for network slices for which PDU sessions with an active user plane are established at the RAN node.
Embodiment 33: The method of embodiment 31 or 32 wherein the S-MBR information comprises S-MBR value(s) for network slices that do not have an active user plane connection established at the RAN node.
Embodiment 34: The method of any of embodiments 30 to 33 wherein the information comprised in the response comprises information that indicates whether the RAN node (102) supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node (102) for a particular network slice.
Embodiment 35: The method of any of embodiments 30 to 34 wherein the information comprised in the response comprises information that indicates whether the RAN node (102) supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node (102) for a particular PDU session.
Embodiment 36: The method of any of embodiments 30 to 33 wherein the information comprised in the response comprises, for each PDU session of one or more PDU sessions for which an active user plane is established at the RAN node, information that indicates whether the RAN node (102) supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node (102) for the PDU session.
Embodiment 37: The method of any of embodiments 30 to 36 wherein the information comprised in the response comprises a slice maximum bit rate enforcement indicator.
Embodiment 38: The method of any of embodiments 30 to 37 wherein the response is a NGAP message.
Embodiment 39: The method of any of embodiments 30 to 37 wherein the response is a PDU session response setup response, a PDU session resource modify response, a PDU session resource notify, an initial UE context setup response, or a handover request acknowledge.
Embodiment 40: The method of any of embodiments 30 to 39 further comprising, at the core network node (200), performing one or more actions based on the information comprised in the response.
Embodiment 41: The method of any of embodiments 27 to 40 wherein the core network node (200) is an AMF (200).
Embodiment 42: A method performed by a core network node (200) in a core network (110) of the cellular communications system (100), the method comprising: sending (600; 700; 900) a message to a radio access network, RAN, node (102) in a RAN of the cellular communications system (100), the message comprising slice-maximum bit rate, S-MBR, information for one or more network slices.
Embodiment 43: The method of embodiment 42 wherein the message is a message associated to signaling or updating of a UE context of an associated UE.
Embodiment 44: The method of embodiment 42 wherein the message is a message associated to signaling of a PDU session modification.
Embodiment 45: The method of embodiment 42 further comprising receiving (602; 902) a response from the RAN node (102), the response comprising information that explicitly or implicitly indicates whether the RAN node (102) supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node (102).
Embodiment 46: The method of embodiment 45 wherein the message is an Initial UE Context Setup Request message and the response is an Initial UE Context Setup Failure message.
Embodiment 47: The method of embodiment 46 wherein the S-MBR information comprises S-MBR value(s) for network slices for which PDU sessions with an active user plane are established at the RAN node.
Embodiment 48: The method of embodiment 46 or 47 wherein the S-MBR information comprises S-MBR value(s) for network slices that do not have an active user plane connection established at the RAN node.
Embodiment 49: The method of any of embodiments 45 to 48 wherein the information comprised in the response comprises information that indicates whether the RAN node (102) supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node (102) for a particular network slice.
Embodiment 50: The method of any of embodiments 45 to 49 wherein the information comprised in the response comprises information that indicates whether the RAN node (102) supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node (102) for a particular PDU session.
Embodiment 51: The method of any of embodiments 45 to 48 wherein the information comprised in the response comprises, for each PDU session of one or more PDU sessions for which an active user plane is established at the RAN node, information that indicates whether the RAN node (102) supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node (102) for the PDU session.
Embodiment 52: The method of any of embodiments 45 to 51 wherein the information comprised in the response comprises a slice maximum bit rate enforcement indicator.
Embodiment 53: The method of any of embodiments 45 to 52 wherein the response is a NGAP message.
Embodiment 54: The method of any of embodiments 45 to 52 wherein the response is a PDU session response setup response, a PDU session resource modify response, a PDU session resource notify, an initial UE context setup response, or a handover request acknowledge.
Embodiment 55: The method of any of embodiments 45 to 54 further comprising performing one or more actions based on the information comprised in the response.
Embodiment 56: The method of any of embodiments 42 to 55 wherein the core network node (200) is an AMF (200).
Embodiment 57: A method performed by a radio access network, RAN, node (102) in a RAN of the cellular communications system (100), the method comprising receiving (600; 700; 900) a message from a core network node (200) in a core network (110) of the cellular communications system (100), the message comprising slice-maximum bit rate, S-MBR, information for one or more network slices.
Embodiment 58: The method of embodiment 57 wherein the message is a message associated to signaling or updating of a UE context of an associated UE.
Embodiment 59: The method of embodiment 57 wherein the message is a message associated to signaling of a PDU session modification.
Embodiment 60: The method of embodiment 57 further comprising sending (602; 902) a response to the core network node (200), the response comprising information that explicitly or implicitly indicates whether the RAN node (102) supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node (102).
Embodiment 61: The method of embodiment 60 wherein the message is an Initial UE Context Setup Request message and the response is an Initial UE Context Setup Failure message.
Embodiment 62: The method of embodiment 61 wherein the S-MBR information comprises S-MBR value(s) for network slices for which PDU sessions with an active user plane are established at the RAN node.
Embodiment 63: The method of embodiment 61 or 62 wherein the S-MBR information comprises S-MBR value(s) for network slices that do not have an active user plane connection established at the RAN node.
Embodiment 64: The method of any of embodiments 60 to 63 wherein the information comprised in the response comprises information that indicates whether the RAN node (102) supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node (102) for a particular network slice.
Embodiment 65: The method of any of embodiments 60 to 64 wherein the information comprised in the response comprises information that indicates whether the RAN node (102) supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node (102) for a particular PDU session.
Embodiment 66: The method of any of embodiments 60 to 63 wherein the information comprised in the response comprises, for each PDU session of one or more PDU sessions for which an active user plane is established at the RAN node, information that indicates whether the RAN node (102) supports S-MBR enforcement and/or whether S-MBR enforcement is feasible at the RAN node (102) for the PDU session.
Embodiment 67: The method of any of embodiments 60 to 66 wherein the information comprised in the response comprises a slice maximum bit rate enforcement indicator.
Embodiment 68: The method of any of embodiments 60 to 67 wherein the response is a NGAP message.
Embodiment 69: The method of any of embodiments 60 to 67 wherein the response is a PDU session response setup response, a PDU session resource modify response, a PDU session resource notify, an initial UE context setup response, or a handover request acknowledge.
Embodiment 70: The method of any of embodiments 27 to 69 wherein the core network node (200) is an AMF (200).
Embodiment 71: A network node (1000) adapted to perform the method of any of embodiments 42 to 70.
Embodiment 72: A network node (1000) comprising processing circuitry (1004; 1104) configured to cause the network node (1000) to perform the method of any of embodiments 42 to 70.
Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.
This application claims the benefit of provisional patent application Ser. No. 63/173,694, filed Apr. 12, 2021, and provisional patent application Ser. No. 63/257,831, filed Oct. 20, 2021, the disclosures of which are hereby incorporated herein by reference in their entireties.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/IB2022/053324 | 4/8/2022 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63257831 | Oct 2021 | US | |
| 63173694 | Apr 2021 | US |
