Abstract: Systems and methods are described herein to automate managing of service layer operations comprised of multiple elementary operations and offloading the burden of performing such multi-step operations from a requesting entity to the service layer. A Request Abstraction Service (RAS) is described herein for the autonomous execution of such multi-step operations. Methods and apparatuses are also described herein for a service layer framework for integrating generic and functional user interfaces as services managed by the SL on behalf of requesting entities.

Abstract: Lightweight, dynamic mechanisms are provided to support service layer interworking and resource extensibility. For example, one mechanism disclosed herein comprises defining a new service layer (SL) resource definition registration procedure that allows for specifying custom attributes of service layer resources to represent third party technology resources. A second mechanism disclosed herein comprises defining a new SL data model mapping registration procedure to map service layer resources to third party data models and to provide a new interworked retargeting indicator to the service layer. Further, a third mechanism disclosed herein comprises defining a SL generic interworking procedure to intelligently retarget requests toward interworked resources based on the interworked retargeting indicator provided by the data model mapping.

Abstract: Internet of Things (IoT) configurable event and action sequencing mechanisms for interconnecting various IoT events together to achieve an event and action sequencing process that may efficiently enable complex uses of the data available in IoT systems.

Abstract: Mechanisms for subscription and notification may include dynamically changing notification behavior based on notification target status or support access to notification history information.

Abstract: IoT service layer capabilities may be employed to automate and simplify the service enrollment process for IoT service subscribers/enrollees. These capabilities enable virtualization of a service subscriber and the physical IoT devices, applications, data and authorized users of the subscriber into a software profile that is representative of the subscriber. Once virtualized, a service subscriber may then delegate the complexities and burden of service enrollment to an automated IoT service enrollment software function.

Abstract: Cellular devices are becoming more and more powerful, and may host a number of different non-cellular capabilities, such as cameras, accelerometers, and sensors. Today, these capabilities are used mainly to provide some service to the device or the device owner. Disclosed herein are methods and systems for enabling devices to register their device capabilities with a cellular network, providing a mechanism for Application Servers to discover non-cellular capabilities of the devices, providing a mechanism to have the Application Servers configure these non-cellular capabilities of the devices, and preparing the device and the network for cellular traffic generated as a result of the Application Server using these non-cellular capabilities.

Abstract: A method of multi-hop relay chain formation in a wireless communication network includes discovering, via a remote electronic device, one or more other electronic devices in communication range of the remote electronic device; selecting one of the discovered electronic devices as an relay electronic device for communicating in the multi-hop relay chain; after selecting the relay electronic device, transmitting, via the remote electronic device, a request to establish a PC5 link; and establishing the PC5 link with the remote electronic device to join or form the multi-hop relay chain within the wireless communication network.

Abstract: Methods and apparatuses are described herein for multi-subscriber identification module (SIM) connected mode operation. In one embodiment, a wireless communications device may receive, from an access stratum interface, a request access to the receiver chain during a receiving opportunity. The wireless communications device may determine that the receiver chain is available during the receiving opportunity. The wireless communications device may send a response indicating access is granted to cause the access stratum interface to receive a downlink transmission during the receiving opportunity. The wireless communications device may receive, from the access stratum interface, a second request for a transmitter chain during a transmitting opportunity. The wireless communications device may determine that the transmitter chain is available during the transmitting opportunity.

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: A user equipment (UE) and a network may communicate to dynamically adapt the steering of traffic over both 3GPP 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: A Data Sample Collection Service (DSCS) may be configured to receive various data sample collection requests from users and to process the one or more requests on behalf of the users. In order to properly describe what kind of Ready-to-Use Data Samples (RDS) a user needs, the DSCS may adopt a Data Sample Template (DST). By using the DST, the user can clearly depict what their desired data samples look like, along with various quality requirements regarding the data samples. The DSCS can further provide a DST Management function to users. In general, DST management involves the processes of DST creation, DST update, DST deletion and DST activation/de-activation. For example, a user may create a DST based on its data sample collection needs. Later, the created DST can also be updated and/or deleted based on dynamic changes to the needs of the user.

Abstract: Some underlying networks such as Low-Power Wide-Area Networks (LPWAN) have limited communication bandwidth and strict requirements on maximum message size. These requirements may pose a challenge for data or resource exchange between two service layer (SL) entities, for example, because resource representations to be exchanged may have too large a size to be supported by the underlying networks. In some cases, traditional data compression algorithms can be used to alleviate this problem to some degree, but it is recognized herein that there are associated computation costs due to compression and decompression that may not be affordable for constrained IoT devices. Various embodiments described herein address this problem, among others by defining a Resource Representation Common Part (RRCP) and storing it at the service layer. In some cases, the RRCP is not transmitted between SL entities, thereby reducing SL message sizes to cater to the constraints of underlying networks.

Abstract: A distributed ledger interworking architecture is described wherein a distributed ledger proxy interfaces with IoT service layer systems and distributed ledger systems. Service layer nodes may interact with the distributed ledger proxy to leverage functions provided by distributed ledger systems, such as to request that the distributed ledger proxy insert some service layer information into the distributed ledgers. A distributed ledger proxy can support multiple service layer nodes and may interface to multiple different distributed ledger systems.

Abstract: Internet of Things (IoT) event objects can be tailored to specific device types and capabilities. An IoT event object can use a flexible definition of an event that can be reconfigured. An IoT event object allows for the ability to set different triggering conditions and priorities. Individual event definitions can be extended to create more complex events. A Notification Handler supports sending a request or command in response to an event that requires action.

Abstract: A user equipment (UE) operating in an “Onboarding Mode” may search for a network broadcasting Onboarding Capability Information (OCI), then register using onboarding credentials and receive SNPN credentials from the network. The UE may then exit onboarding mode, enter Manual Network Selection or Automatic Network Selection mode, and connect to the SNPN. A UE may also receive from a network a list of PLMNs and SNPNs that are equivalent then, when registering, indicate to the network that a requested slice is not associated with the UE's HPLMN, but is associated with an SNPN. The network may indicate to the UE how the slices of the network map to the slices of the SNPN, and may indicate whether a slice that is offered by the network only partially maps to a slice of the SNPN or HPLMN.

Abstract: A Network Data Analytic Function (NWDAF) may assist an application server by determining a quality of server (QoS) or delivery timing requirements can be met at a location, e.g., along a route. The NWDAF may collect information from one or more cells near the location, e.g., an Operations and Management (OAM) system. Communications with the NWDAF may be facilitated by a Network Exposure Function (NEF) or an Nnwdaf_AnalyticsInfo_Request service operation. The NWDAF may indicate a potential QoS change at the location. The application server may be a V2X application server.

Abstract: An electronic device is configured to transmit, to a wireless network, a link request message requesting a user identifier be associated with an identifier corresponding to the electronic device; receive, from the wireless network, a registration response confirming that the user identifier has been associated with the identifier corresponding to the electronic device; and receive, from the wireless network, updated configuration information for the electronic device, wherein at least part of configuration information is associated with the user identifier.

Abstract: Methods, apparatus, and systems are described for improved application interaction for network slicing. A wireless transmit/receive unit may send, to a network node, a registration request including an indication that the WTRU is capable of receiving information associated with a temporal availability of a network slice. The WTRU may receive a registration response including the information associated with the temporal availability of the network slice. The WTRU may determine, based on the temporal availability of the network slice, to stop use of a protocol data unit (PDU) session associated with the network slice.

Abstract: A wireless transmit/receive unit may request, from a core network, authorization for creating one or more personal networks of one or more devices. After being granted authorization, the UE may be enabled to create a personal network and to cause a PDU session for the personal network to be established with the core network. The UE may enable members of the personal network to send data associated with the personal network via the PDU session.

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.