Method and apparatus for activating a ruleset based on operational criteria

Abstract

A user equipment (UE) can select a rule set of a plurality of rule sets based on one or more operational criteria associated with the UE. The rule set can be used to at least partially define a user equipment route selection policy (URSP). Each rule of the rule set can correspond to a respective rule set identifier of a plurality of rule set identifiers. The rule set can include a plurality of traffic descriptors (TDs) and a plurality of route selection descriptors (RSDs) corresponding to the plurality of TDs. The UE can transmit user plane traffic matching a TD of the rule set selected based on the one or more operational criteria associated with the UE, where the user plane traffic is transmitted via a route indicated by one of the RSDs associated with the TD of the selected rule set.

Description

Related applications

[0001] This application claims priority to UK Patent Application No. 2404872.0, filed on 5 April 2024, which is incorporated herein by reference in its entirety as if reproduced in its entirety. Technical Field

[0002] The examples generally relate to wireless communication, and more specifically, but not exclusively, to methods, apparatus, and computer program products for activating rule sets based on operational criteria. Background Technology

[0003] Some communication devices can be configured to communicate via one or more communication paths. For example, a User Equipment (UE) can be configured to transmit one or more data packets using a communication path specified in a path selection policy. This path selection policy can include a single path selection rule set that provides a mapping between communication paths and corresponding types of communication services. For example, the path selection rule set can specify that a particular type of communication service will be relayed via a specific path. Path types that can be specified by the path selection rule set include various Session and Service Continuity (SSC) modes, network slices, data networks, PDU session types, and / or access types. For example, a UE can be configured to use a specific network slice to transmit a specific type of data (e.g., data associated with a specific application). However, conventional path selection policies do not take into account various non-service-based conditions and criteria, such as UE-based operational criteria, which may limit communication effectiveness and present other challenges. Summary of the Invention

[0004] According to one or more examples described herein, a communication device (such as a user equipment (UE)) may be provided with multiple sets of path selection rules. Each of these multiple sets of rules may correspond to one or more operating criteria of the communication device, enabling the communication device to select one or more sets of path selection rules based on one or more operating criteria. For example, a first set of rules may correspond to an energy-saving mode of the communication device, and a second set of rules may correspond to a high-performance mode (e.g., for increased communication throughput). Accordingly, the communication device may select or otherwise utilize the first set of rules when the communication device is in energy-saving mode, and select or otherwise utilize the second set of rules when the communication device is in high-performance mode. This technique enables the communication device to customize the utilization of various communication paths to better match various operating criteria, conditions, capabilities, and / or states of the communication device, which can improve performance, increase communication efficiency, and reduce power consumption.

[0005] In one aspect, a method includes: a UE selecting a set of rules from a plurality of rule sets based on one or more operating criteria associated with the UE, the rule sets defining at least partially a User Equipment Path Selection Policy (URSP), each rule in the rule sets corresponding to a corresponding rule set identifier among a plurality of rule set identifiers, wherein the rule sets include a plurality of service descriptors (TDs) and a plurality of path selection descriptors (RSDs) corresponding to the plurality of TDs; and the UE transmitting a user plane service matching a TD in the selected rule set, wherein the user plane service is transmitted via a path indicated by one of the RSDs associated with the TD in the selected rule set.

[0006] In some examples, one or more operating criteria associated with the UE include one or more of the following: (i) the UE operates in an energy-saving mode, (ii) the UE operates in an on-duty mode associated with the user's occupation, or (iii) the UE operates in a personal use mode. In some examples, the method further includes: receiving a user equipment configuration for the UE from the core network of the communication network, the user equipment configuration including multiple rule sets and multiple rule set identifiers; and storing the multiple rule sets and the multiple rule set identifiers for future use.

[0007] In some examples, the method further includes sending an indication of the selected rule set to the core network. In some examples, the method further includes receiving an indication of an operating mode selected by the user for the UE, wherein the selection further includes selecting a rule set based on the operating mode for the UE. In some examples, the method further includes determining that one or more operating criteria associated with the UE are met, wherein the UE selects a rule set in response to the satisfaction of one or more operating criteria.

[0008] In some examples, the method further includes receiving from the core network an indication of one or more network slices corresponding to one or more rule sets among a plurality of rule sets, wherein the UE transmits user plane services on one or more paths associated with the one or more network slices. In some examples, the RSDs among the plurality of RSDs include an indication of at least one rule set identifier. In some examples, the TDs among the plurality of TDs include an indication of at least one rule set identifier. In some examples, the plurality of rule set identifiers are based on corresponding values ​​for one or more of: (i) path selection verification criteria or (ii) TD verification criteria. In some examples, one or more rule set identifiers are associated with at least a user-selectable setting identified using human-readable characters.

[0009] In another approach, one method includes: generating (i) multiple rule sets that at least partially define multiple URSPs, and (ii) multiple rule set identifiers corresponding to the multiple rule sets, wherein the rule sets in the multiple rule sets include multiple TDs and multiple RSDs corresponding to the multiple TDs; and configuring the UE using the multiple rule sets based on the generation of the multiple rule sets. In some examples, the method further includes: sending to the UE an association between a rule set identifier among the multiple rule set identifiers and a user-selectable setting identified using human-readable characters.

[0010] In some examples, the method further includes: sending to the UE an indication of one or more network slices corresponding to one or more URSP rule sets in a plurality of URSP rule sets, wherein the indication of the selected URSP rule set in the plurality of URSP rule sets is received via one or more network slices. In some examples, the method further includes: receiving from the UE an indication of the selected rule set in the plurality of rule sets. In some examples, the method further includes: sending to the UE an indication of one or more network slices corresponding to one or more rule sets in the plurality of rule sets.

[0011] In some examples, an RSD among multiple RSDs includes an indication of at least one rule set identifier. In some examples, a TD among multiple TDs includes an indication of at least one rule set identifier. In some examples, multiple rule set identifiers are based on corresponding values ​​for one or more of the following: (i) path selection validation criteria or (ii) TD validation criteria. In some examples, one or more rule set identifiers are associated with user-selectable settings identified using human-readable characters. In some examples, one or more rule set identifiers are associated with user-selectable settings identified using human-readable characters.

[0012] In one aspect, a UE includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the UE to perform an operation comprising: selecting a rule set from a plurality of rule sets based on one or more operation criteria associated with the UE, the rule set being used to at least partially define a URSP, each rule in the rule set corresponding to a corresponding rule set identifier in a plurality of rule set identifiers, wherein the rule set includes a plurality of TDs and a plurality of RSDs corresponding to the plurality of TDs; and transmitting a user plane service matching a TD in the selected rule set, wherein the user plane service is transmitted via a path indicated by an RSD in one of the RSDs associated with the TD in the selected rule set.

[0013] In another aspect, an apparatus includes: at least one processor; and at least one memory storing instructions for policy control functions of the core network of a communication network, wherein execution of the instructions by the at least one processor causes the apparatus to perform operations including: generating (i) a plurality of rule sets that at least partially define a plurality of URSPs and (ii) a plurality of rule set identifiers corresponding to the plurality of rule sets, wherein the rule sets in the plurality of rule sets include a plurality of TDs and a plurality of RSDs corresponding to the plurality of TDs; and configuring a UE using the plurality of rule sets based on the generation of the plurality of rule sets.

[0014] In one aspect, a non-transitory computer-readable storage medium includes program instructions stored thereon configured to perform at least the following: selecting a rule set from a plurality of rule sets based on one or more operating criteria associated with a UE, the rule set being used to at least partially define a URSP, each rule in the rule set corresponding to a corresponding rule set identifier among a plurality of rule set identifiers, wherein the rule set includes a plurality of TDs and a plurality of RSDs corresponding to the plurality of TDs; and transmitting a user plane service matching a TD in the selected rule set, wherein the user plane service is transmitted via a path indicated by an RSD in one of the RSDs associated with the TD in the selected rule set.

[0015] On the other hand, a non-transitory computer-readable storage medium includes program instructions stored thereon, the program instructions being configured to perform at least the following: generating (i) a plurality of rule sets that at least partially define a plurality of URSPs and (ii) a plurality of rule set identifiers corresponding to the plurality of rule sets, wherein the rule sets in the plurality of rule sets include a plurality of TDs and a plurality of RSDs corresponding to the plurality of TDs; and configuring the UE using the plurality of rule sets based on the generation of the plurality of rule sets.

[0016] In one aspect, a UE includes: components for selecting a rule set from a plurality of rule sets based on one or more operating criteria associated with the UE, the rule set defining at least partially a URSP, each rule in the rule set corresponding to a corresponding rule set identifier among a plurality of rule set identifiers, wherein the rule set includes a plurality of TDs and a plurality of RSDs corresponding to the plurality of TDs; and components for transmitting user plane services matching the TDs in the selected rule set, wherein the user plane services are transmitted via a path indicated by one of the RSDs associated with the TDs in the selected rule set.

[0017] In another aspect, an apparatus includes: components for generating (i) a plurality of rule sets that at least partially define a plurality of URSPs and (ii) a plurality of rule set identifiers corresponding to the plurality of rule sets, wherein the rule sets in the plurality of rule sets include a plurality of TDs and a plurality of RSDs corresponding to the plurality of TDs; and components for configuring a UE using the plurality of rule sets based on the generation of the plurality of rule sets.

[0018] In one aspect, a core network includes: an access management function configured to: generate (i) multiple rule sets for at least partially defining multiple URSPs and (ii) multiple rule set identifiers corresponding to the multiple rule sets, wherein the rule sets in the multiple rule sets include multiple TDs and multiple RSDs corresponding to the multiple TDs; and a policy control function configured to: configure a UE using the multiple rule sets based on the generation of the multiple rule sets. Attached Figure Description

[0019] Having described above certain exemplary aspects of this disclosure in general terms, this document will now refer to the accompanying drawings, which are not necessarily drawn to scale, and in which:

[0020] Figure 1 An example of a communication network that supports an activation rule set based on operational guidelines, as described herein, is shown.

[0021] Figure 2 The present disclosure illustrates means that may include various components configured to perform operations for the techniques disclosed herein.

[0022] Figure 3 The present disclosure illustrates means that may include various components configured to perform operations for the techniques disclosed herein.

[0023] Figure 4 An example is shown that supports a signaling graph based on an operational criterion activation rule set, as described in this document.

[0024] Figure 5 An example is shown that supports a processing flow based on an activation rule set of operational criteria, as described in this article.

[0025] Figure 6 An example is shown that supports a processing flow based on an activation rule set of operational criteria, as described in this article.

[0026] Figure 7 An example is shown that supports a processing flow based on an activation rule set of operational criteria, as described in this article.

[0027] Figure 8An example is shown that supports a processing flow based on an activation rule set of operational criteria, as described in this article.

[0028] Figure 9 An example is shown that supports a processing flow based on an activation rule set of operational criteria, as described in this article.

[0029] Figure 10 An example flowchart is shown that supports the activation of rule sets based on operational guidelines, as described in this article.

[0030] Figure 11 An example flowchart is shown that supports the activation of rule sets based on operational guidelines, as described in this article.

[0031] Figure 12 An example flowchart is shown that supports the activation of rule sets based on operational guidelines, as described in this article.

[0032] Figure 13 An example flowchart is shown that supports the activation of rule sets based on operational guidelines, as described in this article.

[0033] Figure 14 An example flowchart is shown that supports the activation of rule sets based on operational guidelines, as described in this article.

[0034] Figure 15 An example flowchart is shown that supports the activation of rule sets based on operational guidelines, as described in this article.

[0035] Figure 16 An example is shown that supports a processing flow based on an activation rule set of operational criteria, as described in this article.

[0036] Figure 17 An example is shown that supports a processing flow based on an activation rule set of operational criteria, as described in this article.

[0037] Figure 18 An example is shown that supports a processing flow based on an activation rule set of operational criteria, as described in this article.

[0038] Figure 19 An example flowchart is shown that supports the activation of rule sets based on operational guidelines, as described in this article.

[0039] Figure 20 An example flowchart is shown that supports the activation of rule sets based on operational guidelines, as described in this article. Detailed Implementation

[0040] Some aspects of this disclosure will now be described more fully below with reference to the accompanying drawings, in which some, but not all, aspects of this disclosure are illustrated. In fact, various aspects of this disclosure may be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these examples are provided so that this disclosure will meet the requirements of applicable law. Similar reference numerals refer to similar elements throughout. As used herein, the terms “data,” “content,” “information,” and similar terms are used interchangeably to refer to data that can be transmitted, received, and / or stored according to the examples of this disclosure. Therefore, any use of such terms should not be considered as limiting the spirit and scope of the exemplary aspects of this disclosure.

[0041] This disclosure provides apparatus, methods, and computer-readable media for activating rule sets based on operational guidelines. The decision to select a single network slice selection assistance information (S-NSSAI) and data network name (DNN) to serve a specific service of a user equipment (UE) can be based on a local configuration at the UE or a UE path selection policy (URSP) configured at the UE by the Home Public Land Mobile Network (HPLMN). More specifically, if the UE has URSP rules (e.g., a rule set), it uses those URSP rules, and the local configuration in the UE can only be used to match applied services to a specific connectivity if it cannot use those URSP rules (e.g., no URSP rules are matched). For example, the UE may have a local configuration to select an Internet Protocol Multimedia Subsystem (IMS) DNN and / or an enhanced mobile broadband (eMBB) slice, and then match all rules for that Internet DNN.

[0042] A URSP (e.g., the rule set associated with the URSP) may include one or more Path Selection Descriptors (RSDs) associated with one or more Service Descriptors (TDs). The RSD associated with the TD can determine which S-NSSAI and DNN will be used for a specific service identified in the TD of the URSP rule. The RSD may be subject to certain conditions based on time and UE location (e.g., path selection verification criteria). The RSD of the URSP rule defines the S-NSSAI and DNN that will be used for connectivity. The validity of the RSD is also considered valid based on whether the associated S-NSSAI is included in the allowed Network Slice Selection Assistance Information (NSSAI). Starting with rel-18, if the S-NSSAI of the RSD is not included in the allowed NSSAI, and if the S-NSSAI is in the configured NSSAI, the UE may attempt to register with the S-NSSAI before considering the RSD invalid (making the S-NSSAI part of the allowed NSSAI).

[0043] URSP includes a list of URSP rules, which are further described in 3GPP TS 23.503 and 3GPP TS 24.526. Each URSP rule contains a rule priority, a TD (Distributed Term), and a list of path selection descriptors. The rule priority determines the order in which the UE executes URSP rules. Service descriptors can be used to determine whether a rule matches. Matching can be based on, for example, application descriptors, destination IP or non-IP descriptors, DNNs, domain descriptors, and / or connectivity capabilities. Application descriptors can include an Operating System Identifier (OSID) and / or one or more OS-Specific Application Identifiers (OSAppIDs). Destination IP and / or non-IP descriptors can include a destination IP address or prefix, a destination port number, or a protocol ID. Domain descriptors can include a destination Fully Qualified Domain Name (FQDN) or a regular expression, which can be used as a domain name matching criterion. Connectivity capabilities can include the capabilities described in Section 5.2 of 3GPP TS 24.526, which can include the format and value of connectivity capabilities. In some examples, service categories can be encoded within a Connectivity Capability Information Element (IE). One or more values ​​can be provided.

[0044] The path selection descriptor may include Session and Service Continuity (SSC) mode selection (e.g., a signal value), Network Slice selection (e.g., one or more S-NSSAI), DNN selection (e.g., one or more DNNs), PDU session type selection (e.g., a single value, such as IP4v6 or IPv6), Access Type Preference (e.g., indicating the preferred access type, such as 3GPP or non-3GPP), and / or path selection verification criteria. Path selection verification criteria may include a time window indicating a time window when matching traffic is permitted. Additionally or alternatively, path selection verification criteria may include a location criterion indicating the UE location where matching traffic is permitted.

[0045] Path selection verification criteria are limited to time and location. However, it may be expected that the RSD (and even TD) of URSP can rely on some “activation / selection” criteria, which can be simply defined by settings or logic in the UE.

[0046] In other words, in the current specification, the UE is supplied with a single URSP rule set, which applies regardless of the UE state and / or UE settings. The technique described herein allows the UE to switch to different rule sets based on user input, settings selectable by the user within the UE, and / or logic, depending on factors such as whether the user or UE intends to conserve energy, maximize performance, operate under on-duty or off-duty settings of a public safety agent, or operate in personal or enterprise mode. Similar concepts can be applied to local configuration. The technique described herein also provides examples of how to configure the UE using these different rules.

[0047] The techniques described herein enable HPLMN to configure UEs using URSP rules or local configuration information that is activated based on UE-local information (e.g., user-driven UE settings for higher performance or lower battery consumption). In the case of local configuration, the UE can be configured with a set of rules that depend on UE settings that can be selected by the user. The UE can then operate according to the selected options. In the case of URSP, one aspect of this disclosure is identifying in the network the UE's ability to support rule set selection / activation features (e.g., URSP set selection / activation features). This includes sending an indication of this capability as part of the AMF during registration when the UE sends a UE policy container. When the AMF creates / updates a UE policy association, it sends the UE policy container to the PCF, thus making the PCF aware of the UE's feature support.

[0048] When the PCF receives an indication of support for rule set selection / activation features (e.g., an indication of UE capability), the PCF supplies the relevant rule set for that subscriber to the UE. Each rule set TD and RSD are tagged with the rule set ID. TDs and RSDs with the same value can belong to one or more rule sets and are tagged with the value of that rule set ID. All UEs are configured with a default rule set unless they indicate support for rule set selection / activation features. For UEs that do not support the feature, the default set is tagged with no rule set ID (treated as a normal URSP rule) and corresponds to the default subscription setting of the UE's Subscriber Permanent Identifier (SUPI). For UEs that indicate support for rule set selection / activation features, the default rule set can be associated with any value.

[0049] In one aspect, the default rule set in a UE that supports the rule set selection / activation feature is associated with a specific value that will be defined in the standard, which is understood to mean that the UE uses that set unless the UE or the user selects a different option. In another aspect, the initial setting when a UE is first configured with URSP rules is always the setting associated with the default rule set state.

[0050] On the other hand, there is the activation of specific rule sets. The rule set ID is based on one of the settings that can be selected by the user at the UE or by the UE based on certain logic running at the UE. The settings at the UE can be provided directly by the user (manual behavior selection) or can be automatic (based on the UE's logic).

[0051] For example, a battery / energy-efficient URSP set can be activated because the user settings in the UE have selected a low-power mode (manually selected) or because the battery is low (if automatic selection is enabled by the user). As a result of selecting the battery-efficient rule set, the UE can switch the connection to a "low-power" network slice, which allows the UE to save battery (e.g., the slice used is associated with a different discontinuous reception (DRX) timer, the UE is put into Radio Resource Control (RRC) inactive state more quickly, Radio Resource Management (RRM) changes to a more battery-efficient state, etc.), and also adopts energy-efficient RAN behavior in the network.

[0052] As another example, employees of public safety agencies can set off-duty behavior for UEs and activate access to a set of network slices that are not available when on duty (e.g., on-duty network slices are only associated with public safety access and other network slices are not allowed, while off-duty network slices are only used when the UE user is off duty).

[0053] When the settings at the UE change based on local or network actions, the UE should select the relevant rule set, retain only connections shared with the new set, and immediately evaluate the new URSP rules.

[0054] One aspect also includes an indication of rule set selection support in the UE MM capability, which triggers an indication of this capability to the Unified Data Management (UDM) function, and can also enable the indication of the relevant subscription S-NSSAI and DNN set as part of the subscription information. This indication then causes the configured NSSAI for each rule set ID to be sent to the UE. However, this indication is optional, and this feature should also work using a single configured NSSAI valid for all rule set IDs.

[0055] On the other hand, the UE receives a single rule set, but if the UE has already received multiple configured NSSAIs (one for each rule set ID), changes to the settings at the UE result in different configured NSSAIs being used. Therefore, some S-NSSAIs can be added, and some must be removed from the allowed NSSAIs. In some examples, these changes can cause some local RSDs to become active or inactive.

[0056] In one aspect, for manual selection, the rule set ID is provided with a mapping to a human-readable string that identifies options that can be displayed in the device settings, and these options can therefore be manually selected by the user. When the user selects such an option, the corresponding rule set ID is selected.

[0057] In one aspect, for automatic mode, the rule set ID is mapped to a known state supported by the device, which is identified by the PEI received from the UE at the PCF when the UE policy association is established.

[0058] In one aspect, the rule set ID is defined as the value of a new RSD path selection verification criterion and / or a newly introduced TD service descriptor verification criterion. This is understood to mean that if the user (in manual selection mode) and / or the UE (in automatic mode) selects the value of that RSD and / or TD verification criterion as the rule set ID to be used, then the associated RSD and TD are valid. An RSD or TD can be associated with one or more such verification criterion values.

[0059] In one respect, multiple rule set IDs can exist that can be activated simultaneously. In some examples, at least one rule set can be activated at a time.

[0060] In one aspect, the value of a rule set ID or a setting associated with that rule set ID is sent to the network in a registration request and / or PDU session establishment request, and this can be used by the network to further tune network behavior based on the semantics associated with that setting or rule set ID.

[0061] In some examples, the end-user experience (e.g., Quality of Service (QoS) and / or Quality of Experience (QoE)) provided by the communication network can be modulated based on policy, taking into account energy-related considerations. For example, considering different energy-saving profiles, different RAN network configurations can be used for the UE, where some configurations can be followed without QoS degradation due to energy saving. The RAN can benefit from receiving instructions from the PCF on how to perform such modulation for the UE, aiming to perform better modulation and minimize QoS degradation (rather than modulation based on policies configured locally at the RAN). When deriving policies, the PCF can benefit from knowing specific UE preferences, such as those received via UE assistance (e.g., preferred energy settings or energy saving by the UE). For example, the PCF can provide customized service offerings (e.g., policy and charging control (PCC) rules) to match preferences indicated by the UE. One objective is to assist the RAN node in determining how to provide appropriate QoS performance for the services requested by the UE when the UE radio configuration can be modified for energy saving purposes.

[0062] The techniques described herein address several aspects of the challenges described herein. First, a UE can have subscription information related to its preferred energy settings stored in a unified data repository (UDR), accessible by the PCF and UDM. This subscription information can be per UE, per S-NSSAI, and / or per DNN. Second, a UE can assist the network by sending UE assistance information, including its preferred energy settings, to the Access and Mobility Management Function (AMF) and / or Session Management Function (SMF) so that the network can define the most appropriate QoS policies, settings, and UE processing. This value can override any value stored in the UDR. Third, the AMF, SMF, and / or Policy Control Function (PCF) can receive the preferred energy settings information for the UE as UE assistance information via NAS signaling, and can override the information stored in the UDR and / or UDM. The SMF can provide the received information to the PCF. UE assistance can be provided by the UE as part of a PDU session establishment or modification process in an ongoing PDU session, or as part of a Resource Management (RM) process. Fourth, based on the preferred energy settings information, the PCF can derive PCC rules to be provided to the SMF. For example, modified QoS requirements for PDU sessions (e.g., lower Session Aggregate Maximum Bit Rate (AMBR), higher latency) can be considered for energy saving. Based on the received PCC rules, the SMF can update authorized alternative QoS profiles (access-specific QoS parameters) and can also provide UE assistance (regarding preferred energy settings) to the gNB. Furthermore, the SMF can reconfigure or otherwise configure affected QoS flows at the UE. The AMF can also provide new UE-AMBR and / or assistance to the RAN.

[0063] As described herein, system behavior can be controlled based on the UE's preferred energy settings. The techniques described herein propose that if the UE operates in manual mode of energy settings, the end-to-end system behavior for the UE can be modulated based on the preferred energy settings selected by the user at the UE (via enabling the user interface for collecting energy settings), or if the UE operates in automatic mode of energy settings, it can be modulated based on some logic. Alternatively, UE behavior can also be modulated based on one or more subscriptions. End-to-end system behavior can be modulated by selecting network slices and / or DNNs depending on the energy settings. Alternatively, end-to-end system behavior can be modulated by instructions to the network per session and / or slice. These instructions can specify the UE's preferred energy settings, allowing the network to adapt its behavior accordingly.

[0064] The slices used for PDU sessions can be selected based on policies associated with preferred energy settings. The resulting processing can optimize performance and / or energy consumption. For example, RAN and / or network configurations can be used based on the slices, and this can help minimize energy consumption or deliver a given level of performance (e.g., throughput, operating speed).

[0065] If the network receives an indication of a preferred energy setting in a registration message (if the scope is at the UE or slice level) or during PDU session establishment (if the scope is at the session level), the network can adapt system behavior (e.g., QoS / QoE or other aspects, or other behaviors that may depend on implementation and / or configuration) based on policies associated with that energy setting. For example, the RAN, such as in the slice-based scenario described above, can benefit from receiving indications from the PCF (at the session level, as part of the Session Management (SM) process) or from the AMF (or at the UE and / or slice level as part of the RM process), which can influence how modulation is performed for the UE to achieve optimal modulation and minimize QoS degradation. When deriving rules and policies, in addition to subscription information that can be used to set default behavior or limit allowed behavior (in a manner very similar to how subscribing to S-NSSAI determines the allowed network slices for a UE), the PCF and / or AMF can benefit from knowing UE-specific preferences associated with the energy setting. Different RAN configurations can be used depending on the consideration of different energy-saving profiles, where some configurations can be followed without QoS degradation due to energy saving. The instruction from the core network to the NG-RAN can be the energy settings themselves, or it can be a per-PDU session or per-UE instruction that takes into account more information about the UE (including subscription data) available at the PCF. The PCF can provide customized services for the UE (e.g., PCC rules) to match the preferences indicated by the UE. The goal is to assist the RAN network in determining how to provide appropriate QoS performance for the services requested by the UE when the UE's radio configuration can be modified for energy-saving purposes. If the UE does not provide the network with preferred energy settings assistance, the default instruction can be provided solely by the PCF and / or AMF based on subscriptions.

[0066] In some examples, the UE can receive a human-readable tag from the network identifying its selectable energy setting, along with a mapping to the preferred energy setting value to be sent to the network. The preferred energy setting can also be used as a rule set ID (which is the value for each Public Land Mobile Network (PLMN)). For example, when the UE roams, if the URSP is VPLMN-related, the network can set a rule set ID for the visited Public Land Mobile Network (VPLMN). In roaming scenarios, the values ​​of the preferred energy settings that can be used (and the corresponding human-readable tags) are VPLMN-specific and negotiated as part of the roaming protocol.

[0067] In some examples, a UE can be configured with one or more rule sets, which can be selected based on which energy setting is preferred (e.g., when the UE selects an energy setting, this also selects the corresponding rule set associated with a rule set ID equal to the value of that preferred energy setting). Depending on the energy setting at the UE, this configuration can drive the selection of different slices for the same service at the UE. The preferred energy setting at the UE is mapped 1:1 to a rule set ID, which identifies the URSP rule set selected or otherwise activated based on the preferred energy setting. URSP rules can be applied to one or more preferred energy settings and / or rule set IDs. Default energy settings and / or rule sets can be provided by the network, and this applies to UEs that do not support them.

[0068] In some examples, alternatively or additionally, the UE may receive different configuration NSSAIs, each corresponding to one or more values ​​of an energy setting, or additional information may be provided to the UE to associate the S-NSSAIs of the configuration NSSAIs with one or more energy settings. If a single rule set is provided, different energy settings can drive the selection of individual S-NSSAI sets from the configuration NSSAIs, thereby enabling different RSD sets to be verified.

[0069] In some examples, if "manual mode" is used, the user can select a specific energy setting through an appropriate interface at the UE, or the preferred energy setting can be based on the logic running at the UE in "automatic mode". The network can also provide the UE with a default energy setting based on a subscription.

[0070] In some examples, when the preferred energy setting changes at the UE, the relevant rule set (if more than one rule set is provided based on the energy state) (as well as the applicable configuration NSSAI and / or the S-NSSAI set in the configuration NSSAI) is considered for the new preferred energy setting at the UE, and the UE re-evaluates the URSP rules. Therefore, the UE can establish, modify, or release existing PDU sessions and may also request different network slice sets.

[0071] In some examples, when a UE applies a specific URSP rule, the UE also indicates a preferred power setting (e.g., a preferred rule set ID) to the network. This rule set includes instructions on whether to indicate that power setting to the network at the UE level (via the Maximum Reassembly Unit (MRU)), the S-NSSAI level (if the S-NSSAI is applied to the selected preferred power setting, or when the S-NSSAI is registered via the MRU), or the session level (session establishment or modification). When a URSP rule (such as an RSD) applies to several power settings, the UE action for the RSD is an indication to the network of a change to the power setting (e.g., the MRU updates the power setting at the slice level, or the session modifier updates it at the session level). If the setting is provided at the UE level, it may not be provided at the slice or session levels. If the setting is provided at the slice level, it may not be provided at the session level.

[0072] In some examples, the AMF, SMF, and / or PCF can receive preferred energy setting information for the UE from subscription data stored at the UDR (if available), as well as UE auxiliary information received directly from the supported UE via Non-Access Stratum (NAS) SM signaling. The SMF can provide preferred energy setting auxiliary information to the PCF and / or the PCF can obtain this information from the UDR. Depending on the configuration at the UE (as described herein), or based on other configurations or standards-defined provisions, the UE auxiliary information for preferred energy setting can be provided to the network by the UE via the MRU or as part of the PDU session establishment process, and accordingly, can be updated via the MRU and / or the PDU session modification process of an ongoing PDU session.

[0073] In some examples, based on preferred energy setting information, depending on network settings and signaling used by the UE to provide preferred energy setting assistance information, the AMF, SMF, and / or PCF may provide instructions (e.g., provide UE-assisted preferred energy settings) to the next-generation RAN (NG-RAN) for a PDU session (associated with the SM context of the PDU session sent to the gNB), the UE (as indicated in Solution #24), or a network slice (associated with an allowed S-NSSAI or a partially allowed NSSAI sent to the NG-RAN), to the gNB.

[0074] In some examples, depending on the received preferred energy settings, the PCF can derive or modify the QoS policy to be provided to the SMF. Based on the received policy rules, the SMF can update authorized alternative QoS profiles (e.g., access-specific QoS parameters). Depending on the received preferred energy settings, the AMF can provide either UE-AMBR or UE-Slice-MBR. The values ​​of UEAMBR and UE-Slice-MBR can be defined according to the UE preferred energy settings.

[0075] The techniques described herein can have several impacts on services, entities, and interfaces. For example, a UE can support the configuration of preferred energy settings (e.g., rule set IDs and / or rule sets) as described above. UE assistance related to preferred energy settings is provided to the network according to instructions. Network nodes (such as gNBs) can consider processing radio configurations based on QoS profiles with UE assistance related to energy settings preferences. The SMF can process QoS profiles based on UE assistance related to energy settings preferences. Alternatively or additionally, the SMF can retrieve UE subscription information related to energy settings preferences from the UDM. The PCF can process PCC rules based on the configuration of UE assistance related to energy settings preferences and / or the rule sets described herein. The UDM can store UE subscription information related to energy settings preferences. The AMF can retrieve UE subscription information related to energy settings preferences from the UDM and optionally provide UE assistance for preferred energy settings to the NG-RAN.

[0076] Although the methods, apparatuses, and computer program products described herein are described in the context of 5G core networks and systems, they can still be applied in a broader context within any suitable telecommunications system, network, standard, or protocol. For example, the methods, apparatuses, and computer program products described herein can be applied in a 6G context, an advanced 5G context, and / or similar contexts.

[0077] As used herein, the term "user equipment" or "UE" refers to any device configured for operation by a user to communicate with or within a communication network. Other terms used synonymously with "user equipment" or "UE" herein include communication equipment, user equipment, telephone, smartphone, tablet, etc. A UE can be a device that provides voice / data connectivity to a user, such as a handheld device with wireless connectivity. As described herein, some examples of UEs may include mobile phones, tablets, computers with wireless transceiver capabilities (such as laptops, handheld computers, etc.), mobile internet devices (MIDs), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control equipment, wireless terminals in autonomous vehicles, wireless devices in telemedicine equipment, terminals, wireless terminals in smart grids, wireless terminals in traffic safety equipment, wireless terminals in smart city equipment, wireless terminals in smart home equipment, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices, or other processing devices connected to a wireless modem, in-vehicle equipment, wearable devices, terminal devices in 5G networks, or terminal devices in the future evolution of public land mobile networks (PLMNs), etc.

[0078] Additionally, a UE can also be a device in an Internet of Things (IoT) system. IoT is a crucial part of the future development of information technology. Its main technical characteristic is connecting objects to a network through communication technology, thereby realizing an intelligent network that enables human-machine interaction and machine-to-machine interaction. IoT technology can achieve massive connectivity, deep coverage, and terminal energy saving through technologies such as narrowband (NB).

[0079] As used herein, the term "access node" generally refers to any access network device or equipment that provides network access functionality to authorized users in a specific area and can use transmission tunnels of different qualities depending on user level and service requirements. Terms used synonymously with "access node" in this document may include "network access node," "network node," "node," "access point," "node B," "evolved node B" or "eNB," "next-generation node B" or "gNB," "base station," "base transceiver station," "tower," "relay station," "vehicle-mounted relay," "network entity," "network equipment," etc. Currently, there are two types of radio access technologies: 3GPP access technologies (such as those used in 3G, 4G, or 5G systems) and non-3GPP access technologies. 3GPP access technologies refer to access technologies that conform to 3GPP standards and specifications. For example, access network equipment in a 5G system is called a next-generation node base station (gNB). Non-3GPP access technologies refer to access technologies that do not conform to 3GPP standards and specifications, such as air interface technologies represented by access points (APs) in Wi-Fi.

[0080] Access nodes that implement network access functions based on wireless communication technology can be referred to as access networks and / or radio access networks (RANs). These RANs manage radio resources, provide access services to terminal devices, and thus facilitate the forwarding of control signals and user data between the terminals and the core network.

[0081] Wireless access network equipment may include, but is not limited to: Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (e.g., Home Evolved Node B or Home Node B (HNB)), Baseband Unit (BBU), Access Point (AP) in a Wi-Fi system, Wireless Relay Node, Wireless Backhaul Node, Transport Point (TP), Transmit and Receive Point (TRP), gNB, Transport Point (TRP or TP) in a 5G (e.g., NR) system, Base Station in a 5G system, one or more antenna panels, or network nodes constituting a gNB or Transport Point, such as Baseband Unit (BBU), Distributed Unit (DU), or Next Generation Base Station in a 6G communication system. This application does not limit the specific technology or equipment form adopted by the wireless access network equipment.

[0082] As used herein, the term "Access and Mobility Management Function" or "AMF" refers to a network function belonging to the core network, primarily used for user equipment registration, mobility management, and tracking area update processes in mobile networks. This Access and Mobility Management network element terminates Non-Access Stratum (NAS) messages, is responsible for registration management, connection management, reachability management, allocating tracking area lists (TA lists), and mobility management, and is also responsible for forwarding Session Management (SM) messages to the Session Management network element.

[0083] As used herein, the term “path” refers to a data path, such as the optimal data path, for user plane services (e.g., data services) between the UE and an external data network (e.g., the data network identified by the DNN in the RSD) via the 5G core network.

[0084] As defined herein, “computer-readable storage medium” refers to a non-transitory physical storage medium (e.g., volatile or non-volatile storage device), which can be distinguished from “computer-readable transmission medium”, which refers to an electromagnetic signal. Such a medium can take many forms, including but not limited to non-transitory computer-readable storage media (e.g., non-volatile media, volatile media) and transmission media. Transmission media include, for example, coaxial cables, copper wires, fiber optic cables, and carrier waves that propagate through space without conductors or cables, such as sound waves and electromagnetic waves, including radio waves, light waves, and infrared waves. Signals include artificial transient changes in amplitude, frequency, phase, polarization, or other physical properties transmitted through the transmission medium. Examples of nontransitory computer-readable media include magnetic computer-readable media (e.g., floppy disks, hard disks, magnetic tapes, any other magnetic media), optical computer-readable media (e.g., optical disc read-only memory (CD-ROM), digital versatile optical disc (DVD), Blu-ray disc, etc.), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), FLASH-EPROM, or any other nontransitory media from which a computer can read. The term computer-readable storage medium is used herein to refer to any computer-readable medium other than a transmission medium. However, it will be understood that where aspects are described as using computer-readable storage media, alternatively, other types of computer-readable media may be used in place of or supplemented to that computer-readable storage medium.

[0085] Figure 1An example is shown that supports a communication network 100 based on an operational rule set, as described herein. In some examples, UE 205 can access communication network 100 to communicate with an application server (not shown) carrying third-party application functions (not shown) via data network 202. Communication network 100 includes a radio access network 210 (e.g., NG-RAN) and a core network 204 (e.g., a 5G core network (5GC)) operating based on fifth-generation radio access technology as described in the 3GPP New Radio standard. Core network 204 is connected to the operation and maintenance entity 203 of communication network 100, which is described in further detail below.

[0086] Radio access network 210 includes one or more RAN nodes (also called base stations), such as gNBs. Radio access network nodes may include a central unit (e.g., gNB-CU) and one or more distributed units (e.g., one or more gNB-DUs) linked to the central unit (e.g., gNB-CU) via an F1 interface.

[0087] Core network 204 has a service-based architecture and includes multiple network functions, including AMF, AF, Authentication Server Function (AUSF), Network Open Function (NEF), Network Repository Function (NRF), Network Slice Selection Function (NSSF), PCF, SMF, User Plane Function (UPF), and UDM. Other network functions of core network 204 may include Binding Support Function (BSF) and / or Charging Function (CHF). The functionality of the core network functions is well known to those skilled in the art and therefore will not be described in detail.

[0088] Each Network Function (NF) of core network 204 can provide one or more services to other network functions of core network 204 via an Application Programming Interface (API). Each NF can also register itself and the services it supports (e.g., the services it provides to other network functions) with the NRF of core network 204. Any network function can use the NRF to discover other network functions (or instances of NFs) and the services supported by other NFs (e.g., services provided by other NFs). Any NF can consume (e.g., use) services provided and offered by another NF. An NF that consumes services from another network function is typically referred to as a network function service consumer. A network function that provides and offers one or more of its services is referred to as a network function service producer.

[0089] A core network function (or network entity) (also referred to as a "core network function" or "core network entity") refers to a combination of hardware processing circuitry and memory, which includes software containing machine-readable instructions executable by the hardware processing circuitry, or software containing machine-readable instructions executable by the processing circuitry. The hardware processing circuitry may include any or some combination of a microprocessor, a core of a multi-core microprocessor, a microcontroller, a central processing unit, a graphics processing unit, a tensor processing unit, a programmable integrated circuit, a programmable field gate array, a digital signal processor, or another hardware processing circuitry.

[0090] Figure 2 An example of a device 200 supporting an activation rule set based on operational guidelines, as described herein, is illustrated. Device 200 may be an example of a communication device, such as a UE. As described herein, device 200 may be configured to perform any one or more of the functions described herein. In any case, device 200 may more generally be a computing device or computing entity, such as a server, a standalone computer, a distributed computing system, or a cloud computing system. Regardless of how device 200 is embodied, it may be configured as... Figure 2 As shown, it includes processing circuitry, is associated with or otherwise communicates with the processing circuitry, the processing circuitry including, for example, a processor 102, a memory 104 and / or a communication interface 106.

[0091] In device 200, processor 102 (and / or auxiliary processor 102 or coprocessor or any other circuitry otherwise associated with processor 102) may communicate with memory 104 via a bus for transferring information between components of device 200. Memory 104 may include, for example, one or more volatile and / or non-volatile memories. In other words, for example, memory 104 may be an electronic storage device (e.g., a computer-readable storage medium) including gates configured to store data (e.g., bits) retrievable by a machine (e.g., a computing device like processor 102). Memory 104 may be configured to store information, data, content, applications, instructions, etc., for enabling device 200 to perform various operations of one or more core network functions according to exemplary aspects of this disclosure. For example, memory device 104 may be configured to buffer input data for processing by processor 102. Additionally or alternatively, memory 104 may be configured to store instructions for core network functions for execution by processor 102.

[0092] Processor 102 can be embodied in a variety of different ways. For example, processor 102 can be embodied as one or more of various hardware processing units, such as a coprocessor, microprocessor, controller, digital signal processor (DSP), processing element with or without an accompanying DSP, or various other circuits including integrated circuits, such as ASIC (Application-Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), microcontroller unit (MCU), hardware accelerator, application-specific computer chip, etc. Thus, in some examples, processor 102 may include one or more processing cores configured to execute independently. Multi-core processors can enable multiprocessing within a single physical package. Additionally or alternatively, processor 102 may include one or more other processors configured in series via a bus to enable independent execution of instructions, pipelined processing, and / or multi-threaded processing.

[0093] In an example, processor 102 may be configured to execute instructions stored in memory 104 or otherwise accessible to processor 102. Additionally or alternatively, processor 102 may be configured to perform hard-coded functions. Thus, whether configured by hardware or software methods, or by a combination thereof, processor 102 may represent an entity (e.g., physically embodied in a circuit) capable of performing operations according to aspects of this disclosure when appropriately configured. Thus, for example, when processor 102 is embodied as an ASIC, FPGA, etc., processor 102 may be hardware specifically configured to perform the operations described herein. Alternatively, as another example, when processor 102 is embodied as an executor of instructions, those instructions may, when executed, specifically configure processor 102 to perform the algorithms and / or operations described herein. However, in some cases, processor 102 may be a processor of a particular device (e.g., an encoder and / or decoder) configured to further configure processor 102 to employ aspects of this disclosure through instructions for performing the algorithms and / or operations described herein. The processor 102 may include a clock, an arithmetic logic unit (ALU), and logic gates configured to support the operation of the processor 102.

[0094] In the aspect including communication interface 106, communication interface 106 can be any component, such as a device or circuit system embodied in hardware or a combination of hardware and software, configured to receive data from and / or send data to a network and / or any other device or module communicating with device 200, such other device or module as a network function (NF), UE (e.g., UE 205), RAN (e.g., RAN 210), core network services, application servers and / or functions, databases, or other storage devices. In this respect, communication interface 106 may include, for example, an antenna (or multiple antennas) and hardware and / or software supporting communication with a wireless communication network. Additionally or alternatively, communication interface 106 may include circuitry for interacting with the antenna(s) to induce signal transmission via the antenna(s) or for processing signals received via the antenna(s). In some environments, communication interface 106 may alternatively or also support wired communication. Therefore, for example, communication interface 106 may include a communication modem and / or other hardware and / or software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB), or other mechanisms. In some examples, apparatus 200 may represent a UE (e.g., UE 205) configured to connect to other core network entities or network equipment. In some examples, user equipment may include mobile phones (cellular phones), etc.

[0095] As shown, device 200 may include processor 102 that communicates with memory 104 and is configured to provide signals to and receive signals from communication interface 106. In some examples, communication interface 106 may include a transmitter and a receiver. In some examples, processor 102 may be configured to at least partially control the functionality of device 200. In some examples, processor 102 may be configured to control the functionality of the transmitter and receiver via electrical wires leading to the transmitter and receiver. Similarly, processor 102 may be configured to control other elements of device 200 via electrical wires connecting processor 102 to other elements, such as a display or memory 104. Processor 102 may be embodied in various ways, including circuit systems, at least one processing core, one or more microprocessors with accompanying digital signal processors (DSPs), one or more processors without accompanying DSPs, one or more coprocessors, one or more multi-core processors, one or more controllers, processing circuit systems, one or more computers, various other processing elements including integrated circuits (e.g., application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc.), or some combination thereof. Therefore, although in Figure 2While shown as a single processor, processor 102 may include multiple processors or processing cores.

[0096] Device 200 may operate using one or more air interface standards, communication protocols, modulation types, access types, etc. Signals transmitted and received by processor 102 may include signaling information according to the air interface standard of the applicable cellular system, and / or signaling information from any number of different wired or wireless networking technologies, including but not limited to Wi-Fi, wireless local area network (WLAN) technologies such as IEEE 802.11, 802.16, 802.3, ADSL, DOCSIS, etc. Furthermore, these signals may include voice data, user-generated data, user-requested data, etc.

[0097] For example, device 200 and / or its cellular modem can operate according to various first-generation (1G), second-generation (2G or 2.5G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), advanced 5G (e.g., Advanced 5G), sixth-generation (6G), and Internet Protocol Multimedia Subsystem (IMS) (e.g., Session Initiation Protocol (SIP)) communication protocols. For example, device 200 can operate according to 2G wireless communication protocols such as IS-136, Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), IS-95, and Code Division Multiple Access (CDMA). Additionally, for example, device 200 can operate according to 2.5G wireless communication protocols such as General Packet Radio Service (GPRS) and Enhanced Data GSM Environment (EDGE). Additionally, device 200 may be able to operate according to 3G wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), and Time Division Synchronous Code Division Multiple Access (TD-SCDMA). Furthermore, device 200 may be able to operate according to 3.9G wireless communication protocols, such as Long Term Evolution (LTE) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN). Additionally, device 200 may be able to operate according to 4G wireless communication protocols, such as Advanced LTE, 5G, and similar wireless communication protocols that may be developed subsequently. In some examples, device 200 may be able to operate under or within any suitable control plane and user plane separation (CUPS) architecture, such as for gateway GPRS support node (GGSN-C), trusted wireless access gateway (TWAG-C), broadband network gateway (BNG), N4, Sxa, Sxb, Sxc, evolved packet core (EPC) SWG-C, EPC PGW-C, EPC TDF-C, etc.

[0098] It should be understood that processor 102 may include circuitry for implementing audio and / or video and logic functions of device 200. For example, processor 102 may include digital signal processor devices, microprocessor devices, analog-to-digital converters, digital-to-analog converters, etc. Control and signal processing functions of device 200 can be distributed among these devices according to their respective capabilities. Additionally, processor 102 may include an internal voice encoder (VC), an internal data modem (DM), etc. Furthermore, processor 102 may include functionality for operating one or more software programs, which may be stored in memory 104. Generally, processor 102 and the software instructions stored in memory 104 can be configured to cause device 200 to perform actions. For example, processor 102 may be able to operate a connectivity program, such as a web browser. This connectivity program may allow device 200 to send and receive web page content (such as location-based content) according to protocols such as Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), etc.

[0099] In some examples, device 200 may also include a user interface, such as headphones or speakers, a ringer, a microphone, a display, a user input interface, etc., operatively coupled to processor 102. As described above, the display may include a touch-sensitive display on which a user can touch and / or gesture to make selections, input values, etc. Processor 102 may also include a user interface circuitry configured to control at least some functions of one or more elements of the user interface (such as speakers, ringers, microphones, displays, etc.). Processor 102 and / or the user interface circuitry including processor 102 may be configured to control one or more functions of one or more elements of the user interface via computer program instructions (e.g., software and / or firmware) stored in memory 104 accessible by processor 102 (e.g., volatile memory, non-volatile memory, devices including the same memory, etc.). Device 200 may include a battery for powering various circuits associated with the mobile terminal, such as circuitry for providing mechanical vibration as a detectable output. The user input interface may include a device that allows device 200 to receive data, such as a keypad (e.g., a virtual keyboard displayed on a display or an externally coupled keyboard).

[0100] like Figure 2As shown, device 200 may also include one or more mechanisms for sharing and / or acquiring data, shown as communication interface 106. For example, communication interface 106 of device 200 may include a short-range radio frequency (RF) transceiver and / or interrogator, thus enabling sharing and / or acquiring data with and / or from electronic devices based on RF technology. Device 200 may include other short-range transceivers, such as infrared (IR) transceivers, Bluetooth™ (BT) transceivers operating using Bluetooth™ wireless technology, wireless universal serial bus (USB) transceivers, Bluetooth™ Low Energy transceivers, ZigBee transceivers, ANT transceivers, cellular device-to-device transceivers, wireless LAN link transceivers, and / or any other short-range radio technology. In some examples, device 200, particularly short-range transceivers, may be able to send data to and / or receive data from electronic devices in its vicinity (e.g., within approximately 10 meters). The device 200, including a Wi-Fi or wireless LAN modem, can also be able to send data to and / or receive data from electronic devices according to various wireless networking technologies, including 6LoWpan, Wi-Fi, Wi-Fi Low Energy, WLAN technologies (e.g., IEEE 802.11, IEEE 802.15, IEEE 802.16, etc.).

[0101] Device 200 may include volatile and / or non-volatile memory, which may include some or all of memory 104, or alternatively may be separate memory within or connected to device 200. For example, volatile memory may include random access memory (RAM), including dynamic and / or static RAM, on-chip or off-chip cache memory, etc. Embedded and / or removable non-volatile memory may include, for example, read-only memory, flash memory, magnetic storage devices (e.g., hard disks, floppy disk drives, magnetic tape, optical disk drives, and / or media), non-volatile random access memory (NVRAM), etc. Like volatile memory, non-volatile memory may include cache regions for temporary data storage. At least a portion of the volatile and / or non-volatile memory may be embedded in processor 102. The memory may store one or more software programs, instructions, information fragments, data, etc. For example, memory 104 may store software or instructions for one or more network functions of the core network, which may be used by the device to perform the operations disclosed herein.

[0102] The memory may include identifiers, such as an International Mobile Equipment Identity (IMEI), that can uniquely identify device 200. In this example, processor 102 may be configured using computer code stored in the memory, and / or provide the operations disclosed herein regarding base stations, WLAN access points, network nodes including UEs, etc. Similarly, device 200 may be configured as any other component or network device from the core network.

[0103] Some aspects disclosed herein can be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. For example, the software, application logic, and / or hardware may reside on memory 104, processor 102, or electronic components. In some example aspects, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media. In the context of this document, "computer-readable media" can be a system, apparatus, or device that can contain, store, communicate, propagate, or transport instructions for instruction execution (e.g., computer or data processor circuitry, examples of which are shown in [document name missing]). Figure 2 (as shown in the figure) Any non-transitory medium used or used in conjunction with it, computer-readable medium may include non-transitory computer-readable storage medium, which may be any medium that can contain or store instructions for use by or in conjunction with an instruction execution system, apparatus or device (e.g., a computer).

[0104] In some examples, according to the exemplary aspects of this disclosure, apparatus 200 may be embodied by a user equipment or by a network entity such as a server or other computing device. As described below in conjunction with the flowcharts and block diagrams presented herein, apparatus 200 of the exemplary aspects may be configured to perform the functions and operations described herein. In any case, apparatus 200 may more generally be embodied by a computing device, such as a server, personal computer, computer workstation, or other type of computing device, including those computing devices used as components of a UE and / or wireless network or wireless local area network. Regardless of how apparatus 200 is embodied, apparatus 200 of the exemplary aspects may be configured as follows Figure 2 As shown, this is to include processor 102 and memory 104 (in some examples, and communication interface 106), to be associated with them, or to communicate with them in other ways.

[0105] Although not shown, the device 200 of the example aspect may optionally include a user interface, such as a touchscreen, display, keypad, etc., or combinations thereof. Furthermore, the device 200 according to the example aspect may be configured with a global positioning circuit, which includes a global positioning receiver and / or a global positioning transmitter configured to communicate with one or more global navigation satellite systems (e.g., GPS, GLONASS, Galileo, etc., or combinations thereof). This global positioning circuit may be configured for the transmission and / or reception of direct / indirect satellite and / or cell signals to determine geolocation data (e.g., latitude, longitude, elevation, altitude, geographic coordinates, etc., or combinations thereof) of device 200 and / or another communication device associated with device 200 or one or more global navigation satellite systems.

[0106] In some examples, geolocation data may include a time dimension, such as a timestamp that associates the geolocation data with a corresponding time (e.g., 01:00 AM EST) and a corresponding date (e.g., September 26, 2020). This time dimension may be configured based on one or more of the following: reception time, generation time, transmission time, etc. (e.g., by the device). In some examples, geolocation data may be associated with one or more time dimensions.

[0107] Processor 102 (and / or a coprocessor or other circuitry associated with the processor) may communicate with memory 104 via a bus for transferring information between components of device 200. Memory device 104 may include, for example, one or more volatile and / or non-volatile memories, such as non-transitory storage devices. In other words, for example, memory device 104 may be an electronic storage device (e.g., a computer-readable storage medium) including gates configured to store data (e.g., bits) retrievable by a machine (e.g., a computing device like a processor). Memory device 104 may be configured to store information, data, content, applications, instructions, etc., or combinations thereof, to enable device 200 to perform various functions according to example aspects. For example, memory device 104 may be configured to buffer input data for processing by processor 102. Additionally or alternatively, memory device 104 may be configured to store instructions for execution by processor 102.

[0108] In some examples, device 200 may be embodied in various computing devices as described above. However, in some examples, device 200 may be embodied as a chip or chipset. In other words, device 200 may include one or more physical packages (e.g., chips) that include materials, components, and / or wires on a structural component (e.g., a substrate). The structural component may provide physical strength, dimensional retention, and / or electrical interaction constraints for the component circuitry included thereon. Thus, in some cases, device 200 may be configured to implement an aspect of this disclosure on a single chip, or as a single "system-on-a-chip." Thus, in some cases, a chip or chipset may constitute components for performing one or more operations to provide the functions described herein.

[0109] Processor 102 can be embodied in a variety of different ways. For example, processor 102 can be embodied as one or more of various hardware processing units, such as a coprocessor, microprocessor, controller, digital signal processor (DSP), processing element with or without an accompanying DSP, or various other circuits including integrated circuits, such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), microcontroller units (MCUs), hardware accelerators, application-specific computer chips, etc. Thus, in some examples, processor 102 may include one or more processing cores configured to execute independently. Multi-core processors can enable multiprocessing within a single physical package. Additionally or alternatively, processor 102 may include one or more processors configured in series via a bus to enable independent execution of instructions, pipelined processing, and / or multi-threaded processing.

[0110] In an example, processor 102 may be configured to execute instructions stored in memory 104 or otherwise accessible to the processor. Additionally or alternatively, processor 102 may be configured to perform hard-coded functions. Thus, whether configured by hardware or software methods, or by a combination thereof, processor 102 may represent an entity (e.g., physically embodied in a circuit) capable of performing operations according to aspects of this disclosure when appropriately configured. Therefore, for example, when processor 102 is embodied as an ASIC, FPGA, or a combination thereof, processor 102 may be hardware specifically configured to perform the operations described herein.

[0111] Alternatively, as another example, when processor 102 embodies an executor of instructions, those instructions may, upon execution, specifically configure processor 102 to perform the algorithms and / or operations described herein. However, in some cases, processor 102 may be a processor for a specific device (e.g., an encoder and / or decoder) configured to further configure processor 102 to employ aspects of this disclosure via instructions for performing the algorithms and / or operations described herein. Processor 102 may include a clock, an arithmetic logic unit (ALU), and logic gates configured to support the operation of processor 102.

[0112] In some examples, communication interface 106 can be any component, such as a device or circuitry system embodied in hardware or a combination of hardware and software, configured to receive data from and / or send data to a network and / or any other device or module (such as network functions, network repository functions, base stations, access points, service communication agents, wireless access networks, core network services, databases or other storage devices, or combinations thereof) communicating with device 200. In this regard, the communication interface may include, for example, one or more antennas and hardware and / or software supporting communication with a wireless communication network. Additionally or alternatively, the communication interface may include circuitry for interacting with one or more antennas to induce the transmission of signals via one or more antennas or to process the reception of signals received via one or more antennas.

[0113] In some examples, one or more antennas may include one or more of the following: dipole antennas, monopole antennas, helical antennas, loop antennas, waveguides, horn antennas, parabolic reflectors, corner reflectors, dish antennas, microstrip patch arrays, convex-planar lenses, concave-planar lenses, convex-convex lenses, concave-concave lenses, etc., or combinations thereof. Alternatively or additionally, in some environments, the communication interface may support wired communication. Thus, for example, the communication interface may include a communication modem and / or other hardware / software for supporting communication via cable, digital subscriber line (DSL), USB, etc., or combinations thereof.

[0114] In some examples, session management functions (e.g., SMF) may include 5GC session management functions for any suitable CUPS architecture, such as those for General Packet Radio Service (GPRS), Gateway GPRS Support Node Control Plane Function (GGSN-C), Trusted Radio Access Gateway Control Plane Function (TWAG-C), Broadband Network Gateway Control Plane and User Plane Separation (BNG-CUPS), N4 interface, Sxa interface, Sxb interface, Sxc interface, Evolved Packet Core (EPC) Services Gateway Control Plane Function (SGW-C), EPC Packet Data Network Gateway Control Plane Function (PGW-C), EPC Traffic Detection Control Plane Function (TDF-C), etc., or combinations thereof.

[0115] In some examples, processor 102, communicating with memory 104, may be configured to provide signals to and receive signals from communication interface 106. In some examples, communication interface 106 may include a transmitter and a receiver. In some examples, processor 102 may be configured to at least partially control the functionality of device 200. In some examples, processor 102 may be configured to control the functionality of transmitter and receiver via control signaling through electrical wires leading to transmitter and receiver. Similarly, processor 102 may be configured to control other elements of device 200 via control signaling through electrical wires connecting processor 102 to other elements, such as display or memory 104.

[0116] Device 200 may operate using one or more air interface standards, communication protocols, modulation types, access types, etc. Signals transmitted and received by processor 102 may include signaling information according to the air interface standard of the applicable cellular system, and / or signaling information from any number of different wired or wireless networking technologies, including but not limited to Wi-Fi, wireless local area network (WLAN) technologies such as IEEE 802.11, 802.16, 802.3, Asymmetric Digital Subscriber Line (ADSL), Cable Data Service Interface Specification (DOCSIS), etc., or combinations thereof. Furthermore, these signals may include voice data, user-generated data, user-requested data, etc., or combinations thereof.

[0117] Some of the example aspects disclosed herein can be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. For example, the software, application logic, and / or hardware may reside on memory 104, processor 102, or electronic components. In some examples, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media. In the context of this document, "computer-readable media" can be any non-transitory medium that can contain, store, communicate, propagate, or transport instructions for instruction execution systems, apparatuses, or devices (such as computer or data processor circuitry, examples of which are shown in [document name missing]). Figure 2 (as shown in the figure) for use or in combination with. The computer-readable medium may include a non-transitory computer-readable storage medium, which may be any medium that may contain or store instructions for use by or in combination with an instruction execution system, apparatus, or device, such as a computer.

[0118] In some examples, device 200 may also include transceiver circuitry 108. Transceiver circuitry 108 may be configured at least to function as a receiver and / or a transmitter. In some examples, but not necessarily in all examples, transceiver circuitry 108 is configured at least to function as a transceiver, i.e., to function as a receiver and to function as a transmitter.

[0119] In some examples, the transceiver circuitry 108 may be or include a printed circuit board, one or more directional antennas, an antenna array, etc. In some examples, the antennas / antenna arrays may have or create a radiation pattern covering corresponding plurality of partially overlapping sectors extending outward from the transceiver circuitry 108.

[0120] In some of the illustrated examples, device 200 is described as different from and distinct from a transmission point, relay station, eNb, gNb, access point, access network, etc. However, in some examples, device 200 may operate as any or all of a transmission point, relay station, eNb, gNb, access point, access network, etc., and / or one or more of a transmission point, relay station, eNb, gNb, access point, access network, etc. may operate as device 200.

[0121] As used herein, a “module” refers to a unit or device that excludes certain parts / components that will be added by the terminal manufacturer or user. Processor 102 may be a module. Transceiver circuitry 108 may be a module. Multiple directional antennas / antenna arrays may be modules.

[0122] Processor 102 may be a controller. Processor 102 may be implemented in hardware only, may have software aspects including only firmware, or may be a combination of hardware and software (including firmware).

[0123] Processor 102 can be implemented using instructions that enable hardware functions, for example by using executable instructions of a computer program in a general-purpose or special-purpose processor, which can be stored on a computer-readable storage medium (disk, memory, etc.) for execution by such processor.

[0124] Processor 102 can be configured to read from and write to memory 104. Processor 102 may also include an output interface through which the processor outputs data and / or commands, and an input interface through which data and / or commands are input to processor 102.

[0125] Memory 104 may store instructions (e.g., as program code, computer program code) that control the operation of device 200 when loaded into the processor. The instructions (e.g., instructions of a computer program) stored in memory 104 provide logic and routines that enable device 200 to perform the illustrated and described methods. By reading memory 104, processor 102 is able to load and execute these instructions.

[0126] Therefore, device 200 may include: at least one processor; and at least one memory including program code (e.g., computer program code, computer program instructions, computer-readable instructions, program instructions, etc.), wherein the at least one memory and program code / computer program code are configured together with the at least one processor to cause device 200 to perform at least any of the methods, processes, signaling processes, communication methods, receiver filter boot steps or other method sub-steps described herein.

[0127] Instructions (e.g., a computer program) can reach device 200 via any suitable delivery mechanism. This delivery mechanism can be, for example, a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a recording medium (such as an optical disc read-only memory (CD-ROM) or digital versatile optical disc (DVD) or solid-state storage), or an article of manufacture that includes or tangibly embodies the computer program. The delivery mechanism can be a signal configured to reliably transmit the computer program. Device 200 can propagate or transmit the computer program as a computer data signal.

[0128] The instructions described herein may include computer program instructions for causing an apparatus (e.g., 200) to perform some or all of the steps in any method, process, signaling flow, communication method, receiver filter boot step, or other method sub-step described herein.

[0129] Computer program instructions can be included in a computer program, a non-transitory computer-readable medium, a computer program product, or a machine-readable medium. In some, but not necessarily all, examples, computer program instructions may be distributed across more than one computer program.

[0130] The memory 104 can be implemented as one or more separate components / circuit systems, some or all of which may be integrated / removable and / or provide permanent / semi-permanent / dynamic / cache storage.

[0131] Processor 102 can be implemented as one or more separate components / circuit systems, some or all of which may be integrated / removable. Processor 102 may be a single-core or multi-core processor.

[0132] Figure 3 An example of apparatus 300 supporting an activation rule set based on operational guidelines, as described herein, is illustrated. Apparatus 300 may be an example of one or more aspects of a communication network (e.g., RAN, AMF, SMF, PCF, etc.). Alternatively or additionally, apparatus 300 may be an example of a core network and / or one or more aspects of a core network. Apparatus 300 may include one or more processors 102 and / or one or more memories 104, which may be as described in reference... Figure 2 Examples of the corresponding components described herein. Additionally or alternatively, device 300 may include a network interface 305 that enables device 300 to communicate with one or more other network functions, components, and / or entities. Device 300 may be configured to perform any one or more of the functions described herein. In some examples, device 300 may include software stored at one or more memories 104 that, when executed, can implement one or more network functions of the core network (e.g., see reference 104). Figure 1 (Any one or more network functions described). In any case, device 300 may more generally be a computing device or computing entity, such as a server, a standalone computer, a distributed computing system, or a cloud computing system. Regardless of how device 300 is embodied, the device can be configured as follows: Figure 3 As shown, it includes, is associated with or otherwise communicates with a processing circuitry system, such as a processor 102, a memory 104 and / or a network interface 305.

[0133] Figure 4An example of signaling diagram 400 supporting an activation rule set based on operational guidelines, as described herein, is illustrated. In some examples, various communication devices can be configured to communicate via one or more communication paths. For example, UE 205 can be configured to operate according to a path selection policy (e.g., URSP). In some examples, the path selection policy can specify or otherwise include multiple rules (e.g., rule set 445) for communication between communication devices. In some examples, path selection rule set 445 can specify that a particular type of communication (e.g., a particular type of service) will be relayed via a particular path. Path types that can be specified by path selection rule set 445 include various Session and Service Continuity (SSC) modes, network slices, data networks, PDU session types, and / or access types. For example, UE 205 can be configured to use a particular network slice to deliver a particular type of data (e.g., data associated with a particular application). However, conventional techniques only involve providing a single path selection rule that will be applied in any communication scenario, which can lead to many challenges, such as reduced communication and / or operational efficiency and excessive power consumption, as well as other challenges that may stem from device-independent communication path selection.

[0134] According to one or more examples described herein, a communication device (such as UE 205) may be provided with multiple rule sets 445 (e.g., multiple rule sets, multiple URSP rule sets). In some examples, UE 205 may receive multiple rule sets 445 from network 225 (e.g., from PCF 220 via AMF 215 and RAN 210). In some examples, UE 205 may be provided with multiple rule sets 445 in response to sending a capability indication 430. The capability indication may indicate that UE 205 is configured or otherwise able to select one or more rule sets 445 (e.g., based on one or more operating criteria associated with UE 205). In some examples, UE 205 may send the capability indication 430 to RAN 210, which may then transmit the capability indication 430 to AMF 215 and / or PCF 220.

[0135] Each of the multiple rule sets 445 can correspond to one or more operating criteria of the communication device, enabling the communication device to select one or more rule sets 445 based on one or more operating criteria. For example, rule set 445-a can correspond to the power-saving mode of the communication device, and rule set 445-b can correspond to a high-performance mode (e.g., for increasing communication throughput). Therefore, the communication device can select or otherwise utilize rule set 445-a when the communication device is in power-saving mode, and select or otherwise utilize rule set 445-b when the communication device is in high-performance mode. This technique enables the communication device to adjust the utilization of various communication paths to better match the various conditions, capabilities, and / or operating states of the communication device, which can improve performance, increase communication efficiency, and reduce power consumption.

[0136] In some examples, UE 205 may select rule set 445 from multiple rule sets 445 based on one or more operating criteria associated with UE 205. This rule set 445 may be used to at least partially define the URSP. For example, the URSP may include one or more rule sets 445. In such an example, one or more RSDs 460 of one or more rule sets 445 may provide one or more indications for one or more communication paths for one or more communication devices. The one or more communication devices can then operate in accordance with or otherwise according to the URSP by utilizing one or more communication paths.

[0137] In some examples, each rule in rule set 445 may correspond to a corresponding rule set identifier 450 among a plurality of rule set identifiers 450. As described herein, a rule may include one or more TDs 455 and one or more RSDs 460 corresponding to a TD 455. In some examples, a single TD 455 may be mapped to one or more RSDs 460. Alternatively or additionally, a single RSD 460 may be mapped to one or more TDs 455. In some examples, if the communication service is of the same type as indicated by the corresponding TD 455, the rule may be applied by communicating using the communication path indicated by the RSD 460. In some examples, rule set 445 may include a plurality of TDs 455 and a plurality of RSDs 460 corresponding to the plurality of TDs 455. In some examples, RSD 460 and / or TD 455 may at least include an indication of rule set ID 450, which may additionally or alternatively be included in the RSD verification criteria information and / or TD verification criteria information, respectively.

[0138] In some examples, UE 205 may send one or more messages 435 (e.g., user plane services) via a path indicated by one or more RSDs 460 of a selected rule set 445. In some examples, one or more messages 435 may include one or more data packets. In some examples, one or more messages 435 may include one or more indications of the rule set 445 selected by UE 205.

[0139] In some examples, one or more operating criteria associated with UE 205 include one or more of the following: UE 205 operates in power-saving mode, UE 205 operates in on-duty mode associated with the user's occupation, or UE 205 operates in personal use mode. As described herein, one or more operating criteria may correspond to one or more rule sets 445. For example, when UE 205 operates in power-saving mode, UE 205 may activate, select, or otherwise utilize rule set 445 corresponding to power-saving mode. In such an example, when UE 205 operates in high-performance mode, UE 205 may activate, select, or otherwise utilize rule set 445 corresponding to high-performance mode.

[0140] In some examples, UE 205 may receive UE 205 configuration (e.g., one or more UE configuration messages 440) for UE 205 from the core network of the communication network (e.g., network 225, one or more network entities of network 225). This UE 205 configuration may include multiple rule sets 445 and multiple rule set identifiers 450. In some examples, UE 205 may send an indication of the selected rule set 445 to the core network (e.g., to any one or more components and / or functions of network 225) (e.g., in one or more messages 435). In some examples, UE 205 may receive an indication of the operating mode of UE 205 selected by a user. For example, the user of UE 205 may select a low-power mode, which may correspond to one or more rule sets 445. In some examples, this selection may include selecting rule sets 445 based on the operating mode of UE 205. For example, selecting an operating mode may additionally select one or more rule sets 445 corresponding to that operating mode.

[0141] In some examples, UE 205 may determine that one or more operating criteria associated with UE 205 are met. In response to the satisfaction of one or more operating criteria, UE 205 may select rule set 445. For example, in response to determining that UE 205 is in a low-power mode, UE 205 may select rule set 445. Rule set 445 may include one or more RSDs 460 that enable UE 205 to save power compared to one or more other RSDs 460. Therefore, by selecting rule set 445 in response to the satisfaction of one or more operating criteria, path selection and utilization at UE 205 can more effectively take into account UE state and / or UE conditions.

[0142] Figure 5 An example of a process flow 500 supporting the activation of a rule set based on operational criteria, as described herein, is illustrated. One or more operations of process flow 500 may be performed by UE 205, RAN 210, AMF 215, and / or PCF 220. Process flow 500 may provide an illustrative example of the order or sequence of operations described herein; however, any order or sequence may be used. In some cases, one or more operations of process flow 500 may not be performed or may be otherwise omitted. Additionally or alternatively, UE 205, RAN 210, AMF 215, and / or PCF 220 may perform operations not shown in process flow 500. It should also be understood that any operation described herein may be performed independently of other operations described herein. For example, UE 205 may send an uplink (UL) NAS transmission message and may not receive a downlink (DL) NAS transmission message. As described herein, process flow 500 may provide an example of UE policy association establishment and rule set configuration.

[0143] In the first instance (e.g., Operation 1), UE 205 may send a policy container to AMF 215, which includes indications of rule set selection and / or rule set activation support. In some examples, the UE policy container may be included in a message or along with another message, such as a registration request message. In some examples, the registration request may be sent in a UL NAS transport message, which may also include the UE policy container.

[0144] In the second instance (e.g., operation 2), AMF 215 may accept registration and / or send a message to UE 205 indicating that the registration request has been accepted. For example, AMF 215 may send an acknowledgment (ACK) message to UE 205.

[0145] In the third instance (e.g., operation 3), AMF 215 may determine whether to create or otherwise determine the generation of UE policy associations.

[0146] At the fourth instance (e.g., operation 4), AMF 215 and / or PCF 220 may create or otherwise generate UE policy associations. In some examples, AMF 215 may send a UE policy container to PCF 220, which includes rule set selection and / or activation support indications.

[0147] In the fifth instance (e.g., operation 5), PCF 220 can respond to a UE policy association creation request. For example, PCF 220 can send messages and / or commands to AMF 215.

[0148] At the sixth instance (e.g., Operation 6), PCF 220 may provide UE 205 with one or more URSP rule sets having associated IDs using the procedures specified in Clause 4.2.4.3 of TS 23.502 (e.g., the UE configuration update procedure for transparent UE policy delivery). In some examples, one or more URSP rule sets may be provided to UE 205, RAN 210, and / or AMF 215. In some examples, PCF 220 may provide a mapping of rule set IDs to user-selectable settings in human-readable character form. The mapping of rule set IDs may be provided to UE 205, RAN 210, and / or AMF 215.

[0149] Figure 6 An example of a process flow 600 supporting operation criteria-based activation of a rule set, as described herein, is shown. One or more operations of process flow 600 may be performed by UE 205, RAN 210, AMF 215, and / or PCF 220. Process flow 600 may provide an illustrative example of the order or sequence of operations described herein; however, any order or sequence may be used. In some cases, one or more operations of process flow 600 may not be performed or may be otherwise omitted. Additionally or alternatively, UE 205, RAN 210, AMF 215, and / or PCF 220 may perform operations not shown in process flow 600. It should also be understood that any operation described herein may be performed independently of other operations described herein. As described herein, process flow 600 may be an example of UE policy association establishment and rule set configuration. Additionally or alternatively, process flow 600 may provide an example of NSSAI configuration for each rule set ID.

[0150] In the first instance (e.g., Operation 1), UE 205 may send a registration request message to AMF 215 (e.g., the registration request may be sent in a UL NAS transport message, which may also include a UE policy container). In some examples, the registration request message may include (or be sent with) a UE policy container that includes an indication that the UE supports rule set selection (e.g., rule set activation). In some examples, the indication that the UE supports rule set selection may be included in or otherwise associated with UE mobility management (MM) capability information. In some examples, AMF 215 may store the indication that the UE supports rule set selection and provide it to UDM (not shown) to obtain subscription information for each rule set ID.

[0151] In the second instance (e.g., operation 2), AMF 215 can accept registration and / or send a message to UE 205 indicating that the registration request has been accepted. For example, AMF 215 can send an acknowledgment (ACK) message to UE 205. In some examples, AMF 215 can send multiple configured NSSAIs to UE 205.

[0152] In the third instance (e.g., operation 3), AMF 215 may determine whether to create or otherwise determine the generation of UE policy associations.

[0153] At the fourth instance (e.g., operation 4), AMF 215 and / or PCF 220 may create or otherwise generate UE policy associations. In some examples, AMF 215 may send a UE policy container to PCF 220, which includes rule set selection and / or activation support indications.

[0154] In the fifth instance (e.g., operation 5), PCF 220 can respond to a UE policy association creation request. For example, PCF 220 can send messages and / or commands to AMF 215.

[0155] At the sixth instance (e.g., Operation 6), PCF 220 may provide UE 205 with one or more URSP rule sets having associated IDs using the procedures specified in Clause 4.2.4.3 of TS 23.502 (e.g., the UE configuration update procedure for transparent UE policy delivery). In some examples, one or more URSP rule sets may be provided to UE 205, RAN 210, and / or AMF 215. In some examples, PCF 220 may provide a mapping of rule set IDs to user-selectable settings in human-readable character form. The mapping of rule set IDs may be provided to UE 205, RAN 210, and / or AMF 215.

[0156] Figure 7 An example of a process flow 700 supporting operation criteria-based activation of rule sets is shown, according to the examples described herein. One or more operations of process flow 700 may be performed by UE 205, RAN 210, AMF 215, and / or PCF 220. Process flow 700 may provide an illustrative example of the order or sequence of operations described herein; however, any order or sequence may be used. In some cases, one or more operations of process flow 700 may not be performed or may be otherwise omitted. Additionally or alternatively, UE 205, RAN 210, AMF 215, and / or PCF 220 may perform operations not shown in process flow 700. It should also be understood that any operation described herein may be performed independently of other operations described herein. As described herein, process flow 700 may provide an example of NSSAI for UE policy association establishment and configuration of each rule set ID.

[0157] In the first instance (e.g., Operation 1), UE 205 may send a registration request message to AMF 215 (e.g., the registration request may be sent in a UL NAS transport message, which may also include a UE policy container). In some examples, the registration request message may include (or be sent with) a UE policy container that includes an indication that the UE supports rule set selection. In some examples, the indication that the UE supports rule set selection may be included in or otherwise associated with UE mobility management (MM) capability information. In some examples, AMF 215 may store the indication that the UE supports rule set selection and provide it to UDM (not shown) to obtain subscription information for each rule set ID.

[0158] In the second instance (e.g., operation 2), AMF 215 may accept registration and / or send a message to UE 205 indicating that the registration request has been accepted. For example, AMF 215 may send an acknowledgment (ACK) message to UE 205. Alternatively or additionally, AMF 215 may send a configured S-NSSAI to UE 205, which includes indications for each S-NSSAI specifying which rule set ID a particular S-NSSAI applies to.

[0159] In the third instance (e.g., operation 3), AMF 215 may determine whether to create or otherwise determine the generation of UE policy associations.

[0160] At the fourth instance (e.g., operation 4), AMF 215 and / or PCF 220 may create or otherwise generate UE policy associations. In some examples, AMF 215 may send a UE policy container to PCF 220, which includes rule set selection and / or activation support indications.

[0161] In the fifth instance (e.g., operation 5), PCF 220 can respond to a UE policy association creation request. For example, PCF 220 can send messages and / or commands to AMF 215.

[0162] At the sixth instance (e.g., Operation 6), PCF 220 may provide UE 205 with one or more URSP rule sets having associated IDs using the procedures specified in Clause 4.2.4.3 of TS 23.502 (e.g., the UE configuration update procedure for transparent UE policy delivery). In some examples, one or more URSP rule sets may be provided to UE 205, RAN 210, and / or AMF 215. In some examples, PCF 220 may provide a mapping of rule set IDs to user-selectable settings in human-readable character form. The mapping of rule set IDs may be provided to UE 205, RAN 210, and / or AMF 215.

[0163] Figure 8An example of a process flow 800 supporting operation criteria-based activation of rule sets is shown, according to the examples described herein. One or more operations of process flow 800 may be performed by UE 205, RAN 210, AMF 215, and / or PCF 220. Process flow 800 may provide an illustrative example of the order or sequence of operations described herein; however, any order or sequence may be used. In some cases, one or more operations of process flow 800 may not be performed or may be otherwise omitted. Additionally or alternatively, UE 205, RAN 210, AMF 215, and / or PCF 220 may perform operations not shown in process flow 800. It should also be understood that any operation described herein may be performed independently of other operations described herein. As described herein, process flow 800 may provide examples of UE policy association establishment and rule set configuration. Additionally or alternatively, process flow 800 may provide examples of NSSAI configuration for each rule set ID.

[0164] In the first instance (e.g., Operation 1), UE 205 may send a registration request message to AMF 215 (e.g., the registration request may be sent in a UL NAS transport message, which may also include a UE policy container). In some examples, the registration request message may include (or be sent with) a UE policy container that includes an indication that the UE supports rule set selection. In some examples, the indication that the UE supports rule set selection may be included in or otherwise associated with UE mobility management (MM) capability information. In some examples, AMF 215 may store the indication that the UE supports rule set selection and provide it to UDM (not shown) to obtain subscription information for each rule set ID.

[0165] In the second instance (e.g., operation 2), AMF 215 may accept registration and / or send a message to UE 205 indicating that the registration request has been accepted. For example, AMF 215 may send an acknowledgment (ACK) message to UE 205. Alternatively or additionally, AMF 215 may send to UE 205 one or more configured NSSAIs with one or more Network Slice Simultaneous Registration Groups (NSSRGs) and a mapping of rule set IDs to one or more NSSRGs (e.g., if received from the UDM for UE 205 and / or if UE 205 indicates support for rule set selection).

[0166] In the third instance (e.g., operation 3), AMF 215 may determine whether to create or otherwise determine the generation of UE policy associations.

[0167] At the fourth instance (e.g., operation 4), AMF 215 and / or PCF 220 may create or otherwise generate UE policy associations. In some examples, AMF 215 may send a UE policy container to PCF 220, which includes rule set selection and / or activation support indications.

[0168] In the fifth instance (e.g., operation 5), PCF 220 can respond to a UE policy association creation request. For example, PCF 220 can send messages and / or commands to AMF 215.

[0169] At the sixth instance (e.g., Operation 6), PCF 220 may provide UE 205 with one or more URSP rule sets having associated IDs using the procedures specified in Clause 4.2.4.3 of TS 23.502 (e.g., the UE configuration update procedure for transparent UE policy delivery). In some examples, one or more URSP rule sets may be provided to UE 205, RAN 210, and / or AMF 215. In some examples, PCF 220 may provide a mapping of rule set IDs to user-selectable settings in human-readable character form. The mapping of rule set IDs may be provided to UE 205, RAN 210, and / or AMF 215.

[0170] Figure 9 An example of a process flow 900 supporting operation criteria-based activation of rule sets is shown, according to the examples described herein. One or more operations of process flow 900 may be performed by UE 205, RAN 210, AMF 215, and / or PCF 220. Process flow 900 may provide an illustrative example of the order or sequence of operations described herein; however, any order or sequence may be used. In some cases, one or more operations of process flow 900 may not be performed or may be otherwise omitted. Additionally or alternatively, UE 205, RAN 210, AMF 215, and / or PCF 220 may perform operations not shown in process flow 900. It should also be understood that any operation described herein may be performed independently of other operations described herein. As described herein, process flow 900 may be an example of NSSAI for UE policy association establishment and configuration of each rule set ID.

[0171] In the first instance (e.g., Operation 1), UE 205 may send a registration request message to AMF 215 (e.g., the registration request may be sent in a UL NAS transport message, which may also include a UE policy container). In some examples, the registration request message may include (or be sent with) a UE policy container that includes an indication that the UE supports rule set selection. In some examples, the indication that the UE supports rule set selection may be included in or otherwise associated with UE mobility management (MM) capability information. In some examples, AMF 215 may store the indication that the UE supports rule set selection and provide it to UDM (not shown) to obtain subscription information for each rule set ID.

[0172] In the second instance (e.g., operation 2), AMF 215 may accept registration and / or send a message to UE 205 indicating that the registration request has been accepted. For example, AMF 215 may send an acknowledgment (ACK) message to UE 205. In some examples, AMF 215 may send multiple configured NSSAIs to UE 205. Alternatively or additionally, AMF 215 may send to UE 205 one or more configured NSSAIs with one or more NSSRGs, along with a mapping of rule set IDs to one or more NSSRGs (e.g., if received from a UDM for UE 205 and / or if UE 205 indicates support for rule set selection).

[0173] In the third instance (e.g., operation 3), AMF 215 may determine whether to create or otherwise determine the generation of UE policy associations.

[0174] At the fourth instance (e.g., operation 4), AMF 215 and / or PCF 220 may create or otherwise generate UE policy associations. In some examples, AMF 215 may send a UE policy container to PCF 220, which includes rule set selection and / or activation support indications.

[0175] In the fifth instance (e.g., operation 5), PCF 220 can respond to a UE policy association creation request. For example, PCF 220 can send messages and / or commands to AMF 215.

[0176] At the sixth instance (e.g., Operation 6), PCF 220 may provide UE 205 with one or more URSP rule sets having associated IDs using the procedures specified in Clause 4.2.4.3 of TS 23.502 (e.g., the UE configuration update procedure for transparent UE policy delivery). In some examples, one or more URSP rule sets may be provided to UE 205, RAN 210, and / or AMF 215. In some examples, PCF 220 may provide a mapping of rule set IDs to user-selectable settings in human-readable character form. The mapping of rule set IDs may be provided to UE 205, RAN 210, and / or AMF 215.

[0177] Figure 10 An example flowchart 1000 supporting an activation rule set based on operational criteria, as described herein, is illustrated. Flowchart 1000 may illustrate examples of one or more operations performed by one or more devices (e.g., device 200 and / or device 300), which may be embodied by a UE, RAN, AMF, PCF, SMF, or other computing device or controller, as referenced herein. Figures 1 to 9 As described.

[0178] As shown in block 1005, the apparatus may include components for transmitting one or more indications to the network, such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc. For example, the apparatus may send an indication to the network that the apparatus supports rule set selection features. This indication may be sent in the UE policy container and / or in the UE MM core network capability.

[0179] As shown in block 1010, the apparatus may include components for receiving URSP information, such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc., such URSP information as one or more rule sets (e.g., URSP rule sets) and / or URSP mapping information. For example, the apparatus may receive more than one rule set and / or more than one configured NSSAI, each applicable to at least one rule set ID in the rule set IDs. In some examples, the rule set may be received in a DL NAS transport message. The rule set ID may be mapped to or otherwise correspond to one or more human-readable tags that can be selected by the user. In some examples, the URSP information may be received in a registration acceptance or UE configuration command message. In some examples, the apparatus may store the received information.

[0180] It should be noted that the rule set ID corresponding to the selectable UE settings is assumed to be based either on a known ID that depends on the device (the PCF sets this ID based on its awareness of the UE mode in the PEI), or on a value to be normalized, or on a mapping from the human-readable label of the UE settings to the rule set ID provided to the UE by the PCF.

[0181] Figure 11 An example of a flowchart 1100 supporting an activation rule set based on operational criteria, as described herein, is illustrated. Flowchart 1100 may illustrate examples of one or more operations performed by one or more devices (e.g., device 200 and / or device 300), which may be embodied by a UE, RAN, AMF, PCF, SMF, or other computing device or controller, as referenced herein. Figures 1 to 10 As described.

[0182] As shown in block 1105, the apparatus may include components for transmitting an indication to the network, such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc., such as an indication that the apparatus supports rule set selection features. In some examples, the indication may be sent in the UE MM core network capability information.

[0183] As shown in block 1110, the apparatus may include components for storing indication information (e.g., indication of UE capability information), such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc. For example, the AMF may store information from the UE. Alternatively or additionally, the apparatus may send multiple configured NSSAIs (e.g., one for each rule set ID) or one configured NSSAI, wherein each S-NSSAI applies to one or more rule set IDs. For example, the AMF may send multiple configured NSSAIs or one configured NSSAI to the UE. In some examples, multiple configured NSSAIs or one configured NSSAI may be sent in a registration acceptance message or a UE configuration update message.

[0184] Figure 12 An example flowchart 1200 supporting an activation rule set based on operational criteria, as described herein, is illustrated. Flowchart 1200 may illustrate examples of one or more operations performed by one or more devices (e.g., device 200 and / or device 300), which may be embodied by a UE, RAN, AMF, PCF, SMF, or other computing device or controller, as referenced herein. Figures 1 to 11 As described.

[0185] As shown in block 1205, the apparatus may include components for transmitting an indication to the network, such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc., such as an indication that the apparatus supports rule set selection features. In some examples, the indication may be sent in the UE MM core network capability information.

[0186] As shown in block 1210, the apparatus may include components for storing indication information (e.g., indication of UE capability information), such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc. For example, the AMF may store information from the UE. Alternatively or additionally, the apparatus may receive from the AMF a configured NSSAI with NSSRGs and a mapping of NSSRGs to rule set IDs. In some examples, the configured NSSAI and / or the mapping of NSSRGs to rule set IDs may be received during registration acceptance or UE configuration update.

[0187] Figure 13 An example flowchart 1300 supporting an activation rule set based on operational criteria, as described herein, is shown. Flowchart 1300 may illustrate examples of one or more operations performed by one or more devices (e.g., device 200 and / or device 300), which may be embodied by a UE, RAN, AMF, PCF, SMF, or other computing device or controller, as referenced... Figures 1 to 12 As described.

[0188] As shown in block 1305, the device may include components for user-selectable settings and / or device-selectable settings (e.g., autonomously), such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc. For example, the user may select energy-saving settings to conserve device power. In some examples, user-selected settings may be mapped to or otherwise correspond to a rule set ID.

[0189] As shown in block 1310, the apparatus may include components for determining whether the apparatus has received more than one configured NSSAI, such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc. If the apparatus has received more than one configured NSSAI, the process may continue to block 1215. If the apparatus has not yet received more than one configured NSSAI, the process may terminate and / or one or more other operations (not shown) may be performed.

[0190] As shown in block 1315, the device may include NSSAI components for selecting a configuration mapped to a selected rule set ID (e.g., a rule set ID corresponding to a setting selected by the user), such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc.

[0191] As shown in block 1320, the apparatus may include components for applying rule sets, such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc. In some examples, one or more PDU sessions that cannot be maintained (e.g., PDU sessions associated with other communications and / or rule sets) may be released (e.g., terminated) by the UE. Alternatively or additionally, one or more new PDU sessions may be established.

[0192] Figure 14 An example flowchart 1400 supporting an activation rule set based on operational criteria, as described herein, is illustrated. Flowchart 1400 may illustrate examples of one or more operations performed by one or more devices (e.g., device 200 and / or device 300), which may be embodied by a UE, RAN, AMF, PCF, SMF, or other computing device or controller, as referenced herein. Figures 1 to 13 As described.

[0193] As shown in block 1405, the device may include components for user-selectable settings and / or device-selectable settings (e.g., autonomously), such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc. For example, the user may select energy-saving settings to conserve device power. In some examples, user-selected settings may be mapped to or otherwise correspond to a rule set ID.

[0194] As shown in block 1410, the apparatus may include components such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc., for determining whether the apparatus has received an NSSAI with an applicable rule set ID for each S-NSSAI. For example, the UE may determine whether it has received an NSSAI with an applicable rule set ID from the AMF. If the apparatus has an NSSAI with an applicable rule set ID, the process may continue to block 1315. If the apparatus has not yet received an NSSAI with an applicable rule set ID, the process may terminate and / or one or more other operations (not shown) may be performed.

[0195] As shown in block 1415, the apparatus may include components such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc., for considering or otherwise evaluating an S-NSSAI in a configured NSSAI that has a rule set ID value mapped to or otherwise corresponding to a selected rule set ID.

[0196] As shown in block 1420, the apparatus may include components for applying rule sets, such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc. In some examples, one or more PDU sessions that cannot be maintained (e.g., PDU sessions associated with other communications and / or rule sets) may be released (e.g., terminated) by the UE. Alternatively or additionally, one or more new PDU sessions may be established.

[0197] Figure 15 An example flowchart 1500 supporting an activation rule set based on operational criteria, as described herein, is shown. Flowchart 1500 may illustrate examples of one or more operations performed by one or more devices (e.g., device 200 and / or device 300), which may be embodied by a UE, RAN, AMF, PCF, SMF, or other computing device or controller, as referenced herein. Figures 1 to 14 As described.

[0198] As shown in block 1505, the device may include components for user-selectable settings and / or device-selectable settings (e.g., autonomously), such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc. For example, the user may select energy-saving settings to conserve device power. In some examples, user-selected settings may be mapped to or otherwise correspond to a rule set ID.

[0199] As shown in block 1510, the apparatus may include components such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc., for determining whether the UE has received an NSSAI with an NSSRG configuration and a mapping of rule set IDs to NSSRGs. If the apparatus has received an NSSAI with an NSSRG configuration and a mapping of rule set IDs to NSSRGs, the process may continue to block 1415. If the apparatus has not yet received an NSSAI with an NSSRG configuration and a mapping of rule set IDs to NSSRGs, the process may terminate and / or one or more other operations (not shown) may be performed.

[0200] As shown in block 1515, the apparatus may include components such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc., for considering or otherwise evaluating an S-NSSAI with NSSAI values ​​mapped to a selected rule set ID.

[0201] As shown in block 1520, the apparatus may include components for applying rule sets, such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, network interface 305, etc. In some examples, one or more PDU sessions that cannot be maintained (e.g., PDU sessions associated with other communications and / or rule sets) may be released (e.g., terminated) by the UE. Alternatively or additionally, one or more new PDU sessions may be established.

[0202] Figure 16 An example of a process flow 1600 supporting an activation rule set based on operational criteria, as described herein, is illustrated. One or more operations of process flow 1600 may be performed by UE 205, RAN 210, AMF 215, SMF 1405, and / or PCF 220. Process flow 1600 may provide an illustrative example of the order or sequence of operations described herein; however, any order or sequence may be used. In some cases, one or more operations of process flow 1600 may not be performed or may be otherwise omitted. Additionally or alternatively, UE 205, RAN 210, AMF 215, SMF 1505, and / or PCF 220 may perform operations not shown in process flow 1600. It should also be understood that any operation described herein may be performed independently of other operations described herein.

[0203] The following operation illustrates an example of UE 205 sending a selected rule set ID to the network during the SM / RM process. The network can then constrain behavior based on this rule set ID or perform checks related to subscription information for each rule set ID. Rule set IDs can also be associated with known semantics in the system (e.g., on-duty / off-duty, energy saving, maximum performance, etc.). A rule set ID can actually correspond to a subscription value like "energy saving priority" or "on-duty," and this can then help the network check subscriptions against relevant S-NSSAI and / or DNN. The network can also pass this rule set ID to the RAN to apply related behaviors.

[0204] At the first instance (e.g., Operation 1), UE 205 (e.g., a supported UE) has selected a preferred energy setting, and this, based on its associated rule set, enables the establishment of a PDU session. The preferred energy setting is indicated in the URSP rules to be applied at the session level; therefore, the PDU session establishment process includes UE assistance provided by UE 205 to SMF 1505 via NAS signaling for the preferred energy setting. Alternatively, if available, SMF 1505 can receive default preferred energy setting information for UE 205 from subscription data stored at UDM. This can be used to authorize values ​​from UE 205, or if no instruction is received from UE 205 (e.g., for a non-supported UE), the information can be used. Alternatively, the same information can be accessed by PCF 220 at UDR. Based on the information received from PCF 220, SMF 1505 should update the authorized alternative QoS profiles (access-specific QoS parameters) and may also provide UE 205 assistance to RAN 210 (e.g., gNB).

[0205] In the second instance (e.g., operation 2), the UE preferably changes its energy settings. UE 205 re-evaluates the URSP rules based on the received local configuration.

[0206] In the third instance (e.g., Operation 3), similar to Operation 1, after the URSP rules are re-evaluated, UE 205 triggers a PDU session modification using the updated preferred energy setting UE assistance determined in step 2. Based on the received updated UE assistance, the core network can update the PDU session configuration and provide the NG-RAN with a new UE assistance for the preferred energy setting information. If this applies, the PDU session can also be released, or a new PCU session can be established using the appropriate S-NSSAI(s). S-NSSAIs that have not yet been permitted can be requested (see also Clause 6.x.3.3).

[0207] Figure 17 An example of a process flow 1700 supporting an activation rule set based on operational criteria, as described herein, is illustrated. One or more operations of process flow 1700 may be performed by UE 205, RAN 210, and / or AMF 215. Process flow 1700 may provide an illustrative example of the order or sequence of operations described herein; however, any order or sequence may be used. In some cases, one or more operations of process flow 1700 may not be performed or may be otherwise omitted. Additionally or alternatively, UE 205, RAN 210, and / or AMF 215 may perform operations not shown in process flow 1700. It should also be understood that any operation described herein may be performed independently of other operations described herein.

[0208] At the first instance (e.g., operation 1), one or more registration request operations (e.g., communication) can be performed. For example, UE 205 can (e.g., via RAN 210) transmit a registration request message to AMF 215. The registration request can be associated with a rules set ID. For example, AMF 215 can provide a rules set ID in response to receiving a registration request message from UE 205.

[0209] At the second instance (e.g., operation 2), one or more rule set ID change operations can be performed. For example, UE205 can change from a previous rule set associated with a previous rule set ID to a new rule set associated with the received rule set ID.

[0210] At the third instance (e.g., operation 3), one or more registration request operations (e.g., communication) can be performed. For example, UE 205 can (e.g., via RAN 210) transmit a registration request message to AMF 215. The registration request can be associated with a new rule set ID (e.g., the received rule set ID).

[0211] Figure 18 An example of a process flow 1800 supporting an activation rule set based on operational criteria, as described herein, is illustrated. One or more operations of process flow 1800 may be performed by UE 205, RAN 210, AMF 215, and / or PCF 220. Process flow 1800 may provide an illustrative example of the order or sequence of operations described herein; however, any order or sequence may be used. In some cases, one or more operations of process flow 1800 may not be performed or may be otherwise omitted. Additionally or alternatively, UE 205, RAN 210, AMF 215, and / or PCF 220 may perform operations not shown in process flow 1800. It should also be understood that any operation described herein may be performed independently of other operations described herein.

[0212] Prior to the first instance (e.g., operation 0), UE 205 can select a new preferred energy setting.

[0213] At the first instance (e.g., Operation 1), UE 205 (e.g., a supported UE) determines the requested NSSAI 1 based on configuration and URSP rules, depending on the S-NSSAI applicable based on UE local information and the current preferred energy setting at UE 205. If the URSP information includes a configuration for reporting energy settings for each S-NSSAI or UE level, the preferred energy setting is reported to AMF 215.

[0214] At the second instance (e.g., Operation 2), AMF 215 triggers an AM policy association update and reports the new preferred energy settings (if provided), and obtains any auxiliary information to be provided to RAN 210, as well as updated QoS information (such as UE-AMBR), or based on a new Service Provider Request (RFSP) that allows NSSAI.

[0215] At the third instance (e.g., Operation 3), AMF 215 provides the NG-RAN with the permitted NSSAI 1, and any additional auxiliary information provided to the NG-RAN if necessary.

[0216] Figure 19 An example flowchart 1900 supporting an activation rule set based on operational criteria, as described herein, is shown. Flowchart 1900 may illustrate examples of one or more operations performed by a device (e.g., device 200), such as that performed by a UE or as referenced... Figures 1 to 18 Other computing devices or controllers described are embodied in this description.

[0217] As shown in box 1905, the apparatus may include components (such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, etc.) for the UE to select a rule set from a plurality of rule sets based on one or more operating criteria associated with the UE, the rule set being used to at least partially define the URSP, each rule in the rule set corresponding to a corresponding rule set identifier in a plurality of rule set identifiers, wherein the rule set includes a plurality of TDs and a plurality of RSDs corresponding to the plurality of TDs.

[0218] As shown in box 1910, the apparatus may include components (such as processor 102, communication interface 106, transceiver circuitry 108, memory 104, etc.) for transmitting user plane services by the UE that match the TD in the selected rule set, wherein the user plane services are transmitted via a path indicated by one of the RSDs associated with the TD in the selected rule set.

[0219] Figure 20 An example flowchart 2000 supporting an activation rule set based on operational guidelines, as described herein, is shown. Flowchart 2000 may illustrate examples of one or more operations performed by a device (e.g., device 300), such as a network (e.g., one or more network devices) or as referenced... Figures 1 to 19 Other computing devices or controllers described are embodied in this description.

[0220] As shown in box 2005, the apparatus may include components (such as processor 102, memory 104, network interface 305, etc.) for generating (i) multiple rule sets that at least partially define multiple URSPs and (ii) multiple rule set identifiers corresponding to the multiple rule sets, wherein the rule sets in the multiple rule sets include multiple TDs and multiple RSDs corresponding to the multiple TDs.

[0221] As shown in box 2010, the apparatus may include components (such as processor 102, memory 104, network interface 305, etc.) for configuring the UE using multiple rule sets based on the generation of multiple rule sets.

[0222] Figures 5 to 20 Flowcharts and process diagrams depicting methods according to the example aspects are shown. It should be understood that each block or signal, and combinations of blocks and signals, can be implemented by various components, such as hardware, firmware, processors, circuit systems, and / or other communication devices associated with software that executes one or more computer program instructions. For example, one or more processes in the above-described process can be embodied by computer program instructions. In this regard, computer program instructions embodying the above-described processes can be stored in memory 104 of apparatus 200 and / or apparatus 300 employing the example aspects and executed by processor 102. As will be understood, any such computer program instructions can be loaded onto a computer or other programmable device (e.g., hardware) to produce a machine, such that the resulting computer or other programmable device performs the functions specified in the flowchart blocks. These computer program instructions can also be stored in a computer-readable storage medium that can direct a computer or other programmable device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of art, the execution of which performs the functions specified in the flowchart blocks. Computer program instructions may also be loaded onto a computer or other programmable device to cause a series of operations to be performed on the computer or other programmable device to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable device, provide operations for implementing the function specified in the flowchart box.

[0223] Therefore, the boxes in a flowchart support combinations of components used to perform a specified function and combinations of operations used to perform the specified function. It should also be understood that one or more boxes in a flowchart, and combinations of boxes in a flowchart, can be implemented by a dedicated hardware-based computer system that performs the specified function, or by a combination of dedicated hardware and computer instructions.

[0224] Many modifications and other embodiments set forth herein will be apparent to those skilled in the art who have benefited from the teachings given in the foregoing description and associated drawings. Therefore, it should be understood that this disclosure is not limited to the specific embodiments disclosed, and that modifications and other embodiments are intended to be included within the scope of the appended claims. Furthermore, although the foregoing description and associated drawings describe exemplary aspects in the context of certain example combinations of elements and / or functions, it should be understood that alternative aspects may provide different combinations of elements and / or functions 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 being 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.

Claims

1. A method for a user equipment (UE), the method comprising: Based on one or more operating criteria associated with the UE, a rule set from a plurality of rule sets is selected, the rule set being used to at least partially define the User Equipment Path Selection Policy (URSP), each rule in the rule set corresponding to a corresponding rule set identifier in a plurality of rule set identifiers, wherein the rule set includes a plurality of service descriptors (TDs) and a plurality of path selection descriptors (RSDs) corresponding to the plurality of TDs. as well as Send user plane traffic that matches a TD in the selected rule set, wherein the user plane traffic is sent via a path indicated by one of the RSDs associated with the TD in the selected rule set.

2. The method of claim 1, wherein the one or more operating criteria associated with the UE include one or more of the following: (i) the UE operates in an energy-saving mode, (ii) the UE operates in an on-duty mode associated with the user's occupation, or (iii) the UE operates in a personal use mode.

3. The method according to any one of claims 1 or 2, further comprising: The user equipment configuration for the UE is received from the core network of the communication network. The user equipment configuration includes the plurality of rule sets and the plurality of rule set identifiers. as well as The plurality of rule sets and the plurality of rule set identifiers are stored for future use.

4. The method according to any one of claims 1 to 3, further comprising: Send an indication of the selected rule set to the core network.

5. The method according to any one of claims 1 to 4, further comprising: Receive an instruction for an operating mode selected by the user for the UE, wherein the selection further includes selecting the rule set based on the operating mode for the UE.

6. The method according to any one of claims 1 to 5, further comprising: It is determined that one or more operating criteria associated with the UE are met, wherein the UE selects the rule set in response to the one or more operating criteria being met.

7. The method according to any one of claims 1 to 6, further comprising: The UE receives an indication from the core network of one or more network slices corresponding to one or more rule sets in the plurality of rule sets, wherein the UE transmits the user plane service on one or more paths associated with the one or more network slices.

8. The method according to any one of claims 1 to 7, wherein the RSD in the plurality of RSDs includes an indication of at least one rule set identifier.

9. The method according to any one of claims 1 to 8, wherein one of the plurality of TDs includes an indication of at least one rule set identifier.

10. The method according to any one of claims 1 to 9, wherein the plurality of rule set identifiers are based on corresponding values ​​for one or more of the following: (i) path selection verification criteria, or (ii) TD verification criteria.

11. The method according to any one of claims 1 to 10, wherein one or more of the plurality of rule set identifiers are associated at least with a user-selectable setting identified using human-readable characters, the user-selectable setting corresponding to the one or more operating criteria.

12. A method comprising: Generate (i) multiple rule sets that at least partially define multiple User Equipment Path Selection Policies (URSPs), and (ii) multiple rule set identifiers corresponding to the multiple rule sets, wherein the rule sets in the multiple rule sets include multiple Service Descriptors (TDs) and multiple Path Selection Descriptors (RSDs) corresponding to the multiple TDs. as well as Based on the generated multiple rule sets, the user equipment (UE) is configured using the multiple rule sets.

13. The method of claim 12, further comprising: Send the association between the rule set identifier among the plurality of rule set identifiers and the user-selectable settings identified using human-readable characters to the UE.

14. The method according to any one of claims 12 or 13, further comprising: Send to the UE an indication of one or more network slices corresponding to one or more URSP rule sets in the plurality of URSP rule sets, wherein the indication of the selected URSP rule set in the plurality of URSP rule sets is received via the one or more network slices.

15. The method according to any one of claims 12 to 14, further comprising: The UE receives an indication of the selected rule set from the plurality of rule sets.

16. The method according to any one of claims 12 to 15, further comprising: Send to the UE an indication of one or more network slices corresponding to one or more rule sets in the plurality of rule sets.

17. The method according to any one of claims 12 to 16, wherein the RSDs in the plurality of RSDs include an indication of a corresponding rule set identifier.

18. The method according to any one of claims 12 to 17, wherein one of the plurality of TDs includes an indication of a corresponding rule set identifier.

19. The method according to any one of claims 12 to 18, wherein the plurality of rule set identifiers are based on corresponding values ​​for one or more of: (i) a path selection verification criterion, or (ii) a TD verification criterion.

20. The method of any one of claims 12 to 19, wherein one or more rule set identifiers are associated with user-selectable settings identified using human-readable characters.

21. A user equipment (UE), comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the UE to perform the method according to any one of claims 1 to 11.

22. An apparatus comprising: At least one processor; as well as At least one memory stores instructions for policy control functions of the core network of the communication network, wherein the execution of the instructions by the at least one processor causes the device to perform operations, the operations including: Generate (i) multiple rule sets that at least partially define multiple User Equipment Path Selection Policies (URSPs), and (ii) multiple rule set identifiers corresponding to the multiple rule sets, wherein the rule sets in the multiple rule sets include multiple Service Descriptors (TDs) and multiple Path Selection Descriptors (RSDs) corresponding to the multiple TDs. as well as Based on the generated multiple rule sets, the user equipment (UE) is configured using the multiple rule sets.

23. A non-transitory computer-readable storage medium comprising instructions that, when executed by at least one processor of a user equipment, cause the user equipment to perform the method according to any one of claims 1 to 11.

24. A non-transitory computer-readable storage medium comprising instructions that, when executed by at least one processor of the apparatus, cause the apparatus to perform the method according to any one of claims 12 to 20.

25. A computer program comprising instructions, wherein when the computer program is run on a user equipment, the user equipment is caused to perform the method according to any one of claims 1 to 11.

26. A computer program comprising instructions, wherein when the computer program is run on a device, the device is caused to perform the method according to any one of claims 12 to 20.

27. A core network, comprising: An access management function, configured to perform the method according to any one of claims 12 to 20.

Images