Abstract: The present application at least describes an apparatus including a non-transitory memory including instructions stored thereon and a processor, operably coupled to the non-transitory memory, configured to execute as set of instructions. The set of instructions include determining a preference to operate in a reduced capacity (REDCAP) mode in a network. The set of instructions also include transmitting, via a radio resource control (RRC) message to a registration location on the network, a registration request to operate in the REDCAP mode. The registration request prompts a selection of an access and mobility function (AMF) configured to authorize the apparatus to operate in the REDCAP mode and communicate with the apparatus. The registration request prompts a session management function (SMF) to determine characteristics of a protocol data unit (PDU) session of the apparatus.

Abstract: A method and devices may assist in addressing signaling efficiency issues when the network aims to page a group of UEs in a multicast group so that the UEs will switch from CM-IDLE state to CM-CONNECTED state.

Abstract: Methods, apparatus, and systems are described for improved discontinuous reception (DRX) for PCS communication (e.g., including unicast, groupcast and broadcast) for a User Equipment (UE) and particularly for reducing the power consumption.

Abstract: A method performed by a wireless transmit receive unit (WTRU), of receiving a mobile terminated (MT) transmission using an ambient Internet of Things (IOT) service (AIS) is described. The method includes the WTRU receiving an activation signal from a radio access network (RAN) node and harvesting energy. The WTRU determines a format of the received activation signal and based on the format of the activation signal, determines to begin an MT Data procedure with the network. The WTRU receives system information broadcasted by the RAN node and determines to continue the MT data procedure with the network. The WTRU transmits a MT data request message to the RAN node; and receives a MT data container message from the RAN node. The MT data request may include an RRC part and NAS part. The MT data request may include a device identifier and an AIS ID.

Abstract: A procedure performed by a network node of providing an Ambient IoT service (AIS) is described. The procedure includes a network node receiving an API request from an application server to perform a procedure with one or more ambient IoT devices. The request may include a time duration. The network node invokes a UDM service UDM to check application servicer authorization to perform the procedure. The network node determines at least an AMF identity. The network node invokes an AMF service requesting the AMF initiate a procedure with one or more ambient IoT devices. A response is received from the AMF including at least one identifier of an Ambient IoT device. The network nodes sends a response to the application server, the response including the at least one identifier of an Ambient IoT device.

Abstract: A first policy control function (PCF) in a first network node may receive an indication from a session management function (SMF) that a protocol data unit (PDU) session is an alternative PDU session, and an indication of whether the PDU session is in a drop state. The first PCF may send a message with an indication to a second PCF in a second network node to indicate that the network node is serving a PDU session that is an alternative PDU session. In an example, the message with an indication to the second PCF may also identify the PDU session. The first PCF may receive a message from the second PCF with an indication that a second PDU session has experienced a fault or degraded performance. Further, the first PCF may send a message to the SMF to change the PDU session to a no-drop state.

Abstract: One or more systems, devices, and/or methods may address approaches and use techniques described herein to onboard a device when the device does not have a predetermined home network. The device may indicate, explicitly or implicitly, that it does not have a home network to an onboarding network. The onboarding network may authenticate the device, then provide the device with a provisioning server address. The onboarding network may initiate a unified data management service, and provide the provisioning server with a temporary identifier for the device. The device may establish a connection with the provisioning server, and provide the temporary credentials to the device. The device may use the temporary credentials to register with the onboarding network.

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: System and methods that improve the use of network functions on edge data networks are disclosed. A mechanism that supports edge-assisted UE context and trigger collection is described herein, where a UE can actively send its context information and/or any trigger (e.g. a request for a network function/service to be deployed in edge data networks, etc.) to an edge enabler server, which processes the received context and triggers from its UEs. The edge enabler server may also forward UE context and triggers to 5G core network (5GC) upon receiving a solicitation request from the 5GC, or if the 5GC has already made a subscription for getting notification on UE context and triggers. A network repository function is provided as a new network function collect, store, and manage edge data network information.

Abstract: A wireless transmit/receive unit (WTRU) may receive a power reporting policy from a network node. The power reporting policy may include one or more triggers associated with sending a power status report. The WTRU may determine that a trigger of the one or more triggers associated with sending the power status report has been satisfied. The WTRU may send the power status report to the network node in accordance with the power reporting policy. The power status report may include power status information associated with the WTRU and/or an indication that indicates the determined trigger to send the power status report.

Abstract: Methods are described for dynamically managing device locationing groups. According to some aspects, mobile devices may be tracked on a group basis, e.g., as opposed to being tracking on an individual basis. For example, location information for each of a plurality of mobile devices may be received at a location group server (LGS) and the LGS may determine (e.g., based on the location information) that each of the plurality of devices are in a physical location. One or more location group operations may be triggered by the location group server (e.g., based on determining that each of the plurality of devices are in the physical location) and the LGS may receive a location update from a device of the plurality of mobile devices (e.g., wherein the location update is not received from a remainder of the plurality of mobile devices).

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: Methods, systems, and devices may assist in performing group-based paging, such as downlink control information-based group paging, paging radio network temporary identifier- based group paging, wakeup signal-based group paging, or sweep-based group paging. Also, method, systems, and devices may assist in performing beam-based paging or configuring cross- slot scheduling for paging.

Abstract: A caching entity may store a cached copy of a service layer resource. An original hosting entity may maintain a registry of the corresponding cached resources. Optionally, the original hosting entity may set cache parameters to govern the lifetime of the cache on a caching entity. The caching entity may keep storing the cached copy of the resource and the original hosting entity may obtain statistics about the cached resource. By knowing the statistics, e.g. how many times a resource is retrieved on each caching entity, the original hosting entity may better manage the resource.

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: Systems, methods, and instrumentalities may implement service-based discovery in a network, such as a 3GPP or 3GPP2 network. A Discovery Server may be used to query and find services offered by the network or by entities that interface with the network. Situational context information or policy information, or both, may be communicated to the discovery server so that the Discovery Server can provide context-aware and policy-based discovery services. The Discovery Server may be used to control which of the entities that interface with the network can discover one another. The Discovery Server may support queries based on, for example, the type of MTC entity, the type of services hosted on the entity, the availability times of the entity, types of protocols supported, levels of Quality of Service (QoS) supported, and MTC-IWF services.