Abstract: A common Data Analytics Service (DAS) at service layer is designed to use underlying existing/future data analytics technologies or tools and provide them to service layer entities that need those data analytics operations with uniform access approach. A general operation framework/interface design is used for enabling DAS and the operation details within DAS. Related procedures for interacting with DAS, including the new parameters in service layer request/response messages can be used.

Abstract: It is recognized herein that capabilities are lacking related to how different users can be authenticated on top of an existing subscription authentication. In some examples, a user-centric authentication layer may be supported on top of an existing subscription authentication, such that different users may use the same user equipment (UE) with customized services, and different users of devices can be identified behind a gateway with a 3GPP subscription (without the devices having a dedicated 3GPP subscription). Further, a user identifier may be linked to a subscription to access 3GPP services via non-3GPP access.

Abstract: Methods, apparatus, and systems are described for assistance information from the UE to network side, e.g., enabling faster decision-making for secondary cell group deactivation in 3GPP MR DC/CA deployments. According to some aspects, instructions for UE behavior upon MR DC/CA secondary cell group activation are provided in a secondary cell group deactivation message to reduce delays for a UE triggered secondary group activation. RRC signaling ambiguities for conditional PSCell addition/change may be resolved by a synchronization message between a main node and a secondary node to avoid delays and signaling errors.

Abstract: Multicast/Broadcast Service (MBS) for user equipments (UE) in Radio Resource Control (RRC) idle/inactive modes via signally of MBS frequency ranges and/or switching between frequency ranges as required. Bandwidth Part (BWP) operation for MBS in RRC_IDLE and RRC_INACTIVE states may be implemented using a dedicated MBS BWP or by sharing a frequency range with other operations. An MBS frequency range may be wider or narrower than an initial BWP used by a UE, for example. MBS frequency range configure may be achieved in a number of ways, such as via Control Resource Set (CORESET), search space, and/or PDCCH monitoring occasions pattern settings for MBS in RRC idle/inactive. Downlink scheduling without dynamic grant for MBS in RRC idle/inactive may include configured scheduling and/or semi-persistent scheduling.

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: A first apparatus including: a processor; a memory; and communication circuitry. The first apparatus is connected to a communications network via the communication circuitry. The first apparatus further includes computer-executable instructions stored in the memory which, when executed by the processor, causes the first apparatus to: discover a second apparatus that the first apparatus can communicate with; obtain device information related to the second apparatus; and configure a radio protocol of the first apparatus for direct sidelink communication with the second apparatus.

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: Methods and apparatuses are described herein for Multicast/Broadcast Services (MBS). The embodiments described herein are directed to procedures for managing multiplexed MBS traffic, for prioritization between MBS related UL traffic, unicast UL traffic, and SL traffic, for handling HARQ retransmissions over C-RNTI, to support PDCP Status Reporting for MBS services, and for a wireless transmit/receive unit (WTRU) joining already started/activated Multicast Sessions. In one example, a WTRU may receive multiplexed MBS services via one or more MBS radio bearers (MRB) and/or one or more unicast data radio bearers (DRBs). The WTRU may be configured with a single Service Data Adaptation Protocol (SDAP) entity for the MBS services, and demultiplexing of traffic may be performed at the SDAP layer. The WTRU may be configured to demultiplex multiple logical channels across different MBS services, where the logical channels are received over the same transport block.

Abstract: An Authorization Verification Service (AVS) is disclosed that may be provided by an IoT/M2M service layer to registrants of the service layer for Dynamic Context Aware Authorization. The AVS may allow the IoT/M2M service layer entities to define dynamic limits for authorizing access to services or data. The limits may be set, for example, in terms of the number of allowed accesses. When an IoT/M2M registrant makes a request for data or services for which it has dynamic context aware authorization, the AVS may maintain records of the remaining accesses available.

Abstract: A device and method for registering devices on advanced networks as well as providing operative communications between a legacy device and an advanced network. The legacy device may contain data, such as sensor data, which is being collected on a network outside the communication range/abilities of the legacy device. An intermediary device may receive the data via a first communication scheme and send the device to a server collecting the data via a second communication scheme.

Abstract: A network entity, such as a user equipment (UE), may request that a network provide multicast and broadcast services, e.g., where the request includes entity preferences such as network slice selection information. The network may provide information regarding provision of such services, where the information may include, for example, whether a service will be provided via a user plane or a control plane connection, network slice information, additional connections to be formed, separate encryption for such connections, etc. A Multicast/Broadcast Network Function (MBNF) may be used to establish such connections and manage a broadcast and multicast sessions. The MBNF may, for example, manage groups of entities, check an entity's access privileges for services, communicate with the a Management and Network Orchestration (MANO) system to reserve resources, and send data to entities over a shared control plane connection.

Abstract: A Data Producer may be configured to negotiate and initiate a Data Continuity service with an M2M/IoT system. This service may be for specific data sets or all data sets generated by the Data Producer. The M2M/IoT system may be configured to autonomously decide to start a Data Continuity Service for a data set of a Data Producer. The Data Producer may interact directly with an Aggregator SL to store its aggregated data set, and may also be configured to update and delete entries in this data set and start a data service on this aggregated data set. A Local SL may be configured to manage all interactions with an Aggregator SL, and the Local SL may be configured to retarget requests from the Data Producer to the Aggregator SL, including a request to start a data service on the aggregated data set.

Abstract: A method and apparatus for allocating resources to a wireless transmit receive unit (WTRU) includes the WTRU transmitting a signature sequence to a Node B, receiving an acknowledge signal from the Node B, and determining a default resource index. The resource index is associated with enhanced dedicated channel (E-DCH) parameters.

Abstract: A device and method for registering devices on advanced networks as well as providing operative communications between a legacy device and a advanced network. The legacy device may contain data, such as sensor data, which is being collected on a network outside the communication range/abilities of the legacy device. An intermediary device may receive the data via a first communication scheme and send the device to a server collecting the data via a second communication scheme.

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: A method and apparatus for allocating resources to a wireless transmit receive unit (WTRU) includes the WTRU transmitting a signature sequence to a Node B, receiving an acknowledge signal from the Node B, and determining a default resource index. The resource index is associated with enhanced dedicated channel (E-DCH) parameters.

Abstract: A network entity, such as a user equipment (UE), may request that a network provide multicast and broadcast services, e.g., where the request includes entity preferences such as network slice selection information. The network may provide information regarding provision of such services, where the information may include, for example, whether a service will be provided via a user plane or a control plane connection, network slice information, additional connections to be formed, separate encryption for such connections, etc. A Multicast/Broadcast Network Function (MBNF) may be used to establish such connections and manage a broadcast and multicast sessions. The MBNF may, for example, manage groups of entities, check an entity's access privileges for services, communicate with a Management and Network Orchestration (MANO) system to reserve resources, and send data to entities over a shared control plane connection.

Abstract: A common Data Analytics Service (DAS) at service layer is designed to use underlying existing/future data analytics technologies or tools and provide them to service layer entities that need those data analytics operations with uniform access approach. A general operation framework/interface design is used for enabling DAS and the operation details within DAS. Related procedures for interacting with DAS, including the new parameters in service layer request/response messages can be used.

Abstract: A first apparatus includes a processor, a memory, and communication circuitry. The first apparatus is connected to a communications network via its communication circuitry. The first apparatus further includes computer-executable instructions stored in the memory of the first apparatus which, when executed by the processor of the first apparatus, cause the first apparatus to: receive voice content or other biometric content of a user; prepare a message including the voice or other biometric content; send the message to the communications network or a second apparatus through a control plane of the communications network in order to authenticate and authorize the first apparatus and the user; receive a response message from the communications network or the second apparatus, wherein the response message includes authentication and authorization results for the first apparatus and identification information that identifies the user.

Abstract: Radio networks such as Public Land Mobile Networks (PLMNs), user equipment devices (UEs), servers such as Internet-of-Things servers, and core network entities may be adapted to facilitate transfers of connections of wireless devices. For example, a first PLMN may provide restricted access to a UE to assist the UE in finding a second PLMN for a full connection. Entities may be adapted to support for non-coverage related PLMN transfers, such as transfers initiated by UEs, PLMNs, servers, and core network entities, e.g., in response to changing usage, congestion, etc.