Initiation and registration procedure for unavailable cycles

Abstract

According to one aspect of the present disclosure, a method, a computer readable medium, and an apparatus are provided. The device may be a user equipment (UE). The user equipment determines that the unavailable information has changed. The unavailable information includes at least one of a start time of an unavailable period or a duration of the unavailable period. The user equipment performs a registration procedure using the network to provide updated unavailable information.

Description

[0001] Cross-references

[0002] This application claims priority to Indian Patent Application Serial No. 202321055928, entitled “Initiation and Registration Process of Unavailable Cycles”, filed on August 21, 2023, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to wireless communication, and more specifically to techniques for updating unavailable periodic information in wireless communication systems. Background Technology

[0004] The statements in this section provide only background information in relation to this disclosure and may not constitute prior art.

[0005] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies to support communication with multiple users by sharing available system resources. Examples of these 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.

[0006] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. One example of a telecommunications standard is 5G New Radio (NR). 5G NR is part of the ongoing evolution of mobile broadband driven by the Third Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., the Internet of Things (IoT)), and other requirements. Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements may also apply to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0007] The following is a simplified summary of one or more aspects to provide a basic understanding of them. This summary is not a comprehensive overview of all hypothetical aspects, nor is it intended to identify key or important elements of all aspects, nor to define 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 a more detailed description thereafter.

[0008] In one aspect of this disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a user equipment (UE). The UE determines that unavailability information has changed. The unavailability information includes at least one of the start time of an unavailability period or the duration of the unavailability period. The UE performs a registration process with a network to provide updated unavailability information.

[0009] To achieve the foregoing and related objectives, one or more aspects include the following features, which will be described in detail below and specifically pointed out in the claims. The following description and figures list in detail certain illustrative features of one or more aspects. However, these features merely illustrate several ways in which the principles of the various aspects can be adopted, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0010] Figure 1 This is a schematic diagram of an example wireless communication system and access network.

[0011] Figure 2 This is a schematic diagram showing the communication between the base station and user equipment in the access network.

[0012] Figure 3 An example logical architecture for a distributed access network is shown.

[0013] Figure 4 An example physical architecture of a distributed access network is shown.

[0014] Figure 5 This is a schematic diagram showing an example of a downlink center timeslot.

[0015] Figure 6 This is a schematic diagram showing an example of the uplink center timeslot.

[0016] Figure 7 This is a schematic diagram showing a wireless communication system that supports 5G networks.

[0017] Figure 8 This is a schematic diagram showing a wireless communication system that supports unavailable cycles in a 4G network.

[0018] Figure 9 This is a flowchart of the method for updating unavailable cycles. Detailed Implementation

[0019] The following detailed description, taken in conjunction with the accompanying drawings, is intended to illustrate various configurations and is not intended to represent the only configurations in which the concepts described herein can be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, those skilled in the art will appreciate that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0020] Several aspects of a telecommunications system will now be introduced with reference to various devices and methods. These devices and methods will be described in detail below and illustrated in the accompanying drawings by various modules, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination of both. Whether these elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

[0021] For example, an element, any part of an element, or any combination of elements can be implemented as a “processing system” containing 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 hardware suitable for performing the various functions described in this disclosure. One or more processors in a processing system can execute software. Software should be understood broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, application programs, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or others.

[0022] Therefore, in one or more example aspects, the described functionality can be implemented in hardware, software, or any combination of both. If implemented in software, these functions can be stored or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media. Storage media can be any available medium that is accessible to a computer. For example, and not limited to, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium that can be used to store computer-executable code in the form of instructions or data structures and is accessible to a computer.

[0023] Figure 1This is a schematic diagram of an example wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes a base station 102, a user equipment (UE) 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core network (5GC)). The base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

[0024] Base station 102 configured as 4G LTE (collectively referred to as the Evolved UMTS Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via backhaul link 132 (e.g., SI interface). Base station 102 configured as 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via backhaul link 184. In addition to other functions, base station 102 may perform one or more of the following functions: user data transmission, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection setup and release, load balancing, distribution of Non-Access Stratum (NAS) messages, NAS node selection, synchronization, Radio Access Network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, location, and warning message delivery. Base station 102 may communicate with each other directly or indirectly (e.g., via EPC 160 or core network 190) via backhaul link 134 (e.g., X2 interface). Backhaul link 134 may be wired or wireless.

[0025] Base station 102 can wirelessly communicate with user equipment (UE) 104. Each base station 102 can provide communication coverage for a corresponding geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network containing small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may also include Home Evolved Node Bs (HeNBs), which can provide service to a restricted group referred to as a closed subscriber group (CSG). The communication link 120 between base station 102 and user equipment 104 may include uplink (UL) (also known as reverse link) transmission from user equipment 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to user equipment 104. Communication link 120 may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be established via one or more carriers. Base station 102 / user equipment 104 may use each carrier with a spectrum bandwidth up to 7 MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) to allocate transmission in each direction in carrier aggregation, for a total of up to Yx MHz (x component carriers). Carriers may be adjacent or non-adjacent. Carrier allocation may be asymmetrical in terms of DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include one primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carriers may be referred to as secondary cells (SCells).

[0026] Some user equipment 104 can communicate with each other using device-to-device (D2D) communication links 158. D2D communication links 158 can use DL / UL WWAN spectrum. D2D communication links 158 can use one or more sidelink channels, such as physical sidelink broadcast channels (PSBCH), physical sidelink discovery channels (PSDCH), physical sidelink shared channels (PSSCH), and physical sidelink control channels (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0027] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with Wi-Fi stations (STAs) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, STA 152 / AP 150 may perform a clear channel assessment (CCA) before communication to determine whether the channel is available.

[0028] Small Cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, Small Cell 102' can employ NR and use the same 5 GHz unlicensed spectrum as Wi-Fi AP 150. Employing NR in unlicensed spectrum can enhance the coverage and / or increase the capacity of the access network.

[0029] Base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include an eNB, gNodeB (gNB), or other types of base stations. Some base stations, such as gNB 180, can communicate with user equipment 104 in conventional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near-millimeter wave frequencies. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Extremely high frequency (EHF) is the radio frequency portion of the electromagnetic spectrum. EHF ranges from 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near-millimeter waves can extend down to frequencies of 3 GHz with wavelengths of 100 mm. The ultra-high frequency (SHF) band is between 3 GHz and 30 GHz, also known as centimeter waves. Communication using millimeter wave / near millimeter wave radio frequency bands (e.g., 3 GHz - 300 GHz) suffers from extremely high path loss and short range. Millimeter wave base station 180 can utilize beamforming 182 to communicate with user equipment 104 to compensate for the extremely high path loss and short range.

[0030] Base station 180 can transmit beamforming signals to user equipment 104 in one or more transmit directions 108a. User equipment 104 can receive beamforming signals from base station 180 in one or more receive directions 108b. User equipment 104 can also transmit beamforming signals to base station 180 in one or more transmit directions. Base station 180 can receive beamforming signals from user equipment 104 in one or more receive directions. Base station 180 / user equipment 104 can perform beam training to determine the optimal receive and transmit directions for base station 180 / user equipment 104. The transmit and receive directions of base station 180 may be the same or different. The transmit and receive directions of user equipment 104 may be the same or different.

[0031] 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. MME 162 can communicate with the Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. BM-SC 170 can provide MBMS user service provisioning and delivery functions. BM-SC 170 can serve as an entry point for content provider MBMS transmission, can be used to authorize and initiate MBMS bearer services within a public landmobile network (PLMN), and can be used to schedule MBMS transmissions. MBMS gateway 168 can be used to distribute MBMS traffic to base station 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts specific services, and can be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0032] The core network 190 may include an 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 can communicate with the Unified Data Management (UDM) 196. The AMF 192 is the control node that handles signaling between the UE 104 and the core network 190. Typically, the SMF 194 provides QoS streaming and session management. All user Internet Protocol (IP) packets are transmitted through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 connects to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services.

[0033] A base station may also be referred to as a gNB, Node B, evolved Node B (eNB), access point, base transceiver station, wireless base station, wireless transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit reception point (TRP), or other suitable terms. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite broadcasting, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, gas pumps, large or small kitchen appliances, medical devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UE 104 devices may be referred to as Internet of Things (IoT) devices (e.g., parking timers, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, user station, mobile unit, user cell, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile user station, access terminal, mobile terminal, radio terminal, remote terminal, handheld device, user agent, mobile client, client, or other suitable terms.

[0034] While this disclosure may refer to 5G New Radio (NR), it may apply to other similar fields, such as LTE, LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Global System for Mobile communications (GSM), or other wireless / wireless access technologies.

[0035] Figure 2This is a block diagram illustrating communication between base station 210 and user equipment (UE) 250 in the access network. In the downlink, IP packets from EPC 160 may be provided to controller / processor 275. Controller / processor 275 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 275 provides RRC layer functions related to system information (e.g., MIB, SIBs) broadcasting, 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 reports; PDCP layer functions related to header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions related to upper-layer packet data unit (PDU) transmission, error correction via ARQ, RLC service data unit (SDU) connection, segmentation and reassembly, RLC data PDU resegmentation, and RLC data PDU reordering; and MAC layer functions related to mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority.

[0036] Transmit (TX) processor 216 and receive (RX) processor 270 implement Layer 1 functions related to various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 216 processes the mapped signal constellation according to various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). Encoded and modulated symbols may be split into parallel streams. Each stream may be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 274 may be used to determine coding and modulation schemes, as well as for spatial processing. The channel estimates may be derived from the reference signal and / or channel condition feedback transmitted by 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 to transmit the corresponding spatial stream.

[0037] At UE 250, each receiver 254RX receives signals through its corresponding antenna 252. Each receiver 254RX recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 256. The TX processor 268 and RX processor 256 implement Layer 1 functions related to various signal processing functions. The RX processor 256 may perform spatial processing on the information to recover any spatial streams oriented towards UE 250. If multiple spatial streams are oriented towards UE 250, they may be combined by the RX processor 256 into a single OFDM symbol stream. The RX processor 256 then uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each OFDM signal subcarrier. The symbols and reference signals on each subcarrier are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 210. These soft decisions may be based on channel estimates calculated by channel estimator 258. The soft decision is then decoded and deinterleaved to recover the data and control signals initially transmitted by base station 210 on the physical channel. The data and control signals are then provided to controller / processor 259, which implements Layer 3 and Layer 2 functions.

[0038] Controller / processor 259 may be associated with memory 260, which stores program code and data. Memory 260 may be referred to as a computer-readable medium. In the uplink, controller / processor 259 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between the transmission and logical channels to recover IP packets from EPC 160. Controller / processor 259 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0039] Similar to the functions described in the downlink transmission of base station 210, controller / processor 259 provides RRC layer functions related to system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions related to header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions related to upper-layer PDU transmission, error correction via ARQ, RLC SDU connection, segmentation and reassembly, RLC data PDU resegmentation, and RLC data PDU reordering; and MAC layer functions related to mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and logical channel priority.

[0040] The channel estimate derived by channel estimator 258 from the reference signal or feedback transmitted by base station 210 can be used by TX processor 268 to select appropriate coding and modulation schemes and facilitate spatial processing. The spatial stream generated by TX processor 268 can be provided to different antennas 252 via individual transmitters 254TX. Each transmitter 254TX can modulate an RF carrier and transmit it with the corresponding spatial stream. UL transmission is processed at base station 210 in a manner similar to the reception function at UE 250. Each receiver 218RX receives the signal through its corresponding antenna 220. Each receiver 218RX recovers the information modulated onto the RF carrier and provides the information to RX processor 270.

[0041] Controller / processor 275 may be associated with memory 276, which stores program code and data. Memory 276 may be referred to as computer-readable medium. In the UL, controller / processor 275 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from UE 250. IP packets from controller / processor 275 may be provided to EPC 160. Controller / processor 275 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0042] New radio (NR) can refer to a radio configured to operate under a new air interface (e.g., in addition to the Orthogonal Frequency Division Multiple Access (OFDMA) air interface) or a fixed transport layer (e.g., in addition to Internet Protocol (IP)). NR can utilize OFDM with a cyclic prefix (CP) on both the uplink and downlink, and may include support for half-duplex operation using Time Division Duplex (TDD). NR may include enhanced mobile broadband (eMBB) services targeting wide bandwidth (e.g., exceeding 80 MHz), millimeter wave (mmW) services targeting high carrier frequencies (e.g., 60 GHz), massive MTC (mMTC) services targeting backward-incompatible MTC technologies, and / or mission-critical services targeting ultra-reliable low latency communication (URLLC) services.

[0043] It can support a single component carrier bandwidth of 100 MHz. In one example, NR resource blocks (RBs) can span 12 subcarriers with a subcarrier bandwidth of 60 kHz and a duration of 0.25 ms, or a bandwidth of 30 kHz and a duration of 0.5 ms (similarly, a 15 kHz SCS is a 50 MHz BW for a duration of 1 ms). Each radio frame can consist of 10 subframes (10, 20, 40, or 80 NR slots) with a length of 10 ms. Each slot can indicate the link direction of data transmission (i.e., DL or UL), and the link direction of each slot can be dynamically switched. Each slot can include DL / UL data as well as DL / UL control data. The UL and DL slots of NR can be defined as follows: Figure 5 and Figure 6 As described in more detail.

[0044] NR RAN can include central cells (CUs) and distributed cells (DUs). NR base stations (e.g., gNB, 5G NodeB, Node B, Transmitter Receiver Point (TRP), Access Point (AP)) can correspond to one or more base stations. NR cells can be configured as access cells (ACells) or data-only cells (DCells). For example, RAN (e.g., central cells or distributed cells) can configure cells. DCells can 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), and in others, they may transmit SS. NR base stations can send downlink signals to the UE indicating the cell type. Based on the cell type indication, the UE can communicate with the NR base station. For example, the UE can determine the NR base station based on the indicated cell type to consider for cell selection, access, handover, and / or measurement.

[0045] Figure 3 An example logical architecture of a distributed RAN 300 according to aspects of this disclosure is shown. A 5G access node 306 may include an access node controller (ANC) 302. The ANC may be the 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 the adjacent next-generation access node (NG-AN) 310 may terminate at the ANC. The ANC may include one or more TRPs 308 (also referred to as base stations, NR base stations, Node B, 5G NB, AP, or other terms). As mentioned above, TRP can be used interchangeably with "cell".

[0046] TRP 308 can be a distributed unit (DU). A TRP can be connected to one ANC (ANC 302) or multiple ANCs (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific ANC deployments, a TRP can be connected to multiple ANCs. A TRP can include one or more antenna ports. A TRP can be configured to provide traffic services to the UE individually (e.g., dynamically selected) or jointly (e.g., jointly transported).

[0047] The local architecture of the distributed RAN 300 can be used to illustrate the fronthaul definition. The architecture can define fronthaul solutions that support different deployment types. For example, the architecture can be based on transport network capabilities (e.g., bandwidth, latency, and / or jitter). The architecture can share features and / or components with LTE. Depending on the aspect, the next-generation AN (NG-AN) 310 can support dual connectivity with NR. The NG-AN can share a common fronthaul for LTE and NR.

[0048] This architecture enables cooperation between TRPs 308. For example, cooperation can be pre-defined within and / or across TRPs via ANC 302. Depending on various aspects, inter-TRP interfaces may be unnecessary or nonexistent.

[0049] Depending on various factors, the architecture of a distributed RAN 300 may involve dynamic configuration of segmentation logic functions. PDCP, RLC, and MAC protocols can be adaptively placed in the ANC or TRP.

[0050] Figure 4 An example physical architecture of a distributed RAN 400 according to various aspects of this disclosure is illustrated. A centralized core network unit (C-CU) 402 can host core network functions. The C-CU can be centrally deployed. C-CU functions can be offloaded (e.g., to advanced wireless services (AWS)) to handle peak capacity. A centralized RAN unit (C-RU) 404 can host one or more ANC functions. Optionally, the C-RU can host core network functions locally. The C-RU can be distributed. The C-RU may be located closer to the network edge. A distributed unit (DU) 406 can host one or more TRPs. The DU may be located at the network edge with radio frequency (RF) capabilities.

[0051] Figure 5Figure 500 illustrates an example of a DL center timeslot. The DL center timeslot may include a control section 502. The control section 502 may be present in the initial or beginning portion of the DL center timeslot. The control section 502 may include various scheduling and / or control information corresponding to different portions of the DL center timeslot. In some configurations, the control section 502 may be a physical DL control channel (PDCCH), such as... Figure 5 As shown. The DL center time slot may also include a DL data portion 504. The DL data portion 504 may sometimes be referred to as the payload of the DL center time slot. The DL data portion 504 may include communication resources for communicating DL data from a scheduling entity (e.g., a UE or BS) to a subordinate entity (e.g., a UE). In some configurations, the DL data portion 504 may be a Physical DL Shared Channel (PDSCH).

[0052] The DL center timeslot may also include a common UL portion 506. The common UL portion 506 may sometimes be referred to as a UL burst, a common UL burst, and / or various other suitable terms. The common UL portion 506 may include feedback information corresponding to other portions of the DL center timeslot. For example, the common UL portion 506 may include feedback information corresponding to the control portion 502. Non-limiting examples of feedback information may include ACK signals, NACK signals, HARQ indicators, and / or various other suitable types of information. The common UL portion 506 may include additional or alternative information, such as information related to the Random Access Channel (RACH) procedure, scheduling requests (SRs), and various other suitable types of information.

[0053] like Figure 5 As shown, the end of the DL data section 504 may be time-separated from the start of the common UL section 506. This time separation may sometimes be referred to as a gap, protection period, protection interval, and / or various other suitable terms. This separation provides the switching time from DL communication (e.g., reception operation of a subordinate entity (e.g., UE)) to UL communication (e.g., transmission of a subordinate entity (e.g., UE)). Those skilled in the art will understand that the above is merely one example of a DL central time slot, and alternative structures with similar characteristics may exist without departing from the various aspects described herein.

[0054] Figure 6 Figure 600 illustrates an example of a UL center time slot. A UL center time slot may include a control section 602. The control section 602 may be present at the beginning or start portion of the UL center time slot. Figure 6 The control section 602 in the reference may be similar to the one mentioned above. Figure 5The control portion 502 is described above. The UL center timeslot may also include a UL data portion 604. The UL data portion 604 may sometimes be referred to as the payload of the UL center timeslot. The UL portion may refer to the communication resources used for communicating UL data from a subordinate entity (e.g., UE) to a scheduling entity (e.g., UE or BS). In some configurations, the control portion 602 may be a physical DL control channel (PDCCH).

[0055] like Figure 6 As shown, the end of control section 602 may be time-separated from the start of UL data section 604. This time separation may sometimes be referred to as a gap, protection period, protection interval, and / or various other suitable terms. This separation provides the switching time from DL communication (e.g., receiving operations of a scheduling entity) to UL communication (e.g., transmissions of a scheduling entity). The UL central time slot may also include common UL section 606. Figure 6 The public UL section 606 in the reference above may be similar to the one mentioned above. Figure 5 The common UL portion 506 is described above. Common UL portion 606 may additionally or alternatively include information related to channel quality indicators (CQI), sounding reference signals (SRSs), and various other suitable types of information. Those skilled in the art will understand that the above is merely one example of a UL center slot, and alternative structures with similar features may exist without departing from the various aspects described herein.

[0056] In some cases, two or more dependent entities (e.g., user equipment (UE)) may communicate using sidelink signaling. Practical applications of such sidelink communication may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communication, Internet of Things (IoE) communication, Internet of Things (IoT) communication, mission-critical meshes, and a variety of other applicable applications. Typically, sidelink signaling may refer to signaling communication from one dependent entity (e.g., UE1) to another dependent entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., a UE or base station), even if the scheduling entity may be used for scheduling and / or control purposes. In some examples, sidelink signaling may use licensed spectrum for communication (unlike wireless LANs that typically use unlicensed spectrum).

[0057] Figure 7 This is a schematic diagram 700 illustrating a wireless communication system supporting unavailable cycles in a 5G network. In this example, UE 704 wirelessly communicates with base station 702, which is connected to network 710 containing components such as Access and Mobility Management Functions (AMF) 714.

[0058] In this example, UE 704 and AMF 714 in network 710 support unavailable periods. An unavailable period is a feature that allows a UE to inform the network of periods during which it is temporarily unavailable for communication. This feature is designed to improve network resource management and efficiency, particularly when a UE may experience predictable unavailable periods, such as when entering areas with discontinuous satellite coverage.

[0059] In this example, during registration procedure 732, UE 704 indicates its support for unavailable cycle features by including an "Unavailable Cycle Support" indication in the 5GMM core network capability field of the registration request message. This message is sent to AMF 714 via base station 702 during initial registration or mobility registration.

[0060] In response, AMF 714 indicates whether it supports the feature by including an "Unavailable Cycle Support" indication in the registration acceptance message sent back to UE 704. Thus, network 710 communicates its ability to handle unavailable information.

[0061] When an event is about to occur that renders UE 704 unusable, such as entering an area with discontinuous satellite coverage, UE 704 sends additional information to network 710 during the mobility registration update process or the UE-initiated deregistration process 734. This information includes: 1. an unavailability indication; 2. the type of unavailability; 3. the start time of the unavailability period (if known); and 4. the duration of the unavailability period (if known).

[0062] For example, if the current time is 1:00, UE 704 might notify network 710 that it will become unavailable at 2:00 (start time) for a duration of 3 hours. Network 710 uses this information to manage its resources and anticipate the availability of UE 704. For instance, AMF 714 might adjust the paging process or modify timer values ​​based on the known unavailability period of UE 704.

[0063] More specifically, when UE 704 sends unavailability information (including start time and duration) via mobility registration update or a UE-initiated deregistration procedure, AMF 714 receives and processes this information. Based on the received unavailability information, AMF 714 manages network resources. It may adjust various network parameters and procedures to account for upcoming UE unavailability periods. AMF 714 may modify timer values ​​based on known unavailability periods for UE 704. This may include adjusting the mobility reachability timer and implicit deregistration timer. AMF 714 may adjust the paging procedure based on the UE's unavailability information to optimize network efficiency.

[0064] However, in the first configuration, UE behavior is not explicitly defined in certain scenarios related to unavailable cycles. These scenarios include: 1. when UE 704 needs to indicate a previously unknown “start of unavailable cycle” to network 710; 2. when UE 704 determines that the impending loss of coverage (or the initiation of discontinuous coverage) is no longer applicable; 3. when the time / timestamp of the “start of unavailable cycle” changes; and 4. when the value of the duration of the unavailable cycle changes.

[0065] In this first configuration, once UE 704 initially notifies AMF 714 of the start and duration of the unavailability period during the update or deregistration procedure 734, there is no defined mechanism for UE 704 to update this information if it changes. For example, if UE 704 initially notifies network 710 that it will be unavailable starting at 2:00 PM for 3 hours, but later realizes that this information has changed, there is no standardized method in this configuration for UE 704 to communicate this updated information to AMF 714.

[0066] This undefined behavior creates a significant gap in the communication protocol between UE 704 and network 710. It could cause network 710 to operate based on outdated or incorrect information about UE 704 availability, potentially leading to inefficient resource allocation and degraded quality of service.

[0067] To address this issue, a new mechanism needs to be defined that allows UE 704 to perform the registration process to update network 710 with the latest unavailable information.

[0068] Therefore, in the second configuration, when UE 704 determines that coverage is about to be lost and is no longer applicable, or that the unavailability information becomes invalid, UE 704 performs registration procedure 736 (initial registration or mobility registration update), which does not include a "start of unavailability period" indication. Furthermore, or alternatively, UE 704 does not include the duration of the unavailability period when performing the registration procedure. By performing a registration procedure without unavailability information, UE 704 implicitly informs network 710 that it has exited the unavailability period and can resume normal service.

[0069] In the second configuration, when User Equipment (UE) 704 determines that coverage information about an impending loss has been modified, a new coverage loss has been detected, or the time has changed, UE 704 performs registration procedure 736 (initial registration or mobility registration update) using the latest value of the "start of unavailability period". Alternatively, UE 704 performs the registration procedure using the latest value of the duration of the unavailability period. This solution allows UE 704 to update network 710 with the latest information on its availability.

[0070] Therefore, the Access and Mobility Management Function (AMF) 714 processes this update information and adjusts its resource management and expectations accordingly. If the UE 704 does not include an "unavailable period start" or unavailable period duration during the registration process, the AMF 714 interprets this as the UE having exited the unavailable period and being able to resume normal service. During the registration process, the AMF 714 can determine the negotiated extended DRX parameter values ​​based on the unavailable period duration and unavailable period start. The AMF 714 can also set the values ​​of the mobile reachability timer and implicit deregistration timer based on the unavailable period duration and unavailable period start.

[0071] These features enable the AMF 714 to effectively manage network resources and maintain optimal communication with the UE when the UE 704 is expected to be unavailable for certain periods. The AMF's ability to process and act on updated unavailability information addresses the problem of outdated or incorrect information about UE availability, potentially improving resource allocation and quality of service in 5G networks.

[0072] As described above, for a 5G system, in one example, it can provide or update unavailability information to UE 704 during the mobility registration update process in the 5GMM-REGISTERED state. More specifically, UE 704 sends a registration request message containing updated values ​​to AMF 714. For example, if UE 704 previously indicated that it would be unavailable for 3 hours starting at 2:00 PM, but later determined that it would actually be unavailable for 2 hours starting at 3:00 PM, it can send a new registration request message containing these updated values.

[0073] In another example, if UE 704 determines that it will no longer be unavailable as previously indicated, it may send a registration request message during the initial registration process that does not include the start and / or duration of the unavailable period. The absence of these fields implicitly informs AMF 714 that UE 704 has exited an unavailable period or that the previously indicated unavailability no longer applies.

[0074] This mechanism in the second configuration provides a standardized way for UE 704 to communicate updated unavailability information to AMF 714, addressing the lack of defined behavior in the first configuration when unavailability information changes after the initial notification. It allows network 710 to operate based on up-to-date information about UE 704's availability, potentially improving resource allocation and quality of service in the wireless communication system.

[0075] Figure 8Figure 800 illustrates a wireless communication system supporting unavailable cycles in a 4G network. In this example, UE 804 wirelessly communicates with base station 802, which is connected to network 810 containing components such as Mobility Management Entity (MME) 814.

[0076] The Tracking Area Update (TAI) process is a mechanism in 4G LTE networks used to manage UE mobility and maintain network connectivity. This process can be initiated by the UE and serves multiple purposes, including informing the network of unavailable information or changes to unavailable information.

[0077] The tracking area update process in 4G networks can be extended to include features similar to those unavailable in 5G networks.

[0078] When UE 804 needs to notify network 810 of its unavailability or a change in its unavailability status in the 4G network, it initiates the Tracking Area Update procedure 832. This procedure allows UE 804 to send update information to MME 814 regarding: 1. the start time of the unavailability period; 2. the duration of the unavailability period; and 3. any changes to previously provided unavailability information.

[0079] This mechanism addresses the issue of undefined behavior when updating unavailability information after initial notification. By leveraging the tracking area update process, UE 804 in the 4G network can inform network 810 of its latest unavailability status, similar to the solution proposed for 5G networks.

[0080] For example, if UE 804 initially notifies network 810 that it will be unavailable for 3 hours starting at 2:00 PM, but later determines that this information has been changed, it can initiate a tracking area update process to provide updated information. This could include a new start time, a different duration, or even canceling the previously announced unavailability period.

[0081] By extending the tracking area update process to include unavailability information, 4G networks can benefit from improved resource management and more efficient UE unavailability handling, similar to the advantages offered by unavailability cycle features in 5G networks.

[0082] Furthermore, the LTE attach procedure can be extended to include unavailability information, similar to the modified tracking area update procedure described for 4G networks. This extension addresses the need for a standardized mechanism for communicating and updating unavailability information in LTE networks, similar to the unavailability periodicity feature in 5G networks.

[0083] In this extended LTE attach procedure 842, UE 804 may provide unavailability information to network 810 during the initial attach procedure or subsequent attach procedures. This information includes: 1. an unavailability indication; 2. an unavailability type (e.g., entering a coverage discontinuity area); 3. the start time of the unavailability period (if known); and / or 4. the duration of the unavailability period (if known).

[0084] UE 804 includes this information in the attach request message sent by base station 802 to MME 814. This allows UE 804 to notify network 810 of its impending unavailability at the earliest opportunity, thus enabling more efficient resource management.

[0085] When unavailability information changes after the initial attach, UE 804 can initiate a new attach procedure to update network 810. This addresses an issue identified in the initial configuration of the 5G network where no mechanism is defined to update unavailability information after the initial notification.

[0086] For example, if UE 804 initially indicates in attach procedure 842 that it will be unavailable for 3 hours starting at 2:00 PM, but later determines that this information has been changed, it can initiate a new attach procedure and update the information. UE 804 sends a new attach request message containing the revised unavailability details.

[0087] If UE 804 determines that it will no longer be unavailable as previously indicated, it can send an attach request message that does not contain unavailability information. The absence of this information implicitly informs MME 814 that UE 804 has exited an unavailability period or that the previously indicated unavailability no longer applies.

[0088] Upon receiving an attach request message containing unavailability information, the MME 814 processes this data and adjusts its resource management accordingly. This may include: 1. modifying timer values ​​based on the known unavailability period of the UE 804; 2. adjusting the paging process to optimize network efficiency; and / or 3. managing the allocation of network resources during the unavailability period of the UE 804.

[0089] By extending the LTE attach process in this way, 4G networks can benefit from improved UE unavailability handling, similar to the advantages offered by unavailability cycle features in 5G networks. This extension allows for more efficient use of network resources, better management of discontinuous coverage scenarios, and improved overall network performance in LTE systems.

[0090] Figure 9This is a flowchart 900 illustrating the method for updating unavailable cycles. This method can be performed by a UE (e.g., UE 704 or 804). In operation 902, the UE indicates support for the unavailable cycle feature in a registration request message during the initial registration process. In operation 904, the UE receives a registration acceptance message indicating whether the network supports the unavailable cycle feature.

[0091] In operation 906, the UE determines that the unavailability information has been changed. The unavailability information includes at least one of the start time or duration of the unavailability period. In some configurations, determining that the unavailability information has been changed includes at least one of the following: the information indicating impending coverage loss has been modified, new impending coverage loss has been detected, the impending coverage loss has been brought forward, or the impending coverage loss is no longer applicable.

[0092] In Operation 908, the UE performs a registration process with the network to provide updated unavailability information. In some configurations, the registration process includes at least one of the following: initial registration, mobility registration update, attach procedure, or tracking area update procedure. In some configurations, the unavailability information further includes the unavailability type.

[0093] In some configurations, performing the registration process includes sending a registration request message containing information elements that update the unavailability information. The registration request message includes at least one of the following: the latest value of the start time of the unavailability period, or the latest value of the duration of the unavailability period.

[0094] In some configurations, the UE determines that the unavailable information is no longer valid, and the registration process does not include at least one of the start of an unavailable period or the duration of an unavailable period.

[0095] In some configurations, the registration process is performed in a 5G network, and performing the registration process includes sending a registration request message to the access and mobility management functions. In some configurations, the registration process is performed in a 4G network, and performing the registration process includes initiating a tracking area update process. Initiating the tracking area update process includes sending a tracking area update request message to the mobility management entity.

[0096] In some configurations, the registration process is an attach process within the 4G network, and performing the registration process includes sending an attach request message to the network containing updated unavailability information. The attach request message includes at least one of the following: a latest value for the start time of the unavailability period, or a latest value for the duration of the unavailability period.

[0097] It should be understood that the specific order or hierarchy of boxes in the disclosed process / flowcharts is merely an illustration of exemplary methods. Based on design preferences, it should be understood that the specific order or hierarchy of boxes in the process / flowcharts may be rearranged. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in an exemplary order and are not intended to be limited to the specific order or hierarchy presented.

[0098] The above description is intended to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims should not be limited to the aspects shown herein, but should be given a consistent and complete scope by the language of the claims, wherein reference to a singular element does not mean “only one” unless otherwise specified, but rather “one or more.” The word “exemplary” as used herein means “as an example, instance, or illustration.” Any aspect described as “exemplary” is not necessarily to be construed as superior to other aspects. Unless otherwise specified, the term “some” means one or more. Phrases such as “at least one A, B, or C,” “one or more A, B, or C,” “at least one A, B, and C,” “one or more A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, phrases such as "at least one A, B, or C," "one or more A, B, or C," "at least one A, B, and C," "one or more A, B, and C," and "A, B, C, or any combination thereof" can be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described herein, whether known or subsequently known to those skilled in the art, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be made public, whether such disclosure is expressly stated in the claims. The terms "module," "mechanism," "element," "device," etc., may not be substitutes for the term "means." Therefore, unless an element expressly uses the phrase "means for," no claim element should be construed as means plus function.

Claims

1. A wireless communication method for a user equipment, comprising: It is determined that the unavailability information has been changed, wherein the unavailability information includes at least one of the start time of an unavailability period or a duration of the unavailability period; as well as Use the network to perform a registration process to provide information that is no longer available once updated.

2. The method of claim 1, wherein the registration process includes at least one of an initial registration process, a mobility registration update process, an attachment process, or a tracking area update process.

3. The method of claim 1, wherein determining that the unavailable information has been changed includes at least one of the following: It has been confirmed that information that was about to lose coverage has been modified; A new layer has been detected that is about to lose coverage. It was determined that a device was about to lose coverage and was brought forward; or It has been determined that the coverage is about to be lost and is no longer applicable.

4. The method of claim 1, wherein performing the registration process includes sending a registration request message containing an information element of the updated unavailability information.

5. The method of claim 4, wherein the registration request message includes at least one of the following: The latest value of the start time of the unavailable period; or The latest value of the duration of the unavailable period.

6. The method of claim 1, further comprising: The unavailable information is determined to be no longer valid, wherein the execution of the registration process does not include at least one of the start of the unavailable period or the duration of the unavailable period.

7. The method of claim 1, further comprising: During the initial registration process, a registration request message indicates support for an unavailable periodic feature.

8. The method of claim 7, further comprising: Receive a registration acceptance message that indicates whether the network supports the unavailable periodicity feature.

9. The method of claim 1, wherein the registration process is performed in a 5G network, and wherein performing the registration process includes sending a registration request message to an access and mobility management function.

10. The method of claim 1, wherein the registration process is performed in a 4G network, and wherein performing the registration process includes initiating a tracking area update process.

11. The method of claim 10, wherein initiating the tracking area update process includes sending a tracking area update request message to a mobility management entity.

12. The method of claim 1, wherein the unavailability information further includes an unavailability type.

13. The method of claim 1, wherein the registration process is an attachment process in a 4G network, and wherein performing the registration process includes: Send an attach request message to the network, the attach request message containing the updated unavailable information.

14. The method of claim 13, wherein the attach request message comprises at least one of the following: The latest value of the start time of that unavailable period, or The latest value of the duration of the unavailable period.

15. An apparatus for wireless communication, the apparatus being a user equipment, comprising: A memory; as well as At least one processor, coupled to the memory, is configured to: Determine that an unavailability information has been changed, wherein the unavailability information includes at least one of the start time of the unavailability period or a duration of the unavailability period; as well as Use the network to perform a registration process to provide information that is no longer available once updated.

16. The device of claim 15, wherein the registration process includes at least one of an initial registration process, a mobility registration update process, an attachment process, or a tracking area update process.

17. The device of claim 15, wherein, in order to determine that the unavailability information has been changed, the at least one processor is configured to perform at least one of the following: It has been confirmed that information that was about to lose coverage has been modified; A new layer has been detected that is about to lose coverage. It was determined that a device was about to lose coverage and was brought forward; or It has been determined that the coverage is about to be lost and is no longer applicable.

18. The apparatus of claim 15, wherein, in order to perform the registration process, the at least one processor is configured to send a registration request message containing an information element of the updated unavailable information.

19. The device of claim 18, wherein the registration request message includes at least one of the following: The latest value of the start time of the unavailable period; or The latest value of the duration of the unavailable period.

20. A computer-readable medium storing computer-executable code for wireless communication of a user equipment, including the code for: Determine that the unavailability information has been changed, wherein the unavailability information includes at least one of the start time of an unavailability period or a duration of the unavailability period; and Use the network to perform a registration process to provide updated, unavailable information.

Images