Attention commands for multiple subscriber identity module devices - Patents.com

Abstract

A technique for multiple universal subscriber identity module (MUSIM) operation includes generating an attention (AT) command by a terminal equipment (TE) of a device. The AT command indicates values ​​of parameters related to the MUSIM operation of the device, such as whether to release a non-access stratum (NAS) connection associated with a particular USIM of the device, whether to reject or restrict paging associated with a particular USIM of the device, or a requested (or selected) IMSI offset associated with a particular USIM of the device. The AT command is communicated from the TE to a mobile terminal (MT) of the device via a terminal adapter (TA).

Description

[Technical field]

[0001] Claiming priority This application claims priority to Indian Patent Application No. 202111049667 filed on October 29, 2021.

[0002] The present disclosure relates generally to attention (AT) commands for wireless devices such as multiple universal subscriber identity module (MUSIM) devices. [Background technology]

[0003] In many wireless communication networks, such as cellular networks, users subscribe to a service provider (sometimes called a "carrier"), which provides services to users over the wireless communication network that it operates. To identify and authenticate a subscriber, each subscriber may be assigned a subscriber identity, such as an International Mobile Subscriber Identity (IMSI) number and its associated key. This information may be securely stored within the subscriber's wireless device, such as on a Universal Integrated Circuit Card (UICC) inserted or embedded in the wireless device, as part of a Subscriber Identity Module (SIM) or Universal SIM (USIM).

[0004] In some cases, a user may want to have multiple subscriptions with one or more carriers on a single wireless device. For example, a user may want to have separate personal and business subscriptions without having to carry multiple wireless devices. To support this functionality, some wireless devices may include multiple USIMs on the same or different UICCs, thereby allowing a user to register with and communicate over networks associated with each USIM on a single wireless device. Summary of the Invention

[0005] The techniques described herein facilitate MUSIM operation by allowing MUSIM devices to set and retrieve values ​​for MUSIM-related parameters based on their capabilities. In particular, new AT commands are defined that allow the Terminal Equipment (TE) of a MUSIM device to control the Mobile Termination (MT) capabilities of that device to set and / or retrieve parameter values ​​for various MUSIM features, including Non-Access Stratum (NAS) Connection Release, Paging Cause Indication for Voice, Rejection of Paging Request, Paging Restrictions, and Paging Timing Collision Control. By defining a standard means by which MUSIM devices can set and / or retrieve values ​​for MUSIM-related parameters, the techniques improve MUSIM operation by, for example, reducing collisions between communications associated with separate USIMs, preventing interruptions that disrupt the user experience, and enabling more efficient allocation of device and network resources.

[0006] In general, in a first aspect, the device is a processing circuit including a TE, a MT, and a TA, the processing circuit including processing circuitry for generating, by the TE, an AT command indicating a value of a parameter related to MUSIM operation of the device, and communicating the AT command from the TE to the MT via the TA, and a memory for storing data related to the value of the parameter related to MUSIM operation of the device.

[0007] In general, in a second aspect, a method includes generating, by a TE of a device, an AT command indicating a value of a parameter related to a MUSIM operation of the device, and communicating the AT command from the TE to an MT of the device via a TA.

[0008] In general, in a third aspect, at least one non-transitory computer-readable medium stores instructions executable by at least one processor to perform operations including generating, by a TE of a device, an AT command indicating a value of a parameter related to a MUSIM operation of the device, and communicating the AT command from the TE to an MT of the device via a TA.

[0009] In general, in a fourth aspect combinable with any of the first to third aspects, the parameters include a NAS connection release parameter, a value of the NAS connection release parameter indicating whether to release a NAS connection between the device and the network node.

[0010] Generally, in a fifth aspect combinable with the fourth aspect, the MT indicates to the network node whether to release a NAS connection between the device and the network node based on a value of a NAS connection release parameter.

[0011] In a sixth aspect which may be generally combined with any of the first to fifth aspects, the parameters include a paging reject parameter, a value of the paging reject parameter indicating whether to reject paging of the device by the network node.

[0012] Generally, in a seventh aspect combinable with the sixth aspect, the MT indicates to the network node whether the device has rejected a paging based on a value of a paging rejection parameter.

[0013] In an eighth aspect, which may generally be combined with any of the first to seventh aspects, the parameters include a paging restriction parameter, and a value of the paging restriction parameter indicates whether paging is not restricted, all paging is restricted, all paging is restricted except for voice services, all paging is restricted except for a specified public data network (PDN) connection or protocol data unit (PUD) session, or all paging is restricted except for voice services and a specified PDN connection or PDU session.

[0014] Generally, in a ninth aspect combinable with the eighth aspect, values ​​of one or more other paging restriction parameters indicate a specified PDN connection or PDU session.

[0015] Generally, in a tenth aspect combinable with the eighth aspect, the MT indicates one or more paging restrictions to a network node based on a value of a paging restriction parameter.

[0016] In an eleventh aspect which may be generally combined with any of the first to tenth aspects, the parameters include a paging collision parameter, a value of the paging collision parameter indicating whether to present an unsolicited return code in response to a change in an IMSI offset associated with the device.

[0017] In general, in a twelfth aspect which can be combined with any of the first to eleventh aspects, the parameters include a paging collision parameter, and a value of the paging collision parameter indicates a requested IMSI offset for the device or a selected IMSI offset for the device.

[0018] Generally, in a thirteenth aspect which may be combined with any of the first to twelfth aspects, the MT sends a message to a network node based on a value of a parameter during an Evolved Packet System Mobility Management (EMM) tracking area update procedure or a service request procedure, or during a 5G Mobility Management (5GMM) registration request procedure or a service request procedure.

[0019] In general, in a fourteenth aspect combinable with any of the first to thirteenth aspects, an AT command response is communicated from the MT to the TE via the TA in response to the AT command.

[0020] The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings, and from the claims. [Brief description of the drawings]

[0021] [Figure 1] 1 illustrates an example of a wireless communication system.

[0022] [Diagram 2] 1 shows an example of infrastructure equipment.

[0023] [Diagram 3] An example of a device is shown.

[0024] [Figure 4] 1 illustrates an exemplary architecture of a device.

[0025] [Diagram 5] 1 illustrates an exemplary process for setting and / or retrieving values ​​for MUSIM-related parameters.

[0026] Like reference symbols in the various drawings indicate like elements. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] FIG. 1 illustrates an example of a wireless communication system 100. For convenience, but not by way of limitation, the exemplary system 100 is described in the context of Long Term Evolution (LTE) and Fifth Generation (5G) New Radio (NR) communication standards defined by the 3rd Generation Partnership Project (3GPP) Technical Specifications (TS). More specifically, the wireless communication system 100 is described in the context of a non-standalone (NSA) network incorporating both LTE and NR, such as an Evolved Universal Terrestrial Radio Access (E-UTRA)-NR Dual Connectivity (EN-DC) network and a NE-DC network. However, the wireless communication system 100 may be a stand-alone (SA) network incorporating only NR. Additionally, other types of communication standards are possible, including future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0028] As shown in FIG. 1, the system 100 includes a UE 101a and a UE 101b (collectively referred to as "UE 101"). In this example, UE 101 is illustrated as a smartphone (e.g., a portable touchscreen mobile computing device capable of connecting to one or more cellular networks), but may include any mobile or non-mobile computing device, such as a consumer electronic device, a mobile phone, a smartphone, a feature phone, a tablet computer, a wearable computing device, a personal digital assistant (PDA), a pager, a wireless handset, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-car entertainment (ICE) device, an instrument cluster (IC), a head-up display (HUD) device, an on-board diagnostics (OBD) device, a dashtop mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine control unit (ECU), an electronic engine / engine control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a networked or "smart" appliance, an MTC device, an M2M, an IoT device, and / or the like.

[0029] The UE 101 may be configured to connect, e.g., communicatively couple, with the RAN 110 or multiple RANs 110 (e.g., when the UE 101 is a MUSIM UE). In some examples, the RAN 110 may be an NG RAN or a 5G RAN, an E-UTRAN, or a legacy RAN such as a UTRAN or a GERAN. As used herein, the term "NG RAN" or the like may refer to a RAN 110 operating in an NR or 5G system 100, and the term "E-UTRAN" or the like may refer to a RAN 110 operating in an LTE or 4G system 100. The UE 101 utilizes connections (or channels) 103 and 104, respectively, each of which includes a physical communication interface or layer (described in more detail below).

[0030] In this example, the connections 103 and 104 are shown as air interfaces for enabling communication coupling and may correspond to a cellular communication protocol such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, an Advanced Long Term Evolution (LTE-A) protocol, an LTE-based access to unlicensed spectrum (LTE-U), a 5G protocol, an NR protocol, an NR-based access to unlicensed spectrum (NR-U) protocol, and / or any of the other communication protocols described herein. In some examples, the UE 101 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as an SL interface 105 and may comprise one or more logical channels, including, but not limited to, a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

[0031] The UE 101b is shown configured to access the AP 106 (also referred to as "WLAN node 106", "WLAN 106", "WLAN termination 106", "WT 106", etc.) via a connection 107. The connection 107 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, and the AP 106 may comprise a Wireless Fidelity (WiFi) router. In this example, the AP 106 is connected to the Internet without connecting to a wireless system core network, as shown (described in further detail below). In various examples, the UE 101b, the RAN 110, and the AP 106 may be configured to utilize LWA and / or LWIP operations. LWA operations may involve the UE 101b being RRC connected, configured by the RAN nodes 111a-111b to utilize LTE and WLAN radio resources. LWIP operations may involve UE 101b using WLAN radio resources (e.g., connection 107) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over connection 107. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the IP packet's original header.

[0032] The RAN 110 may include one or more AN or RAN nodes 111a and 111b (collectively referred to as "RAN nodes 111") that enable the connections 103 and 104. As used herein, the terms "access node", "access point", etc. may refer to equipment that provides wireless baseband functionality for data and / or voice connectivity between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, TRPs, etc., and may include terrestrial stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, terms such as "NG RAN node" may refer to a RAN node 111 operating in an NR or 5G system 100 (e.g., gNB), and terms such as "E-UTRAN node" may refer to a RAN node 111 operating in an LTE or 4G system 100 (e.g., eNB). According to various examples, the RAN node 111 may be implemented as one or more of dedicated physical devices, such as a macrocell base station and / or a low power (LP) base station to provide a femtocell, picocell, or other like cell having a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0033] In some examples, all or part of the RAN node 111 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these examples, the CRAN or vBBUP may implement a RAN functionality split such as a PDCP split where the RRC and PDCP layers are operated by the CRAN / vBBUP and other L2 protocol entities are operated by the individual RAN nodes 111, a MAC / PHY split where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP and the PHY layer is operated by the individual RAN nodes 111, or a "lower PHY" split where the RRC, PDCP, RLC, MAC, and upper parts of the PHY layer are operated by the CRAN / vBBUP and lower parts of the PHY layer are operated by the individual RAN nodes 111. This virtualized framework allows freed processor cores of the RAN node 111 to run other virtualized applications. In some examples, each RAN node 111 may represent an individual gNB-DU connected to a gNB-CU via an individual F1 interface (not shown by FIG. 1). In some examples, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., FIG. 2), and the gNB-CU may be operated by a server located in the RAN 110 (not shown) or by a server pool in a manner similar to the CRAN / vBBUP. Additionally or alternatively, one or more of the RAN nodes 111 may be a Next Generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminations towards the UE 101 and is connected to the 5GC via an NG interface (described below).

[0034] Any of the RAN nodes 111 may terminate the air interface protocols and may be the first point of contact for the UE 101. In some examples, any of the RAN nodes 111 may perform various logical functions for the RAN 110, including, but not limited to, Radio Network Controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0035] In some examples, the UEs 101 may be configured to communicate with either one another or the RAN nodes 111 using OFDM communication signals over multi-carrier communication channels according to various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communications) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communications), and the scope of the embodiments is not limited in this respect. OFDM signals may include multiple orthogonal subcarriers.

[0036] In some examples, a downlink resource grid may be used for downlink transmissions from any of the RAN nodes 111 to the UE 101, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, called a resource grid or a time-frequency resource grid, which is the physical resources of the downlink in each slot. Such a time-frequency plane representation is common in OFDM systems, making the allocation of radio resources intuitive. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit of the resource grid is denoted as a resource element. Each resource grid contains a number of resource blocks, which represent the mapping of a particular physical channel to the resource elements. Each resource block contains a set of resource elements, which in the frequency domain may represent the smallest amount of resources that can currently be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[0037] According to various examples, the UE 101 and the RAN node 111 communicate (e.g., transmit and receive) data over a licensed medium (also referred to as a “licensed spectrum” and / or “licensed band”) and an unlicensed shared medium (also referred to as an “unlicensed spectrum” and / or “unlicensed band”). The licensed spectrum may include channels operating in a frequency range from about 400 MHz to about 3.8 GHz, and the unlicensed spectrum may include the 5 GHz band. NR in the unlicensed spectrum may be referred to as NR-U, and LTE in the unlicensed spectrum may be referred to as LTE-U, licensed assisted access (LAA), or MulteFire. To operate in the unlicensed spectrum, the UE 101 and the RAN node 111 may operate using LAA, eLAA, and / or feLAA mechanisms. In some examples, the UE 101 and the RAN node 111 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operation may be performed according to a Listen-Before-Talk (LBT) protocol.

[0038] In some examples, a physical downlink shared channel (PDSCH) carries user data and higher layer signaling to the UE 101. In some examples, a physical downlink control channel (PDCCH) carries, among other things, information regarding transport format and resource allocation for the PDSCH channel. It may also inform the UE 101 about transport format, resource allocation, and HARQ information for the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to the UEs 101b in the cell) may be performed in any of the RAN nodes 111 based on channel quality information fed back from any of the UEs 101. The downlink resource allocation information may be transmitted in the PDCCH used (e.g., assigned) for each of the UEs 101.

[0039] The PDCCH conveys control information using CCEs. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets and then permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, and each CCE may correspond to nine sets of four physical resource elements known as REGs. Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH may be transmitted using one or more CCEs depending on the size of the DCI and the channel conditions. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0040] Some examples may use a concept for resource allocation for control channel information that is an extension of the concept above. For example, some examples may utilize an EPDCCH that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more ECCEs. As above, each ECCE may correspond to nine sets of four physical resource elements known as EREGs. An ECCE may have other numbers of EREGs in some situations.

[0041] The RAN nodes 111 may be configured to communicate with each other via the interface 112. In an example where the system 100 is an LTE system, the interface 112 may be an X2 interface 112. The X2 interface may be defined between two or more RAN nodes 111 (e.g., two or more eNBs) that connect to the EPC 120 and / or between two eNBs that connect to the EPC 120. In some examples, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user data packets forwarded over the X2 interface and may be used to communicate information regarding delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information for user data forwarded from the MeNB to the SeNB, information regarding successful sequence delivery of PDCP PDUs from the SeNB to the UE 101 for user data, information regarding PDCP PDUs that were not delivered to the UE 101, information regarding a current minimum desired buffer size at the SeNB for transmitting UE user data, etc. X2-C may provide intra-LTE access mobility functions, load management functions, and inter-cell interference coordination functions, including context transfer from source eNB to target eNB, user plane transport control, etc.

[0042] In an example where the system 100 is a 5G or NR system, the interface 112 may be an Xn interface 112. The Xn interface is defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) that connect to the 5GC 120, between a RAN node 111 (e.g., a gNB) and an eNB that connect to the 5GC 120, and / or between two eNBs that connect to the 5GC 120. In some examples, the Xn interface may include an Xn User Plane (Xn-U) interface and an Xn Control Plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data transfer and flow control functions. The Xn-C may provide mobility support for the UE 101 in connected mode (e.g., CM-CONNECTED), including management and error handling functions, functions for managing the Xn-C interface, and functions for managing UE mobility for connected mode between one or more RAN nodes 111. Mobility support may include context transfer from the old (source) serving RAN node 111 to the new (target) serving RAN node 111 and control of user plane tunnels between the old (source) serving RAN node 111 and the new (target) serving RAN node 111. To carry user plane PDUs, the protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer and a GTP-U layer on top of UDP and / or IP layer(s). The Xn-C protocol stack may include an application layer signaling protocol (called Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may be on top of the IP layer and may provide guaranteed delivery of application layer messages. At the transport IP layer, point-to-point transmission is used to deliver signaling PDUs.In some examples, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stack(s) shown and described herein.

[0043] The RAN 110 is shown communicatively coupled to a core network, in this example, a core network (CN) 120. The CN 120 may comprise a number of network elements 122 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UEs 101) connected to the CN 120 via the RAN 110. The components of the CN 120 may be implemented in a single physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some examples, NFV may be utilized to virtualize any or all of the network node functions described above via executable instructions stored in one or more computer-readable storage media (described in more detail below). A logical instantiation of the CN 120 may be referred to as a network slice, and a logical instantiation of a portion of the CN 120 may be referred to as a network sub-slice. The NFV architecture and infrastructure may be used to virtualize one or more network functions on physical resources including a combination of industry-standard server hardware, storage hardware, or switches, or may be performed by dedicated hardware. In other words, an NFV system can be used to execute a virtual or reconfigurable implementation of one or more EPC components / functions.

[0044] In general, the application server 130 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 130 may also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 101 via the EPC 120.

[0045] In some examples, the CN 120 may be a 5GC (e.g., referred to as "5GC 120"), and the RAN 110 may be connected to the CN 120 via an NG interface 113. In some examples, the NG interface 113 may be split into two parts: an NG User Plane (NG-U) interface 114, which carries traffic data between the RAN node 111 and the UPF, and an S1 Control Plane (NG-C) interface 115, which is a signaling interface between the RAN node 111 and the AMF.

[0046] In some examples, the CN 120 may be a 5G CN (referred to as "5GC 120" or the like), and in other examples, the CN 120 may be an EPC. When the CN 120 is an EPC (referred to as "EPC 120" or the like), the RAN 110 may be connected to the CN 120 via an S1 interface 113. In some examples, the S1 interface 113 may be split into two parts: an S1 user plane (S1-U) interface 114 that carries traffic data between the RAN node 111 and the S-GW, and an S1-MME interface 115 that is a signaling interface between the RAN node 111 and the MME.

[0047] 2 illustrates an example of infrastructure equipment 200 according to various examples. Infrastructure equipment 200 (or "system 200") may be implemented as a base station, a radio head, a RAN node such as RAN node 111 and / or AP 106 illustrated and described above, application server(s) 130, and / or any other element / device described herein. In other examples, system 200 may be implemented within or by a UE.

[0048] System 200 includes application circuitry 205, baseband circuitry 210, one or more Radio Front End Modules (RFEM) 215, memory circuitry 220, Power Management Integrated Circuitry (PMIC) 225, power T circuitry 230, network controller circuitry 235, network interface connector 240, satellite positioning circuitry 245, and user interface 250. In some examples, device 200 may include additional elements, such as memory / storage, a display, a camera, sensors, or input / output (I / O) interfaces. In other examples, the components described below may be included in two or more devices. For example, the circuits may be included separately in two or more devices for CRAN, vBBU, or other similar implementations.

[0049] The application circuitry 205 may include, but is not limited to, one or more of the following circuits: a low drop-out voltage regulator (LDO), an interrupt controller, a serial interface such as an SPI, I2C, or a universal programmable serial interface module, a timer counter including a real time clock (RTC), an interval timer, and a watchdog timer, a general purpose input / output (I / O or IO), a memory card controller such as a Secure Digital (SD) Multi Media Card (MMC), a Universal Serial Bus (USB) interface, a Mobile Industry Processor Interface (MIPI), and a Joint Test Access Group (JTAG) test access port. The processor (or core) of the application circuitry 205 may be coupled to or may include memory / storage elements and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the system 200. In some examples, the memory / storage elements may be on-chip memory circuits, which may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology as described herein.

[0050] The processor(s) of application circuitry 205 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphic processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some examples, application circuitry 205 may comprise or be a dedicated processor / controller for operating in accordance with various examples herein. By way of example, the processor(s) of application circuit 205 may include one or more Apple A-series processors, Intel Pentium®, Core®, or Xeon® processor(s), Advanced Micro Devices (AMD) Ryzen® processor(s), Accelerated Processing Unit (APU), or Epyc® processor, ARM-based processor(s) licensed from ARM Holdings Ltd., such as the ARM Cortex-A family processors and ThunderX2® offered by Cavium™, Inc., MIPS-based designs by MIPS Technologies, Inc., such as the MIPS Warrior P-class processor, etc. In some examples, system 200 may not utilize application circuit 205 and instead may include a dedicated processor / controller for processing IP data received from, for example, an EPC or 5GC.

[0051] In some examples, the application circuitry 205 may include one or more hardware accelerators, which may be a microprocessor, a programmable processing device, or the like. The one or more hardware accelerators may include, for example, a computer vision (CV) and / or a deep learning (DL) accelerator. By way of example, the programmable processing device may be one or more of a field programmable device (FPD), such as a field programmable gate array (FPGA), a programmable logic device (PLD), such as a complex PLD (CPLD), a high capacity PLD (HCPLD), an ASIC, such as a structured ASIC, a programmable SoC (PSoC), or the like. In some examples, the circuitry of the application circuitry 205 may comprise logic blocks or logic fabrics and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions of various embodiments described herein. In such examples, the circuitry of application circuit 205 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), antifuses, etc.)) used to store logic blocks, logic fabric, data, etc., in look-up tables (LUTs), etc.

[0052] The baseband circuitry 210 may include circuitry and / or control logic configured to execute various wireless / network protocols and wireless control functions that enable communication with one or more wireless networks via RF circuitry. In some examples, the baseband circuitry 210 may be implemented as, for example, a soldered board containing one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0053] User interface circuitry 250 may include one or more user interfaces designed to enable user interaction with system 200 or peripheral component interfaces designed to enable peripheral component interaction with system 200. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, a speaker or other audio light emitting device, a microphone, a printer, a scanner, a headset, a display screen or device, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0054] The radio front-end module (RFEM) 215 may comprise a millimeter-wave (mm-wave) RFEM and one or more sub-mm-wave radio frequency integrated circuits (RFICs). In some examples, the one or more sub-mm-wave RFICs may be physically separate from the mm-wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In some examples, both mm-wave and sub-mm-wave wireless functions may be implemented within the same physical RFEM 215 that incorporates both mm-wave and sub-mm-wave antennas.

[0055] The memory circuit 220 may include one or more of volatile memory including dynamic random access memory (DRAM) and / or synchronous dynamic random access memory (SDRAM), and non-volatile memory (NVM) including high speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), and the like, and may incorporate Intel® and Micron® three-dimensional (3D) cross point (XPOINT) memory. The memory circuit 220 may be implemented as one or more of a solder packaged integrated circuit, a socketed memory module, and a plug-in memory card.

[0056] The PMIC 225 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or a capacitor. The power alarm detection circuit may detect one or more of brownout (under-voltage) and surge (over-voltage) conditions. The power T-circuit 230 may supply power drawn from a network cable that provides both power and data connectivity to the infrastructure equipment 200 using a single cable.

[0057] The network controller circuitry 235 may provide connectivity to a network using a standard network interface protocol, such as Ethernet, Ethernet over a GRE tunnel, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to / from the infrastructure equipment 200 via the network interface connectors 240 using a physical connection that may be electrical (commonly referred to as "copper wiring"), optical, or wireless. The network controller circuitry 235 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some examples, the network controller circuitry 235 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0058] The positioning circuitry 245 includes circuitry for receiving and decoding signals transmitted / broadcast by a positioning network of a Global Navigation Satellite System (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States Global Positioning System (GPS), the Russian Global Navigation System (GLONASS), the European Union's Galileo system, the Chinese Beidou navigation satellite system, regional navigation systems or GNSS augmentation systems (e.g., Navigation by Indian Constellation (NAVIC), the Japanese Quasi-Zenith Satellite System (QZSS), the French Doppler Orbitography and Radio positioning Integrated by Satellite (DORIS), etc.). The positioning circuitry 245 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. to facilitate OTA communication) for communicating with components of the positioning network, such as navigation satellite constellation nodes. In some examples, the positioning circuitry 245 may include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC for performing position tracking / estimation without GNSS assistance using a master timing clock. The positioning circuitry 245 may also be part of or interact with the baseband circuitry 210 and / or the RFEM 215 to communicate with nodes and components of a positioning network. The positioning circuitry 245 may also provide position and / or time data to the application circuitry 205, which may use the data to synchronize operations with various infrastructures (e.g., RAN nodes 111, etc.), etc.

[0059] The components shown in FIG. 2 can communicate with each other using interface circuitry that may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX may be a proprietary bus used in SoC-based systems, for example. Other bus or IX systems may be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, among others.

[0060] FIG. 3 illustrates an example of a platform 300 (or "device 300") according to various examples. In some examples, the computer platform 300 may be suitable for use as the UE 101, the application server 130, and / or any other element / device described herein. The platform 300 may include any combination of components illustrated in the examples. The components of the platform 300 may be implemented as an integrated circuit (IC) adapted to the computer platform 300, a portion thereof, a separate electronic device, or other module, logic, hardware, software, firmware, or a combination thereof, or as components otherwise incorporated within a chassis of a larger system. The block diagram of FIG. 3 is intended to illustrate an overhead view of the components of the computer platform 300. However, some of the components illustrated may be omitted, additional components may be present, and different arrangements of the illustrated components may occur in other implementations.

[0061] The application circuitry 305 includes, but is not limited to, one or more processors (or processor cores), cache memory, and circuits such as one or more LDOs, interrupt controllers, serial interfaces such as SPI, I2C, or universal programmable serial interface modules, timer counters including RTC, interval and watchdog timers, general purpose I / O, memory card controllers such as SD MMC, USB interface, MIPI interface, and JTAG test access port. The processors (or cores) of the application circuitry 305 may be coupled to memory / storage devices and may include memory / storage elements and may be configured to execute instructions stored in the memory / storage devices to enable various applications or operating systems to run on the system 300. In some examples, the memory / storage elements may be on-chip memory circuits, which may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid state memory, and / or any other type of memory device technology as described herein.

[0062] The processor(s) of application circuitry 205 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some examples, application circuitry 205 may comprise or be a dedicated processor / controller for operating in accordance with various examples herein.

[0063] By way of example, the processor(s) of application circuit 305 may include an Apple A-series processor. The processor of the application circuit 305 may also include one or more of an Intel® architecture core-based processor, such as a Quark®, Atom®, i3, i5, i7, or MCU class processor, or another such processor available from Intel® Corporation of Santa Clara, Calif., an Advanced Micro Devices (AMD) Ryzen processor(s) or accelerated processing unit (APU), one or more Snapdragon™ processor(s) from Qualcomm® Technologies Inc., one or more Open Multimedia Application Platform (OMAP)™ processor(s) from Texas Instruments®, or MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors, ARM-based designs licensed from ARM Holdings, Ltd, such as the ARM Cortex-A, Cortex-R, and Cortex-M families of processors, and the like. In some examples, the application circuit 305 may be part of a system-on-chip (SoC) in which the application circuit 305 and other components are formed within a single integrated circuit.

[0064] Additionally or alternatively, the application circuitry 305 may include circuitry such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, programmable logic devices (PLDs) such as composite PLDs (CPLDs) or high performance PLDs (HCPLDs), ASICs such as structured ASICs, programmable SoCs (PSoCs), etc. In such examples, the circuitry of the application circuitry 305 may comprise logic blocks or logic fabrics and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, and functions of various embodiments described herein. In such examples, the circuitry of the application circuitry 305 may include memory cells (e.g., erasable programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.) used to store logic blocks, logic fabric, data, etc., such as in look-up tables (LUTs).

[0065] The baseband circuitry 310 includes circuitry and / or control logic configured to perform various wireless / network protocols and wireless control functions that enable communication with one or more wireless networks via RF circuitry. In some examples, the baseband circuitry 310 may be implemented as, for example, a soldered board containing one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0066] The RFEM 315 may comprise a millimeter-wave (mm-wave) RFEM and one or more sub-mm-wave radio frequency integrated circuits (RFICs). In some examples, the one or more sub-mm-wave RFICs may be physically separate from the mm-wave RFEM. The RFIC may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In some examples, both mm-wave and sub-mm-wave wireless functions may be implemented within the same physical RFEM 315 that incorporates both mm-wave and sub-mm-wave antennas.

[0067] The memory circuit 320 may include any number and type of memory devices used to provide a given amount of system memory. By way of example, the memory circuit 320 may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (SDRAM), and non-volatile memory (NVM) including high speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 320 may be developed according to a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR) based design, such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 320 may be implemented as one or more of a solder package integrated circuit, a single die package (SDP), a dual die package (DDP) or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered onto a motherboard via a ball grid array (BGA). In a low power implementation, the memory circuit 320 may be an on-die memory or register associated with the application circuit 305. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 320 may include one or more mass storage devices, which may include a solid state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive memory, a phase change memory, a holographic memory, or a chemical memory, among others. For example, the computer platform 300 may incorporate three-dimensional (3D) cross point (XPOINT) memory from Intel® and Micron®.

[0068] The removable memory circuitry 323 may include devices, circuits, enclosures, ports or receptacles, etc. used to couple portable data storage devices with the platform 300. These portable data storage devices may be used for mass storage purposes and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD image cards, etc.), USB flash drives, optical disks, external HDDs, etc.

[0069] Platform 300 may also include interface circuitry (not shown) used to connect external devices with platform 300. External devices connected to platform 300 via the interface circuitry include sensor circuitry 321 and electromechanical components (EMC) 322, as well as a removable memory device coupled to removable memory circuitry 323.

[0070] The sensor circuitry 321 may include devices, modules, or subsystems intended to detect events or changes in the environment and transmit information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others, inertial measurement units (IMUs) including accelerometers, gyroscopes, and / or magnetometers, microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes, and / or magnetometers, level sensors, flow sensors, temperature sensors (e.g., thermistors), pressure sensors, barometric pressure sensors, gravimeters, altimeters, image capture devices (e.g., cameras or lensless apertures), light detection and ranging (LiDAR) sensors, proximity sensors (e.g., infrared detectors, etc.), depth sensors, ambient light sensors, ultrasonic transceivers, microphones or other similar audio capture devices, etc.

[0071] EMC 322 includes devices, modules, or subsystems whose purpose is to enable platform 300 to change its state, position, and / or orientation, or to move or control mechanisms or (sub)systems. Additionally, EMC 322 may be configured to generate and send messages / signaling to other components of platform 300 to indicate the current state of EMC 322. Examples of EMC 322 include one or more power switches, relays including electromechanical relays (EMRs) and / or solid-state relays (SSRs), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and / or other similar electromechanical components. In some examples, platform 300 is configured to operate one or more EMCs 322 based on one or more captured events and / or commands or control signals received from service providers and / or various clients.

[0072] In some examples, the interface circuitry may connect the platform 300 with the positioning circuitry 345. The positioning circuitry 345 includes circuitry for receiving and decoding signals transmitted / broadcast by a GNSS positioning network. Examples of navigation satellite constellations (or GNSS) include the United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's Beidou navigation satellite system, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, Japan's QZSS, France's DORIS, etc.), and the like. The positioning circuitry 345 includes various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. to facilitate OTA communications) for communicating with components of the positioning network, such as navigation satellite constellation nodes. In some examples, the positioning circuitry 345 may include a Micro-PNT IC for performing position tracking / estimation without GNSS assistance using a master timing clock. The positioning circuitry 345 may also be part of or interact with the baseband circuitry 210 and / or the RFEM 315 to communicate with nodes and components of a positioning network. The positioning circuitry 345 may also provide position and / or time data to the application circuitry 305, which may use the data to synchronize operation with various infrastructures (e.g., wireless base stations), such as for turn-by-turn navigation applications.

[0073] In some examples, the interface circuit may connect the platform 300 with a near field communication (NFC) circuit 340. The NFC circuit 340 is configured to provide contactless short-range communication based on the Radio Frequency Identification (RFID) standard, and magnetic field induction is used to enable communication between the NFC circuit 340 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 300. The NFC circuit 340 comprises an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides the NFC circuit 340 with NFC functionality by executing the NFC controller firmware and the NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit a near-field RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 340, or may initiate data transfer between the NFC circuitry 340 and another active NFC device (e.g., a smartphone or NFC-enabled POS terminal) in proximity to the platform 300.

[0074] The driver circuitry 346 may include software and hardware elements that operate to control particular devices embedded in, attached to, or otherwise communicatively coupled to the platform 300. The driver circuitry 346 may include individual drivers that allow other components of the platform 300 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 300. For example, the driver circuitry 346 may include a display driver that allows control of and access to a display device, a touchscreen driver that allows control of and access to a touchscreen interface of the platform 300, a sensor driver that obtains sensor readings of the sensor circuitry 321 and allows control of and access to the sensor circuitry 321, an EMC driver that obtains actuator positions of the EMC 322 and allows control of and access to the EMC 322, a camera driver that allows control of and access to an embedded image capture device, and an audio driver that allows control of and access to one or more audio devices.

[0075] A power management integrated circuit (PMIC) 325 (also referred to as "power management circuit 325") may manage the power supplied to various components of platform 300. Specifically, with respect to baseband circuit 310, PMIC 325 may control power source selection, voltage scaling, battery charging, or DC-DC conversion. For example, PMIC 325 may be included in many cases when platform 300 can be powered by battery 330, such as when the device is included in UE 101.

[0076] The battery 330 may power the platform 300, although in some examples the platform 300 may be deployed and mounted at a fixed location and may have a power source tied to an electrical grid. The battery 330 may be a lithium ion battery, a metal air battery such as a zinc air battery, an aluminum air battery, a lithium air battery, etc. In some examples, such as in V2X applications, the battery 330 may be a typical lead acid automobile battery.

[0077] User interface circuitry 350 includes various input / output (I / O) devices present in or connected to platform 300 and may include one or more user interfaces designed to enable user interaction with platform 300 and / or peripheral component interfaces designed to enable peripheral component interaction with platform 300. User interface circuitry 350 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input including, among others, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying or otherwise communicating information, such as a sensor reading, an actuator position(s), or other similar information. The output device circuitry may include any number and / or combination of audio or visual displays, among others, one or more simple visual outputs / indicators, such as binary status indicators (e.g., light emitting diodes (LEDs)), and multi-character visual outputs or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where output such as characters, graphics, multimedia objects, etc. are generated or created from operation of the platform 300. The output device circuitry may also include speakers or other audio emitting devices, printer(s), and / or the like. In some examples, the sensor circuitry 321 may be used as an input device circuitry (e.g., an image capture device, a motion capture device, etc.), and one or more EMCs may be used as output device circuitry (e.g., an actuator for providing haptic feedback, etc.). In another example, an NFC circuitry comprising an NFC controller coupled to an antenna element and a processing device may be included for reading an electronic tag and / or connecting with another NFC-enabled device.The peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power interface, and the like.

[0078] Although not shown, the components of platform 300 can communicate with each other using a suitable bus or interconnect (IX) technology, which may include any number of technologies including ISA, EISA, PCI, PCIx, PCIe, a time-triggered protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus / IX may be, for example, a proprietary bus / IX used in an SoC-based system. Other bus or IX systems may be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus.

[0079] As described above, a device (e.g., UE 101 or device 300) can support multiple USIMs from the same or different service providers to allow a user to communicate over a network associated with each USIM. Currently, multi-USIM (MUSIM) operation is supported in an implementation-specific manner, with each implementation having a different behavior. Since MUSIM devices share radio and baseband resources across USIMs, the lack of standardization for MUSIMs can lead to various problems. For example, while communicating with a first system associated with a first USIM, the MUSIM device may sometimes need to monitor communications from a second system associated with a second USIM to read system information, perform signal measurements, or respond to paging, which may cause interruptions to ongoing services with the first system. As another example, if the MUSIM device cannot interrupt ongoing activity with the first system when responding to a page from the second system, the MUSIM device may need to drop a connection (e.g., an RRC connection) with the first system to stop activity on the first system, thereby degrading the user experience and wasting network resources. Similarly, when the MUSIM device receives a page on the second system, without additional information about the service type that triggered the page, the MUSIM device may not know how to respond. As another example, paging collisions due to the same wireless device identifier (e.g., IMSI) value being used for communications associated with both USIMs can lead to missed pages.

[0080] To promote more predictable MUSIM device behavior and improve MUSIM performance, 3GPP has undertaken to standardize aspects of MUSIM operation. In particular, 3GPP has undertaken to define operation procedures for various MUSIM-related functions (e.g., in 3GPP TS 22.101, TS 22.261, and TS 22.278, among others), including, among others, NAS connection release, paging cause indication for voice, rejection of paging requests, paging restrictions, and paging timing collision control. For NAS connection release, it has been agreed (e.g., in 3GPP TS 23.501 and TS 23.502) that the NAS connection may be released and the MUSIM device may transition to an idle state on one USIM due to activity on another USIM. For paging cause indication for voice, it has been agreed (e.g., in 3GPP TS 23.501) that the network provides an indication for voice services in a paging message. For rejection of paging requests, it has been agreed (e.g., in 3GPP TS 23.501 and TS 23.502) that a MUSIM device can indicate to the network that it is unable to respond to pages for a particular USIM(s) and can request to be released to idle mode. For paging restrictions, it has been agreed (e.g., in 3GPP TS 23.501) that a MUSIM device and network can support paging restrictions including, among others, all paging restrictions, all paging restrictions except paging for voice services (e.g., MMTel voice or CS domain voice), all paging restrictions except for a particular public data network (PDN) or packet data unit (PDU) connection(s), and all paging restrictions except for a particular PDN / PDU connection(s) and voice service (e.g., MMTel voice or CS domain voice).For paging timing collision control, it has been agreed (eg, in 3GPP TS 23.501) that MUSIM devices and networks can negotiate an IMSI offset to avoid paging collisions across different USIMs.

[0081] Generally, the MUSIM device and the network(s) can negotiate their MUSIM capabilities, including capabilities for the above-mentioned functions, during the Attach / Tracking Area Update (TAU) and Service Request procedures in the Evolved Packet System (EPS) (see, for example, 3GPP TS 24.301) and during the Registration and Service Request procedures in the 5GS (see, for example, 3GPP TS 24.501). In particular, in the EPS, the MUSIM device can specify its capabilities in the UE Network Capability IE, and the network can specify its capabilities in the EPS Network Capability Support IE. In the 5GS, the MUSIM device can specify its capabilities in the 5G Mobility Management (5GMM) Capability IE, and the network can specify its capabilities in the 5GS Network Capability Support IE.

[0082] The techniques described herein facilitate MUSIM operation by allowing a MUSIM device to set and retrieve values ​​of MUSIM-related parameters (e.g., parameters related to MUSIM operation of the device). In particular, new attention (AT) commands are defined that allow the terminal equipment (TE) of a MUSIM device to control the mobile termination (MT) functions of the device to set and / or retrieve parameter values ​​for various MUSIM functions, including NAS connection release, paging cause indication for voice, rejection of paging requests, paging restrictions, and paging timing collision control. By defining a standard means by which a MUSIM device can set and / or retrieve values ​​of MUSIM-related parameters, the techniques improve MUSIM operation by, for example, reducing collisions between communications associated with separate USIMs, preventing interruptions that disrupt the user experience, and enabling more efficient allocation of device and network resources.

[0083] 4 illustrates an example architecture of a MUSIM device 400 according to one aspect of the disclosure. In this example, the device 400 includes a terminal equipment (TE) 402 communicatively coupled to a mobile termination (MT) 404 via a terminal adapter (TA) 406. In some examples, the TE 402 includes an application circuit (e.g., the application circuit 305 of the device 300 of FIG. 3) and the MT 404 includes a baseband circuit (e.g., the baseband circuit 310 of the device 300 of FIG. 3).

[0084] The abstract architecture of the UE 400 can be physically implemented in a variety of ways. For example, in some examples, the TE 402, the MT 404, and the TA 406 may be implemented as three separate entities. In some examples, the TA 406 is integrated under the MT 404 cover and the TE 402 is implemented as a separate entity. In some examples, the TA 406 is integrated under the TE 402 cover and the MT 404 is implemented as a separate entity. In some examples, the TA 406 and the MT 404 are integrated under the TE 402 cover as a single entity.

[0085] In operation, one or more applications 408 executing on the device 400 may utilize MUSIM-related functionality. Thus, the application(s) 408 may send data to the TE indicating, for example, values ​​of MUSIM-related parameters, a request to read the MUSIM-related parameters, etc. (shown as operation 412). In response, the TE 402 may generate and send one or more AT commands to the TA 406 (shown as operation 414), which are then parsed and sent as MT control commands for controlling the MT 404 (shown as operation 416).

[0086] In general, AT commands may include, for example, general commands, call control commands, network service related commands, MT control and status commands, MT error result codes, commands for packet domains, commands for Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS), and commands for the USIM Application Toolkit, among other commands described herein. In some examples, AT commands set and / or retrieve values ​​of one or more MUSIM-related parameters, such as, among others, values ​​of parameters related to handling of a NAS connection with a CN or RAN associated with a particular USIM, values ​​of parameters related to incoming paging from a CN or RAN associated with a particular USIM, values ​​of parameters related to an IMSI used by a CN or RAN (or MME or AMF) for a particular USIM, or combinations thereof.

[0087] The MT 404 may transmit data to and receive data from one or more networks 410 associated with one or more particular USIMs of the device 400 (shown as operation 418). For example, the MT 404 may transmit a request to the network 410 (e.g., a network node such as an MME in EPS or an AMF in 5GS) associated with a particular USIM to indicate to the network whether to release a NAS connection, whether to restrict or reject paging, whether to negotiate an IMSI offset, etc. The MT 404 may then transmit an MT status message to the TA 406 based on a response received from the network 410 (shown as operation 420), which in turn transmits an MT status message to the TE 402 in response to the AT command (shown as operation 422). Data from these responses may then be transmitted to one or more applications 408, stored in memory (or another data storage medium), or both. In this manner, the AT commands described herein provide a way for the TE 402 to control the MT 404 to set and / or retrieve values ​​for MUSIM-related parameters.

[0088] The following description provides example command / response tables for new MUSIM AT commands according to one aspect of the disclosure. These AT commands enable the TE 402 of the MUSIM device 400 to communicate with the MT 404 to set and / or retrieve values ​​of MUSIM-related parameters based on, for example, UE capabilities. The command / response tables described below may be used in various cellular communication standards, such as the 3GPP LTE standard and / or the NR standard. In some examples, some or all of the command / response tables may be incorporated into one or more of the 3GPP technical specifications, such as 3GPP TS 27.007. Although the following description provides example command / response tables for various MUSIM AT commands, in some examples, one or more of the AT commands (and associated command / response tables) may be combined with another AT command or modified.

[0089] For the purposes of the illustrated command / response table, the following syntax definitions apply:

[0090] <cr>This is the carriage return character, and its value is specified by command S3.

[0091] <lf>This is a line feed character, and its value is specified by command S4.

[0092] <...> Names enclosed in angle brackets are syntax elements. The brackets themselves do not appear on the command line.

[0093] [...] Optional subparameters of a command or optional parts of a TA information response are enclosed in square brackets. The brackets themselves do not appear on the command line. When a subparameter is not given in a parameter type command, the new value is equal to its previous value. In an action type command, the action should be taken based on the recommended default setting of the subparameter.

[0094] Underline The underlined defined subparameter value is the recommended default setting for this subparameter. For parameter type commands, this value should be used as the factory setting that may be configured, for example, by ITU-T Recommendation V.250: "Serial asynchronous automatic dialing and control". For action type commands, this value should be used when the subparameter is not given.

[0095] In some examples, the techniques described herein provide a new NAS-Connection Release AT command. Such a command may be defined, for example, in 3GPP TS 27.007. In some examples, the NAS-Connection Release AT command is defined as follows: [Table 1]

[0096] explanation

[0097] The SET command allows the UE to specify a request to release its NAS connection to the network during normal and periodic tracking area update and service request procedures in EPS (see e.g. 3GPP TS 24.301, subclauses 5.5.3.2 and 5.6.1) and during registration and service request procedures in 5GS (see e.g. 3GPP TS 24.501, subclauses 5.5.1 and 5.6.1).

[0098] The read command is<NAS Connection Release> Returns the current value of .

[0099] Defined value

[0100] <NAS Connection Release> : Integer type

[0101] 0: Do not release the NAS signaling connection.

[0102] 1: Release the NAS signaling connection

[0103] In some examples, the techniques described herein provide a new Reject Paging AT command. Such a command may be defined, for example, in 3GPP TS 27.007. In some examples, the Reject Paging AT command is defined as follows: [Table 2]

[0104] explanation

[0105] The SET command allows the UE to indicate to the network the rejection of a paging request during the service request procedure in EPS (see, e.g., 3GPP TS 24.301 subclause 5.6.1) as well as when responding to a paging during the service request procedure in 5GS (see, e.g., 3GPP TS 24.501 subclause 5.6.1).

[0106] The read command is<Reject Paging> Returns the current value of .

[0107] Defined value

[0108] <Reject Paging> : Integer type

[0109] 0: Do not reject paging

[0110] 1: Reject paging

[0111] In some examples, the techniques described herein provide a new paging restriction AT command. Such a command may be defined, for example, in 3GPP TS 27.007. In some examples, the paging restriction AT command is defined as follows: [Table 3]

[0112] explanation

[0113] The SET command allows the UE to specify paging restrictions to the network during normal and periodic tracking area update and service request procedures in EPS (see e.g. 3GPP TS 24.301, subclauses 5.5.3.2 and 5.6.1) and during registration and service request procedures in 5GS (see e.g. 3GPP TS 24.501, subclauses 5.5.1 and 5.6.1).

[0114] The read command is<Paging Restrictions> Returns the current value of <ebi>and / or<PDU Session> Returns the current value(s) of .

[0115] Defined value

[0116] <Paging Restrictions> : Integer type

[0117] 0: Paging is not restricted

[0118] 1: All paging is restricted

[0119] 2: All paging is restricted except for voice services.

[0120] 3: All paging is restricted except for the designated PDN connection in the EPS

[0121] 4: All paging is restricted except for voice services in EPS and designated PDN connections.

[0122] 5: All paging is restricted except for designated PDU session connections in 5GS

[0123] 6: All paging is restricted except for voice services and designated PDU sessions in 5GS.

[0124] <ebi>: A bitmap indicating the PDN connection associated with the EPS bearer identity to which paging is restricted (see, for example, 3GPP TS 24.301, clause 9.9.3.66).

[0125] 0: Paging is restricted to the PDN connection associated with the EPS bearer identity

[0126] 1: Paging is not restricted to the PDN connection associated with the EPS bearer identity

[0127] <PDU Session> : A bitmap indicating the PDU sessions for which paging is restricted (see, for example, 3GPP TS 24.501, clause 9.11.3.77).

[0128] 0: Paging is restricted to PDU sessions.

[0129] 1: Paging is not restricted for PDU sessions

[0130] In some examples, the techniques described herein provide a new paging collision AT command. Such a command may be defined, for example, in 3GPP TS 27.007. In some examples, a paging restriction AT command is defined as follows: [Table 4]

[0131] explanation

[0132] The set command is <n>=1 and is set by the network during the attach and normal and periodic tracking area update procedures in EPS (see, e.g., subclauses 5.5.1 and 5.5.3.2 of 3GPP TS 24.301) and during the registration and service request procedures in 5GS (see, e.g., subclauses 5.5.1 and 5.6.1 of 3GPP TS 24.501).<IMSI Offset> Unsolicited return code when there is a change in the value of +CPAGCOL:<Selected IMSI Offset> Control the presentation of. <n>When =2, the SET command also allows the UE to specify the requested IMSI offset in the Attach and TAU procedures, as well as in the Registration and Service Request procedures.

[0133] The read command is<Selected IMSI Offset> Returns the current value of .

[0134] Defined value

[0135] <n>: Integer type

[0136] 0: Disable paging collision unsolicited result code

[0137] 1: Paging collision unsolicited result code + CPAGCOL:<Selected IMSI Offset> Enable

[0138] 2: Configure the UE requested IMSI offset for use in the Attach Request message and the TAU Request message (or the Registration Request message and the Service Request message).

[0139] <Requested IMSI Offset> IMSIOffsetRequestedByUE: is of type integer and indicates the value of the IMSI offset requested by the UE in binary format (see, for example, 3GPP TS 24.301, clause 9.9.3.64).

[0140] <Selected IMSI Offset> IMSI_OFFSET_VALUE: is an integer type indicating the value of the IMSI offset selected by the network in binary format (see, for example, 3GPP TS 24.301, clause 9.9.3.64).

[0141] 5 illustrates an example process 500 for setting and / or retrieving values ​​of MUSIM-related parameters according to one aspect of the disclosure. In some examples, the process 500 is performed by one or more of the devices or systems described herein, such as the UE 101 or components thereof.

[0142] The operations of process 500 include generating 502 an AT command, by a TE of the device. The AT command may indicate a value of a parameter related to MUSIM operations of the device. The TE (e.g., TE 402 of device 400) may include processing circuitry, such as a processor and / or other application circuitry (e.g., application circuitry 305). In some examples, the AT command may be generated in response to an instruction received from an application (e.g., application 408) executing on the device executing process 500, such as an operating system of the device or an application interfacing with an operating system of the device.

[0143] In some examples, the MUSIM-related parameter is a NAS connection release parameter. A value of the NAS connection release parameter can indicate to the MT (e.g., via the TA) whether to release a NAS connection between the device and a network node, such as a NAS connection associated with a particular USIM. In some examples, the MUSIM-related parameter is a paging reject parameter. A value of the paging reject parameter can indicate to the MT (e.g., via the TA) whether to reject a paging request by a network node to the device, such as a paging request associated with a particular USIM.

[0144] In some examples, the MUSIM-related parameters include one or more paging restriction parameters. A value of one of the paging restriction parameters can indicate to the MT (e.g., via the TA) the paging restriction(s) for the device, such as, among others, no paging restriction, all paging restriction, all paging restriction except voice services, all paging restriction except a designated PDN connection in EPS or a designated PDU session in 5GS, or all paging restriction except voice services and a designated PDN connection or PDU session. In some examples, one or more other paging restriction parameters can include one or more bitmaps indicating a designated PDN connection and / or PDU session associated with the restriction(s).

[0145] In some examples, the MUSIM-related parameters include one or more paging collision parameters. A value of one of the paging collision parameters may indicate to the MT (e.g., via the TA) whether to submit an unsolicited return code in response to a change in the IMSI offset associated with the device (or a particular USIM of the device). In some examples, one or more other paging collision parameters may indicate a requested IMSI offset for the device (e.g., for a particular USIM of the device) or a selected IMSI offset for the device.

[0146] The AT command is communicated 504 from the TE to the MT of the device via the TA. The MT and TA may be, for example, the MT 404 and the TA 406 of the device 400. In some examples, the MT and / or TA include or are implemented by processing circuitry, such as a processor and / or other baseband circuitry (e.g., the baseband circuitry 310).

[0147] In some examples, the MT may send messages to a network node based on the values ​​of parameters included in the AT command. For example, the MT may send messages to a network node (e.g., MME in EPS or AMF in 5GS) indicating, among others, whether to release the NAS connection based on the value of the NAS connection release parameter, whether the device rejected paging based on the value of the paging rejection parameter, one or more paging restrictions based on the value(s) of the paging restriction parameter(s), a requested IMSI offset, or whether to present an unsolicited return code in response to a change in the IMSI offset based on the value(s) of the paging collision parameter(s), or a combination thereof. In some examples, some or all of these indications are made during a TAU request procedure or a service request procedure in EPS, or during a registration request procedure or a service request procedure in 5GS.

[0148] In some examples, an AT command response is communicated from the MT to the TE via the TA (506). Such a response may be based on a message received from a network node (e.g., MME or AMF) during, for example, a TAU request or service request procedure in EPS, or a registration request or service request procedure in 5GS. Data indicative of this response may be stored in memory or another storage device, provided to an application running on the device, or both. In some examples, other data associated with the AT command (e.g., values ​​of parameters) may also be stored.

[0149] For one or more embodiments, at least one of the components described in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as described in the example section below. For example, processing circuitry, which may include application circuitry and / or baseband circuitry described in connection with one or more of the preceding figures, may be configured to operate according to one or more of the examples described below. As another example, circuitry associated with a UE, base station, network element, etc., as described above in connection with one or more of the preceding figures, may be configured to operate according to one or more of the examples described below in the example section.

[0150] Working Example

[0151] Example 1 is a device of a user equipment (UE), the device including a processing circuit including a TE, an MT, and a TA, the TE being configured to communicate with the MT via the TA, the processing circuit providing a request from a MUSIM device (e.g., UE) to process a NAS signaling connection or an incoming paging from a CN or a RAN to a network endpoint (e.g., MME in EPS or AMF in 5GS), indicating to the network endpoint a paging restriction in the MUSIM device that restricts paging from a CN or a RAN on one USIM, and transmitting an IM between the MUSIM device and the network endpoint to avoid paging collisions across multiple USIMs. and a memory that stores the UE request type, the paging restriction, or the IMSI offset.

[0152] Example 2 is the apparatus described in Example 1, wherein the MT is further configured to indicate a MUSIM device request type of NAS connection release in a TAU request or service request in the MME in EPS and / or a registration request or service request in the AMF in 5GS.

[0153] In a third embodiment, at least one AT command is<NAS Connection Release> indicating a MUSIM device request to release a NAS signaling connection via a parameter,<NAS Connection Release> 3. The apparatus according to any one of the first to second embodiments, wherein the parameter is configured to indicate whether the NAS connection should be released.

[0154] Example 4 is the apparatus of any one of Examples 1 to 3, wherein the MT is further configured to indicate a MUSIM device request type of paging rejection in the service request at the MME in EPS and in the service request at the AMF in 5GS.

[0155] In a fifth embodiment, at least one AT command is<Reject Paging> indicates the MUSIM device request to reject paging via the parameter<Reject Paging> 5. The apparatus of any one of embodiments 1 to 4, wherein the parameter is configured to indicate whether an incoming CN page in RRC_IDLE or a RAN page in RRC_INACTIVE should be rejected by the UE.

[0156] Example 6 is the apparatus of any one of Examples 1 to 5, wherein the MT is further configured to indicate a paging restriction in a TAU request and a service request in the MME in EPS and a registration request and a service request in the AMF in 5GS.

[0157] In the seventh embodiment, at least one AT command is<Paging Restrictions> and <ebi>Indicates the paging restriction specified by the MUSIM device via the parameters,<Paging Restrictions> The parameters include whether incoming paging is not restricted, whether all incoming paging is restricted, whether all paging is restricted except for voice services, whether all paging is restricted except for a specified PDN connection in the EPS, whether all paging is restricted except for voice services in the EPS and a specified PDN connection, and the parameter <ebi>The apparatus of any one of Examples 1 to 6, wherein the PDN connection associated with the EPS bearer identity is configured to indicate whether the PDN connection associated with the EPS bearer identity is restricted for paging.

[0158] In the eighth embodiment, at least one AT command is<Paging Restrictions> and<PDU Session> Indicates the paging restriction specified by the MUSIM device via the parameters,<Paging Restrictions> The parameters include whether incoming paging is not restricted, whether all incoming paging is restricted, whether all paging is restricted except for voice services, whether all paging is restricted except for designated PDU sessions in 5GS, whether all paging is restricted except for voice services and designated PDU sessions in 5GS, and the parameter<PDU Session> The apparatus of any one of embodiments 1 to 7, wherein the PDU session is configured to indicate whether paging is restricted.

[0159] In Example 9, TE is<Paging Restrictions> further configured to indicate a change in paging restriction to the MT in the +CPAGRES AT command via a parameter;<Paging Restrictions> 9. The apparatus of any of the previous examples, wherein the parameter is configured to indicate whether paging is restricted.

[0160] It is understood that use of personally identifiable information should comply with privacy policies and practices generally recognized as meeting or exceeding industry or governmental requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and handled in a manner that minimizes the risk of unintended or unauthorized access or use, and the nature of permitted uses should be clearly indicated to users.

[0161] The methods described herein may be implemented in different implementations in the form of software, hardware, or a combination thereof. In addition, the order of blocks of the methods may be changed, and various elements may be added, rearranged, combined, omitted, modified, etc. Various modifications and variations may be made, as would be apparent to one of ordinary skill in the art having the benefit of this disclosure. The various implementations described herein are illustrative and not limiting. Many variations, modifications, additions, and improvements are possible. Thus, multiple instances may be provided for components described herein as a single instance. Boundaries between various components, operations, and data stores are somewhat arbitrary, and particular operations are illustrated in the context of specific example configurations. Other allocations of functionality are contemplated and may be included within the scope of the following claims. Finally, structures and functions presented as separate components in example configurations may be implemented as combined structures or components. These and other variations, modifications, additions, and improvements may be included within the scope of the implementations, as defined in the following claims.< / ebi> < / ebi> < / n> < / n> < / n> < / ebi> < / ebi> < / lf> < / cr>

Claims

1. A device, A processing circuit comprising a terminal equipment (TE), a mobile termination (MT), and a terminal adapter (TA), said processing circuit comprising: generating, by the TE, an Attention (AT) command indicating values ​​of parameters related to a Multiple Universal Subscriber Identity Module (MUSIM) operation of the device, the parameters including any of a Non-Access Stratum (NAS) connection release parameter, a rejected paging parameter, a paging restriction parameter, or a paging collision parameter; communicating the AT command from the TE to the MT via the TA; a processing circuit configured to a memory configured to store data relating to the values ​​of the parameters relating to MUSIM operation of the device; A device comprising:

2. The device of claim 1 , wherein the parameters include the NAS connection release parameter, the value of the NAS connection release parameter indicating whether to release a NAS connection between the device and a network node.

3. The device of claim 2 , wherein the MT is configured to indicate to the network node whether to release the NAS connection between the device and the network node based on the value of the NAS connection release parameter.

4. 4. The device of claim 1, wherein the parameters include a reject paging parameter, the value of which indicates whether to reject paging of the device by a network node.

5. The device of claim 4 , wherein the MT is configured to indicate to the network node whether the device has rejected a page based on the value of the paging rejection parameter.

6. 6. The device of claim 1, wherein the parameters include the paging restriction parameter, and the value of the paging restriction parameter indicates whether paging is not restricted, all paging is restricted, all paging is restricted except for voice services, all paging is restricted except for a specified public data network (PDN) connection or protocol data unit (PDU) session, or all paging is restricted except for voice services and the specified PDN connection or PDU session.

7. The device of claim 6 , wherein values ​​of one or more other paging restriction parameters indicate the specified PDN connection or PDU session.

8. The device of claim 6 , wherein the MT is configured to indicate one or more paging restrictions to a network node based on the value of the paging restriction parameter.

9. 9. The device of claim 1, wherein the parameters include the paging collision parameter, the value of the paging collision parameter indicating whether to present an unsolicited return code in response to a change in an International Mobile Subscriber Identity (IMSI) offset associated with the device.

10. 10. The device of claim 1, wherein the parameters include the paging collision parameter, the value of the paging collision parameter indicating a requested IMSI offset for the device or a selected IMSI offset for the device.

11. 11. The device of claim 1, wherein the MT is configured to send a message to a network node based on the value of the parameter during an Evolved Packet System Mobility Management (EMM) Tracking Area Update or Service Request procedure, or during a 5G Mobility Management (5GMM) Registration Request or Service Request procedure.

12. The device of claim 1 , wherein the processing circuitry is configured to communicate an AT command response from the MT to the TE via the TA in response to the AT command.

13. generating, by a terminal equipment (TE) of a device, an attention (AT) command indicating values ​​of parameters related to a multiple universal subscriber identity module (MUSIM) operation of the device, the parameters including any of a non-access stratum (NAS) connection release parameter, a rejected paging parameter, a paging restriction parameter, or a paging collision parameter; communicating said AT command from said TE to a mobile terminal (MT) of said device via a terminal adapter (TA); A method comprising:

14. 14. The method of claim 13, wherein the parameters include a NAS connection release parameter, the value of which indicates whether to release a NAS connection between the device and a network node, or a paging reject parameter, the value of which indicates whether to reject paging of the device by a network node.

15. 15. The method of claim 13 or 14, wherein the parameters include the paging restriction parameter, and the value of the paging restriction parameter indicates whether paging is not restricted, all paging is restricted, all paging is restricted except for voice services, all paging is restricted except for a specified public data network (PDN) connection or protocol data unit (PDU) session, or all paging is restricted except for voice services and the specified PDN connection or PDU session.

16. 16. The method of claim 13, wherein the parameters include the paging collision parameter, the value of which indicates whether to present an unsolicited return code in response to a change in an International Mobile Subscriber Identity (IMSI) offset associated with the device, indicates a requested IMSI offset for the device, or indicates a selected IMSI offset for the device.

17. At least one non-transitory computer-readable medium storing instructions executable by at least one processor to perform operations, the operations comprising: generating, by a terminal equipment (TE) of a device, an attention (AT) command indicating values ​​of parameters related to a multiple universal subscriber identity module (MUSIM) operation of the device, the parameters including any of a non-access stratum (NAS) connection release parameter, a rejected paging parameter, a paging restriction parameter, or a paging collision parameter; communicating said AT command from said TE to a mobile terminal (MT) of said device via a terminal adapter (TA); 1. A non-transitory computer-readable medium comprising:

18. 18. The non-transitory computer-readable medium of claim 17, wherein the parameters include a NAS connection release parameter, the value of which indicates whether to release a NAS connection between the device and a network node, or a paging reject parameter, the value of which indicates whether to reject paging of the device by a network node.

19. 19. The non-transitory computer-readable medium of claim 17 or 18, wherein the parameters include the paging restriction parameter, and the value of the paging restriction parameter indicates whether paging is not restricted, all paging is restricted, all paging is restricted except for voice services, all paging is restricted except for a specified public data network (PDN) connection or protocol data unit (PDU) session, or all paging is restricted except for voice services and the specified PDN connection or PDU session.

20. 20. The non-transitory computer-readable medium of claim 17, wherein the parameters include the paging collision parameter, the value of which indicates whether to present an unsolicited return code in response to a change in an International Mobile Subscriber Identity (IMSI) offset associated with the device, indicates a requested IMSI offset for the device, or indicates a selected IMSI offset for the device.

Images