WO2022009177A1 - Paging management for multiple universal subscriber identity modules - Google Patents

Paging management for multiple universal subscriber identity modules Download PDF

Info

Publication number
WO2022009177A1
WO2022009177A1 PCT/IB2021/056201 IB2021056201W WO2022009177A1 WO 2022009177 A1 WO2022009177 A1 WO 2022009177A1 IB 2021056201 W IB2021056201 W IB 2021056201W WO 2022009177 A1 WO2022009177 A1 WO 2022009177A1
Authority
WO
WIPO (PCT)
Prior art keywords
paging
usims
alleviating
assistance
wireless communication
Prior art date
Application number
PCT/IB2021/056201
Other languages
French (fr)
Inventor
Prateek Basu Mallick
Genadi Velev
Joachim Loehr
Hyung-Nam Choi
Ravi Kuchibhotla
Original Assignee
Lenovo (Singapore) Pte. Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Singapore) Pte. Ltd. filed Critical Lenovo (Singapore) Pte. Ltd.
Publication of WO2022009177A1 publication Critical patent/WO2022009177A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices
    • H04W88/06Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W68/00User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02Arrangements for increasing efficiency of notification or paging channel

Definitions

  • the subject matter disclosed herein relates generally to wireless communications and more particularly relates to paging management for multiple universal subscriber identity modules.
  • a User Equipment device In certain wireless communication systems, a User Equipment device (“UE”) is able to connect with a fifth-generation (“5G”) core network (i.e., “5GC”) in a Public Land Mobile Network (“PLMN”).
  • 5G fifth-generation
  • PLMN Public Land Mobile Network
  • certain UEs support multiple universal subscriber identity modules.
  • One method of a user equipment device includes receiving, from a mobile wireless communication network associated with at least one of a plurality of universal subscriber identity modules (“USIMs”) of a user equipment (“UE”) device, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs, determining a paging collision for paging occasions of at least a subset of the plurality of USIMs, and sending a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs.
  • USIMs universal subscriber identity modules
  • One method of a network function in a mobile communication network includes sending, to a user equipment (“UE”) device comprising a plurality of universal subscriber identity modules (“USIMs”), an indication that a mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs, receiving, from the UE, a request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs, determining a solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs, and sending the determined solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs to the UE.
  • UE user equipment
  • USIMs universal subscriber identity modules
  • Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for paging management for multiple universal subscriber identity modules
  • Figure 2A is a diagram illustrating one embodiment of paging opportunities that overlap
  • Figure 2B is a diagram illustrating another embodiment of paging opportunities that overlap
  • Figure 3 is a signal flow diagram illustrating one embodiment of a procedure for paging management for multiple universal subscriber identity modules
  • Figure 4A is a diagram illustrating one embodiment of downlink timing of two cells
  • Figure 4B is a diagram illustrating one embodiment of using an absolute time scale to compare timelines
  • Figure 5 A is a signal flow diagram illustrating one embodiment of a procedure for paging management for multiple universal subscriber identity modules
  • Figure 5B is a signal flow diagram illustrating one embodiment of a procedure for paging management for multiple universal subscriber identity modules
  • Figure 6 is a block diagram illustrating one embodiment of a user equipment apparatus that may be used for paging management for multiple universal subscriber identity modules
  • Figure 7 is a block diagram illustrating one embodiment of a network apparatus that may be used for paging management for multiple universal subscriber identity modules
  • Figure 8 is a flowchart diagram illustrating one embodiment of a method for paging management for multiple universal subscriber identity modules
  • Figure 9 is a flowchart diagram illustrating one embodiment of a method for paging management for multiple universal subscriber identity modules
  • Figure 10 is a flowchart diagram illustrating one embodiment of a method for paging management for multiple universal subscriber identity modules
  • Figure 11 is a flowchart diagram illustrating one embodiment of a method for paging management for multiple universal subscriber identity modules.
  • Figure 12 is a flowchart diagram illustrating one embodiment of a method for paging management for multiple universal subscriber identity modules.
  • embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.
  • the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very-large-scale integration
  • the disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.
  • the disclosed embodiments may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.
  • embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code.
  • the storage devices may be tangible, non- transitory, and/or non-transmission.
  • the storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
  • the computer readable medium may be a computer readable storage medium.
  • the computer readable storage medium may be a storage device storing the code.
  • the storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • a storage device More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object- oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages.
  • the code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider (“ISP”)).
  • LAN local area network
  • WLAN wireless LAN
  • WAN wide area network
  • ISP Internet Service Provider
  • a list with a conjunction of “and/or” includes any single item in the list or a combination of items in the list.
  • a list of A, B and/or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
  • a list using the terminology “one or more of’ includes any single item in the list or a combination of items in the list.
  • one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
  • a list using the terminology “one of’ includes one and only one of any single item in the list.
  • “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C.
  • a member selected from the group consisting of A, B, and C includes one and only one of A, B, or C, and excludes combinations of A, B, and C.”
  • “a member selected from the group consisting of A, B, and C and combinations thereof’ includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
  • the code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the flowchart diagrams and/or block diagrams.
  • the code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.
  • each block in the flowchart diagrams and/or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
  • the present disclosure describes systems, methods, and apparatus for paging management for multiple universal subscriber identity modules.
  • the methods may be performed using computer code embedded on a computer-readable medium.
  • an apparatus or system may include a computer-readable medium containing computer-readable code which, when executed by a processor, causes the apparatus or system to perform at least a portion of the below described solutions.
  • Certain mobile devices can support multiple universal subscription identifier modules (“USIM”).
  • a multi-USIM device is a device that supports more than one SIM/USIM in the same user/mobile equipment (“UE”).
  • the USIMs of the multi-USIM device may belong to the same or different network operators.
  • the USIMs may be associated with networks that have the same or different radio access technologies, e.g., 5G New Radio (“NR”), 4G Fong Term Evolution (“FTE”), or the like.
  • NR 5G New Radio
  • FTE 4G Fong Term Evolution
  • a multi-USIM device may wish to receive paging for all associated USIMs, e.g., the USIMs are operational simultaneously in the device.
  • the UE may calculate the paging occasions and seek assistance before initiating registration.
  • the UE sends a non-access stratum (“NAS”) registration request first and calculates the paging occasions and determines collisions from then on.
  • the network allows the UE to seek paging assistance knowing that the network supports providing such assistance. Further, a rule may be used that defines situations where a UE is allowed to declare a paging collision of at least two USIMs and thereby seek assistance, e.g., transmit a paging assistance required message.
  • the proposed solutions remedy the problems with the existing solutions, which do not specify when the UE is allowed to seek assistance for paging collisions among multiple USIMs and depend on a hit-or-miss method that is dependent on whether the network supports paging collision assistance. Otherwise, the UE battery life may be wasted in transitioning to a radio resource control (“RRC”) connection. Moreover, a core network-based solution may potentially delay paging reception.
  • RRC radio resource control
  • FIG. 1 depicts a wireless communication system 100 for paging management for multiple universal subscriber identity modules, according to embodiments of the disclosure.
  • the wireless communication system 100 includes at least one remote unit 105, a Fifth-Generation Radio Access Network (“5G-RAN”) 115, and a mobile core network 140.
  • the 5G-RAN 115 and the mobile core network 140 form a mobile communication network.
  • the 5G- RAN 115 may be composed of a 3GPP access network 120 containing at least one cellular base unit 121 and/or a non-3GPP access network 130 containing at least one access point 131.
  • the remote unit 105 communicates with the 3GPP access network 120 using 3GPP communication links 123 and/or communicates with the non-3GPP access network 130 using non-3GPP communication links 133. Even though a specific number of remote units 105, 3GPP access networks 120, cellular base units 121, 3GPP communication links 123, non-3GPP access networks 130, access points 131, non-3GPP communication links 133, and mobile core networks 140 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 105, 3GPP access networks 120, cellular base units 121, 3GPP communication links 123, non-3GPP access networks 130, access points 131, non-3GPP communication links 133, and mobile core networks 140 may be included in the wireless communication system 100.
  • the RAN 120 is compliant with the 5G system specified in the Third Generation Partnership Project (“3GPP”) specifications.
  • the RAN 120 may be a NG-RAN, implementing NR RAT and/or FTE RAT.
  • the RAN 120 may include non-3GPP RAT (e.g., Wi-Fi® or Institute of Electrical and Electronics Engineers (“IEEE”) 802.11-family compliant WLAN).
  • the RAN 120 is compliant with the LTE system specified in the 3GPP specifications.
  • the wireless communication system 100 may implement some other open or proprietary communication network, for example Worldwide Interoperability for Microwave Access (“WiMAX”) or IEEE 802.16-family standards, among other networks.
  • WiMAX Worldwide Interoperability for Microwave Access
  • IEEE 802.16-family standards among other networks.
  • the present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
  • the remote units 105 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like.
  • the remote units 105 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • the remote units 105 may be referred to as the UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit (”WTRU”), a device, or by other terminology used in the art.
  • the remote unit 105 includes a subscriber identity and/or identification module (“SIM”) and the mobile equipment (“ME”) providing mobile termination functions (e.g., radio transmission, handover, speech encoding and decoding, error detection and correction, signaling and access to the SIM).
  • SIM subscriber identity and/or identification module
  • ME mobile equipment
  • the remote unit 105 may include a terminal equipment (“TE”) and/or be embedded in an appliance or device (e.g., a computing device, as described above).
  • the remote units 105 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like.
  • the remote units 105 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • the remote units 105 may be referred to as UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit (“WTRU”), a device, or by other terminology used in the art.
  • WTRU wireless transmit/receive unit
  • the remote units 105 may communicate directly with one or more of the cellular base units 121 in the 3GPP access network 120 via uplink (“UL”) and downlink (“DL”) communication signals. Furthermore, the UL and DL communication signals may be carried over the 3GPP communication links 123. Similarly, the remote units 105 may communicate with one or more access points 131 in the non-3GPP access network(s) 130 via UL and DL communication signals carried over the non-3GPP communication links 133.
  • the access networks 120 and 130 are intermediate networks that provide the remote units 105 with access to the mobile core network 140.
  • the remote units 105 communicate with a remote host (e.g., in the data network 150 or in the data network 160) via a network connection with the mobile core network 140.
  • a remote host e.g., in the data network 150 or in the data network 160
  • an application 107 e.g., web browser, media client, telephone and/or Voice-over-Intemet-Protocol (“VoIP”) application
  • VoIP Voice-over-Intemet-Protocol
  • the mobile core network 140 then relays traffic between the remote unit 105 and the remote host using the PDU session.
  • the PDU session represents a logical connection between the remote unit 105 and a User Plane Function (“UPF”) 141.
  • UPF User Plane Function
  • the remote unit 105 In order to establish the PDU session (or PDN connection), the remote unit 105 must be registered with the mobile core network 140 (also referred to as “attached to the mobile core network” in the context of a Fourth Generation (“4G”) system). Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 140. As such, the remote unit 105 may have at least one PDU session for communicating with the packet data network 150. Additionally - or alternatively - the remote unit 105 may have at least one PDU session for communicating with the packet data network 160. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and/or other communication peers.
  • the mobile core network 140 also referred to as “attached to the mobile core network” in the context of a Fourth Generation (“4G”) system.
  • the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 140.
  • the remote unit 105 may have at least one PDU session for communicating with the packet
  • PDU Session refers to a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between the remote unit 105 and a specific Data Network (“DN”) through the UPF 131.
  • E2E end-to-end
  • UP user plane
  • DN Data Network
  • a PDU Session supports one or more Quality of Service (“QoS”) Flows.
  • QoS Quality of Service
  • EPS Evolved Packet System
  • PDN Packet Data Network
  • the PDN connectivity procedure establishes an EPS Bearer, i.e., atunnel between the remote unit 105 and a Packet Gateway (“PGW”, not shown) in the mobile core network 130.
  • PGW Packet Gateway
  • QCI QoS Class Identifier
  • the remote unit 105 may use a first data connection (e.g., PDU Session) established with the first mobile core network 130 to establish a second data connection (e.g., part of a second PDU session) with the second mobile core network 140.
  • a data connection e.g., PDU session
  • the remote unit 105 uses the first data connection to register with the second mobile core network 140.
  • the cellular base units 121 may be distributed over a geographic region.
  • a cellular base unit 121 may also be referred to as an access terminal, a base, a base station, a Node-B (“NB”), an Evolved Node B (abbreviated as eNodeB or “eNB,” also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node B), a 5G/NR Node B (“gNB”), a Home Node-B, a Home Node-B, a relay node, a device, or by any other terminology used in the art.
  • NB Node-B
  • eNB Evolved Node B
  • gNB 5G/NR Node B
  • Home Node-B a Home Node-B
  • relay node a device, or by any other terminology used in the art.
  • the cellular base units 121 are generally part of a radio access network (“RAN”), such as the 3GPP access network 120, that may include one or more controllers communicably coupled to one or more corresponding cellular base units 121. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art.
  • the cellular base units 121 connect to the mobile core network 140 via the 3GPP access network 120.
  • the cellular base units 121 may serve a number of remote units 105 within a serving area, for example, a cell or a cell sector, via a 3GPP wireless communication link 123.
  • the cellular base units 121 may communicate directly with one or more of the remote units 105 via communication signals.
  • the cellular base units 121 transmit DL communication signals to serve the remote units 105 in the time, frequency, and/or spatial domain.
  • the DL communication signals may be carried over the 3GPP communication links 123.
  • the 3GPP communication links 123 may be any suitable carrier in licensed or unlicensed radio spectrum.
  • the 3GPP communication links 123 facilitate communication between one or more of the remote units 105 and/or one or more of the cellular base units 121. Note that during NR operation on unlicensed spectrum (referred to as “NR-U”), the base unit 121 and the remote unit 105 communicate over unlicensed (i.e., shared) radio spectrum.
  • NR-U unlicensed spectrum
  • the non-3GPP access networks 130 may be distributed over a geographic region. Each non-3GPP access network 130 may serve a number of remote units 105 with a serving area. An access point 131 in a non-3GPP access network 130 may communicate directly with one or more remote units 105 by receiving UL communication signals and transmitting DL communication signals to serve the remote units 105 in the time, frequency, and/or spatial domain. Both DL and UL communication signals are carried over the non-3GPP communication links 133.
  • the 3GPP communication links 123 and non-3GPP communication links 133 may employ different frequencies and/or different communication protocols.
  • an access point 131 may communicate using unlicensed radio spectrum.
  • the mobile core network 140 may provide services to a remote unit 105 via the non-3GPP access networks 130, as described in greater detail herein.
  • a non-3GPP access network 130 connects to the mobile core network 140 via an interworking entity 135.
  • the interworking entity 135 provides an interworking between the non-3GPP access network 130 and the mobile core network 140.
  • the interworking entity 135 supports connectivity via the “N2” and “N3” interfaces. As depicted, both the 3GPP access network 120 and the interworking entity 135 communicate with the AMF 143 using a “N2” interface.
  • the 3GPP access network 120 and interworking entity 135 also communicate with the UPF 141 using a “N3” interface. While depicted as outside the mobile core network 140, in other embodiments the interworking entity 135 may be a part of the core network.
  • a non-3GPP access network 130 may be controlled by an operator of the mobile core network 140 and may have direct access to the mobile core network 140. Such a non-3GPP AN deployment is referred to as a “trusted non-3GPP access network.”
  • a non-3GPP access network 130 is considered as “trusted” when it is operated by the 3GPP operator, or a trusted partner, and supports certain security features, such as strong air-interface encryption.
  • a non-3GPP AN deployment that is not controlled by an operator (or trusted partner) of the mobile core network 140, does not have direct access to the mobile core network 140, or does not support the certain security features is referred to as a “non-trusted” non-3GPP access network.
  • An interworking entity 135 deployed in atrusted non-3GPP access network 130 may be referred to herein as a Trusted Network Gateway Function (“TNGF”).
  • An interworking entity 135 deployed in a non-trusted non-3GPP access network 130 may be referred to herein as a non-3GPP interworking function (“N3IWF”). While depicted as a part of the non-3GPP access network 130, in some embodiments the N3IWF may be a part of the mobile core network 140 or may be located in the data network 150.
  • TNGF Trusted Network Gateway Function
  • N3IWF non-3GPP interworking function
  • the mobile core network 140 is a 5G core (“5GC”) or the evolved packet core (“EPC”), which may be coupled to a data network 150, like the Internet and private data networks, among other data networks.
  • a remote unit 105 may have a subscription or other account with the mobile core network 140.
  • Each mobile core network 140 belongs to a single public land mobile network (“PLMN”).
  • PLMN public land mobile network
  • the mobile core network 140 includes several network functions (“NFs”). As depicted, the mobile core network 140 includes at least one UPF (“UPF”) 141.
  • the mobile core network 140 also includes multiple control plane functions including, but not limited to, an Access and Mobility Management Function (“AMF”) 143 that serves the 5G-RAN 115, a Session Management Function (“SMF”) 145, a Policy Control Function (“PCF”) 146, an Authentication Server Function (“AUSF”) 147, a Unified Data Management (“UDM”) and Unified Data Repository function (“UDR”).
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • PCF Policy Control Function
  • AUSF Authentication Server Function
  • UDM Unified Data Management
  • UDR Unified Data Repository function
  • the UPF(s) 141 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU session for interconnecting Data Network (“DN”), in the 5G architecture.
  • the AMF 143 is responsible for termination ofNAS signaling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management.
  • the SMF 145 is responsible for session management (i.e., session establishment, modification, release), remote unit (i.e., UE) IP address allocation & management, DL data notification, and traffic steering configuration for UPF for proper traffic routing.
  • the PCF 146 is responsible for unified policy framework, providing policy rules to CP functions, access subscription information for policy decisions in UDR.
  • the AUSF 147 acts as an authentication server.
  • the UDM is responsible for generation of Authentication and Key Agreement (“AKA”) credentials, user identification handling, access authorization, subscription management.
  • AKA Authentication and Key Agreement
  • the UDR is a repository of subscriber information and can be used to service a number of network functions.
  • the UDR may store subscription data, policy-related data, subscriber- related data that is permitted to be exposed to third party applications, and the like.
  • the UDM is co-located with the UDR, depicted as combined entity “UDM/UDR” 149.
  • the mobile core network 140 may also include an Network Exposure Function (“NEF”) (which is responsible for making network data and resources easily accessible to customers and network partners, e.g., via one or more APIs), a Network Repository Function (“NRF”) (which provides NF service registration and discovery, enabling NFs to identify appropriate services in one another and communicate with each other over Application Programming Interfaces (“APIs”)), or other NFs defined for the 5GC.
  • NEF Network Exposure Function
  • NRF Network Repository Function
  • APIs Application Programming Interfaces
  • the mobile core network 140 may include an authentication, authorization, and accounting (“AAA”) server.
  • AAA authentication, authorization, and accounting
  • the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice.
  • a “network slice” refers to a portion of the mobile core network 140 optimized for a certain traffic type or communication service.
  • a network instance may be identified by a S-NSSAI, while a set of network slices for which the remote unit 105 is authorized to use is identified by NSSAI.
  • the various network slices may include separate instances of network functions, such as the SMF and UPF 141.
  • the different network slices may share some common network functions, such as the AMF 143. The different network slices are not shown in Figure 1 for ease of illustration, but their support is assumed.
  • FIG. 1 Although specific numbers and types of network functions are depicted in Figure 1, one of skill in the art will recognize that any number and type of network functions may be included in the mobile core network 140. Moreover, where the mobile core network 140 comprises an EPC, the depicted network functions may be replaced with appropriate EPC entities, such as an MME, S-GW, P-GW, HSS, and the like.
  • Figure 1 depicts components of a 5G RAN and a 5G core network
  • the described embodiments for using a pseudonym for access authentication over non-3GPP access apply to other types of communication networks and RATs, including IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfoxx, and the like.
  • the AMF 143 may be mapped to an MME, the SMF mapped to a control plane portion of a PGW and/or to an MME, the UPF 141 may be mapped to an SGW and a user plane portion of the PGW, the UDM/UDR 149 may be mapped to an HSS, etc.
  • a remote unit 105 may connect to the mobile core network (e.g., to a 5G mobile communication network) via two types of accesses: (1) via 3GPP access network 120 and (2) via a non-3GPP access network 130.
  • the first type of access e.g., 3GPP access network 120
  • uses a 3GPP-defmed type of wireless communication e.g., NG-RAN
  • the second type of access e.g., non-3GPP access network 130
  • uses a non-3GPP -defined type of wireless communication e.g., WLAN.
  • the 5G-RAN 115 refers to any type of 5G access network that can provide access to the mobile core network 140, including the 3GPP access network 120 and the non-3GPP access network 130.
  • the present disclosure proposes solutions where, in one embodiment, the UE calculates the paging occasions and seeks assistance before initiating registration. In another embodiment, the UE sends a NAS registration request first and calculates the paging occasions and determines collisions from then on. In yet another embodiment, the network allows the UE to seek paging assistance knowing that the network supports providing such assistance. Further, a rule may be used that defines situations where a UE is allowed to declare a paging collision of at least two USIMs and thereby seek assistance, e.g., transmit a paging assistance required message.
  • the proposed solution in one embodiment, conserves the UE battery life by eliminating, avoiding, or reducing the transition to a radio resource control (“RRC”) connection. Moreover, in another embodiment, the proposed solution avoids using the core network, which may potentially delay paging reception.
  • RRC radio resource control
  • a multi -USIM device may wish to receive paging for all associated USIMs, e.g., the USIMs that are operational simultaneously in the device.
  • the time occasions where a multi-USIM device expects paging messages in idle mode are calculated in a specified way, e.g., as described in TS 38.304 for NR/5GS.
  • the UE may use discontinuous reception (“DRX”) in RRC IDFE and RRC INACTIVE state to reduce power consumption.
  • DRX discontinuous reception
  • the UE monitors one paging occasion (“PO”) per DRX cycle.
  • a PO may refer to a set of physical downlink control channel (“PDCCH”) monitoring occasions and may consist of multiple time slots (e.g., subframe or orthogonal frequency-division multiplexing (“OFDM”) symbols) where paging downlink control information (“DCI”) can be sent, e.g., according to TS 38.213.
  • PDCCH physical downlink control channel
  • OFDM orthogonal frequency-division multiplexing
  • DCI paging downlink control information
  • One paging frame ( PF ) is one radio frame and may contain one or multiple PO(s) or a starting point of a PO.
  • the PF and PO for paging are determined by the following formula:
  • SFN System frame number
  • T DRX cycle of the UE (T is determined by the shortest of the UE specific DRX value(s), if configured by RRC and/or upper layers, and a default DRX value broadcast in system information. If UE specific DRX is not configured by RRC or by upper layers, the default value is applied).
  • N number of total paging frames in T
  • Ns number of paging occasions for a PF PF offset: offset used for PF determination
  • the UE ID used for calculating PF, PO, and corresponding PDCCH monitoring occasions may be the same for two USIM devices because the UE_ID are the modulo values (e.g., mod 1024), or the operations ‘div’, ‘mod’, or 7’, which may result in that some of the paging opportunities (e.g., PF + PO) corresponding to the two USIMs overlap.
  • the collision of paging opportunities also depends on whether the two USIM devices are camped on the same cell (or a different cell with same or different parameter values impacting the PF/PO calculations such as Ns, nAndPagingFrameOffset, nroftOCCH-MonitoringOccasionPerSSB- InPO, and the length of default DRX Cycle that are signaled in SIB1). If a UE has a single receiver (“Rx”) chain, it may not be able to receive paging for both USIMs when the paging opportunities completely or partially overlap/collide in time.
  • Rx receiver
  • the first USIM in a UE that supports more than one USIM is already active and has a serving cell (e.g., camped in an RRC Idle or an RRC Connected state).
  • a serving cell e.g., camped in an RRC Idle or an RRC Connected state.
  • the UE e.g., USIM -2
  • the UE may initiate a NAS registration procedure.
  • the UE may already include some access stratum paging parameters (e.g., pcch-Config from a serving cell of another USIM(s) including its 10 bit 5G-S- TMSI mod 1024 value) in a NAS registration request message when at least one other USIM is already active.
  • the AMF upon and/or if deciding on successful registration (e.g., a NAS registration accept message) allocates a 5G-TMSEGUTI and a UE specific DRX cycle that avoids paging collisions.
  • the UE sends the NAS registration request first and calculates the paging occasions, e.g., as described in TS 38.304, based on the parameters broadcasted in SIB1 (e.g., specifically the pcch-Config parameter), e.g., as defined in TS 38.331, only after receiving a NAS registration accept message while considering a UE specific DRX cycle, if signaled in the registration accept message. If a paging collision is foreseen between the calculated paging opportunities of both USIMs, the UE may request the network to modify the paging occasions for one of the USIMs, e.g., sending a paging assistance required message to the network.
  • SIB1 e.g., specifically the pcch-Config parameter
  • the UE sends the paging assistance request to the network that corresponds to the second USIM, e.g., the USIM that is activated (registered) after the first USIM is activated.
  • the UE sends the paging assistance request to the network that corresponds to the first USIM, e.g., the USIM that is activated (registered) before the second USIM.
  • An AMF in the network is referred in most cases for an RRC Idle UE, but the same methods described herein may apply to a UE seeking assistance from a RAN node (e.g., a gNB) if it initiates an RRC connection establishment to seek such assistance.
  • a RAN node e.g., a gNB
  • Paging assistance in one embodiment, is an adjustment made for a specific UE that may not be able to monitor regular paging opportunities, enabling it to monitor different sets of paging opportunities, and send the paging on the sets of different paging opportunities.
  • the “adjustment” is made to one or more of the paging parameters, configuration, or UE ID described herein.
  • the UE seeks blindly the paging assistance, e.g., without knowing if the network can provide paging assistance.
  • the UE is registered for both USIMs, but paging collisions start when the paging configuration (e.g., pcch-Config) from a serving cell of one of the USIM changes, e.g., one or more of the parameters Ns, nAndPagingFrameOffset, nrofPDCCFl-MomtoringOccasionP erSSB-lnPO , and/or the length of default DRX Cycle is/are modified, which may lead to paging collisions.
  • the UE may realize at some point that it needs assistance to avoid paging collisions corresponding to the two USIMs.
  • the UE is allowed to seek paging assistance knowing that the network supports providing such assistance.
  • the broadcast information from a serving cell indicates that the network provides “assistance for paging collision alleviation.” This may be done in several ways.
  • the network may broadcast a one bit flag indicating whether the network provides “assistance for paging collision alleviation.”
  • it may be implied based on broadcasting any required paging assistance parameter.
  • An example of a required paging assistance parameter may be an offset value for changing a starting position of a first paging occasion in the SFN cycle, which may impact the firstPDCCH- MonitoringOccasionOfl’O parameter.
  • the UE may send a “paging assistance required” message to the network (e.g., the AMF). If only one of the networks corresponding to the two USIMs provides, supports, or otherwise indicates that it supports “assistance for paging collision alleviation,” the UE sends a “paging assistance required” message to that corresponding network.
  • the network e.g., the AMF
  • a UE may reselect another cell that provides “assistance for paging collision alleviation” for one of the USIMs.
  • the network may provide more information than just an indication of whether the network supports or does not support “assistance for paging collision alleviation,” e.g., if there are more than one solution/technique that can be used for paging collision alleviation, the network may inform the UE using broadcast or dedicated RRC/NAS signaling as to which solution/technique is used for paging collision alleviation by the serving network. Upon sending the “paging assistance required” message, the UE may prepare to apply the solution/technique for paging collision alleviation that the servicing network supports.
  • the network may resend the paging message in the new paging opportunities upon receiving a “paging assistance required” message for a UE that was being paged recently but had not responded to the page .
  • a network may store the paging after completing its paging attempts if the UE has still not responded to the page.
  • the UE behavior and possible network control is outlined so that UEs each have the same behavior as far as paging collision detection is concerned.
  • some UEs will declare, detect, or determine a paging collision and seek assistance when all paging opportunities of both of the USIMs collide, as shown in 2A, and some other UEs may seek assistance when less than all of the paging opportunities of both of the USIMs collide, as shown in Error! Reference source not found.B.
  • a rule may be established, defined, used or the like that determines when a UE is allowed to declare a paging collision of at least two USIMs, and thereby seek assistance (e.g., transmit a “paging assistance required” message).
  • the UE may be allowed to seek assistance if a single paging collision in each time period such as a DRX cycle is foreseen or detected. This rule may be useful if the network does not re-transmit a paging message in a particular serving cell.
  • another rule could be defined or established that states that upon collision of at least contiguous (or otherwise) ‘x’ paging opportunities (e.g., in a DRX cycle, in a SFN cycle, in a time period, or the like) in each time period such as a DRX cycle, the UE may be allowed to seek assistance.
  • the rule may be expressed in terms of a percentage of colliding POs (e.g., in a DRX cycle or in the entire SFN cycle) such as 50% of paging opportunities results in collisions, 100% of paging opportunities result in collisions, and/or the like.
  • the rule may be hard-coded in a specification or may be configurable by the network using RRC signaling, e.g., by broadcast signaling in SIB.
  • the paging collision may be noted as an overlap, either partial or full, in time and/or also in the paging search space.
  • the number of “paging assistance required” messages that are sent from the UE may be restricted or limited by way of a timer such that the UE is not allowed to send another “paging assistance required” until the timer has expired.
  • the timer may be started once the UE has transmitted a “paging assistance required” message.
  • the number of “paging assistance required” messages that are sent from the UE may be restricted or limited by way of a constraint that allows the UE to repeat “paging assistance required” at least after ‘x’ milliseconds, seconds, or the like.
  • a “paging assistance required” message may be sent immediately.
  • Figure 3 depicts a procedure 300 for paging management for multiple universal subscriber identity modules.
  • a network 304 indicates (see messaging 306) to a UE 302 its support or capability, e.g., using one-bit broadcast signaling for “assistance for paging collision alleviation.”
  • a UE 302 upon determining a paging collision, evaluates (see block 308) a rule to check if it is allowed to send a “paging assistance required” message to the network 304.
  • the UE 302 transmits (see messaging 310) the “paging assistance required” message to the network 304.
  • the network 304 provides (see messaging 312) paging assistance that indicates a paging solution (e.g., modified paging opportunities present at an offset to the regular paging opportunities) to the UE 302.
  • the network 304 transmits, and the UE 302 monitors, paging at the modified paging opportunities.
  • a further embodiment describes the UE protocol implementation and the behavior of access stratus (“AS”) and non-access stratum (“NAS”) in the event of paging collisions.
  • the NAS upon activating the second protocol stack corresponding to the second USIM, requests the AS to perform cell search and look for suitable PLMN(s).
  • the NAS upon PLMN and cell selection corresponding to the second USIM, and optionally after receiving a registration accept message, the NAS requests both the AS protocols (of the two corresponding USIMs) to calculate the paging opportunities from the broadcast information of the serving cell corresponding to each of the USIMs.
  • the UE specific DRX cycle if provided by upper layers, may also be considered.
  • both the AS protocols that correspond to the two USIMs calculate their corresponding paging opportunities and send the same to the NAS.
  • the NAS determines if there is a paging collision in some or all of the paging opportunities of the involved USIMs.
  • the UE accounts for the DL time difference across the concerned serving cells.
  • the UE needs to advance the SFN cycle timeline for one of the serving cells by delta_T (or alternatively, the UE needs to delay the SFN cycle timeline for the other serving cell by delta_T). If this is not performed and the two paging opportunities are indicated to the NAS, then the NAS will assume that PF#x and PO#y of two cells are colliding whereas they may not in reality if the delta_T is longer than a slot length.
  • the timelines of the two serving cells are aligned by considering the delta_T, and the UE checks for collisions of paging opportunities between the two cells.
  • the frame boundary of SFN#0 of the two cells starts at the same point in time, e.g., using an absolute time reference like global navigation satellite system (“GNSS”).
  • GNSS global navigation satellite system
  • the UE may determine actual paging collision or overlap of the paging opportunities.
  • the UE compares the collisions between the paging opportunities while also considering the retuning time between the frequencies.
  • the NAS upon determining a paging collision, reports the paging collision issue to the network and seeks assistance to avoid the same.
  • the NAS is generally meant as some common, combined, or upper NAS protocol, e.g., sitting above the individual NAS protocol that has overview of the two USIMs and the two protocol stacks.
  • the UE supports more than one USIM registration and receives the NAS registration accept message or NAS UE configuration update message (or a corresponding attach accept message or TAU accept message in EPS) including 1) a new GUTI and/or 2) a DRX timer for paging.
  • the NAS layer requests the AS layer to determine whether a paging occasion collision occurs considering the parameters for the USIM registration, e.g., GUTI and DRX timer for paging.
  • the NAS layer waits with the “acknowledgement for the registration accept” message or “UE configuration update” message until feedback from the AS layer.
  • NAS# 1 protocol stack requests the AS to monitor the POs according to the parameters sent from
  • NAS#2 protocol stack requests the AS to monitor the POs for NAS#2.
  • the AS layer exchanges with two NAS instances and the AS stores, for each NAS instance, idle state parameters, e.g., S-TMSI, DRX timer, allowed TA list, frequency band preference, and/or the like.
  • the AS layer performs a check to determine whether paging occasion collision occurs. This may be done by comparing the paging opportunities of both USIMs using the same time reference and checking if the paging opportunities of both USIMs overlap, either partially or fully/completely.
  • the AS if the AS layer determines that paging occasion collision occurs, the AS sends an indication to the NAS regarding the collision.
  • the NAS layer sends a registration complete message or a UE configuration update complete message (or corresponding NAS EPS messages), including an indication to the AMF (or MME) that paging collision is detected.
  • the UE selects a USIM for which the UE seeks paging assistance from the network in the event of paging collisions between multiple USIMs.
  • various parameters or criteria may be used to determine which USIM is selected, including, but not limited to, a preference for new radio (“NR”) USIM in case of inter-radio access technologies (“RAT”) over other RAT USIMs; in response to not receiving a response from a mobile wireless communication network corresponding to one of the USIMs to the request for assistance with alleviating the determined paging collision, selecting a mobile wireless communication network for a next USIM to request assistance with alleviating the determined paging collision; a preference for a solution for alleviating the determined paging collision provided by a mobile wireless communication network corresponding to one of the USIMs over a different solution provided by a mobile wireless communication network corresponding to a different USIM; a preference for using an equivalent home public land mobile network (“EHPLMN”) USIM over a visited PLMN (“VPLMN
  • a UE after performing a registration procedure checks corresponding to the received GUTE5G-S-TMSI, if the paging opportunities (e.g., based on the pcch-Config of the serving cell) would collide with that of the other USIM(s). If so, in one embodiment, the UE performs deregistration and then re-registers and receives another GUTE5G- S-TMSI. In certain embodiments, this procedure is repeated until no paging collision is foreseen.
  • a UE upon indicating paging collisions to the network and seeking assistance by sending a “paging assistance required” message to the network, e.g., AMF, as shown in 5A, starts monitoring POs that are calculated with a fixed offset from the “regular” calculated paging opportunities, e.g., as defined in TS 38.304.
  • AMF paging assistance required
  • the RRC Idle UE upon determining the paging collisions, the RRC Idle UE first initiates a transition to RRC Connected, using optionally a new EstablishmentCause, a new logical channel identifier (“LCID”), or the like, to allow the gNB to understand the reason for initiating an RRC Connection establishment.
  • the said “offset” may be fixed in a specification and may be quantified in a number of time slots, subframes, paging frames, a firstPDCCH-MonitoringOccasionOfiO parameter (e.g., as defined in 38331-g00), in the UE_ID, and/or the like.
  • the UE may calculate the PF+PO corresponding to a UE ID New, where UE ID New is UE ID + 2 and where the UE ID is calculated as UE ID: 5G-S-TMSI mod 1024.
  • the offset can be negative. Instead of calculating the new values of the parameters (e.g., time slots, subframes, frames, UE_ID, and/or the like), some fixed values for one or more of these parameters may be used as well.
  • the offset, or the fixed value can be specified or (pre)configured using RRC signaling.
  • the UE and the network may use an alternative value for one or more of the parameters Ns, nAndPagingFrameOffset, nrofiOCCH-MonitoringOccasionPerSSB-InPO, and the length of default DRX Cycle as signaled in SIBL
  • the alternative values may be an offset value from the broadcasted values, or a fixed value.
  • the offset may be negative.
  • the offset, or the fixed value may be specified or (pre)configured using RRC signaling.
  • the “paging assistance required” message in one embodiment, is an empty message that implicitly indicates that the UE needs assistance for avoiding paging collisions.
  • the “paging assistance required” message may contain information that either allows the gNB to understand where the paging opportunities from the other USIM(s) lie, and/or, directly indicates which parameter (value) can be modified/ reconfigured.
  • the parameter may be one or more of the parameters discussed above.
  • a lightweight NAS procedure is used instead of a NAS registration or service request procedure.
  • the UE 502 sends a NAS message (e.g., see messaging 508 - a “paging assistance required” message as shown in Figure 5 A) to an AMF 504 that indicates that paging collisions are foreseen, once the UE 502 is registered to the network (see block 506).
  • the AMF 504 may apply a solution or indicate to the NG-RAN to apply an AS solution when the UE needs to be paged.
  • the UE 502 is informed back from the AMF 504 in a NAS paging assistance indicating whether an AS-based or a NAS-based solution is to be applied in a confirmation message (see messaging 510 in Figure 5A).
  • the solution is not fixed (since more than one solution can be applied), the UE 502 is informed back in a NAS “paging assistance confirm” message (see messaging 512) as shown in Figure 5B, signaling which solution shall be applied.
  • Such an embodiment e.g., the lightweight procedure
  • the UE 502 may use the “regular PF+POs” to seek new assistance when the previous assistance/technique/solution is not effective anymore due to any reason, e.g., such as reconfiguration of pcch-Config, mobility, and/or the like of any of the involved USIMs.
  • Figure 6 depicts a user equipment apparatus 600 that may be used for paging management for multiple universal subscriber identity modules, according to embodiments of the disclosure.
  • the user equipment apparatus 600 is used to implement one or more of the solutions described above.
  • the user equipment apparatus 600 may be one embodiment of the remote unit 105 and/or the UE 205, described above.
  • the user equipment apparatus 600 may include a processor 605, a memory 610, an input device 615, an output device 620, and a transceiver 625.
  • the input device 615 and the output device 620 are combined into a single device, such as a touchscreen.
  • the user equipment apparatus 600 may not include any input device 615 and/or output device 620.
  • the user equipment apparatus 600 may include one or more of: the processor 605, the memory 610, and the transceiver 625, and may not include the input device 615 and/or the output device 620.
  • the transceiver 625 includes at least one transmitter 630 and at least one receiver 635.
  • the transceiver 625 communicates with one or more cells (or wireless coverage areas) supported by one or more base units 121.
  • the transceiver 625 is operable on unlicensed spectrum.
  • the transceiver 625 may include multiple UE panel supporting one or more beams.
  • the transceiver 625 may support at least one network interface 640 and/or application interface 645.
  • the application interface(s) 645 may support one or more APIs.
  • the network interface(s) 640 may support 3GPP reference points, such as Uu, Nl, PC5, etc. Other network interfaces 640 may be supported, as understood by one of ordinary skill in the art.
  • the processor 605 may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations.
  • the processor 605 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller hi some embodiments, the processor 605 executes instructions stored in the memory 610 to perform the methods and routines described herein.
  • the processor 605 is communicatively coupled to the memory 610, the input device 615, the output device 620, and the transceiver 625.
  • the processor 605 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.
  • main processor also known as “main processor”
  • baseband processor also known as “baseband radio processor”
  • the processor 605 controls the user equipment apparatus 600 to implement the above described UE behaviors.
  • the transceiver 625 receives, from a mobile wireless communication network associated with at least one of the USIMs, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision, and the processor 605 that determines a paging collision for paging occasions of at least a subset of the plurality of USIMs.
  • the transceiver 625 sends a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs .
  • the transceiver 625 further receives a same paging message according to the indicated solution in response to the request for assistance with alleviating the determined paging collision that was previously supposed to be received as part of the paging collision.
  • the processor 605 determines the paging collision based on a rule that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network. In one embodiment, the processor 605 determines the paging collision as at least a partial overlap in one of time and paging search space of at least one paging occasion of the paging occasions of the at least a subset of the plurality of USIMs.
  • the transceiver 625 sends a subsequent request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs in response to expiration of timer that is initiated in response to the initial request for assistance with alleviating the determined paging collision.
  • the processor 605 further selects a USIM of the at least a subset of USIMs for seeking assistance for alleviating paging collisions.
  • the processor 605 performs a registration procedure with a mobile wireless communication network, and the transceiver 625 receives an identifier from the mobile wireless communication network and checks for paging collisions between paging opportunities for the plurality of USIMs based on the received identifier. In one embodiment, in response to determining paging collisions between the paging opportunities for the plurality of USIMs, the processor 605 continuously performs deregistration from the mobile wireless communication network and re-registration with the mobile wireless communication network until no paging collisions between the paging opportunities for the plurality of USIMs are expected.
  • the transceiver 625 in response to notifying a mobile wireless communication network of paging collisions between paging opportunities for the plurality of USIMs, receives an offset value for monitoring paging opportunities for at least one of the plurality of USIMs associated with the paging collisions, and the processor 605 monitors paging opportunities for the at least one of the plurality of USIMs associated with the paging collisions using the received offset.
  • the processor 605 determines the paging collisions between paging opportunities for the plurality of USIMs and in response to the determined paging collisions, the transceiver 625 initiates a radio resource connection (“RRC”) with the mobile wireless communication network.
  • RRC radio resource connection
  • the memory 610 in one embodiment, is a computer readable storage medium.
  • the memory 610 includes volatile computer storage media.
  • the memory 610 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”).
  • the memory 610 includes non-volatile computer storage media.
  • the memory 610 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device.
  • the memory 610 includes both volatile and non-volatile computer storage media.
  • the memory 610 stores data related to paging management for multiple universal subscriber identity modules.
  • the memory 610 may store various parameters, panel/beam configurations, resource assignments, policies, and the like as described above.
  • the memory 610 also stores program code and related data, such as an operating system or other controller algorithms operating on the user equipment apparatus 600.
  • the input device 615 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like.
  • the input device 615 may be integrated with the output device 620, for example, as a touchscreen or similar touch-sensitive display.
  • the input device 615 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen.
  • the input device 615 includes two or more different devices, such as akeyboard and atouch panel.
  • the output device 620 in one embodiment, is designed to output visual, audible, and/or haptic signals.
  • the output device 620 includes an electronically controllable display or display device capable of outputting visual data to a user.
  • the output device 620 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user.
  • the output device 620 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 600, such as a smart watch, smart glasses, a heads-up display, or the like.
  • the output device 620 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
  • the output device 620 includes one or more speakers for producing sound.
  • the output device 620 may produce an audible alert or notification (e.g., a beep or chime).
  • the output device 620 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback.
  • all, or portions of the output device 620 may be integrated with the input device 615.
  • the input device 615 and output device 620 may form a touchscreen or similar touch-sensitive display.
  • the output device 620 may be located near the input device 615.
  • the transceiver 625 communicates with one or more network functions of a mobile communication network via one or more access networks.
  • the transceiver 625 operates under the control of the processor 605 to transmit messages, data, and other signals and also to receive messages, data, and other signals.
  • the processor 605 may selectively activate the transceiver 625 (or portions thereof) at particular times in order to send and receive messages.
  • the transceiver 625 includes at least transmitter 630 and at least one receiver 635.
  • One or more transmitters 630 may be used to provide UL communication signals to a base unit 121, such as the UL transmissions described herein.
  • one or more receivers 635 may be used to receive DL communication signals from the base unit 121, as described herein.
  • the user equipment apparatus 600 may have any suitable number of transmitters 630 and receivers 635.
  • the transmitter(s) 630 and the receiver(s) 635 may be any suitable type of transmitters and receivers.
  • the transceiver 625 includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.
  • the first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum.
  • the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components.
  • certain transceivers 625, transmitters 630, and receivers 635 may be implemented as physically separate components that access a shared hardware resource and/or software resource, such as for example, the network interface 640.
  • one or more transmitters 630 and/or one or more receivers 635 may be implemented and/or integrated into a single hardware component, such as a multi -transceiver chip, a system -on-a-chip, an ASIC, or other type of hardware component.
  • one or more transmitters 630 and/or one or more receivers 635 may be implemented and/or integrated into a multi -chip module.
  • other components such as the network interface 640 or other hardware components/circuits may be integrated with any number of transmitters 630 and/or receivers 635 into a single chip.
  • the transmitters 630 and receivers 635 may be logically configured as a transceiver 625 that uses one more common control signals or as modular transmitters 630 and receivers 635 implemented in the same hardware chip or in a multi -chip module.
  • Figure 7 depicts a network apparatus 700 that may be used for paging management for multiple universal subscriber identity modules, according to embodiments of the disclosure.
  • the network apparatus 700 may be one implementation of a RAN node, such as the base unit 121, the RAN node 210, or gNB, described above.
  • the base network apparatus 700 may include a processor 705, a memory 710, an input device 715, an output device 720, and a transceiver 725.
  • the input device 715 and the output device 720 are combined into a single device, such as a touchscreen.
  • the network apparatus 700 may not include any input device 715 and/or output device 720.
  • the network apparatus 700 may include one or more of: the processor 705, the memory 710, and the transceiver 725, and may not include the input device 715 and/or the output device 720.
  • the transceiver 725 includes at least one transmitter 730 and at least one receiver 735.
  • the transceiver 725 communicates with one or more remote units 105.
  • the transceiver 725 may support at least one network interface 740 and/or application interface 745.
  • the application interface(s) 745 may support one or more APIs.
  • the network interface(s) 740 may support 3GPP reference points, such as Uu, Nl, N2 and N3. Other network interfaces 740 may be supported, as understood by one of ordinary skill in the art.
  • the processor 705, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations.
  • the processor 705 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller.
  • the processor 705 executes instructions stored in the memory 710 to perform the methods and routines described herein.
  • the processor 705 is communicatively coupled to the memory 710, the input device 715, the output device 720, and the transceiver 725.
  • the processor 805 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio function.
  • main processor also known as “main processor”
  • baseband processor also known as “baseband radio processor”
  • the network apparatus 700 is a RAN node (e.g., gNB) that provides paging assistance for alleviating paging collisions, as described herein.
  • the transceiver (725) sends, to a user equipment (“UE”) device comprising a plurality of universal subscriber identity modules (“USIMs”), an indication that a mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision, and receives, from the UE, a request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs.
  • UE user equipment
  • USIMs universal subscriber identity modules
  • the processor 705 that determines a solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs and the transceiver 725 sends the determined solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs to the UE.
  • transceiver 725 resends a paging message according to the determined solution in response to the received request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs.
  • the processor 705 stores one or more paging messages that are sent to the UE for a predetermined period of time, the stored paging messages accessed for resending paging messages that do not receive a response.
  • the processor 705 configures at least one rule for the UE that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network.
  • the transceiver 725 receives an indication from a user equipment (“UE”) device that supports a plurality of universal subscriber identity modules (“USIMs”) of paging collisions between paging opportunities of the plurality of USIMs and the processor 705 determines an offset value for modifying at least one parameter that is used in determining paging opportunities for at least one of the plurality of USIMs that is associated with the paging collisions. In certain embodiments, the transceiver 725 sends the determined offset to the UE for modifying the determination of the paging opportunities for the at least one of the plurality of USIMs using the determined offset.
  • UE user equipment
  • USIMs universal subscriber identity modules
  • the memory 710 in one embodiment, is a computer readable storage medium.
  • the memory 710 includes volatile computer storage media.
  • the memory 710 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”).
  • the memory 710 includes non-volatile computer storage media.
  • the memory 710 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device.
  • the memory 710 includes both volatile and non-volatile computer storage media.
  • the memory 710 stores data related to paging management for multiple universal subscriber identity modules.
  • the memory 710 may store parameters, configurations, resource assignments, policies, and the like, as described above.
  • the memory 710 also stores program code and related data, such as an operating system or other controller algorithms operating on the network apparatus 700.
  • the input device 715 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like.
  • the input device 715 may be integrated with the output device 720, for example, as a touchscreen or similar touch-sensitive display.
  • the input device 715 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen.
  • the input device 715 includes two or more different devices, such as akeyboard and atouch panel.
  • the output device 720 in one embodiment, is designed to output visual, audible, and/or haptic signals.
  • the output device 720 includes an electronically controllable display or display device capable of outputting visual data to a user.
  • the output device 720 may include, but is not limited to, an FCD display, an FED display, an OFED display, a projector, or similar display device capable of outputting images, text, or the like to a user.
  • the output device 720 may include a wearable display separate from, but communicatively coupled to, the rest of the network apparatus 700, such as a smart watch, smart glasses, a heads-up display, or the like.
  • the output device 720 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
  • the output device 720 includes one or more speakers for producing sound.
  • the output device 720 may produce an audible alert or notification (e.g., a beep or chime).
  • the output device 720 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback.
  • all, or portions of the output device 720 may be integrated with the input device 715.
  • the input device 715 and output device 720 may form a touchscreen or similar touch-sensitive display.
  • the output device 720 may be located near the input device 715.
  • the transceiver 725 includes at least transmitter 730 and at least one receiver 735.
  • One or more transmitters 730 may be used to communicate with the UE, as described herein.
  • one or more receivers 735 may be used to communicate with network functions in the NPN, PLMN and/or RAN, as described herein.
  • the network apparatus 700 may have any suitable number of transmitters 730 and receivers 735.
  • the transmitter(s) 730 and the receiver(s) 735 may be any suitable type of transmitters and receivers.
  • FIG. 8 is a flowchart diagram of a method 800 for paging management for multiple universal subscriber identity modules.
  • the method 800 may be performed by a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 600.
  • the method 700 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the method 800 includes receiving 805, from a mobile wireless communication network associated with at least one of a plurality of universal subscriber identity modules (“USIMs”) of a user equipment (“UE”) device, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision.
  • the method 800 includes determining 810 a paging collision for paging occasions of at least a subset of the plurality of USIMs.
  • the method 800 includes sending 815 a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality ofUSIMs. The method 800 ends.
  • Figure 9 is a flowchart diagram of a method 900 for paging management for multiple universal subscriber identity modules.
  • the method 900 may be performed by a network device as described herein, for example, the network equipment apparatus 700.
  • the method 900 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the method 900 includes sending 905, to a user equipment (“UE”) device comprising a plurality of universal subscriber identity modules (“USIMs”), an indication that a mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs.
  • the method 900 includes receiving 910, from the UE, a request for assistance with alleviating the determined paging collision of the at least a subset of the plurality ofUSIMs and an indication of a solution to be used for alleviating the determined paging collision.
  • the method 900 includes determining 915 a solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs. In further embodiments, the method 900 includes sending 920 the determined solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs to the UE. The method 900 ends.
  • Figure 10 is a flowchart diagram of a method 1000 for paging management for multiple universal subscriber identity modules.
  • the method 1000 may be performed by a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700.
  • the method 1000 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the method 1000 includes performing 1005 a registration procedure for a user equipment (”UE”) with a mobile wireless communication network, the UE comprising a plurality of universal subscriber identity modules (“USIMs”). In further embodiments, the method 1000 includes receiving 1010 an identifier from the mobile wireless communication network.
  • the method 1000 includes checking 1015 for paging collisions between paging opportunities for the plurality ofUSIMs based on the received identifier. In certain embodiments, the method 1000 includes, in response to determining paging collisions between the paging opportunities for the plurality of USIMs, continuously performing 1020 deregistration from the mobile wireless communication network and re-registration with the mobile wireless communication network until no paging collisions between the paging opportunities for the plurality of USIMs are expected. The method 1020 ends.
  • Figure 11 is a flowchart diagram of a method 1100 for paging management for multiple universal subscriber identity modules.
  • the method 1100 may be performed by a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700.
  • the method 1100 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the method 1100 includes, in response to notifying a mobile wireless communication network of paging collisions between paging opportunities of a plurality of universal subscriber identity modules (“USIMs”) of a user equipment (“UE”) device, receiving 1105 an offset value for monitoring paging opportunities for at least one of the plurality of USIMs associated with the paging collisions.
  • the method 1100 includes monitoring 1110 paging opportunities forthe at least one ofthe plurality of USIMs associated with the paging collisions using the received offset. The method 1100 ends.
  • Figure 12 is a flowchart diagram of a method 1200 for paging management for multiple universal subscriber identity modules.
  • the method 1200 may be performed by a network device as described herein, for example, the network equipment apparatus 700.
  • the method 1200 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the method 1200 includes receiving 1205 an indication from a user equipment (“UE”) device that supports a plurality of universal subscriber identity modules (“USIMs”) of paging collisions between paging opportunities of the plurality of USIMs.
  • the method 1200 includes determining 1210 an offset value for modifying at least one parameter that is used in determining paging opportunities for at least one of the plurality of USIMs that is associated with the paging collisions.
  • the method 1200 includes sending 1215 the determined offset to the UE for modifying the determination of the paging opportunities for the at least one of the plurality of USIMs using the determined offset. The method 1200 ends.
  • a first apparatus for paging management for multiple universal subscriber identity modules.
  • the first apparatus may be embodied as a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700.
  • the first apparatus includes a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the first apparatus includes a plurality of universal subscriber identity modules (“USIMs”), a transceiver that receives, from a mobile wireless communication network associated with at least one of the USIMs, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision, and a processor that determines a paging collision for paging occasions of at least a subset of the plurality of USIMs.
  • the transceiver sends a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs.
  • the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises a one bit flag. In some embodiments, the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises an offset value for changing a starting position of a first paging occasion.
  • the transceiver further receives a same paging message according to the indicated solution in response to the request for assistance with alleviating the determined paging collision that was previously supposed to be received as part of the paging collision.
  • the processor determines the paging collision based on a rule that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network.
  • the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining at least one paging collision among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
  • the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining paging collisions among all received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs. In some embodiments, the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining a paging collision for a threshold number of contiguous paging opportunities among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
  • the processor determines the paging collision as at least a partial overlap in one of time and paging search space of at least one paging occasion of the paging occasions of the at least a subset of the plurality of USIMs.
  • the transceiver sends a subsequent request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs in response to expiration of timer that is initiated in response to the initial request for assistance with alleviating the determined paging collision.
  • the processor further selects a USIM of the at least a subset of USIMs for seeking assistance for alleviating paging collisions based at least on one of the following criteria: a preference for new radio (“NR”) USIM in case of inter-radio access technologies (“RAT”) over other RAT USIMs; in response to not receiving a response from a mobile wireless communication network corresponding to one of the USIMs to the request for assistance with alleviating the determined paging collision, selecting a mobile wireless communication network for a next USIM to request assistance with alleviating the determined paging collision; a preference for a solution for alleviating the determined paging collision provided by a mobile wireless communication network corresponding to one of the USIMs over a different solution provided by a mobile wireless communication network corresponding to a different USIM; a preference for using an equivalent home public land mobile network (“EHPUMN”) USIM over a visited PUMN (“VPUMN”) USIM; and a preference for a USIM for a mobile wireless communication network that has
  • a first method is disclosed for paging management for multiple universal subscriber identity modules.
  • the first method may be performed by a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700.
  • the first method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the first method includes receiving, from a mobile wireless communication network associated with at least one of a plurality of universal subscriber identity modules (“USIMs”) of a user equipment (“UE”) device, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIM and an indication of a solution to be used for alleviating the determined paging collision, determining a paging collision for paging occasions of at least a subset of the plurality of USIMs, and sending a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs.
  • USIMs universal subscriber identity modules
  • UE user equipment
  • the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises a one bit flag. In some embodiments, the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises an offset value for changing a starting position of a first paging occasion. [00166] In certain embodiments, the method includes receiving an indication of a solution to be used for alleviating the determined paging collision. In one embodiment, the method includes receiving a same paging message according to the indicated solution in response to the request for assistance with alleviating the determined paging collision that was previously supposed to be received as part of the paging collision.
  • the method includes determining the paging collision based on a rule that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network.
  • the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining at least one paging collision among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
  • the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining paging collisions among all received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs. In some embodiments, the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining a paging collision for a threshold number of contiguous paging opportunities among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
  • the method includes determining the paging collision as at least a partial overlap in one of time and paging search space of at least one paging occasion of the paging occasions of the at least a subset of the plurality of USIMs. In some embodiments, the method includes sending a subsequent request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs in response to expiration of timer that is initiated in response to the initial request for assistance with alleviating the determined paging collision.
  • the method includes selecting aUSIM of the at least a subset of USIMs for seeking assistance for alleviating paging collisions based at least on one of the following criteria: a preference for new radio (“NR”) USIM in case of inter-radio access technologies (“RAT”) over other RAT USIMs; in response to not receiving a response from a mobile wireless communication network corresponding to one of the USIMs to the request for assistance with alleviating the determined paging collision, selecting a mobile wireless communication network for a next USIM to request assistance with alleviating the determined paging collision; a preference for a solution for alleviating the determined paging collision provided by a mobile wireless communication network corresponding to one of the USIMs over a different solution provided by a mobile wireless communication network corresponding to a different USIM; a preference for using an equivalent home public land mobile network (“EHPUMN”) USIM over a visited PUMN (“VPUMN”) USIM; and a preference for a USIM for a mobile wireless communication network that has
  • a second apparatus for paging management for multiple universal subscriber identity modules.
  • the second apparatus may be embodied as a network device as described herein, for example, the network equipment apparatus 700.
  • the second apparatus may be embodied by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the second apparatus includes a transceiver that sends, to a user equipment (“UE”) device comprising a plurality of universal subscriber identity modules (“USIMs”), an indication that a mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision and receives, from the UE, a request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs.
  • the second apparatus includes a processor that determines a solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs.
  • the transceiver sends the determined solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs to the UE.
  • the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises a one bit flag. In some embodiments, the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises an offset value for changing a starting position of a first paging occasion.
  • the transceiver resends a paging message according to the determined solution in response to the received request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs.
  • the processor further stores one or more paging messages that are sent to the UE for a predetermined period of time, the stored paging messages accessed for resending paging messages that do not receive a response.
  • the processor further configures at least one rule for the UE that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network.
  • the rule indicates that the UE sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining at least one paging collision among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
  • the rule indicates that the UE sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining paging collisions among all received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs. In certain embodiments, the rule indicates that the UE sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining a paging collision for a threshold number of contiguous paging opportunities among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs. [00177] A second method is disclosed for paging management for multiple universal subscriber identity modules.
  • the second method may be performed by a network device as described herein, for example, the network equipment apparatus 700.
  • the second method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the second method includes sending, to a user equipment (“UE”) device comprising a plurality of universal subscriber identity modules (“USIMs”), an indication that a mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision, receiving, from the UE, a request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs, determining a solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs, and sending the determined solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs to the UE.
  • UE user equipment
  • USIMs universal subscriber identity modules
  • the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises a one bit flag.
  • the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises an offset value for changing a starting position of a first paging occasion.
  • the method includes resending a paging message according to the determined solution in response to the received request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs.
  • the method includes storing one or more paging messages that are sent to the UE for a predetermined period of time, the stored paging messages accessed for resending paging messages that do not receive a response.
  • the method includes configuring at least one rule for the UE that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network.
  • the rule indicates that the UE sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining at least one paging collision among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
  • the rule indicates that the UE sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining paging collisions among all received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
  • the rule indicates that the UE sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining a paging collision for a threshold number of contiguous paging opportunities among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
  • a third apparatus is disclosed for paging management for multiple universal subscriber identity modules.
  • the third apparatus may be embodied as a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700.
  • the third apparatus includes a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the third apparatus includes a plurality of universal subscriber identity modules (“USIMs”), a processor that performs a registration procedure with a mobile wireless communication network, and a transceiver that receives an identifier from the mobile wireless communication network and checks for paging collisions between paging opportunities for the plurality of USIMs based on the received identifier.
  • USIMs universal subscriber identity modules
  • the processor in response to determining paging collisions between the paging opportunities for the plurality of USIMs, continuously performs deregistration from the mobile wireless communication network and re-registration with the mobile wireless communication network until no paging collisions between the paging opportunities for the plurality of USIMs are expected.
  • a third method is disclosed for paging management for multiple universal subscriber identity modules.
  • the third method may be performed by a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700.
  • the third method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the third method includes performing a registration procedure for a user equipment (”UE”) with a mobile wireless communication network, the UE comprising a plurality of universal subscriber identity modules (“USIMs”), receiving an identifier from the mobile wireless communication network, checking for paging collisions between paging opportunities for the plurality of USIMs based on the received identifier, and in response to determining paging collisions between the paging opportunities for the plurality of USIMs, continuously performing deregistration from the mobile wireless communication network and re registration with the mobile wireless communication network until no paging collisions between the paging opportunities for the plurality of USIMs are expected.
  • UE user equipment
  • USIMs universal subscriber identity modules
  • a fourth apparatus is disclosed for paging management for multiple universal subscriber identity modules.
  • the fourth apparatus may be embodied as a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700.
  • the fourth apparatus includes a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the fourth apparatus includes a plurality of universal subscriber identity modules (“USIMs”), a transceiver that, in response to notifying a mobile wireless communication network of paging collisions between paging opportunities for the plurality of USIMs, receives an offset value for monitoring paging opportunities for at least one of the plurality of USIMs associated with the paging collisions, and a processor that monitors paging opportunities for the at least one of the plurality of USIMs associated with the paging collisions using the received offset.
  • USIMs universal subscriber identity modules
  • the processor determines the paging collisions between paging opportunities for the plurality of USIMs and in response to the determined paging collisions, the transceiver initiates a radio resource connection (“RRC”) with the mobile wireless communication network.
  • RRC radio resource connection
  • the RRC further comprises at least one of a new establishment cause and a logical channel identifier (“UCID”) for informing the mobile wireless communication network of a reason for initiating the RRC.
  • the offset value is fixed according to a predetermined specification.
  • the offset value is for at least one of the following parameters: a number of time slots, a number of subframes, a number of paging frames, a firstPDCCH-MonitoringOccasionOfiO parameter, and a user equipment identifier.
  • the offset value comprises a fixed value for the at least one of the parameters. In certain embodiments, the offset value is a negative value. In various embodiments, the offset value is configured using radio resource connection (“RRC”) signaling. In some embodiments, the notification of the paging collisions that is sent to the mobile wireless communication network further comprises an indication of at least one parameter associated with monitoring paging opportunities for modifying with the offset value.
  • RRC radio resource connection
  • a fourth method is disclosed for paging management for multiple universal subscriber identity modules.
  • the fourth method may be performed by a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700.
  • the fourth method is performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the fourth method includes, in response to notifying a mobile wireless communication network of paging collisions between paging opportunities of a plurality of universal subscriber identity modules (“USIMs”) of a user equipment (“UE”) device, receiving an offset value for monitoring paging opportunities for at least one of the plurality of USIMs associated with the paging collisions, and monitoring paging opportunities for the at least one of the plurality of USIMs associated with the paging collisions using the received offset.
  • USIMs universal subscriber identity modules
  • UE user equipment
  • the fourth method includes determining the paging collisions between paging opportunities for the plurality of USIMs and in response to the determined paging collisions, initiating a radio resource connection (“RRC”) with the mobile wireless communication network.
  • RRC radio resource connection
  • the RRC further comprises at least one of a new establishment cause and a logical channel identifier (“LCID”) for informing the mobile wireless communication network of a reason for initiating the RRC.
  • LCID logical channel identifier
  • the offset value is fixed according to a predetermined specification.
  • the offset value is for at least one of the following parameters: a number of time slots, a number of subframes, a number of paging frames, a firstPDCCH-MonitoringOccasionOfiO parameter, and a user equipment identifier.
  • the offset value comprises a fixed value for the at least one of the parameters. In certain embodiments, the offset value is a negative value. In various embodiments, the offset value is configured using radio resource connection (“RRC”) signaling. In some embodiments, the notification of the paging collisions that is sent to the mobile wireless communication network further comprises an indication of at least one parameter associated with monitoring paging opportunities for modifying with the offset value.
  • RRC radio resource connection
  • a fifth apparatus is disclosed for paging management for multiple universal subscriber identity modules.
  • the fifth apparatus may be embodied as a network device as described herein, for example, the network equipment apparatus 700.
  • the fifth apparatus may be embodied by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the fifth apparatus includes a transceiver that receives an indication from a user equipment (“UE”) device that supports a plurality of universal subscriber identity modules (“USIMs”) of paging collisions between paging opportunities of the plurality of USIMs and a processor that determines an offset value for modifying at least one parameter that is used in determining paging opportunities for at least one of the plurality of USIMs that is associated with the paging collisions.
  • the transceiver sends the determined offset to the UE for modifying the determination of the paging opportunities for the at least one of the plurality of USIMs using the determined offset.
  • a fifth method is disclosed for paging management for multiple universal subscriber identity modules.
  • the fifth method may be performed by a network device as described herein, for example, the network equipment apparatus 700.
  • the fifth method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the fifth method includes receiving an indication from a user equipment (“UE”) device that supports a plurality of universal subscriber identity modules (“USIMs”) of paging collisions between paging opportunities of the plurality of USIMs, determining an offset value for modifying at least one parameter that is used in determining paging opportunities for at least one of the plurality of U SIMs that is associated with the paging collisions, and sending the determined offset to the UE for modifying the determination of the paging opportunities for the at least one of the plurality of USIMs using the determined offset.
  • UE user equipment
  • USIMs universal subscriber identity modules

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Apparatuses, methods, and systems are disclosed for paging management for multiple universal subscriber identity modules. One apparatus (600) includes a plurality of universal subscriber identity modules ("USIMs"), a transceiver (625) that receives, from a mobile wireless communication network associated with at least one of the USIMs, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision, and a processor (605) that determines a paging collision for paging occasions of at least a subset of the plurality of USIMs. The transceiver (625) sends a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs.

Description

PAGING MANAGEMENT FOR MULTIPLE UNIVERSAL SUBSCRIBER
IDENTITY MODULES
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to United States Provisional Patent Application Number 63/050064 entitled “RECEIVING PAGING IN MUSIM SCENARIO” and filed on July 9, 2020, for Prateek Basu Mallick, et al., which is incorporated herein by reference. This application also claims priority to United States Provisional Patent Application Number 63/050059 entitled “AVOIDANCE OF PAGING COLLISION IN MUSIM SCENARIO” and filed on July 9, 2020, for Prateek Basu Mallick, et al., which is incorporated herein by reference.
FIELD
[0002] The subject matter disclosed herein relates generally to wireless communications and more particularly relates to paging management for multiple universal subscriber identity modules.
BACKGROUND
[0003] In certain wireless communication systems, a User Equipment device (“UE”) is able to connect with a fifth-generation (“5G”) core network (i.e., “5GC”) in a Public Land Mobile Network (“PLMN”). In wireless networks, certain UEs support multiple universal subscriber identity modules.
BRIEF SUMMARY
[0004] Disclosed are procedures for paging management for multiple universal subscriber identity modules. Said procedures may be implemented by apparatus, systems, methods, and/or computer program products.
[0005] One method of a user equipment device (“UE”) includes receiving, from a mobile wireless communication network associated with at least one of a plurality of universal subscriber identity modules (“USIMs”) of a user equipment (“UE”) device, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs, determining a paging collision for paging occasions of at least a subset of the plurality of USIMs, and sending a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs. [0006] One method of a network function in a mobile communication network includes sending, to a user equipment (“UE”) device comprising a plurality of universal subscriber identity modules (“USIMs”), an indication that a mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs, receiving, from the UE, a request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs, determining a solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs, and sending the determined solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs to the UE.
BRIEF DESCRIPTION OF THE DRAWINGS
[0007] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:
[0008] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for paging management for multiple universal subscriber identity modules;
[0009] Figure 2A is a diagram illustrating one embodiment of paging opportunities that overlap;
[0010] Figure 2B is a diagram illustrating another embodiment of paging opportunities that overlap;
[0011] Figure 3 is a signal flow diagram illustrating one embodiment of a procedure for paging management for multiple universal subscriber identity modules;
[0012] Figure 4A is a diagram illustrating one embodiment of downlink timing of two cells;
[0013] Figure 4B is a diagram illustrating one embodiment of using an absolute time scale to compare timelines;
[0014] Figure 5 A is a signal flow diagram illustrating one embodiment of a procedure for paging management for multiple universal subscriber identity modules;
[0015] Figure 5B is a signal flow diagram illustrating one embodiment of a procedure for paging management for multiple universal subscriber identity modules;
[0016] Figure 6 is a block diagram illustrating one embodiment of a user equipment apparatus that may be used for paging management for multiple universal subscriber identity modules; [0017] Figure 7 is a block diagram illustrating one embodiment of a network apparatus that may be used for paging management for multiple universal subscriber identity modules;
[0018] Figure 8 is a flowchart diagram illustrating one embodiment of a method for paging management for multiple universal subscriber identity modules;
[0019] Figure 9 is a flowchart diagram illustrating one embodiment of a method for paging management for multiple universal subscriber identity modules;
[0020] Figure 10 is a flowchart diagram illustrating one embodiment of a method for paging management for multiple universal subscriber identity modules;
[0021] Figure 11 is a flowchart diagram illustrating one embodiment of a method for paging management for multiple universal subscriber identity modules; and
[0022] Figure 12 is a flowchart diagram illustrating one embodiment of a method for paging management for multiple universal subscriber identity modules.
DETAILED DESCRIPTION
[0023] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects.
[0024] For example, the disclosed embodiments may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.
[0025] Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non- transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.
[0026] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
[0027] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.
[0028] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object- oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”), wireless LAN (“WLAN”), or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider (“ISP”)).
[0029] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.
[0030] Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.
[0031] As used herein, a list with a conjunction of “and/or” includes any single item in the list or a combination of items in the list. For example, a list of A, B and/or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one or more of’ includes any single item in the list or a combination of items in the list. For example, one or more of A, B and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C. As used herein, a list using the terminology “one of’ includes one and only one of any single item in the list. For example, “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C. As used herein, “a member selected from the group consisting of A, B, and C,” includes one and only one of A, B, or C, and excludes combinations of A, B, and C.” As used herein, “a member selected from the group consisting of A, B, and C and combinations thereof’ includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C or a combination of A, B and C.
[0032] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the f mctions/acts specified in the flowchart diagrams and/or block diagrams.
[0033] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the flowchart diagrams and/or block diagrams.
[0034] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart diagrams and/or block diagrams.
[0035] The flowchart diagrams and/or block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods, and program products according to various embodiments. In this regard, each block in the flowchart diagrams and/or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
[0036] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.
[0037] Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.
[0038] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.
[0039] Generally, the present disclosure describes systems, methods, and apparatus for paging management for multiple universal subscriber identity modules. In certain embodiments, the methods may be performed using computer code embedded on a computer-readable medium. In certain embodiments, an apparatus or system may include a computer-readable medium containing computer-readable code which, when executed by a processor, causes the apparatus or system to perform at least a portion of the below described solutions.
[0040] Certain mobile devices can support multiple universal subscription identifier modules (“USIM”). A multi-USIM device is a device that supports more than one SIM/USIM in the same user/mobile equipment (“UE”). In such an embodiment, the USIMs of the multi-USIM device may belong to the same or different network operators. Furthermore, the USIMs may be associated with networks that have the same or different radio access technologies, e.g., 5G New Radio (“NR”), 4G Fong Term Evolution (“FTE”), or the like. A multi-USIM device may wish to receive paging for all associated USIMs, e.g., the USIMs are operational simultaneously in the device. However, certain issues may arise with paging for multi-USIM devices such as how does the UE foresee a paging collision across USIMs and what is the UE behavior when it determines that paging opportunities for multiple USIMs collide or overlap. When and how often is it allowed to seek assistance from the network to resolve paging collisions? Which USIM is used for seeking paging collision avoidance assistance from the corresponding network?
[0041] The subject matter disclosed herein describes various solutions for resolving paging collisions for multi-USIM devices. In one embodiment, the UE may calculate the paging occasions and seek assistance before initiating registration. In another embodiment, the UE sends a non-access stratum (“NAS”) registration request first and calculates the paging occasions and determines collisions from then on. In yet another embodiment, the network allows the UE to seek paging assistance knowing that the network supports providing such assistance. Further, a rule may be used that defines situations where a UE is allowed to declare a paging collision of at least two USIMs and thereby seek assistance, e.g., transmit a paging assistance required message.
[0042] The proposed solutions remedy the problems with the existing solutions, which do not specify when the UE is allowed to seek assistance for paging collisions among multiple USIMs and depend on a hit-or-miss method that is dependent on whether the network supports paging collision assistance. Otherwise, the UE battery life may be wasted in transitioning to a radio resource control (“RRC”) connection. Moreover, a core network-based solution may potentially delay paging reception.
[0043] Figure 1 depicts a wireless communication system 100 for paging management for multiple universal subscriber identity modules, according to embodiments of the disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, a Fifth-Generation Radio Access Network (“5G-RAN”) 115, and a mobile core network 140. The 5G-RAN 115 and the mobile core network 140 form a mobile communication network. The 5G- RAN 115 may be composed of a 3GPP access network 120 containing at least one cellular base unit 121 and/or a non-3GPP access network 130 containing at least one access point 131. The remote unit 105 communicates with the 3GPP access network 120 using 3GPP communication links 123 and/or communicates with the non-3GPP access network 130 using non-3GPP communication links 133. Even though a specific number of remote units 105, 3GPP access networks 120, cellular base units 121, 3GPP communication links 123, non-3GPP access networks 130, access points 131, non-3GPP communication links 133, and mobile core networks 140 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 105, 3GPP access networks 120, cellular base units 121, 3GPP communication links 123, non-3GPP access networks 130, access points 131, non-3GPP communication links 133, and mobile core networks 140 may be included in the wireless communication system 100.
[0044] In one implementation, the RAN 120 is compliant with the 5G system specified in the Third Generation Partnership Project (“3GPP”) specifications. For example, the RAN 120 may be a NG-RAN, implementing NR RAT and/or FTE RAT. In another example, the RAN 120 may include non-3GPP RAT (e.g., Wi-Fi® or Institute of Electrical and Electronics Engineers (“IEEE”) 802.11-family compliant WLAN). In another implementation, the RAN 120 is compliant with the LTE system specified in the 3GPP specifications. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication network, for example Worldwide Interoperability for Microwave Access (“WiMAX”) or IEEE 802.16-family standards, among other networks. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
[0045] In one embodiment, the remote units 105 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. In some embodiments, the remote units 105 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 105 may be referred to as the UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit (”WTRU”), a device, or by other terminology used in the art. In various embodiments, the remote unit 105 includes a subscriber identity and/or identification module (“SIM”) and the mobile equipment (“ME”) providing mobile termination functions (e.g., radio transmission, handover, speech encoding and decoding, error detection and correction, signaling and access to the SIM). In certain embodiments, the remote unit 105 may include a terminal equipment (“TE”) and/or be embedded in an appliance or device (e.g., a computing device, as described above).
[0046] In one embodiment, the remote units 105 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), smart appliances (e.g., appliances connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), or the like. In some embodiments, the remote units 105 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 105 may be referred to as UEs, subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, user terminals, wireless transmit/receive unit (“WTRU”), a device, or by other terminology used in the art.
[0047] The remote units 105 may communicate directly with one or more of the cellular base units 121 in the 3GPP access network 120 via uplink (“UL”) and downlink (“DL”) communication signals. Furthermore, the UL and DL communication signals may be carried over the 3GPP communication links 123. Similarly, the remote units 105 may communicate with one or more access points 131 in the non-3GPP access network(s) 130 via UL and DL communication signals carried over the non-3GPP communication links 133. Here, the access networks 120 and 130 are intermediate networks that provide the remote units 105 with access to the mobile core network 140.
[0048] In some embodiments, the remote units 105 communicate with a remote host (e.g., in the data network 150 or in the data network 160) via a network connection with the mobile core network 140. For example, an application 107 (e.g., web browser, media client, telephone and/or Voice-over-Intemet-Protocol (“VoIP”) application) in a remote unit 105 may trigger the remote unit 105 to establish a protocol data unit (“PDU”) session (or other data connection) with the mobile core network 140 via the 5G-RAN 115 (i.e., via the 3GPP access network 120 and/or non- 3GPP network 130). The mobile core network 140 then relays traffic between the remote unit 105 and the remote host using the PDU session. The PDU session represents a logical connection between the remote unit 105 and a User Plane Function (“UPF”) 141.
[0049] In order to establish the PDU session (or PDN connection), the remote unit 105 must be registered with the mobile core network 140 (also referred to as “attached to the mobile core network” in the context of a Fourth Generation (“4G”) system). Note that the remote unit 105 may establish one or more PDU sessions (or other data connections) with the mobile core network 140. As such, the remote unit 105 may have at least one PDU session for communicating with the packet data network 150. Additionally - or alternatively - the remote unit 105 may have at least one PDU session for communicating with the packet data network 160. The remote unit 105 may establish additional PDU sessions for communicating with other data networks and/or other communication peers.
[0050] In the context of a 5G system (“5GS”), the term “PDU Session” refers to a data connection that provides end-to-end (“E2E”) user plane (“UP”) connectivity between the remote unit 105 and a specific Data Network (“DN”) through the UPF 131. A PDU Session supports one or more Quality of Service (“QoS”) Flows. In certain embodiments, there may be a one-to-one mapping between a QoS Flow and a QoS profile, such that all packets belonging to a specific QoS Flow have the same 5G QoS Identifier (“5QI”).
[0051] In the context of a 4G/FTE system, such as the Evolved Packet System (“EPS”), a Packet Data Network (“PDN”) connection (also referred to as EPS session) provides E2E UP connectivity between the remote unit and a PDN. The PDN connectivity procedure establishes an EPS Bearer, i.e., atunnel between the remote unit 105 and a Packet Gateway (“PGW”, not shown) in the mobile core network 130. In certain embodiments, there is a one-to-one mapping between an EPS Bearer and a QoS profile, such that all packets belonging to a specific EPS Bearer have the same QoS Class Identifier (“QCI”).
[0052] As described in greater detail below, the remote unit 105 may use a first data connection (e.g., PDU Session) established with the first mobile core network 130 to establish a second data connection (e.g., part of a second PDU session) with the second mobile core network 140. When establishing a data connection (e.g., PDU session) with the second mobile core network 140, the remote unit 105 uses the first data connection to register with the second mobile core network 140.
[0053] The cellular base units 121 may be distributed over a geographic region. In certain embodiments, a cellular base unit 121 may also be referred to as an access terminal, a base, a base station, a Node-B (“NB”), an Evolved Node B (abbreviated as eNodeB or “eNB,” also known as Evolved Universal Terrestrial Radio Access Network (“E-UTRAN”) Node B), a 5G/NR Node B (“gNB”), a Home Node-B, a Home Node-B, a relay node, a device, or by any other terminology used in the art. The cellular base units 121 are generally part of a radio access network (“RAN”), such as the 3GPP access network 120, that may include one or more controllers communicably coupled to one or more corresponding cellular base units 121. These and other elements of radio access network are not illustrated but are well known generally by those having ordinary skill in the art. The cellular base units 121 connect to the mobile core network 140 via the 3GPP access network 120.
[0054] The cellular base units 121 may serve a number of remote units 105 within a serving area, for example, a cell or a cell sector, via a 3GPP wireless communication link 123. The cellular base units 121 may communicate directly with one or more of the remote units 105 via communication signals. Generally, the cellular base units 121 transmit DL communication signals to serve the remote units 105 in the time, frequency, and/or spatial domain. Furthermore, the DL communication signals may be carried over the 3GPP communication links 123. The 3GPP communication links 123 may be any suitable carrier in licensed or unlicensed radio spectrum. The 3GPP communication links 123 facilitate communication between one or more of the remote units 105 and/or one or more of the cellular base units 121. Note that during NR operation on unlicensed spectrum (referred to as “NR-U”), the base unit 121 and the remote unit 105 communicate over unlicensed (i.e., shared) radio spectrum.
[0055] The non-3GPP access networks 130 may be distributed over a geographic region. Each non-3GPP access network 130 may serve a number of remote units 105 with a serving area. An access point 131 in a non-3GPP access network 130 may communicate directly with one or more remote units 105 by receiving UL communication signals and transmitting DL communication signals to serve the remote units 105 in the time, frequency, and/or spatial domain. Both DL and UL communication signals are carried over the non-3GPP communication links 133. The 3GPP communication links 123 and non-3GPP communication links 133 may employ different frequencies and/or different communication protocols. In various embodiments, an access point 131 may communicate using unlicensed radio spectrum. The mobile core network 140 may provide services to a remote unit 105 via the non-3GPP access networks 130, as described in greater detail herein.
[0056] In some embodiments, a non-3GPP access network 130 connects to the mobile core network 140 via an interworking entity 135. The interworking entity 135 provides an interworking between the non-3GPP access network 130 and the mobile core network 140. The interworking entity 135 supports connectivity via the “N2” and “N3” interfaces. As depicted, both the 3GPP access network 120 and the interworking entity 135 communicate with the AMF 143 using a “N2” interface. The 3GPP access network 120 and interworking entity 135 also communicate with the UPF 141 using a “N3” interface. While depicted as outside the mobile core network 140, in other embodiments the interworking entity 135 may be a part of the core network. While depicted as outside the non-3GPP RAN 130, in other embodiments the interworking entity 135 may be a part of the non-3GPP RAN 130. [0057] In certain embodiments, a non-3GPP access network 130 may be controlled by an operator of the mobile core network 140 and may have direct access to the mobile core network 140. Such a non-3GPP AN deployment is referred to as a “trusted non-3GPP access network.” A non-3GPP access network 130 is considered as “trusted” when it is operated by the 3GPP operator, or a trusted partner, and supports certain security features, such as strong air-interface encryption. In contrast, a non-3GPP AN deployment that is not controlled by an operator (or trusted partner) of the mobile core network 140, does not have direct access to the mobile core network 140, or does not support the certain security features is referred to as a “non-trusted” non-3GPP access network. An interworking entity 135 deployed in atrusted non-3GPP access network 130 may be referred to herein as a Trusted Network Gateway Function (“TNGF”). An interworking entity 135 deployed in a non-trusted non-3GPP access network 130 may be referred to herein as a non-3GPP interworking function (“N3IWF”). While depicted as a part of the non-3GPP access network 130, in some embodiments the N3IWF may be a part of the mobile core network 140 or may be located in the data network 150.
[0058] In one embodiment, the mobile core network 140 is a 5G core (“5GC”) or the evolved packet core (“EPC”), which may be coupled to a data network 150, like the Internet and private data networks, among other data networks. A remote unit 105 may have a subscription or other account with the mobile core network 140. Each mobile core network 140 belongs to a single public land mobile network (“PLMN”). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.
[0059] The mobile core network 140 includes several network functions (“NFs”). As depicted, the mobile core network 140 includes at least one UPF (“UPF”) 141. The mobile core network 140 also includes multiple control plane functions including, but not limited to, an Access and Mobility Management Function (“AMF”) 143 that serves the 5G-RAN 115, a Session Management Function (“SMF”) 145, a Policy Control Function (“PCF”) 146, an Authentication Server Function (“AUSF”) 147, a Unified Data Management (“UDM”) and Unified Data Repository function (“UDR”).
[0060] The UPF(s) 141 is responsible for packet routing and forwarding, packet inspection, QoS handling, and external PDU session for interconnecting Data Network (“DN”), in the 5G architecture. The AMF 143 is responsible for termination ofNAS signaling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The SMF 145 is responsible for session management (i.e., session establishment, modification, release), remote unit (i.e., UE) IP address allocation & management, DL data notification, and traffic steering configuration for UPF for proper traffic routing.
[0061] The PCF 146 is responsible for unified policy framework, providing policy rules to CP functions, access subscription information for policy decisions in UDR. The AUSF 147 acts as an authentication server.
[0062] The UDM is responsible for generation of Authentication and Key Agreement (“AKA”) credentials, user identification handling, access authorization, subscription management. The UDR is a repository of subscriber information and can be used to service a number of network functions. For example, the UDR may store subscription data, policy-related data, subscriber- related data that is permitted to be exposed to third party applications, and the like. In some embodiments, the UDM is co-located with the UDR, depicted as combined entity “UDM/UDR” 149.
[0063] In various embodiments, the mobile core network 140 may also include an Network Exposure Function (“NEF”) (which is responsible for making network data and resources easily accessible to customers and network partners, e.g., via one or more APIs), a Network Repository Function (“NRF”) (which provides NF service registration and discovery, enabling NFs to identify appropriate services in one another and communicate with each other over Application Programming Interfaces (“APIs”)), or other NFs defined for the 5GC. In certain embodiments, the mobile core network 140 may include an authentication, authorization, and accounting (“AAA”) server.
[0064] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, wherein each mobile data connection utilizes a specific network slice. Here, a “network slice” refers to a portion of the mobile core network 140 optimized for a certain traffic type or communication service. A network instance may be identified by a S-NSSAI, while a set of network slices for which the remote unit 105 is authorized to use is identified by NSSAI. In certain embodiments, the various network slices may include separate instances of network functions, such as the SMF and UPF 141. In some embodiments, the different network slices may share some common network functions, such as the AMF 143. The different network slices are not shown in Figure 1 for ease of illustration, but their support is assumed.
[0065] Although specific numbers and types of network functions are depicted in Figure 1, one of skill in the art will recognize that any number and type of network functions may be included in the mobile core network 140. Moreover, where the mobile core network 140 comprises an EPC, the depicted network functions may be replaced with appropriate EPC entities, such as an MME, S-GW, P-GW, HSS, and the like.
[0066] While Figure 1 depicts components of a 5G RAN and a 5G core network, the described embodiments for using a pseudonym for access authentication over non-3GPP access apply to other types of communication networks and RATs, including IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA 2000, Bluetooth, ZigBee, Sigfoxx, and the like. For example, in an 4G/LTE variant involving an EPC, the AMF 143 may be mapped to an MME, the SMF mapped to a control plane portion of a PGW and/or to an MME, the UPF 141 may be mapped to an SGW and a user plane portion of the PGW, the UDM/UDR 149 may be mapped to an HSS, etc.
[0067] As depicted, a remote unit 105 (e.g., a UE) may connect to the mobile core network (e.g., to a 5G mobile communication network) via two types of accesses: (1) via 3GPP access network 120 and (2) via a non-3GPP access network 130. The first type of access (e.g., 3GPP access network 120) uses a 3GPP-defmed type of wireless communication (e.g., NG-RAN) and the second type of access (e.g., non-3GPP access network 130) uses a non-3GPP -defined type of wireless communication (e.g., WLAN). The 5G-RAN 115 refers to any type of 5G access network that can provide access to the mobile core network 140, including the 3GPP access network 120 and the non-3GPP access network 130.
[0068] To solve the problem of detecting and alleviating paging collisions among multiple USIMs on the same device, described above, the present disclosure proposes solutions where, in one embodiment, the UE calculates the paging occasions and seeks assistance before initiating registration. In another embodiment, the UE sends a NAS registration request first and calculates the paging occasions and determines collisions from then on. In yet another embodiment, the network allows the UE to seek paging assistance knowing that the network supports providing such assistance. Further, a rule may be used that defines situations where a UE is allowed to declare a paging collision of at least two USIMs and thereby seek assistance, e.g., transmit a paging assistance required message.
[0069] Beneficially, the proposed solution, in one embodiment, conserves the UE battery life by eliminating, avoiding, or reducing the transition to a radio resource control (“RRC”) connection. Moreover, in another embodiment, the proposed solution avoids using the core network, which may potentially delay paging reception.
[0070] In one embodiment, a multi -USIM device may wish to receive paging for all associated USIMs, e.g., the USIMs that are operational simultaneously in the device. The time occasions where a multi-USIM device expects paging messages in idle mode are calculated in a specified way, e.g., as described in TS 38.304 for NR/5GS.
[0071] In such an embodiment, the UE may use discontinuous reception (“DRX”) in RRC IDFE and RRC INACTIVE state to reduce power consumption. In one embodiment, the UE monitors one paging occasion (“PO”) per DRX cycle. A PO may refer to a set of physical downlink control channel (“PDCCH”) monitoring occasions and may consist of multiple time slots (e.g., subframe or orthogonal frequency-division multiplexing (“OFDM”) symbols) where paging downlink control information (“DCI”) can be sent, e.g., according to TS 38.213. One paging frame ( PF ). in some embodiments, is one radio frame and may contain one or multiple PO(s) or a starting point of a PO.
[0072] In one embodiment, the PF and PO for paging are determined by the following formula:
[0073] System frame number (“SFN”) for the PF is determined by:
(SFN + PF offset) mod T = (T div N)*(UE_ID mod N) [0074] Index (i s), indicating the index of the PO is determined by: i_s = floor (UE_ID/N) mod Ns
[0075] The following parameters, in one embodiment, are used for the calculation of PF and i_s above:
T: DRX cycle of the UE (T is determined by the shortest of the UE specific DRX value(s), if configured by RRC and/or upper layers, and a default DRX value broadcast in system information. If UE specific DRX is not configured by RRC or by upper layers, the default value is applied).
N: number of total paging frames in T
Ns: number of paging occasions for a PF PF offset: offset used for PF determination
UE ID: 5G-S-TMSI mod 1024
[0076] In a dual USIM scenario, for example, the UE ID used for calculating PF, PO, and corresponding PDCCH monitoring occasions (collectively referred to as a paging opportunity herein) may be the same for two USIM devices because the UE_ID are the modulo values (e.g., mod 1024), or the operations ‘div’, ‘mod’, or 7’, which may result in that some of the paging opportunities (e.g., PF + PO) corresponding to the two USIMs overlap. The collision of paging opportunities, in some embodiments, also depends on whether the two USIM devices are camped on the same cell (or a different cell with same or different parameter values impacting the PF/PO calculations such as Ns, nAndPagingFrameOffset, nroftOCCH-MonitoringOccasionPerSSB- InPO, and the length of default DRX Cycle that are signaled in SIB1). If a UE has a single receiver (“Rx”) chain, it may not be able to receive paging for both USIMs when the paging opportunities completely or partially overlap/collide in time.
[0077] The proposed solutions described herein are focused, for simplicity, on UEs that support two USIMs. However, a more generalized scope is not limited to two USIMs only. The solution(s) may be extended to UEs that support a third USIM, a fourth USIM, and so on.
[0078] Consider a scenario where the first USIM in a UE that supports more than one USIM is already active and has a serving cell (e.g., camped in an RRC Idle or an RRC Connected state). When a second USIM is activated, e.g., the protocol stack of the second USIM is activated, the UE (e.g., USIM -2) may initiate a NAS registration procedure.
[0079] In one embodiment, the UE may already include some access stratum paging parameters (e.g., pcch-Config from a serving cell of another USIM(s) including its 10 bit 5G-S- TMSI mod 1024 value) in a NAS registration request message when at least one other USIM is already active. The AMF upon and/or if deciding on successful registration (e.g., a NAS registration accept message) allocates a 5G-TMSEGUTI and a UE specific DRX cycle that avoids paging collisions.
[0080] In one embodiment, the UE sends the NAS registration request first and calculates the paging occasions, e.g., as described in TS 38.304, based on the parameters broadcasted in SIB1 (e.g., specifically the pcch-Config parameter), e.g., as defined in TS 38.331, only after receiving a NAS registration accept message while considering a UE specific DRX cycle, if signaled in the registration accept message. If a paging collision is foreseen between the calculated paging opportunities of both USIMs, the UE may request the network to modify the paging occasions for one of the USIMs, e.g., sending a paging assistance required message to the network.
[0081] In one implementation of this embodiment, the UE sends the paging assistance request to the network that corresponds to the second USIM, e.g., the USIM that is activated (registered) after the first USIM is activated. In another implementation of this embodiment, the UE sends the paging assistance request to the network that corresponds to the first USIM, e.g., the USIM that is activated (registered) before the second USIM. An AMF in the network is referred in most cases for an RRC Idle UE, but the same methods described herein may apply to a UE seeking assistance from a RAN node (e.g., a gNB) if it initiates an RRC connection establishment to seek such assistance.
[0082] Paging assistance, in one embodiment, is an adjustment made for a specific UE that may not be able to monitor regular paging opportunities, enabling it to monitor different sets of paging opportunities, and send the paging on the sets of different paging opportunities. The “adjustment” is made to one or more of the paging parameters, configuration, or UE ID described herein.
[0083] The embodiments described above, in one embodiment, assume that the UE seeks blindly the paging assistance, e.g., without knowing if the network can provide paging assistance. Further, in certain embodiments, there may be cases where the UE is registered for both USIMs, but paging collisions start when the paging configuration (e.g., pcch-Config) from a serving cell of one of the USIM changes, e.g., one or more of the parameters Ns, nAndPagingFrameOffset, nrofPDCCFl-MomtoringOccasionP erSSB-lnPO , and/or the length of default DRX Cycle is/are modified, which may lead to paging collisions. In this case as well, the UE may realize at some point that it needs assistance to avoid paging collisions corresponding to the two USIMs.
[0084] In one embodiment, the UE is allowed to seek paging assistance knowing that the network supports providing such assistance. In this embodiment, the broadcast information from a serving cell indicates that the network provides “assistance for paging collision alleviation.” This may be done in several ways. In a first embodiment, the network may broadcast a one bit flag indicating whether the network provides “assistance for paging collision alleviation.” In a second embodiment, it may be implied based on broadcasting any required paging assistance parameter. An example of a required paging assistance parameter may be an offset value for changing a starting position of a first paging occasion in the SFN cycle, which may impact the firstPDCCH- MonitoringOccasionOfl’O parameter.
[0085] In one embodiment, if the serving cell indicates that it provides “assistance for paging collision alleviation,” the UE may send a “paging assistance required” message to the network (e.g., the AMF). If only one of the networks corresponding to the two USIMs provides, supports, or otherwise indicates that it supports “assistance for paging collision alleviation,” the UE sends a “paging assistance required” message to that corresponding network. If none of the networks provides, supports, or otherwise indicates that it supports “assistance for paging collision alleviation,” e.g., the corresponding information is missing or the one bit flag indicating whether the network supports “assistance for paging collision alleviation” is set to false, a UE may reselect another cell that provides “assistance for paging collision alleviation” for one of the USIMs.
[0086] In one embodiment, the network may provide more information than just an indication of whether the network supports or does not support “assistance for paging collision alleviation,” e.g., if there are more than one solution/technique that can be used for paging collision alleviation, the network may inform the UE using broadcast or dedicated RRC/NAS signaling as to which solution/technique is used for paging collision alleviation by the serving network. Upon sending the “paging assistance required” message, the UE may prepare to apply the solution/technique for paging collision alleviation that the servicing network supports. The network (e.g., the AMF in the case of CN based paging or the RAN node in the case of RAN based paging) may resend the paging message in the new paging opportunities upon receiving a “paging assistance required” message for a UE that was being paged recently but had not responded to the page . To enable such behavior, a network may store the paging after completing its paging attempts if the UE has still not responded to the page.
[0087] Regarding what a paging collision is and what the corresponding UE behavior is in response to declaring a collision, in one embodiment, the UE behavior and possible network control is outlined so that UEs each have the same behavior as far as paging collision detection is concerned. In the absence of a uniform UE behavior, some UEs will declare, detect, or determine a paging collision and seek assistance when all paging opportunities of both of the USIMs collide, as shown in 2A, and some other UEs may seek assistance when less than all of the paging opportunities of both of the USIMs collide, as shown in Error! Reference source not found.B.
[0088] In one embodiment, a rule may be established, defined, used or the like that determines when a UE is allowed to declare a paging collision of at least two USIMs, and thereby seek assistance (e.g., transmit a “paging assistance required” message). As one example of a rule, the UE may be allowed to seek assistance if a single paging collision in each time period such as a DRX cycle is foreseen or detected. This rule may be useful if the network does not re-transmit a paging message in a particular serving cell.
[0089] If the network, in another embodiment, repeats paging in the same cell, another rule could be defined or established that states that upon collision of at least contiguous (or otherwise) ‘x’ paging opportunities (e.g., in a DRX cycle, in a SFN cycle, in a time period, or the like) in each time period such as a DRX cycle, the UE may be allowed to seek assistance. The rule may be expressed in terms of a percentage of colliding POs (e.g., in a DRX cycle or in the entire SFN cycle) such as 50% of paging opportunities results in collisions, 100% of paging opportunities result in collisions, and/or the like. The rule may be hard-coded in a specification or may be configurable by the network using RRC signaling, e.g., by broadcast signaling in SIB. The paging collision may be noted as an overlap, either partial or full, in time and/or also in the paging search space.
[0090] In one embodiment, the number of “paging assistance required” messages that are sent from the UE may be restricted or limited by way of a timer such that the UE is not allowed to send another “paging assistance required” until the timer has expired. The timer may be started once the UE has transmitted a “paging assistance required” message. In further embodiments, the number of “paging assistance required” messages that are sent from the UE may be restricted or limited by way of a constraint that allows the UE to repeat “paging assistance required” at least after ‘x’ milliseconds, seconds, or the like. However, in certain embodiments, if information has changed, e.g., detection of new paging collisions, a “paging assistance required” message may be sent immediately. [0091] Figure 3 depicts a procedure 300 for paging management for multiple universal subscriber identity modules. As shown in Figure 3, in certain embodiments, a network 304 indicates (see messaging 306) to a UE 302 its support or capability, e.g., using one-bit broadcast signaling for “assistance for paging collision alleviation.” In one embodiment, a UE 302, upon determining a paging collision, evaluates (see block 308) a rule to check if it is allowed to send a “paging assistance required” message to the network 304. In some embodiments, upon a positive evaluation, the UE 302 transmits (see messaging 310) the “paging assistance required” message to the network 304. The network 304, in various embodiments, provides (see messaging 312) paging assistance that indicates a paging solution (e.g., modified paging opportunities present at an offset to the regular paging opportunities) to the UE 302. The network 304 transmits, and the UE 302 monitors, paging at the modified paging opportunities.
[0092] A further embodiment describes the UE protocol implementation and the behavior of access stratus (“AS”) and non-access stratum (“NAS”) in the event of paging collisions. In one embodiment, the NAS, upon activating the second protocol stack corresponding to the second USIM, requests the AS to perform cell search and look for suitable PLMN(s). In further embodiments, upon PLMN and cell selection corresponding to the second USIM, and optionally after receiving a registration accept message, the NAS requests both the AS protocols (of the two corresponding USIMs) to calculate the paging opportunities from the broadcast information of the serving cell corresponding to each of the USIMs. The UE specific DRX cycle, if provided by upper layers, may also be considered. [0093] In certain embodiments, both the AS protocols that correspond to the two USIMs calculate their corresponding paging opportunities and send the same to the NAS. In further embodiments, upon receiving the paging opportunities from both the AS protocols, the NAS determines if there is a paging collision in some or all of the paging opportunities of the involved USIMs. In such an embodiment, the UE accounts for the DL time difference across the concerned serving cells.
[0094] For example, if the DL time difference between subframe#0 - SFN#0 of the two cells is delta_T, the UE needs to advance the SFN cycle timeline for one of the serving cells by delta_T (or alternatively, the UE needs to delay the SFN cycle timeline for the other serving cell by delta_T). If this is not performed and the two paging opportunities are indicated to the NAS, then the NAS will assume that PF#x and PO#y of two cells are colliding whereas they may not in reality if the delta_T is longer than a slot length.
[0095] As shown in Figures 4A and 4B, the timelines of the two serving cells are aligned by considering the delta_T, and the UE checks for collisions of paging opportunities between the two cells. In Figure 4B, the frame boundary of SFN#0 of the two cells starts at the same point in time, e.g., using an absolute time reference like global navigation satellite system (“GNSS”). The UE may determine actual paging collision or overlap of the paging opportunities.
[0096] In a further implementation, the UE compares the collisions between the paging opportunities while also considering the retuning time between the frequencies. In one embodiment, the NAS, upon determining a paging collision, reports the paging collision issue to the network and seeks assistance to avoid the same. In such an embodiment, the NAS is generally meant as some common, combined, or upper NAS protocol, e.g., sitting above the individual NAS protocol that has overview of the two USIMs and the two protocol stacks.
[0097] In one embodiment regarding the UE protocol implementation and the behavior of AS and NAS, which is different from the implementation described above in that the collision detection here happens in the AS layer and not in the NAS, the UE supports more than one USIM registration and receives the NAS registration accept message or NAS UE configuration update message (or a corresponding attach accept message or TAU accept message in EPS) including 1) a new GUTI and/or 2) a DRX timer for paging. [0098] In one embodiment, the NAS layer requests the AS layer to determine whether a paging occasion collision occurs considering the parameters for the USIM registration, e.g., GUTI and DRX timer for paging. The NAS layer, in some embodiments, waits with the “acknowledgement for the registration accept” message or “UE configuration update” message until feedback from the AS layer. When USIM1 registers and goes to idle, in certain embodiments, NAS# 1 protocol stack requests the AS to monitor the POs according to the parameters sent from
NAS#1. When USIM2 registers, in further embodiments, NAS#2 protocol stack requests the AS to monitor the POs for NAS#2. In some embodiments, the AS layer exchanges with two NAS instances and the AS stores, for each NAS instance, idle state parameters, e.g., S-TMSI, DRX timer, allowed TA list, frequency band preference, and/or the like. [0099] In one embodiment, the AS layer performs a check to determine whether paging occasion collision occurs. This may be done by comparing the paging opportunities of both USIMs using the same time reference and checking if the paging opportunities of both USIMs overlap, either partially or fully/completely. [00100] In one embodiment, if the AS layer determines that paging occasion collision occurs, the AS sends an indication to the NAS regarding the collision. In further embodiments, the NAS layer sends a registration complete message or a UE configuration update complete message (or corresponding NAS EPS messages), including an indication to the AMF (or MME) that paging collision is detected.
[00101] In one embodiment, the UE selects a USIM for which the UE seeks paging assistance from the network in the event of paging collisions between multiple USIMs. In such an embodiment, various parameters or criteria may be used to determine which USIM is selected, including, but not limited to, a preference for new radio (“NR”) USIM in case of inter-radio access technologies (“RAT”) over other RAT USIMs; in response to not receiving a response from a mobile wireless communication network corresponding to one of the USIMs to the request for assistance with alleviating the determined paging collision, selecting a mobile wireless communication network for a next USIM to request assistance with alleviating the determined paging collision; a preference for a solution for alleviating the determined paging collision provided by a mobile wireless communication network corresponding to one of the USIMs over a different solution provided by a mobile wireless communication network corresponding to a different USIM; a preference for using an equivalent home public land mobile network (“EHPLMN”) USIM over a visited PLMN (“VPLMN”) USIM; a preference for a USIM for a mobile wireless communication network that has a higher radio quality than a different mobile wireless communication network corresponding to a different USIM; and/or the like.
[00102] Regarding proposed solutions for alleviating paging collisions, in a UE-based approach, in one embodiment, a UE after performing a registration procedure checks corresponding to the received GUTE5G-S-TMSI, if the paging opportunities (e.g., based on the pcch-Config of the serving cell) would collide with that of the other USIM(s). If so, in one embodiment, the UE performs deregistration and then re-registers and receives another GUTE5G- S-TMSI. In certain embodiments, this procedure is repeated until no paging collision is foreseen.
[00103] In one embodiment, in an AS, RAN-based solution, a UE, upon indicating paging collisions to the network and seeking assistance by sending a “paging assistance required” message to the network, e.g., AMF, as shown in 5A, starts monitoring POs that are calculated with a fixed offset from the “regular” calculated paging opportunities, e.g., as defined in TS 38.304. In order to send the said message, in one embodiment, upon determining the paging collisions, the RRC Idle UE first initiates a transition to RRC Connected, using optionally a new EstablishmentCause, a new logical channel identifier (“LCID”), or the like, to allow the gNB to understand the reason for initiating an RRC Connection establishment. As one implementation of this embodiment, the said “offset” may be fixed in a specification and may be quantified in a number of time slots, subframes, paging frames, a firstPDCCH-MonitoringOccasionOfiO parameter (e.g., as defined in 38331-g00), in the UE_ID, and/or the like. For example, if the offset is two frames, the UE, after calculating the PF+PO, uses the PF new as PF+2, where the PF is calculated as (SFN + PF offset) mod T = (T div N)*(UE_ID mod N).
[00104] As another example, if the offset is two for UE_ID, the UE may calculate the PF+PO corresponding to a UE ID New, where UE ID New is UE ID + 2 and where the UE ID is calculated as UE ID: 5G-S-TMSI mod 1024.
[00105] In one embodiment, the offset can be negative. Instead of calculating the new values of the parameters (e.g., time slots, subframes, frames, UE_ID, and/or the like), some fixed values for one or more of these parameters may be used as well. The offset, or the fixed value, can be specified or (pre)configured using RRC signaling.
[00106] As another embodiment, after seeking assistance from the network (e.g., in response to transmitting a “paging assistance required” message as shown in Figure 5A) and receiving a confirmation, the UE and the network may use an alternative value for one or more of the parameters Ns, nAndPagingFrameOffset, nrofiOCCH-MonitoringOccasionPerSSB-InPO, and the length of default DRX Cycle as signaled in SIBL The alternative values may be an offset value from the broadcasted values, or a fixed value. The offset may be negative. The offset, or the fixed value, may be specified or (pre)configured using RRC signaling.
[00107] The “paging assistance required” message, in one embodiment, is an empty message that implicitly indicates that the UE needs assistance for avoiding paging collisions. Alternatively, the “paging assistance required” message may contain information that either allows the gNB to understand where the paging opportunities from the other USIM(s) lie, and/or, directly indicates which parameter (value) can be modified/ reconfigured. The parameter may be one or more of the parameters discussed above.
[00108] In one embodiment, in a NAS, CN-based solution, a lightweight NAS procedure is used instead of a NAS registration or service request procedure. Here, in one embodiment, the UE 502 sends a NAS message (e.g., see messaging 508 - a “paging assistance required” message as shown in Figure 5 A) to an AMF 504 that indicates that paging collisions are foreseen, once the UE 502 is registered to the network (see block 506). The AMF 504 may apply a solution or indicate to the NG-RAN to apply an AS solution when the UE needs to be paged. If the solution is fixed (e.g., in specification), in one embodiment, the UE 502 is informed back from the AMF 504 in a NAS paging assistance indicating whether an AS-based or a NAS-based solution is to be applied in a confirmation message (see messaging 510 in Figure 5A). [00109] If the solution is not fixed (since more than one solution can be applied), the UE 502 is informed back in a NAS “paging assistance confirm” message (see messaging 512) as shown in Figure 5B, signaling which solution shall be applied. Such an embodiment (e.g., the lightweight procedure) can be applied irrespective of RRC state, can be applied multiple times to seek assistance, can indicate that no more assistance is required, e.g., the UE 502 may use the “regular PF+POs” to seek new assistance when the previous assistance/technique/solution is not effective anymore due to any reason, e.g., such as reconfiguration of pcch-Config, mobility, and/or the like of any of the involved USIMs. Once a solution is provided, in one embodiment, it is assumed to be available in the entire registration area (e.g., TA list) of the UE 502. [00110] Figure 6 depicts a user equipment apparatus 600 that may be used for paging management for multiple universal subscriber identity modules, according to embodiments of the disclosure. In various embodiments, the user equipment apparatus 600 is used to implement one or more of the solutions described above. The user equipment apparatus 600 may be one embodiment of the remote unit 105 and/or the UE 205, described above. Furthermore, the user equipment apparatus 600 may include a processor 605, a memory 610, an input device 615, an output device 620, and a transceiver 625.
[00111] In some embodiments, the input device 615 and the output device 620 are combined into a single device, such as a touchscreen. In certain embodiments, the user equipment apparatus 600 may not include any input device 615 and/or output device 620. In various embodiments, the user equipment apparatus 600 may include one or more of: the processor 605, the memory 610, and the transceiver 625, and may not include the input device 615 and/or the output device 620.
[00112] As depicted, the transceiver 625 includes at least one transmitter 630 and at least one receiver 635. In some embodiments, the transceiver 625 communicates with one or more cells (or wireless coverage areas) supported by one or more base units 121. In various embodiments, the transceiver 625 is operable on unlicensed spectrum. Moreover, the transceiver 625 may include multiple UE panel supporting one or more beams. Additionally, the transceiver 625 may support at least one network interface 640 and/or application interface 645. The application interface(s) 645 may support one or more APIs. The network interface(s) 640 may support 3GPP reference points, such as Uu, Nl, PC5, etc. Other network interfaces 640 may be supported, as understood by one of ordinary skill in the art.
[00113] The processor 605, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 605 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller hi some embodiments, the processor 605 executes instructions stored in the memory 610 to perform the methods and routines described herein. The processor 605 is communicatively coupled to the memory 610, the input device 615, the output device 620, and the transceiver 625. In certain embodiments, the processor 605 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.
[00114] In various embodiments, the processor 605 controls the user equipment apparatus 600 to implement the above described UE behaviors. In one embodiment, the transceiver 625 receives, from a mobile wireless communication network associated with at least one of the USIMs, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision, and the processor 605 that determines a paging collision for paging occasions of at least a subset of the plurality of USIMs. In certain embodiments, the transceiver 625 sends a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs .
[00115] In one embodiment, the transceiver 625 further receives a same paging message according to the indicated solution in response to the request for assistance with alleviating the determined paging collision that was previously supposed to be received as part of the paging collision.
[00116] In various embodiments, the processor 605 determines the paging collision based on a rule that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network. In one embodiment, the processor 605 determines the paging collision as at least a partial overlap in one of time and paging search space of at least one paging occasion of the paging occasions of the at least a subset of the plurality of USIMs. In some embodiments, the transceiver 625 sends a subsequent request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs in response to expiration of timer that is initiated in response to the initial request for assistance with alleviating the determined paging collision. In one embodiment, the processor 605 further selects a USIM of the at least a subset of USIMs for seeking assistance for alleviating paging collisions. [00117] In one embodiment, the processor 605 performs a registration procedure with a mobile wireless communication network, and the transceiver 625 receives an identifier from the mobile wireless communication network and checks for paging collisions between paging opportunities for the plurality of USIMs based on the received identifier. In one embodiment, in response to determining paging collisions between the paging opportunities for the plurality of USIMs, the processor 605 continuously performs deregistration from the mobile wireless communication network and re-registration with the mobile wireless communication network until no paging collisions between the paging opportunities for the plurality of USIMs are expected.
[00118] In one embodiment, the transceiver 625, in response to notifying a mobile wireless communication network of paging collisions between paging opportunities for the plurality of USIMs, receives an offset value for monitoring paging opportunities for at least one of the plurality of USIMs associated with the paging collisions, and the processor 605 monitors paging opportunities for the at least one of the plurality of USIMs associated with the paging collisions using the received offset. [00119] In one embodiment, the processor 605 determines the paging collisions between paging opportunities for the plurality of USIMs and in response to the determined paging collisions, the transceiver 625 initiates a radio resource connection (“RRC”) with the mobile wireless communication network.
[00120] The memory 610, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 610 includes volatile computer storage media. For example, the memory 610 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 610 includes non-volatile computer storage media. For example, the memory 610 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 610 includes both volatile and non-volatile computer storage media.
[00121] In some embodiments, the memory 610 stores data related to paging management for multiple universal subscriber identity modules. For example, the memory 610 may store various parameters, panel/beam configurations, resource assignments, policies, and the like as described above. In certain embodiments, the memory 610 also stores program code and related data, such as an operating system or other controller algorithms operating on the user equipment apparatus 600.
[00122] The input device 615, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 615 may be integrated with the output device 620, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 615 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 615 includes two or more different devices, such as akeyboard and atouch panel.
[00123] The output device 620, in one embodiment, is designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 620 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 620 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 620 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 600, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 620 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
[00124] In certain embodiments, the output device 620 includes one or more speakers for producing sound. For example, the output device 620 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 620 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all, or portions of the output device 620 may be integrated with the input device 615. For example, the input device 615 and output device 620 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 620 may be located near the input device 615.
[00125] The transceiver 625 communicates with one or more network functions of a mobile communication network via one or more access networks. The transceiver 625 operates under the control of the processor 605 to transmit messages, data, and other signals and also to receive messages, data, and other signals. For example, the processor 605 may selectively activate the transceiver 625 (or portions thereof) at particular times in order to send and receive messages.
[00126] The transceiver 625 includes at least transmitter 630 and at least one receiver 635. One or more transmitters 630 may be used to provide UL communication signals to a base unit 121, such as the UL transmissions described herein. Similarly, one or more receivers 635 may be used to receive DL communication signals from the base unit 121, as described herein. Although only one transmitter 630 and one receiver 635 are illustrated, the user equipment apparatus 600 may have any suitable number of transmitters 630 and receivers 635. Further, the transmitter(s) 630 and the receiver(s) 635 may be any suitable type of transmitters and receivers. In one embodiment, the transceiver 625 includes a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.
[00127] In certain embodiments, the first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components. For example, certain transceivers 625, transmitters 630, and receivers 635 may be implemented as physically separate components that access a shared hardware resource and/or software resource, such as for example, the network interface 640.
[00128] In various embodiments, one or more transmitters 630 and/or one or more receivers 635 may be implemented and/or integrated into a single hardware component, such as a multi -transceiver chip, a system -on-a-chip, an ASIC, or other type of hardware component. In certain embodiments, one or more transmitters 630 and/or one or more receivers 635 may be implemented and/or integrated into a multi -chip module. In some embodiments, other components such as the network interface 640 or other hardware components/circuits may be integrated with any number of transmitters 630 and/or receivers 635 into a single chip. In such embodiment, the transmitters 630 and receivers 635 may be logically configured as a transceiver 625 that uses one more common control signals or as modular transmitters 630 and receivers 635 implemented in the same hardware chip or in a multi -chip module.
[00129] Figure 7 depicts a network apparatus 700 that may be used for paging management for multiple universal subscriber identity modules, according to embodiments of the disclosure. In one embodiment, the network apparatus 700 may be one implementation of a RAN node, such as the base unit 121, the RAN node 210, or gNB, described above. Furthermore, the base network apparatus 700 may include a processor 705, a memory 710, an input device 715, an output device 720, and a transceiver 725.
[00130] In some embodiments, the input device 715 and the output device 720 are combined into a single device, such as a touchscreen. In certain embodiments, the network apparatus 700 may not include any input device 715 and/or output device 720. In various embodiments, the network apparatus 700 may include one or more of: the processor 705, the memory 710, and the transceiver 725, and may not include the input device 715 and/or the output device 720. [00131] As depicted, the transceiver 725 includes at least one transmitter 730 and at least one receiver 735. Here, the transceiver 725 communicates with one or more remote units 105. Additionally, the transceiver 725 may support at least one network interface 740 and/or application interface 745. The application interface(s) 745 may support one or more APIs. The network interface(s) 740 may support 3GPP reference points, such as Uu, Nl, N2 and N3. Other network interfaces 740 may be supported, as understood by one of ordinary skill in the art.
[00132] The processor 705, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 705 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller. In some embodiments, the processor 705 executes instructions stored in the memory 710 to perform the methods and routines described herein. The processor 705 is communicatively coupled to the memory 710, the input device 715, the output device 720, and the transceiver 725. In certain embodiments, the processor 805 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio function.
[00133] In various embodiments, the network apparatus 700 is a RAN node (e.g., gNB) that provides paging assistance for alleviating paging collisions, as described herein. In such embodiments, the transceiver (725) sends, to a user equipment (“UE”) device comprising a plurality of universal subscriber identity modules (“USIMs”), an indication that a mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision, and receives, from the UE, a request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs. [00134] In one embodiment, the processor 705 that determines a solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs and the transceiver 725 sends the determined solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs to the UE.
[00135] In one embodiment, transceiver 725 resends a paging message according to the determined solution in response to the received request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs. In certain embodiments, the processor 705 stores one or more paging messages that are sent to the UE for a predetermined period of time, the stored paging messages accessed for resending paging messages that do not receive a response. In one embodiment, the processor 705 configures at least one rule for the UE that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network.
[00136] In one embodiment, the transceiver 725 receives an indication from a user equipment (“UE”) device that supports a plurality of universal subscriber identity modules (“USIMs”) of paging collisions between paging opportunities of the plurality of USIMs and the processor 705 determines an offset value for modifying at least one parameter that is used in determining paging opportunities for at least one of the plurality of USIMs that is associated with the paging collisions. In certain embodiments, the transceiver 725 sends the determined offset to the UE for modifying the determination of the paging opportunities for the at least one of the plurality of USIMs using the determined offset.
[00137] The memory 710, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 710 includes volatile computer storage media. For example, the memory 710 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 710 includes non-volatile computer storage media. For example, the memory 710 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 710 includes both volatile and non-volatile computer storage media.
[00138] In some embodiments, the memory 710 stores data related to paging management for multiple universal subscriber identity modules. For example, the memory 710 may store parameters, configurations, resource assignments, policies, and the like, as described above. In certain embodiments, the memory 710 also stores program code and related data, such as an operating system or other controller algorithms operating on the network apparatus 700.
[00139] The input device 715, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 715 may be integrated with the output device 720, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 715 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 715 includes two or more different devices, such as akeyboard and atouch panel.
[00140] The output device 720, in one embodiment, is designed to output visual, audible, and/or haptic signals. In some embodiments, the output device 720 includes an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 720 may include, but is not limited to, an FCD display, an FED display, an OFED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the output device 720 may include a wearable display separate from, but communicatively coupled to, the rest of the network apparatus 700, such as a smart watch, smart glasses, a heads-up display, or the like. Further, the output device 720 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
[00141] In certain embodiments, the output device 720 includes one or more speakers for producing sound. For example, the output device 720 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 720 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all, or portions of the output device 720 may be integrated with the input device 715. For example, the input device 715 and output device 720 may form a touchscreen or similar touch-sensitive display. In other embodiments, the output device 720 may be located near the input device 715.
[00142] The transceiver 725 includes at least transmitter 730 and at least one receiver 735. One or more transmitters 730 may be used to communicate with the UE, as described herein. Similarly, one or more receivers 735 may be used to communicate with network functions in the NPN, PLMN and/or RAN, as described herein. Although only one transmitter 730 and one receiver 735 are illustrated, the network apparatus 700 may have any suitable number of transmitters 730 and receivers 735. Further, the transmitter(s) 730 and the receiver(s) 735 may be any suitable type of transmitters and receivers.
[00143] Figure 8 is a flowchart diagram of a method 800 for paging management for multiple universal subscriber identity modules. The method 800 may be performed by a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 600. In some embodiments, the method 700 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
[00144] In one embodiment, the method 800 includes receiving 805, from a mobile wireless communication network associated with at least one of a plurality of universal subscriber identity modules (“USIMs”) of a user equipment (“UE”) device, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision. In further embodiments, the method 800 includes determining 810 a paging collision for paging occasions of at least a subset of the plurality of USIMs. In some embodiments, the method 800 includes sending 815 a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality ofUSIMs. The method 800 ends.
[00145] Figure 9 is a flowchart diagram of a method 900 for paging management for multiple universal subscriber identity modules. The method 900 may be performed by a network device as described herein, for example, the network equipment apparatus 700. In some embodiments, the method 900 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
[00146] In one embodiment, the method 900 includes sending 905, to a user equipment (“UE”) device comprising a plurality of universal subscriber identity modules (“USIMs”), an indication that a mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs. In certain embodiments, the method 900 includes receiving 910, from the UE, a request for assistance with alleviating the determined paging collision of the at least a subset of the plurality ofUSIMs and an indication of a solution to be used for alleviating the determined paging collision.
[00147] In one embodiment, the method 900 includes determining 915 a solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs. In further embodiments, the method 900 includes sending 920 the determined solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs to the UE. The method 900 ends.
[00148] Figure 10 is a flowchart diagram of a method 1000 for paging management for multiple universal subscriber identity modules. The method 1000 may be performed by a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700. In some embodiments, the method 1000 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
[00149] In one embodiment, the method 1000 includes performing 1005 a registration procedure for a user equipment (”UE”) with a mobile wireless communication network, the UE comprising a plurality of universal subscriber identity modules (“USIMs”). In further embodiments, the method 1000 includes receiving 1010 an identifier from the mobile wireless communication network.
[00150] In one embodiment, the method 1000 includes checking 1015 for paging collisions between paging opportunities for the plurality ofUSIMs based on the received identifier. In certain embodiments, the method 1000 includes, in response to determining paging collisions between the paging opportunities for the plurality of USIMs, continuously performing 1020 deregistration from the mobile wireless communication network and re-registration with the mobile wireless communication network until no paging collisions between the paging opportunities for the plurality of USIMs are expected. The method 1020 ends. [00151] Figure 11 is a flowchart diagram of a method 1100 for paging management for multiple universal subscriber identity modules. The method 1100 may be performed by a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700. In some embodiments, the method 1100 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
[00152] The method 1100 includes, in response to notifying a mobile wireless communication network of paging collisions between paging opportunities of a plurality of universal subscriber identity modules (“USIMs”) of a user equipment (“UE”) device, receiving 1105 an offset value for monitoring paging opportunities for at least one of the plurality of USIMs associated with the paging collisions. In certain embodiments, the method 1100 includes monitoring 1110 paging opportunities forthe at least one ofthe plurality of USIMs associated with the paging collisions using the received offset. The method 1100 ends.
[00153] Figure 12 is a flowchart diagram of a method 1200 for paging management for multiple universal subscriber identity modules. The method 1200 may be performed by a network device as described herein, for example, the network equipment apparatus 700. In some embodiments, the method 1200 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
[00154] In one embodiment, the method 1200 includes receiving 1205 an indication from a user equipment (“UE”) device that supports a plurality of universal subscriber identity modules (“USIMs”) of paging collisions between paging opportunities of the plurality of USIMs. In certain embodiments, the method 1200 includes determining 1210 an offset value for modifying at least one parameter that is used in determining paging opportunities for at least one of the plurality of USIMs that is associated with the paging collisions. In some embodiments, the method 1200 includes sending 1215 the determined offset to the UE for modifying the determination of the paging opportunities for the at least one of the plurality of USIMs using the determined offset. The method 1200 ends.
[00155] A first apparatus is disclosed for paging management for multiple universal subscriber identity modules. The first apparatus may be embodied as a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700. In some embodiments, the first apparatus includes a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
[00156] In one embodiment, the first apparatus includes a plurality of universal subscriber identity modules (“USIMs”), a transceiver that receives, from a mobile wireless communication network associated with at least one of the USIMs, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision, and a processor that determines a paging collision for paging occasions of at least a subset of the plurality of USIMs. In certain embodiments, the transceiver sends a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs.
[00157] In one embodiment, the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises a one bit flag. In some embodiments, the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises an offset value for changing a starting position of a first paging occasion.
[00158] In one embodiment, the transceiver further receives a same paging message according to the indicated solution in response to the request for assistance with alleviating the determined paging collision that was previously supposed to be received as part of the paging collision.
[00159] In various embodiments, the processor determines the paging collision based on a rule that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network. In one embodiment, the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining at least one paging collision among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
[00160] In one embodiment, the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining paging collisions among all received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs. In some embodiments, the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining a paging collision for a threshold number of contiguous paging opportunities among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
[00161] In one embodiment, the processor determines the paging collision as at least a partial overlap in one of time and paging search space of at least one paging occasion of the paging occasions of the at least a subset of the plurality of USIMs. In some embodiments, the transceiver sends a subsequent request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs in response to expiration of timer that is initiated in response to the initial request for assistance with alleviating the determined paging collision.
[00162] In one embodiment, the processor further selects a USIM of the at least a subset of USIMs for seeking assistance for alleviating paging collisions based at least on one of the following criteria: a preference for new radio (“NR”) USIM in case of inter-radio access technologies (“RAT”) over other RAT USIMs; in response to not receiving a response from a mobile wireless communication network corresponding to one of the USIMs to the request for assistance with alleviating the determined paging collision, selecting a mobile wireless communication network for a next USIM to request assistance with alleviating the determined paging collision; a preference for a solution for alleviating the determined paging collision provided by a mobile wireless communication network corresponding to one of the USIMs over a different solution provided by a mobile wireless communication network corresponding to a different USIM; a preference for using an equivalent home public land mobile network (“EHPUMN”) USIM over a visited PUMN (“VPUMN”) USIM; and a preference for a USIM for a mobile wireless communication network that has a higher radio quality than a different mobile wireless communication network corresponding to a different USIM.
[00163] A first method is disclosed for paging management for multiple universal subscriber identity modules. The first method may be performed by a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700. In some embodiments, the first method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
[00164] In one embodiment, the first method includes receiving, from a mobile wireless communication network associated with at least one of a plurality of universal subscriber identity modules (“USIMs”) of a user equipment (“UE”) device, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIM and an indication of a solution to be used for alleviating the determined paging collision, determining a paging collision for paging occasions of at least a subset of the plurality of USIMs, and sending a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs. [00165] In one embodiment, the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises a one bit flag. In some embodiments, the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises an offset value for changing a starting position of a first paging occasion. [00166] In certain embodiments, the method includes receiving an indication of a solution to be used for alleviating the determined paging collision. In one embodiment, the method includes receiving a same paging message according to the indicated solution in response to the request for assistance with alleviating the determined paging collision that was previously supposed to be received as part of the paging collision. [00167] In various embodiments, the method includes determining the paging collision based on a rule that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network. In one embodiment, the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining at least one paging collision among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
[00168] In one embodiment, the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining paging collisions among all received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs. In some embodiments, the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining a paging collision for a threshold number of contiguous paging opportunities among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs. [00169] In one embodiment, the method includes determining the paging collision as at least a partial overlap in one of time and paging search space of at least one paging occasion of the paging occasions of the at least a subset of the plurality of USIMs. In some embodiments, the method includes sending a subsequent request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs in response to expiration of timer that is initiated in response to the initial request for assistance with alleviating the determined paging collision.
[00170] In one embodiment, the method includes selecting aUSIM of the at least a subset of USIMs for seeking assistance for alleviating paging collisions based at least on one of the following criteria: a preference for new radio (“NR”) USIM in case of inter-radio access technologies (“RAT”) over other RAT USIMs; in response to not receiving a response from a mobile wireless communication network corresponding to one of the USIMs to the request for assistance with alleviating the determined paging collision, selecting a mobile wireless communication network for a next USIM to request assistance with alleviating the determined paging collision; a preference for a solution for alleviating the determined paging collision provided by a mobile wireless communication network corresponding to one of the USIMs over a different solution provided by a mobile wireless communication network corresponding to a different USIM; a preference for using an equivalent home public land mobile network (“EHPUMN”) USIM over a visited PUMN (“VPUMN”) USIM; and a preference for a USIM for a mobile wireless communication network that has a higher radio quality than a different mobile wireless communication network corresponding to a different USIM.
[00171] A second apparatus is disclosed for paging management for multiple universal subscriber identity modules. The second apparatus may be embodied as a network device as described herein, for example, the network equipment apparatus 700. In some embodiments, the second apparatus may be embodied by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
[00172] In one embodiment, the second apparatus includes a transceiver that sends, to a user equipment (“UE”) device comprising a plurality of universal subscriber identity modules (“USIMs”), an indication that a mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision and receives, from the UE, a request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs. In one embodiment, the second apparatus includes a processor that determines a solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs. In some embodiments, the transceiver sends the determined solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs to the UE.
[00173] In one embodiment, the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises a one bit flag. In some embodiments, the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises an offset value for changing a starting position of a first paging occasion.
[00174] In one embodiment, the transceiver resends a paging message according to the determined solution in response to the received request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs. In some embodiments, the processor further stores one or more paging messages that are sent to the UE for a predetermined period of time, the stored paging messages accessed for resending paging messages that do not receive a response. [00175] In one embodiment, the processor further configures at least one rule for the UE that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network. In certain embodiments, the rule indicates that the UE sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining at least one paging collision among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
[00176] In one embodiment, the rule indicates that the UE sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining paging collisions among all received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs. In certain embodiments, the rule indicates that the UE sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining a paging collision for a threshold number of contiguous paging opportunities among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs. [00177] A second method is disclosed for paging management for multiple universal subscriber identity modules. The second method may be performed by a network device as described herein, for example, the network equipment apparatus 700. In some embodiments, the second method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
[00178] In one embodiment, the second method includes sending, to a user equipment (“UE”) device comprising a plurality of universal subscriber identity modules (“USIMs”), an indication that a mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision, receiving, from the UE, a request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs, determining a solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs, and sending the determined solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs to the UE.
[00179] In one embodiment, the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises a one bit flag. In certain embodiments, the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises an offset value for changing a starting position of a first paging occasion.
[00180] In one embodiment, the method includes resending a paging message according to the determined solution in response to the received request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs. In certain embodiments, the method includes storing one or more paging messages that are sent to the UE for a predetermined period of time, the stored paging messages accessed for resending paging messages that do not receive a response.
[00181] In one embodiment, the method includes configuring at least one rule for the UE that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network. In one embodiment, the rule indicates that the UE sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining at least one paging collision among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
[00182] In one embodiment, the rule indicates that the UE sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining paging collisions among all received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs. In various embodiments, the rule indicates that the UE sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining a paging collision for a threshold number of contiguous paging opportunities among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
[00183] A third apparatus is disclosed for paging management for multiple universal subscriber identity modules. The third apparatus may be embodied as a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700. In some embodiments, the third apparatus includes a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
[00184] In one embodiment, the third apparatus includes a plurality of universal subscriber identity modules (“USIMs”), a processor that performs a registration procedure with a mobile wireless communication network, and a transceiver that receives an identifier from the mobile wireless communication network and checks for paging collisions between paging opportunities for the plurality of USIMs based on the received identifier.
[00185] In one embodiment, in response to determining paging collisions between the paging opportunities for the plurality of USIMs, the processor continuously performs deregistration from the mobile wireless communication network and re-registration with the mobile wireless communication network until no paging collisions between the paging opportunities for the plurality of USIMs are expected.
[00186] A third method is disclosed for paging management for multiple universal subscriber identity modules. The third method may be performed by a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700. In some embodiments, the third method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [00187] In one embodiment, the third method includes performing a registration procedure for a user equipment (”UE”) with a mobile wireless communication network, the UE comprising a plurality of universal subscriber identity modules (“USIMs”), receiving an identifier from the mobile wireless communication network, checking for paging collisions between paging opportunities for the plurality of USIMs based on the received identifier, and in response to determining paging collisions between the paging opportunities for the plurality of USIMs, continuously performing deregistration from the mobile wireless communication network and re registration with the mobile wireless communication network until no paging collisions between the paging opportunities for the plurality of USIMs are expected.
[00188] A fourth apparatus is disclosed for paging management for multiple universal subscriber identity modules. The fourth apparatus may be embodied as a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700. In some embodiments, the fourth apparatus includes a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [00189] In one embodiment, the fourth apparatus includes a plurality of universal subscriber identity modules (“USIMs”), a transceiver that, in response to notifying a mobile wireless communication network of paging collisions between paging opportunities for the plurality of USIMs, receives an offset value for monitoring paging opportunities for at least one of the plurality of USIMs associated with the paging collisions, and a processor that monitors paging opportunities for the at least one of the plurality of USIMs associated with the paging collisions using the received offset.
[00190] In one embodiment, the processor determines the paging collisions between paging opportunities for the plurality of USIMs and in response to the determined paging collisions, the transceiver initiates a radio resource connection (“RRC”) with the mobile wireless communication network. In certain embodiments, the RRC further comprises at least one of a new establishment cause and a logical channel identifier (“UCID”) for informing the mobile wireless communication network of a reason for initiating the RRC.
[00191] In one embodiment, the offset value is fixed according to a predetermined specification. In certain embodiments, the offset value is for at least one of the following parameters: a number of time slots, a number of subframes, a number of paging frames, a firstPDCCH-MonitoringOccasionOfiO parameter, and a user equipment identifier.
[00192] In one embodiment, the offset value comprises a fixed value for the at least one of the parameters. In certain embodiments, the offset value is a negative value. In various embodiments, the offset value is configured using radio resource connection (“RRC”) signaling. In some embodiments, the notification of the paging collisions that is sent to the mobile wireless communication network further comprises an indication of at least one parameter associated with monitoring paging opportunities for modifying with the offset value.
[00193] A fourth method is disclosed for paging management for multiple universal subscriber identity modules. The fourth method may be performed by a UE as described herein, for example, the remote unit 105, the UE 205 and/or the user equipment apparatus 700. In some embodiments, the fourth method is performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [00194] In one embodiment, the fourth method includes, in response to notifying a mobile wireless communication network of paging collisions between paging opportunities of a plurality of universal subscriber identity modules (“USIMs”) of a user equipment (“UE”) device, receiving an offset value for monitoring paging opportunities for at least one of the plurality of USIMs associated with the paging collisions, and monitoring paging opportunities for the at least one of the plurality of USIMs associated with the paging collisions using the received offset.
[00195] In one embodiment, the fourth method includes determining the paging collisions between paging opportunities for the plurality of USIMs and in response to the determined paging collisions, initiating a radio resource connection (“RRC”) with the mobile wireless communication network. In certain embodiments, the RRC further comprises at least one of a new establishment cause and a logical channel identifier (“LCID”) for informing the mobile wireless communication network of a reason for initiating the RRC.
[00196] In one embodiment, the offset value is fixed according to a predetermined specification. In certain embodiments, the offset value is for at least one of the following parameters: a number of time slots, a number of subframes, a number of paging frames, a firstPDCCH-MonitoringOccasionOfiO parameter, and a user equipment identifier.
[00197] In one embodiment, the offset value comprises a fixed value for the at least one of the parameters. In certain embodiments, the offset value is a negative value. In various embodiments, the offset value is configured using radio resource connection (“RRC”) signaling. In some embodiments, the notification of the paging collisions that is sent to the mobile wireless communication network further comprises an indication of at least one parameter associated with monitoring paging opportunities for modifying with the offset value.
[00198] A fifth apparatus is disclosed for paging management for multiple universal subscriber identity modules. The fifth apparatus may be embodied as a network device as described herein, for example, the network equipment apparatus 700. In some embodiments, the fifth apparatus may be embodied by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [00199] In one embodiment, the fifth apparatus includes a transceiver that receives an indication from a user equipment (“UE”) device that supports a plurality of universal subscriber identity modules (“USIMs”) of paging collisions between paging opportunities of the plurality of USIMs and a processor that determines an offset value for modifying at least one parameter that is used in determining paging opportunities for at least one of the plurality of USIMs that is associated with the paging collisions. In one embodiment, the transceiver sends the determined offset to the UE for modifying the determination of the paging opportunities for the at least one of the plurality of USIMs using the determined offset.
[00200] A fifth method is disclosed for paging management for multiple universal subscriber identity modules. The fifth method may be performed by a network device as described herein, for example, the network equipment apparatus 700. In some embodiments, the fifth method may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
[00201] In one embodiment, the fifth method includes receiving an indication from a user equipment (“UE”) device that supports a plurality of universal subscriber identity modules (“USIMs”) of paging collisions between paging opportunities of the plurality of USIMs, determining an offset value for modifying at least one parameter that is used in determining paging opportunities for at least one of the plurality of U SIMs that is associated with the paging collisions, and sending the determined offset to the UE for modifying the determination of the paging opportunities for the at least one of the plurality of USIMs using the determined offset.
[00202] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

CUAIMS
1. An apparatus, comprising: a plurality of universal subscriber identity modules (“USIMs”); a transceiver that receives, from a mobile wireless communication network associated with at least one of the USIMs, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision; and a processor that determines a paging collision for paging occasions of at least a subset of the plurality of USIMs, wherein the transceiver sends a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs.
2. The apparatus of claim 1, wherein the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises a one bit flag.
3. The apparatus of claim 1, wherein the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises an offset value for changing a starting position of a first paging occasion.
4. The apparatus of claim 1, wherein the transceiver further receives a same paging message according to the indicated solution in response to the request for assistance with alleviating the determined paging collision that was previously supposed to be received as part of the paging collision.
5. The apparatus of claim 1, wherein the processor determines the paging collision based on a rule that defines situations where the request for assistance with alleviating the determined paging collision is sent to the mobile wireless communication network.
6. The apparatus of claim 5, wherein the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining at least one paging collision among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
7. The apparatus of claim 5, wherein the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining paging collisions among all received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs .
8. The apparatus of claim 5, wherein the rule indicates that the transceiver sends the request to the mobile wireless communication network for assistance with alleviating the determined paging collision in response to determining a paging collision for a threshold number of contiguous paging opportunities among received paging opportunities in a certain time period of the at least a subset of the plurality of USIMs.
9. The apparatus of claim 1, wherein the processor determines the paging collision as at least a partial overlap in one of time and paging search space of at least one paging occasion of the paging occasions of the at least a subset of the plurality of USIMs.
10. The apparatus of claim 1, wherein the transceiver sends a subsequent request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs in response to expiration of timer that is initiated in response to the initial request for assistance with alleviating the determined paging collision.
11. The apparatus of claim 1, wherein the processor further selects a USIM of the at least a subset of USIMs for seeking assistance for alleviating paging collisions based at least on one of the following criteria: a preference for new radio (“NR”) USIM in case of inter-radio access technologies (“RAT”) over other RAT USIMs; in response to not receiving a response from a mobile wireless communication network corresponding to one of the USIMs to the request for assistance with alleviating the determined paging collision, selecting a mobile wireless communication network for a next USIM to request assistance with alleviating the determined paging collision; a preference for a solution for alleviating the determined paging collision provided by a mobile wireless communication network corresponding to one of the USIMs over a different solution provided by a mobile wireless communication network corresponding to a different USIM; a preference for using an equivalent home public land mobile network
(“EHPLMN”) USIM over a visited PLMN (“VPLMN”) USIM; and a preference for a USIM for a mobile wireless communication network that has a higher radio quality than a different mobile wireless communication network corresponding to a different USIM.
12. A method, comprising: receiving, from a mobile wireless communication network associated with at least one of a plurality of universal subscriber identity modules (“USIMs”) of a user equipment (“UE”) device, an indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision; determining a paging collision for paging occasions of at least a subset of the plurality of USIMs; and sending a request to the mobile wireless communication network for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs.
13. The method of claim 12, wherein the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises a one bit flag.
14. The method of claim 12, wherein the indication that the mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs comprises an offset value for changing a starting position of a first paging occasion.
15. An apparatus, comprising: a transceiver that: sends, to a user equipment (“UE”) device comprising a plurality of universal subscriber identity modules (“USIMs”), an indication that a mobile wireless communication network supports assistance for alleviating paging collisions between multiple USIMs and an indication of a solution to be used for alleviating the determined paging collision; and receives, from the UE, a request for assistance with alleviating the determined paging collision of the at least a subset of the plurality of USIMs; and a processor that determines a solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs, wherein the transceiver sends the determined solution for alleviating the determined paging collision of the at least a subset of the plurality of USIMs to the UE.
PCT/IB2021/056201 2020-07-09 2021-07-09 Paging management for multiple universal subscriber identity modules WO2022009177A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063050064P 2020-07-09 2020-07-09
US63/050,064 2020-07-09

Publications (1)

Publication Number Publication Date
WO2022009177A1 true WO2022009177A1 (en) 2022-01-13

Family

ID=76959010

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2021/056201 WO2022009177A1 (en) 2020-07-09 2021-07-09 Paging management for multiple universal subscriber identity modules

Country Status (1)

Country Link
WO (1) WO2022009177A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024167294A1 (en) * 2023-02-09 2024-08-15 엘지전자 주식회사 Communication method of musim terminal

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111294789A (en) * 2019-05-05 2020-06-16 展讯通信(上海)有限公司 Paging processing method and device, storage medium, terminal and network equipment

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111294789A (en) * 2019-05-05 2020-06-16 展讯通信(上海)有限公司 Paging processing method and device, storage medium, terminal and network equipment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on system enablers for devices having multiple Universal Subscriber Identity Modules (USIM) (Release 17)", no. V0.4.0, 24 June 2020 (2020-06-24), pages 1 - 77, XP051924123, Retrieved from the Internet <URL:ftp://ftp.3gpp.org/Specs/archive/23_series/23.761/23761-040.zip 23761-040rm.docx> [retrieved on 20200624] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024167294A1 (en) * 2023-02-09 2024-08-15 엘지전자 주식회사 Communication method of musim terminal

Similar Documents

Publication Publication Date Title
US20220053448A1 (en) Connection suspension for multiple sims
US20230093965A1 (en) Paging for multiple sims
US20230098840A1 (en) Measurement configuration for non-public radio cell
EP4374605A1 (en) Group-based mobility configuration
US20230292326A1 (en) Dci format that indicates to monitor for paging dci
US20230164834A1 (en) Incrementing a transmission counter in response to lbt failure
WO2021191873A1 (en) Requesting an information element of a system information block
WO2022009177A1 (en) Paging management for multiple universal subscriber identity modules
US20230319780A1 (en) Receiving collected data from a group of devices
US20240259997A1 (en) Paging management
WO2022009179A1 (en) Paging management for multiple universal subscriber identity modules
US20240196468A1 (en) Keeping a terminal in a connected state while the terminal is away from a communication network
US20230300725A1 (en) Acquiring on-demand system information
US20240147574A1 (en) User equipment power saving for v2x communications
US20230422341A1 (en) Configuring discontinuous reception for pc5 interface
WO2023042098A1 (en) Enhancing security against false base stations
WO2023126909A1 (en) Voice call support in wireless communication systems
EP4385276A1 (en) Downlink transmission/reception procedure for small data transmissions
WO2023047381A1 (en) Reporting sensing beams and association with transmission beams for lbt
WO2023170611A1 (en) Signaling slice to slice group mapping to a user equipment device
WO2023067502A1 (en) Resource selection considering sidelink drx
WO2023131907A1 (en) Cell reselection based on network slicing considering mobility
WO2023053091A1 (en) Timing alignment in rrc_inactive
WO2022070169A1 (en) Leaving a wireless network by a multi-sim ue for a stipulated time after receiving a paging message
CN118476269A (en) Determining slice support for neighboring cells

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21742898

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21742898

Country of ref document: EP

Kind code of ref document: A1