A network function and a method for associating a UE of a UE group to a PDU session with in a CN. The NF establishes a shared PDU session for the UE group before all of the UEs in the UE group register with the CN and binds a UE that has not yet registered with the CN to the shared PDU session when the UE registers with the CN, provided the UE will share at least one of a UL UP connection and a DL UP connection associated with the shared PDU session. The NF may be an SMF.

A network function and a method for associating a UE of a UE group to a PDU session with in a CN. The NF establishes a shared PDU session for the UE group before all of the UEs in the UE group register with the CN and binds a UE that has not yet registered with the CN to the shared PDU session when the UE registers with the CN, provided the UE will share at least one of a UL UP connection and a DL UP connection associated with the shared PDU session. The NF may be an SMF.

Various techniques are described herein for autonomously registering and/or activating Internet-of-Things (IoT) devices, provisioning wireless network access of those devices, and connecting the IoT device to an NB-IoT network with agreed-to terms for network usage. In various embodiments, IoT devices may be configured to negotiate for NB-IoT network access by (i) sharing their data with the NB-IoT network provider, (ii) security storing and using cryptocurrency to obtain NB-IoT network access, and/or (iii) automatically providing the NB-IoT network provider with access to data from other associated IoT devices and/or with payment from a separate payment provider. Individual IoT devices may be preconfigured with negotiation terms for NB-IoT network access, pre-associated with other devices/users, and/or pre-loaded with cryptocurrency in a secure storage.

Methods, systems, and storage media are described for the utilization of user equipment (UE) identifiers for registration in fifth generation (5G) systems. An apparatus of a user equipment includes processing circuitry to: retrieve a first 5G-GUTI from a memory; generate a registration request message that includes the first 5G-GUTI; encode the registration request message for transmission to a fifth-generation core (5GC) network of a second PLMN; receive a registration accept message that includes a second 5G-GUTI; and access the second PLMN using the second 5G-GUTI.

Methods, systems, and storage media are described for the utilization of user equipment (UE) identifiers for registration in fifth generation (5G) systems. An apparatus of a user equipment includes processing circuitry to: retrieve a first 5G-GUTI from a memory; generate a registration request message that includes the first 5G-GUTI; encode the registration request message for transmission to a fifth-generation core (5GC) network of a second PLMN; receive a registration accept message that includes a second 5G-GUTI; and access the second PLMN using the second 5G-GUTI.

Apparatuses, methods, and systems are disclosed for determining mobile network policy freshness. One method includes accessing a first policy associated with a first mobile network, a first policy identifier, and a freshness parameter. The method includes determining, based on the freshness parameter, whether the first policy is fresh. The method includes transmitting a registration message to a second mobile network. The registration message includes the first policy identifier in response to determining that the first policy is not fresh.

Electronic subscriber identity modules (eSIM) can be more susceptible to hackers and more vulnerable than physical subscriber identity modules. The current disclosure discusses systems and methods to facilitate eSIM security by utilizing a management software application (MSA) hosted on a mobile device. This MSA can cross-reference eSIM registration data with mobile device signature data to determine if the correct user identity is associated with mobile device prior to an eSIM being issued to the mobile device. Additionally, various degrees of data flagging can be utilized to allow an end user to properly address an indication of mobile device vulnerability.

Electronic subscriber identity modules (eSIM) can be more susceptible to hackers and more vulnerable than physical subscriber identity modules. The current disclosure discusses systems and methods to facilitate eSIM security by utilizing a management software application (MSA) hosted on a mobile device. This MSA can cross-reference eSIM registration data with mobile device signature data to determine if the correct user identity is associated with mobile device prior to an eSIM being issued to the mobile device. Additionally, various degrees of data flagging can be utilized to allow an end user to properly address an indication of mobile device vulnerability.

A method of a network function (NF) entity performing communication in a wireless communication system includes: in case that a first registration request of a user equipment (UE) for a slice is received at an access and mobility function (AMF) entity through a first network, receiving a first slice availability request message for the slice from the AMF entity; determining whether the slice is available for the UE, based on a network slice policy; and transmitting, to the AMF entity, a response message including information regarding slice availability of the UE according to the first registration request, wherein in case that a second registration request of the UE for the slice is received at the AMF entity through a second network, slice availability of the UE according to the second registration request is determined based on at least one of the network slice policy or the information regarding the slice availability of the UE according to the first registration request.

An interworking service entity receives server registration requests including indications of service layer protocols used by each server, maintains a repository of server information, and uses the repository for interworking requests of devices to servers of different protocols based on a server type provided in discovery requests. Other matching information may include, for example, server security protocol, supported services, service territory, availability, capacity, or loading, as device information or preferences, such a supported service, supported interface type, or a supported device type.