Per radio access technology or cross radio access technology aggregate rate limitation

Abstract

A method of rate limiting per radio access technology or across radio access technologies is provided that includes receiving a request related to a session management (SM) policy association for protocol data unit (PDU) session establishment / modification for a user equipment (UE) associated with a network slice. The method includes receiving information indicating a remaining maximum bit rate associated with a group of one or more PDU sessions associated with the network slice. The remaining maximum bit rate has a value that is specific to a radio access technology (RAT) type of a radio access network (RAN) to which the UE is connected or a value that is common across at least two RAT types including the RAT type of the RAN. And the method includes making a policy decision to accept or reject the establishment / modification of the SM policy association based on whether the value of the remaining maximum bit rate is higher than a value of a granted maximum bit rate for the PDU session.

Description

Technical Field

[0001] This disclosure relates generally to telecommunications, and more specifically to the quality of service in telecommunications systems. Background Technology

[0002] A telecommunications system can be viewed as a facility that enables communication between two or more entities, such as between two user equipments (UEs), between a UE and a base station, between two base stations, between a UE and a network function of a communication network, and / or between a base station and other nodes. A telecommunications system may include a communication network and one or more UEs. A communication session may include, for example, communication of data used to carry communications such as voice, video, email, text messages, multimedia, and / or content data. Non-limiting examples of services provided include two-way or multi-way calling, data communication or multimedia services, and access to data network systems such as the Internet.

[0003] In telecommunications systems that include wireless communication networks, at least a portion of a communication session between at least two stations occurs via a wireless link. Examples of wireless communication networks include Public Land Mobile Networks (PLMNs), satellite-based communication networks, and various wireless local networks, such as Wireless Local Area Networks (WLANs). Some wireless communication networks can be divided into cells and are therefore often referred to as cellular networks.

[0004] Users can access the telecommunications system through appropriate communication equipment or terminals. The user's communication equipment may be referred to as user equipment (UE) or user device. The communication equipment is provided with appropriate signal receiving and transmitting means to enable communication, such as enabling access to a communication network or direct communication with other users. The communication equipment can access a carrier provided by, for example, a base station in a cell, and transmit and / or receive communication on that carrier.

[0005] Telecommunication systems and associated equipment typically operate according to a given standard or specification that defines what the various entities associated with the communication system are allowed to do and how their operations should be implemented. The communication protocols and / or parameters used for the connections between the various entities are also usually defined. An example of a telecommunications system is the Universal Mobile Telecommunications System (UMTS). Other examples of telecommunications systems are Long Term Evolution (LTE), LTE-Advanced, and so-called 5G or New Radio (NR) networks. NR is being standardized by the 3rd Generation Partnership Project (3GPP). Summary of the Invention

[0006] The example implementations of this disclosure relate to telecommunications, and more specifically to quality of service in telecommunications systems. This disclosure includes, but is not limited to, the following example implementations.

[0007] Some example implementations provide an apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute the instructions such that the apparatus at least: receives a request relating to a session management (SM) policy association for establishing or modifying a Protocol Data Unit (PDU) session for a User Equipment (UE) associated with a network slice; receives information indicating a remaining maximum bit rate associated with a group of one or more PDU sessions associated with a network slice, the remaining maximum bit rate having: a value specific to the Radio Access Network (RAN) to which the UE is connected, or a value common to at least two RAT types including the RAN; makes a policy decision to accept or reject the establishment or modification of the SM policy association based on whether the value of the remaining maximum bit rate is higher than the value of the authorized maximum bit rate for the PDU session; and sends a response to the request, the response including information indicating the policy decision.

[0008] Some example implementations provide a method comprising: receiving a request relating to a session management (SM) policy association for establishing or modifying a Protocol Data Unit (PDU) session for a User Equipment (UE) associated with a network slice; receiving information indicating a remaining maximum bit rate associated with a group of one or more PDU sessions associated with a network slice, the remaining maximum bit rate having: a value specific to the Radio Access Technology (RAT) type of the Radio Access Network (RAN) to which the UE is connected, or a value common to at least two RAT types including the RAN; making a policy decision to accept or reject the establishment or modification of the SM policy association based on whether the value of the remaining maximum bit rate is higher than the value of the authorized maximum bit rate used for the PDU session; and sending a response to the request, the response including information indicating the policy decision.

[0009] Some example implementations provide an apparatus including: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute the instructions such that the apparatus at least: discovers a policy control network function (NF) responsible for: policy control of network slices for at least two radio access technology (RAT) types, the at least two RAT types including: the RAT type of the radio access network (RAN) to which the user equipment (UE) is connected; and sends a request to the policy control NF, the request being related to the establishment of a protocol data unit (PDU) session. The request relates to a modified Session Management (SM) policy association for a PDU session associated with a network slice; and to receiving a response to the request, the response including information indicating: accepting or rejecting a policy decision to establish or modify an SM policy association, the policy decision being made by a policy control NF based on the remaining maximum bit rate associated with a group of one or more PDU sessions associated with a network slice, the remaining maximum bit rate having: a value specific to the RAT type of the RAN to which the UE is connected, or a value common to at least two RAT types including the RAN's RAT type.

[0010] Some example implementations provide a method comprising: discovering a policy control network function (NF) responsible for: policy control of a network slice for at least two radio access technology (RAT) types, the at least two RAT types including: the RAT type of a radio access network (RAN) to which a user equipment (UE) is connected; sending a request to the policy control NF relating to a session management (SM) policy associated with the establishment or modification of a protocol data unit (PDU) session for a UE associated with the network slice; and receiving a response to the request including information indicating: a policy decision to accept or reject the establishment or modification of the SM policy association, the policy decision being made by the policy control NF based on the remaining maximum bit rate associated with a group of one or more PDU sessions associated with the network slice, the remaining maximum bit rate having: a value specific to the RAT type of the RAN to which the UE is connected, or a value common to at least two RAT types including the RAN's RAT type.

[0011] These and other features, aspects, and advantages of this disclosure will become apparent from the following detailed description taken in conjunction with the accompanying drawings, which will be briefly described below. This disclosure includes any combination of two, three, four, or more features or elements set forth herein, whether such features or elements are explicitly combined or otherwise stated in the specific example implementations described herein. This disclosure is intended to be read holistically, such that any separable feature or element of this disclosure should be considered composable in any aspect and example implementation thereof, unless the context of this disclosure explicitly indicates otherwise.

[0012] Therefore, it should be understood that the invention is provided merely for the purpose of summarizing some exemplary implementations in order to provide a basic understanding of some aspects of this disclosure. Consequently, it should be understood that the above-described exemplary implementations are merely examples and should not be construed as limiting the scope or spirit of this disclosure in any way. Other exemplary implementations, aspects, and advantages will become apparent from the following detailed description taken in conjunction with the accompanying drawings, which illustrate by way of example the principles of some of the described exemplary implementations. Attached Figure Description

[0013] Having thus described the exemplary implementation of this disclosure in such a general manner, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and in which:

[0014] Figure 1 The illustration shows a telecommunications system implemented according to some examples of this disclosure, including one or more public land mobile networks (PLMNs) coupled to one or more external data networks;

[0015] Figure 2 The diagram illustrates a PLMN implementation based on some examples;

[0016] Figure 3 This is a diagram of the process for establishing access and mobility (AM) policy associations based on some examples, during which aggregate rate-limited quality of service (QoS) parameters for user equipment (UE) for each radio access technology (RAT) can be configured and provided to the mobility management (MM) network function (NF).

[0017] Figure 4 This is a block diagram based on some examples of the process for providing aggregate rate limiting QoS parameters from the MM NF to the radio access network (RAN) for execution at the RAN;

[0018] Figure 5 It is a block diagram of a process for AM policy association modification initiated by MM NF, based on some examples, and the value of the aggregation rate limit QoS parameter can be changed during the process;

[0019] Figure 6 This is a block diagram of the process for establishing Session Management (SM) policy associations, implemented according to some examples. During this process, the aggregate rate limit QoS parameters for Protocol Data Unit (PDU) sessions of the UE for each RAT can be configured and provided to the SM NF.

[0020] Figure 7 , 8 1, 2, 3, and 4 are block diagrams of the corresponding procedures for executing one or more aggregate rate limiting QoS parameters for each RAT or a network slice across a RAT, implemented according to various examples.

[0021] Figure 14A and Figure 14B It is a flowchart illustrating the steps in a method performed by a network function (NF) service consumer, implemented according to various examples;

[0022] Figure 15A and Figure 15B It is a flowchart illustrating the steps in the methods executed by the NF service producer, implemented according to various examples;

[0023] Figure 16 It is a flowchart illustrating the steps in the methods implemented based on various examples;

[0024] Figure 17A and Figure 17B It is a flowchart illustrating the steps in the methods implemented based on various examples; and

[0025] Figure 18 The diagram illustrates a device implemented based on some examples. Detailed Implementation

[0026] Some implementations of this disclosure will now be described in more detail below with reference to the accompanying drawings, which show, however, some, but not all, implementations of this disclosure. In fact, various implementations of this disclosure may be practiced in many different forms and should not be construed as limited to the implementations described herein; rather, these exemplary implementations are provided so that this disclosure will be exhaustive and complete, and will fully convey the scope of this disclosure to those skilled in the art. The same reference numerals refer to the same elements throughout the drawings.

[0027] Unless otherwise specified or clearly apparent from the context, references to first, second, etc., should not be construed as implying a particular order. A feature described as being above another feature (unless otherwise stated or clearly apparent from the context) may also be described as being below, and vice versa; similarly, a feature described as being to the left of another feature may also be described as being to the right, and vice versa. Furthermore, although quantitative measurements, values, geometric relationships, etc., may be referred to herein, any one or more of these (if not all of them) may be absolute or approximate, unless otherwise stated, to account for acceptable variations that may occur, such as deviations due to engineering tolerances, etc.

[0028] As used herein, unless otherwise specified or clearly apparent from the context, "OR" of operand sets is "inclusive OR," and therefore true only if one or more operands are true, unlike "XOR," which is false when all operands are true. Thus, for example, "[A] OR [B]" is true if [A] is true, or if [B] is true, or if both [A] and [B] are true. Furthermore, the articles "a" and "an" mean "one or more," unless otherwise stated or clearly apparent from the context as referring to the singular form. Additionally, it should be understood that, unless otherwise stated, the terms "data," "content," "digital content," "information," and similar terms are sometimes used interchangeably. The term "network" can refer to an interconnected group of computers, including clients and servers; and within a network, these computers can be interconnected directly or indirectly in various ways, including via one or more switches, routers, gateways, access points, etc.

[0029] This disclosure discusses telecommunications systems and mobile or cellular networks and their user equipment, and while specific terms may be used, they are broadly applicable to a wide range of technologies. For example, while this disclosure may refer to radio access technologies such as 5G NR and 5G Advanced, it is equally applicable to next-generation radio access technologies such as 6G. The example implementations of this disclosure described herein also refer to Public Land Mobile Networks (PLMNs) and Mobile Network Operators (MNOs), but the example implementations are similarly applicable to Standalone Non-Public Networks (SNPNs). Furthermore, although some examples and figures focus on Radio Access Networks (RANs) and particularly radio access networks operating according to the 3GPP standards for NR (often referred to as 3GPP access or 3GPP access network), the example implementations are applicable to any type of access network. This includes not only 3GPP access networks, but also non-3GPP access networks (such as wired access), untrusted non-3GPP access networks, and trusted non-3GPP access networks using the Radio Access Gateway Function (W-AGF), Non-3GPP Interconnect Function (N3IWF), or Trusted Non-3GPP Gateway Function (TNGF) to connect to the core network of a mobile or cellular network (e.g., 5G core network (5GC) or 6G core network (6GC)).

[0030] Furthermore, as used in this application, the term "circuit system" may refer to one or more or all of the following: (a) a hardware circuit implementation only (such as an implementation only in analog and / or digital circuit systems); (b) a combination of hardware circuits and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuits with software / firmware, and (ii) any part of (multiple) hardware processors (including (multiple) digital signal processors) having software, software, and (multiple) memories, which work together to enable a device (such as a mobile phone or a server) to perform various functions; or (c) (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but the software may be absent when operation does not require the software.

[0031] The foregoing definition of "circuit system" applies to all uses of the term in this application, including in any claim. As another example, as used herein, the term "circuit system" also covers implementations of only hardware circuitry or processors (or processors) or portions thereof and their accompanying software and / or firmware. If applicable to a particular claim element, the term "circuit system" also covers, for example, baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0032] Figure 1 The illustration depicts a telecommunications system 100 implemented according to various examples of this disclosure. The telecommunications system 100 (or system 100) typically includes one or more mobile or cellular networks. For example, as shown, system 100 includes one or more PLMNs 102 coupled to one or more other external data networks 104—particularly including wide area networks (WANs) such as the Internet. As will be understood, the PLMN may be a standalone PLMN including a 5GC, or it may be a non-standalone PLMN including both an evolved packet core (EPC) and a 5GC connected to a RAN.

[0033] Each PLMN 102 includes a core network (CN) 106, such as an EPC, 5GC, or 6GC; and each CN is coupled to one or more RANs 108 implementing one or more Radio Access Technologies (RATs). Examples of these RANs include the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) for 4G LTE, the Next Generation Radio Access Network (NG-RAN) for 5G NR, and a 6G RAN. As used herein, “network equipment” refers to any suitable equipment in the RAN or core network of a telecommunications system. Examples of suitable network equipment are described in more detail below.

[0034] Examples of RATs include 3GPP radio access technologies such as GSM, CDMA2000 1xEV-DO (HRPD), CDMA2000 1x (1xRTT), UTRA, E-UTRA, 5G NR, Advanced 5G, and 6G. Other examples of RATs include IEEE 802 technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.15 (including 802.15.1 (WPAN / Bluetooth), 802.15.4 (Zigbee), and 802.15.6 (WBAN)), Bluetooth, Bluetooth Low Energy (BLE), Ultra Wideband (UWB), etc. Generally, RAT can refer to any 2G, 3G, 4G, 5G, 6G, or higher generation RAT and its different versions, as well as any other RAT that can be deployed to interoperate with such a RAT to provide access to CN 106 of the MNO.

[0035] Telecommunication system 100 also includes one or more communication devices, which may be referred to differently as User Equipment (UE) 110, terminal device, mobile station, etc. The UE is typically a device configured to communicate with network equipment (e.g., an access node of a RAN node such as RAN 108) or one or more other UEs within the telecommunications system. The UE may be a portable computer (e.g., a laptop computer, notebook computer, tablet computer), a mobile phone (e.g., a cellular phone, smartphone), a wearable computer (e.g., a smartwatch), etc. In other examples, the UE may be an Internet of Things (IoT) device, an Industrial IoT (IIoT) device, a vehicle equipped with Vehicle-to-Everything (V2X) communication technology, etc. In some examples, such as those referenced by 3GPP, the UE may be a Narrowband IoT (NB-IoT) device, an enhanced machine-type communication (eMTC) device, a RedCap device, an environmental IoT device, etc.

[0036] In operation, these UEs 110 can connect to one or more RAN nodes of RAN 108 according to their specific RAT, thereby accessing a specific CN 106 of PLMN 102, or accessing one or more external data networks 104 (e.g., the Internet), or services provided by the PLMN. External data networks can provide Internet access or third-party services. For example, the International Telecommunication Union (ITU) has classified 5G mobile network services (e.g., services provided by 5G mobile networks) into three categories: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC) or massive Internet of Things (MIoT).

[0037] In various examples, RAN 108 can be configured to provide one or more macro cells, micro cells, pico cells, femto cells, etc. RAN 108 typically includes one or more RAN nodes that interact with UE 110. In various examples, RAN nodes can be referred to as base stations (BS), access points (AP), base transceiver stations (BTS). Examples of RAN nodes include node B (NB), evolved NB (eNB), macro BS, macro NB (MNB) or macro eNB (MeNB), home BS, home NB (HNB) or home eNB (HeNB), next-generation NB (gNB), enhanced gNB (en-gNB), next-generation eNB (ng-eNB), 6G NB (6gNB), etc. The term “gNB” in 5G NR can correspond to eNB in ​​4G LTE. Additionally, NG-RAN node can refer to gNB or ng-eNB. And unless otherwise stated, gNB in ​​5G NR or 6gNB in ​​6G can sometimes be more generally referred to as (6) gNB or more simply as gNB.

[0038] In some implementations, the operation of a gNB or other RAN node can be distributed or functionally broken down into components including one or more Remote Radio Heads (RRHs) or Radio Units (RUs) and Baseband Units (BBUs); and in some implementations, the BBU can be divided into Centralized Units (CUs) (central nodes) and Distributed Units (DUs) (distributed nodes). A CU can be, for example, a server, host, or node. In some implementations, RRHs / RUs and DUs can be co-located at network devices. The operation of a gNB or RAN node can also be distributed among multiple servers, hosts, or nodes.

[0039] RAN 108 may include some type of network control / management entity responsible for controlling the RAN nodes. The network control / management entity and the RAN nodes may be separate or integrated into a single device. The network control / management entity may include a processing circuitry system configured to perform various management functions for controlling the RAN nodes of RAN 108. The processing circuitry system may be associated with a memory, a computer-readable storage medium, or a data storage device including a database for maintaining the information required for the various management functions.

[0040] Figure 2 The illustration shows an example of a PLMN 102 (such as a 4G LTE, 5G NR, or 6G PLMN) communicating with a UE 110 of a telecommunications system 100 and an external data network 104. As shown, a RAN 108 (e.g., E-UTRAN, NG-RAN, 6G RAN) includes one or more RAN nodes 202 configured to connect one or more UEs to the RAN for access to a CN 106 (e.g., EPC, 5GC, 6GC). In 4G LTE, the UE, E-UTRAN, and EPC are sometimes collectively referred to as an Evolved Packet System (EPS). Similarly, in 5G NR, the UE, NG-RAN, and 5GC are sometimes collectively referred to as a 5G System (5GS). In 6G, the UE, 6G RAN, and 6GC can sometimes be collectively referred to as a 6G System (6GS).

[0041] CN 106 may include multiple network functions (NFs) partitioned between the control plane (CP) and the user plane (UP). Specifically, for example, CN may include NFs for, for example, access and mobility management (MM) 204 (sometimes referred to as MM NF) and session management (SM) 206 (sometimes referred to as SM NF). MM NF may be, for example, a mobility management entity (MME) in EPS, a 5G MM or access and mobility management function (AMF) in 5GS, or a 6G MM in 6GS. Similarly, SM NF may be, for example, a Serving Gateway (SGW) control plane function (SGW-C) and / or a Packet Data Network Gateway (PGW) control plane function (PGW-C) in EPS, a 5G SM or session management function (SMF) in 5GS, or a 6G SM in 6GS.

[0042] CN 106 may also include NFs for receiving and transmitting traffic (e.g., data), which may sometimes be referred to as User Plane Functions (UPFs) 208. In EPS, the UPF may be an SGW User Plane Function (SGW-U) and / or a PGW User Plane Function (PGW-U). CN may include policy control (PC) NFs, such as Policy and Charging Functions (PCFs) 210 (or Policy and Charging Rules Functions (PCRFs) in EPS, etc.). Other examples of suitable NFs include Unified Data Management (UDMs) 212 (or Home Subscriber Server (HSS) in EPS), User or Unified Data Repository (UDRs) 214, Charging Functions (CHFs) 216, Network Repository Functions (NRFs) 218, Network Slice Selection Functions (NSSFs) 220, etc.

[0043] The General Network Slice Template (GST), defined in the Special Group on Mobility (SGMP) specification NG.116, is a set of attributes characterizing a network slice type or service type (a network slice is sometimes simply referred to as a "slice"). This set of attributes includes the maximum downlink throughput for each UE 110, describing the maximum data rate (or bit rate) supported by the network slice for each UE in the downlink, and the maximum uplink throughput for each UE, describing the maximum data rate supported by the network slice for each UE in the uplink. The attribute set also includes the downlink throughput for each network slice, which is related to the aggregated data rate in the downlink for all UEs in the network slice; and the uplink throughput for each network slice, which is related to the aggregated data rate in the uplink for all UEs in the network slice. These attributes are supported in the existing 5G network slicing framework and are considered in the 3GPP standard. In the 5G network slicing framework, network slices can be identified by a single Network Slice Selection Auxiliary Information (S-NSSAI).

[0044] Specifically, for example, the 3GPP standard specifies the number of aggregate rate-limiting Quality of Service (QoS) parameters for each UE 110. For instance, each Protocol Data Unit (PDU) session of the UE can be associated with a session aggregate maximum bit rate (session-AMBR), which can be signaled to the appropriate UPF(s) 208 entities, the UE, and RAN108 (or other access networks). The session-AMBR limits the aggregate bit rate provided by all non-guaranteed bit rate (non-GBR) QoS flows that can be expected to be used across a particular PDU session. The session-AMBR can be measured over an AMBR averaging window that is a normalized value. The session-AMBR may not be applicable to GBR QoS flows.

[0045] As another example, each UE 110 can be associated with a per-UE aggregated maximum bit rate (UE-AMBR), the limit of which can be expected to be the aggregated bit rate provided by all non-GBR QoS flows across the UE. Each RAN 108 (or other access network) can set its UE-AMBR to the sum of the session-AMBRs of all PDU sessions with active UPs to the RAN, but this sum cannot exceed the value of the UE-AMBR received from MM NF 204 (e.g., AMF). The UE-AMBR can be provided to the RAN by the MM NF based on the value of the UE-AMBR of the subscription obtained from UDM 212, or the value of the dynamic service network UE-AMBR (e.g., for roaming subscribers) obtained from PCF 210. If available, the MM NF can provide the RAN with the UE-AMBR provided by the PCF. Similar to session-AMBR, UE-AMBR can be measured over an AMBR averaging window as a normalized value. UE-AMBR may also not be applicable to GBR QoS flows.

[0046] As another example, each group of PDU sessions for UE 110 for the same network slice (S-NSSAI) can be associated with a maximum bit rate per UE per slice (UE-slice-MBR), the limit of which can be expected to be the aggregate bit rate provided across all GBR and non-GBR QoS flows corresponding to multiple PDU sessions for the same slice (S-NSSAI) with an active UP. Each supporting RAN 108 can set its UE-slice-MBR to the sum of session-AMBR and the maximum flow bit rate (MFBR) for all PDU sessions for the network slice (S-NSSAI) with an active UP to the RAN, but this sum cannot exceed the value of the UE-slice-MBR corresponding to the slice (S-NSSAI) received from MM NF 204 (e.g., AMF). Similar to other aggregate rate limiting QoS parameters, UE-slice-MBR can be measured over an AMBR averaging window as a normalized value. The UE-slice-MBR can be an optional parameter provided to the RAN by the MM NF.

[0047] Aggregate rate limiting QoS parameters can be enforced in several different ways. During the establishment or modification of a QoS flow, for example, if the UE-slice-MBR is to be overtaken by a new / modified GBR QoS flow, RAN 108 can determine, based on the allocation and reservation priority (ARP) value of the new / modified GBR QoS flow, whether it can preempt any existing GBR QoS flow in the PDU(multiple) sessions of the UE corresponding to the same S-NSSAI. If this is not possible, the RAN can reject the establishment / modification of the QoS flow.

[0048] The data rate provisioning and constraints used for services are currently common across multiple RATs and may be sufficient to provide QoS and user experience for services offered across RAN 108 based on their specific RAT. However, different RATs (e.g., 5G, 6G) may have different QoS characteristics and enable different user experiences for the same service. Common data rate provisioning and constraints are insufficient to provide differentiated QoS and experience across different RATs and prevent operators from managing UEs with different QoS and Quality of Experience (QoE) across different RATs. Common data rate configuration and constraints for services also lack the flexibility to be used by operators to manage different slices (S-NSSAI) for each RAT, or to manage the same slice (S-NSSAI) for each RAT across RATs with different data rate provisioning and constraints to provide services with different QoS and user experiences.

[0049] Based on the foregoing description, the example implementation of this disclosure provides a solution for configuring, providing, and / or executing one or more aggregated QoS parameters having values ​​specific to the RAT type of the RAN108 to which the UE is connected. Depending on the context, the RAT type may sometimes be more simply referred to as RAT, as each RAT type corresponds to a specific RAT. The solution is described below in the context of RAT types including 5G RAT and 6G RAT; however, it should be understood that the solution can be equally applied to any of a variety of different RAT types, such as those described above. In various examples, the solution can be implemented in scenarios where a generic S-NSSAI is used to identify network slices across 5GS and 6GS, and in scenarios where different S-NSSAIs are used to identify network slices within 5GS and 6GS.

[0050] Some example implementations can be implemented in scenarios where one or more NFs (e.g., PCF210) are compatible with both 5GS and 6GS; and in these example implementations, each of the NFs can support both 5GS and 6GS technologies. Other example implementations can be implemented in scenarios where these NFs are separate or otherwise dedicated to 5GS and 6GS; and in these other example implementations, the 5GS NF can support 5GS technology, while the corresponding 6GS NF can support 6GS technology. In some of these other example implementations, the PCF (e.g., the 5G PCF) responsible for policy control of network slices (S-NSSAI) for at least two RAT types (e.g., 5G, 6G) can be designated as the primary PCF.

[0051] In some example implementations, network slice profile information for network slicing can be specified to indicate the RAT type supported for network slicing (S-NSSAI). In some of these example implementations, the network slice profile information can also indicate the primary RAT type of the RAT, which in some other examples can be used to discover the primary PCF 210. In some examples, this network slice profile information can be carried by: attributes used to provide or limit data rates across different RAT types (e.g., slice coordination information), and slice applicability across multiple RATs.

[0052] According to some example implementations, (multiple) aggregated QoS parameters may include aggregated QoS parameters associated with UE 110, such as the AMBR for each RAT type of UE 110, which may sometimes be referred to as UE- <rat>-AMBR。UE- <rat>The -AMBR value can be specified for RAT type UEs connected to RAN 108. <rat>-AMBR can be configured in PCF210 and / or UDM 212. UE- <rat>-AMBR can be provided to MM NF 204, which can provide parameters to the RAN, which can then be executed at that RAN. In some examples, when the UE changes or moves to a second RAT of a second RAT type (e.g., connects to a second RAN implementing the second RAT), the MM NF can update the PCF using the second RAT type and obtain UE-specific parameters for the second RAT type. <rat>-AMBR's second value.

[0053] In some examples, aggregated QoS parameters may additionally or alternatively include aggregated QoS parameters associated with the UE 110's PDU session, such as the AMBR for the PDU session of each RAT type UE, which may sometimes be referred to as session- <rat>-AMBR。session- <rat>The -AMBR value can be specified for a RAT-type PDU session used by the RAN 108 to which the UE is connected. <rat>-AMBR can be configured in PCF 210. session- <rat>-AMBR can be provided to SM NF 206, and SM NF 206 can provide this parameter to UPF 208 and / or to any UE where this parameter can be executed at that UE.

[0054] In some examples, aggregated QoS parameters may additionally or alternatively include aggregated QoS parameters associated with a group of PDU sessions of UE 110 for network slicing, such as the MBR for each RAT type UE for network slices, which may sometimes be referred to as UE-slice- <rat>-MBR。UE-slice- <rat>The MBR value can be set for a group of (multiple) PDU sessions for a UE connected to a RAT-type network slice of RAN 108. <rat>-MBR can be configured in UDM 212 and provided to the RAN where this parameter can be executed.

[0055] UE-slice- <rat>-MBR can limit the aggregate bit rate that can be expected to be provided across all GBR and non-GBR QoS flows corresponding to multiple PDU sessions for UE 110 in the same slice (S-NSSAI) with active UP of each RAT type on the RAN 108 to which the UE is currently connected. Each supporting RAN can set its UE-slice- <rat>-MBR is configured for the session of GBR QoS flows corresponding to all PDU sessions with active UP networks to that RAN (S-NSSAI). <rat>The sum of AMBR and MFBR, which does not exceed the UE-slice corresponding to the slice (S-NSSAI) received from AMF. <rat>-MBR value. UE-slice- <rat>-MBR can be measured on the AMBR averaging window, which is a standardized value.

[0056] In some examples, aggregated QoS parameters may include one or more aggregated QoS parameters associated with a group of PDU sessions (multiple) for a network slice, either per RAT or across a RAT. These aggregated QoS parameters may include, for example, UE-slice parameters for UE 110. <rat>-MBR. Alternatively or alternatively, for example, aggregated QoS parameters may include MBRs across (multiple) UEs for each RAT type used for network slicing, and / or MBRs across (multiple) UEs for network slicing across RAT types. As described in more detail below, aggregated QoS parameters for network slicing can be implemented in various scenarios involving different combinations of a common S-NSSAI or different S-NSSAIs used to identify network slices, and common or independent NFs (e.g., PCF 210). Again, the example implementation can be described in the context of RAT types including 5G RAT and 6G RAT, but it should be understood that the solution can be equally applied to any of the many different RAT types.

[0057] Figure 3 This is a diagram illustrating the process for establishing access and mobility (AM) policy associations, implemented based on some examples, during which the UE- <rat>-AMBR can be configured and provided to MM NF 204 (e.g., 5G MM / AMF, 6GMM). Although not shown separately, in some examples, UE-slice- <rat>- The MBR can be configured and provided during the same or another similar process used for AM policy association establishment. As shown in the figure, this process involves the MM NF as an NF service consumer and the PCF 210 or V-PCF (usually (V-)PCF) as an NF service producer. The process includes both roaming scenarios involving access to the PLMN (VPLMN) and non-roaming scenarios involving the home PLMN (HPLMN). In roaming scenarios, the V-PCF in the VPLMN interacts with the MM NF. In non-roaming scenarios, the role of the V-PCF is performed by the PCF in the HPLMN.

[0058] As shown in step 301A, UE- <rat>-AMBR can be configured in (V-)PCF 210, and the value of the parameter can be obtained from (V-)PCF 210 by MM NF 204, as described below. Alternatively or alternatively, in some examples, as shown at step 301B, UE- <rat>-AMBR can be configured in UDM 212, and the parameter value can be obtained from the UDM by the MM NF. In some scenarios involving general NFs (e.g., PCF, UDM), UE- <rat>-AMBR can be explicitly defined for each RAT type (e.g., UE-5G-AMBR, UE-6G-AMBR). In other scenarios involving independent NFs, each NF can be configured with UE- <rat>-AMBR, or more simply UE-AMBR.

[0059] Based on the value of the local policy or AM policy association indicator received from UDM 212, MM NF 204 can determine at step 302 to establish an AM policy association with (V-)PCF 210. If MM NF has not yet obtained access and mobility related policy information for UE 110, or if the access and mobility related policy information in MM NF is no longer valid, MM NF can request (V-)PCF to apply operator policies for UE from PCF.

[0060] At step 303, the MM NF can send a request to the (V-)PCF to establish an AM policy association with (V-)PCF 210, such as using the (V-)PCF's service operation (Npcf_AMPolicyControl_Create). This request may include information indicating the RAT type of the RAN 108 to which the UE 110 is connected, which can be determined by the MM NF (e.g., based on the global RAN node ID associated with the N2 interface and, additionally, the tracking area indicated by the RAN). The (V-)PCF can invoke the Data Management (DM) service (Nudr_DM_Query) to the UDR 214, and the UDR can respond using the requested policy control subscription data and / or application data.

[0061] (V-)PCF 210 can determine the UE based on the RAN's RAT type. <rat>The value of -AMBR. In some examples, (V-)PCF can determine the UE- for multiple RAT types. <rat>-AMBR has multiple values. In some of these examples, (V-)PCF can determine the UE- for all subscription / availability information in UDM 212. <rat>The value of AMBR can be optimized for future changes to the RAT. In this respect, these values ​​can be used to preempt the AMBR for the target (second) RAT and prevent the MM NF from subsequently acquiring the value for the target RAT when the Policy Control Request Trigger (PCRT) is requested.

[0062] (V)-PCF 210 may respond to a request from MM NF 204 at step 304. (V)-PCF may send access and mobility-related policy information to the MMNF, and the access and mobility-related policy information may include information about the RAT type of the UE to which UE110 is connected. <rat>-AMBR value (and may also include UE for (multiple) other RAT types- <rat>-AMBR (multiple values). Then, the MM NF can deploy or otherwise apply access and mobility-related policy information at step 305. For example, the MM NF can provide the RAN with UE- <rat>-AMBR is used for execution.

[0063] MM NF 204 can provide UE to RAN 108 in a variety of different ways. <rat>-AMBR (including RAN-specific RAT type values). Figure 4 It is based on some examples of implementations for providing UE from MM NF to RAN. <rat>-AMBR is a diagram of the process performed at the RAN. Similar to before, although not shown separately, in some examples, the UE-slice- <rat>- The MBR can be provided to the RAN for execution during the same or another similar process. Alternatively, UE-slice- <rat>-MBR can be executed at PCF 210. In some examples, Figure 4 The procedures shown can be implemented during a UE-triggered service request procedure, such as according to 3GPP TS 23.502. A UE-triggered service request procedure can be triggered by a service request from UE 110 to the RAN.

[0064] As shown in the figure, RAN 108 can send an N2 message, including a service request and one or more N2 parameters, to MM NF 204 at step 401 (step 2 of the UE-triggered service request procedure). MM NF can later send an N2 request to RAN at step 402 (step 12 of the UE-triggered service request procedure) to request the establishment of a UE context for the UE in the RAN. The N2 request may include, for example, UE- <rat>-AMBR value, so that the RAN can perform UE- based on that value. <rat>-AMBR.

[0065] In some examples, such as when a UE connects to a second RAN 108 implementing a second RAT type, the PCRT conditions can be satisfied by the UE 110 changing or moving to a second RAT type. MM NF 204 can be triggered by the satisfaction of the PCRT conditions to utilize the second RAT type update (V)-PCF 210, such as in modifications associated with AM policies. In this regard, Figure 5 This is a block diagram of a process for AM policy association modification initiated by MM NF, implemented based on some examples, and during this process, UE- <rat>The value of -AMBR can be changed. Again, in some examples, UE-slice- <rat>- The MBR can be changed during the same or another similar process used for AM policy association modifications. Similar to before, this process applies to both roaming and non-roaming scenarios.

[0066] As shown in the figure, when the PCRT condition is met, the MM NF can update the AM policy association at step 501 and provide the (V-)PCF 210 with information about one or more conditions that have changed, such as by invoking the AM policy control update service operation (Npcf_AMPolicyControl_Update). The information about the changed conditions(s) may include information indicating the second RAT type associated with the connection from UE 110 to the second RAN 108.

[0067] (V-)PCF 210 can store the information received in step 501 and make a policy decision at step 502. (V-)PCF can determine the UE- based on the second RAT type. <rat>-The second value of AMBR. (V-)PCF can utilize updated access and mobility-related policy information (including UE-) at step 503. <rat>The MM NF then responds to MM NF204 with the second value of the AMBR. The MM NF can then deploy or otherwise apply updated access and mobility-related policy information at step 504. For example, the MM NF can provide UE- <rat>The second value of -AMBR is used for execution.

[0068] Figure 6 This is a block diagram illustrating the process of establishing SM policy associations for a PDU session in UE 110, implemented based on some examples, during which the session - <rat>-AMBR can be configured and provided to SM NF 206 (e.g., 5GSM / SMF, 6G SM). As shown in the figure, this process involves the SM NF as an NF service consumer and the PCF 210 as an NF service producer. Similarly, this process applies to both roaming and non-roaming scenarios. As shown in the figure, session- <rat>-AMBR can be configured in the PCF, and the value of the parameter can be obtained from the PCF by the SM NF, as described below.

[0069] In some examples, SM NF 206 may determine that Policy and Charging Control (PCC) authorization is required. The SM NF may send a request to PCF 210 at step 601 to establish an SM policy association with the PCF, such as by invoking the PCF's service operation (Npcf_SMPolicyControl_Create). This request may include information about the UE's PDU session, and this information may include information indicating the RAT type of the RAN 108 to which the UE 110 is connected. In some examples, the RAT type may be determined by MM NF 204, which may indicate the RAT type to the SM NF, and the SM NF may also determine the RAT type accordingly.

[0070] If PCF 210 does not have subscription-related information for the user (subscriber) of UE 110, PCF can send a request to UDR 214 at step 602, such as by invoking the UDR's DM query service operation (Nudr_DM_Query), to receive information related to the PDU session. PCF can request notifications from the UDR regarding changes to subscription information, such as by invoking the DM subscription service operation (Nudr_DM_Subscribe).

[0071] If PCF 210 determines that the policy decision depends on the status of the policy counter(s) available at CHF 216, and a policy counter status report has not been established for the subscriber, then PCF may initiate an initial spending limit report retrieval at step 603. If a policy counter status report has been established for the subscriber and PCF determines that the status of the additional policy counter(s) is required, then PCF may initiate an intermediate spending limit report retrieval.

[0072] PCF 210 can make authorization and policy decisions at step 604. PCF 210 can determine the session for the PDU session of UE 110 based on the RAT type of the RAN 108 to which the UE is connected. <rat>The value of -AMBR. The PCF can respond to the request (Npcf_SMPolicyControl_Create) from SM NF 204 at step 605. The PCF can send policy information for the PDU session to the SM NF, and this policy information may include a RAT type session for the RAN. <rat>The value of -AMBR. The SM NF can then deploy or otherwise apply policy information, which may include providing session information to UPF 208 and / or UE 110. <rat>-AMBR is used for execution. In some examples, session - <rat>-AMBR can be shared with the UE, and then the UE can use the value of the parameter of type RAT for the RAN.

[0073] Now for reference Figure 7-13 The illustration shows the corresponding procedures for the execution of aggregate rate limiting QoS parameters for each RAT or network slice(s) across RATs, implemented according to various examples. As described in more detail below, in some examples, the corresponding procedures may be implemented at least in part during the UE-requested PDU session establishment (or modification) procedure, such as according to 3GPP TS 23.502.

[0074] Figure 7 It is implemented based on some examples for UE-slice- <rat>- A block diagram of the execution process of the MBR. This process involves processing the MM NF204 of the UE 110 connected to the RAN 108 implementing a RAT type (e.g., 5G RAT, 6G RAT). As shown in the figure, the MM NF can be a 5G MM (AMF) 204A or a 6G MM 204B; and in these examples, the MM NF can be referred to as 5G / 6G MM NF 204A, 204B. The process also involves SM NF 206, PCF 210, UDM 212, and UDR 214.

[0075] As shown in step 701, UE-slice- <rat>- The MBR can be configured in the UDM 212, such as in the access and mobile subscription data section, and / or as part of the PDU session policy control subscription information. In some examples, 5G / 6G MMNF 204A, 204B can report the UE-slice subscription for each RAT for each network slice (S-NSSAI) of the serving network. <rat>-MBR, and PCF 210 can return the authorized UE-slice for each RAT used for the serving network slice- <rat>-MBR (Authorization MBR for PDU sessions).

[0076] 5G / 6G MM NFs 204A and 204B can send a request to SM NF 206 at step 702 (step 3 of the UE-requested PDU session establishment process) to create or modify the SM context of the PDU session for UE 110 for network slicing. This request can be sent by the 5G / 6G MM NF invoking the appropriate service operation (Nsmf_PDUSession_CreateSMContext, Nsmf_PDUSession_UpdateSMContext) of the SMNF. The request may include information indicating the RAT type of the RAN 108 to which the UE is connected. The request may also include information identifying the network slice (S-NSSAI).

[0077] As shown in step 703 (step 4 of the UE-requested PDU session establishment process), if the relevant session management subscription data is unavailable, SM NF 206 can obtain the session management subscription data and subscribe to it to be notified when the subscription data is modified. UDM 212 can obtain this information from UDR 214 and can subscribe to notifications for the same data from the UDR.

[0078] The SM NF can send a response to the request from 5G / 6G MM NF 204A or 204B at step 704 (step 5 of the UE-requested PDU session establishment process). If a request to establish a PDU session is received, and the SMF receives a request to create an SM context at step 702, and the SM NF is capable of handling the PDU session establishment request, the SM NF can create an SM context and respond to the 5G / 6G MM NF by providing an identifier for the SM context.

[0079] SM NF 206 can perform the SM policy association establishment (or modification) procedure (step 7b of the UE-requested PDU session establishment procedure). The SM NF can send a request to PCF 210 at step 705 to establish an SM policy association with the PCF, such as by invoking the PCF's service operation (Npcf_SMPolicyControl_Create). This request may include information about the UE 110's PDU session, such as information indicating the RAT type of the RAN 108 to which the UE is connected, and information identifying the network slice (S-NSSAI).

[0080] PCF 210 may receive information related to the PDU session from UDR 214 at step 706, and this information may include: the remaining MBRs for the RAT of RAN 108 to which the UE is connected, and for the network slice (S-NSSAI) of UE 110. If PCF does not have subscription-related information for the UE's users (subscribers), PCF may send a request (Nudr_DM_Query) to UDR to receive information related to the PDU session.

[0081] PCF 210 can, at step 707, base its decision on whether the remaining MBR value of the (multiple) PDU sessions of UE 110 used for network slices for RAT is greater than that of the authorized UE-slice. <rat>A high MBR value is used to make policy decisions regarding accepting or rejecting the establishment (or modification) of SM policy associations. In this regard, the PCF can check whether the remaining MBR of the (multiple) PDU sessions for the UE used for the network slice against the RAT is higher than that of the authorized UE-slice. <rat>-MBR high. If so, the PCF can, at step 707.1, such as via the DM service (Nudr_DM_Update), deduct the authorized UE-slice- from the remaining MBR of the (multiple) PDU sessions for the UE for the network slice against the RAT in UDR 214. <rat>- The value of MBR. If the remaining MBR is insufficient, PCF can reject the establishment (or modification) of SM policy associations.

[0082] PCF 210 may respond to a request (Npcf_SMPolicyControl_Create) from SM NF 204 at step 708. PCF may send policy information for the PDU session to SM NF, and the policy information may include information indicating the policy decision made at step 707.

[0083] Figure 8 and Figure 9 This is a diagram illustrating the process of executing an MBR across RATs and across (multiple) UE 110s for network slices, implemented according to various examples. This process addresses the following issue: 5G and 6G RATs are supported by different NFs (e.g., PCF 210, UDM 212, UDR 214), and the operator desires a universal MBR for network slices across (multiple) UE 110s accessing the network slices from both 5G and 6G RATs. In some examples, the MBR for network slices across RATs and across (multiple) UEs can be set as the sum of the session MBRs for each QoS flow under the active PDU session for the network slice under each RAT.

[0084] The MBR for network slicing across RATs and across (multiple) UEs 110 can be used in policy control for establishing or modifying PDU sessions (QoS flows). Figure 8 and Figure 9 The process is illustrated for a scenario involving: a general S-NSSAI that identifies network slices, and a separate PCF 210 including a primary PCF (e.g., 5G PCF 210A). This process also involves SM NF206 (e.g., 6G SM NF), 6G PCF 210B, and 5G UDR 214A. The primary PCF can be responsible for policy control of network slices (S-NSSAI) for at least two RATs (e.g., 5G, 6G), and the MBR for network slices across RATs and across (multiple) UEs can be defined and managed by the primary PCF for both non-roaming and roaming users.

[0085] exist Figure 8 In the process shown, the 5G PCF 210A (primary PCF) can be discovered by the 6G PCF 210B, and the establishment / modification of SM policy associations for PDU sessions is requested at the 6G PCF 210B. As shown, at step 801, the 5G PCF and 6G PCF can be configured with attributes (e.g., slice coordination information) used for providing or limiting data rates across different RATs. This attribute can carry network slice profile information, indicating the RATs supported for the network slice (S-NSSAI), and indicating the primary RAT (e.g., 5G). In some examples, the PCF can be configured with a list of attributes that includes the supported RATs and the primary RAT (e.g., eMBB slices supported in both 5G and 6G, where the network slice identifier only includes the slice / service type (SST) of the network slice).

[0086] During the UE-requested PDU session establishment (or modification) process (at step 7b), the SM NF 206 (e.g., a 6GSM NF) can perform an SM policy association establishment (or modification) process. The SM NF can send a request to the 6G PCF 210B at step 802 to establish an SM policy association with the 6G PCF, such as by invoking the 6G PCF's service operation (Npcf_SMPolicyControl_Create). This request may include information about the UE 110's PDU session, such as information indicating the RAT of the RAN 108 to which the UE is connected, and information identifying the network slice (S-NSSAI).

[0087] The 6G PCF 210B can check the supported RATs for the network slice based on the network slice profile information at step 803. If support for more than one RAT is indicated, the 6G PCF can determine the primary RAT (e.g., 5G) for the network slice indicated by the network slice profile information at step 804, and discover the 5G PCF 210A that supports the primary RAT for the network slice. Then, the 6G PCF can send a request for policy control for the network slice to the 5G PCF at step 805, such as by invoking a policy control service operation (e.g., Npcf_PolicyControl). This request may include information identifying the network slice (S-NSSAI). The request may also include information indicating the maximum authorized bit rate for the PDU session, which in some examples may be carried by a Data Use Information Element (IE).

[0088] The 5G PCF 210A can receive information related to the PDU session from the UDR 214 at step 806, and this information may include the residual MBR (S-NSSAI) across RAT and across UE 110 for network slicing. If the PCF does not have subscription-related information for the UE's users (subscribers), the PCF can send a request (Nudr_DM_Query) to the UDR to receive information related to the PDU session.

[0089] The 5G PCF 210A can make a policy decision at step 807 to accept or reject the establishment (or modification) of an SM policy association based on whether the value of the remaining MBR across RAT and UE 110 for network slicing is higher than the value of the authorized MBR for PDU sessions. In this regard, the PCF can check whether the remaining MBR across RAT and UE for network slicing is higher than the authorized MBR for PDU sessions. If so, the PCF can, at step 807.1, deduct the value of the authorized MBR for PDU sessions from the remaining MBR across RAT and UE for network slicing in UDR 214, such as via the DM service (Nudr_DM_Update). If the remaining MBR is insufficient, the PCF can reject the establishment (or modification) of the SM policy association.

[0090] The 5G PCF 210A can send a response at step 808 to a request (e.g., Npcf_PolicyControl) from the 6G PCF 210. This response may include information identifying the network slice (S-NSSAI) and information indicating the policy decision made at step 807. The 6G PCF 210B can then respond at step 809 to a request (Npcf_SMPolicyControl_Create) from the SM NF 204. The 6G PCF can send policy information for the PDU session to the SM NF, and this policy information may include information indicating the policy decision.

[0091] exist Figure 9 In the process shown, the 5G PCF 210A (primary PCF) can be discovered by SM NF 206 (instead of 6G PCF 210B). As shown, at step 901, the 5G PCF 210A can be configured with network slice profile information indicating the RAT (S-NSSAI) and primary RAT (e.g., 5G) supported by the network slice. The 5G PCF can register its NF profile in NRF 218 at step 902, and the 5G PCF's NF profile can include network slice profile information. As described above, and now shown at step 903, the MBR for network slices across RATs and across (multiple) UEs can be defined and managed by the primary PCF for both non-roaming and roaming users. In some examples, the primary PCF can be the home PCF for UE 110.

[0092] SM NF 206 (e.g., 6G SM NF) can discover the primary PCF (5G PCF 210A) and RAT type for network slicing (S-NSSAI) at step 904, and NRF can respond back to SM NF using network slice profile information from NRF 218.

[0093] SM NF 206 can perform an SM policy association establishment (or modification) procedure for a PDU session (at step 7b of the PDU session establishment procedure requested by the UE). During the SM policy association establishment (or modification) procedure, the SM NF can send a request to the 5G PCF 210A (primary PCF) at step 905, such as by invoking the SM policy control to create a service operation (Npcf_SMPolicyControl_Create). This request may include information about the PDU session of UE 110, such as information identifying the network slice (S-NSSAI).

[0094] The 5G PCF 210A can receive information related to the PDU session from the UDR 214 at step 806, as described above. The 5G PCF can make a policy decision at steps 807 and 807.1 to accept or reject the establishment (or modification) of an SM policy association based on whether the value of the remaining MBR across RAT and across UE 110 for network slicing is higher than the value of the authorized MBR for the PDU session, also as described above. In some of these examples, the 5G PCF can use subscription information and operator policies to derive the authorized MBR for the PDU session. Then, the 5G PCF 210A can respond to a request (Npcf_SMPolicyControl_Create) from the SMNF 204 at step 908. The 5G PCF can send policy information for the PDU session to the SM NF, and this policy information may include information indicating the policy decision made at step 807.

[0095] Figure 10 This is a block diagram illustrating the process for executing an MBR across RAT and across (multiple) UE 110 for network slices, implemented based on some other examples. This process addresses a similar issue where the 5G and 6G RATs are supported by different NFs (e.g., PCF 210, UDM 212, UDR 214), and the operator desires a common MBR for network slices across (multiple) UE 110s accessing the network slices from both 5G and 6G RATs. In some examples, the MBR for network slices across RAT and across (multiple) UEs can be set as the sum of the session MBRs for each QoS flow under the active PDU session for the network slice under each RAT.

[0096] The MBR for network slicing across RATs and across (multiple) UEs 110 can be used in policy control for establishing or modifying PDU sessions (QoS flows). Figure 10 The process is illustrated for a scenario involving different S-NSSAIs for identifying network slices in 5GS and 6GS, and a separate PCF 210 including a main PCF (e.g., 5G PCF 210A). S-NSSAIs may include, for example, 5G S-NSSAIs for identifying network slices in 5GS and 6G S-NSSAIs for identifying network slices in 6GS.

[0097] Figure 10 The process also involves SM NF 206 (e.g., 6G SM NF), 6G PCF 210B, 5G UDR 214A, and NSSF 220. Similarly, the primary PCF can be responsible for: policy control for network slicing (S-NSSAI) for at least two RATs (e.g., 5G, 6G), and the MBR for network slicing across RATs and across (multiple) UEs can be defined and managed by the primary PCF for both non-roaming and roaming users. S-NSSAIs can be mapped to each other to have a common MBR for network slicing, and the network slice profile information used to map S-NSSAIs can be configured or otherwise stored in a host NSSF, which can be common or different for the RAT. In some examples, S-NSSAIs may include a primary S-NSSAI (the identifier of the network slice), and the common MBR for network slicing can be defined on the primary S-NSSAI (e.g., 5G S-NSSAI). In some examples, the primary PCF can be the home PCF for UE 110.

[0098] like Figure 10 As shown, at step 1001, the NSSF 220 can be configured with network slice profile information. Again, as shown at step 1002, the MBR for network slices across RATs and across (multiple) UEs can be defined and managed by the primary PCF for both non-roaming and roaming users, and the generic MBR for network slices can be defined on the primary S-NSSAI. The SM NF206 (e.g., a 6G SM NF) can obtain network slice profile information from the NSSF at step 1003, such as by invoking the NSSF service operation (Nnssf_NSSelection).

[0099] During the UE-requested PDU session establishment (or modification) process (at step 7b), the SM NF 206 (e.g., a 6GSM NF) can perform an SM policy association establishment (or modification) process. The SM NF can send a request (Npcf_SMPolicyControl_Create) to the 6G PCF 210B at step 1004 to establish an SM policy association with the 6G PCF, and this request may include network slice profile information from the NSSF 220.

[0100] The 6G PCF 210B can check the supported RATs for the network slice at step 1005 based on the network slice profile information. If support for more than one RAT is indicated, the 6G PCF can discover the 5G PCF 210A that supports the primary RAT for the network slice based on the network slice profile information from the NRF 218, in a manner similar to or as described above. The 6G PCF can also determine the 5G S-NSSAI (primary S-NSSAI) for the network slice based on the network slice profile information for mapping the S-NSSAI from the NSSF 220. The 6G PCF can then send a request for policy control for the network slice (e.g., Npcf_PolicyControl) to the 5G PCF at step 1006. This request may include the primary S-NSSAI (5G S-NSSAI) and information indicating the authorized maximum bit rate for the PDU session (e.g., data usage IE).

[0101] The 5G PCF 210A can receive information related to the PDU session from UDR 214 at step 1007 based on the primary S-NSSAI, and this information may include the remaining MBR (S-NSSAI) across RAT and UE 110 for network slicing. At step 1008, the 5G PCF 210A can make a policy decision to accept or reject the establishment (or modification) of SM policy associations based on whether the value of the remaining MBR across RAT and UE 110 for network slicing is higher than the value of the authorized MBR for the PDU session, in a manner similar to the previous steps. If the remaining MBR across RAT and UE for network slicing is higher than the authorized MBR for the PDU session, the PCF can, at step 1008.1, subtract the value of the authorized MBR for the PDU session from the remaining MBR across RAT and UE for network slicing in UDR 214, such as via the DM service (Nudr_DM_Update). If the remaining MBR is insufficient, the PCF can reject the establishment (or modification) of the SM policy association.

[0102] The 5G PCF 210A can send a response at step 1009 to a request (e.g., Npcf_PolicyControl) from the 6G PCF 210. This response may include information identifying the network slice (6G S-NSSAI) and information indicating the policy decision made at step 1008. The 6G PCF 210B can then respond at step 1010 to a request (Npcf_SMPolicyControl_Create) from the SM NF 204. The 6G PCF can send policy information for the PDU session to the SM NF, and this policy information may include information indicating the policy decision.

[0103] In some examples, the UDM 212 / UDR 214 can be a generic NF serving both 5GS and 6GS. In some of these examples, the 6G PCF 212B can interact directly with the generic UDR at step 1006 and perform policy control-related operations at steps 1007 and 1008. According to some other example implementations, each RAT used for network slicing spans the MBR of UE(multiple) UE(s) 110.

[0104] Figure 11 This is a block diagram illustrating the process of executing an MBR across (multiple) UE 110s for each RAT used in a network slice, based on some examples. The process addresses the following issue: 5G and 6G RATs are supported by a generic PCF 210, and operators desire corresponding MBRs for network slices across (multiple) UE 110s, which access the network slice for each RAT targeting both 5G and 6G RATs. The process is also illustrated for a scenario involving a generic S-NSSAI for identifying network slices. The process involves handling 5G / 6G MM NF204A, 204B for UE 110s connected to RAN 108 implementing RATs (e.g., 5G RAT, 6G RAT). The process also involves SM NF 206, PCF 210, and UDR 214.

[0105] As shown at step 1101, the MBR across (multiple) UEs for each RAT used in a network slice can be configured in or provided to the PCF 212. This process may include steps 702 to 704 of the PDU session establishment or modification procedure requested by the UE, as referenced above. Figure 7 As described above, similarly to what was previously stated, SM NF 206 can perform the SM policy association establishment (or modification) procedure (step 7b of the UE-requested PDU session establishment procedure). The SM NF can send a request (Npcf_SMPolicyControl_Create) to PCF 210 at step 705 to establish an SM policy association with the PCF. This request may include information about the UE 110's PDU session, such as information indicating the RAT of RAN 108 to which the UE is connected, and information identifying the network slice (S-NSSAI).

[0106] PCF 210 may receive information related to the PDU session from UDR 214 at step 1106, and this information may include the remaining MBR for the network slice (S-NSSAI) of the RAT to which the UE is connected, across multiple UEs 110. At step 1107, PCF may make a policy decision to accept or reject the establishment (or modification) of the SM policy association based on whether the value of the remaining MBR for the network slice of the RAT across multiple UEs 110 is higher than the value of the authorized MBR for the PDU session. If so, at step 1107.1, PCF may subtract the value of the authorized MBR for the PDU session from the remaining MBR of the network slice of the RAT across multiple UEs in UDR 214. If the remaining MBR is insufficient, PCF may reject the establishment (or modification) of the SM policy association.

[0107] PCF210 can respond to a request (Npcf_SMPolicyControl_Create) from SM NF 204 at step 708. PCF can send policy information for the PDU session to SM NF, and the policy information may include information indicating the policy decision made at step 1107.

[0108] Figure 12 and Figure 13 This is a diagram illustrating the process for enforcing an MBR across RATs and UE(s) 110 for network slices, implemented using various examples. This process addresses the following issue: 5G and 6G RATs are supported by a generic PCF 210, and operators desire a generic MBR for network slices (multiple) UE(s) 110 accessing the network slices from both 5G and 6G RATs. Furthermore, the MBR for network slices, spanning RATs and UE(s), can be used in policy control for establishing or modifying PDU sessions (QoS flows). Figure 12 and Figure 13 The process for scenarios involving different S-NSSAIs (such as 5G S-NSSAI for identifying network slices in 5GS and 6G S-NSSAI for identifying network slices in 6GS) is illustrated.

[0109] exist Figure 12 In the process shown, the generic MBR for network slicing can be configured in PCF 210 to map to the attributes of S-NSSAI for network slices, as shown at step 1201. This process may include steps 702 to 704 of the PDU session establishment or modification procedure requested by the UE, as referenced above. Figure 7 As described above, similarly to what was previously stated, SM NF206 can perform the SM policy association establishment (or modification) procedure (step 7b of the UE-requested PDU session establishment procedure). The SM NF can send a request (Npcf_SMPolicyControl_Create) to the PCF at step 705 to establish an SM policy association with the PCF. This request may include information about the UE 110's PDU session, such as information identifying the network slice (e.g., 6G S-NSSAI).

[0110] PCF 210 may receive information related to the PDU session from UDR 214 at step 1206, and this information may include the remaining MBR for the PDU session(s) mapped to S-NSSAI across RAT and across(multiple) UE(s) 110. At step 1207, PCF may make a policy decision to accept or reject the establishment (or modification) of the SM policy association based on whether the value of the remaining MBR for the PDU session(s) across RAT and across(multiple) UE(s) 110 for the network slice is higher than the value of the authorized MBR for that PDU session. If so, at step 1207.1, PCF may subtract the value of the authorized MBR for the PDU session from the remaining MBR for the PDU session(s) across RAT and across(multiple) UE(s) for the network slice in UDR 214. If the remaining MBR is insufficient, PCF may reject the establishment (or modification) of the SM policy association.

[0111] PCF 210 may respond to a request (Npcf_SMPolicyControl_Create) from SM NF 204 at step 708. PCF may send policy information for the PDU session to SM NF, and the policy information may include information indicating the policy decision made at step 1207.

[0112] exist Figure 13 In the process shown, the S-NSSAI used for network slicing may include a primary S-NSSAI (the identifier of the network slice), and the generic MBR used for network slicing may be defined on the primary S-NSSAI (e.g., 5G S-NSSAI). As shown, at step 1301, the network slice profile information used to map the S-NSSAI may be configured or otherwise stored in the host NSSF 220, as shown at step 1301. This process may include steps 702 to 704 of the process for establishing or modifying a PDU session requested by the UE, as referenced above. Figure 7 As described above, similarly to before, SM NF 206 can perform the SM policy association establishment (or modification) procedure (step 7b of the UE-requested PDU session establishment procedure). The SMNF can send a request (Npcf_SMPolicyControl_Create) to the PCF at step 705 to establish an SM policy association with the PCF. This request may include information about the UE 110's PDU session, such as information identifying the network slice (e.g., 6GS-NSSAI).

[0113] PCF 210 can determine the 5G S-NSSAI (primary S-NSSAI) for the network slice based on the network slice profile information for mapping S-NSSAI from NSSF 220 at step 1306. PCF can receive information related to PDU sessions from UDR 214 based on the primary S-NSSAI, and this information may include the remaining MBR for the PDU sessions mapped to the S-NSSAI for the network slice, spanning RATs and multiple UEs 110. At step 1307, PCF can make a policy decision to accept or reject the establishment (or modification) of the SM policy association based on whether the value of the remaining MBR for the PDU sessions across RATs and multiple UEs 110 for the network slice is higher than the value of the authorized MBR for that PDU session. If so, the PCF can, at step 1307.1, deduct the value of the authorized MBR for the PDU session from the remaining MBR for the PDU session across RAT and across (multiple) UEs for the network slice in UDR 214. If the remaining MBR is insufficient, the PCF can refuse the establishment (or modification) of the SM policy association.

[0114] PCF 210 may respond to a request (Npcf_SMPolicyControl_Create) from SM NF 204 at step 708. PCF may send policy information for the PDU session to SM NF, and the policy information may include information indicating the policy decision made at step 1307.

[0115] Figure 14A and Figure 14B This is a flowchart illustrating the various steps of method 1400 performed by a Network Functions (NF) service consumer, implemented according to various examples. The method includes: sending a request to an NF service producer for information regarding user equipment (UE) for connecting to a radio access network (RAN), such as... Figure 14A As shown in box 1402. The method includes receiving information from an NF service provider in response to the request, the information including the value of at least one aggregate rate limiting quality of service (QoS) parameter associated with the UE, the UE's Protocol Data Unit (PDU) session, or one or more PDU session groups of the UE for network slicing, as shown in box 1404. The value of the at least one aggregate rate limiting QoS parameter is specific to the RAN's Radio Access Technology (RAT) type. And the method includes applying information to the UE, the information including at least one aggregate rate limiting QoS parameter having a value specific to the RAN's RAT type, when the UE is connected to the RAN or another RAN of the same RAT type, as shown in box 1406.

[0116] In some examples, the request sent to the NF service producer at box 1402 includes information indicating the RAT type, which is used by the NF service producer to determine the value of at least one aggregate rate limiting QoS parameter based on the RAT type.

[0117] In some examples, method 1400 also includes determining a change from the RAT type to a second RAT type, which is associated with the UE's connection to a second RAN, such as... Figure 14B As shown in box 1408. In some of these examples, the method includes: sending information indicating a second RAT type to the NF service producer, as shown in box 1410. The method includes receiving a second value of at least one aggregation rate limiting QoS parameter from the NF service producer, as shown in box 1412. This second value is specific to a second RAT type of the second RAN. And the method includes: when the UE is connected to the second RAN or another RAN of the second RAT type, applying at least one aggregation rate limiting QoS parameter having a second value specific to the second RAT type of the second RAN, as shown in box 1414.

[0118] In some examples, the information received from the NF service producer at box 1404 includes multiple values ​​for at least one aggregate rate limiting QoS parameter for multiple RAT types. In some of these examples, method 1400 also includes storing the multiple values ​​of at least one aggregate rate limiting QoS parameter in UE context information for the UE.

[0119] In some examples, the NF service consumer is a mobility management NF, the NF service producer is a policy control NF or a unified data management NF, and this information includes access and mobility management information for the UE. In some of these examples, at least one aggregated rate-limiting QoS parameter includes an aggregated QoS parameter associated with the UE. The aggregated QoS parameter is the aggregated maximum bit rate for each RAT type UE, and the value of this aggregated maximum bit rate is used for UEs of the RAT type for the RAN.

[0120] In some examples, applying this information at box 1406 includes: sending the value of the aggregated maximum bit rate to the RAN so that the RAN can perform aggregated maximum bit rate based on that value.

[0121] In some examples, the NF service consumer is a session management NF, the NF service producer is a policy control NF, and the information includes session management information for the UE's PDU session. In some of these examples, the at least one aggregated rate-limiting QoS parameter includes an aggregated QoS parameter associated with the UE's PDU session. This aggregated QoS parameter is the aggregated maximum bit rate for each RAT type PDU session for one or more RAT types, and the value of the aggregated maximum bit rate is used for the RAN's RAT type PDU session.

[0122] In some examples, applying this information at box 1406 includes sending a value for the aggregated maximum bit rate for at least one of the user plane NF or UE to perform the aggregated maximum bit rate based on that value.

[0123] In some examples, the NF service consumer is a mobility management NF, the NF service producer is a policy control NF or a unified data management NF, and the information includes access and mobility management information for the UE. In some of these examples, at least one aggregated rate-limiting QoS parameter includes an aggregated QoS parameter associated with a group of one or more PDU sessions of the UE for the network slice. The aggregated QoS parameter is the maximum bit rate for each RAT type of UE for the network slice, and the value of the maximum bit rate is a group of one or more PDU sessions of the UE for the network slice of the RAT type of the RAN.

[0124] In some examples, applying this information includes sending the maximum bit rate value to the RAN so that the RAN can perform aggregated maximum bit rate based on that value.

[0125] Figure 15A and Figure 15B This is a flowchart illustrating various steps in method 1500, implemented according to various examples and performed by a Network Function (NF) service provider. The method includes receiving a request from an NF service consumer for information regarding a User Equipment (UE) for connecting to a Radio Access Network (RAN), the request including information indicating the Radio Access Technology (RAT) type of the RAN, such as... Figure 15A As shown in box 1502. The method includes determining the value of at least one aggregate rate limiting quality of service (QoS) parameter associated with the UE, a UE's Protocol Data Unit (PDU) session, or a group of one or more PDU sessions of the UE for network slicing, based on the RAN's RAT type, as shown in box 1504. The method also includes sending information including the value of the at least one aggregate rate limiting QoS parameter to an NF service consumer in response to the request, as shown in box 1506.

[0126] In some examples, method 1500 also includes determining a change from a RAT type to a second RAT type associated with the UE-to-second RAN connection, such as... Figure 15B As shown in box 1508. In some of these examples, the method includes: receiving information from an NF serving consumer indicating a second RAT type associated with a UE-to-second RAN connection, as shown in box 1510. The method includes determining a second value for at least one aggregation rate limiting QoS parameter based on the second RAT type, as shown in box 1512. And the method includes: sending the second value of at least one aggregation rate limiting QoS parameter to the NF serving consumer, as shown in box 1514.

[0127] In some examples, determining the value of at least one aggregate rate limiting QoS parameter at box 1504 includes determining multiple values ​​of the at least one aggregate rate limiting QoS parameter for multiple RAT types. In some of these examples, the information sent to the NF service consumer at box 1506 includes multiple values ​​of the at least one aggregate rate limiting QoS parameter.

[0128] In some examples, the NF service producer is a policy control NF or a unified data management NF, the NF service consumer is a mobility management NF, and the information includes access and mobility management information for the UE. In some of these examples, at least one aggregated rate-limiting QoS parameter includes an aggregated QoS parameter associated with the UE. This aggregated QoS parameter is the aggregated maximum bit rate for each RAT type UE, and the value of the aggregated maximum bit rate is used for RAT type UEs for the RAN.

[0129] In some examples, the NF service producer is a policy control NF, the NF service consumer is a session management NF, and the information includes session management information for the UE's PDU session. In some of these examples, at least one aggregated rate-limiting QoS parameter includes an aggregated QoS parameter associated with the UE's PDU session. This aggregated QoS parameter is the aggregated maximum bit rate for each RAT type PDU session for one or more RAT types, and the value of the aggregated maximum bit rate is for the RAN's RAT type PDU session.

[0130] In some examples, the NF service producer is a policy control NF or a unified data management NF, the NF service consumer is a mobility management NF, and the information includes access and mobility management information for the UE. In some of these examples, at least one aggregated rate-limiting QoS parameter includes an aggregated QoS parameter associated with a group of one or more PDU sessions of the UE for the network slice. The aggregated QoS parameter is the maximum bit rate for each RAT type UE for that slice, and the value of the maximum bit rate is a group of one or more PDU sessions of the UE for the network slice of the RAT type of the RAN.

[0131] Figure 16 This is a flowchart illustrating the various steps of method 1600 implemented according to various examples. The method includes receiving a request relating to a session management (SM) policy association for establishing or modifying a Protocol Data Unit (PDU) session for a User Equipment (UE) associated with a network slice, as shown in box 1602. The method includes receiving information indicating a remaining maximum bit rate associated with a group of one or more PDU sessions associated with the network slice, as shown in box 1604. This remaining maximum bit rate has: a value specific to the Radio Access Network (RAN) to which the UE is connected, or a value common to at least two RAT types including the RAN's RAT type. The method includes making a policy decision to accept or reject the establishment or modification of the SM policy association based on whether the value of the remaining maximum bit rate is higher than the value of the authorized maximum bit rate for the PDU session, as shown in box 1606. The method also includes sending a response to the request, the response including information indicating the policy decision, as shown in box 1608.

[0132] In some examples, the remaining maximum bit rate is associated with a group of one or more PDU sessions of the UE, and the value of the aggregated maximum bit rate is specific to the RAT type of the RAN to which the UE is connected.

[0133] In some examples, the remaining maximum bit rate is associated with a group of one or more PDU sessions of a UE group that includes the UE, and the value of the remaining maximum bit rate is specific to the RAT type of the RAN to which the UE is connected.

[0134] In some examples, the remaining maximum bit rate is associated with a group of one or more PDU sessions that include the UE group, and the value of the remaining maximum bit rate is common to at least two RAT types that include the RAT type to which the UE is connected.

[0135] In some examples, the network slice has a corresponding network slice identifier associated with at least two RAT types, and the remaining maximum bit rate is associated with each of the corresponding network slice identifiers. In some of these examples, the information indicating the remaining maximum bit rate is based on one of the corresponding network slice identifiers, received at box 1604, which is associated with the RAT type of the RAN to which the UE is connected.

[0136] In some examples, the network slice has a corresponding network slice identifier associated with at least two RAT types, and the remaining maximum bit rate is associated with the master network slice identifier of the corresponding network slice identifier. In some of these examples, the information indicating the remaining maximum bit rate is received at box 1604 based on the master network slice identifier.

[0137] In some examples, the request is for establishing or modifying an SM policy association, and the request is received from the SM network function (NF) at box 1602.

[0138] In some examples, the request is a policy control request, and the policy control request is received from the policy control network function (NF) at box 1602, where the establishment or modification of the SM policy association for the PDU session is requested.

[0139] In some examples, the value of the remaining maximum bit rate is higher than the value of the authorized maximum bit rate for that PDU session, and the policy decision is to accept the establishment or modification of the SM policy association.

[0140] In some examples, the information for network slicing indicating the remaining maximum bit rate is received from a Unified Data Repository (UDR). In some of these examples, the method 1600 further includes subtracting the value of the authorized maximum bit rate for the PDU session from the remaining maximum bit rate in the UDR.

[0141] Figure 17A and Figure 17B This is a flowchart illustrating the various steps in method 1700 implemented according to various examples. The method includes: discovering a policy control network function (NF) responsible for policy control of network slices for at least two radio access technology (RAT) types, including: the RAT type of the radio access network (RAN) to which the user equipment (UE) is connected, such as... Figure 17A As shown in box 1702, the method includes sending a request to the policy control NF relating to a session management (SM) policy associated with the establishment or modification of a Protocol Data Unit (PDU) session for a UE associated with the network slice, as shown in box 1704. The method also includes receiving a response to the request, the response including information indicating whether to accept or reject a policy decision to establish or modify the SM policy association, the policy decision being made by the policy control NF based on the remaining maximum bit rate associated with a group of one or more PDU sessions associated with the network slice, as shown in box 1706. The remaining maximum bit rate has a value specific to the RAT type of the RAN to which the UE is connected, or a value common to at least two RAT types including the RAN's RAT type.

[0142] In some examples, the remaining maximum bit rate is associated with a group of one or more PDU sessions of a UE group that includes the UE, and the value of the remaining maximum bit rate is specific to the RAT type of the RAN to which the UE is connected.

[0143] In some examples, the remaining maximum bit rate is associated with a group of one or more PDU sessions that include the UE group, and the value of the remaining maximum bit rate is common across at least two RAT types, including the RAT type of the RAN to which the UE is connected.

[0144] In some examples, the network slice has a corresponding network slice identifier associated with the at least two RAT types, and the remaining maximum bit rate is associated with each of the corresponding network slice identifiers. In some of these examples, the request includes: a corresponding network slice identifier from the corresponding network slice identifiers associated with the RAT type of the RAN to which the UE is connected.

[0145] In some examples, the network slice has a corresponding network slice identifier associated with at least two RAT types, and the remaining maximum bit rate is associated with the master network slice identifier of the corresponding network slice identifier. In some of these examples, the request includes the master network slice identifier.

[0146] In some examples, the policy control NF found at box 1702 includes: determining the primary RAT type among at least two RAT types supported for the network slice, based on the network slice profile information used for the network slice, such as... Figure 17B As shown in box 1708. In some of these examples, the discovery of the policy control NF also includes: discovering the policy control NF that supports the main RAT type as the policy control NF that sends the request to it, as shown in box 1710.

[0147] In some examples, method 1700 is performed by another policy control NF, where the establishment or modification of the SM policy association for the PDU session is requested, and where network slice profile information is configured.

[0148] In some examples, method 1700 also includes obtaining network slice profile information from another NF where the network slice profile information is configured.

[0149] In some examples, method 1700 is executed by the session management NF, and the request is for establishing or modifying SM policy associations.

[0150] In some examples, method 1700 is performed by another policy control NF, where the establishment or modification of the SM policy association for the PDU session is requested, and the request is a policy control request.

[0151] According to example implementations of this disclosure, the telecommunications system 100 or PLMN 102 and its components, such as UE 110, CN 106, RAN 108, RAN node 202, MM NF 204, SM NF 206, UPF 208, PCF 210, UDM 212, UDR 214, CHF 216, NRF 218 and / or NSSF 220, can be implemented by various parts. The parts used to implement the system and its components can include hardware, firmware, software, or a combination thereof. In some examples, one or more devices can be configured to serve as or otherwise implement the system and its components shown and described herein. In examples involving more than one device, the respective devices can be connected to each other or otherwise communicate with each other in a variety of different ways, such as directly or indirectly via wired or wireless networks.

[0152] Based on some example implementations, refer to Figure 14A and 14B as well as Figure 15A and Figure 15B At least some of the methods described in methods 1400 and 1500 can be performed by one or more means including components for performing functions corresponding to the steps of the respective methods. Similarly, refer to Figure 16 And 17A and Figure 17B At least some of the methods described in 1600 and 1700 can be performed by one or more means including components for performing functions corresponding to the steps of the respective methods. Examples of suitable means may include a standalone computer (such as a server, host, or node) containing MM NF, SM NF, PC NF, and / or UDM, a distributed computing system containing MM NF, SM NF, PC NF, and / or UDM, or a cloud computing system containing MM NF, SM NF, PC NF, and / or UDM. MM NF, SM NF, PC NF, and / or UDM may be implemented as virtual machines or containers by the distributed computing system or cloud computing system.

[0153] Figure 18 The illustration shows an apparatus 1800 implemented according to some examples of the present disclosure, wherein components for performing various operations include: separate hardware, or hardware directed by one or more computer programs from a computer-readable storage medium or other memory, such as computer memory. The apparatus may include one or more of each of a plurality of components, such as, for example, a processing circuitry system 1802 connected to a computer-readable storage medium or other memory 1804.

[0154] The processing circuit system 1802 may consist of one or more independent processors, or a processor combined with one or more computer-readable storage media. A processing circuit system is generally any computer hardware capable of processing information, such as, for example, data, computer programs, computer code, and / or other suitable electronic information. A processing circuit system consists of a collection of electronic circuits, some of which may be packaged as integrated circuits or multiple interconnected integrated circuits (integrated circuits are sometimes more commonly referred to as "chips"). The processing circuit system may be configured to execute computer programs, which may be stored on the processing circuit system or otherwise stored in memory 1804 (on the same or another device).

[0155] The processing circuit system 1802 may include multiple processors, multi-core processors, or some other type of processor, such as a central processing unit, graphics processing unit, tensor processing unit, or accelerator, depending on the specific implementation. Furthermore, the processing circuit system may be implemented using multiple heterogeneous processor systems, where the main processor resides on a single chip along with one or more auxiliary processors. As another illustrative example, the processing circuit system may be a symmetric multiprocessor system containing multiple processors of the same type. In yet another example, the processing circuit system may be implemented as or otherwise include one or more application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc. Therefore, while the processing circuit system may be able to execute a computer program to perform one or more functions, the various examples of processing circuit systems may be able to perform one or more functions without the aid of a computer program. In any case, the processing circuit system may be appropriately programmed to perform functions or operations implemented according to the examples of this disclosure.

[0156] Memory 1804 is typically any computer hardware capable of temporarily and / or permanently storing information such as, for example, data, computer programs, instructions 1806 (e.g., computer-readable program code), and / or other suitable information. Memory may include volatile and / or non-volatile memory and may be fixed or removable. Examples of suitable memory include recording media, random access memory (RAM), read-only memory (ROM), hard disk drives, flash memory, thumb drives, removable computer floppy disks, optical disks, or some combination thereof.

[0157] Memory 1804 is a non-transient device capable of storing information. An example of a suitable memory is a computer-readable storage medium, which differs from a computer-readable transmission medium capable of carrying information from one location to another. Examples of suitable computer-readable transmission media include electronic carrier signals, telecommunication signals, or some combination thereof. As used herein, the term "non-transient" is a limitation on the medium itself (i.e., tangible, not a signal), not on the persistence of data storage (e.g., RAM versus ROM). Computer-readable media as described herein generally refers to either computer-readable storage media or computer-readable transmission media. A computer-readable medium is any entity or device in which information, such as one or more computer programs or portions thereof, can be stored and carried.

[0158] In addition to memory 1804 (e.g., a computer-readable storage medium), processing circuitry 1802 may also be connected to one or more interfaces for displaying, sending, and / or receiving information. These interfaces may include communication interface 1808 and / or one or more user interfaces (e.g., a display, a user input interface). The communication interface may be configured to send and / or receive information, such as to other devices or networks. The communication interface may be configured to send and / or receive information via physical (wired) and / or wireless communication links. Examples of suitable communication interfaces include network interface controllers (NICs), wireless NICs (WNICs), etc.

[0159] The execution of instructions 1806 of the processing circuitry 1802 or the storage of instructions in memory 1804 supports a combination of operations for implementing the exemplary implementations of this disclosure. In this way, apparatus 1800 may include: at least one processing circuitry and at least one memory coupled to the at least one processing circuitry, wherein the at least one processing circuitry is configured to execute instructions stored in the at least one memory. It should also be understood that one or more functions, and combinations thereof, may be implemented by: a dedicated hardware-based computer system and / or processing circuitry that performs the specified function, or a combination of dedicated hardware and program code instructions.

[0160] Some example implementations of this disclosure can also be executed as a computer process defined by one or more computer programs or portions thereof. Example implementations of this disclosure can be executed by executing at least a portion of a computer program including instructions. The computer program can be in source code form, object code form, or some intermediate form. The computer program can be stored in a computer-readable medium that can be read by a computer, processing circuitry system, or other suitable means. As indicated above, for example, the computer program can be stored in memory, such as a computer-readable storage medium. Alternatively or alternatively, for example, the computer program can be stored in a computer-readable transmission medium. The coding of software used to perform example implementations of this disclosure is entirely within the scope of those skilled in the art.

[0161] As will be understood, any suitable instructions may be loaded from memory or a computer-readable medium (e.g., a computer-readable storage medium, a computer-readable transmission medium) onto a computer, processing circuitry, or other programmable means to produce a particular machine, such that the particular machine becomes a component for implementing the functions specified herein. Instructions may also be stored in a computer-readable medium that can instruct a computer, processing circuitry, or other programmable means to operate in a particular manner to produce a particular machine or a particular article of manufacture. In some examples, instructions stored in a computer-readable medium can produce an article of manufacture, wherein the article of manufacture becomes a component for implementing the functions described herein. Instructions may be retrieved from a computer-readable medium and loaded onto a computer, processing circuitry, or other programmable means to configure the computer, processing circuitry, or other programmable means to perform operations that will be performed on or by the computer, processing circuitry, or other programmable means.

[0162] The fetching, loading, and execution of instructions, including program code instructions, can be performed sequentially, such that one instruction is fetched, loaded, and executed once. In some example implementations, fetching, loading, and / or execution can be performed in parallel, such that multiple instructions are fetched, loaded, and / or executed together. The execution of program code instructions can produce computer-implemented processes, such that the instructions, executed by a computer, processing circuitry system, or other programmable device, provide operations for implementing the functions described herein.

[0163] As stated above and reiterated below, this disclosure includes, but is not limited to, the following example implementations.

[0164] Clause 1. A method performed by a Network Function (NF) service consumer, the method comprising: sending a request to an NF service producer for information for a user equipment (UE) for connecting to a radio access network (RAN); receiving information from the NF service producer in response to the request, the information including a value of at least one aggregation rate limiting quality of service (QoS) parameter associated with: the UE, a Protocol Data Unit (PDU) session of the UE, or a group of one or more PDU sessions of the UE for network slicing, the value of the at least one aggregation rate limiting QoS parameter being specific to a radio access technology (RAT) type of the RAN; and applying the information to the UE, the information including at least one aggregation rate limiting QoS parameter having a value specific to a RAT type of the RAN, when the UE connects to the RAN or another RAN of the RAT type.

[0165] Clause 2. The method according to Clause 1, wherein the request sent to the NF service producer includes information indicating the RAT type for the NF service producer to determine the value of at least one aggregate rate limit QoS parameter based on the RAT type.

[0166] Clause 3. The method according to Clause 1 or Clause 2, wherein the method further comprises: determining a change from the RAT type to a second RAT type associated with a UE connection to a second RAN; sending information indicating the second RAT type to an NF service provider; receiving from the NF service provider a second value of at least one aggregation rate limiting QoS parameter, the second value being specific to the second RAT type of the second RAN; and applying at least one aggregation rate limiting QoS parameter having the second value specific to the second RAT type of the second RAN when the UE is connected to the second RAN or another RAN of the second RAT type.

[0167] Clause 4. The method according to any one of Clauses 1 to 3, wherein the information received from the NF service producer includes: multiple values ​​of at least one aggregate rate limiting QoS parameter for multiple RAT types, and wherein the method further includes: storing the multiple values ​​of at least one aggregate rate limiting QoS parameter in UE context information for the UE.

[0168] Clause 5. The method according to any one of Clauses 1 to 4, wherein the NF service consumer is a mobility management NF, the NF service producer is a policy control NF or a unified data management NF, and the information includes access and mobility management information for the UE, and wherein at least one aggregate rate limiting QoS parameter includes an aggregate QoS parameter associated with the UE, the aggregate QoS parameter being the aggregate maximum bit rate for each RAT type UE, and the aggregate maximum bit rate being for RAT type UEs for the RAN.

[0169] Clause 6. The method according to Clause 5, wherein applying the information includes: sending a value of the aggregated maximum bit rate to the RAN, for the RAN to perform aggregated maximum bit rate based on the value.

[0170] Clause 7. The method according to any one of Clauses 1 to 6, wherein the NF service consumer is a session management NF, the NF service producer is a policy control NF, and the information includes session management information for the PDU session of the UE, and wherein the at least one aggregated rate limiting QoS parameter includes an aggregated QoS parameter associated with the PDU session of the UE, the aggregated QoS parameter being an aggregated maximum bit rate for the PDU session of each RAT type for one or more RAT types, and the value of the aggregated maximum bit rate being used for the PDU session of the RAT type for the RAN.

[0171] Clause 8. The method according to Clause 7, wherein applying the information includes: sending a value of the aggregated maximum bit rate for at least one of the user plane NF or UE to perform the aggregated maximum bit rate based on the value.

[0172] Clause 9. The method according to any one of Clauses 1 to 8, wherein the NF service consumer is a mobility management NF, the NF service producer is a policy control NF or a unified data management NF, and the information includes access and mobility management information for the UE, and wherein at least one aggregate rate limiting QoS parameter includes: an aggregate QoS parameter associated with a group of one or more PDU sessions of the UE for a network slice, the aggregate QoS parameter being the maximum bit rate for each RAT type of UE for the network slice, and the value of the maximum bit rate being the group of one or more PDU sessions of the UE for a network slice of RAT type for the RAN.

[0173] Clause 10. The method according to Clause 9, wherein applying the information includes: sending a value of the maximum bit rate to the RAN for the RAN to perform aggregated maximum bit rate based on the value.

[0174] Clause 11. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus to perform the method of any one of Clauses 1 to 10.

[0175] Clause 12. An apparatus comprising components for performing the method described in any one of Clauses 1 to 10.

[0176] Clause 13. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 1 to 10.

[0177] Clause 14. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 1 to 10.

[0178] Clause 15. A computer program comprising instructions that, in response to execution by at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 1 to 10.

[0179] Clause 16. A method performed by a Network Function (NF) service provider, the method comprising: receiving a request from an NF service consumer for information for a user equipment (UE) for connecting to a radio access network (RAN), the request including information indicating the radio access technology (RAT) type of the RAN; determining, based on the RAN's RAT type, the value of at least one aggregate rate limiting quality of service (QoS) parameter associated with the UE, a group of Protocol Data Unit (PDU) sessions of the UE, or one or more PDU sessions of the UE for network slicing; and, in response to the request, sending the information to the NF service consumer, the information including the value of the at least one aggregate rate limiting QoS parameter.

[0180] Clause 17. The method according to Clause 16, wherein the method further comprises: determining a change from a RAT type to a second RAT type associated with a UE-to-second RAN connection; receiving from an NF service consumer information indicating the second RAT type associated with the UE-to-second RAN connection; determining a second value for at least one aggregation rate limiting QoS parameter based on the second RAT type; and sending the second value of at least one aggregation rate limiting QoS parameter to the NF service consumer.

[0181] Clause 18. The method according to Clause 16 or Clause 17, wherein determining the value of the at least one aggregate rate limiting QoS parameter comprises: determining multiple values ​​of the at least one aggregate rate limiting QoS parameter for multiple RAT types, and wherein the information sent to the NF service consumer includes the multiple values ​​of the at least one aggregate rate limiting QoS parameter.

[0182] Clause 19. The method according to any one of Clauses 16 to 18, wherein the NF service producer is a policy control NF or a unified data management NF, the NF service consumer is a mobility management NF, and the information includes access and mobility management information for the UE, and wherein at least one aggregate rate limiting QoS parameter includes an aggregate QoS parameter associated with the UE, the aggregate QoS parameter being an aggregate maximum bit rate for each RAT type UE, and the value of the aggregate maximum bit rate being used for RAT type UEs for the RAN.

[0183] Clause 20. The method according to any one of Clauses 16 to 19, wherein the NF service producer is a policy control NF, the NF service consumer is a session management NF, and the information includes session management information for a PDU session of the UE, and wherein at least one aggregate rate limiting QoS parameter includes an aggregate QoS parameter associated with a PDU session of the UE, the aggregate QoS parameter being an aggregate maximum bit rate for a PDU session of each RAT type for one or more RAT types, and the value of the aggregate maximum bit rate is used for a PDU session of a RAT type for the RAN.

[0184] Clause 21. The method according to any one of Clauses 16 to 20, wherein the NF service producer is a policy control NF or a unified data management NF, the NF service consumer is a mobility management NF, and the information includes access and mobility management information for the UE, and wherein at least one aggregate rate limiting QoS parameter includes: an aggregate QoS parameter associated with a group of one or more PDU sessions of the UE for a network slice, the aggregate QoS parameter being the maximum bit rate for each RAT type of UE for the slice, and the value of the maximum bit rate being the group of one or more PDU sessions of the UE for a network slice of RAT type of RAN.

[0185] Clause 22. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus to perform the method of any one of Clauses 16 to 21.

[0186] Clause 23. An apparatus comprising components for performing the method described in any one of Clauses 16 to 21.

[0187] Clause 24. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry system, cause a device to perform any one of Clauses 16 to 21.

[0188] Clause 25. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry system, cause a device to perform any one of Clauses 16 to 21.

[0189] Clause 26. A computer program comprising instructions that, in response to execution by at least one processing circuitry system, cause a device to perform any one of Clauses 16 to 21.

[0190] Clause 27. A method comprising: receiving a request relating to a session management (SM) policy association for establishing or modifying a protocol data unit (PDU) session for a user equipment (UE) associated with a network slice; receiving information indicating a remaining maximum bit rate associated with a group of one or more PDU sessions associated with the network slice, the remaining maximum bit rate having: a value specific to the radio access technology (RAT) type of a radio access network (RAN) to which the UE is connected, or a value common to at least two RAT types including the RAT type of the RAN; making a policy decision to accept or reject the establishment or modification of the SM policy association based on whether the value of the remaining maximum bit rate is higher than a value of the authorized maximum bit rate for the PDU session; and sending a response to the request, the response including information indicating the policy decision.

[0191] Clause 28. The method according to Clause 27, wherein the remaining maximum bit rate is associated with a group of one or more PDU sessions of the UE, and the value of the aggregated maximum bit rate is specific to the RAT type of the RAN to which the UE is connected.

[0192] Clause 29. The method according to Clause 27 or Clause 28, wherein the remaining maximum bit rate is associated with a group of one or more PDU sessions of a UE group, the UE group including the UE, and the value of the remaining maximum bit rate is specific to the RAT type of the RAN to which the UE is connected.

[0193] Clause 30. The method according to any one of Clauses 27 to 29, wherein the remaining maximum bit rate is associated with a group of one or more PDU sessions that include the UE group, and the value of the remaining maximum bit rate is common among at least two RAT types including the RAT type to which the UE is connected.

[0194] Clause 31. The method according to Clause 30, wherein the network slice has a corresponding network slice identifier associated with at least two RAT types, and the remaining maximum bit rate is associated with each of the corresponding network slice identifiers, and wherein information indicating the remaining maximum bit rate is received based on one of the corresponding network slice identifiers, which is associated with the RAT type of the RAN to which the UE is connected.

[0195] Clause 31. The method according to Clause 30 or Clause 31, wherein the network slice has a corresponding network slice identifier associated with at least two RAT types, and the remaining maximum bit rate is associated with the master network slice identifier of the corresponding network slice identifier, and wherein information indicating the remaining maximum bit rate is received based on the master network slice identifier.

[0196] Clause 33. The method according to any one of Clauses 27 to 32, wherein the request is a request to establish or modify an SM policy association, and the request is received from an SM network function (NF).

[0197] Clause 34. The method according to any one of Clauses 27 to 33, wherein the request is a policy control request, and the policy control request is received from a policy control network function (NF), whereby the establishment or modification of the SM policy association for the PDU session is requested.

[0198] Clause 35. The method according to any one of Clauses 27 to 34, wherein the value of the remaining maximum bit rate is higher than the value of the authorized maximum bit rate for the PDU session, and the policy decision is: to accept the establishment or modification of the SM policy association.

[0199] Clause 36. The method according to Clause 35, wherein information indicating the remaining maximum bit rate for network slicing is received from a unified data repository (UDR), and wherein at least one processing circuitry is configured to execute the instruction such that the apparatus further subtracts from the remaining maximum bit rate in the UDR a value for the authorized maximum bit rate for the PDU session.

[0200] Clause 37. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus to perform the method of any one of Clauses 27 to 36.

[0201] Clause 38. An apparatus comprising components for performing the method described in any one of Clauses 27 to 36.

[0202] Clause 39. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry system, cause a device to perform any one of Clauses 27 to 36.

[0203] Clause 40. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry system, cause a device to perform any one of Clauses 27 to 36.

[0204] Clause 41. A computer program comprising instructions that, in response to execution by at least one processing circuitry system, cause a device to perform any one of Clauses 27 to 36.

[0205] Clause 42. A method comprising: discovering a policy control network function (NF) responsible for policy control of a network slice for at least two radio access technology (RAT) types, the at least two RAT types including: the RAT type of a radio access network (RAN) to which a user equipment (UE) is connected; sending a request to the policy control NF relating to a session management (SM) policy associated with the establishment or modification of a protocol data unit (PDU) session for a UE associated with the network slice; and receiving a response to the request, the response including information indicating: accepting or rejecting a policy decision for the establishment or modification of the SM policy association, the policy decision being made by the policy control NF based on a remaining maximum bit rate associated with a group of one or more PDU sessions associated with the network slice, the remaining maximum bit rate having: a value specific to the RAT type of the RAN to which the UE is connected, or a value common to at least two RAT types including the RAT type of the RAN.

[0206] Clause 43. The method according to Clause 42, wherein the remaining maximum bit rate is associated with a group of one or more PDU sessions of a UE group, the UE group including the UE, and the value of the remaining maximum bit rate is specific to the RAT type of the RAN to which the UE is connected.

[0207] Clause 44. The method according to Clause 42 or Clause 43, wherein the remaining maximum bit rate is associated with a group of one or more PDU sessions that include the UE group, and the value of the remaining maximum bit rate is common to at least two RAT types, including the RAT type of the RAN to which the UE is connected.

[0208] Clause 45. The method according to Clause 44, wherein the network slice has a corresponding network slice identifier associated with the at least two RAT types, and the remaining maximum bit rate is associated with each of the corresponding network slice identifiers, and wherein the request includes a corresponding network slice identifier among the corresponding network slice identifiers associated with the RAT type of the RAN to which the UE is connected.

[0209] Clause 46. The method according to Clause 44 or Clause 45, wherein the network slice has a corresponding network slice identifier associated with at least two RAT types, and the remaining maximum bit rate is associated with a master network slice identifier of the corresponding network slice identifier, and wherein the request includes the master network slice identifier.

[0210] Clause 47. The method according to any one of Clauses 42 to 46, wherein discovering the policy control NF comprises: determining, based on network slice profile information for the network slice, a primary RAT type among at least two RAT types supported for the network slice; and discovering the policy control NF supporting the primary RAT type as the policy control NF to which the request is sent.

[0211] Clause 48. The method according to Clause 47, wherein the method is performed by another policy control NF, the establishment or modification of the SM policy association for the PDU session is requested at that other policy control NF, and the network slice profile information is configured at that other policy control NF.

[0212] Clause 49. The method according to Clause 47 or Clause 48, wherein the method further comprises obtaining the network slice profile information from another NF, the network slice profile information being configured at that other NF.

[0213] Clause 50. The method according to any one of Clauses 42 to 49, wherein the method is performed by the Session Management NF, and the request is a request to establish or modify the association of the SM policy.

[0214] Clause 51. The method according to any one of Clauses 42 to 50, wherein the method is performed by another policy control NF, the establishment or modification of the SM policy association for the PDU session is requested at that other policy control NF, and the request is a policy control request.

[0215] Clause 52. An apparatus comprising: at least one memory configured to store instructions; and at least one processing circuitry configured to access the at least one memory and execute the instructions to cause the apparatus to perform the method of any one of Clauses 27 to 36.

[0216] Clause 53. An apparatus comprising components for performing the method described in any one of Clauses 42 to 51.

[0217] Clause 54. A computer-readable medium comprising instructions that, in response to execution by at least one processing circuitry system, cause a device to perform the method described in any one of Clauses 42 to 51.

[0218] Clause 55. A computer-readable storage medium comprising instructions that, in response to execution by at least one processing circuitry system, cause a device to perform any one of Clauses 42 to 51.

[0219] Clause 56. A computer program comprising instructions that, in response to execution by at least one processing circuitry system, cause a device to perform any one of Clauses 42 to 51.

[0220] Benefiting from the teachings presented in the foregoing description and associated drawings, those skilled in the art to which this disclosure pertains will conceive of numerous modifications and other implementations of the disclosure set forth herein. Therefore, it should be understood that this disclosure should not be limited to the specific implementations disclosed, and that modifications and other implementations are intended to be included within the scope of the appended claims. Furthermore, although the foregoing description and associated drawings describe exemplary implementations in the context of certain exemplary combinations of elements and / or functions, it should be understood that different combinations of elements and / or functions may be provided by alternative implementations without departing from the scope of the appended claims. In this regard, for example, combinations of elements and / or functions different from those explicitly described above are also contemplated, as may be set forth in some of the appended claims. Although specific terminology is used herein, it is used only in a general and descriptive sense and not for limiting purposes.< / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat> < / rat>

Claims

1. A device for communication, comprising: At least one memory, the at least one memory being configured to store instructions; as well as At least one processing circuitry system is configured to access the at least one memory and execute the instructions such that the device at least: Receive a request related to establishing or modifying a session management (SM) policy for a Protocol Data Unit (PDU) session, the PDU session being used for a User Equipment (UE) associated with a network slice; Receive information indicating the remaining maximum bit rate associated with a group of one or more PDU sessions, which is associated with the network slice, the remaining maximum bit rate having: a value specific to the Radio Access Technology (RAT) type of the Radio Access Network (RAN) to which the UE is connected, or a value common to at least two RAT types that include the RAT type of the RAN; Based on whether the value of the remaining maximum bit rate is higher than the value of the authorized maximum bit rate for the PDU session, a policy decision is made to accept or reject the establishment or modification associated with the SM policy. as well as Send a response to the request, the response including information instructing the policy decision.

2. The apparatus of claim 1, wherein the remaining maximum bit rate is associated with the group of one or more PDU sessions of the UE, and the value of the aggregated maximum bit rate is specific to the RAT type of the RAN to which the UE is connected.

3. The apparatus of claim 1 or claim 2, wherein the remaining maximum bit rate is associated with the group of one or more PDU sessions of a UE group, the UE group including the UE, and the value of the remaining maximum bit rate is specific to the RAT type of the RAN to which the UE is connected.

4. The apparatus according to any one of claims 1 to 3, wherein the remaining maximum bit rate is associated with the group of one or more PDU sessions comprising the UE group, and the value of the remaining maximum bit rate is common across the at least two RAT types, the at least two RAT types comprising: The RAT type of the RAN to which the UE is connected.

5. The apparatus of claim 4, wherein the network slice has a corresponding network slice identifier associated with the at least two RAT types, and the remaining maximum bit rate is associated with each of the corresponding network slice identifiers, and The information indicating the remaining maximum bit rate is based on the receipt of a corresponding network slice identifier, which is associated with the RAT type of the RAN to which the UE is connected.

6. The apparatus of claim 4 or claim 5, wherein the network slice has: a corresponding network slice identifier associated with the at least two RAT types, and the remaining maximum bit rate is associated with a master network slice identifier of the corresponding network slice identifier, and The information indicating the remaining maximum bit rate is received based on the main network slice identifier.

7. The apparatus according to any one of claims 1 to 6, wherein the request is: a request for the establishment or modification of the SM policy association, and the request is received from the SM network function NF.

8. The apparatus according to any one of claims 1 to 7, wherein the request is a policy control request, and the policy control request is received from a policy control network function NF, and the establishment or modification of the SM policy association for the PDU session is requested at the policy control network function.

9. The apparatus according to any one of claims 1 to 8, wherein the value of the remaining maximum bit rate is higher than the value of the authorized maximum bit rate for the PDU session, and the policy decision is to accept the establishment or modification associated with the SM policy.

10. The apparatus of claim 9, wherein the information indicating the remaining maximum bit rate for the network slice is received from a unified data repository (UDR), and wherein the at least one processing circuitry is configured to execute the instructions such that the apparatus further subtracts the value of the authorized maximum bit rate for the PDU session from the remaining maximum bit rate in the UDR.

11. An apparatus for communication, comprising: At least one memory, the at least one memory being configured to store instructions; as well as At least one processing circuitry system is configured to access the at least one memory and execute the instructions such that the device at least: Discovery Policy Control Network Function (NF), the Policy Control NF is responsible for: policy control for network slices for at least two Radio Access Technology (RAT) types, the at least two RAT types including: the RAT type of the Radio Access Network (RAN) to which the User Equipment (UE) is connected; Send a request to the policy control NF, the request relating to the establishment or modification of a session management SM policy for a Protocol Data Unit (PDU) session, the PDU session being used by the UE associated with the network slice; and A response to the request is received, the response including information indicating whether to accept or reject the establishment or modification policy decision associated with the SM policy, the policy decision being made by the policy-controlled NF based on the remaining maximum bit rate associated with a group of one or more PDU sessions, the group of one or more PDU sessions being associated with the network slice, the remaining maximum bit rate having: a value specific to the RAT type of the RAN to which the UE is connected, or a value common to at least two RAT types including the RAT type of the RAN.

12. The apparatus of claim 11, wherein the remaining maximum bit rate is associated with the group of one or more PDU sessions of a UE group, the UE group including the UE, and the value of the remaining maximum bit rate is specific to the RAT type of the RAN to which the UE is connected.

13. The apparatus of claim 11 or claim 12, wherein the remaining maximum bit rate is associated with the group of one or more PDU sessions comprising the UE group, and the value of the remaining maximum bit rate is common across the at least two RAT types, the at least two RAT types including the RAT type of the RAN to which the UE is connected.

14. The apparatus of claim 13, wherein the network slice has a corresponding network slice identifier associated with the at least two RAT types, and the remaining maximum bit rate is associated with each of the corresponding network slice identifiers, and The request includes: A corresponding network slice identifier associated with the RAT type of the RAN to which the UE is connected.

15. The apparatus of claim 13 or claim 14, wherein the network slice has: a corresponding network slice identifier associated with the at least two RAT types, and the remaining maximum bit rate is associated with a master network slice identifier of the corresponding network slice identifier, and The request includes the main network slice identifier.

16. The apparatus according to any one of claims 11 to 15, wherein the apparatus caused to discover the policy control NF comprises the apparatus caused to perform: Based on the network slice profile information used for the network slice, determine the primary RAT type among the at least two RAT types supported for the network slice; and A policy control NF that supports the main RAT type is discovered, which is the policy control NF to which the request is sent.

17. The apparatus of claim 16, wherein the apparatus is configured to implement another policy control NF, the establishment or modification of the SM policy association for the PDU session is requested at the other policy control NF, and the network slice profile information is configured at the other policy control NF.

18. The apparatus of claim 16 or claim 17, wherein the at least one processing circuitry is configured to execute the instructions such that the apparatus: further acquires the network slice profile information from another NF, the network slice profile information being configured to be acquired at the other NF.

19. The apparatus according to any one of claims 11 to 18, wherein the apparatus is configured to implement session management NF, and the request is a request for establishment or modification associated with the SM policy.

20. The apparatus according to any one of claims 11 to 19, wherein the apparatus is configured to implement another policy control NF, wherein the establishment or modification of the SM policy association for the PDU session is requested at the other policy control NF, and the request is a policy control request.

Images