Abstract: A network node, e.g., an edge configuration server (ECS), associated with a first PLMN may receive a first message from a WTRU. The first message may indicate a request to be notified if a type of network node, e.g., an ECS, becomes available to be accessed by the WTRU. The network node may receive a second message from a second network node. The second message may indicate an identity of a second PLMN and may indicate that the WTRU has become registered with the second PLMN. The network node may determine that a third network node of the type of network node, e.g., an ECS, is available to be accessed by the WTRU in the second PLMN. The network node may determine local breakout (LBO) information for the WTRU to establish a LBO packet data unit (PDU) session in the second PLMN and access the third network node.

Abstract: A base station device may include a processor and memory. The base station device may be configured to receive a registration request from a WTRU. The registration request may include an indication that the WTRU is requesting access to a private network. The base station device may send the registration request to a network node. The base station device may receive an identifier of the WTRU from a network node. The base station device may determine whether the WTRU is authorized to access the private network based on the received identifier of the WTRU and a list of allowed device identifiers for the private network. The base station device may send authorization information and an indication that the WTRU has been authorized to access the private network to the network node. The base station device may forward a registration accept message to the WTRU.

Abstract: Systems and methods are described herein for handling connection rejects via a wireless transmit/receive unit (WTRU)-to-WTRU (U2U) relay associated with backoff times on behalf of a source end WTRU. A relay WTRU may retry to establish connection with a target WTRU on behalf of a source WTRU, for example, based on receiving a rejection (e.g., with a backoff value) from the target WTRU. The source WTRU may associate the reject message to the target WTRU, and the relay WTRU may be available to reach other target WTRUs. The relay WTRU may send a reject message to other source WTRUs (e.g., if the back off duration is active, running) for the same target WTRU.

Abstract: Procedures, methods, architectures, apparatuses, systems, devices, and computer program products for offloading data traffic flows, received by a wireless transmit-receive unit (WTRU) via an edge network of a cellular network or transmitted by the WTRU via the edge network of the cellular network, to a non-cellular network. A WTRU may determine that a data traffic flow received-transmitted by the WTRU transits via the edge network and take appropriate actions.

Abstract: A relay node may detect conflicts regarding media access control (MAC) addresses. A source node may send a request to the relay node. The request may be a request to establish communications with a target node. The source may send, to the relay node, an indication of the MAC address of the source node. The source node may receive a reject message from the relay node. The reject message may comprise an indication of a conflict associated with the MAC address of the source node.

Abstract: In one or more embodiments, one or more devices, systems, and/or methods may address solutions and/or innovations for 5G System edge computing, edge applications, and/or other wireless systems. For example, one or more of the following techniques may be used to address shared-application vertical-session-based edge-application-instance discovery and selection: there may be an application vertical-session identifier; one or more application-vertical-session-based EAS registration, discovery, and selection procedures; application-vertical-session-based EDN/EES provisioning; and/or, application-vertical-session management.

Abstract: Systems and methods for supporting multiple uncrewed aerial vehicle (UAV) Service Suppliers (multi-USS) are described. The methods may be performed by a wireless transmit/receive unit (WTRU) including a UAV application enabling (UAE) client located in the UAV with the method performed with the UAV in-flight. Steps may include: sending a registration request to a UAE server, the registration request including an indication of multi-USS capability; receiving a registration response message that includes an indication that the UAE server supports multi-USS capability; receiving a multi-USS configuration request that includes multi-USS configuration parameters related to conditions under which the UAE client may initiate a USS change and a list of allowed USSs; sending a multi-USS configuration response; and performing a multi-USS change and sending a multi-USS change notification based on the multi-USS configuration parameters.

Abstract: A wireless transmit receive unit (WTRU) may be configured to transmit on a first interface and determine to transmit on a second interface. The WTRU may receive configuration information. For example, the configuration information may include a path switching capability indication, a path switching policy, and an information sharing method indication. Based on the configuration information, the WTRU may determine to perform a path switch. In response to determining to perform a path switch, the WTRU may retrieve certain information associated with a peer WTRU. The WTRU may transmit, based on the retrieved information, a path switch request to the peer WTRU. The WTRU may receive a response to the path switch request. If the response indicates that the path switch request has been accepted by the peer WTRU, the WTRU may perform a communication path switch from the first interface to a second interface.

Abstract: A wireless transmit/receive unit (WTRU) may receive parameters associated with a plurality of personal Internet of Things (IoT) network (PIN) gateways (GWs) connected to a PIN. The received parameters may comprise a PIN element type and one or more PIN policy parameters for each of the plurality of PIN GWs. The WTRU may determine a priority for each of the plurality of PIN GWs using the PIN element types and the one or more PIN policy parameters. The WTRU may generate, using the determined priorities, a prioritized list of PIN GWs available on the PIN. The WTRU may receive a connection request from a PIN element connected to the PIN. The WTRU may select one of the plurality of PIN GWs for the PIN element to use to establish connection to the core network.

Abstract: A wireless transmit/receive unit (WTRU) may send a discovery request to a first edge enabler server (EES) instance to obtain edge application server (EAS) information. The WTRU may receive a discovery response from the first EES instance. The discovery response may indicate a list of EAS information and/or registrar EES information for one or more EAS instances in the list of EAS information. The WTRU may select an EAS instance based on one or more of the list of EAS information or the registrar EES information for the one or more EAS instances. A second EES instance of the plurality of EES instances may be the registrar EES of the selected EAS instance.

Abstract: The disclosure relates to early detection and indication of a Quality-of-Service (QoS) non-fulfillment in one or more radio links serving an application. A client device monitors for a QoS non-fulfillment in the one or more radio links based on a QoS monitoring configuration associated with the application. The QoS monitoring configuration may be received from a network node and/or derived based on a predefined rule. Upon detection of a QoS non-fulfillment of one or more QoS requirements obtained from the QoS monitoring configuration, the client device provides a QoS non-fulfillment indication to the application. The QoS non-fulfillment indication gives the application an early warning about QoS non-fulfillment on the one or more radio links. Thereby, allowing the application to take precautionary actions to counteract possible negative consequences of the QoS non-fulfillment. Furthermore, the disclosure also relates to corresponding methods and a computer program.

Abstract: A method for UE-to-UE (U2U) relay discovery security is disclosed. The method may comprise provisioning an end-UE with security material for a direct discovery set and a U2U discovery message and provisioning a U2U relay with security material for the U2U discovery message. The security material for the direct discovery set may comprise at least one of: A ProSe restricted code, associated key material, or an indicator associated with a relay service code (RSC) that indicates whether the RSC supports per ProSe direct discovery set protection. The method may comprise sending, by the end-UE to the U2U relay, a direct connection request (DCR) message. The DCR message may comprise at least one of: an RSC, and end-UE User info identification (ID), or a ProSe restricted code. The method may comprise sending, by the end-UE, an indication for direct discovery set protection.

Abstract: A relay node may detect conflicts regarding media access control (MAC) addresses. A source node may send a request to the relay node. The request may be a request to establish communications with a target node. The source may send, to the relay node, an indication of the MAC address of the source node. The source node may receive a reject message from the relay node. The reject message may comprise an indication of a conflict associated with the MAC address of the source node.

Abstract: A relay node may detect conflicts regarding media access control (MAC) addresses. A target node may receive a request from the relay node. The request may comprise a request to establish communications with the target node. The target node may send, to the relay node, an indication of the MAC address of the target node. The target may receive a link release message from the relay node. The link release message may comprise an indication of conflict associated with the MAC address of the target node.

Abstract: A Relay node may detect conflicts regarding media access control (MAC) addresses. A relay node may receive a request to establish a link with a source node. The relay node may receive the MAC address of the source node. The relay node may detect a conflict associated with the MAC address of the source node. The relay node may reject the request to establish the link with the source node.

Abstract: A relay node may detect conflicts regarding media access control (MAC) addresses. The relay node may receive a request to establish a links with a source node and a target node. The relay node may receive the MAC addresses of the source node and the target node. The relay node may detect a conflict associated with the MAC addresses of the source node and the target node. The relay node may release the link with the target node.

Abstract: Systems and methods for supporting multiple uncrewed aerial vehicle (UAV) Service Suppliers (multi-USS) are described. The methods may be performed by a wireless transmit/receive unit (WTRU) including a UAV application enabling (UAE) client located in the UAV with the method performed with the UAV in-flight. Steps may include: sending a registration request to a UAE server, the registration request including an indication of multi-USS capability; receiving a registration response message that includes an indication that the UAE server supports multi-USS capability; receiving a multi-USS configuration request that includes multi-USS configuration parameters related to conditions under which the UAE client may initiate a USS change and a list of allowed USSs; sending a multi-USS configuration response; and performing a multi-USS change and sending a multi-USS change notification based on the multi-USS configuration parameters.

Abstract: Methods and apparatuses for power saving are described herein. A method performed by a remote wireless transmit/receive unit (WTRU) may include receiving a broadcast message indicating a power saving capability, sending, to a relay WTRU, a request for direct communication, receiving an acknowledgement from the relay WTRU in response to the request for direct communication, and establishing a link to the relay WTRU based on the received acknowledgement. The method may further include sending, to the relay WTRU, a message for registration with a network, receiving, via the relay WTRU, a message from the network in response to the message for registration, sending, to the relay WTRU, a message indicating that a power saving feature is enabled, and adjusting parameters for power saving. The request for direct communication may include information indicating one or more power saving capabilities or power saving requirements of the remote WTRU.

Abstract: A wireless transmit/receive unit (WTRU) may send a discovery request to a first edge enabler server (EES) instance to obtain edge application server (EAS) information. The WTRU may receive a discovery response from the first EES instance. The discovery response may indicate a list of EAS information and/or registrar EES information for one or more EAS instances in the list of EAS information. The WTRU may select an EAS instance based on one or more of the list of EAS information or the registrar EES information for the one or more EAS instances. A second EES instance of the plurality of EES instances may be the registrar EES of the selected EAS instance.

Abstract: A method for UE-to-UE (U2U) relay discovery security is disclosed. The method may comprise provisioning an end-UE with security material for a direct discovery set and a U2U discovery message and provisioning a U2U relay with security material for the U2U discovery message. The security material for the direct discovery set may comprise at least one of: A ProSe restricted code, associated key material, or an indicator associated with a relay service code (RSC) that indicates whether the RSC supports per ProSe direct discovery set protection. The method may comprise sending, by the end-UE to the U2U relay, a direct connection request (DCR) message. The DCR message may comprise at least one of: an RSC, and end-UE User info identification (ID), or a ProSe restricted code. The method may comprise sending, by the end-UE, an indication for direct discovery set protection.