Abstract: Profile based services and content can assist with the backward and forward compatibility of conventional service layers or the like. Using a profile to manage content and access to services offered may reduce the overhead or processing associated with providing those value added services by service layers.

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.

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 and apparatuses are described herein for a 5G system that deploys services providing optimizations and value add services based on delay tolerant data (DTD) exchanges between end devices and machine to machine (M2M) servers. In accordance with one embodiment, an apparatus may receive, from a second apparatus via the network, first information comprising a delay tolerant communication configuration comprising an identifier and a delay tolerant characteristic. The apparatus may receive, from a third apparatus, data in a plurality of data bundles that each comprises the identifier. The apparatus may process, based on the first information, the plurality of data bundles. The apparatus may route, based on the first information, the plurality of data bundles. The third apparatus may comprise a user equipment (UE).

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: Methods and devices may be provided for aggregating component carriers in the licensed spectrum with at least one component carriers in the licensed exempt spectrum. Control information may be processed in a wireless transmit/receive unit (WTRU) while receiving and sending information on a primary component carrier (PCC) and a supplementary component carrier (SuppCC). A PCC subframe with a control portion and a data portion may be received. Resource assignment information associated with a downlink shared channel on the PCC may be embedded in the control portion of the subframe. Based on the resource assignment information on the PCC, resource assignment information associated with a downlink shared channel on the SuppCC may be identified in the data portion of the PCC subframe. A SuppCC subframe of the shared channel on the SuppCC may be processed as per the identified resource assignment information associated with the downlink shared channel on the SuppCC.

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.

Abstract: The application is at least directed to a core network including a non-transitory memory having instructions stored thereon for registering a network function or network function template in the core network. The network includes a processor, operably coupled to the non-transitory memory. The processor is configured to perform the instruction of determining that registration of the network function or network function template is acceptable. The processor is also configured to perform the instruction of transmitting a message including the network function or network function template to a repository in the core network. The processor is also configured to perform the instruction of verifying the network function or network function template against existing policies in the core network. The processor is also configured to perform the instruction of registering the network function or network function template in the repository after verification.

Abstract: A network node may be configured to receive a request for an authentication and key establishment procedure from a machine to machine (M2M) device. The network node may be configured to determine a key agreement between the network node and the M2M device using the authentication and key establishment procedure. The network node may be configured to receive a request from an M2M server for the key agreement to be used to communicate with the M2M device. The network node may be configured to send the key agreement to the M2M server.

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 batch of CRUD operations can be coupled with the resource discovery operation and directly conducted on the matched resources, without initiating new CRUD requests. New functionality at the Originator and Receiver can differentiate the resources for which criteria matching is applied from the resources included in the discovery/filtering results. Enhanced functionality at the Originator and Receiver can combine discovery with RESTful operations targeting a resource set different than but related the discovered resources. Other enhancements may be used to request discovery of resources in a specified relationship to those matching a filter, or to request group formation based on the result.

Abstract: Profile based services and content can assist with the backward and forward compatibility of conventional service layers or the like. Using a profile to manage content and access to services offered may reduce the overhead or processing associated with providing those value added services by service layers.

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: 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: 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: Methods are described for enabling 5G MBS operation. The disclosed methods overcome limitations in LTE and UTRAN MBMS operation, address the unique characteristic of 5G NR, and meet requirements of 5G MBS use cases. Disclosed are techniques for MCCH configuration procedures, including change notification procedures; triggers for MCCH acquisition; a RAN paging procedure for triggering counting for UEs in RRC INACTIVE; triggers for an MBS interest indication based on BWP switching; a timescale for scheduling of an MRB transport channel, a signal control channel, and a traffic channel; procedures for scheduling MCCH, including a scheduling configuration, an SCS, and a BWP; procedures for scheduling (P)TrCH; and procedures for scheduling MTCH.

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: 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: A set of point-of-contact information including a service level identifier, an address, a list of interfaces, and a set of interface selection preferences for each of several entities may be used to facilitate communications among the entities by selecting a preferred interface in accordance with the set. Interface preferences may also be derived from a set of policies. The preferred interface may be resolved in accordance with the preferences of multiple entities. Messages may include an interface type parameter to be used for forwarding of the message, and message forwarding may be resolved in accordance with the parameter and the messages.

Abstract: Methods and apparatus are disclosed for integrating NF discovery and application layer service capability discovery in a communications network, such as the 3GPP NR (e.g., 5G) network.