Abstract: User equipment (UE) may detect a disaster condition, and the resolution thereof, based on broadcast information, RRC messaging, NAS messaging, the ability to connect to an allowable PLMN, and indications from forbidden PLMNs. In a disaster condition, a UE may perform an enhanced PLMN selection procedure wherein, for example, the UE will not consider PLMNs that are in a disaster situation if the disaster situation applies to a current location of the UE, prioritize forbidden PLMNs for disaster roaming connection. For disaster roaming connection, the UE may be configured by an otherwise forbidden PLMN with information about what services the UE can access and what type of authentication procedure the network is able to perform with UE. Upon detecting that the disaster condition is over, the UE move back to an allowable PLMN.

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: The present application describes a method and apparatus for managing a service in a service layer. In particular, a method describes a computer readable storage medium including instructions for managing a service in a service layer where the instructions are executed by a processor. The executed instructions cause the processor to receive a request to manage, via a service enabler function of the service layer, a change of state of the service including adding, removing, activating, or deactivating the service. The request may include a service description. The executed instructions also cause the processor to evaluate, via the service enabler function, the service description comprising identifiers of one or more services to manage. The executed instructions further cause the processor to identify one or more service capabilities in the service layer to assist in managing the one or more services identified in the service description.

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 system described herein may receive, from a User Equipment (“UE”) via a first network, a request to establish a communication session. The system may determine, based on one or more attributes of the request, that the requested communication session should be established between the UE and a gateway device that is communicatively coupled to a second network. The system may establish, based on the determining, the communication session between the UE and the gateway device. The UE may output communications to the gateway device via the established communication session, and the gateway device may forward the communications received via the communication session to an Internet Protocol (“IP”) Multimedia Subsystem (“IMS”) core of the second network. In this manner, the UE connected to the first network may receive multimedia services provided by the IMS core of the second network.

Abstract: A network device may receive network data identifying core networks supported by the network device and emergency service data identifying one or more of the core networks that support emergency services. The network device may generate, based on the network data and the emergency service data, system information that includes identifiers of the core networks and indicators of whether the core networks support emergency services. The network device may provide the system information to a user equipment to inform the user equipment about which of the core networks support emergency services.

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 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 user equipment (UE) operating in an “Onboarding Mode” may search for a network broadcasting Onboarding Capability Information (OCT), 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 IJE'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 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: 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: System and methods that improve the use of network functions on edge data networks are disclosed. A mechanism that supports edge-assisted UE context and trigger collection is described herein, where a UE can actively send its context information and/or any trigger (e.g. a request for a network function/service to be deployed in edge data networks, etc.) to an edge enabler server, which processes the received context and triggers from its UEs. The edge enabler server may also forward UE context and triggers to 5G core network (5GC) upon receiving a solicitation request from the 5GC, or if the 5GC has already made a subscription for getting notification on UE context and triggers. A network repository function is provided as a new network function collect, store, and manage edge data network information.

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 5G Network Architecture uses virtualization and network slicing. The user equipment (UE) interacts with an underlay network that interacts with virtual network slices. The UE interacts with the underlay network (ULN) to establish a connection to a virtual network slice. Procedures are defined to assign a new slice instance to a UE (UE initiated and ULN initiated); to change a UE Profile (UE initiated and ULN Initiated); and to change a UE's assigned slice instance (ULN Initiated).

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: Methods and apparatus are disclosed for facilitating social discovery and social communication among M2M/IoT devices, connected via cellular networks, such as 3 GPP NR networks, and, optionally, supported by M2M/IoT servers.

Abstract: An M2M Service Layer is expanded to access the services of third parties and exchange data with these third parties. The M2M Service Layer is then able to act as a proxy between M2M Devices and the third party services. The M2M Service Layer is able to present a single/consistent interface, or API, to the M2M Device and hide the details of the third party service provider from the M2M Device.

Abstract: A method and devices may assist in addressing signaling efficiency issues when the network aims to page a group of UEs in a multicast group so that the UEs will switch from CM-IDLE state to CM-CONNECTED state.

Abstract: The present application at least describes an apparatus including a non-transitory memory including instructions stored thereon and a processor, operably coupled to the non-transitory memory, configured to execute as set of instructions. The set of instructions include determining a preference to operate in a reduced capacity (REDCAP) mode in a network. The set of instructions also include transmitting, via a radio resource control (RRC) message to a registration location on the network, a registration request to operate in the REDCAP mode. The registration request prompts a selection of an access and mobility function (AMF) configured to authorize the apparatus to operate in the REDCAP mode and communicate with the apparatus. The registration request prompts a session management function (SMF) to determine characteristics of a protocol data unit (PDU) session of the apparatus.

Abstract: Methods, apparatus, and systems are described for improved discontinuous reception (DRX) for PCS communication (e.g., including unicast, groupcast and broadcast) for a User Equipment (UE) and particularly for reducing the power consumption.