Techniques of handling GUTI assignment for musim while discontinuous offset timer is running
MUSIM UEs can initiate registration procedures to acquire necessary identifiers despite the running timer, addressing paging collisions and ensuring reliable paging reception.
Patent Information
- Application Number
- PCT/CN2025/097663
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2024-06-06
- Filing Date
- 2025-05-28
- Publication Date
- 2025-12-11
AI Technical Summary
MUSIM UEs face challenges in managing paging occasions due to paging timing collisions when the discontinuous coverage maximum time offset timer is running, preventing them from requesting necessary identifiers for paging timing control, leading to potential paging failures.
Allow MUSIM UEs to initiate registration procedures and stop the discontinuous coverage maximum time offset timer when specific conditions are met, such as detecting paging collisions or needing new identifiers, to promptly acquire necessary identifiers for paging management.
Enables MUSIM UEs to resolve paging timing collisions and maintain reliable paging reception by allowing timely acquisition of identifiers, preventing failures and optimizing network access.
Smart Images

Figure CN2025097663_11122025_PF_FP_ABST
Abstract
Description
TECHNIQUES OF HANDLING GUTI ASSIGNMENT FOR MUSIM WHILE DISCONTINUOUS OFFSET TIMER IS RUNNINGCROSS-REFERENCE TO RELATED APPLICATION (S)
[0001] This application claims priority to Indian Patent Application Serial No. 202421044000, entitled “METHOD TO HANDLE GUTI ASSIGNMENT FOR MUSIM WHILE DISCONTINUOUS OFFSET TIMER IS RUNNING” and filed on June 6, 2024, which is expressly incorporated by reference herein in its entirety.TECHNICAL FIELD
[0002] The present disclosure relates generally to wireless communications, and more particularly, to techniques of handling network signaling by Multi-Universal Subscriber Identity Module (MUSIM) User Equipment (UE) needing paging-related identifiers while a discontinuous coverage timer is running.BACKGROUND
[0003] The statements in this section merely provide background information related to the present disclosure and may not constitute prior art.
[0004] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with Internet of Things (IoT) ) , and other requirements. Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.SUMMARY
[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
[0007] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a UE. The UE starts a discontinuous coverage maximum time offset timer upon returning to coverage of a tracking area in a current registration after being out of coverage due to discontinuous coverage. The UE determines, while the discontinuous coverage maximum time offset timer is running, that the UE needs to request a new identifier for paging timing collision control or for deriving a paging occasion. The UE initiates a registration procedure to request the new identifier while the discontinuous coverage maximum time offset timer is running.
[0008] In another aspect of the disclosure, a method, a computer-readable medium, and a wireless network are provided. The wireless network may include one or more network entities. The one or more network entities receive a registration request from a User Equipment (UE) for a new identifier. The registration request is received while a discontinuous coverage maximum time offset timer is running at the UE. The UE has previously returned to coverage of a tracking area after a period of discontinuous coverage. The UE has determined it needs to request the new identifier for paging timing collision control or for deriving a paging occasion. The one or more network entities provide the new identifier to the UE in response to the registration request.
[0009] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.BRIEF DESCRIPTION OF THE DRAWINGS
[0010] FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.
[0011] FIG. 2 is a diagram illustrating a base station in communication with a UE in an access network.
[0012] FIG. 3 illustrates an example logical architecture of a distributed access network.
[0013] FIG. 4 illustrates an example physical architecture of a distributed access network.
[0014] FIG. 5 is a diagram illustrating an example of a satellite communication system with a UE in a coverage area of a satellite.
[0015] FIG. 6 is a flow chart of a method for initiating a registration procedure to obtain an identifier for paging management while a discontinuous coverage maximum time offset timer is running.
[0016] FIG. 7 is a flow chart of a method for providing an identifier to a UE for paging management in response to a registration request initiated by the UE while its discontinuous coverage maximum time offset timer is running.DETAILED DESCRIPTION
[0017] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
[0018] Several aspects of telecommunications systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
[0019] By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
[0020] Accordingly, in one or more example aspects, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.
[0021] FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network 100. The wireless communications system (also referred to as a wireless wide area network (WWAN) ) includes base stations 102, UEs 104, an Evolved Packet Core (EPC) 160, and another core network 190 (e.g., a 5G Core (5GC) ) . The base stations 102 may include macrocells (high power cellular base station) and / or small cells (low power cellular base station) . The macrocells include base stations. The small cells include femtocells, picocells, and microcells.
[0022] The base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) ) may interface with the EPC 160 through backhaul links 132 (e.g., SI interface) . The base stations 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN) ) may interface with core network 190 through backhaul links 184. In addition to other functions, the base stations 102 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages. The base stations 102 may communicate directly or indirectly (e.g., through the EPC 160 or core network 190) with each other over backhaul links 134 (e.g., X2 interface) . The backhaul links 134 may be wired or wireless.
[0023] The base stations 102 may wirelessly communicate with the UEs 104. Each of the base stations 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, the small cell 102’ may have a coverage area 110’ that overlaps the coverage area 110 of one or more macro base stations 102. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links 120 between the base stations 102 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to a base station 102 and / or downlink (DL) (also referred to as forward link) transmissions from a base station 102 to a UE 104. The communication links 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be through one or more carriers. The base stations 102 / UEs 104 may use spectrum up to 7 MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
[0024] Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.
[0025] The wireless communications system may further include a Wi-Fi access point (AP) 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154 in a 5 GHz unlicensed frequency spectrum. When communicating in an unlicensed frequency spectrum, the STAs 152 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
[0026] The small cell 102’ may operate in a licensed and / or an unlicensed frequency spectrum. When operating in an unlicensed frequency spectrum, the small cell 102’ may employ NR and use the same 5 GHz unlicensed frequency spectrum as used by the Wi-Fi AP 150. The small cell 102’ , employing NR in an unlicensed frequency spectrum, may boost coverage to and / or increase capacity of the access network.
[0027] A base station 102, whether a small cell 102’ or a large cell (e.g., macro base station) , may include an eNB, gNodeB (gNB) , or another type of base station. Some base stations, such as gNB 180 may operate in a traditional sub 6 GHz spectrum, in millimeter wave (mmW) frequencies, and / or near mmW frequencies in communication with the UE 104. When the gNB 180 operates in mmW or near mmW frequencies, the gNB 180 may be referred to as an mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. Radio waves in the band may be referred to as a millimeter wave. Near mmW may extend down to a frequency of 3 GHz with a wavelength of 100 millimeters. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, also referred to as centimeter wave. Communications using the mmW / near mmW radio frequency band (e.g., 3 GHz -300 GHz) has extremely high path loss and a short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short range.
[0028] The base station 180 may transmit a beamformed signal to the UE 104 in one or more transmit directions 108a. The UE 104 may receive the beamformed signal from the base station 180 in one or more receive directions 108b. The UE 104 may also transmit a beamformed signal to the base station 180 in one or more transmit directions. The base station 180 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 180 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 180 / UE 104. The transmit and receive directions for the base station 180 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.
[0029] The EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. The MME 162 may be in communication with a Home Subscriber Server (HSS) 174. The MME 162 is the control node that processes the signaling between the UEs 104 and the EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet protocol (IP) packets are transferred through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation as well as other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176. The IP Services 176 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and / or other IP services. The BM-SC 170 may provide functions for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmission, may be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN) , and may be used to schedule MBMS transmissions. The MBMS Gateway 168 may be used to distribute MBMS traffic to the base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and may be responsible for session management (start / stop) and for collecting eMBMS related charging information.
[0030] The core network 190 may include a Access and Mobility Management Function (AMF) 192, other AMFs 193, a location management function (LMF) 198, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. The AMF 192 may be in communication with a Unified Data Management (UDM) 196. The AMF 192 is the control node that processes the signaling between the UEs 104 and the core network 190. Generally, the SMF 194 provides QoS flow and session management. All user Internet protocol (IP) packets are transferred through the UPF 195. The UPF 195 provides UE IP address allocation as well as other functions. The UPF 195 is connected to the IP Services 197. The IP Services 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS) , a PS Streaming Service, and / or other IP services.
[0031] The base station may also be referred to as a gNB, Node B, evolved Node B (eNB) , an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a transmit reception point (TRP) , or some other suitable terminology. The base station 102 provides an access point to the EPC 160 or core network 190 for a UE 104. Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.
[0032] Although the present disclosure may reference 5G New Radio (NR) , the present disclosure may be applicable to other similar areas, such as LTE, LTE-Advanced (LTE-A) , Code Division Multiple Access (CDMA) , Global System for Mobile communications (GSM) , or other wireless / radio access technologies.
[0033] FIG. 2 is a block diagram of a base station 210 in communication with a UE 250 in an access network. In the DL, IP packets from the EPC 160 may be provided to a controller / processor 275. The controller / processor 275 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 275 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0034] The transmit (TX) processor 216 and the receive (RX) processor 270 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 216 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 274 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and / or channel condition feedback transmitted by the UE 250. Each spatial stream may then be provided to a different antenna 220 via a separate transmitter 218TX. Each transmitter 218TX may modulate an RF carrier with a respective spatial stream for transmission.
[0035] At the UE 250, each receiver 254RX receives a signal through its respective antenna 252. Each receiver 254RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor 256. The TX processor 268 and the RX processor 256 implement layer 1 functionality associated with various signal processing functions. The RX processor 256 may perform spatial processing on the information to recover any spatial streams destined for the UE 250. If multiple spatial streams are destined for the UE 250, they may be combined by the RX processor 256 into a single OFDM symbol stream. The RX processor 256 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal comprises a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 210. These soft decisions may be based on channel estimates computed by the channel estimator 258. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 210 on the physical channel. The data and control signals are then provided to the controller / processor 259, which implements layer 3 and layer 2 functionality.
[0036] The controller / processor 259 can be associated with a memory 260 that stores program codes and data. The memory 260 may be referred to as a computer-readable medium. In the UL, the controller / processor 259 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 259 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.
[0037] Similar to the functionality described in connection with the DL transmission by the base station 210, the controller / processor 259 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0038] Channel estimates derived by a channel estimator 258 from a reference signal or feedback transmitted by the base station 210 may be used by the TX processor 268 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 268 may be provided to different antenna 252 via separate transmitters 254TX. Each transmitter 254TX may modulate an RF carrier with a respective spatial stream for transmission. The UL transmission is processed at the base station 210 in a manner similar to that described in connection with the receiver function at the UE 250. Each receiver 218RX receives a signal through its respective antenna 220. Each receiver 218RX recovers information modulated onto an RF carrier and provides the information to a RX processor 270.
[0039] The controller / processor 275 can be associated with a memory 276 that stores program codes and data. The memory 276 may be referred to as a computer-readable medium. In the UL, the controller / processor 275 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 250. IP packets from the controller / processor 275 may be provided to the EPC 160. The controller / processor 275 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.
[0040] New radio (NR) may refer to radios configured to operate according to a new air interface (e.g., other than Orthogonal Frequency Divisional Multiple Access (OFDMA) -based air interfaces) or fixed transport layer (e.g., other than Internet Protocol (IP) ) . NR may utilize OFDM with a cyclic prefix (CP) on the uplink and downlink and may include support for half-duplex operation using time division duplexing (TDD) . NR may include Enhanced Mobile Broadband (eMBB) service targeting wide bandwidth (e.g. 80 MHz beyond) , millimeter wave (mmW) targeting high carrier frequency (e.g. 60 GHz) , massive MTC (mMTC) targeting non-backward compatible MTC techniques, and / or mission critical targeting ultra-reliable low latency communications (URLLC) service.
[0041] A single component carrier bandwidth of 100 MHz may be supported. In one example, NR resource blocks (RBs) may span 12 sub-carriers with a sub-carrier bandwidth of 60 kHz over a 0.25 ms duration or a bandwidth of 30 kHz over a 0.5 ms duration (similarly, 50MHz BW for 15kHz SCS over a 1 ms duration) . Each radio frame may consist of 10 subframes (10, 20, 40 or 80 NR slots) with a length of 10 ms. Each slot may indicate a link direction (i.e., DL or UL) for data transmission and the link direction for each slot may be dynamically switched. Each slot may include DL / UL data as well as DL / UL control data. UL and DL slots for NR may be as described in more detail below with respect to FIGs. 5 and 6.
[0042] The NR RAN may include a central unit (CU) and distributed units (DUs) . A NR BS (e.g., gNB, 5G Node B, Node B, transmission reception point (TRP) , access point (AP) ) may correspond to one or multiple BSs. NR cells can be configured as access cells (ACells) or data only cells (DCells) . For example, the RAN (e.g., a central unit or distributed unit) can configure the cells. DCells may be cells used for carrier aggregation or dual connectivity and may not be used for initial access, cell selection / reselection, or handover. In some cases DCells may not transmit synchronization signals (SS) in some cases DCells may transmit SS. NR BSs may transmit downlink signals to UEs indicating the cell type. Based on the cell type indication, the UE may communicate with the NR BS. For example, the UE may determine NR BSs to consider for cell selection, access, handover, and / or measurement based on the indicated cell type.
[0043] FIG. 3 illustrates an example logical architecture of a distributed RAN 300, according to aspects of the present disclosure. A 5G access node 306 may include an access node controller (ANC) 302. The ANC may be a central unit (CU) of the distributed RAN. The backhaul interface to the next generation core network (NG-CN) 304 may terminate at the ANC. The backhaul interface to neighboring next generation access nodes (NG-ANs) 310 may terminate at the ANC. The ANC may include one or more TRPs 308 (which may also be referred to as BSs, NR BSs, Node Bs, 5G NBs, APs, or some other term) . As described above, a TRP may be used interchangeably with “cell. ”
[0044] The TRPs 308 may be a distributed unit (DU) . The TRPs may be connected to one ANC (ANC 302) or more than one ANC (not illustrated) . For example, for RAN sharing, radio as a service (RaaS) , and service specific ANC deployments, the TRP may be connected to more than one ANC. A TRP may include one or more antenna ports. The TRPs may be configured to individually (e.g., dynamic selection) or jointly (e.g., joint transmission) serve traffic to a UE.
[0045] The local architecture of the distributed RAN 300 may be used to illustrate fronthaul definition. The architecture may be defined that support fronthauling solutions across different deployment types. For example, the architecture may be based on transmit network capabilities (e.g., bandwidth, latency, and / or jitter) . The architecture may share features and / or components with LTE. According to aspects, the next generation AN (NG-AN) 310 may support dual connectivity with NR. The NG-AN may share a common fronthaul for LTE and NR.
[0046] The architecture may enable cooperation between and among TRPs 308. For example, cooperation may be preset within a TRP and / or across TRPs via the ANC 302. According to aspects, no inter-TRP interface may be needed / present.
[0047] According to aspects, a dynamic configuration of split logical functions may be present within the architecture of the distributed RAN 300. The PDCP, RLC, MAC protocol may be adaptably placed at the ANC or TRP.
[0048] FIG. 4 illustrates an example physical architecture of a distributed RAN 400, according to aspects of the present disclosure. A centralized core network unit (C-CU) 402 may host core network functions. The C-CU may be centrally deployed. C-CU functionality may be offloaded (e.g., to advanced wireless services (AWS) ) , in an effort to handle peak capacity. A centralized RAN unit (C-RU) 404 may host one or more ANC functions. Optionally, the C-RU may host core network functions locally. The C-RU may have distributed deployment. The C-RU may be closer to the network edge. A distributed unit (DU) 406 may host one or more TRPs. The DU may be located at edges of the network with radio frequency (RF) functionality.
[0049] FIG. 5 is a diagram 500 illustrating an example of a satellite communication system with a UE 504 in a coverage area 550 of a satellite 506. The UE 504 is a Multi-USIM (MUSIM) capable device that can operate with multiple subscriber identities simultaneously. The satellite 506 provides wireless communication services within its geographic coverage area 550, connecting the UE 504 to various core networks including a 5G System (5GS) 516 with an Access and Mobility Management Function (AMF) 518, and an Evolved Packet System (EPS) 556 with a Mobility Management Entity (MME) 558. Other network elements may be present in the 5GS 516 and EPS 556 as described in relation to FIG. 1 (e.g., SMF, UPF, Serving Gateway, PDN Gateway) .
[0050] In satellite communications, discontinuous coverage scenarios frequently occur when a UE 504 moves outside the coverage area 550 and later returns. When the UE 504 re-enters the coverage area 550, it may need to manage its network access timing to prevent congestion. This is particularly important in satellite networks where resources are limited and multiple UEs may attempt to access the network simultaneously upon regaining coverage.
[0051] The UE 504 may have previously received a discontinuous coverage maximum time offset value from the network in a REGISTRATION ACCEPT message, along with an indication that the UE needs to report the end of unavailability period. This maximum time offset value is specific to the current Public Land Mobile Network (PLMN) and NR satellite access. A PLMN refers to a network established by a mobile network operator to provide mobile telecommunications services, while NR satellite access refers to the 5G New Radio technology adapted for satellite communications.
[0052] Upon re-entering the coverage area 550, the UE 504 starts a discontinuous coverage maximum time offset timer with a random value up to and including the stored maximum time offset value. This randomization helps distribute network access attempts from multiple UEs over time, reducing potential congestion on the satellite link and core network nodes like the AMF 518 or MME 558.
[0053] As a MUSIM UE, the UE 504 can operate with multiple Universal Subscriber Identity Modules (USIMs) , allowing it to maintain registrations for different subscriptions, potentially with different network operators or services, concurrently. To manage the complexities of multiple active subscriptions, both the MUSIM UE 504 and the network (represented by the 5GS 516 including the AMF 518, or the EPS 556 including the MME 558) may support specific MUSIM features. These features include, but are not limited to, N1 Non-Access Stratum (NAS) signaling connection release, paging indication for voice services, reject paging request, paging restriction, and paging timing collision control. These features aim to optimize resource usage and improve the user experience for devices managing multiple subscriptions.
[0054] During network registration procedures (e.g., initial registration or mobility registration update with the AMF 518, or attach / tracking area update with the MME 558) , the MUSIM UE 504 indicates its supported MUSIM features to the network. The support for paging timing collision control may be determined through UE capabilities rather than explicitly indicated in the registration request message itself. If the UE 504 supports features like N1 NAS signaling connection release or reject paging request, and also supports paging restriction, it indicates support for paging restriction. The network, upon receiving the UE’s indication, decides which features it will support for this UE 504 and informs the UE 504 in the corresponding registration accept message (e.g., REGISTRATION ACCEPT from the AMF 518 or TRACKING AREA UPDATE ACCEPT from the MME 558) . The network enforces certain dependencies; for instance, it will only indicate support for paging restriction if it also supports either the N1 NAS signaling connection release or the reject paging request feature for that UE 504.
[0055] The paging timing collision control feature allows the MUSIM UE 504 to manage the timing of its paging occasions (POs) across its different subscriptions to prevent or resolve collisions, where the UE 504 might be expected to monitor for pages for multiple subscriptions simultaneously. To effectively manage these POs, the UE’s lower layers often rely on parameters derived from identifiers assigned by the network. Specifically, in 5GS 516, the UE 504 may need a new 5G Globally Unique Temporary Identifier (5G-GUTI) assigned by the AMF 518, which influences PO calculation. Similarly, in EPS 556, the UE 504 may need an International Mobile Subscriber Identity (IMSI) offset value assigned by the MME 558 for PO calculation. The need to request a new 5G-GUTI or IMSI offset can arise when the UE 504 detects a potential PO collision or based on other internal triggers related to managing multiple radio interfaces or subscriptions.
[0056] In one scenario, the MUSIM UE 504, supporting paging timing collision control, may need to request a new 5G-GUTI from the AMF 518 or an IMSI offset from the MME 558 while the discontinuous coverage maximum time offset timer is running. As described supra, this timer is started when the UE 504 re-enters the satellite coverage area 550 after a period of discontinuous coverage, specifically to stagger network access attempts.
[0057] In a first scheme, if the need to request these identifiers arises (e.g., due to detected PO collision or other lower layer requirements) while the discontinuous coverage maximum time offset timer is running, the UE 504 is prohibited from initiating the necessary signaling (e.g., Registration Request or Tracking Area Update Request) . This restriction poses a significant problem for MUSIM operation. If the UE 504 requires a new identifier for paging timing collision control but is barred from requesting it because the discontinuous coverage maximum time offset timer is active, it cannot resolve the PO collision or adjust its PO timing as needed. This inability to obtain the necessary network-assigned identifier can lead directly to paging failures, as the UE 504 may not monitor the correct PO for incoming calls or data for one or more of its subscriptions.
[0058] In a second scheme, to address the problem identified in the first scheme, specific exceptions are introduced to the restrictions imposed by the discontinuous coverage maximum time offset timer. This second scheme allows a MUSIM capable UE 504 to prioritize the resolution of potential paging issues related to its multiple subscriptions, even shortly after returning to satellite coverage.
[0059] Specifically, if the MUSIM UE 504, while the discontinuous coverage maximum time offset timer is running, detects a paging occasion (PO) collision between its subscriptions, or determines a need to request an IMSI Offset value for deriving its paging occasion when operating in the EPS 556, or determines a need to request a new 5G-GUTI assignment for paging timing collision control when operating in the 5GS 516, the UE 504 is permitted to initiate the necessary Non-Access Stratum (NAS) signaling procedures. That is, the UE 504 can send a TRACKING AREA UPDATE REQUEST message to the MME 558 to obtain the IMSI offset value, or send a REGISTRATION REQUEST message (for mobility registration update) to the Access and Mobility Management Function (AMF) 518 to obtain a new 5G-GUTI, despite the timer being active.
[0060] Furthermore, upon initiating such a procedure under these specific MUSIM-related conditions (i.e., needing an IMSI offset for PO derivation or needing a 5G-GUTI for paging timing collision control) , the UE 504 may also stop the discontinuous coverage maximum time offset timer, if it is running. This modification allows the MUSIM UE 504 to promptly acquire the required identifiers needed for its lower layers to manage and resolve PO timing issues, thereby preventing potential paging failures that could occur if the UE 504 were forced to wait for the timer to expire or until another triggering condition occurred. The primary purpose of the timer, which is to stagger network access for general registration updates after returning to coverage, is overridden in these specific circumstances to maintain reliable paging reception for the MUSIM UE 504.
[0061] The second scheme, in 5G systems, modifies the conditions under which the UE 504, operating under the discontinuous coverage maximum time offset timer, is allowed to stop the timer and initiate NAS signaling. The conditions (e.g., receiving a paging message, receiving a NOTIFICATION message over non-3GPP access, having pending emergency services, establishing an emergency PDU session, performing emergency services fallback, or entering a Tracking Area Identity (TAI) outside the registration area) are augmented with a new condition specific to MUSIM needs. That is, the UE shall stop the discontinuous coverage maximum time offset timer and initiate NAS signaling if the MUSIM UE needs to request a new 5G-GUTI assignment as described supra. An exception is created for the MUSIM UE 504 needing a new 5G-GUTI for reasons such as paging timing collision control. The MUSIM UE 504 bypasses the restriction imposed by the running timer and initiate a mobility registration update procedure towards the AMF 518.
[0062] A similar exception is introduced for EPS operation, allowing the UE 504 to stop the timer and initiate a Tracking Area Update procedure towards the MME 558 to request an IMSI offset value when needed for PO derivation, even if the corresponding timer for discontinuous coverage is running. More specifically, the MUSIM UE 504 might need to request an IMSI offset value from the Mobility Management Entity (MME) 558. This IMSI offset is used in deriving the UE’s paging occasion, and requesting a new value might be necessary to resolve potential PO collisions between different subscriptions or for other reasons related to managing multiple USIMs.
[0063] The second scheme modifies the conditions in the first scheme under which the UE 504 can stop the timer and initiate NAS signaling. The modification explicitly allows the MUSIM UE 504 to stop the discontinuous coverage maximum time offset timer and initiate NAS signaling (i.e., send a TRACKING AREA UPDATE REQUEST message to the MME 558) if the MUSIM UE 504 needs to request an IMSI offset value. The MUSIM UE 504 can obtain the necessary IMSI offset from the MME 558 without undue delay caused by the timer, thereby maintaining reliable paging reception.
[0064] FIG. 6 is a flow chart 600 of a method for initiating a registration procedure to obtain an identifier for paging management while a discontinuous coverage maximum time offset timer is running. The method may be performed by a User Equipment (UE) , for example, the UE 504 as described in Technical Description A.
[0065] In operation 602, the UE starts a discontinuous coverage maximum time offset timer upon returning to coverage of a tracking area in a current registration after being out of coverage due to discontinuous coverage. In certain configurations, the discontinuous coverage maximum time offset timer is started with a random value up to and including a stored maximum time offset value received from a network.
[0066] In operation 604, the UE determines, while the discontinuous coverage maximum time offset timer is running, that the UE needs to request a new identifier for paging timing collision control or for deriving a paging occasion. In certain configurations, the UE is a Multi-Universal Subscriber Identity Module (MUSIM) UE supporting paging timing collision control. In certain configurations, to determine that the UE needs to request the new identifier, the UE detects a paging occasion collision between multiple subscriptions of the UE. In certain configurations, to determine that the UE needs to request the new identifier, the UE receives a request from a lower layer of the UE to modify timing of paging occasions.
[0067] In operation 606, the UE initiates a registration procedure to request the new identifier while the discontinuous coverage maximum time offset timer is running. In certain configurations, the new identifier comprises a 5G Globally Unique Temporary Identifier (5G-GUTI) for operation in a 5G System (5GS) . To initiate the registration procedure, the UE further initiates a mobility registration update procedure with an Access and Mobility Management Function (AMF) . In certain configurations, the new identifier comprises an International Mobile Subscriber Identity (IMSI) offset value for operation in an Evolved Packet System (EPS) . To initiate the registration procedure, the UE further initiates a tracking area update procedure with a Mobility Management Entity (MME) .
[0068] In certain configurations, the UE stops the discontinuous coverage maximum time offset timer in response to determining that the UE needs to request the new identifier.
[0069] FIG. 7 is a flow chart 700 of a method for providing an identifier to a UE for paging management in response to a registration request initiated by the UE while its discontinuous coverage maximum time offset timer is running. The method may be performed by one or more network entities (e.g., the 5GS 516 including the AMF 518, or the EPS 556 including the MME 558, as described supra referring to FIG. 5) .
[0070] In certain configurations, prior to receiving a registration request, the one or more network entities transmit, to a UE, a maximum time offset value for starting the discontinuous coverage maximum time offset timer. The discontinuous coverage maximum time offset timer is started by the UE with a random value up to and including the maximum time offset value.
[0071] In operation 702, the one or more network entities receive, from the UE, a registration request for a new identifier while a discontinuous coverage maximum time offset timer is running at the UE. The registration request is received after the UE returned to coverage of a tracking area after being out of coverage due to discontinuous coverage, and the UE determined a need to request the new identifier for paging timing collision control or for deriving a paging occasion.
[0072] In certain configurations, the UE is a Multi-Universal Subscriber Identity Module (MUSIM) UE supporting paging timing collision control. In certain configurations, the registration request is received based on a determination by the UE to modify timing of paging occasions responsive to a request from a lower layer of the UE. In certain configurations, the one or more network entities determine that the registration request is for requesting the new identifier for paging timing collision control, and process the registration request despite the discontinuous coverage maximum time offset timer running at the UE.
[0073] In operation 704, the one or more network entities provide, to the UE, the new identifier in response to the registration request. In certain configurations, the new identifier includes a 5G Globally Unique Temporary Identifier (5G-GUTI) for operation in a 5G System (5GS) , and the one or more network entities include an Access and Mobility Management Function (AMF) . In certain configurations, the new identifier includes an International Mobile Subscriber Identity (IMSI) offset value for operation in an Evolved Packet System (EPS) , and the one or more network entities include a Mobility Management Entity (MME) . In certain configurations, providing the new identifier enables the UE to resolve a paging occasion collision between multiple subscriptions of the UE.
[0074] The UE 504, as depicted in FIG. 5, may be implemented with hardware components analogous to those detailed for the UE 250 shown in FIG. 2. Specifically, UE 504 would typically comprise one or more processors (such as the controller / processor 259) , a memory (such as memory 260) , and one or more transceivers. These transceivers would generally include transmit (TX) processors (e.g., TX processor 268) , receive (RX) processors (e.g., RX processor 256) , associated transmitters (e.g., 254TX) and receivers (e.g., 254RX) , and one or more antennas (e.g., antennas 252) . This hardware configuration enables UE 504 to perform wireless communication, including the specific operations within satellite communication systems (e.g., with satellite 506) and interaction with core network entities such as the Access and Mobility Management Function (AMF) 518 or the Mobility Management Entity (MME) 558.
[0075] These hardware components are used by the UE 504 to execute the method described in FIG. 6. For instance, the controller / processor 259, executing program code stored in memory 260, would be responsible for managing the discontinuous coverage maximum time offset timer, including starting the timer upon returning to coverage, determining if conditions are met to request a new identifier (e.g., a 5G-GUTI or an IMSI offset) for paging timing collision control or paging occasion derivation while the timer is running, and potentially stopping the timer. The memory 260 would store the discontinuous coverage maximum time offset value, the UE’s current identifiers, and context related to its Multi-USIM (MUSIM) operations. The determination that a new identifier is needed (e.g., due to a detected Paging Occasion (PO) collision or a request from lower layers) would be made by the controller / processor 259. Subsequently, the controller / processor 259 would initiate the appropriate registration procedure (e.g., a mobility registration update or a tracking area update procedure) by constructing the relevant Non-Access Stratum (NAS) messages, which are then processed by the TX processor 268 and transmitted via the transmitters 254TX and antennas 252 to the network. The MUSIM-specific functionalities, such as supporting paging timing collision control, would also be managed by the controller / processor 259, using the memory 260 for managing multiple subscription contexts.
[0076] The network entities involved, particularly the AMF 518 in a 5GS or the MME 558 in an EPS as referenced in FIG. 5, may be realized using server-grade hardware. This hardware infrastructure generally includes one or more powerful processors (conceptually analogous to the controller / processor 275 found in base station 210, but scaled for core network demands) , substantial amounts of memory (akin to memory 276) , and high-throughput network interfaces. These components enable communication with other network elements (e.g., the satellite 506 or the base station 102) and user data repositories (e.g., UDM / HSS) . The processors in the AMF or MME execute specialized software stored in their memory to manage critical functions like UE registration, mobility, and temporary identifier assignment. Specifically, in the scenario described supra, when the MUSIM UE 504 transmits a request for a new 5G-GUTI or an IMSI offset to resolve paging occasion issues-even while its discontinuous coverage maximum time offset timer is active-the processors of the AMF 518 or MME 558 are responsible for receiving this request (via an access network node) , processing it according to the new permissive logic, allocating the requested identifier, and transmitting a response message (e.g., REGISTRATION ACCEPT or TRACKING AREA UPDATE ACCEPT) containing the new identifier back to the UE 504.
[0077] The access network node, which directly communicates with the UE 504 and relays messages to / from the core network entities (AMF 518 / MME 558) , can be a terrestrial base station (e.g., eNB / gNB 102, or base station 210 as detailed in FIG. 2) or a satellite 506. The hardware of such a node, as exemplified by base station 210, includes a controller / processor 275, memory 276, a transmit (TX) processor 216, a receive (RX) processor 270, multiple transmitters 218TX and receivers 218RX, and antennas 220. The controller / processor 275, executing firmware / software from memory 276, manages the radio interface and the forwarding of Non-Access Stratum (NAS) messages. When the UE 504 initiates a registration procedure to request a new identifier while its discontinuous coverage timer is running, the base station’s RX processor 270 and receivers 218RX receive the uplink NAS message. The controller / processor 275 then forwards this message towards the AMF 518 or MME 558. Subsequently, when the core network responds (e.g., with a new 5G-GUTI or IMSI offset) , the base station receives the downlink NAS message, which is processed by its TX processor 216 and transmitted via transmitters 218TX and antennas 220 to the UE 504.
[0078] It is understood that the specific order or hierarchy of blocks in the processes / flowcharts disclosed is an illustration of exemplary approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not meant to be limited to the specific order or hierarchy presented.
[0079] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but is to be accorded the full scope consistent with the language claims, wherein reference to an element in the singular is not intended to mean “one and only one” unless specifically so stated, but rather “one or more. ” The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, the term “some” refers to one or more. Combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”
Claims
1.A method of wireless communication performed by a User Equipment (UE) , comprising:starting a discontinuous coverage maximum time offset timer upon returning to coverage of a tracking area in a current registration after being out of coverage due to discontinuous coverage;determining, while the discontinuous coverage maximum time offset timer is running, that the UE needs to request a new identifier for paging timing collision control or for deriving a paging occasion; andinitiating a registration procedure to request the new identifier while the discontinuous coverage maximum time offset timer is running.2.The method of claim 1, further comprising:stopping the discontinuous coverage maximum time offset timer in response to determining that the UE needs to request the new identifier.3.The method of claim 1, wherein the UE is a Multi-Universal Subscriber Identity Module (MUSIM) UE supporting paging timing collision control.4.The method of claim 1, wherein the new identifier comprises a 5G Globally Unique Temporary Identifier (5G-GUTI) for operation in a 5G System (5GS) , and wherein initiating the registration procedure comprises initiating a mobility registration update procedure with an Access and Mobility Management Function (AMF) .5.The method of claim 1, wherein the new identifier comprises an International Mobile Subscriber Identity (IMSI) offset value for operation in an Evolved Packet System (EPS) , and wherein initiating the registration procedure comprises initiating a tracking area update procedure with a Mobility Management Entity (MME) .6.The method of claim 1, wherein determining that the UE needs to request the new identifier comprises detecting a paging occasion collision between multiple subscriptions of the UE.7.The method of claim 1, wherein determining that the UE needs to request the new identifier comprises receiving a request from a lower layer of the UE to modify timing of paging occasions.8.The method of claim 1, wherein the discontinuous coverage maximum time offset timer is started with a random value up to and including a stored maximum time offset value received from a network.9.A method for wireless communication and performed by one or more network entities, comprising:receiving, from a User Equipment (UE) , a registration request for a new identifier while a discontinuous coverage maximum time offset timer is running at the UE, wherein the registration request is received after the UE returned to coverage of a tracking area after being out of coverage due to discontinuous coverage, and wherein the UE determined a need to request the new identifier for paging timing collision control or for deriving a paging occasion; andproviding, to the UE, the new identifier in response to the registration request.10.The method of claim 9, wherein the UE is a Multi-Universal Subscriber Identity Module (MUSIM) UE supporting paging timing collision control.11.The method of claim 9, wherein the new identifier comprises a 5G Globally Unique Temporary Identifier (5G-GUTI) for operation in a 5G System (5GS) , and wherein the network comprises an Access and Mobility Management Function (AMF) .12.The method of claim 9, wherein the new identifier comprises an International Mobile Subscriber Identity (IMSI) offset value for operation in an Evolved Packet System (EPS) , and wherein the network comprises a Mobility Management Entity (MME) .13.The method of claim 9, wherein providing the new identifier enables the UE to resolve a paging occasion collision between multiple subscriptions of the UE.14.The method of claim 9, wherein the registration request is received based on a determination by the UE to modify timing of paging occasions responsive to a request from a lower layer of the UE.15.The method of claim 9, further comprising:transmitting, to the UE, a maximum time offset value for starting the discontinuous coverage maximum time offset timer, wherein the discontinuous coverage maximum time offset timer is started with a random value up to and including the maximum time offset value.16.The method of claim 9, further comprising:determining that the registration request is for requesting the new identifier for paging timing collision control; andprocessing the registration request despite the discontinuous coverage maximum time offset timer running at the UE.17.An apparatus for wireless communication, the apparatus being a user equipment (UE) , comprising:a memory; andat least one processor coupled to the memory and configured to:start a discontinuous coverage maximum time offset timer upon returning to coverage of a tracking area in a current registration after being out of coverage due to discontinuous coverage;determine, while the discontinuous coverage maximum time offset timer is running, that the UE needs to request a new identifier for paging timing collision control or for deriving a paging occasion; andinitiate a registration procedure to request the new identifier while the discontinuous coverage maximum time offset timer is running.18.The apparatus of claim 17, wherein the at least one processor is further configured to:stop the discontinuous coverage maximum time offset timer in response to determining that the UE needs to request the new identifier.19.The apparatus of claim 17, wherein the UE is a Multi-Universal Subscriber Identity Module (MUSIM) UE supporting paging timing collision control.20.The apparatus of claim 17, wherein the new identifier comprises a 5G Globally Unique Temporary Identifier (5G-GUTI) for operation in a 5G System (5GS) , and wherein to initiate the registration procedure, the at least one processor is configured to initiate a mobility registration update procedure with an Access and Mobility Management Function (AMF) .
Citation Information
Patent Citations
User equipment operation with multiple subscriber identity modules
US20210120524A1
Musim IMSI offset value handling for paging timing collision control
US20230034780A1
Multi subscriber identity module user equipment, network node, and method for operating same
WO2020238127A1
Paging in discontinuous coverage
WO2023015151A1