Abstract: Methods and apparatus are described for configuring desired network capabilities in a service-based network, including a method for a UE to initiate a network capability based registration to configure its desired network capabilities, a method for UEs to initiate a network capability based registration update when UEs are already registered to the network and want to dynamically re-configure their network capabilities, and a method for a network capability based UE configuration update, which allows NFs or ASs to initiate updating the network capabilities in a network slice for the UE.

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: 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: 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: There is provided an apparatus that includes processing circuitry which determines that a policy is needed from a network for a particular type of traffic or network connection, transmit a non-access stratum (NAS) message to the network to request a policy, the message indicating what type of traffic or network the policy is required, and receive a response from the network. Provided is another apparatus that includes processing circuitry which receives a first non-access stratum (NAS) message from a network with configuration information that indicates that notifications related to the use of policies by the apparatus are desired, and transmit a second non-access stratum (NAS) message to the network, the second NAS message includes the notification relating to the use of policies by the apparatus.

Abstract: Methods and apparatuses are described herein for a framework for data brokerage services in a service layer. A first apparatus may receive, from a second apparatus, a first signal comprising first information indicating a publishing intent associated with atopic indicator. The first apparatus may receive, from a third apparatus, a second signal comprising second information indicating a subscription intent associated with the topic indicator. The first apparatus may generate, based on the publishing intent and the subscription request, a topic instance. The first apparatus may send a third signal comprising an announcement message indicating the generated topic instance. The first apparatus may receive, from the third apparatus, a fourth signal comprising a subscription request for the generated topic instance. The first apparatus may send, to the third apparatus, at least one fifth signal comprising notifications and publish instances associated with the generated topic instance.

Abstract: An IoT/M2M service layer may be provided with the capability to protect user privacy. This functionality may allow the IoT/M2M service layer to anonymize user data, particularly when user data is shared with third party consumers. A privacy policy service may enable the IoT service layer system to generate anonymization (e.g., privacy) policies based on inputs such as legal obligations, subscriber privacy preferences, and an authorization level of the data consumer. Data anonymization policies may be output from the privacy policy service and may be sent to a data anonymization service, where raw data may be anonymized based on the one or more data anonymization policies. The output from the data anonymization service function may be a privatized (e.g., anonymized) version of data that may prevent the data consumer from discovering one or more identifying characteristics of a user.

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: An IoT/M2M service layer may be provided with the capability to protect user privacy. This functionality may allow the IoT/M2M service layer to anonymize user data, particularly when user data is shared with third party consumers. A privacy policy service may enable the IoT service layer system to generate anonymization (e.g., privacy) policies based on inputs such as legal obligations, subscriber privacy preferences, and an authorization level of the data consumer. Data anonymization policies may be output from the privacy policy service and may be sent to a data anonymization service, where raw data may be anonymized based on the one or more data anonymization policies. The output from the data anonymization service function may be a privatized (e.g., anonymized) version of data that may prevent the data consumer from discovering one or more identifying characteristics of a user.

Abstract: Methods, systems, and apparatuses that enable a Service Layer (SL) to support analysis of internet of things (IoT) data and enable shared access to information generated by the analysis. An analytics management service may allow SL entities to configure analytics functions for many different IoT sources of data and organize the results in a customizable manner. The SL may support coordinating the analysis of IoT data from multiple independent sources and organizing the results of the analysis.

Abstract: Methods, systems, and apparatuses that enable a Service Layer (SL) to support analysis of internet of things (IoT) data and enable shared access to information generated by the analysis. An analytics management service may allow SL entities to configure analytics functions for many different IoT sources of data and organize the results in a customizable manner. The SL may support coordinating the analysis of IoT data from multiple independent sources and organizing the results of the analysis.

Abstract: Methods and apparatuses are described herein for an automated product management (APM) service. An apparatus may receive from a second apparatus, at least one first request to enroll a third apparatus with a service layer associated with the second apparatus. The apparatus may send a second request to verify authenticity of the third apparatus and to generate a customized firmware or software for the third apparatus. The apparatus may send a third request to configure the third apparatus based on consent of a user of the third apparatus. The apparatus may send a response indicating whether the third apparatus has been enrolled with the service layer. The apparatus may receive a fourth request to diagnose or troubleshoot the third apparatus and a fifth request comprising information and the consent and requesting the fourth apparatus to perform at least one operation on the third apparatus.

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: 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: 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: An apparatus can monitor interactions between IoT devices and IoT applications. Based on the monitoring, the apparatus may identify an interaction between a given IoT device and a given IoT application that can be adjusted. In an example, the apparatus may generate a recommendation or instruction in response to identifying the interaction. A first instruction may indicate a change in behavior for one of the IoT device or the IoT application. The apparatus may send the instruction to the one of the IoT device or the IoT application, for example, so as to cause the one of the IoT device or the IoT application to change the respective behavior, thereby adjusting the interaction between the IoT device and the IoT application.

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: A service layer (SL) function may be used for managing a user profile that is associated with a SL user and using this profile to automatically configure different types of devices connected to an IoT service provider's platform. A SL function may be used to support user data privacy and security when data is imported and exported between gateways or servers temporarily.

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.