Extension of subscriber identity module toolkit application commands to additional user equipment

Abstract

A user equipment (UE) that includes at least a processor and universal integrated circuit card (UICC) are described. The UE or a processor thereof can perform initializing a universal subscriber identity module (USIM) for communication with a cellular network, and registering with the cellular network using the USIM. The UE or processor provides, to the UICC, location information for a serving cell of the cellular network, where the location information including an identifier of a reduced capability serving cell or a private network cell. The UE or processor can then communicate with the serving cell according to a configuration that is based at least in part on the location information that is provided to the UICC.

Description

EXTENSION OF SUBSCRIBER IDENTITY MODULE TOOLKIT APPLICATION COMMANDS TO ADDITIONAL USER EQUIPMENTCROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Cooperation Treaty patent application claims priority to U.S. Provisional Patent Application No. 63 / 552,035, filed February 9, 2024, and titled “Extension of Subscriber Identity Module Toolkit Application Commands to Additional User Equipment,” the contents of which are incorporated herein by reference as if fully disclosed herein in its entirety.TECHNICAL FIELD

[0002] This application relates generally to wireless communication systems, including systems, apparatuses, and methods for extension of subscriber identity module toolkit application commands to additional user equipment.BACKGROUND

[0003] Wireless mobile communication technology uses various standards and protocols to transmit data between a network device (e.g., a base station, a radio head, etc.) and a wireless communication device. Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G), 3GPP new radio (NR) (e.g., 5G), and IEEE 802.11 standard for wireless local area networks (WLAN) (commonly known to industry groups as Wi-Fi®).

[0004] As contemplated by the 3GPP, different wireless communication systems standards and protocols can use various radio access networks (RANs) for communicating between a network device of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE). 3GPP RANs can include, for example, global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next-Generation Radio Access Network (NG-RAN).

[0005] Each RAN may use one or more radio access technologies (RATs) to perform communication between the network device and the UE. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3 GPP RAT, the E-UTRAN implements LTE RAT (sometimes simplyreferred to as LTE), and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR). Tn certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.

[0006] A network device used by a RAN may correspond to that RAN. One example of an E- UTRAN network device is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN)Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB). One example of an NG-RAN network device is a next generation Node B (also sometimes referred to as a g Node B or gNB).

[0007] A RAN provides its communication services with external entities through its connection to a core network (CN). For example, E-UTRAN may utilize an Evolved Packet Core(EPC), while NG-RAN may utilize a 5G Core Network (5GC).BRIEF DESCRIPTION OF THE DRAWINGS

[0008] To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0009] FIG. 1 shows an example wireless communication system, according to embodiments described herein.

[0010] FIG. 2 shows an example message flow, according to one or more aspects described herein.

[0011] FIG. 3 shows an example message flow, according to one or more aspects described herein.

[0012] FIG. 4 shows another example method of wireless communication, according to one or more aspects described herein.

[0013] FIG. 5 illustrates an example architecture of a wireless communication system, according to embodiments described herein.

[0014] FIG. 6 illustrates an example system for performing signaling between a wireless device and a network device, according to embodiments described herein.DETAILED DESCRIPTION

[0015] Various embodiments are described with regard to a user equipment (UE). However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to exchange information and data with a network. Therefore, the UE as described herein is used to represent any appropriate electronic device.

[0016] Private networks, which may also be referred to as non-public networks (NPN) herein, are cellular networks that are generally intended for non-public (or private) use. A private network can be deployed in a variety of configurations where both virtual and physical network elements can be utilized. Two major categories or types of private network (e.g., NPN) include a standalone NPN (SNPN) and a public network integrated NPN (PNI-NPN).

[0017] An SNPN is an NPN that does not rely on network functions provided by a public land mobile network (PLMN), or mobile network operator (MNO). An SNPN is a private network (e.g., NPN) that is deployed in isolation, and usually involves more investment and commitment from the owner (network operator) of the SNPN. For a SNPN, generally all network functions are located inside the defined premises of the organization, and the SNPN is separate from the public network.

[0018] A PNI-NPN is an NPN that is deployed with the support of a PLMN. A PNI-NPN is a private network that may be deployed as a private slice (dedicated network slice by the PLMN for the sole use of the owner), or the PNI-NPN may involve part of the networks being deployed by the PLMN and others by the owner. For a PNI-NPN sharing a radio access network (RAN), part of the RAN is shared among the owner and the mobile operator. Generally, all other network functions are segregated as in the case of SNPN. In most cases, for this scenario, the NPN data resides within the defined premises of the organization.

[0019] A reduced capability (RedCap) device is generally a UE with a reduced capability set relative to other UEs. RedCap UEs may be characterized by reduced complexity (e.g., fewer receive (Rx) and / or transmit (Tx) antennas), reduced use of bandwidth, lower power consumption, relaxed (e.g., slower) data rates, relaxed processing times, relaxed processing capabilities, and so on. Specific use cases for RedCap UEs include for industrial wireless sensors, video surveillance, and wearables. RedCap UEs may make use of extended discontinuous reception (DRX) in a radio resource control (RRC) idle state or inactive state, or relaxed radio resource management (RRM) measurements for neighbor cells (e.g., in a stationary state, or when not at a cell edge). A RedCap cell refers to a serving cell that is configured to serve RedCap UEs, for example according to oneor more of the features discussed above. In some examples, a RedCap cell may be capable of serving both RedCap UEs as well as non-RedCap UEs, but nonetheless benefit from identifying which UEs, if any, are RedCap UEs.

[0020] According to current approaches, one or more commands and messages do not provide information about whether a serving cell (e.g., RAN cell or next generation RAN (NG RAN) cell) is a PNI-NPN cell (e.g., a closed access group (CAG)), a NPN cell (e.g., SNPN), or a RedCap cell. For example, certain commands and messages may identify certain information about the cell, but may fail to inform a UE whether the serving cell is a PNI-NPN cell, SNPN cell, or RedCap cell. Such commands and messages include a “provide local information” (PLI) command that may include location information such as a mobile country code (MCC), a mobile network code (MNC), a location area code (LAC), a tracking area code (TAC), a cell identity, and an extended cell identity; a “provide local information” command that may include network measurement results; an “event download” command for location status; an “event download” command for network rejection; or a “CAG cell selection status” provided for provide local information (PLI) command that may include CAG information, envelope event download CAG cell selection. A UICC chip, including a subscriber identity module (SIM) applet running on the UICC, may not operate properly without such information. In some instances, the SIM toolkit (STK) applet that initiates actions on the UE (e.g., interactive services such as balance inquiries, menu-based services, and value-added services) may not operate properly for the serving cells that are PNI- NPN cells, SNPN cells, or RedCap cells. In some examples, the UE (e.g., the UICC, a UICC applet) may infer the wrong cell configuration for a serving cell.

[0021] Techniques that improve or ensure interoperability between regular serving cells for UEs and UEs operating in a PNI-NPN cell, SNPN cell, or RedCap cell are discussed herein. As further described herein, a UE can initialize a SIM (e.g., a universal SIM (USIM)) for communication with a cellular network, and register with the cellular network using the SIM. The USIM may be embodied as a physical SIM card and / or an embedded SIM (eSIM). The UE can then provide to a UICC of the UE, location information for a serving cell of the cellular network with which the UE is seeking to establish a connection. The location information includes an identifier of a reduced capability (e.g., RedCap) serving cell or a private network (e.g., PNI-NPN cell, or NPN cell). The UICC can then know and be configured according to a configuration applicable to the reduced capability serving cell or private network, and the UE can communicate with the serving cell according to such configuration. In the case that the UE is capable of operating in more than one configuration, for example, or when SIM cards are reused between two or moretypes of UE configurations, the UE can be appropriately configured for communication between the different UE configurations.

[0022] FIG. 1 shows an example wireless communications system 100, according to one or more aspects described herein. In one or more embodiments, wireless communications system 100, supports one or more aspects of extension of subscriber identity module toolkit application commands to additional user equipment, as further described herein.

[0023] Wireless communications system 100 includes a UE 102 and a network device 104. In one or more embodiments described herein, the network device 104 is a NG RAN cell having a coverage area 110, such as a reduced capability serving cell or a private network cell, which are further described herein. In some embodiments, the network device 104 may be one of multiple network device (e.g., NG RANs) that make up the cellular network with which the UE 102 is being registered.

[0024] In one or more embodiments, UE 102 includes a processor 114. In some embodiments, processor 114 is a baseband processor. In some embodiments, processor 114 includes two or more processors, memory, firmware, or other components or circuitry to facilitate or otherwise support wireless communications, including performing one or more operations further described herein.

[0025] In one or more embodiments, UE 102 is associated with a universal SIM (USIM), such as a UICC 116. In one or more embodiments, the UE 102 or the combination of the UE 102 and UICC 116, may be referred to as a mobile equipment (ME) or a mobile station (MS). In some embodiments, UICC 116 may be an embedded UICC (eUICC).

[0026] In one or more embodiments, the UICC 116 is configured to support multiple SIM or eSIM profiles, for example two or more profiles, and any number of profiles may be supported, configured, or used at the UICC 116. In one or more embodiments, the UICC 116 may allow a user (e.g., a user of the UE 102) to choose between multiple MNO profiles. In some embodiments, the UICC 116 may be a discrete chip or integrated circuit component, for example mounted on a printed circuit board of the UE 102. In other embodiments, the UICC 116 may be incorporated into an integrated circuit chip, module, or assembly with other components or circuits of UE 102, such as a modem or baseband processor (which may also be referred to herein as simply “a processor”).

[0027] In some embodiments, UICC 116 (e.g., a UICC chip) may run a SIM applet, such as the STK applet discussed above that initiates actions on the UE 102. The UE 102 and the UICC 116 may power up, initialize the USIM, and exchange messages between the UE 102 and the UICC 116. The UE 102 may exchange the registration messages 124 with the network device 104 toregister the UE 102 with the cellular network via network device 104. In one or more embodiments, the UE 102 may specifically indicate (e.g., during USIM initialization, to the UICC 116, from the processor 114) a capability of the UE 102 to provide the location information for a serving cell of a cellular network, as further discussed herein (e.g., location information that includes an identifier of a RedCap serving cell or a private network cell (e.g., PNI-NPN or SNPN cell)). In some embodiments, the indication of the capability may be provided in a “terminal profile” command (e.g., using a dedicated bit of the command).

[0028] Following registration with the cellular network via the network device 104, the UE 102 may have established a packet data unit (PDU) session 120, where the PDU session 120 is a logical connection between the UE 102 and the cellular network. In some examples, the PDU session 120 is established with a data network name (DNN), the name of the data network to which the PDU Session 120 provides connectivity, and a single network slice selection assistance information (s- NSSAI), which is used to uniquely identify the network slice in which the PDU session 120 is established.

[0029] Following registration via the exchange of the registration messages 124 and / or establishment of the PDU session 120, the UE 102 provides (transmits) location information to the UICC 116. The provided location information is for the serving cell (e.g., an NG RAN cell) of the network device 104 having the coverage area 110. The location information includes an identifier of a reduced capability (e.g., RedCap) serving cell or a private network (e.g., PNI-NPN cell, or NPN cell). The UICC 116 can then know and be configured or reconfigured according to a configuration applicable to the reduced capability serving cell or private network, and the UE can communicate with the serving cell according to such configuration. In the case that the UE is capable of operating in more than one configurations, for example, or when SIM cards are reused between two or more types of UE configurations, the UE 102 can be appropriately configured for communication between the different UE configurations.

[0030] The location information may be obtained by the UE 102 from network device 104, or another network device associated with the cellular network. In some embodiments, for example for a private network (e.g., PNI-NPN, SNPN) or a RedCap cell, the network device 104 serves a PNI-NPN cell, SNPN cell, or RedCap cell, and the cell broadcasts the location information that the UE 102 receives. For example, the broadcast of location information may be in system information (e.g., a system information broadcast 1 message (SIB 1), system information broadcast message (SIB 10)), and include one or more CAG IDs or NIDs, and be associated with a human readable network name.

[0031] In some examples described herein, the serving cell location information is provided by the UE 102 (e.g., ME) to the UICC 1 16 via a terminal response in the case of PLT commands from the UICC, requesting current location information about the MCC, current serving cell information. In other examples, the location information is provided by the UE 102 to the UICC 116 via location information in the case of an event download-location status envelope command is received from the UICC 116 in response to Set up Event list- event download-location status. The Set up Event list-event download-location status command requests dynamic current location information whenever there is a change of cell detected on the side of the UE 102 . In other examples, the location information is provided by the UE 102 to the UICC 116 in the case of an event download command for network rejection.

[0032] FIG. 2 shows an example message flow 200, according to one or more aspects described herein. In one or more embodiments, message flow 200, supports one or more aspects of extension of subscriber identity module toolkit application commands to additional user equipment, as further described herein. Message flow 200 includes signaling and actions performed by one or more of a UE 102, network device 104, or both, where the UE 102 includes a processor 114 and a UICC 116.

[0033] At 202, the UE 102 (including processor 114 and UICC 116) perform power up operations. At 204, a USIM initialization procedure is performed, including to prepare the UE communication, using the USIM, with the cellular network that includes network device 104. In one or more embodiments, the UE 102 may indicate (e.g., as part of, during, or otherwise in connection with USIM initialization at 204) a capability of the UE 102 to provide to the UICC 116, and from the processor 114, the location information for a serving cell of a cellular network, as further discussed herein (e.g., location information that includes an identifier of a RedCap serving cell or a private network cell (e.g., PNI-NPN or SNPN cell). In some embodiments, the indication of the capability may be provided in a “terminal profile” command (e.g., using a dedicated bit of the command).

[0034] A proactive command 206 is sent from the UICC 116 to the processor 114 of UE 102, the proactive command 206 requesting for the processor 114 to send (transmit, provide) current local information to the UICC 116. In one or more embodiments, the proactive command 206 is a provide local information (PLI) command for location information. Prior to registration 222, a terminal response 208 may be sent from the processor 114 to the UICC 116 indicating that there is no service, and location information is not provided. In some embodiments, the terminal response 208 indicates: “ME (e.g., or UE) currently unable to process command - no service.” However, in some embodiments, once the ME (e.g., or UE) is registered (e.g., followingregistration 222), the terminal response includes the requested information, including the location information. In some embodiments, the terminal response 208 indicates: “limited service” where only emergency services are offered due to limited registration to available cell, and may additionally include location information of the RedCap cell, or PNI-NPN cell, or NPN cell where the device is in a limited service state.

[0035] Registration 222 may be performed between the UE 102 (e.g., via the processor 114) and the cellular network (e.g., via the network device 104). Registration 222 includes at least the UE 102 (e.g., via processor 1 14) transmitting a registration request message 210 to the network device 104; UE 102 (e.g., via processor 114) receiving a registration accept message 212; and UE 102 (e.g., via processor 114) transmitting a registration complete message 214. Following registration 222 with the cellular network via the network device 104, the UE 102 (e.g., and processor 114) may have established a PDU session 216. In some embodiments, the PDU session 216 is a logical connection between the UE 102 and the cellular network (e.g., via network device 104), is established with a DNN, and may have s-NSSAI.

[0036] A proactive command 218 is sent from the UICC 116 to the processor 114 of UE 102, the proactive command 218 requesting for the processor 114 to send (transmit, provide) current local information to the UICC 116. In one or more embodiments, the proactive command 218 is a provide local info (PEI) command requesting for location information that may also include an identifier (indication) of a reduced capability serving cell or a PNI-NPN, or SNPN (standalone private network) cell. In some embodiments, a terminal response message 220 is transmitted (sent, provided) by the processor 114 and received (obtained) by the UICC 116 indicating (identifying, providing, transmitting) the requested local information. In one or more embodiments, the provided local information includes location information such as one or more of an MCC, an MNC, a LAC, a TAC, a cell identity of the current cell. As further described herein, in some embodiments, the provided local information may include a CAG cell (e.g., a CAG ID type), a CAG ID, or both. In some embodiments, the provided local information may include an NID cell (e.g., an NID type), an NID ID, or both. In some embodiments, this may include the indication of the RedCap, or NPN cell, on which the UE is in limited service.

[0037] In some embodiments, the terminal response message 220, and specifically existing location information, may be effectively extended from current approaches to include additional bytes to carry (indicate, convey) the location information that includes an identifier (indication) of a reduced capability serving cell, PNI-NPN cell or a SNPN (Standalone private network) cell. For example the terminal response message may include location information with a set of bytes (e.g., sixteen or more bytes) for a location information tag, a length indicator, an MCC, an MNC, a TAC,an NG-RAN / satellite NG-RAN cell identifier (NCI), an NG-RAN tracking area identification (TAT) list identifier tag, an indicator of a length (e.g., in total bytes) in the satellite NG-RAN TAI list, a satellite NT-RAN TAI list, and one or more additional bits or bytes (e.g., which may generally be referred to as extended information or extended location information) of information that includes the identifier (indication) of a reduced capability serving cell or a private network cell. In one or more embodiments, the extended location information is only included in the location information in the case of the UE 102 being camped on a PNI-NPN, SNPN, or reduced capability cell or supported cell. In some embodiments, the location information of the terminal response message 220 may be or be referred to as a parameter, command parameter, or data. In some embodiments, the terminal response message 220 is only required to be sent by the provide location information proactive command.

[0038] In one or more embodiments, the extended location information includes a number of bytes (e.g., 7 bytes in the case of a CAG ID) that include an extended information tag (e.g., 1 byte), an indication of length (e.g., 1 byte), an extended information type (e.g., 1 byte), and the extended identification (e.g., 4 bytes in the case of a CAG ID). In some embodiments, the extended information tag may indicate (e.g., include an identifier) a reduced capability serving cell or a private network cell that the UE is then-currently registered on. In some embodiments, the extended information tag may indicate one of a CAG ID, NID, or reduced capability cell. The extended identification may be one or a CAG ID or NID, corresponding to the extended information tag indicating the one of CAG ID or NID, respectively. In some embodiments, if the extended information tag indicates a reduced capability cell, the extended identification may be absent, and the identifier of length may be indicated accordingly (for example, “01”).

[0039] FIG. 3 shows an example message flow 300, according to one or more aspects described herein. In one or more embodiments, message flow 300, supports one or more aspects of extension of subscriber identity module toolkit application commands to additional user equipment, as further described herein. Message flow 300 includes signaling and actions performed by one or more of a UE 102, network device 104, or both, where the UE 102 includes a processor 1 14 and a UICC 116.

[0040] At 302, the UE 102 (including processor 114 and UICC 116) perform power up operations. At 304, a USIM initialization procedure is performed, including to prepare the UE communication, using the USIM, with the cellular network that includes network device 104. In one or more embodiments, the UE 102 may indicate (e.g., as part of, during, or otherwise in connection with USIM initialization at 304) a capability of the UE 102 to provide the location information for a serving cell of a cellular network, as further discussed herein (e.g., locationinformation that includes an identifier of a RedCap serving cell or a private network cell (e.g., PNI-NPN or SNPN cell). Tn some embodiments, the indication of the capability may be provided in a “terminal profile” command (e.g., using a dedicated bit of the command).

[0041] A proactive command 306 (e.g., proactive command (SET UP EVENT LIST : EVENT DOWNLOAD - - Location status)) is sent from the UICC 116 to the processor 114 of UE 102, the proactive command 306 requesting for the processor 114 to send (transmit, provide) current location information to the UICC 116. In one or more embodiments, the proactive command 306 from UICC 1 16 supplies (transmits, provides) to the processor 1 14 (e.g., via UE 102) an event list with Event download-location status (e.g., by using the set up event (SET UP EVENT) list command). In some embodiments, the UE 102 (e.g.., via processor 114) provides a terminal response 308, followed (e.g., immediately after, as a next message) an envelope command 310 (e.g., ENVELOPE) associated with an event download for location status may be sent from the processor 114 to the UICC 116. The envelope command 310 indicates that there is no service, and location information is not provided. In one or more embodiments, the envelope command 310 is sent prior to registration 322.

[0042] In one or more embodiments, in the event the setup event list (e.g., of proactive command 306 ) included a network rejection, then the envelope command 310 from the UE 102 (e.g., via processor 114) includes a network rejection when the network rejects the registration attempt.

[0043] Registration 322 may be performed between the UE 102 (e.g., via the processor 1 14) and the cellular network (e.g., via the network device 104). Registration 322 includes at least the UE 102 (e.g., via processor 114) transmitting a registration request message 312 to the network device 104; UE 102 (e.g., via processor 114) receiving a registration accept message 314; and UE 102 (e.g., via processor 114) transmitting a registration complete message 316. Following registration 222 with the cellular network via the network device 104, the UE 102 (e.g., and processor 114) may have established a PDU session 318. In some embodiments, the PDU session 318 is a logical connection between the UE 102 and the cellular network (e.g., via network device 104), is established with a DNN, and may have an s-NSSAl.

[0044] Following registration 322 (either as a next communication, or with one or more intervening communications) an envelope command 320 that includes the location information (e.g., current location information) is provided from the processor 114 to the UICC 116. In one or more embodiments, the envelope command 320 (e.g., ENVELOPE) is associated with an event download location status and is sent from the processor 114 to the UICC 116. In one or more embodiments, the requested local information includes location information such as one or moreof an MCC, an MNC, a LAC, a TAC, or a cell identity of the current cell. As further described herein, in some embodiments, the requested, provided local information may include a CAG cell (e.g., a CAG ID type), a CAG ID, or both. In some embodiments, the requested, provided local information may include an NID cell (e.g., an NID type), an NID ID, or both. In some embodiments, the provided information may include an indication that the UE is in a RedCap configuration and registered to a RedCap cell

[0045] In some embodiments, the envelope command 320, and specifically an existing location information, may be effectively extended from current approaches to include additional bytes to carry (indicate, convey) the location information that includes an identifier (indication) of a reduced capability serving cell or a private network cell. For example the envelope command 320 may include location information with a set of bytes (e.g., sixteen or more bytes) for a location information tag, a length indicator, an MCC, an MNC, a TAC, an NG-RAN / satellite NG-RAN cell identifier (NCI), an NG-RAN tracking area identification (TAI) list identifier tag, an indicator of a length (e.g., in total bytes) in the satellite NG-RAN TAI list, a satellite NT-RAN TAI list, and one or more additional bits or bytes (e.g., which may generally be referred to as extended information or extended location information) of information that includes the identifier (indication) of a reduced capability serving cell or a private network cell. In one or more embodiments, the extended location information is only included in the location information in the case of the UE 102 being camped on a PNI-NPN, SNPN, or reduced capability cell or supported cell. In some embodiments, the location information of the envelope command 320 may be or be referred to as a parameter, command parameter, or data. In some embodiments, the envelope command 320 is only required to be sent by the provided location information proactive command.

[0046] In one or more embodiments, the extended location information includes a number of bytes (e.g., 7 bytes in the case of a CAG ID) that include an extended information tag (e.g., 1 byte), an identifier of length (e.g., 1 byte), an extended information type (e.g., 1 byte), and the extended identification (e.g., 4 bytes in the case of a CAG ID). In some embodiments, the extended information tag may indicate (e.g., include an identifier) a reduced capability serving cell or a private network cell that the UE is then-currently registered on. In some embodiments, the extended information tag may indicate one of a CAG ID, NID, or reduced capability cell. The extended identification may be one or a CAG ID or NID, corresponding to the extended information tag indicating the one of CAG ID or NID, respectively. In some embodiments, if the extended information tag indicates a reduced capability cell, the extended identification may be absent, and the identifier of length may be indicated accordingly (for example, “01”).

[0047] In one or more embodiments, for example when a network device 104 is a satellite or other network device of a non-terrestrial network, a location status message may additionally include extended location information about cells with which the UE 102 is registered, for example, an indication of reduced capability, a CAG (PNI-NPN), or SNPN configuration.

[0048] In one or more embodiments, a network rejection message includes location information. For example, an envelope command (e.g., ENVELOPE) associated with an event download for a network rejection is sent from the processor 114 to the UICC 116. In some embodiments, the network rejection message may be sent when the network rejects a registration attempt by the UE 102 (e.g., via processor 114). In some embodiments, the network rejection message, and specifically an existing network rejection message, may be effectively extended from current approaches to include additional bytes to carry (indicate, convey) the location information that includes an identifier (indication) of a reduced capability serving cell or a private network cell. For example, the network rejection message may include an event download tag, a length indicator, an event list, device identities, location information, routing area identification, tracking area identification, access technology, update / attach / registration type, rejection cause code, extended rejection cause code, and extended information. Extended information may also be referred to as extended location information, and include the identifier (indication) of a reduced capability serving cell or a private network cell. In one or more embodiments, the extended location information is included in the location information in the case of the UE 102 being rejected on a PNI-NPN, SNPN, or reduced capability cell or supported cell. In some embodiments, the location information of the network rejection message may be or be referred to as a parameter, command parameter, or data.

[0049] In one or more embodiments, the extended location information includes a number of bytes (e.g., 7 bytes in the case of a CAG ID) that include an extended information tag (e.g., 1 byte), an identifier of length (e.g., 1 byte), an extended information type (e.g., 1 byte), and the extended identification (e.g., 4 bytes in the case of a CAG ID). In some embodiments, the extended information tag may indicate (e.g., include an identifier) a reduced capability serving cell or a private network cell that the UE is then-currently registered on. In some embodiments, the extended information tag may indicate one of a CAG ID, NID, or reduced capability cell. The extended identification may be one of a CAG ID or NID, corresponding to the extended information tag indicating the one of CAG ID or NID, respectively. In some embodiments, if the extended information tag indicates a reduced capability cell, the extended identification may be absent, and the identifier of length may be indicated accordingly (for example as “01”).

[0050] In one or more embodiments described herein, the location information may include a CAG ID without (excluding, but does not include) a CAG ID type for the CAG ID. In some embodiments described herein, the location information includes an NID without (excluding, but does not include) an NID type for the NID.

[0051] In one or more embodiments, the signaling or message that provides the location information can include an indication that the UE is a reduced capability UE without (excluding, but does not include) the capability to convey (carry, provide) an indication that the cell on which the UE is camped (e.g., registered) is a CAG cell or SNPN cell. In some embodiments, the signaling or message can include an indication that the cell on which the UE is camped (e.g., registered) is a CAG cell, without (excluding, but does not include) the capability to convey (carry, provide) an indication that the cell is a reduced capability UE or that the cell on which the UE is camped (e.g., registered) is a SNPN cell. In some embodiments, the signaling or message can include an indication of the cell on which the UE is camped (e.g., registered) is a SNPN cell, without (excluding, but does not include) the capability to convey (carry, provide) an indication that the cell is a reduced capability UE or that the cell on which the UE is camped (e.g., registered) is a CAG cell. In some embodiments, the signaling or message can include an indication of the cell on which the UE is camped (e.g., registered) is a CAG cell or a SNPN cell, without (excluding, but does not include) the capability to convey (carry, provide) an indication that the cell is a reduced capability UE. In some embodiments, this may include the indication of the RedCap, or NPN cell on which UE is in limited service.

[0052] In one or more embodiments, the current serving cell CAG ID can be conveyed (carried, provided) by extending a CAG cell selection status. For example, the CAG cell selection status message, and specifically an existing CAG cell selection status message, may be effectively extended from current approaches to include additional bytes to carry (indicate, convey) one or both of a current CAG cell identifier (e.g., CAG ID) or a current CAG cell human readable network name (HRNN), in addition to CAG cell selection status tag, a length indicator, and a CAG cell selection status.

[0053] FIG. 4 shows an example method 400 of wireless communication. In one or more embodiments, method 400 supports one or more aspects of extension of subscriber identity module toolkit application commands to additional user equipment, as further described herein. In some cases, the UE may be the UE 102, wireless device 602, or one of the other UEs described herein. The method 400 may be performed using a processor, a transceiver (e.g., main radio), or other components of the UE.

[0054] At 402, the method 400 includes providing, to a UICC of a UE, location information for a serving cell of the cellular network, the location information including an identifier of a reduced capability serving cell or a private network.

[0055] At 404, the method 400 includes communicating with the serving cell according to a configuration that is based at least in part on the location information that is provided to the UICC.

[0056] In some embodiments, providing the location information for the serving cell includes transmitting a terminal response message, the terminal response message including the identifier of the reduced capability serving cell or the private network. In one or more embodiments, the method further includes receiving, from the UICC, a proactive command requesting the location information, the terminal response message transmitted in response to the proactive command.

[0057] In some embodiments, providing the location information for the serving cell includes transmitting an envelope command for event download location status, the envelope command including the identifier of the reduced capability serving cell or the private network.

[0058] In some embodiments, providing the location information for the serving cell includes transmitting an envelope command for a network rejection event, the envelope command including the identifier of the reduced capability serving cell or the private network.

[0059] In some embodiments, the location information further includes a CAG ID without a CAG ID type for the CAG ID. In some embodiments, the location information includes an NID without an NID type for the NID. In some embodiments, the location information includes an indication that the UE is a reduced capability UE, that the serving cell is a CAG cell, or that the serving cell is a standalone non-public network; and the indication is without a corresponding one or more of a CAG ID or an NID.

[0060] In some embodiments, providing the location information for the serving cell includes transmitting a CAG cell selection status message that indicates a CAG ID, the location information including the CAG ID.

[0061] In one or more embodiments, the UE includes a US IM associated with the UICC, and the method further includes initializing the USIM associated with the UICC for communication with the cellular network, and registering with the cellular network according to subscriber information of the USIM. In some embodiments, the USIM comprises one or both of a physical SIM card, or an eSIM. In some embodiments, the UE provides (e.g., transmits) to the UICC an indication of a capability of the UE to provide (transmit) to the UICC the location information for the serving cell.

[0062] In one or more embodiments, the method further includes transmitting, to the UICC, a terminal profile command indicating a capability to provide the location information for one or more serving cells of the cellular network.

[0063] In some embodiments, the private network includes one of a PNI-NPN or a SNPN.

[0064] The method 400 may be variously embodied, extended, or adapted, as described in the following paragraphs and elsewhere in this description.

[0065] Embodiments contemplated herein include one or more non-transitory computer- readable media storing instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 400. In the context of method 400, this non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 606 of a wireless device 602 that is a UE, as described herein).

[0066] Embodiments contemplated herein include an apparatus having logic, modules, or circuitry to perform one or more elements of the method 400. In the context of method 400, this apparatus may be, for example, an apparatus of a UE (such as a wireless device 602 that is a UE).

[0067] Embodiments contemplated herein include an apparatus having one or more processors and one or more computer-readable media, using or storing instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 400. In the context of method 400, this apparatus may be, for example, an apparatus of a UE (such as a wireless device 602 that is a UE, as described herein).

[0068] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 400.

[0069] Embodiments contemplated herein include a computer program or computer program product having instructions, wherein execution of the program by a processor causes the processor to carry out one or more elements of the method 400. In the context of method 400, the processor may be a processor of a UE (such as a processor(s) 604 of a wireless device 602 that is a UE, as described herein), and the instructions may be, for example, located in the processor and / or on a memory of the UE (such as a memory 606 of a wireless device 602 that is a UE, as described herein).

[0070] FIG. 5 illustrates an example architecture of a wireless communication system, according to embodiments described herein. The following description is provided for an example wireless communication system 500 that operates in conjunction with the LTE system standardsor specifications and / or 5G or NR system standards or specifications, as provided by 3GPP technical specifications.

[0071] As shown, the wireless communication system 500 includes UE 502 and UE 504 (although any number of UEs may be used). In this example, the UE 502 and the UE 504 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also comprise any mobile or non-mobile computing device configured for wireless communication.

[0072] The UE 502 and UE 504 may be configured to communicatively couple with a RAN 506. In embodiments, the RAN 506 may be NG-RAN, E-UTRAN, etc. The UE 502 and UE 504 utilize connections (or channels) (shown as connection 508 and connection 510, respectively) with the RAN 506, each of which comprises a physical communications interface. The RAN 506 can include one or more network devices, such as base station 512 and base station 514, that enable the connection 508 and connection 510.

[0073] In this example, the connection 508 and connection 510 are air interfaces to enable such communicative coupling and may be consistent with RAT(s) used by the RAN 506, such as, for example, an LTE and / or NR.

[0074] In some embodiments, the UE 502 and UE 504 may also directly exchange communication data via a sidelink interface 516. The UE 504 is shown to be configured to access an access point (shown as AP 518) via connection 520. By way of example, the connection 520 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 518 may comprise a Wi-Fi® router. In this example, the AP 518 may be connected to another network (for example, the Internet) without going through a CN 524.

[0075] In embodiments, the UE 502 and UE 504 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 512 and / or the base station 514 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0076] In some embodiments, all or parts of the base station 512 or base station 514 may be implemented as one or more software entities running on server computers as part of a virtualnetwork. In addition, or in other embodiments, the base station 512 or base station 514 may be configured to communicate with one another via interface 522. In embodiments where the wireless communication system 500 is an LTE system (e.g., when the CN 524 is an EPC), the interface 522 may be an X2 interface. The X2 interface may be defined between two or more network devices of a RAN (e.g., two or more eNBs and the like) that connect to an EPC, and / or between two eNBs connected to the EPC. In embodiments where the wireless communication system 500 is an NR system (e.g., when CN 524 is a 5GC), the interface 522 may be an Xn interface. The Xn interface is defined between two or more network devices of a RAN (e.g., two or more gNBs and the like) that connect to the 5GC, between a base station 512 (e.g., a gNB) connecting to the 5GC and an eNB, and / or between two eNBs connecting to the 5GC (e.g., CN 524).

[0077] The RAN 506 is shown to be communicatively coupled to the CN 524. The CN 524 may comprise one or more network elements 526, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UE 502 and UE 504) who are connected to the CN 524 via the RAN 506. The components of the CN 524 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0078] In embodiments, the CN 524 may be an EPC, and the RAN 506 may be connected with the CN 524 via an SI interface 528. In embodiments, the SI interface 528 may be split into two parts, an S 1 user plane (S 1-U) interface, which carries traffic data between the base station 512 or base station 514 and a serving gateway (S-GW), and the Sl-MME interface, which is a signaling interface between the base station 512 or base station 514 and mobility management entities (MMEs).

[0079] In some embodiments, the CN 524 may be a 5GC, and the RAN 506 may be connected with the CN 524 via an NG interface 528. In some embodiments, the NG interface 528 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 512 or base station 514 and a user plane function (UPF), and the SI control plane (NG-C) interface, which is a signaling interface between the base station 512 or base station 514 and access and mobility management functions (AMFs).

[0080] Generally, an application server 530 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 524 (e.g., packet switched data services). The application server 530 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for the UE 502 and UE 504 via the CN 524.The application server 530 may communicate with the CN 524 through an IP communications interface 532.

[0081] FIG. 6 illustrates an example system 600 for performing signaling 638 by a wireless device 602, according to embodiments described herein. The system 600 may be a portion of a wireless communication system as herein described. The wireless device 602 may be, for example, a UE of a wireless communication system.

[0082] The wireless device 602 may include one or more processor(s) 604. The processor(s) 604 may execute instructions such that various operations of the wireless device 602 are performed, as described herein. The processor(s) 604 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0083] The wireless device 602 may include a memory 606. The memory 606 may be a non- transitory computer-readable storage medium that stores instructions 608 (which may include, for example, the instructions being executed by the processor(s) 604). The instructions 608 may also be referred to as program code or a computer program. The memory 606 may also store data used by, and results computed by, the processor(s) 604.

[0084] The wireless device 602 may include one or more transceiver(s) 610 (also collectively referred to as a transceiver 610) that may include radio frequency (RF) transmitter and / or receiver circuitry that use the antenna(s) 612 of the wireless device 602 to facilitate signaling (e.g., the signaling 638) to and / or from the wireless device 602 with other devices (e.g., a network device) according to corresponding RATs.

[0085] The wireless device 602 may include one or more antenna(s) 612 (e.g., one, two, four, eight, or more). For embodiments with multiple antenna(s) 612, the wireless device 602 may leverage the spatial diversity of such multiple antenna(s) 612 to send and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, MIMO behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect). MIMO transmissions by the wireless device 602 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 602 that multiplexes the data streams across the antenna(s) 612 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream). Some embodiments may use single user MIMO(SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multiuser MIMO (MU-MTMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).

[0086] In some embodiments having multiple antennas, the wireless device 602 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s) 612 are relatively adjusted such that the (joint) transmission of the antenna(s) 612 can be directed (this is sometimes referred to as beam steering).

[0087] The wireless device 602 may include one or more interface(s) 614. The interface(s) 614 may be used to provide input to or output from the wireless device 602. For example, a wireless device 602 that is a UE may include interface(s) 614 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 610 / antenna(s) 612 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

[0088] The wireless device 602 may include a UICC 618, which may be an example of one or more UICCs described herein, including UICC 116, and may be an eUICC in some examples.

[0089] The wireless device 602 may include location information manager 616. The location information manager 616 may be implemented via hardware, software, or combinations thereof. For example, the location information manager 616 may be implemented as a processor, circuit, and / or instructions 608 stored in the memory 606 and executed by the processor(s) 604. In some examples, the location information manager 616 may be integrated within the processor(s) 604 and / or the transceiver(s) 610. For example, the location information manager 616 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 604 or the transceiver(s) 610.

[0090] The location information manager 616 may be used for various aspects of the present disclosure, for example, aspects of FIGs. 1-6, from a wireless device or UE perspective. The location information manager 616 may be configured to perform, for example, providing, to a UICC of the UE, location information for a serving cell of a cellular network, the location information including an identifier of a reduced capability serving cell or a private network; communicating with the serving cell according to a configuration that is based at least in part on the location information that is provided to the UICC.

[0091] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband processor (or processor) as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, network device, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.

[0092] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description but is not intended to be exhaustive or to limit the scope of embodiments to the precise form described. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0093] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.

[0094] The systems described herein pertain to specific embodiments but are provided as examples. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.

[0095] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein but may be modified within the scope and equivalents of the appended claims.

Claims

CLAIMS1. A processor configured to: provide, to a universal integrated circuit card (UICC) of a user equipment (UE), location information for a serving cell of a cellular network, the location information including an identifier of a reduced capability serving cell or a private network cell; and communicate with the serving cell according to a configuration that is based at least in part on the location information that is provided to the UICC.

2. The processor of claim 1 , wherein the processor configured to provide the location information for the serving cell comprises the processor configured to: transmit a terminal response message, the terminal response message including the identifier of the reduced capability serving cell or the private network cell.

3. The processor of claim 2, wherein the processor is further configured to: receive, from the UICC, a proactive command requesting the location information, the terminal response message transmitted in response to the proactive command.

4. The processor of claim 1 , wherein the processor configured to provide the location information for the serving cell comprises the processor configured to: transmit an envelope command for event download location status, the envelope command including the identifier of the reduced capability serving cell or the private network cell.

5. The processor of claim 1 , wherein the processor configured to provide the location information for the serving cell comprises the processor configured to: transmit an envelope command for a network rejection event, the envelope command including the identifier of the reduced capability serving cell or the private network cell.

6. The processor of claim 1 , wherein the location information further comprises a closed access group identifier (CAG ID) without a CAG ID type for the CAG ID.

7. The processor of claim 1 , wherein the location information comprises a network identifier (NID) without an NID type for the NID.

8. The processor of claim 1 , wherein: the location information comprises an indication that the UE is a reduced capability UE, that the serving cell is a closed access group (CAG) cell, or that the serving cell is a standalone non-public network; and the indication is without a corresponding one or more of a closed access group identifier (CAG ID) or a network identifier (NID).

9. The processor of claim 1 , wherein the processor configured to provide the location information for the serving cell comprises the processor configured to: transmit a closed access group (CAG) cell selection status message that indicates a closed access group identifier (CAG ID), the location information comprising the CAG ID.

10. The processor of claim 1 , wherein the processor is further configured to: transmit, to the UICC, a terminal profile command indicating a capability to provide the location information for one or more serving cells of the cellular network.

11. The processor of claim 1 , wherein the private network cell comprises one of a public network integrated non-public network (PNI-NPN) or a standalone non-public network (SNPN).

12. A method of wireless communication at a user equipment (UE), comprising: providing, to a universal integrated circuit card (UICC) of the UE, location information for a serving cell of a cellular network, the location information including an identifier of a reduced capability serving cell or a private network cell; and communicating with the serving cell according to a configuration that is based at least in part on the location information that is provided to the UICC.

13. The method of claim 12, wherein providing the location information for the serving cell comprises: transmitting a terminal response message for providing local information, the terminal response message including the identifier of the reduced capability serving cell or the private network cell.

14. The method of claim 12, wherein providing the location information for the serving cell comprises: transmitting an envelope command for event download location status or for a network rejection event, the envelope command including the identifier of the reduced capability serving cell or the private network cell.

15. The method of claim 12, wherein: the location information further comprises a closed access group identifier (CAG ID) without a CAG ID type for the CAG ID; the location information comprises a network identifier (NID) without an NID type for the NID; or the location information comprises an indication that the UE is a reduced capability UE, that the serving cell is a closed access group (CAG) cell, or that the serving cell is a standalone non-public network, and the indication is without a corresponding one or more of the CAG ID or the NID.

16. The method of claim 12, wherein providing the location information for the serving cell comprises: transmitting a closed access group (CAG) cell selection status message that indicates a closed access group identifier (CAG ID), the location information comprising the CAG ID.

17. A user equipment (UE) comprising: a transceiver; a universal integrated circuit card (UICC); and a processor configured to cause the UE to, provide, to the UICC, location information for a serving cell of a cellular network, the location information including an identifier of a reduced capability serving cell or a private network cell; andcommunicate, via the transceiver, with the serving cell according to a configuration that is based at least in part on the location information that is provided to the UICC.

18. The UE of claim 17, wherein the processor configured to cause the UE to provide the location information for the serving cell comprises the processor further configured to cause the UE to: transmit a terminal response message for providing location information, the terminal response message including the identifier of the reduced capability serving cell or the private network cell.

19. The UE of claim 17, wherein the UE further comprises a universal subscriber identity module (USIM) associated with the UICC, and wherein the processor is configured to: initialize the USIM associated with the UICC for communication with the cellular network; and register, using the transceiver, with the cellular network according to subscriber information of the USIM.

20. The UE of claim 19, wherein the USIM comprises one or both of a physical subscriber identity module (SIM) card, or an embedded SIM (eSIM).

Images