Patent Description:
The present disclosure relates generally to communication systems, and more particularly, to enabling <NUM> New Radio (NR) based services through use of a universal integrated circuit card (UICC) that does not fully independently support <NUM> NR based services.

These multiple radio access technologies (RATs) have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level.

Further, while access to services in an LTE based network was associated with a user equipment (UE) international mobile subscriber identity (IMSI), services in a <NUM> NR based network are associated with a UE Subscription Permanent Identifier (SUPI). The SUPI may be further modified to generate a Subscription Concealed Identifier (SUCI) while contains a concealed SUPI. As such, there is a need to enable UEs to access <NUM> NR based services while still being supported by pre-<NUM> based UICCs. <CIT> discloses a method for transmitting to a physical or virtual element of a telecommunications network an encrypted subscription identifier stored in a security element, characterized in that it consists in pre-calculating proactively at the occurrence of an event the encrypted identifier using a key and storing it in a file or memory of the security element with a parameter enabling the key to be calculated by the element of the telecommunications network in order to be able to transmit to the element of the telecommunications network the encrypted identifier and the parameter, without having to compute the encrypted identifier when the terminal is asking for it. <CIT> discloses a method of operating a first network node, the method comprising:.

Accordingly, in one or more example aspects, the functions described may be implemented in hardware, software, or any combination thereof.

A network that includes both small cell and macro cells may be known as a heterogeneous network. The base stations <NUM> / UEs <NUM> may use spectrum up to Y MHz (e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM>) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or less carriers may be allocated for DL than for UL).

The MBMS Gateway <NUM> may be used to distribute MBMS traffic to the base stations <NUM> belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start/stop) and for collecting eMBMS related charging information.

The base station may also be referred to as a gNB, Node B, evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), or some other suitable terminology. The base station <NUM> provides an access point to the EPC <NUM> for a UE <NUM>. Examples of UEs <NUM> include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a toaster, or any other similar functioning device. Some of the UEs <NUM> may be referred to as loT devices (e.g., parking meter, gas pump, toaster, vehicles, etc.).

Referring again to <FIG>, in certain aspects, the UE <NUM> may include a concealed identifier component <NUM>. Initially, although the following description may be focused towards enabling access to <NUM> NR based services for a UE <NUM> that may not have a fully enabled <NUM> NR based UICC, the concepts described herein may be applicable to any situation in which an UICC installed in a UE is not fully compatible with services available from a network from which the UE intends to receive services. In an aspect, concealed identifier component <NUM> may enable UE <NUM> to generate a concealed identifier to assist the UE <NUM> with accessing services. For example, the services may be <NUM> NR based services. As used herein, services may refer to any activities that use a concealed identifier for the UE <NUM> when interacting with the network (e.g., <NUM> NR based network). In an aspect, a UE <NUM> may have a Subscription Unit Permanent Identifier (SUPI) that uniquely identifies the UE <NUM> in the network. In such an aspect, concealed identifier component <NUM> may be used by UE <NUM> to generate a SUCI from the SUPI for <NUM> and pre-<NUM> cards (e.g., UICCs) on <NUM> devices (e.g., UE <NUM>) even if UICC does not fully support <NUM> services.

In an operational aspect, a UE <NUM> may use information, such as but not limited to, a protection scheme identifier (e.g., ECIES A, ECIES B, Proprietary, etc.), a Home Network (HN) public key, a routing indicator (RI) to assist with enabling access to services (e.g., <NUM> NR based services). Such information may be stored in memory such as a Secure File System (SFS), in software, etc. Further, in the operational aspect, where a card (e.g., UICC) associated with the UE <NUM> is a pre-<NUM> based card, concealed identifier component <NUM> may prompt the UE <NUM> to read the information (e.g., protection scheme, HN public key, RI, etc.) from the memory (e.g., Secure File System, software, etc.). Additionally, or in an alternative operational aspect, where a card (e.g., UICC) associated with the UE <NUM> is <NUM> based card, concealed identifier component <NUM> may prompt the UE <NUM> to read parameters from elementary files (e.g., EF-Suci_Calc_Info, EF-RI, etc.) based on service availability in the <NUM> based card. If the <NUM> based card supports SUCI calculation, then a GET_IDENTITY request may be sent to the <NUM> based card to obtain the SUCI. In an aspect, the SUCI may be used for a registration procedure to camp on a <NUM> NR based network, thereby allowing access to <NUM> NR services.

<FIG> is a component block diagram of a wireless communication device <NUM> suitable for implementing various aspects. With reference to <FIG> and <FIG>, in various aspects, the wireless communication device <NUM> may be similar to the wireless communication device <NUM>. The wireless communication device <NUM> may include a subscriber identity module (SIM) interface <NUM>, which may receive an identity module SIM <NUM> that is associated with a subscription.

A SIM in various aspects may be a UICC that is configured with SIM and/or USIM (Universal Subscriber Identity Module) applications, enabling access to, for example, wireless communication networks. The UICC may also provide storage for a phone book and other applications. A SIM used in various aspects may contain user account information, an international mobile subscriber identity (IMSI), a set of SIM application toolkit (SAT) commands and storage space. A SIM card may further store a Home-Public-Land-Mobile-Network (HPLMN) code to indicate the SIM card network operator provider. An Integrated Circuit Card Identity (ICCID) SIM serial number may be printed on the SIM card for identification. The SIM may be an embedded SIM (e.g., a UICC) that is permanently embedded in a communication device.

The wireless communication device <NUM> may include at least one controller, such as a general-purpose processor <NUM>, which may be coupled to a coder/decoder (CODEC) <NUM>. The CODEC <NUM> may in turn be coupled to a speaker <NUM> and a microphone <NUM>. The general-purpose processor <NUM> may also be coupled to at least one memory <NUM>. The memory <NUM> may be a non-transitory computer-readable storage medium that stores processor-executable instructions. For example, the instructions may include routing communication data relating to the first or second subscription through a corresponding baseband-RF resource chain. The memory <NUM> may store an operating system, as well as application software and executable instructions. The memory <NUM> may also store application data.

The general-purpose processor <NUM> may be coupled to a modem <NUM>. The modem <NUM> may include at least one baseband modem processor <NUM>, which may be coupled to a memory <NUM> and a modulator/demodulator <NUM>. The baseband modem processor <NUM> may include physically or logically separate baseband modem processors. The modulator/demodulator <NUM> may receive data from the baseband modem processor <NUM> and may modulate a carrier signal with encoded data and provide the modulated signal to an RF resource <NUM> for transmission. The modulator/demodulator <NUM> may also extract an information-bearing signal from a modulated carrier wave received from an RF resource <NUM>, and may provide the demodulated signal to the baseband modem processor <NUM>. The modulator/demodulator <NUM> may be or include a digital signal processor (DSP).

The baseband modem processor <NUM> may read and write information to and from the memory <NUM>. The memory <NUM> may also store instructions associated with a protocol stack, such as a protocol stack. A protocol stack generally includes computer executable instructions to enable communication using a radio access protocol or communication protocol. The protocol stack typically includes network protocol layers structured hierarchically to provide networking capabilities. A protocol stack may be associated with the SIM card <NUM> (e.g., a UICC) and/or a subscription. For example, the protocol stack may be associated with the SIM <NUM>. The memory <NUM> may store one or more protocol stacks (not illustrated).

The SIM <NUM> in the wireless communication device <NUM> may be coupled to the modem <NUM> and may be associated with or permitted to use at least one RF resource chain per RAT. A RAT (e.g., an LTE RAT, <NUM> NR RAT) may be associated with RF resource <NUM>. Wireless communication device <NUM> may operate and communicate with SIM <NUM> via SIM interface <NUM>. The SIM interface <NUM> may communicate with SIM <NUM> using a plurality of input and output lines matched to pins on SIM <NUM>. SIM interface <NUM> may operate SIM <NUM> using a plurality of input lines including, but not limited to, a voltage line, a reset line, a clock line, a ground line, and a data line. The SIM interface <NUM> may also receive output from SIM <NUM> via a plurality of output lines including, but not limited to, a voltage line, a clock line, a ground line, and a data line.

Each baseband-RF resource chain may include the baseband modem processor <NUM> to perform baseband/modem functions for communicating with/controlling a RAT, and one or more amplifiers and radios, referred to generally herein as RF resources. In some aspects, baseband-RF resource chains may share a common baseband modem processor <NUM> (i.e., a single device that performs baseband/modem functions for all RATs on the wireless communication device). Alternatively, each baseband-RF resource chain may include the physically or logically separate baseband processors.

The RF resources <NUM> may include transceivers associated with one or more RATs and may perform transmit/receive functions for the wireless communication device <NUM> on behalf of their respective RATs. The RF resources <NUM> may include separate transmit and receive circuitry. The RF resources <NUM> may be coupled to a wireless antenna (e.g., a wireless antenna <NUM>). The RF resources <NUM> may also be coupled to the modem <NUM> (e.g., via the modulator/demodulator <NUM>, or alternatively via the baseband modem processor <NUM> or another component). The term "RF resource chain" may include an RF resource (e.g., the RF resource <NUM>), an antenna (e.g., the antenna <NUM>), and one or more components of the modem <NUM>.

In some aspects, the general-purpose processor <NUM>, memory <NUM>, baseband processor(s) <NUM>, and RF resource <NUM> may be included in the wireless communication device <NUM> as a system-on-chip. Conversely, the general-purpose processor <NUM>, memory <NUM>, baseband processor(s) <NUM>, and RF resource <NUM> may be the packaged as separate components in a device. SIM <NUM> and corresponding interface <NUM> may be external to the system-on-chip. Further, various input and output devices may be coupled to components on the system-on-chip, such as interfaces or controllers. The wireless device <NUM> may or may not include input components such as, but not limited to, a keypad <NUM>, data source <NUM>, and/or a touchscreen display <NUM>. Data source <NUM> may be a sensor, appliance, or any device capable of providing data to the wireless communication device.

In some aspects, the keypad <NUM>, touchscreen display <NUM>, data source <NUM>, microphone <NUM>, or a combination thereof, may perform the function of receiving the request to initiate an outgoing communication. For example, the touchscreen display <NUM>, keypad <NUM>, or microphone <NUM> may function to initiate an outgoing communication. As another example, the request to initiate the outgoing communication may be user driven or device driven (i.e., algorithmically driven). Interfaces may be provided between the various software modules and functions in the wireless communication device <NUM> to enable communication between them.

Layer <NUM> includes a RRC layer, and layer <NUM> includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer.

<FIG> is a diagram illustrating an example wireless communications system <NUM> with a UE <NUM> that may communicate with one or more base stations (<NUM>, <NUM>) using one or more RATs (<NUM>, <NUM>). In an aspect, UE <NUM> may be camped on a cell associated with a RAT (e.g., LTE, <NUM>, <NUM>, EV-DO, etc.). For example, UE <NUM> may be camped on a <NUM> cell (e.g., communicating with base station <NUM> using RAT <NUM>). Further, services may be available through another RAT (e.g., <NUM>, LTE, etc.). For example, to be able to access services available through a <NUM> RAT, the UE <NUM> may camp on a <NUM> RAT (e.g., communicating with base station <NUM> using RAT <NUM>) using concealed identifier generated by the UE <NUM>.

UE <NUM> may include pre-<NUM> identifier card component <NUM> and/or, in an optional aspect, <NUM> identifier card component <NUM> which may enable UE <NUM> to access services from a RAT (e.g., <NUM> NR based RAT) while using a concealed identifier (e.g., SUCI). In an aspect, pre-<NUM> identifier card component <NUM> may include information, such as but not limited to, SUCI calculation information <NUM>, routing indicator <NUM>, and IMSI based information <NUM>. In an aspect, SUCI calculation information <NUM> may include EFs used by UE <NUM> for support of subscribe identity privacy. For example, SUCI calculation information <NUM> may include parameters such as, but not limited to, a Protection Scheme Identifier <NUM>, Home Network Public Key <NUM>, etc., which may be used in calculating the SUCI. Further, routing indicator <NUM> may be obtained from an EF (e.g., EF-RI). As it is described in further depth with reference to <FIG> and <FIG>, routing indicator <NUM>, and IMSI based information <NUM> may also be used by pre-<NUM> identifier card component <NUM> in calculating the SUCI. IMSI based information <NUM> may include values, such as but not limited to, mobile country codes (MCC), Mobile Network Code (MNC), mobile subscription identification number (MSIN), etc. In an operational aspect, pre-<NUM> identifier card component <NUM> may calculate a SUCI based on Protection Scheme Identifier <NUM> and Home Network Public Key <NUM> from SUCI calculation information <NUM>, routing indicator <NUM>, and MCC, MNC, and MSIN from IMSI based information <NUM>.

As noted above, in an optional aspect, UE <NUM> may include <NUM> identifier card component <NUM> which may include elementary files (EFs) <NUM>. In an aspect, EFs <NUM> may be defined in a service table. For example, the service table and EFs may be EFUST (USIM Service Table) Service Numbers <NUM> (Service n<NUM><NUM>) and/or <NUM> (Service n<NUM><NUM>) as defined in 3GPP TS <NUM> Section <NUM>. <NUM> Release <NUM>. Service <NUM> indicates whether Subscriber Identity Privacy Support is available, and Service <NUM> indicates whether SUCI calculation by the USIM is available. In an operational aspect, where UE <NUM> includes <NUM> identifier card component <NUM>, a request may be made to determine whether Service No. <NUM> and <NUM> are available. Where <NUM> identifier card component <NUM> indicates that both of these service number values are available, the UE may generate its own SUCI value using the UICC. Where <NUM> identifier card component <NUM> indicates that Service No. <NUM> is available, but Service No. <NUM> is not available or unable to be obtained, then UE <NUM> may calculate the SUCI with further assistance from information obtained from pre-<NUM> identifier card component <NUM>.

<FIG> is a flowchart <NUM> of a method of wireless communication, according to the claimed invention. The method is performed by a UE (e.g., UE <NUM>, UE <NUM>). In an optional aspect, at <NUM>, the UE may be pre-configured with information sufficient to generate a concealed identifier. The information sufficient to generate the concealed identifier may assist the UE with generating a SUCI to enable the UE to access services from a RAT (e.g., <NUM> RAT) that may use different UE identifying parameters than may be available through a UICC associated with the UE. Such pre-configuring may be done through over-the-air updates, at initial activation, based on user input, etc. As noted above, services may refer to any activities that use a concealed identifier for the UE when interacting with the network (e.g., a <NUM> registration procedure). As also noted above, the concealed identifier information may be stored in memory such as a SFS, in software, etc. In an aspect, UE <NUM> Pre-<NUM> identifier card component <NUM> may be pre-configured with information sufficient to generate the concealed identifier such as described at <NUM>.

At <NUM>, the UE determines whether initial subscriber information available from the UICC is sufficient to enable calculate a concealed identifier (e.g., SUCI). In an aspect, where the UE is attempting to camp on a <NUM> based network, the UE use a SUCI during the registration procedure. In such an aspect, if the UE has a <NUM> enabled UICC, then information available from the UICC (e.g., EFs, parameters associated with EFs, etc.) may sufficient to calculate the SUCI. By contrast, if the UE has a pre-<NUM> enabled UICC, then information available from the UICC alone may not be sufficient to calculate the SUCI. In an aspect, UE <NUM> pre-<NUM> identifier card component <NUM> and/or <NUM> identifier card component <NUM> may be configured to determine whether initial subscriber information available from the UICC is sufficient to calculate a concealed identifier (e.g., SUCI) as described at <NUM>.

If, at <NUM>, the UE determines that there is sufficient initial subscriber information available from the UICC to calculate a concealed identifier (e.g., SUCI), then the UE may attempt to calculate the SUCI, and at <NUM>, the UE determines whether the SUCI was successfully calculated. In an aspect, where the UE has been configured with a <NUM> enabled UICC, the UE may use initial subscriber information available through the <NUM> enabled UICC (e.g., EFUST (USIM Service Table) Service Numbers <NUM> (Service n<NUM><NUM>) and/or <NUM> (Service n<NUM><NUM>) as defined in 3GPP TS <NUM> Section <NUM>. <NUM> Release <NUM>). In an aspect, UE <NUM><NUM> identifier card component <NUM> may be configured to determine whether the SUCI has been successfully calculated as described at <NUM>. If at <NUM>, the UE determines that the SUCI was successfully calculated, then the process may end.

If, at <NUM>, the UE determines that there is not sufficient initial subscriber information available from the UICC to calculate the SUCI, or if, at <NUM>, the UE determines that the SUCI was not successfully calculated then, at <NUM>, the UE obtains additional subscriber information from secure storage. In an aspect, the additional subscriber information may be the pre-configured secure connectivity information noted at <NUM>. In an aspect, the additional subscriber information may be IMSI based information, such as but not limited to, MCC, MNC, and MSIN. In another aspect, the additional subscriber information may further include a protection scheme identifier (e.g., ECIES A, ECIES B, Proprietary, etc.), a HN public key, a RI, etc. In an aspect, UE <NUM> pre-<NUM> identifier card component <NUM> and/or <NUM> identifier card component <NUM> may be configured to obtain additional subscriber information as described at <NUM>.

At <NUM>, the UE generates a SUCI based on the initial subscriber information along with the additional subscriber information. In an aspect, the UE may calculate the SUCI based on information (additional and/or initial), such as but not limited to, Protection Scheme Identifier, Home Network Public Key, routing indicator, MCC, MNC, MSIN, etc. In an aspect, UE <NUM> pre-<NUM> identifier card component <NUM> may generate a SUCI based on the initial subscriber information along with the additional subscriber information as describe at <NUM>.

<FIG> is another flowchart <NUM> of a method of wireless communication, which is not according to the claimed invention. The method may be performed by a UE (e.g., UE <NUM>, UE <NUM>). Although the describe provided with respect to <FIG> focuses on a <NUM>-centric aspect, the process may be applicable to other RAT implementations. Further, UE <NUM> and at least one of pre-<NUM> identifier card component <NUM>, <NUM> identifier card component <NUM>, or any combination thereof, may be configured to perform steps <NUM> through <NUM>.

At <NUM>, the UE may be pre-configured with EFs that may assist with calculation of a SUCI. In an aspect, the EFs may be EFSUCI_Calc_Info as described in 3GPP TS <NUM> Section <NUM>. <NUM>, Release <NUM>. For example, the EFs may include parameters, such as but not limited to, a protection scheme identifier (e.g., ECIES A, ECIES B, Proprietary, etc.), a HN public key, a RI, etc. The EFs may be stored in memory such as a SFS, in software, etc. In an aspect, whether the stored pre-configured information is used by the UE to calculate the SUCI may be based, at least in part, on a type of card (e.g., UICC) the UE has installed.

If, at <NUM>, the UE is configured with a fully enabled <NUM> UICC, then at <NUM> a GET IDENTITY request may be sent to the UICC to obtain information used to calculate the SUCI. In an aspect, a UICC may be a fully enabled <NUM> UICC when both Service No. <NUM> and Service No. <NUM> are available. Further, if, at <NUM>, the UICC returns the proper requested information and a SUCI is generated, then at <NUM> the UE may camp on a <NUM> based cell and may access <NUM> based services using the generated SUCI.

If, at <NUM>, the UE in configured with a partially enabled <NUM> UICC, then the UE may determine what information may be able to be obtained from the UICC. For example, a UICC may be a partially enabled <NUM> UICC where some information used to generate the SUCI is present on the UICC but other information may be available from memory (e.g., SFS) on the UE.

At <NUM>, the UE determines whether EFs (e.g., EF_Suci_Calc_Info) used to calculate the SUCI may be obtained from the UICC (e.g., determine whether Service No. <NUM> is available). If at <NUM>, the UE determines that the EFs used to calculate the SUCI may be obtained from the UICC, the UE may, at <NUM>, determine whether a protection schemed used as part of the SUCI generation is a default (e.g., ECIES A, ECIES B) or a proprietary scheme. If at <NUM>, the UE determines that a default protection scheme is to be used, the UE may, at <NUM> determine whether a HN public key is available from the UICC. If at <NUM>, the HN public key is available from the UICC, then at <NUM> the UE may obtain information (e.g., EF_Suci_Calc_info from <NUM>, default protection scheme from <NUM>, HN public key from <NUM>) for the UICC to assist in generating the SUCI.

Further, if the UE, at <NUM>, determines that the EFs used to calculate the SUCI may not be obtained from the UICC, or if the UE, at <NUM>, determines that a proprietary protection scheme may be used to calculate the SUCI, or if the UE, at <NUM>, determines that HN public key is not available from the UICC, or if at <NUM>, the UE is configured with a pre-<NUM> UICC, or if at <NUM>, the UICC does not return the proper requested information and a SUCI may not be generated, then at <NUM>, the UE may retrieve information used to assist with generating the SUCI from memory (e.g., SFS) on the UE.

At <NUM>, the UE may organize the information used to generate the SUCI, obtained from the UICC and/or from memory on the UE, and at <NUM>, the UE may calculate the SUCI. Thereafter, at <NUM> the UE may camp on a <NUM> based cell and may access <NUM> based services using the generated SUCI.

<FIG> is a conceptual data flow diagram <NUM> illustrating the data flow between different means/components in an exemplary apparatus <NUM>. The apparatus may be a UE. The apparatus includes a reception component <NUM> that may receive information <NUM> (e.g., pre-configured information to assist with SUCI generation) from the network <NUM>, secure storage component <NUM> that may be configured to store the information <NUM> in a secure manner, a network connectivity component <NUM> that may enable UE <NUM> to generate a SUCI <NUM> based at least in part on information stored in UICC <NUM> and information <NUM> obtained from secure storage component <NUM> is to be received via unicast or broadcast transmission, and a transmission component <NUM> to enable to UE <NUM> to use the SUCI <NUM> as part of accessing services.

<FIG> is a diagram <NUM> illustrating an example of a hardware implementation for an apparatus <NUM>' employing a processing system <NUM>. The processing system <NUM> may be implemented with a bus architecture, represented generally by the bus <NUM>. The bus <NUM> may include any number of interconnecting buses and bridges depending on the specific application of the processing system <NUM> and the overall design constraints. The bus <NUM> links together various circuits including one or more processors and/or hardware components, represented by the processor <NUM>, the components <NUM>, <NUM>, <NUM>, <NUM> and the computer-readable medium / memory <NUM>. The bus <NUM> may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.

The processing system <NUM> may be coupled to a transceiver <NUM>. The transceiver <NUM> is coupled to one or more antennas <NUM>. The transceiver <NUM> provides a means for communicating with various other apparatus over a transmission medium. The transceiver <NUM> receives a signal from the one or more antennas <NUM>, extracts information from the received signal, and provides the extracted information to the processing system <NUM>, specifically the reception component <NUM>. In addition, the transceiver <NUM> receives information from the processing system <NUM>, specifically the transmission component <NUM>, and based on the received information, generates a signal to be applied to the one or more antennas <NUM>. The processing system <NUM> includes a processor <NUM> coupled to a computer-readable medium / memory <NUM>. The processor <NUM> is responsible for general processing, including the execution of software stored on the computer-readable medium / memory <NUM>. The software, when executed by the processor <NUM>, causes the processing system <NUM> to perform the various functions described supra for any particular apparatus. The computer-readable medium / memory <NUM> may also be used for storing data that is manipulated by the processor <NUM> when executing software. The processing system <NUM> further includes at least one of the components <NUM>, <NUM>, <NUM>, <NUM>. The components may be software components running in the processor <NUM>, resident/stored in the computer readable medium / memory <NUM>, one or more hardware components coupled to the processor <NUM>, or some combination thereof. The processing system <NUM> may be a component of the UE <NUM> and may include the memory <NUM> and/or at least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM>.

In one configuration, the apparatus <NUM>/<NUM>' for wireless communication includes means for determining that initial subscriber information associated with a UICC alone is insufficient to establish a secure connection with a <NUM> NR based network, means for obtaining additional subscriber information from a secure storage location which is separate from the UICC, means for generating a SUCI based on the additional subscriber information along with the initial subscriber information, and means for establishing the secure connection with the <NUM> NR based network based on the SUCI. The apparatus <NUM>/<NUM>' for wireless communication further include means for pre-configuring the UE with the additional subscriber information, and means for storing the additional subscriber information in the secure storage location in the UE.

Claim 1:
A method of wireless communications performed by a user equipment, UE, the method comprising:
determining (<NUM>) that initial subscriber information associated with a universal integrated circuit card, UICC, alone is insufficient to establish a secure connection with a <NUM> new radio, NR, based network;
obtaining (<NUM>) additional subscriber information from a secure storage location of the UE which is separate from the UICC;
generating (<NUM>) a subscription concealed identifier, SUCI, based on the additional subscriber information along with the initial subscriber information; and
establishing the secure connection with the <NUM> NR based network based on the SUCI.