Abstract: Methods, apparatus, and systems are described for improved edge network access for a UE. According to some aspects, a UE may receive a first Data Network Name (DNN) from an application and determine, based on a Data Network Name (DNN) Replacement Rule, the first DNN is associated with a second Data Network Name (DNN), where the first DNN and the second DNN are different. The UE may determine, based on the DNN Replacement Rule, to associate traffic from the application with a Protocol Data Unit (PDU) Session, where the PDU Session may be used to send data from the application to a network and the PDU Session is associated with the second DNN.

Abstract: Methods and apparatuses are described herein for providing fine-grained QoS rules within UE Policies. A network entity may receive triggers to update the policies of a user equipment (UE) with parameters based on input such as input from a third party. The network entity may derive fine-grained quality of service (QoS) rules and corresponding QoS Profiles and delivers them to the UE using a UE Policy container via the Non-Access Stratum (NAS). The fine-grained rules may comprise: a destination fully qualified domain name (FQDN) or uniform resource locator (URL), an Application ID, a User Route Selection Policy precedence value, etc. The fine-grained rules also provide mechanisms for time gating or volume gating. The UE may request new QoS treatment resulting in UE Policy update and may use the information in the fine-grained QoS rules when establishing or modifying PDU Session to apply QoS Flow Identifier (QFI) marking.

Abstract: Methods, systems, and devices may assist in policy and parameters provision to network to support the redundant transmission configuration using dual connectivity DC. In particular, a PDU session pair information (PSPI) is associated with both a first and second PDU session. The PSPI is then sent to an AMF in the network in both a first PDU session establishment message and a second PDU session establishment message. The AMF may then forward this to the RAN and first and second SMF. This allows the RAN to associate the two PDU sessions.

Abstract: User equipment (UE) may detect a disaster condition, and the resolution thereof, based on broadcast information, RRC messaging, NAS messaging, the ability to connect to an allowable PLMN, and indications from forbidden PLMNs. In a disaster condition, a UE may perform an enhanced PLMN selection procedure wherein, for example, the UE will not consider PLMNs that are in a disaster situation if the disaster situation applies to a current location of the UE, prioritize forbidden PLMNs for disaster roaming connection. For disaster roaming connection, the UE may be configured by an otherwise forbidden PLMN with information about what services the UE can access and what type of authentication procedure the network is able to perform with UE. Upon detecting that the disaster condition is over, the UE move back to an allowable PLMN.

Abstract: A user equipment, (UE) and a network may communicate to dynamically adapt the steering of traffic over both 3 GPP and non-3GPP accesses for uplink, downlink, or both. For example, a UE may request from the network the ability to dynamically adapt uplink traffic and the network may also apply the same traffic adaptation on downlink traffic. The UE and network may communicate dynamic traffic adaptation using traffic steering rules, e.g., via control plane NAS protocol, and with user plane signalling, e.g., via user plane PMF protocol.

Abstract: An overall architecture to integrate multicast and broadcast service into a general 5G core network. The architecture may provide methods and systems to switch the delivery mode of transmitting messages to User Equipment (UE)s from a unicast mode to a multicast mode. The method includes triggering events at UE, network functions, content provider or RAN node to initiate the switch process; a procedure for UE initiated switch from unicast to multicast; a procedure for network-initiated switch from unicast mode to multicast mode; and a procedure for RAN initiated switch from unicast mode to multicast mode. The architecture may also provide methods to switch the delivery mode from multicast mode to unicast mode.

Abstract: A user equipment “UE” may be configured with a client application for data collection, contact information pertaining to a network Application Function “AF,” and data collection information such as parameters, whereby the UE collects data that is specific to the UE and sends it to the AF over a user plane. The data collection parameters may include one or more of a type of data the UE should collect, data associated with one or more analytics IDs and application IDs, a data collection frequency, and a reporting frequency. The data collection information may include a processing requirement, an expiration time for the collected data, a timestamp of the data collection, and/or a correlation identifier that associates the collected data with the UE.

Abstract: Methods, systems, or devices may assist in performing slice-based cell selection and reselection, offloading of initial access attempts for a given slice to a specific frequency layer, performing slice-aware PLMN selection, performing slice-based barring, performing slice-based Random Access, or performing slice-based paging, among other things.

Abstract: Methods, systems, and devices may assist in enhancements to PMF protocol and new ATSSS steering modes to enable support for analytics driven or multi-USIM steering. The following functionalities are disclosed: 1) Enable UEs to use the PMF protocol to provide UE specific data to the NWDAF for analytics purposes; 2) Enable multi-USIM UEs to notify the core network over the user plane of the UE's desire to pause communications with the CN associated with one USIM so the UE can communicate with the CN associated with another USIM; 3) Define new ATSSS steering modes to support data analytics driven steering; and 4) Define new ATSSS steering modes to support Multi-USIM steering, among other things.

Abstract: Network Slice Selection Assistance information (NSSA1) may be signaled between U ser Equipment (UE) and a network. NSSA1 sent from the network to the UE may include, for example. Operating Frequency Band (OFB) for each Single NSSAI(S-NSSA1) in the NSSAI, as well as a Radio Access Technology (RAT) Frequency Selection Priority (RFSP) index, which the network configures as a part of UE access and mobility; subscription, during a UE registration procedure. RAT restrictions may be enhanced to indicate to the UE that certain slices are not accessible via certain RATs. A UE may be provided by the network with an alternative NSSAI and corresponding OFBs for each S-NSSAI thereby indicating to the UE that these S-NSSAI would have been allowed had they been requested. A UE may be able to choose an alternative Allowed NSSAI and send a registration update request to the network.

Abstract: Methods devised for enabling external AF/AS to provide information to SGC regarding Edge Data Network Configurations. Further, methods for UE provisioning for Edge service enablement are provided. Mechanisms are disclosed for: enabling UEs, not hosting an EEC, to request EDN information provisioning in order to enable Application Clients, which are not Edge-aware, to utilize Edge services; enabling an EEC, hosted by a UE, to obtain Edge Configuration information by using URSP rules for establishing IP connectivity with a Configuration Server; and enabling an EEC, hosted by a UE, to obtain Edge Data Network configuration information during registration.

Abstract: Systems and methods are described to automate managing of relationships between IoT entities (e.g., devices, apps, users) and offloading the burden of managing these relationships from users. A Relationship Management Service (RM Service) is described herein for the autonomous establishment, modification, and tear-down of relationships between IoT entities.