Support for no SUPI or no non-3GPP coverage in 5G mobile communications

Examples pertaining to no subscription permanent identifier (SUPI) or no non-3GPP coverage in 5G mobile communications are described. A processor controls a communication device of a UE to connect to one or more wireless networks and receive one or more 5GS services via a 3GPP access and a non-3GPP access. The processor performs either a first procedure or a second procedure. The first procedure involves: (i) detecting either no Subscriber Identity Module (SIM) being inserted in the UE or a SIM inserted in the UE being invalid; and (ii) entering the UE into a 5G no-SUPI substate responsive to the detecting. The second procedure involves: (i) performing registration or determining that the UE is registered to one or more 5GS services over the non-3GPP access; (ii) detecting an absence of non-3GPP coverage; and (iii) entering the UE into a no access point available substate responsive to the detecting.

TECHNICAL FIELD

The present disclosure is generally related to mobile communications and, more particularly, to support for no subscription permanent identifier (SUPI) or no non-3rd-Generation Partnership Project (non-3GPP) coverage in 5thGeneration (5G) mobile communications.

BACKGROUND

In current 3GPP specification for 5G New Radio (NR) mobile communications, among the substates that are specified some of them are not applicable to non-3GPP access. This means that non-3GPP access can be only in one of the main states such as NULL, DEREGISTERED.NORMAL-SERVICE, DEREGISTERED.ATTEMPTING-REGISTRATION, REGISTERED.NORMAL-SERVICE, 5G MM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE, REGISTERED-INITIATED, DEREGISTERED-INITIATED and SERVICE-REQUEST-INITIATED. While some particular 3GPP access-specific states (e.g., LIMITED-SERVICE, PLMN-SEARCH AND eCALL-INACTIVE) are not available for non-3GPP access, there may be an issue that some of the 5G Mobility Management (5GMM) substates are not available for non-3GPP access under the current 3GPP specification.

SUMMARY

In one aspect, a method may involve a processor controlling a communication device of a user equipment (UE) to connect to one or more wireless networks and receive one or more 5th-Generation System (5GS) services via either a 3GPP access or a non-3GPP access. The method may also involve the processor detecting either no Subscriber Identity Module (SIM) being inserted in the UE or a SIM inserted in the UE being invalid. The method may further involve the processor entering the UE into a 5G no-SUPI substate responsive to the detecting.

In one aspect, a method may involve a processor controlling a communication device of a UE to connect to one or more wireless networks via a 3GPP access and a non-3GPP access. The method may also involve the processor performing registration or determination that the UE is registered the UE to one or more 5GS services over the non-3GPP access. The method may further involve the processor detecting an absence of non-3GPP coverage. The method may additionally involve the processor entering the UE into a no access point available substate responsive to the detecting.

In one aspect, a method may involve a processor controlling a communication device of a UE to connect to one or more wireless networks and receive one or more 5GS services via a 3GPP access and a non-3GPP access. The method may also involve the processor performing either a first procedure or a second procedure. The first procedure may involve: (i) detecting either no SIM being inserted in the UE or a SIM inserted in the UE being invalid; and (ii) entering the UE into a 5G no-SUPI substate responsive to the detecting. The second procedure may involve: (i) performing registration or determination that the UE is registered the UE to one or more 5GS services over the non-3GPP access; (ii) detecting an absence of non-3GPP coverage; and (iii) entering the UE into a no access point available substate responsive to the detecting.

It is noteworthy that, although description provided herein may be in the context of certain radio access technologies, networks and network topologies such as New Radio (NR) or non-3GPP access in 5G system, the proposed concepts, schemes and any variation(s)/derivative(s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies such as, for example and without limitation, Evolved Packet System (EPS), Universal Terrestrial Radio Access Network (UTRAN), Evolved UTRAN (E-UTRAN), Global System for Mobile communications (GSM), General Packet Radio Service (GPRS)/Enhanced Data rates for Global Evolution (EDGE) Radio Access Network (GERAN), Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet-of-Things (IoT) and Narrow Band Internet of Things (NB-IoT). Thus, the scope of the present disclosure is not limited to the examples described herein.

DETAILED DESCRIPTION OF PREFERRED IMPLEMENTATIONS

Overview

FIG. 1illustrates an example network environment100in which various solutions and schemes in accordance with the present disclosure may be implemented. Referring toFIG. 1, network environment100may involve a user equipment (UE)110in wireless communication with a wireless network120(e.g., a 5G NR mobile network) via a base station125(e.g., a gNB or transmit-receive point (TRP)). In network environment100, UE110and wireless network120may implement various schemes pertaining to support for no SUPI and/or no non-3GPP coverage in 5G mobile communications in accordance with the present disclosure. For instance, UE110may connect to one or more wireless networks, including and/or via network120, to receive one or more 5G System (5GS) services via a 3GPP access and a non-3GPP access (e.g., via Wi-Fi in accordance with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specifications). The follow description of various solutions in accordance with the present disclosure is provided with reference toFIG. 1.

Under current 3GPP specification, SUPI, as a 5G subscription permanent identifier, is the identifier for a 5G-capable UE (e.g., UE110) and may be seen as equivalent to international mobile subscriber identifier (IMSI) for 4thGeneration (4G) and legacy UEs. 3GPP access and non-3GPP access are enablers for establishing radio resource control (RRC) connections and non-access stratum (NAS) signaling connections between UE110and a core network. If no universal subscriber identity (USIM) or subscriber identify module (SIM) is present in UE110, or if an inserted USIM/SIM is deemed invalid by UE110, then an appropriate substate would be NO-SUPI. For a non-3GPP 5GMM state machine in UE110, however, it may be problematic for UE110to find a suitable state/substate if the USIM/SIM is considered invalid while NO-SUPI is not applicable. The most suitable state would be the main state 5GMM-NULL. However, under current 3GPP specification, the 5GMM-NULL state would indicate that 5GS services are disabled in UE110, yet this is not the case. Another main state, DEREGISTERED, without additional information would also be ambiguous as it could be interpreted as a state to start initial registration, which cannot be done if UE110has no valid USIM/SIM.

Under a proposed scheme in accordance with the present disclosure, the existing substate 5GMM-DEREGISTERED.NO-SUPI may be modified so that it may be applicable also for non-3GPP 5GMM. Accordingly, it would not be necessary to create a new substate for non-3GPP access. For instance, for 3GPP access, UE110may choose and enter the substate 5GMM-DEREGISTERED.NO-SUPI in an event that UE110has no valid subscriber data available (e.g., due to no USIM/SIM being available or due to the USIM/SIM inserted being considered invalid by UE110) and an access point has been selected for non-3GPP access. Additionally, for non-3GPP access, UE110may choose and enter the substate 5GMM-DEREGISTERED.NO-SUPI in an event that UE110has no valid subscriber data available (e.g., due to no USIM/SIM being available or due to the USIM/SIM inserted being considered invalid by UE110).

Under current 3GPP specification, the 3GPP 5GMM state machine would enter the NO-CELL-AVAILABLE substate after an intensive Public Land Mobile Network (PLMN) search when no 5G cell could be selected or when UE110is operating in a single mode and does intersystem change to S1 mode (e.g., leaving N1 mode behind and remaining REGISTERED in both systems). In an event that 5GS services are enabled and UE110supports non-3GPP access, the non-3GPP 5GMM state machine in UE110should leave the 5GMM-NULL state and start to establish NAS signaling connection and then initiate registration in order to reach REGISTERED state. However, it is not defined in current 3GPP specification as to which state 5GMM should select if there is no non-3GPP coverage. In an event that UE110is registered to 5GS services over a non-3GPP access but non-3GPP coverage is lost, then 5GMM would still be registered (e.g., until non-3GPP deregistration timer in UE110expires). The non-3GPP 5GMM state machine in UE110should leave the state 5GMM-REGISTERED.NORMAL-SERVICE. However, it is also not defined in current 3GPP specification as to which state 5GMM should select.

In the above example scenario, the substate 5GMM-DEREGISTERED.NORMAL-SERVICE would mean, to the non-3GPP 5GMM state machine in UE110, that a cell has been found and initial registration can be performed. However, this is not a sufficient substate if there is no non-3GPP coverage. Similarly, the substate 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION would mean, to the non-3GPP 5GMM state machine in UE110, that there is an initial registration failure due to missing response from network120. However, this is also not a sufficient substate if there is no non-3GPP coverage and initial registration has not been started at all.

Thus, if the non-3GPP 5GMM state machine in UE110cannot enter either of the aforementioned substates due to lack of non-3GPP coverage, UE110would remain in the DEREGISTERED state without additional information. Moreover, for the state machine itself and upper layers, there would remain ambiguity as to whether the non-3GPP state machine is intentionally staying in the DEREGISTERED state (e.g., due to NO-SUPI or due to power saving reasons) or whether UE110is actively looking for service(s).

Under a proposed scheme in accordance with the present disclosure, the existing substates 5GMM-DEREGISTERED.NO-CELL-AVAILABLE and 5GMM-REGISTERED.NO-CELL-AVAILABLE may be modified so that they may be applicable also for the non-3GPP 5GMM. For instance, for 3GPP access, the modified 5G MM-DEREGISTERED.NO-CELL-AVAILABLE substate may indicate that no 5G cell can be selected. UE110may enter this substate after a first intensive search results in failure when in the substate 5GMM-DEREGISTERED.PLMN-SEARCH. UE110may search for one or more cells at a low rhythm, and no 5GS service is offered. Additionally, for 3GPP access, the modified 5GMM-REGISTERED.NO-CELL-AVAILABLE substate may indicate that 5G coverage has been lost or that a Mobile Initiated Connection Only (MICO) mode is active in UE110. In event that MICO mode is active, UE110may deactivate the MICO mode at any time by activating the access stratum (AS) layer when UE110needs to send UE-originated signaling or user data. Otherwise, UE110may not initiate any 5GMM procedure except for cell and PLMN reselection.

Moreover, for non-3GPP access, the 5GMM-DEREGISTERED.NO-CELL-AVAILABLE substate may be renamed as 5GMM-DEREGISTERED.NO-ACCESS-POINT-AVAILABLE. UE110may enter the substate 5GMM-DEREGISTERED.NO-ACCESS-POINT-AVAILABLE when there is either no 5G coverage over non-3GPP access or no non-3GPP 5G access can be selected. In addition, this substate may also indicate that no 5GS service is offered. For example, UE110may enter this substate in an event that N1 mode (including non-3GPP access) is just enabled and UE110can register in non-3GPP access when non-3GPP access becomes available. Furthermore, for non-3GPP access, the 5GMM-REGISTERED.NO-CELL-AVAILABLE substate may be renamed as 5GMM-REGISTERED.NO-ACCESS-POINT-AVAILABLE. UE110may enter the substate 5GMM-REGISTERED.NO-ACCESS-POINT-AVAILABLE when there is either no 5G coverage over non-3GPP access or no non-3GPP 5G access can be selected. For example, in this substate, a non-3GPP deregistration timer may be running as UE110has entered in 5GMM-IDLE mode over the non-3GPP access (e.g., due to non-3GPP coverage being lost). UE110may return to REGISTERED.NORMAL-SERVICE state when UE110is back in non-3GPP coverage.

Under another proposed scheme in accordance with the present disclosure, a new substate corresponding to each of 5GMM-DEREGISTERED.NO-CELL-AVAILABLE and 5GMM-REGISTERED.NO-CELL-AVAILABLE for non-3GPP 5GMM may be defined or otherwise added in the 3GPP specification. For instance, UE110may enter a 5GMM deregistered no non-3GPP coverage (5GMM-DEREGISTERED.NO-N3GPP-COVERAGE) substate, a waiting-for-access (WAITING-FOR-ACCESS) substate, or a no non-3GPP access point available (NO-N3GPP-ACCESS-POINT-AVAILABLE) substate when there is either no 5G coverage over the non-3GPP access or there is no non-3GPP 5G access that can be selected, with no 5GS service offered. Similarly, UE110may enter a 5GMM registered no non-3GPP coverage (5GMM-REGISTERED.NO-N3GPP-COVERAGE) substate, a waiting-for-access (WAITING-FOR-ACCESS) substate, or a no non-3GPP access point available (NO-N3GPP-ACCESS-POINT-AVAILABLE) substate when there is either no 5G coverage over the non-3GPP access or no non-3GPP 5G access can be selected.

Illustrative Implementations

FIG. 2illustrates an example system200having at least an example apparatus210and an example apparatus220in accordance with an implementation of the present disclosure. Each of apparatus210and apparatus220may perform various functions to implement schemes, techniques, processes and methods described herein pertaining to support for no SUPI or no non-3GPP coverage in 5G mobile communications, including the various schemes described above with respect to various proposed designs, concepts, schemes, systems and methods described above, including network environment100, as well as processes300,400and500described below.

Each of apparatus210and apparatus220may be a part of an electronic apparatus, which may be a network apparatus or a UE (e.g., UE110), such as a portable or mobile apparatus, a wearable apparatus, a wireless communication apparatus or a computing apparatus. For instance, each of apparatus210and apparatus220may be implemented in a smartphone, a smart watch, a personal digital assistant, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. Each of apparatus210and apparatus220may also be a part of a machine type apparatus, which may be an IoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a wire communication apparatus or a computing apparatus. For instance, each of apparatus210and apparatus220may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center. When implemented in or as a network apparatus, apparatus210and/or apparatus220may be implemented in an eNodeB in an LTE, LTE-Advanced or LTE-Advanced Pro network or in a gNB or TRP in a 5G network, an NR network or an IoT network.

In some implementations, each of apparatus210and apparatus220may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, or one or more complex-instruction-set-computing (CISC) processors. In the various schemes described above, each of apparatus210and apparatus220may be implemented in or as a network apparatus or a UE. Each of apparatus210and apparatus220may include at least some of those components shown inFIG. 2such as a processor212and a processor222, respectively, for example. Each of apparatus210and apparatus220may further include one or more other components not pertinent to the proposed scheme of the present disclosure (e.g., internal power supply, display device and/or user interface device), and, thus, such component(s) of apparatus210and apparatus220are neither shown inFIG. 2nor described below in the interest of simplicity and brevity.

In some implementations, apparatus210may also include a transceiver216coupled to processor212. Transceiver216may be capable of wirelessly transmitting and receiving data. In some implementations, transceiver216may be capable of wirelessly communicating with different types of wireless networks of different radio access technologies (RATs). In some implementations, transceiver216may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver216may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communications. In some implementations, apparatus220may also include a transceiver226coupled to processor222. Transceiver226may include a transceiver capable of wirelessly transmitting and receiving data. In some implementations, transceiver226may be capable of wirelessly communicating with different types of UEs/wireless networks of different RATs. In some implementations, transceiver226may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver226may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications.

In some implementations, apparatus210may further include a memory214coupled to processor212and capable of being accessed by processor212and storing data therein. In some implementations, apparatus220may further include a memory224coupled to processor222and capable of being accessed by processor222and storing data therein. Each of memory214and memory224may include a type of random-access memory (RAM) such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM) and/or zero-capacitor RAM (Z-RAM). Alternatively, or additionally, each of memory214and memory224may include a type of read-only memory (ROM) such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM) and/or electrically erasable programmable ROM (EEPROM). Alternatively, or additionally, each of memory214and memory224may include a type of non-volatile random-access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM) and/or phase-change memory.

Each of apparatus210and apparatus220may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure. For illustrative purposes and without limitation, a description of capabilities of apparatus210, as a UE, and apparatus220, as a base station of a serving cell of a wireless network (e.g., 5G/NR mobile network), is provided below. It is noteworthy that, although the example implementations described below are provided in the context of a UE, the same may be implemented in and performed by a base station. Thus, although the following description of example implementations pertains to apparatus210as a UE (e.g., UE110), the same is also applicable to apparatus220as a network node or base station such as a gNB, TRP or eNodeB (e.g., network node125) of a wireless network (e.g., wireless network120) such as a 5G NR mobile network.

In one aspect, processor212of apparatus210may control transceiver216to connect to one or more wireless networks (e.g., via apparatus220) and receive one or more 5GS services via either a 3GPP access or a non-3GPP access. Additionally, processor212may detect either no SIM being inserted in apparatus210or a SIM inserted in apparatus210being invalid. Moreover, processor212may enter apparatus210into a 5G no-SUPI substate responsive to the detecting.

In some implementations, in entering apparatus210into the 5G no-SUPI substate, processor212may perform some operations. For instance, processor212may determine that a predefined condition exists. Additionally, processor212may operate apparatus210in a 5GMM deregistered no-SUPI (5GMM-DEREGISTERED.NO-SUPI) substate for the 3GPP access. In such cases, the predefined condition may include: (i) an access point having been selected for the non-3GPP access; and (ii) either apparatus210having no valid subscriber data available or apparatus210having an invalid SIM.

In some implementations, in entering apparatus210into the 5G no-SUPI substate, processor212may perform some operations. For instance, processor212may determine that a predefined condition exists. Moreover, processor212may operate apparatus210in a 5G Mobility Management (5GMM) deregistered no-SUPI (5GMM-DEREGISTERED.NO-SUPI) substate for the non-3GPP access. In such cases, the predefined condition may include either apparatus210having no valid subscriber data available or apparatus210having an invalid SIM.

In another aspect, processor212may control transceiver216to connect to one or more wireless networks via a 3GPP access and a non-3GPP access. Additionally, processor212may register or determine that apparatus210is already registered to one or more 5GS services over the non-3GPP access. Moreover, processor212detecting an absence of non-3GPP coverage. Furthermore, processor212may enter apparatus210into a no access point available substate responsive to the detecting

In some implementations, in an event that apparatus210is not yet registered over the non-3GPP access and is in process of registering, in entering apparatus210into the no access point available substate, processor212may perform certain operations. For instance, processor212may perform, for the non-3GPP access, a search for one or more access points in 5GS which results in failure with no 5G core network available over the non-3GPP access and no 5GS service. Moreover, processor212may enter apparatus210into a 5GMM deregistered no cell available (5GMM-DEREGISTERED.NO-CELL-AVAILABLE) substate for the non-3GPP access.

In some implementations, in entering apparatus210into the no access point available substate, processor212may perform some other operations. For instance, processor212may detect, for the non-3GPP access, that there is no 5G coverage over the non-3GPP access, no non-3GPP 5G access being available for selection, and no 5GS service. Moreover, processor212may enter apparatus210into a 5GMM deregistered no access point available (5GMM-DEREGISTERED.NO-CELL-AVAILABLE) substate for the non-3GPP access. In such cases, in entering apparatus210into the 5GMM deregistered no access point available substate, processor212may enter apparatus210into the 5GMM deregistered no access point available substate in an event that N1 mode is enabled and the processor determines to register apparatus210in the non-3GPP access when the non-3GPP access becomes available.

Alternatively, in entering apparatus210into the no access point available substate, processor212may perform certain operations. For instance, processor212may detect either that 5G coverage has been lost or that a Mobile Initiated Connection Only (MICO) mode is active in apparatus210. Additionally, processor212may enter apparatus210into a 5GMM registered no access point available (5GMM-REGISTERED.NO-CELL-AVAILABLE) substate for the 3GPP access.

Still alternatively, in an event that apparatus210is registered over the non-3GPP access, in entering apparatus210into the no access point available substate, processor212may perform some operations. For instance, processor212may detect either that there is no 5G coverage over the non-3GPP access or that non-3GPP 5G access cannot be selected. Moreover, processor212may enter apparatus210into a 5GMM registered no access point available (5GMM-REGISTERED.NO-CELL-AVAILABLE) substate for the non-3GPP access.

In some implementations, processor212may perform additional operations. For instance, processor212may detect a presence of the non-3GPP coverage. Furthermore, processor212may return apparatus210to a registered normal service (REGISTERED.NORMAL-SERVICE) substate responsive to the detecting of the non-3GPP coverage. In such cases, when in the 5GMM registered no access point available substate, a non-3GPP deregistration timer in apparatus210may be running as apparatus210enters into a 5G Mobility Management (5GMM) idle (5GMM-IDLE) mode over the non-3GPP access.

In some implementations, in entering apparatus210into the no access point available substate, processor212may perform other operations. For instance, processor212may enable 5GS services in apparatus210. Additionally, when registering, processor212may detect no 5GS service and either that there is no 5G coverage over the non-3GPP access or that non-3GPP 5G access cannot be selected. Moreover, processor212may enter apparatus210into a 5GMM deregistered no non-3GPP coverage (5GMM-DEREGISTERED.NO-N3GPP-COVERAGE) substate, a waiting-for-access (WAITING-FOR-ACCESS) substate, a no access point available (5GMM-DEREGISTERED.NO-ACCESS-POINT-AVAILABLE) substate, or a no non-3GPP access point available (NO-N3GPP-ACCESS-POINT-AVAILABLE) substate for the non-3GPP access.

Alternatively, in entering apparatus210into the no access point available substate, processor212may perform certain operations. For instance, when registered, processor212may detect either that there is no 5G coverage over the non-3GPP access or that non-3GPP 5G access cannot be selected. Moreover, processor212may enter apparatus210into a 5GMM registered no non-3GPP coverage (5GMM-REGISTERED.NO-N3GPP-COVERAGE) substate, a waiting-for-access (WAITING-FOR-ACCESS) substate, a no access point available (NO-ACCESS-POINT-AVAILABLE) substate, or a no non-3GPP access point available (NO-N3GPP-ACCESS-POINT-AVAILABLE) substate for the non-3GPP access.

In yet another aspect, processor212of apparatus210may control transceiver216to connect to one or more wireless networks (e.g., via apparatus220) and receive one or more 5GS services via a 3GPP access and a non-3GPP access. Moreover, processor212may perform either a first procedure or a second procedure. The first procedure may involve a number of operations, including: (i) detecting either no SIM being inserted in apparatus210or a SIM inserted in apparatus210being invalid; and (ii) entering apparatus210into a 5G no-SUPI substate responsive to the detecting. The second procedure may involve a number of operations, including: (i) registering or determining that apparatus210is already registered to one or more 5GS services over the non-3GPP access; (ii) detecting an absence of non-3GPP coverage; and (iii) entering apparatus210into a no access point available substate responsive to the detecting.

In some implementations, in entering apparatus210into the 5G no-SUPI substate, processor212may perform some operations. For instance, processor212may determine that a predefined condition exists. Additionally, processor212may operate apparatus210in a 5GMM deregistered no-SUPI (5GMM-DEREGISTERED.NO-SUPI) substate for the 3GPP access. In such cases, the predefined condition may include: (i) an access point having been selected for the non-3GPP access; and (ii) either apparatus210having no valid subscriber data available or apparatus210having an invalid SIM.

In some implementations, in entering apparatus210into the 5G no-SUPI substate, processor212may perform some operations. For instance, processor212may determine that a predefined condition exists. Moreover, processor212may operate apparatus210in a 5GMM deregistered no-SUPI (5GMM-DEREGISTERED.NO-SUPI) substate for the non-3GPP access. In such cases, the predefined condition may include either apparatus210having no valid subscriber data available or apparatus210having an invalid SIM.

In some implementations, in an event that apparatus210is not yet registered over the non-3GPP access and is in process of registering, in entering apparatus210into the no access point available substate, processor212may perform some operations. For instance, processor212may perform, for the non-3GPP access, a search for one or more access points in 5GS which results in failure with no 5G core network available over the non-3GPP access and no 5GS service. Furthermore, processor212may enter apparatus210into a 5GMM deregistered no cell available (5GMM-DEREGISTERED.NO-CELL-AVAILABLE) substate for the non-3GPP access.

In some implementations, in entering apparatus210into the no access point available substate, processor212may perform some operations. For instance, processor212may detect, for the non-3GPP access, that there is no 5G coverage over the non-3GPP access, no non-3GPP 5G access being available for selection, and no 5GS service. Additionally, processor212may enter apparatus210into a 5GMM deregistered no access point available (5GMM-DEREGISTERED.NO-CELL-AVAILABLE) substate for the non-3GPP access. In such cases, in entering apparatus210into the 5GMM deregistered no access point available substate, processor212may enter apparatus210into the 5GMM deregistered no access point available substate in an event that N1 mode is enabled and the processor determines to register apparatus210in the non-3GPP access when the non-3GPP access becomes available.

In some implementations, in entering apparatus210into the no access point available substate, processor212may perform some operations. For instance, processor212may detect either that 5G coverage has been lost or that a MICO mode is active in apparatus210. Moreover, processor212may enter apparatus210into a 5GMM registered no cell available (5GMM-REGISTERED.NO-CELL-AVAILABLE) substate for the 3GPP access.

In some implementations, in an event that apparatus210is registered over the non-3GPP access, in entering apparatus210into the no access point available substate, processor212may perform some operations. For instance, processor212may detect either that there is no 5G coverage over the non-3GPP access or that non-3GPP 5G access cannot be selected. Additionally, processor212may enter apparatus210into a 5GMM registered no access point available (5GMM-REGISTERED.NO-CELL-AVAILABLE) substate for the non-3GPP access. Moreover, processor212may detect a presence of the non-3GPP coverage. Furthermore, processor212may return apparatus210to a registered normal service (REGISTERED.NORMAL-SERVICE) substate responsive to the detecting of the non-3GPP coverage. In such cases, when in the 5GMM registered no access point available substate, a non-3GPP deregistration timer in apparatus210may be running as apparatus210enters into a 5GMM idle (5GMM-IDLE) mode over the non-3GPP access.

In some implementations, in entering apparatus210into the no access point available substate, processor212may perform some operations. For instance, processor212may enable 5GS services in apparatus210. Moreover, when registering, processor212may detect no 5GS service and either that there is no 5G coverage over the non-3GPP access or that non-3GPP 5G access cannot be selected. Furthermore, processor212may enter apparatus210into a 5GMM deregistered no non-3GPP coverage (5GMM-DEREGISTERED.NO-N3GPP-COVERAGE) substate, a waiting-for-access (WAITING-FOR-ACCESS) substate, a no access point available (5GMM-DEREGISTERED.NO-ACCESS-POINT-AVAILABLE) substate, or a no non-3GPP access point available (NO-N3GPP-ACCESS-POINT-AVAILABLE) substate for the non-3GPP access.

In some implementations, in entering apparatus210into the no access point available substate, processor212may perform some operations. For instance, when registered, processor212may detect either that there is no 5G coverage over the non-3GPP access or that non-3GPP 5G access cannot be selected. Additionally, processor212may enter apparatus210into a 5GMM registered no non-3GPP coverage (5GMM-REGISTERED.NO-N3GPP-COVERAGE) substate, a waiting-for-access (WAITING-FOR-ACCESS) substate, a no access point available (NO-ACCESS-POINT-AVAILABLE) substate, or a no non-3GPP access point available (NO-N3GPP-ACCESS-POINT-AVAILABLE) substate for the non-3GPP access.

Illustrative Processes

FIG. 3illustrates an example process300in accordance with an implementation of the present disclosure. Process300may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above, whether partially or entirely, including network environment100. More specifically, process300may represent an aspect of the proposed concepts and schemes pertaining to support for no SUPI or no non-3GPP coverage in 5G mobile communications. Process300may include one or more operations, actions, or functions as illustrated by one or more of blocks310,320and330. Although illustrated as discrete blocks, various blocks of process300may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks/sub-blocks of process300may be executed in the order shown inFIG. 3or, alternatively in a different order. Furthermore, one or more of the blocks/sub-blocks of process300may be executed iteratively. Process300may be implemented by or in apparatus210and apparatus220as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process300is described below in the context of apparatus210as a UE (e.g., UE110) and apparatus220as a network node or base station (e.g., network node125) of a wireless network (e.g., wireless network120). Process300may begin at block310.

At310, process300may involve processor212of apparatus210controlling a communication device (e.g., transceiver216) of apparatus210to connect to one or more wireless networks (e.g., via apparatus220) and receive one or more 5GS services via either a 3GPP access or a non-3GPP access. Process300may proceed from310to320.

At320, process300may involve processor212detecting either no SIM being inserted in apparatus210or a SIM inserted in apparatus210being invalid. Process300may proceed from320to330.

In some implementations, in entering apparatus210into the 5G no-SUPI substate, process300may involve processor212performing some operations. For instance, process300may involve processor212determining that a predefined condition exists. Additionally, process300may involve processor212operating apparatus210in a 5GMM deregistered no-SUPI (5GMM-DEREGISTERED.NO-SUPI) substate for the 3GPP access. In such cases, the predefined condition may include: (i) an access point having been selected for the non-3GPP access; and (ii) either apparatus210having no valid subscriber data available or apparatus210having an invalid SIM.

In some implementations, in entering apparatus210into the 5G no-SUPI substate, process300may involve processor212performing some operations. For instance, process300may involve processor212determining that a predefined condition exists. Moreover, process300may involve processor212operating apparatus210in a 5G Mobility Management (5GMM) deregistered no-SUPI (5GMM-DEREGISTERED.NO-SUPI) substate for the non-3GPP access. In such cases, the predefined condition may include either apparatus210having no valid subscriber data available or apparatus210having an invalid SIM.

FIG. 4illustrates an example process400in accordance with an implementation of the present disclosure. Process400may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above, whether partially or entirely, including network environment100. More specifically, process400may represent an aspect of the proposed concepts and schemes pertaining to support for no SUPI or no non-3GPP coverage in 5G mobile communications. Process400may include one or more operations, actions, or functions as illustrated by one or more of blocks410,420,430and440. Although illustrated as discrete blocks, various blocks of process400may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks/sub-blocks of process400may be executed in the order shown inFIG. 4or, alternatively in a different order. Furthermore, one or more of the blocks/sub-blocks of process400may be executed iteratively. Process400may be implemented by or in apparatus210and apparatus220as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process400is described below in the context of apparatus210as a UE (e.g., UE110) and apparatus220as a network node or base station (e.g., network node125) of a wireless network (e.g., wireless network120). Process400may begin at block410.

At410, process400may involve processor212of apparatus210controlling a communication device (e.g., transceiver216) of apparatus210to connect to one or more wireless networks via a 3GPP access and a non-3GPP access. Process400may proceed from410to420.

At420, process400may involve processor212performing registration or determination that the UE is registered apparatus210to one or more 5GS services over the non-3GPP access. Process400may proceed from420to430.

At440, process400may involve processor212entering apparatus210into a no access point available substate responsive to the detecting

In some implementations, in an event that apparatus210is not yet registered over the non-3GPP access and is performing the registration, in entering apparatus210into the no access point available substate, process400may involve processor212performing certain operations. For instance, process400may involve processor212performing, for the non-3GPP access, a search for one or more access points in 5GS which results in failure with no 5G core network available over the non-3GPP access and no 5GS service. Moreover, process400may involve processor212entering apparatus210into a 5GMM deregistered no cell available (5GMM-DEREGISTERED.NO-CELL-AVAILABLE) substate for the non-3GPP access.

In some implementations, in entering apparatus210into the no access point available substate, process400may involve processor212performing some other operations. For instance, process400may involve processor212detecting, for the non-3GPP access, that there is no 5G coverage over the non-3GPP access, no non-3GPP 5G access being available for selection, and no 5GS service. Moreover, process400may involve processor212entering apparatus210into a 5GMM deregistered no access point available (5GMM-DEREGISTERED.NO-CELL-AVAILABLE) substate for the non-3GPP access. In such cases, in entering apparatus210into the 5GMM deregistered no access point available substate, process400may involve processor212entering apparatus210into the 5GMM deregistered no access point available substate in an event that N1 mode is enabled and the processor determines to register apparatus210in the non-3GPP access when the non-3GPP access becomes available.

Alternatively, in entering apparatus210into the no access point available substate, process400may involve processor212performing certain operations. For instance, process400may involve processor212detecting either that 5G coverage has been lost or that a Mobile Initiated Connection Only (MICO) mode is active in apparatus210. Additionally, process400may involve processor212entering apparatus210into a 5GMM registered no access point available (5GMM-REGISTERED.NO-CELL-AVAILABLE) substate for the 3GPP access.

Still alternatively, in an event that apparatus210is registered over the non-3GPP access, in entering apparatus210into the no access point available substate, process400may involve processor212process400may involve processor212detecting either that there is no 5G coverage over the non-3GPP access or that non-3GPP 5G access cannot be selected. Moreover, process400may involve processor212entering apparatus210into a 5GMM registered no access point available (5GMM-REGISTERED.NO-CELL-AVAILABLE) substate for the non-3GPP access.

In some implementations, process400may involve processor212performing additional operations. For instance, process400may involve processor212detecting a presence of the non-3GPP coverage. Furthermore, process400may involve processor212returning apparatus210to a registered normal service (REGISTERED.NORMAL-SERVICE) substate responsive to the detecting of the non-3GPP coverage. In such cases, when in the 5GMM registered no access point available substate, a non-3GPP deregistration timer in apparatus210may be running as apparatus210enters into a 5G Mobility Management (5GMM) idle (5GMM-IDLE) mode over the non-3GPP access.

In some implementations, in entering apparatus210into the no access point available substate, process400may involve processor212performing other operations. For instance, process400may involve processor212enabling 5GS services in apparatus210. Additionally, when registering, process400may involve processor212detecting no 5GS service and either that there is no 5G coverage over the non-3GPP access or that non-3GPP 5G access cannot be selected. Moreover, process400may involve processor212entering apparatus210into a 5GMM deregistered no non-3GPP coverage (5GMM-DEREGISTERED.NO-N3GPP-COVERAGE) substate, a waiting-for-access (WAITING-FOR-ACCESS) substate, a no access point available (5GMM-DEREGISTERED.NO-ACCESS-POINT-AVAILABLE) substate, or a no non-3GPP access point available (NO-N3GPP-ACCESS-POINT-AVAILABLE) substate for the non-3GPP access.

Alternatively, in entering apparatus210into the no access point available substate, process400may involve processor212performing certain operations. For instance, when registered, process400may involve processor212detecting either that there is no 5G coverage over the non-3GPP access or that non-3GPP 5G access cannot be selected. Moreover, process400may involve processor212entering apparatus210into a 5GMM registered no non-3GPP coverage (5GMM-REGISTERED.NO-N3GPP-COVERAGE) substate, a waiting-for-access (WAITING-FOR-ACCESS) substate, a no access point available (NO-ACCESS-POINT-AVAILABLE) substate, or a no non-3GPP access point available (NO-N3GPP-ACCESS-POINT-AVAILABLE) substate for the non-3GPP access.

FIG. 5illustrates an example process500in accordance with an implementation of the present disclosure. Process500may represent an aspect of implementing various proposed designs, concepts, schemes, systems and methods described above, whether partially or entirely, including network environment100. More specifically, process500may represent an aspect of the proposed concepts and schemes pertaining to support for no SUPI or no non-3GPP coverage in 5G mobile communications. Process500may include one or more operations, actions, or functions as illustrated by one or more of blocks510and520as well as sub-blocks522,524,526,528and530. Although illustrated as discrete blocks, various blocks of process500may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. Moreover, the blocks/sub-blocks of process500may be executed in the order shown inFIG. 5or, alternatively in a different order. Furthermore, one or more of the blocks/sub-blocks of process500may be executed iteratively. Process500may be implemented by or in apparatus210and apparatus220as well as any variations thereof. Solely for illustrative purposes and without limiting the scope, process500is described below in the context of apparatus210as a UE (e.g., UE110) and apparatus220as a network node or base station (e.g., network node125) of a wireless network (e.g., wireless network120). Process500may begin at block510.

At510, process500may involve processor212of apparatus210controlling a communication device (e.g., transceiver216) of apparatus210to connect to one or more wireless networks (e.g., via apparatus220) and receive one or more 5GS services via a 3GPP access and a non-3GPP access. Process500may proceed from510to520.

At520, process500may involve processor212performing either a first procedure or a second procedure. The first procedure may involve a number of operations represented by522and524. The second procedure may involve a number of operations represented by526,528and530.

At522, process500may involve processor212detecting either no SIM being inserted in apparatus210or a SIM inserted in apparatus210being invalid. Process500may proceed from522to524.

At526, process500may involve processor212performing registration or determination that apparatus210is already registered to one or more 5GS services over the non-3GPP access. Process500may proceed from526to528.

At530, process500may involve processor212entering apparatus210into a no access point available substate responsive to the detecting.

In some implementations, in entering apparatus210into the 5G no-SUPI substate, process500may involve processor212performing some operations. For instance, process500may involve processor212determining that a predefined condition exists. Additionally, process500may involve processor212operating apparatus210in a 5GMM deregistered no-SUPI (5GMM-DEREGISTERED.NO-SUPI) substate for the 3GPP access. In such cases, the predefined condition may include: (i) an access point having been selected for the non-3GPP access; and (ii) either apparatus210having no valid subscriber data available or apparatus210having an invalid SIM.

In some implementations, in entering apparatus210into the 5G no-SUPI substate, process500may involve processor212performing some operations. For instance, process500may involve processor212determining that a predefined condition exists. Moreover, process500may involve processor212operating apparatus210in a 5GMM deregistered no-SUPI (5GMM-DEREGISTERED.NO-SUPI) substate for the non-3GPP access. In such cases, the predefined condition may include either apparatus210having no valid subscriber data available or apparatus210having an invalid SIM.

In some implementations, in an event that the apparatus is not yet registered over the non-3GPP access and is performing the registration, in entering apparatus210into the no access point available substate, process500may involve processor212performing some operations. For instance, process500may involve processor212performing, for the non-3GPP access, a search for one or more access points in 5GS which results in failure with no 5G core network available over the non-3GPP access and no 5GS service. Furthermore, process500may involve processor212entering apparatus210into a 5GMM deregistered no cell available (5GMM-DEREGISTERED.NO-CELL-AVAILABLE) substate for the non-3GPP access.

In some implementations, in entering apparatus210into the no access point available substate, process500may involve processor212performing some operations. For instance, process500may involve processor212detecting, for the non-3GPP access, that there is no 5G coverage over the non-3GPP access, no non-3GPP 5G access being available for selection, and no 5GS service. Additionally, process500may involve processor212entering apparatus210into a 5GMM deregistered no access point available (5GMM-DEREGISTERED.NO-CELL-AVAILABLE) substate for the non-3GPP access. In such cases, in entering apparatus210into the 5GMM deregistered no access point available substate, process500may involve processor212entering apparatus210into the 5GMM deregistered no access point available substate in an event that N1 mode is enabled and the processor determines to register apparatus210in the non-3GPP access when the non-3GPP access becomes available.

In some implementations, in entering apparatus210into the no access point available substate, process500may involve processor212performing some operations. For instance, process500may involve processor212detecting either that 5G coverage has been lost or that a MICO mode is active in apparatus210. Moreover, process500may involve processor212entering apparatus210into a 5GMM registered no cell available (5GMM-REGISTERED.NO-CELL-AVAILABLE) substate for the 3GPP access.

In some implementations, in an event that the UE is registered over the non-3GPP access, in entering apparatus210into the no access point available substate, process500may involve processor212performing some operations. For instance, process500may involve processor212detecting either that there is no 5G coverage over the non-3GPP access or that non-3GPP 5G access cannot be selected. Additionally, process500may involve processor212entering apparatus210into a 5GMM registered no access point available (5GMM-REGISTERED.NO-CELL-AVAILABLE) substate for the non-3GPP access. Moreover, process500may involve processor212detecting a presence of the non-3GPP coverage. Furthermore, process500may involve processor212returning apparatus210to a registered normal service (REGISTERED.NORMAL-SERVICE) substate responsive to the detecting of the non-3GPP coverage. In such cases, when in the 5GMM registered no access point available substate, a non-3GPP deregistration timer in apparatus210may be running as apparatus210enters into a 5GMM idle (5GMM-IDLE) mode over the non-3GPP access.

In some implementations, in entering apparatus210into the no access point available substate, process500may involve processor212performing some operations. For instance, process500may involve processor212enabling 5GS services in apparatus210. Moreover, when registering, process500may involve processor212detecting no 5GS service and either that there is no 5G coverage over the non-3GPP access or that non-3GPP 5G access cannot be selected. Furthermore, process500may involve processor212entering apparatus210into a 5GMM deregistered no non-3GPP coverage (5GMM-DEREGISTERED.NO-N3GPP-COVERAGE) substate, a waiting-for-access (WAITING-FOR-ACCESS) substate, a no access point available (5GMM-DEREGISTERED.NO-ACCESS-POINT-AVAILABLE) substate, or a no non-3GPP access point available (NO-N3GPP-ACCESS-POINT-AVAILABLE) substate for the non-3GPP access.

In some implementations, in entering apparatus210into the no access point available substate, process500may involve processor212performing some operations. For instance, when registered, process500may involve processor212detecting either that there is no 5G coverage over the non-3GPP access or that non-3GPP 5G access cannot be selected. Additionally, process500may involve processor212entering apparatus210into a 5GMM registered no non-3GPP coverage (5GMM-REGISTERED.NO-N3GPP-COVERAGE) substate, a waiting-for-access (WAITING-FOR-ACCESS) substate, a no access point available (NO-ACCESS-POINT-AVAILABLE) substate, or a no non-3GPP access point available (NO-N3GPP-ACCESS-POINT-AVAILABLE) substate for the non-3GPP access.

Additional Notes