Paging and system information (SI) procedure under adjusted synchronization signal block measurement time configuration (SMTC) in non-terrestrial network (NTN)
By independently adjusting the configuration of reference signal and channel reception resources in user equipment (UE), the problems of propagation delay and measurement efficiency in satellite communications in LEO environment are solved, and more efficient battery life and measurement accuracy are achieved.
Patent Information
- Application Number
- CN202380034039.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-02-14
- Filing Date
- 2023-02-14
- Publication Date
- 2024-12-20
AI Technical Summary
In satellite communication, cell handover and long propagation delay problems caused by mobile satellites, especially in low-earth orbit (LEO) satellite environment, the existing technology is difficult to effectively manage propagation delay changes and cell measurement efficiency, which affects user equipment (UE) ) Battery life and measurement accuracy in idle/inactive mode.
By configuring the adjustment of reference signal (RS) and channel reception resources in the user equipment (UE), the measurement time and priority are automatically adjusted to meet the adjusted RS timing-channel reception resource proximity (ARCP) conditions, extending the measurement time or Adjust measurement priorities and optimize propagation delay and measurement efficiency in LEO environment.
Improves the battery life and measurement accuracy of UE in satellite communications in LEO environment, reduces power consumption, and improves adaptability and measurement efficiency to mobile cells.
Smart Images

Figure CN119174119A_ABST
Abstract
Description
Related Applications
[0001] This application claims the benefit of provisional patent application serial number 63 / 309,768, filed on February 14, 2022, the disclosure of which is hereby incorporated by reference in its entirety. Technical Field
[0002] The present disclosure relates to methods, devices, and systems for enabling satellite communications in a cellular network. Background Art
[0003] Satellite communications are experiencing a resurgence. Several satellite network plans have been announced over the past few years. Satellite networks can complement terrestrial mobile networks by providing connectivity and multicast / broadcast services to underserved areas.
[0004] To benefit from a strong mobile ecosystem and economies of scale, there is a great interest in adapting terrestrial radio access technologies including 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) and New Radio (NR) for satellite networks, which has been reflected in 3GPP standardization work.
[0005] In 3GPP Release 15, the first release of the Fifth Generation (5G) System (5GS) was specified. This is a new generation of radio access technology designed to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine type communications (mMTC). 5GS includes the NR access layer interface and the 5G Core network (5GC). The NR physical layer and higher layers reuse parts of the Long Term Evolution (LTE) specifications and add required components driven by new use cases. One such component is the introduction of a sophisticated framework for beamforming and beam management to extend the support of 3GPP technologies to frequency ranges beyond 6 gigahertz (GHz).
[0006] In Release 15, 3GPP started work on preparing NR for operation in non-terrestrial networks (NTN). This work was conducted in the study project "NR to support Non-Terrestrial Networks" and resulted in 3GPP Technical Report (TR) 38.811 (see, e.g., V15.4.0). In Release 16, work on preparing NR for operation in NTN networks continued with the study project "Solutions for NR to support Non-Terrestrial Network" (see 3GPP TR 38.821, e.g., V16.1.0). 1. Satellite characteristics
[0007] Satellite radio access networks typically include the following components: Satellite, which refers to a space platform. • Earth-based gateways that connect the satellite to a base station or core network, depending on the choice of architecture. Feeder link, which refers to the link between the gateway and the satellite • Access link or serving link, which refers to the link between the satellite and the UE.
[0008] Depending on the orbital altitude, satellites can be classified as low earth orbit (LEO), medium earth orbit (MEO) or geostationary earth orbit (GEO) satellites. LEO: Typical altitudes range from 250-1500 kilometers (km), with orbital periods ranging from 90-120 minutes. MEO: Typical altitudes range from 5,000 to 25,000 km, with orbital periods ranging from 3 to 15 hours. GEO: Altitude is about 35786 km, with an orbital period of 24 hours.
[0009] Satellite communication networks can be divided into two basic structures, depending on the functionality of the satellites in the system: Transparent Payload (also known as bent pipe architecture). The satellite forwards the received signal between the terminal and the network device on the ground, where only amplification and shifting from uplink frequency to downlink frequency is performed. When applied to the general 3GPP architecture and terminology, transparent payload architecture means that the next generation Node B (gNB) is located on the ground and the satellite forwards the signal / data between the gNB and the user equipment (UE). Regenerative payload. The satellite includes onboard processing to demodulate and decode the received signal and regenerate the signal before sending it back to Earth. When applied to the general 3GPP architecture and terminology, the regenerative payload architecture means that the gNB is located in the satellite.
[0010] In the work items for NRNTN in 3GPP Release 17, only the transparent payload architecture is considered.
[0011] Satellite networks or satellite-based mobile networks may also be referred to as non-terrestrial networks (NTNs). On the other hand, mobile networks with ground-based base stations may be referred to as terrestrial networks (TNs) or non-NTN networks. Satellites within NTNs may be referred to as NTN nodes, NTN satellites, or simply satellites.
[0012] Figure 1 An example architecture of a satellite network or NTN with bent pipe repeaters (i.e., a transparent payload architecture) is shown. A base station (e.g., gNB) can be integrated in the gateway or connected to the gateway via a terrestrial connection (wired, optical fiber, wireless link).
[0013] Communications satellites typically generate several beams over a given area. The footprint of a beam typically has an elliptical shape, which is traditionally considered a cell, but cells with multiple beams covering the footprint are not excluded in the 3GPP work. The footprint of a beam is typically referred to as a spot beam. The footprint of a beam may move over the surface of the Earth as the satellite moves, or may be fixed to the Earth by a beam pointing mechanism used by the satellite to compensate for satellite motion (where the latter may be referred to as a quasi-Earth-fixed beam or quasi-Earth-fixed cell). The size of a spot beam depends on the system design and may range from tens of kilometers to thousands of kilometers.
[0014] In LEO or MEO communication systems, a large number of satellites deployed in a series of orbits are required to provide continuous coverage across the globe. Launching a giant satellite constellation is an expensive and time-consuming process. Therefore, it is expected that all LEO and MEO satellite constellations will only provide partial earth coverage at a certain time. In the case of some constellations for large-scale Internet of Things (IoT) services with relaxed delay requirements, it may not even be necessary to support complete earth coverage. It may be sufficient to provide periodic coverage or occasional coverage according to the orbital period of the constellation.
[0015] 3GPP devices in RRC_IDLE or RRC_INACTIVE (RRC is Radio Resource Control) state need to perform multiple procedures, including measurements for mobility purposes, paging monitoring, logging of measurement results, tracking area updates, and searching for new public land mobile networks (PLMNs), to name a few. These procedures will consume power in the device, and the general trend in 3GPP is to allow relaxation of these procedures to extend device battery life. This trend is particularly evident in IoT devices that support reduced capacity (redcap), narrowband IoT (NB-IoT), and LTE machine type communication (LTE-M).
[0016] Propagation delay is an important aspect of satellite communications, which is different from the delay expected in land mobile systems. For bent-pipe satellite networks, the round-trip delay can range from tens of milliseconds in the case of LEO satellites to hundreds of milliseconds for GEO satellites, depending on the orbital altitude. For comparison, the round-trip delay in terrestrial cellular networks is typically less than 1 millisecond (ms).
[0017] The distance between the UE and the satellite can vary significantly, depending on the position of the satellite and therefore the elevation angle ε seen by the UE. Assuming a circular orbit, the minimum distance is achieved when the satellite is directly above the UE (ε = 90°), and the maximum distance is achieved when the satellite is at the minimum possible elevation angle. Table 1 shows the distance between the satellite and the UE for different orbital altitudes and elevation angles, as well as the one-way propagation delay and the maximum propagation delay difference (the difference from the propagation delay when ε = 90°). Note that this table assumes a regenerative payload architecture. For the case of a transparent payload, the propagation delay between the gateway and the satellite also needs to be considered, unless the base station corrects for this. Table 1: Propagation delays for different orbit altitudes and elevation angles.
[0018] Due to the high speeds of LEO and MEO satellites, propagation delays can also be highly variable and vary on the order of 10-100 microseconds (μs) per second, depending on orbit altitude and satellite speed. 2. SSB-MTC and the measurement gap
[0019] The NR synchronization signal (SS) consists of a primary SS (PSS) and a secondary SS (SSS). The NR physical broadcast channel (PBCH) carries very basic system information. In NR, the combination of SS and PBCH is called a synchronization signal block (SSB). Multiple SSBs are transmitted in a local burst set (i.e., an SS burst set). In an SS burst set, multiple SSBs can be transmitted in different beams. The transmission of SSBs within a local burst set is limited to a 5ms window. The possible set of SSB time positions in an SS burst set depends on a parameter set (numerology), which in most cases is uniquely identified by the frequency band. The SSB periodicity can be configured from a value set {5, 10, 20, 40, 80, 160} ms (where the unit used in the configuration is a subframe, which has a duration of 1ms).
[0020] The UE is not required to perform measurements at the same periodicity as the SSB periodicity. Therefore, SSB Measurement Time Configuration (SMTC) has been introduced for NR. Signaling of the SMTC window informs the UE of the timing and periodicity of the SSBs that the UE can use for measurements. The SMTC window periodicity can be configured from the value set {5, 10, 20, 40, 80, 160} ms, matching the possible SSB periodicity. The SMTC window duration can be configured from the value set {1, 2, 3, 4, 5} ms (where the unit used in the configuration is a subframe, which has a duration of 1 ms).
[0021] The UE can use the same radio frequency (RF) module to measure data transmission in neighboring cells and serving cells. The measurement gap allows the UE to suspend data transmission in the serving cell and perform measurements of neighboring cells. The measurement gap repetition period can be configured from the value set {20, 40, 80, 160} ms, and the gap length can be configured from the value set {1.5, 3, 3.5, 4, 5.5, 6, 10, 20} ms. Typically, the measurement gap length is configured to be greater than the SMTC window duration to allow RF retuning time. A measurement gap time advance is also introduced to fine-tune the relative position of the measurement gap with respect to the SMTC window. The measurement gap timing advance can be configured from the value set {0, 0.25, 0.5} ms.
[0022] Figure 2 An illustration of the SSB, SMTC window, and measurement gap is provided. 3 System Information (SI)
[0023] System information provides basic information to the UE, such as cell access information and common radio resource configuration. The UE is required to obtain the system information of a cell before attempting to access the cell.
[0024] System information consists of several information blocks. In NR, system information consists of a master information block (MIB) and one or more system information blocks (SIBs). Depending on the information type, there are several SIBs (e.g. SIB1, SIB2, ...).
[0025] Some system information may also be provided on demand, ie based on a request from the UE, eg based on a Random Access Channel (RACH) or Radio Resource Control (RRC), so an additional delay for requesting on-demand SI may occur before receiving the on-demand SI.
[0026] The MIB is transmitted on the PBCH at the SMTC periodicity (or SSB periodicity). The SMTC periodicity is configurable by the network, and it can be configured to be one of 5, 10, 20, 40, 80, and 160 ms. An example of MIB information is timing information about when to transmit the MIB. Examples of MIB information are: System Frame Number (SFN) The part of the SS / PBCH block (i.e. SSB) where the MIB is transmitted in the SS burst (the remaining SSB block index) SSB blocks are transmitted in the first half of the radio frame or the second half of the radio frame (half-frame timing) SIB1 scheduling information
[0027] The MIB Transmission Time Interval (TTI) or MIB periodicity is 80 ms. This means that the MIB information may change every 80 ms, except for the SFN. Since the SFN changes every 10 ms, the information bits corresponding to the SFN change depending on the transmitted SFN.
[0028] SIB1 is transmitted on the Physical Downlink Shared Channel (PDSCH) with a periodicity of 160ms (called the SIB1 transmission periodicity, or SIB1 TTI) and a variable transmission repetition periodicity within 160ms. The default transmission repetition periodicity for SIB1 is 20ms, but the actual transmission repetition periodicity depends on the network implementation, which means that the network can decide when it transmits SIB1. For SSB and Control Resource Set (CORESET) multiplexing mode 1, where the network transmits SSB and SIB1 at the same time but at different frequencies, the SIB1 repetition transmission periodicity is 20ms. For SSB and CORESET multiplexing modes 2 / 3, where the network transmits SSB and SIB1 at different times, the SIB1 transmission repetition periodicity is the same as the SSB periodicity (or SMTC periodicity). SIB1 includes information about the availability and scheduling of other SIBs (e.g., mapping of SIBs to SI messages, periodicity, SI window size), as well as an indication of whether one or more SIBs are provided only on demand, and in this case, the configuration required for the UE to perform the SI request. The PDSCH conveying SIB1 is scheduled by the physical downlink control channel (PDCCH) with the SI radio network temporary identifier (SI-RNTI). When the UE needs to obtain SIB1, the UE monitors the PDCCH with SI-RNTI at every possible SIB1 transmission opportunity. If the UE finds the PDCCH with SI-RNTI, the UE decodes the downlink control information (DCI) in the PDCCH and obtains the PDSCH scheduling information, such as resource block size, modulation, coding rate, and redundancy version.
[0029] The scheduling of other system information such as SIB2 or SIB3 is configured by the network, and the scheduling information is signaled in SIB1. Scheduling information for on-demand SIBs can be provided separately upon UE request. SIBs other than SIB1 (i.e., SIBx) are transmitted on PDSCH. Each SI message is transmitted within a periodically occurring time domain window (called the SI window or SI transmission periodicity). Each SI message is associated with an SI window, and the SI windows of different SI messages do not overlap. That is, within an SI window, only the corresponding SI message is transmitted. The SI message can be transmitted multiple times within the SI window.
[0030] The PDSCH conveying SIBx is scheduled by the PDCCH with SI-RNTI. When the UE needs to obtain SIBx, the UE monitors the PDCCH with SI-RNTI, which is scheduled by the PDCCH monitoring opportunity for SI messages (i.e., the PDCCH search space for SI). Note that one or more PDCCH monitoring opportunities may be scheduled within one SI window. If the UE finds the PDCCH, the UE decodes the downlink control information (DCI) in the PDCCH and obtains the PDSCH scheduling information, such as resource block size, modulation, coding rate, and redundancy version. 4. Monitor paging in idle / inactive mode
[0031] When the UE is in idle / inactive state, the UE monitors the PDCCH whose transmit opportunity is configured by the gNB in every discontinuous reception (DRX) cycle. The DRX cycle can be 320ms, 640ms, 1280ms and 2560ms. 3GPP Rel-17 extends DRX to enable longer DRX cycles, called extended DRX (eDRX). Using eDRX, it is possible to extend the DRX cycle up to 2.91 hours.
[0032] In NR, paging occasions are associated with SS bursts. There are two possible ways to multiplex SSBs and paging occasions (POs). ·SSB frequency domain multiplexing (FDMed) with PO SSB time domain multiplexing (TDMed) with PO
[0033] The length and periodicity of PDCCH monitoring in different modes are summarized in Table 2. Table 2. Summary of length and periodicity of PDCCH monitoring in different modes
[0034] The paging frame (PF) and the PO used for paging are determined by the following formula: The SFN of the PF is determined by the following formula: (SFN+PF_offset)mod T=(T divN)*(UE_ID modN) Index(i_s), indicates the index of PO, which is determined by the following formula: i_s=floor(UE_ID / N)modNs
[0035] If configured as specified in 3GPP TS 38.331 v16.7.0, the PDCCH monitoring occasions for paging are determined according to pagingSearchSpace as specified in 3GPP TS 38.213 v17.0.0 and firstPDCCH-MonitoringOccasionOfPO and nrofPDCCH-MonitoringOccasionPerSSB-InPO. When SearchSpaceId=0 is configured for pagingSearchSpace, the PDCCH monitoring occasions for paging are the same as those for RMSI as defined in clause 13 of 3GPP TS 38.213 v17.
[0036] When SearchSpaceId=0 is configured for pagingSearchSpace, Ns is 1 or 2. For Ns=1, there is only one PO starting from the first PDCCH monitoring occasion of paging in PF. For Ns=2, the PO is located in the first half frame (i_s=0) or the second half frame (i_s=1) of PF.
[0037] When a SearchSpaceId other than 0 is configured for pagingSearchSpace, the UE monitors the (i_s+1)th PO. PO is a set of "S*X" consecutive PDCCH monitoring opportunities, where "S" is the number of actually transmitted SSBs determined according to ssb-PositionsInBurst in SIB1, and X is nrofPDCCH-MonitoringOccasionPerSSB-InPO (if configured), or equal to 1 otherwise. The [X*S+K]th PDCCH monitoring opportunity for paging in PO corresponds to the Kth transmitted SSB, where x=0, 1, ..., X-1, K=1, 2, ..., S. Starting from the first PDCCH monitoring opportunity for paging in PF, the PDCCH monitoring opportunities for paging that do not overlap with UL symbols (determined according to tdd-UL-DL-ConfigurationCommon) are numbered sequentially starting from zero. When firstPDCCH-MonitoringOccasionOfPO exists, the starting PDCCH monitoring opportunity number of the (i_s+1)th PO is the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter; otherwise, it is equal to i_s*S*X. If X>1, when the UE detects a PDCCH transmission addressed to the P-RNTI within its PO, the UE does not need to monitor the subsequent PDCCH monitoring opportunities of the PO.
[0038] When the UE is in the CampedNormally state or the Campedon Any Cell state on a cell, the UE shall attempt to detect, synchronize and monitor the intra-frequency, inter-frequency and inter-radio access technology (inter-RAT) cells indicated by the serving cell. For intra-frequency and inter-frequency cells, the serving cell may not provide an explicit neighbor list, but only carrier frequency information and bandwidth information. UE measurement activities are also controlled by the measurement rules defined in 3GPP TS 38.304v16.7.0, allowing the UE to limit its measurement activities.
[0039] In idle / inactive mode, the UE will wake up only for a limited time to perform AGC re-tuning, monitor paging occasions, perform intra-frequency measurements and inter-frequency measurements, such as Figure 3 shown. 5. Paging measurement relaxation 5.1 Measurement and evaluation of serving cells
[0040] The UE shall measure the SS reference signal received power (SS-RSRP) and SS reference signal received quality (SS-RSRQ) levels of the serving cell and evaluate the cell selection criterion S defined in TS 38.304v16.7.0 for the serving cell at least once every M1*N1 DRX cycle; where: If SMTC cycle rate (TSMTC) > 20ms and DRX cycle ≤ 0.64 seconds, then M1 = 2, Otherwise M1=1.
[0041] The UE uses at least two measurements to filter the SS-RSRP and SS-RSRQ measurements of the serving cell. Within a set of measurements used for filtering, at least two measurements are separated by at least DRX cycle / 2.
[0042] If the UE has evaluated in Nserv continuous DRX cycles according to Table 3 that the serving cell does not satisfy the cell selection criterion S, the UE initiates measurement of all neighboring cells indicated by the serving cell, regardless of the measurement rules currently restricting the UE's measurement activity.
[0043] If the UE in RRC_IDLE does not find any new suitable cell based on searching and measuring for 10 seconds using intra-frequency, inter-frequency and inter-RAT information indicated in the system information, the UE initiates the cell selection procedure for the selected PLMN as defined in 3GPP TS 38.304 v16.7.0. Table 3: N serv 5.2 Intra-frequency cell measurement and evaluation
[0044] The UE shall not discard PO regardless of whether PO and SSB occur in the same time resource or when they are close to each other in time. However, in this case, under certain conditions, such as when PO and SSB are 20ms or more apart, the measurement time is extended by a factor of 1.5 for DRX cycle = 0.32 seconds. Table 4: T detect,NR_Intra , T measure,NR_Intra and T evaluate,NR_Intra Summary of the invention
[0045] Methods, devices, and computer-readable media for configuring a user equipment (UE) to perform measurements of reference signals (RS) transmitted by a cell served or managed by a satellite node (also referred to herein as a non-terrestrial network (NTN) node) are disclosed. In some embodiments, a method performed by a UE for a wireless access network includes determining whether the UE satisfies one or more adjusted RS timing-channel reception resource proximity (ARCP) conditions for RS timing (RSO) and channel reception resource (CRR). The method also includes performing one or more operational tasks based on whether the UE satisfies the one or more ARCP conditions for RSO and CRR. In some embodiments, performing the one or more operational tasks includes adapting at least one measurement scaling factor to a measurement time to extend the measurement time. Certain embodiments provide one or more technical advantages, including enhancements regarding tradeoffs in flexibility, and details and methods for implementing specific configurations.
[0046] In some embodiments, determining whether the UE satisfies the one or more ARCP conditions for RSO and CRR includes determining whether the UE satisfies the one or more ARCP conditions for RSO and CRR based on one or more rules.
[0047] In some embodiments, the one or more ARCP conditions include: (a) a condition that the RSO overlaps or partially overlaps with the CRR in time, (b) a condition that the time distance between the RSO and the CRR is within a first predetermined or configured threshold, (c) a condition that the time distance between the RSO and the CRR is not greater than a second predetermined or configured threshold, (d) a condition that the magnitude of a difference between the RSO start time or the RSO end time of the RSO and the CRR start time or the CRR end time of the CRR is less than or equal to a third predetermined or configured threshold, or (e) a combination of any two or more of (a)-(d).
[0048] In some embodiments, performing the one or more operating tasks based on whether the UE satisfies the one or more ARCP conditions for RSO and CRR includes: if the UE does not satisfy the one or more ARCP conditions for RSO and CRR, performing at least one operating task in a first set of operating tasks; and if the UE satisfies the one or more ARCP conditions for RSO and CRR, performing at least one operating task in a second set of operating tasks. In some embodiments, the second set of operating tasks includes transmitting information about the adjustment of RSO to the network node, and transmitting information that the one or more ARCP conditions for RSO and CRR are satisfied to the network node. In some embodiments, the first set of operating tasks includes performing or continuing to perform measurements during RSO, or receiving or monitoring one or more channels during CRR, even if RSO is adjusted. In some embodiments, the second set of operational tasks includes: (i) not performing or continuing to perform measurements during the RSO, (ii) receiving or monitoring one or more channels during the CRR, (iii) stopping adjusting the RSO or deferring the adjustment of the RSO for a certain period of time, (iv) prioritizing channel reception during the CRR over performing measurements during the adjusted RSO, or vice versa, depending on the type of CRR, (v) prioritizing performing measurements during the RSO over receiving paging during the CRR, (vi) prohibiting receiving or monitoring a certain channel in the Gt number of continuous channel reception resources up to the G1 number of channel reception resources, (vii) prohibiting receiving or monitoring a certain channel in the G1 number of channel reception resources during a certain period of time, (viii) adapting one or more measurement requirements, (ix) extending the measurement time of measurements that the UE cannot perform in one or more adjusted RSOs; or (x) any combination of two or more of tasks (i)-(ix). In some embodiments, receiving or monitoring the one or more channels during the CRR includes receiving paging or receiving system information (SI).
[0049] In some embodiments, the UE obtains a first set of operation tasks or a second set of operation tasks based on one or more rules. In some embodiments, the one or more rules include: (i) even if the adjusted or shifted RSO is within Z1 time resources before the paging opportunity or within Z2 time resources after the paging opportunity, the UE also receives paging, (ii) even if the adjusted or shifted RSO partially or completely overlaps with the paging opportunity, the UE also receives paging, (iii) even if the adjusted or shifted RSO is within Z3 time resources before the SI reception opportunity or within Z4 time resources after the SI reception opportunity, the UE also receives system information (SI); or (iv) even if the adjusted or shifted RSO partially or completely overlaps with the SI reception opportunity, the UE also receives SI. In some embodiments, the adjusted or shifted RSO includes a synchronization signal block (SBB) measurement timing configuration (SMTC) opportunity. In some embodiments, the SI includes a master information block (MIB), a system information block 1 (SIB1), or other system information blocks (SIBs).
[0050] In some embodiments, the wireless access network is a non-terrestrial network (NTN).
[0051] Corresponding embodiments of a UE are also disclosed. In some embodiments, the UE includes a transmitter circuit and a processing circuit associated with the transmitter circuit. The processing circuit is configured to cause the UE to determine whether the UE satisfies one or more ARCP conditions for RSO and CRR. The processing circuit is further configured to perform one or more operational tasks based on whether the UE satisfies the one or more ARCP conditions for RSO and CRR. In some embodiments, performing the one or more operational tasks includes adapting at least one measurement scaling factor to a measurement time to extend the measurement time.
[0052] In some other embodiments, a non-transitory computer readable medium having code stored thereon, which when executed causes a processor to perform a method as disclosed herein. BRIEF DESCRIPTION OF THE DRAWINGS
[0053] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.
[0054] Figure 1 An example architecture of a satellite network with bent pipe repeaters is shown.
[0055] Figure 2 is a timing diagram showing examples of a synchronization signal block (SSB), an SSB measurement time configuration (SMTC) window, and a measurement gap.
[0056] Figure 3is an example timing diagram illustrating when a user equipment (UE) in idle / inactive mode will wake up to perform automatic gain control (AGC) retuning, monitor paging occasions, perform intra-frequency measurements, and perform inter-frequency measurements.
[0057] Figure 4 An example of a wireless communication system in which embodiments of the present disclosure may be implemented is shown.
[0058] Figure 5 is a timing diagram showing an example of multiple SMTC configurations per measurement object (MO) or per frequency layer transmitted / configured by the network in a cell.
[0059] Figure 6 is a timing diagram illustrating an example of a reference scenario, where a UE is configured with a reference signal (RS) configuration (e.g., an SMTC configuration) that includes periodic RS opportunities and at least one set of periodic channel reception resources (CRRs).
[0060] Figure 7 is a timing diagram illustrating an example RS configuration (eg, SMTC configuration) including periodic RS opportunities and periodically configured channel reception resources.
[0061] Figure 8 is a timing diagram illustrating an example RS configuration (eg, SMTC configuration) including periodic RS occasions and periodically configured channel reception resources (eg, paging occasions).
[0062] Fig. 9 Examples of procedures performed by a UE according to some example embodiments are shown.
[0063] Fig.10 A timing diagram illustrating Paging Occasion (PO) monitoring, AGC measurement, and PO Time Division Multiplexing (TDM) relative to SSB is shown.
[0064] Fig.11 Another timing diagram illustrating PO monitoring, AGC measurement and PO TDM relative to SSB is shown.
[0065] Fig.12 A timing diagram illustrating PO monitoring, AGC measurement, and PO frequency division multiplexing (FDM) relative to SSB is shown.
[0066] Fig.13 An example of a communication system in accordance with some embodiments is shown.
[0067] Fig.14 A UE according to some embodiments is shown.
[0068] Fig.15A network node according to some embodiments is shown.
[0069] Fig.16 A block diagram of a host according to some embodiments is shown.
[0070] Fig.17 Shown is a block diagram illustrating a virtualized environment in accordance with some embodiments.
[0071] Fig.18 A communication diagram is shown in which a host communicates with a UE via a network node over a partially wireless connection according to some embodiments. DETAILED DESCRIPTION
[0072] The embodiments set forth below represent information that enables those skilled in the art to implement the embodiments, and illustrate the best mode of implementing the embodiments. When reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure, and will recognize that the application of these concepts is not particularly presented herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.
[0073] In this disclosure, the term "satellite" is often used, even when a more appropriate term would be "network node associated with a satellite (e.g., gNB)". The term "satellite" may also be referred to as a satellite node, a non-terrestrial network (NTN) node, a space node, etc. Here, a network node associated with a satellite (e.g., gNB) may include both a regenerative satellite (where the network node is the satellite payload, i.e., the network node is integrated with the satellite) or a transparent satellite (where the satellite payload is a relay and the network node is on the ground (i.e., the satellite relays communications between the network node on the ground and the user equipment (UE))).
[0074] The period of time or duration during which a UE can maintain a connection with a satellite or a network node (e.g., a gNB), or can camp on it, or can maintain communication with it, etc. is referred to as the term "coverage time" or "service time" or "network availability" or "dwell time" or "dwell time", etc. The term "non-coverage time", also known as "non-service time" or "network unavailability", or "non-dwell time" or "non-dwell time", refers to the period of time during which a satellite or network node cannot serve the UE or communicate with the UE or provide coverage to the UE. Another way to interpret availability is not about the satellite / network being strictly unable to serve the UE due to lack of coverage, but that the UE does not need to measure certain "unlikely serving cells (via which satellites broadcast serving cells)". In this case, the terminology may still be the same as for the no coverage case, or it may also be different, such as "no measurement required".
[0075] The term node used may be a network node or a UE. Examples of network nodes include Node B, base station (BS), multi-standard radio (MSR) radio node such as MSRBS, eNodeB (eNB), gNodeB (gNB), MeNB, SeNB, location measurement unit (LMU), integrated access backhaul (IAB) node, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlled relay, base transceiver station (BTS), central unit (e.g. in gNB), distributed unit (e.g. in gNB), baseband unit, centralized baseband, C-RAN, access point (AP), transmission point, transmission node, transmission reception point (TRP), RRU, RRH, node in distributed antenna system (DAS), core network node (e.g. MSC, MME, etc.), O&M, OSS, SON, positioning node (e.g. E-SMLC), etc.
[0076] The non-limiting term "UE" refers to any type of wireless device that communicates with a network node and / or with another UE in a cellular or mobile communication system. Examples of UEs are target devices, device-to-device (D2D) UEs, vehicle-to-vehicle (V2V), machine-type UEs, MTC UEs, or UEs capable of machine-to-machine (M2M) communication, PDAs, tablets, mobile terminals, smart phones, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, etc.
[0077] The term radio access technology or RAT may refer to any RAT, such as UTRA, E-UTRA, Narrowband Internet of Things (NB-IoT), WiFi, Bluetooth, Next Generation RAT, New Radio (NR), 4G, 5G, NR NTN, IoT NTN, LTE NTN, etc. Any device denoted by the term node, network node or radio network node may be capable of supporting a single or multiple RATs.
[0078] Embodiments are described using the general terms of downlink (DL) reception or DL signal reception and uplink (UL) transmission or UL signal transmission. DL reception may include the reception of one or more DL signals. Examples of DL signals are physical DL channels and DL physical signals. Physical channels (DL or UL) may carry higher layer information, such as control, data, etc. Examples of DL physical channels are PDSCH, physical downlink control channel (PDCCH), physical broadcast channel (PBCH), control resource set (CORSET), etc. Examples of physical signals (DL or UL) are reference signals (also referred to as pilot signals, training sequences, etc.). Examples of DLRS are PSS, SSS, SSB, CSI-RS, PRS, TRS, DMRS, reference signals (e.g., primary synchronization signal (PSS), secondary synchronization signal (SSS), demodulation reference signal (DMRS) within SSB, etc.). Similarly, UL transmission may include physical UL channels or signals. Examples of UL physical channels are physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH), SR, etc. Examples of UL RS are DMRS, Sounding Reference Signal (SRS), etc. When DL reception or UL transmission is described as dynamically scheduled or semi-statically configured, it may therefore cover all mentioned physical channels and signals.
[0079] The term "signal" or "radio signal" used in this document can be any physical signal or physical channel. Examples of DL physical signals are reference signals (RS), such as PSS, SSS, channel state information reference signal (CSI-RS), DMRS signals in SS / PBCH blocks (SSBs), discovery reference signals (DRS), CRS, PRS, etc. RS can be periodic, for example, RS opportunities carrying one or more RSs can appear at a certain periodic rate (e.g., 20ms, 40ms, etc.). RS can also be non-periodic. Each SSB carries NR-PSS, NR-SSS and NR-PBCH in 4 consecutive symbols. One or more SSBs are transmitted in an SSB burst that is repeated at a certain periodic rate, such as 5ms, 10ms, 20ms, 40ms, 80ms and 160ms. The UE is configured with information about SSBs on a cell of a certain carrier frequency through one or more SS / PBCH block measurement timing configuration (SMTC) configurations. The SMTC configuration includes parameters such as SMTC periodicity, SMTC opportunity time length or duration, SMTC time offset relative to a reference time (e.g., the system frame number (SFN) of the serving cell), etc. Therefore, SMTC opportunities may also occur at a certain periodicity (e.g., 5ms, 10ms, 20ms, 40ms, 80ms, and 160ms). Examples of UL physical signals are reference signals such as SRS, DMRS, etc. The term physical channel refers to any channel that carries higher layer information (e.g., data, control, etc.).
[0080] The term "time resource" as used herein may correspond to any type of physical resource or radio resource expressed in terms of a length of time. Examples of time resources are: symbol, sub-slot, mini-slot, time slot, subframe, radio frame, transmission time interval (TTI), interleaving time, frame, SFN cycle, super SFN (H-SFN) cycle, etc.
[0081] Some challenges that need to be addressed in non-terrestrial networks (NTNs) include moving satellites resulting in moving cells or handovers, and long propagation delays. These challenges are further detailed below.
[0082] Moving satellites result in moving or switching cells: The default assumption in terrestrial network design, such as New Radio (NR) or Long Term Evolution (LTE), is that the cells are fixed. This is not the case for NTN, especially when considering low earth orbit (LEO) satellites. LEO satellites may be visible to UEs on the ground for only a few seconds or minutes. There are two different options for LEO deployment. With earth-fixed beams, the beam / cell coverage is fixed with respect to the geographic location, i.e., a steerable beam at the satellite ensures that a certain beam covers the same geographic area even if the satellite moves with respect to the earth's surface. On the other hand, with mobile beams, LEO satellites have fixed antenna pointing with respect to the earth's surface, e.g., perpendicular to the earth's surface, and therefore the cell / beam coverage sweeps across the earth as the satellite moves. In that case, the spot beam serving the UE may be switched every few seconds.
[0083] Long propagation delay: The propagation delay of land mobile systems is typically less than 1 millisecond. In contrast, the propagation delay of NTNs can be much longer, ranging from a few milliseconds (LEO) to hundreds of milliseconds (geostationary orbit (GEO)), depending on the altitude of the space or space platform where the NTN is deployed.
[0084] In a terrestrial network (TN), the relative time positions of the synchronization signal blocks (SSBs) between the serving cell and the neighboring cells are fixed. The propagation delay within each cell depends on the cell size and the UE location, and from the UE's perspective it will only change due to UE movement.
[0085] In contrast, in the NTN scenario for LEO, even the propagation delay between the UE and the serving cell will vary over time due to the movement of the satellite. In addition, the propagation delay towards neighboring cells on neighboring satellites will also vary over time. The situation may become even worse when the feeder link delay is taken into account and will increase with the increase in satellite altitude.
[0086] The maximum SSB Measurement Time Configuration (SMTC) window duration is 5 subframes, and thus a statically configured window may not be able to handle the variations in propagation delays in the NTN. Since the Radio Layer 2 (RAN2) has agreed that the UE does not need to monitor SSBs outside the configured SMTC window, it makes measurements on neighboring cells in the NTN, which presents a challenge to the current SMTC configuration options, at least for (semi-)static SMTC configurations.
[0087] Furthermore, different satellites are not necessarily time synchronized (in the sense that they use the same timing), they are frame synchronized and transmit their SSBs at the same position in the frame, unlike neighboring cells from the same satellite which can be easily synchronized. Therefore, the configuration of the SMTC and measurement gaps as part of the SSB search and overall synchronization process should at least also take into account this situation and the potential time offset between satellites. For the SMTC window and gap configuration towards the UE, the time offset introduced in the SSB transmission between different cells also needs to be taken into account.
[0088] The following are the issues and agreements regarding SMTC in the RAN2 meeting: RAN2#113bis and RAN2#115 agree that the maximum number of SMTCs in one measurement object is 4. In addition to the traditional SMTC configuration, it is also agreed that multiple SMTC configurations can be implemented by introducing different new offsets. Agreement - via email (from offline
[106] @113bis) - In addition to the traditional SMTC configuration, multiple SMTC configurations are enabled by introducing different new offsets. How will FFS manage / signal the offsets. Agreement via email - from offline 112@115: 1. In a measurement object with the same ssbFrequency, the specific maximum number of SMTC configurations can be 4. And a LS will be sent to RAN4 to confirm the conclusion. • In RAN2#116-e, it was agreed to support a UE-based solution for SMTC adjustment in NTN for idle / inactive UEs. How the UE performs the necessary shift in SMTC is a future study. • In RAN2#116bis-e, the shift in SMTC was discussed and almost agreed. Proposal 18: (16 / 20) A UE-based solution for SMTC adjustment, where the UE autonomously adjusts the SMTC based on location and ephemeris.
[0089] The explanation can be summarized as follows: the network node transmits information about at least two SMTC configurations for each measurement object (e.g., each carrier frequency and / or a group of cells) to one or more UEs in the cell. The UE determines and adjusts one or more SMTC configurations received in the cell (e.g., in the serving cell) based on one or more criteria, such as an offset of the SMTC, and performs one or more operational tasks, such as performing one or more measurements on one or more cells, etc.
[0090] However, the impact of the UE autonomously applying SMTC shift on the operation of other signals is not defined. This can reduce the overall performance of UE operation in the NTN network. This paper discloses a solution to this problem.
[0091] Certain aspects of the present disclosure and its embodiments may provide solutions to the aforementioned problems and / or other challenges. Embodiments are applicable to scenarios in which a UE is configured to perform one or more measurements on a reference signal (RS) (e.g., SSB) transmitted by one or more cells, which are served or managed by their corresponding satellite nodes (also referred to herein as NTN nodes). The time-frequency resources containing the RS are determined by the RS configuration (e.g., SMTC configuration). The UE is configured by a network node (e.g., a base station, such as, for example, a gNB) with information that enables the UE to identify the RS configuration. The satellite node may move relative to the UE position over time. Therefore, in order to perform or continue to perform measurements on the RS, the UE is also configured to autonomously adjust or modify at least one parameter related to the RS configuration. Examples of adjustments to parameters related to the RS configuration are shifting the RS opportunity or window (e.g., SMTC opportunity or window) in time by a certain margin (e.g., by applying a time offset greater than a configured time offset value, etc.), changing the duration of the RS opportunity or window (e.g., SMTC opportunity or window), etc.
[0092] According to an embodiment, the UE determines whether the UE satisfies at least one adjusted RS opportunity-channel reception resource proximity (ARCP) condition, and performs one or more operation tasks, which depends on whether the UE satisfies at least one ARCP condition. The (one or more) operation tasks may also depend on the type of RS adjusted and / or the type of channel received or expected to be received by the UE. In one embodiment, the ARCP condition defines the timing relationship between the timing of the adjusted RS opportunity and the timing of the channel reception resource. In one example, if the adjusted RS opportunity and the channel reception resource overlap at least partially in time, the UE satisfies at least one ARCP condition. In another example, even if the adjusted RS opportunity and the channel reception resource are close in time (e.g., within a certain time margin) but do not overlap in time, the UE satisfies at least one ARCP condition. Examples of channel reception resources are paging reception resources (PRR) (e.g., paging monitoring opportunities, etc.), broadcast channel resources (e.g., physical channels that transmit master information blocks (MIBs) (e.g., physical broadcast channels (PBCHs)), physical channels that transmit one or more system information blocks (SIBs) (e.g., physical downlink shared channels (PDSCHs)), etc.), etc. Examples of operation tasks are: In one example of the (one or more) operational tasks, if at least one ARCP condition is met, the UE does not perform measurement during the adjusted RS opportunity, but instead receives a channel (e.g., receives paging) in a channel reception resource. In this case, the UE may further adjust the measurement process, for example, when the UE does not perform measurement in the RS opportunity, extend the measurement time. For example, the UE may adjust at least one measurement scaling factor, or apply a new measurement scaling factor to the measurement time to extend the measurement time. In another example of an operation task, if the ARCP condition is not satisfied, the UE may perform measurement during the adjusted RS opportunity. In this case, the UE may also receive the channel in the channel reception resource.
[0093] Some embodiments of the present disclosure relate to a set of mechanisms and procedures for a UE in an NTN to perform measurements using, for example, an SMTC configuration.
[0094] Certain embodiments may provide one or more of the following technical advantages(s), including enhancements in the trade-off between flexibility and explicit details and methods for implementing a particular configuration.
[0095] Figure 4 An example of a wireless communication system 400 in which embodiments of the present disclosure may be implemented is shown. As shown, the wireless communication system 400 includes an NTN or satellite-based radio access network (e.g., 3GPP NR NTN) that includes satellites 402 (which may alternatively be referred to herein as, for example, NTN nodes) and one or more gateways 404 that interconnect the satellites 402 to land-based base stations 406. In this example, a UE 408 communicates with the satellite radio access network via the satellites 402. Note that the wireless communication system 400 is only an example of a wireless communication system that utilizes an NTN for radio access. The embodiments disclosed herein are equally applicable to any such system.
[0096] Embodiments of the present disclosure may relate to the following scenario. The scenario includes a UE (e.g., UE 408) configured to perform one or more measurements on a reference signal (RS) transmitted by one or more cells operated or managed by a network node (e.g., a satellite node (e.g., satellite 402)). The UE may also be configured to be in a low activity RRC state. Examples of low activity RRC states are RRC idle states, RRC inactive states, and the like. In order to help the UE perform measurements, the network node configures the UE with information related to RS configuration, for example, via RRC signaling. The RS configuration information may be part of a measurement object (MO). Typically, the RS configuration includes one or more parameters, such as an RS index or identifier (e.g., RS1), RS duration or timing or window, RS periodicity, and time offset, and the like. Examples of RS are SSB, CSI-RS, and the like. Examples of RS configurations are SMTC configurations, CSI-RS configurations, and the like. Each SMTC configuration transmitted to the UE in the MO is associated with a corresponding SMTC parameter, such as an SMTC index or identifier (e.g., SMTC1), SMTC duration, SMTC periodicity, and time offset, and the like. In the case where SMTC1, SMTC2, SMTC3 and SMTC4 indicate the indexes or identities of multiple SMTCs configured by the network, they may also be referred to as RRC IE parameters.
[0097] Figure 5 An example is depicted in which 4 SMTC configurations per MO (measurement object) or per frequency layer are transmitted / configured by Network 1 in a cell (e.g., Cell 1). In the case where the timing of SMTC is not specifically defined for a dedicated UE, such as in the RRC_IDLE state, the UE needs to autonomously adjust the SMTC with optional support from network assistance information. This implies that the actual timing of the SMTC windows of different UEs is not necessarily the same. Figure 5 The example in shows two UEs (UE1 and UE2) having different SMTC window timings after determination at the UE side even though they are signaled the same SMTC configuration by the network.
[0098] In an embodiment of the present disclosure, when the UE 408 determines more than one SMTC, when the paging occasion (PO) is TDM or FDM relative to the SSB position, the UE 408 does not discard any paging and / or system information due to SSB-based measurements. Radio Resource Management (RRM) measurement requirements in RRC idle / inactive state may be affected due to paging reception, which depends on at least the following parameters: DRX cycle length and / or SMTC period.
[0099] Figure 6An example of a reference scenario is shown, where the UE 408 is configured with an RS configuration (e.g., an SMTC configuration) that includes periodic RS opportunities and at least one set of periodic channel reception resources (CRRs) with a TCRR periodicity. The RS configuration also includes a set of periodic RS opportunities (e.g., paging opportunities) with a TRSO periodicity. In the reference scenario, the UE 408 does not adjust or shift or modify any parameters of the configured RS configuration.
[0100] Figure 7 An example RS configuration (e.g., SMTC configuration) is shown, which includes periodic RS opportunities and periodically configured channel reception resources (e.g., paging opportunities), wherein several RS opportunities are adjusted. The adjustment includes extending the RSO duration. In other words, Figure 7 Another exemplary scenario is shown in which the UE 408 autonomously adjusts or shifts or modifies at least one parameter (e.g., RS timing (RSO)) of the configured RS configuration (e.g., SMTC configuration). More specifically, the UE 408 timely adjusts or shifts RSO2, RSO3, and RSO4. In this example, the adjustment of the RSO includes extending the duration of the RSO, such as from 5ms to 8ms, etc. In this example, the start time of the RSO is the same as that configured by the network node. Therefore, the duration of the RSO is also extended compared to the duration of the RSO configured by the network. The following observations are made: 1. The difference between the end of RSO2 in time and the start of CRR3 in time is greater than a certain threshold (H). 2. The difference between the end of RSO3 in time and the start of CRR4 in time is less than H. 3. The onset of RSO4 and CRR5 overlap at least partially in time.
[0101] Figure 8 An example of an RS configuration (e.g., SMTC configuration) is shown, which includes periodic RS opportunities and periodically configured channel reception resources (e.g., paging opportunities), where several RS opportunities are adjusted. The adjustment includes shifting the RSO in time. In other words, Figure 8Still another exemplary scenario is shown, in which the UE 408 autonomously adjusts or shifts or modifies at least one parameter (e.g., RS timing (RSO)) of the configured RS configuration. More specifically, the UE 408 also adjusts or shifts RSO2, RSO3, and RSO4 in time. However, in this example, the adjustment of the RSO only includes shifting the RSO in time relative to a reference time (Tr), for example, by 3 ms relative to Tr. In one example, Tr can be represented according to an absolute time, such as a universal clock (e.g., UTC). In another example, Tr can be represented according to a time resource number or a counter, such as a subframe number, a time slot number, a system frame number (SFN), a super SFN, etc. For example, how much the RSO is shifted compared to a Tr including SFN #X1 and a subframe number #X2. Examples of X1 and X2 are 0 and 0, respectively, or 16 and 1, respectively. In another example, Tr can be the start time of the RSO configured by the network node. In another example, Tr can be the end time of the RSO configured by the network node. In another example, Tr may be the center in time of the RSO configured by the network node. In this example, the start time of the adjusted RSO is offset by some margin (e.g., Y1 time resource) relative to Tr. In another example, Tr may be the start time of the RSO before the RSO was shifted in time, or the start time of the RSO before the last or most recent shift was applied to the RSO time. Thus, the duration of the RSO is the same as configured by the network. The following observations are made: 1. The difference between the end of RSO2 in time and the start of CRR3 in time is greater than a certain threshold (H). 2. The difference between the end of RSO3 in time and the start of CRR4 in time is less than H. 3. The onset of RSO4 and CRR5 overlap at least partially in time.
[0102] The embodiments described herein are applicable to Figure 7 and Figure 8 Two situations are shown.
[0103] Fig. 9 Operation of UE 408 according to at least some embodiments described herein is shown. As shown, UE 408 determines whether UE 408 satisfies one or more adjusted RS opportunity-channel reception resource reception (ARCP) conditions for RS opportunity (RSO) and channel reception resource (CRR) (also referred to herein as a set of RSO and CRR or a set consisting of one RSO and one CRR or a pair of RSO and CRR) (step 900). This determination is made based on one or more rules. Based on the above regarding Figure 7 and Figure 8Based on the observation of , the one or more rules for determining whether the UE 408 satisfies the ARCP condition(s) for RSO and CRR may include any one or more of the following rules: UE 408 satisfies the ARCP condition for a certain set of RSO and CRR given that at least one of the following conditions or criteria is met; otherwise, UE 408 does not satisfy the ARCP condition: 1. If a RS opportunity (RSO) and at least one channel reception resource (CRR) at least partially overlap each other in time. 2. If an RSO and at least one CRR are close to each other in time, even if they do not overlap each other in time. Given that at least one of the following conditions or criteria is met, they are considered to be close in time; otherwise, they are not considered to be close in time: a) If the temporal distance between RSO and CRR is within a certain threshold (H1). b) If the time distance between RSO and CRR is not greater than a certain threshold (H2). c) If the difference between the timing of RSO and the timing of CRR is less than or equal to a certain threshold (H3). A specific example of this situation is: I. If the difference between the end of RSO in time and the start of CRR in time is less than or equal to a certain threshold (H31). II. If the difference between the start of RSO in time and the start of CRR in time is less than or equal to a certain threshold (H32). III. If the difference between the start of RSO in time and the end of CRR in time is less than or equal to a certain threshold (H33). IV. If the difference between the end of CRR in time and the start of RSO in time is less than or equal to a certain threshold (H34). V. If the difference between the start of CRR in time and the start of RSO in time is less than or equal to a certain threshold (H35). VI. If the difference between the start of CRR in time and the end of RSO in time is less than or equal to a certain threshold (H36). Thresholds H1, H2, H3, H31, H32, H33, H34, H35 and H36 may be predefined or configured by the network node. Examples of thresholds are 80ms, 160ms, the longest RSO cycle rate, etc.
[0104] Based on whether the UE 408 satisfies a set of ARCP conditions for RSO and CRR, the UE 408 performs one or more operational tasks (step 902). In some example embodiments, the one or more operational tasks include adapting at least one measurement scaling factor to a measurement time to extend the measurement time. In one embodiment, the UE 408 obtains: Information about a first set of operational tasks that the UE 408 may perform if the UE 408 does not satisfy a set of ARCP conditions for RSO and CRR (step 902A), and • Information about a second set of operational tasks that the UE 408 may perform if the UE satisfies a set of ARCP conditions for RSO and CRR (step 902B).
[0105] UE 408 may obtain information about the first set of operational tasks and / or information about the second set of operational tasks based on one or more rules. The rules may be predefined and / or configured by a network node, such as a serving network node of the UE.
[0106] Examples of the first set of operational tasks are: 1. In one example, if the UE 408 does not meet the ARCP condition of a set of RSO and CRR (i.e., a set consisting of one RSO and one CRR), the UE 408 may perform or continue to perform measurements during the RSO in the set of RSO and CRR, even if the RSO is adjusted. The UE 408 also receives or monitors one or more channels during the CRR, such as receiving paging, receiving system information (e.g., MIB, SIB1, other SIBs, etc.).
[0107] Examples of the second set of operational tasks are: 1. In one example, if the UE 408 satisfies the ARCP conditions for a set of RSO and CRR, the UE 408 does not perform or continue to perform measurements during the RSO in the set of RSO and CRR. However, the UE 408 receives or monitors one or more channels during the CRR of the set of RSO and CRR, such as receiving paging, receiving system information (e.g., MIB, SIB1, other SIBs, etc.). Therefore, the UE 408 enables channel reception during CRR (e.g., paging reception during PO, SI acquisition during PBCH, and / or PDSCH carrying SIBs) Takes precedence over performing measurements during an adjusted RSO. 2. In another example, if the UE 408 meets a set of ARCP conditions for RSO and CRR, the UE 408 may stop adjusting the RSO or postpone the adjustment of the RSO for a certain period of time. The UE 408 may also stop performing measurements during the RSO. However, the UE 408 may receive or monitor one or more channels during the CRR. 3. In another example, if the UE 408 satisfies a set of ARCP conditions for RSO and CRR, whether the UE 408 prioritizes channel reception during CRR over performing measurements during adjusted RSO (or vice versa) depends on the type of CRR. o In one example, the UE 408 prioritizes performing measurements during RSO over receiving SI during CRR. In this example, this means that the UE 408 does not receive SI during CRR, e.g., the UE may defer receiving SI to a later CRR that occurs in the future. However, in another example, the UE 408 prioritizes receiving paging during CRR over performing measurements during RSO. In this example, this means that the UE 408 does not perform measurements during RSO, e.g., the UE 408 may defer measurements to a later RSO. o In one example, the UE 408 prioritizes performing measurements during RSO over receiving paging during CRR. But in another example, the UE 408 prioritizes receiving SI during CRR over performing measurements during RSO. 4. In another example, due to satisfying the ARCP condition, the UE 408 is allowed not to receive or monitor a certain channel of up to G1 number of channel reception resources among Gt number of continuous channel reception resources. Where G1≤Gt. In one example, G1=1. In another example, G1>1. 5. In another example, due to satisfying the ARCP condition, the UE 408 is allowed not to receive or monitor a certain channel in the channel reception resources up to G1 number during a certain time period (T41). In one example, G1=1. In another example, G1>1. In one example, T41 is L1 number of DRX cycles. 6. In any of the above examples, the UE 408 may adapt one or more measurement requirements associated with measurements that are not performed by the UE 408 or are not fully performed by the UE 408 during the RSO (due to satisfying the ARCP condition). Examples of measurement requirements are measurement time, measurement accuracy, etc. Examples of measurement time are measurement period, cell detection period, evaluation period, cell selection time, etc. Examples of adapting the measurement time may include extending the measurement time. 7. Specific examples of rules that can be defined are as follows: a) Even if the adjusted or shifted RS opportunity (e.g., SMTC opportunity) is within Z1 time resources before the paging opportunity or within Z2 time resources after the paging opportunity, the UE 408 should receive the paging. However, in this case, the UE 408 is allowed to extend the measurement time of one or more measurements. In one example, Z1=Z2. In another example, Z1≠Z2. An example of Z1 and Z2 is 160ms. b) Even if the adjusted or shifted RS occasion (eg, SMTC occasion) partially or completely overlaps with the paging occasion, the UE 408 should receive paging. However, in this case, the UE 408 is allowed to extend the measurement time of one or more measurements. c) Even if the adjusted or shifted RS opportunity (e.g., SMTC opportunity) is within the Z3 time resource before the SI reception opportunity or within the Z4 time resource after the SI reception opportunity, the UE 408 should receive system information (SI) (e.g., MIB, SIB1, other SIBs, etc.). However, in this case, the UE 408 is allowed to extend the measurement time of one or more measurements. In one example, Z3=Z4. In another example, Z3≠Z4. An example for Z3 and Z4 is 160ms. d) Even if the adjusted or shifted RS opportunity (eg, SMTC opportunity) partially or completely overlaps with the SI reception opportunity, the UE 408 should receive the SI. However, in this case, the UE 408 is allowed to extend the measurement time of one or more measurements. 8. The following describes a specific example showing a method of extending the measurement time in the UE 408 for measurements in which the UE 408 cannot perform measurements in one or more adjusted RSOs.
[0108] Regarding #8 above, a specific example showing a method of extending, in UE 408, a measurement time for measurements in which UE 408 cannot perform measurements in one or more adjusted RSOs is as follows: Impact of TDM between PO and SSB
[0109] In idle mode, in most cases, the paging occasion and the most recent SMTC are less than the SMTC period rate divided by 2. If the most recent SMTC window is close to the paging occasion, after the UE 408 performs intra-frequency measurements, amplitude gain control (AGC) adjustments, and fine timing during the SMTC duration, the UE 408 enters the idle state until the next paging occasion arrives. The closeness of the SMTC occasion and the PO depends on the UE implementation. The time interval is less than tens of milliseconds.
[0110] The worst case is that the paging cycle (ie, DRX cycle) is in the middle of the SMTC periodicity, such as Fig.10As shown (1SMTC, cycle rate = 40ms, DRX = 320ms). Fig.10 PO TDM relative to SSB is shown, DRX = 320ms. Considering the worst case and SMTC periodicity > 20ms, a possible UE implementation is that UE 408 performs intra-frequency measurements, AGC adjustments and fine timing during the SMTC duration, and then reduces RF power until the paging occasion arrives. If the nearest SMTC occasion is far away from the paging occasion, UE 408 may need to wake up twice during one DRX period.
[0111] A general scaling factor for relaxing measurements to avoid the UE 408 waking up twice within a paging cycle is: T_serving = f1(M1, fp1(TSMTC), fp2(DRX)), to represent Table 3 Te_reselection = f2(M2, fp3(TSMTC), fp4(DRX)), to represent Table 4 Among them, in the current requirements: T_serving is N serv , For intra-frequency measurements Te_reselection is T detect,NR_Intra , T measure,NR_Intra and T evaluate,NR_Intra , for inter-frequency measurements, it is T detect,NR_Inter , T measure,NR_Inter and T evaluate,NR_Inter。 • M1=2, fp1(TSMTC): TSMTC>20ms, and fp2(DRX): DRX cycle≤0.64s (for serving cell measurement). M2=1.5, fp3(TSMTC): TSMTC>20ms, and fp4(DRX): DRX cycle<0.64s (for intra-frequency and inter-frequency measurements).
[0112] exist Fig.10 As an example, increasing the number of SMTCs to 4 will cause some new problems: In case 1, all 4 SMTC windows are close together, when the serving cell SMTC is close to PO, the other 3 SMTC windows may conflict with PO, just like the current 1 SMTC case. More relaxation is needed on the measurement to maintain PO reception. In case 2, the 3 SMTC windows are separated in distance from the serving cell SMTC, part of the total 4 SMTC windows may be outside the receive window for AGC and measurement, and additional measurement time is required to adjust the receive window to cover the correct AGC and measurement. In case 2, the fact that SSB is used for AGC before measurement should be valid in multi-SMTC configuration, but multi-SMTC may cause the last SSB of AGC to be very close to the next SSB of measurement, and the radio circuit cannot complete the return in such a short time.
[0113] One example is when the offset of the SMTC window shifts, such as from case 1 to case 2, the receive window needs to be updated accordingly. During the processing time, the measurement may be invalid and require longer measurement time.
[0114] The above problems require additional scaling factors or extended current scaling factors for measurements to avoid the UE 408 waking up more than twice within a paging cycle, including serving cell measurements, intra-frequency and inter-frequency measurements.
[0115] In one example, the updated scaling factor replaces M2, M1: ·T_serving=f1(M3, fp1(TSMTC), fp2(DRX)) ·Te_reselection=f2(M4, fp3(TSMTC), fp4(DRX)) · Among them, M3 is different from M1, such as 3, 4, ...; M4 is different from M2, such as 2, 3, ...
[0116] In another example, to add a new scaling factor to M1, M2: ·T_serving=f1(M1*M5, fp1(TSMTC), fp2(DRX)) ·Te_reselection=f2(M2*M6, fp3(TSMTC), fp4(DRX)) · Among them, M3 is different from M1, such as 3, 4, ...; M4 is different from M2, such as 2, 3, ...
[0117] It should be noted that in idle / inactive state, the DRX cycle to which relaxation is applied is 320ms for the serving cell and 320ms / 640ms for intra-frequency and inter-frequency measurements. Fig.11 PO TDM relative to SSB is shown, DRX = 640ms. Fig.11 It is shown that compared to the current relaxation which only occurs on DRX 320ms, multiple SMTCs may result in longer “radio on” times relative to longer DRX, such as DRX=640ms, 1280ms, etc., which results in more power consumption on the UE 408 .
[0118] To avoid excessive power consumption, the relaxation of DRX is summarized as follows: ·T_serving=f1(M1, fp1(TSMTC), fp6(DRX)) ·Te_reselection=f2(M2, fp3(TSMTC), fp8(DRX)) In one example, fp5(TSMTC): TSMTC>40ms, and fp6(DRX): DRX cycle ≤ 1.28s In one example, fp3(TSMTC): TSMTC>40ms, and fp4(DRX): DRX loop < 1.28s
[0119] Furthermore, the above relaxations on scaling factor and SMTC / DRX can be combined as follows: ·T_serving=f1(M3, fp5(TSMTC), fp9(DRX)) ·Te_reselection=f2(M4, fp7(TSMTC), fp10(DRX)) or, ·T_serving=f1(M1*M5, fp5(TSMTC), fp6(DRX)) ·Te_reselection=f2(M2*M6, fp7(TSMTC), fp10(DRX)) Effect of FDM between PO and SSB
[0120] In the case of FDM solution, where PO will be configured in SMTC occasion (i.e., in the time resource containing SSB), UE 408 cannot receive both SSB and PO at the same time unless UE 408 can support multiple parameter sets. It is not appropriate to discard PO in SMTC occasion, and UE 408 needs to monitor paging all the time during PO.
[0121] If the subcarrier spacing (SCS) of the PO CORESET is the same as the SSB, the UE 408 can perform intra-frequency measurements and paging reception simultaneously. If the SCS of the PO CORESET is different from the SSB SCS, how the UE 408 performs measurements depends on the UE capabilities. UEs that support hybrid parameter sets can still perform intra-frequency measurements and paging reception simultaneously.
[0122] For UEs that do not support hybrid parameter sets, paging reception should be guaranteed and measurements should be performed on SMTCs outside of paging occasions. From a UE behavior perspective, regardless of the SMTC periodicity, Fig.10On top of the paging reception shown, the UE 408 always wakes up once additionally for intra-frequency measurements (1 SMTC, periodicity = 40 ms, DRX = 320 ms).
[0123] exist Fig.12 As an example, increasing the number of SMTCs to 4 presents three problems: In case 1, all 4 SMTC windows are close together, not only the serving cell SMTC is aligned with PO, but more SMTCs also conflict with PO. More relaxation on the measurement is needed to maintain PO reception. In case 2, where the 3 SMTC windows are separated in distance from the serving cell SMTC, a portion of the total 4 SMTC windows may be outside the receive window for AGC and measurement, and additional measurement time is required to adjust the receive window to cover the correct AGC and measurement. In case 2, the fact that SSB is used for AGC before measurement should be valid in multi-SMTC configuration, but multi-SMTC may cause the last SSB of AGC to be very close to the next SSB for measurement, and the radio circuit cannot complete the return in such a short time.
[0124] One example is when the offset of the SMTC window shifts, such as from case 1 to case 2, the receive window needs to be updated accordingly. During the processing time, the measurement may be invalid and require longer measurement time.
[0125] Same as the TDM problem between PO and SSB, the scaling factor needs to be extended or a new scaling factor is needed, and if necessary, the criteria for SMTC and DRX are changed. Scaling factor between PO and SSB
[0126] There are some additional embodiments according to different conditions.
[0127] In one example, the scaling factor in the present disclosure depends on the shift distance or offset of the SMTC adjusted by the UE 408 . In one example, if the UE 408 adjusts the SMTC window in the time domain by a distance less than a threshold (TH1), the relaxation in the present disclosure is invalid, and if the UE 408 adjusts the SMTC window in the time domain by a distance greater than the threshold (TH1), the relaxation in the present disclosure is valid. In another example, if the UE 408 adjusts the SMTC window in the time domain by a distance less than a threshold (TH1), the relaxation in the present disclosure is effective, and if the UE adjusts the SMTC window in the time domain by a distance greater than the threshold (TH1), the relaxation in the present disclosure is ineffective.
[0128] In another example, the scaling factor in the present disclosure depends on the number of SMTC windows adjusted by the UE. • In one example, if the UE 408 adjusts 1 out of 4 SMTC windows, the relaxation in the present disclosure is ineffective. • In another example, if the UE 408 adjusts all SMTC windows simultaneously, the relaxation in the present disclosure is effective.
[0129] In another example, the scaling factor in the present disclosure depends on when the SMTC window is adjusted. In one example, before time T1 elapses after the UE 408 adjusts the SMTC, the relaxation in the present disclosure is effective, and after time T1 elapses after the UE adjusts the SMTC, the relaxation in the present disclosure is ineffective. In another example, before time T1 elapses after the UE 408 adjusts the SMTC, the relaxation in the present disclosure is invalid, and after time T1 elapses after the UE adjusts the SMTC, the relaxation in the present disclosure is valid.
[0130] Another example is that when the UE 408 adjusts the SMTC, the PO may be discarded, but in DRX without SMTC shift, the PO should not be discarded.
[0131] Another example is that the range of SMTC adjustment should be limited without affecting PO, for example, the adjustment range of the SMTC window should maintain a distance threshold (OH3) from PO.
[0132] Another example is that to ensure PO reception, some SMTCs may be skipped, but no measurement requirements are expected for the skipped SMTCs.
[0133] Fig.13An example of a communication system 1300 according to some embodiments is shown. In this example, the communication system 1300 includes a telecommunications network 1302, which includes an access network 1304, such as a radio access network (RAN), and a core network 1306, which includes one or more core network nodes 1308. The access network 1304 includes one or more access network nodes, such as network nodes 1310A and 1310B (one or more of which are generally referred to as network nodes 1310), or any other similar third generation partnership project (3GPP) access nodes or non-3GPP access points (APs). The network nodes 1310 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1312A, 1312B, 1312C, and 1312D (one or more of which may be collectively referred to as UEs 1312) to the core network 1306 via one or more wireless connections. Note that one or more network nodes 1310 may be base stations 406 ( Figure 4 ), which has satellite 402 to NTN ( Figure 4 ) feeder link. In some example embodiments, one or more of UE 1312 performs the functions and features described above with respect to UE 408. In some example embodiments, one or more network nodes 1310 performs the functions and features described above with respect to BS 406 and / or gateway 404.
[0134] Example wireless communications over wireless connections include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Additionally, in various embodiments, the communication system 1300 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via a wired or wireless connection. The communication system 1300 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar types of systems.
[0135] UE 1312 may be any of a variety of communication devices, including wireless devices that are arranged, configured and / or operable to communicate wirelessly with network node 1310 and other communication devices. Similarly, network node 1310 is arranged, capable, configured and / or operable to communicate directly or indirectly with UE 1312 and / or with other network nodes or devices in telecommunication network 1302 to enable and / or provide network access, such as wireless network access, and / or perform other functions, such as management in telecommunication network 1302.
[0136] In the depicted example, the core network 1306 connects the network node 1310 to one or more hosts, such as the host 1316. These connections may be direct or indirect via one or more intermediate networks or devices. In other examples, the network node may be directly coupled to the host. The core network 1306 includes one or more core network nodes (e.g., core network node 1308) composed of hardware and software components. The features of these components may be substantially similar to those described with respect to the UE, network nodes, and / or hosts, so that their descriptions are generally applicable to the corresponding components of the core network node 1308. The example core network node includes the functions of one or more of the following: a mobile switching center (MSC), a mobility management entity (MME), a home subscriber server (HSS), an access and mobility management function (AMF), a session management function (SMF), an authentication server function (AUSF), a subscription identifier de-hiding function (SIDF), a unified data management (UDM), a security edge protection proxy (SEPP), a network exposure function (NEF), and / or a user plane function (UPF).
[0137] The host 1316 may be owned or controlled by a service provider other than the operator or provider of the access network 1304 and / or the telecommunications network 1302, and may be operated by or on behalf of the service provider. The host 1316 may host various applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services (e.g., retrieving and compiling data about various environmental conditions detected by multiple UEs), analysis functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by a server.
[0138] As a whole, Fig.13The communication system 1300 can enable connectivity between UEs, network nodes, and hosts. In that sense, the communication system 1300 can be configured to operate according to predefined rules or procedures, such as specific standards, including but not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE) and / or other suitable second, third, fourth, or fifth generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standards (e.g., sixth generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi); and / or any other suitable wireless communication standards, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards, such as LoRa and Sigfox.
[0139] In some examples, telecommunication network 1302 is a cellular network implementing 3GPP standardized features. Thus, telecommunication network 1302 can support network slicing to provide different logical networks to different devices connected to telecommunication network 1302. For example, telecommunication network 1302 can provide ultra-reliable low latency communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or provide massive machine type communication (mMTC) / massive Internet of Things (IoT) services to yet other UEs.
[0140] In some examples, UE 1312 is configured to transmit and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from access network 1304, the UE can be designed to transmit information to access network 1304 according to a predetermined schedule. In addition, the UE can be configured to operate in a single or multiple radio access technology (RAT) or multi-standard mode. For example, the UE can operate with any one or a combination of WiFi, new air interface (NR) and LTE, i.e., configured for multi-radio dual connectivity (MR-DC), such as evolved UMTS terrestrial RAN (E-UTRAN) NR-dual connectivity (EN-DC).
[0141] In this example, hub 1314 communicates with access network 1304 to facilitate indirect communication between one or more UEs (e.g., UE 1312C and / or 1312D) and a network node (e.g., network node 1310B). In some examples, hub 1314 can be a controller, a router, a content source, and an analysis device, or any other communication device described herein with respect to a UE. For example, hub 1314 can be a broadband router that enables access to core network 1306 for a UE. As another example, hub 1314 can be a controller that sends commands or instructions to one or more actuators in a UE. Commands or instructions can be received from a UE, a network node 1310, or through executable code, scripts, processes, or other instructions in hub 1314. As another example, hub 1314 can be a data collector that acts as a temporary storage for UE data, and in some embodiments, analysis or other processing of the data can be performed. As another example, hub 1314 can be a content source. For example, for a UE that is a virtual reality (VR) headset, display, speaker, or other media delivery device, hub 1314 can retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, and hub 1314 then provides it to the UE either directly, after performing local processing, and / or after adding additional local content. In yet another example, hub 1314 acts as a proxy server or orchestrator for the UE, particularly when one or more UEs are low-energy IoT devices.
[0142] Hub 1314 may have a continuous / persistent or intermittent connection to network node 1310B. Hub 1314 may also allow different communication schemes and / or scheduling between hub 1314 and UEs (e.g., UE 1312C and / or 1312D) and between hub 1314 and core network 1306. In other examples, hub 1314 is connected to core network 1306 and / or one or more UEs via a wired connection. In addition, hub 1314 may be configured to connect to a machine-to-machine (M2M) service provider via access network 1304, and / or to another UE via a direct connection. In some scenarios, a UE may establish a wireless connection with network node 1310 while still being connected via hub 1314 via a wired or wireless connection. In some embodiments, hub 1314 may be a dedicated hub—that is, a hub whose primary function is to route communications from / to network node 1310B to / from UEs. In other embodiments, hub 1314 may be a non-dedicated hub - ie, a device operable to route communications between UEs and network node 1310B, but also capable of serving as a communications origin and / or endpoint for certain data channels.
[0143] Fig.14UE 1400 according to some embodiments is shown. As used herein, UE refers to a device capable of, configured, arranged and / or operable to wirelessly communicate with a network node and / or other UEs. In some example embodiments, UE 1400 performs the functions and features described above with respect to UE 408. Examples of UEs include, but are not limited to, smart phones, mobile phones, cellular phones, voice over Internet protocol (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless user premises devices (CPEs), vehicle-mounted or vehicle embedded / integrated wireless devices, etc. Other examples include any UE identified by 3GPP, including narrowband Internet of Things (NB-IoT) UEs, machine type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.
[0144] The UE may support device-to-device (D2D) communications, such as by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user owning and / or operating an associated device. Instead, a UE may represent a device that is intended to be sold to or operated by a human user, but the device may not be associated with a specific human user, or may not be initially associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user, but the device may be associated with or operated for the benefit of a user (e.g., a smart meter).
[0145] UE 1400 includes processing circuitry 1402 operatively coupled to input / output interface 1406, power source 1408, memory 1410, communication interface 1412, and / or any other components or any combination thereof via bus 1404. Some UEs may utilize Fig.14 All components or a subset of the components shown. The level of integration between components may vary from one UE to another. In addition, some UEs may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
[0146] The processing circuit 1402 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored in the memory 1410 as a machine-readable computer program. The processing circuit 1402 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as microprocessors or digital signal processors (DSPs), together with appropriate software; or any combination of the above. For example, the processing circuit 1402 may include multiple central processing units (CPUs).
[0147] In this example, the input / output interface 1406 can be configured to provide one or more interfaces to an input device, an output device, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. An input device can allow a user to capture information into the UE 1400. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, web cameras, etc.), microphones, sensors, mice, trackballs, direction pads, trackpads, rollers, smart cards, and the like. A presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biosensor, etc., or any combination thereof. An output device can use an interface port of the same type as an input device. For example, a universal serial bus (USB) port can be used to provide an input device and an output device.
[0148] In some embodiments, the power source 1408 is configured as a battery or battery pack. Other types of power sources may be used, such as an external power source (e.g., an electrical socket), a photovoltaic device, or a battery. The power source 1408 may also include a power circuit for delivering power from the power source 1408 itself and / or an external power source to various parts of the UE 1400 via an input circuit or an interface such as a power cable. The delivered power may be used, for example, to charge the power source 1408. The power circuit may perform any formatting, conversion, or other modification to the power from the power source 1408 so that the power is suitable for the corresponding components of the UE 1400 to which the power is supplied.
[0149] The memory 1410 may be or be configured to include a memory such as a random access memory (RAM), a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrical EPROM (EEPROM), a magnetic disk, an optical disk, a hard disk, a removable cartridge, a flash drive, etc. In one example, the memory 1410 includes one or more application programs 1414, such as an operating system, a web browser application, a widget, a widget engine, or other application, and corresponding data 1416. The memory 1410 may store any of a variety of operating systems or combinations of operating systems for use by the UE 1400.
[0150] The memory 1410 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic RAM (SDRAM), an external micro DIMM SDRAM, a smart card memory, such as a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identity modules (SIMs), such as a universal SIM (USIM) and / or an Internet Protocol Multimedia Service Identity Module (ISIM), other memories, or any combination thereof. For example, the UICC may be an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly referred to as a "SIM card". The memory 1410 may allow the UE 1400 to access instructions, applications, etc. stored on a transient or non-transient storage medium to offload data or upload data. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied as or in memory 1410 , which may be or include a device-readable storage medium.
[0151] The processing circuit 1402 may be configured to communicate with an access network or other network using a communication interface 1412. The communication interface 1412 may include one or more communication subsystems and may include or be communicatively coupled to an antenna 1422. The communication interface 1412 may include one or more transceivers for communication, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or network node in the access network). Each transceiver may include a transmitter 1418 and / or a receiver 1420 suitable for providing network communications (e.g., optical, electrical, frequency allocation, etc.). In addition, the transmitter 1418 and the receiver 1420 may be coupled to one or more antennas (e.g., antenna 1422) and may share circuit components, software, or firmware, or alternatively be implemented separately.
[0152] In the illustrated embodiment, the communication functionality of the communication interface 1412 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, NFC, location-based communication such as using a global positioning system (GPS) to determine location, another similar communication functionality, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, code division multiple access (CDMA), wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, transmission control protocol / Internet protocol (TCP / IP), synchronous optical networking (SONET), asynchronous transfer mode (ATM), fast user datagram protocol Internet connection (QUIC), hypertext transfer protocol (HTTP), etc.
[0153] Regardless of the type of sensor, the UE may provide an output of the data captured by its sensor through its communication interface 1412 or via a wireless connection to a network node. The data captured by the UE's sensor may be transmitted to the network node via another UE over a wireless connection. The output may be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load of reports from several sensors), in response to a trigger event (e.g., when moisture is detected, an alarm is sent), in response to a request (e.g., a user-initiated request), or a continuous stream (e.g., a live video feed of a patient).
[0154] As another example, the UE includes an actuator, motor, or switch associated with a communication interface that is configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input, the state of the actuator, motor, or switch can change. For example, the UE can include a motor that adjusts the control surface or rotor of an unmanned aircraft in flight based on the received input, or adjusts a robotic arm performing a medical procedure based on the received input.
[0155] When in the form of an IoT device, a UE may be a device used in one or more application areas including, but not limited to, urban wearable technology, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices are devices that are or are embedded in connected refrigerators or freezers, televisions, connected lighting devices, electric meters, robotic vacuum cleaners, voice-activated smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / moisture sensors, electronic door locks, connected doorbells, air conditioning systems like heat pumps, autonomous vehicles, monitoring systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smart watches, fitness trackers, head-mounted displays for augmented reality (AR) or VR, wearable devices for tactile enhancement or sensor enhancement, sprinklers, animal or item tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any type of medical device, like a heart rate monitor or a teleoperated surgical robot. In addition to the description of Fig.14 In addition to the other components described for the UE 1400 shown in FIG. 1 , a UE in the form of an IoT device includes circuitry and / or software depending on the intended application of the IoT device.
[0156] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another UE and / or a network node. In this case, the UE may be an M2M device, which may be referred to as an MTC device in the 3GPP context. As a specific example, a UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, bus, truck, ship, airplane, or other device capable of monitoring and / or reporting its operating status or other functions associated with its operation.
[0157] In fact, with respect to a single use case, any number of UEs may be used together. For example, a first UE may be or be integrated in a drone and provide speed information of the drone (obtained via a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the speed of the drone. The first and / or second UE may also include more than one of the above functionalities. For example, a UE may include a sensor and an actuator and handle data communications for the speed sensor and the actuator.
[0158] Fig.15 A network node 1500 according to some embodiments is shown. As used herein, a network node refers to a device that is capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), base stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NRNode Bs (GNBs)). In some example embodiments, the network node 1500 performs the functions and features described above with respect to BS 406 and / or gateway 404. BSs can be classified based on the amount of coverage they provide (or, in other words, their transmit power levels), and therefore, depending on the amount of coverage provided, can be referred to as femto BSs, pico BSs, micro BSs, or macro BSs. The BS can be a relay node or a relay donor node that controls a relay. The network node can also include one or more (or all) parts of a distributed radio BS, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such an RRU may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio BS may also be referred to as nodes in a distributed antenna system (DAS).
[0159] Other examples of network nodes include a multi-transmission point (multi-TRP) 5G access node, a multi-standard radio (MSR) device such as an MSR BS, a network controller such as a radio network controller (RNC) or a BS controller (BSC), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile positioning center (E-SMLC)), and / or a minimization of drive tests (MDT).
[0160] The network node 1500 includes a processing circuit 1502, a memory 1504, a communication interface 1506, and a power source 1508. The network node 1500 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own corresponding components. In certain scenarios where the network node 1500 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared between several network nodes. For example, a single RNC may control multiple Node Bs. In this scenario, each unique Node B and RNC pair may be considered to be a single separate network node in certain instances. In some embodiments, the network node 1500 may be configured to support multiple RATs. In such an embodiment, some components may be copied (e.g., separate memories 1504 for different RATs), and some components may be reused (e.g., different RATs may share antennas 1510). The network node 1500 may also include multiple sets of the various components shown for different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies, integrated into the network node 1500. These wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 1500.
[0161] The processing circuit 1502 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a CPU, a DSP, an ASIC, an FPGA, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic, which can be operated to provide the functionality of the network node 1500 alone or in combination with other network node 1500 components (e.g., memory 1504).
[0162] In some embodiments, processing circuitry 1502 includes a system on a chip (SOC). In some embodiments, processing circuitry 1502 includes one or more of the following: radio frequency (RF) transceiver circuitry 1512 and baseband processing circuitry 1514. In some embodiments, RF transceiver circuitry 1512 and baseband processing circuitry 1514 may be on separate chips (or chipsets), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, part or all of RF transceiver circuitry 1512 and baseband processing circuitry 1514 may be on the same chip or chipset, board, or unit.
[0163] Memory 1504 may include any form of volatile or non-volatile computer-readable storage media, including but not limited to permanent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable storage device that stores information, data and / or instructions that can be used by processing circuit 1502. Memory 1504 may store any suitable instructions, data or information, including computer programs, software, applications including one or more logic, rules, codes, tables and / or other instructions that can be executed by processing circuit 1502 and used by network node 1500. Memory 1504 may be used to store any calculations performed by processing circuit 1502 and / or any data received via communication interface 1506. In some embodiments, processing circuit 1502 and memory 1504 are integrated.
[0164] The communication interface 1506 is used for wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs. As shown, the communication interface 1506 includes (one or more) ports / (one or more) terminals 1516 for sending data to and receiving data from the network, for example, via a wired connection. The communication interface 1506 also includes a radio front-end circuit 1518, which can be coupled to the antenna 1510, or in some embodiments is a part of the antenna 1510. The radio front-end circuit 1518 includes a filter 1520 and an amplifier 1522. The radio front-end circuit 1518 can be connected to the antenna 1510 and the processing circuit 1502. The radio front-end circuit 1518 can be configured to adjust the signal transmitted between the antenna 1510 and the processing circuit 1502. The radio front-end circuit 1518 can receive digital data to be sent to other network nodes or UEs via a wireless connection. The radio front-end circuit 1518 can use a combination of filters 1520 and / or amplifiers 1522 to convert digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 1510. Similarly, when receiving data, antenna 1510 may collect the radio signal, which may then be converted into digital data by radio front end circuit 1518. The digital data may be passed to processing circuit 1502. In other embodiments, communication interface 1506 may include different components and / or different combinations of components.
[0165] In certain alternative embodiments, the network node 1500 does not include a separate radio front end circuit 1518; instead, the processing circuit 1502 includes the radio front end circuit and is connected to the antenna 1510. Similarly, in some embodiments, all or some of the RF transceiver circuit 1512 is part of the communication interface 1506. In still other embodiments, the communication interface 1506 includes one or more ports or terminals 1516, the radio front end circuit 1518, and the RF transceiver circuit 1512 as part of a radio unit (not shown), and the communication interface 1506 communicates with the baseband processing circuit 1514, which is part of the digital unit (not shown).
[0166] Antenna 1510 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1510 may be coupled to radio front end circuit 1518 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 1510 is separate from network node 1500 and may be connected to network node 1500 via an interface or port.
[0167] The antenna 1510, the communication interface 1506 and / or the processing circuit 1502 may be configured to perform any receiving operation and / or certain acquisition operations described herein as being performed by the network node 1500. Any information, data and / or signal may be received from a UE, another network node and / or any other network device. Similarly, the antenna 1510, the communication interface 1506 and / or the processing circuit 1502 may be configured to perform any transmitting operation described herein as being performed by the network node 1500. Any information, data and / or signal may be transmitted to a UE, another network node and / or any other network device.
[0168] The power source 1508 provides power to the various components of the network node 1500 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power source 1508 may also include or be coupled to a power management circuit to supply power to the components of the network node 1500 for performing the functionality described herein. For example, the network node 1500 may be connected to an external power source (e.g., a power grid or an electrical outlet) via an input circuit or an interface such as a cable, whereby the external power source supplies power to the power circuit of the power source 1508. As another example, the power source 1508 may include a power source in the form of a battery or battery pack that is connected to or integrated in the power circuit. If the external power source fails, the battery may provide backup power.
[0169] Embodiments of network node 1500 may include, in addition to Fig.151500 to provide certain aspects of network node functionality, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 1500 may include a user interface device to allow information to be input to network node 1500 and to allow information to be output from network node 1500. This may allow a user to perform diagnostics, maintenance, repair, and other management functions on network node 1500.
[0170] Fig.16 is a block diagram of a host 1600 according to various aspects described herein, which host 1600 may be Fig.13 1316 of the embodiment of the host. As used herein, the host 1600 can be or include various combinations of hardware and / or software, including processing resources in a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or a server cluster. The host 1600 can provide one or more services to one or more UEs.
[0171] Host 1600 includes processing circuitry 1602, which is operably coupled to input / output interface 1606, network interface 1608, power source 1610, and memory 1612 via bus 1604. Other components may be included in other embodiments. The features of these components may be substantially similar to those described with respect to previous figures (e.g., Fig.14 and 15 ) so that its description is generally applicable to the corresponding components of the host 1600.
[0172] Memory 1612 may include one or more computer programs, including one or more host applications 1614 and data 1616, which may include user data, such as data generated by a UE for the host 1600 or data generated by the host 1600 for the UE. An embodiment of the host 1600 may utilize only a subset or all of the components shown. The host application 1614 may be implemented in a container-based architecture and may provide support for video codecs (e.g., generic video coding (VVC), high efficiency video coding (HEVC), advanced video coding (AVC), moving picture experts group (MPEG), VP9) and audio codecs (e.g., free lossless audio codec (FLAC), advanced audio coding (AAC), MPEG, G.711), including transcoding for multiple different categories, types or implementations of UE (e.g., handheld devices, desktop computers, wearable display systems, and head-mounted display systems). The host application 1614 may also provide user authentication and permission checks, and may periodically report health, routing, and content availability to a central node (e.g., a device in a core network or on the edge). Thus, the host 1600 can select and / or instruct different hosts for over-the-top (OTT) services for the UE. The host application 1614 can support various protocols, such as HTTP Live Streaming (HLS) protocol, Real-time Messaging Protocol (RTMP), Real-time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc.
[0173] Fig.17 1700 is a block diagram showing a virtualized environment, in which the functions implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which can include virtualized hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any device or component thereof described herein, and relates to an implementation in which at least a portion of functionality is implemented as one or more virtual components. Some or all of the functions described herein can be implemented as virtual components performed by one or more virtual machines (VMs) implemented in one or more virtual environments 1700, and virtual environments 1700 are hosted by one or more hardware nodes (e.g., hardware computing devices operated as network nodes, UEs, core network nodes, or hosts). In addition, in embodiments where the virtual node does not require radio connectivity (e.g., core network nodes or hosts), the node can be fully virtualized.
[0174] Application 1702 (which may alternatively be referred to as a software instance, a virtual device, a network function, a virtual node, a virtual network function, etc.) runs in a virtualized environment Q400 to implement some features, functions and / or benefits of some embodiments disclosed herein.
[0175] The hardware 1704 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, and the like. The software may be executed by the processing circuitry to instantiate one or more virtualization layers 1706 (also referred to as hypervisors or VM monitors (VMMs)), provide VMs 1708A and 1708B (one or more of which may be collectively referred to as VMs 1708), and / or perform any of the functions, features, and / or benefits described with respect to some of the embodiments described herein. The virtualization layer 1706 may present a virtual operating platform that appears to be networked hardware to the VMs 1708.
[0176] VM 1708 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by a corresponding virtualization layer 1706. Different embodiments of instances of virtual devices 1702 can be implemented on one or more VMs 1708, and these implementations can be performed in different ways. Virtualization of hardware is referred to as network function virtualization (NFV) in some contexts. NFV can be used to integrate many network device types onto industry standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premises devices.
[0177] In the context of NFV, VMs 1708 can be software implementations of physical machines that run programs, just as they would be executed on a physical, non-virtualized machine. Each VM 1708 and a portion of the hardware 1704 on which the VM executes, whether hardware dedicated to the VM and / or hardware shared by the VM with other VMs 1708, form a separate virtual network element. Still in the context of NFV, a virtual network function is responsible for handling a specific network function running in one or more VMs 1708 atop hardware 1704, and corresponds to an application 1702.
[0178] Hardware 1704 may be implemented in a standalone network node with general or specific components. Hardware 1704 may implement some functions via virtualization. Alternatively, hardware 1704 may be part of a larger hardware cluster (e.g., such as in a data center or CPE), where many hardware nodes work together and are managed via management and orchestration 1710, which, among other things, oversees the lifecycle management of application 1702. In some embodiments, hardware 1704 is coupled to one or more radio units, each of which includes one or more transmitters and one or more receivers that may be coupled to one or more antennas. The radio unit may communicate directly with other hardware nodes via one or more appropriate network interfaces, and may be used in conjunction with virtual components to provide radio capabilities to virtual nodes such as RAN or BS. In some embodiments, a control system 1712 may be used to provide some signaling, which may alternatively be used for communication between hardware nodes and radio units.
[0179] Fig.18 A communication diagram is shown in which a host 1802 communicates with a UE 1806 via a network node 1804 over a partially wireless connection according to some embodiments. According to various embodiments, reference will now be made to Fig.18 Describe the UE discussed in the previous paragraph (e.g. Fig.13 UE 1312A and / or Fig.14 UE 1400), network node (e.g. Fig.13 The network node 1310A and / or Fig.15 network nodes 1500) and hosts (e.g. Fig.13 Host 1316 and / or Fig.16 An example implementation of host 1600).
[0180] Like the host 1600, an embodiment of the host 1802 includes hardware, such as a communication interface, a processing circuit, and a memory. The host 1802 also includes software stored in or accessible by the host 1802 and executable by the processing circuit. The software includes a host application that can be used to provide services to a remote user, such as a UE 1806 connected via an OTT connection 1850 extending between the UE 1806 and the host 1802. In providing services to the remote user, the host application can provide user data transmitted using the OTT connection 1850.
[0181] The network node 1804 includes hardware that enables it to communicate with the host 1802 and the UE 1806 via a connection 1860. The connection 1860 may be direct or through a core network (such as Fig.13The core network 1306 of the present invention) and / or one or more other intermediate networks, such as one or more public, private or managed networks. For example, the intermediate network can be a backbone network or the Internet.
[0182] UE 1806 includes hardware and software, which is stored in UE 1806 or accessible by UE 1806, and can be executed by the processing circuit of UE. The software includes a client application, such as a web browser or an operator-specific "app", which is operable to provide services to human or non-human users via UE 1806 with the support of host 1802. In host 1802, the executing host application can communicate with the executing client application via an OTT connection 1850 terminated at UE 1806 and host 1802. When providing services to users, the client application of UE can receive request data from the host application of the host and provide user data in response to the request data. OTT connection 1850 can transmit both request data and user data. The client application of UE can interact with the user to generate user data, and the client application of UE provides the user data to the host application through OTT connection 1850.
[0183] The OTT connection 1850 may extend via a connection 1860 between the host 1802 and the network node 1804 and via a wireless connection 1870 between the network node 1804 and the UE 1806 to provide connectivity between the host 1802 and the UE 1806. The connection 1860 and the wireless connection 1870 over which the OTT connection 1850 may be provided have been drawn abstractly to illustrate communications between the host 1802 and the UE 1806 via the network node 1804 without explicit reference to any intermediate devices and the precise routing of messages via those devices.
[0184] As an example of transmitting data via the OTT connection 1850, in step 1808, the host 1802 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with the UE 1806. In other embodiments, the user data is associated with the UE 1806, and the UE 1806 shares the data with the host 1802 without explicit human interaction. In step 1810, the host 1802 initiates a transmission to the UE 1806 carrying the user data. The host 1802 may initiate the transmission in response to a request transmitted by the UE 1806. The request may be caused by human interaction with the UE 1806 or by the operation of a client application executed on the UE 1806. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be delivered via the network node 1804. Therefore, in step 1812, according to the teachings of the embodiments described throughout the present disclosure, the network node 1804 transmits the user data carried in the transmission initiated by the host 1802 to the UE 1806. In step 1814 , UE 1806 receives the user data carried in the transmission, which may be performed by a client application executing on UE 1806 that is associated with a host application executed by host 1802 .
[0185] In some examples, UE 1806 executes a client application that provides user data to host 1802. The user data may be provided as a reaction or response to data received from host 1802. Therefore, in step 1816, UE 1806 may provide user data, which may be performed by executing a client application. In providing the user data, the client application may further consider user input received from a user via an input / output interface of UE 1806. Regardless of the specific manner in which the user data is provided, in step 1818, UE 1806 initiates transmission of the user data to host 1802 via network node 1804. In step 1820, in accordance with the teachings of the embodiments described throughout the present disclosure, network node 1804 receives user data from UE 1806 and initiates transmission of the received user data to host 1802. In step 1822, host 1802 receives the user data carried in the transmission initiated by UE 1806.
[0186] One or more of the various embodiments improve the performance of OTT services provided to UE 1806 using OTT connection 1850, with wireless connection 1870 forming the last leg.
[0187] In an example scenario, plant status information may be collected and analyzed by host 1802. As another example, host 1802 may process audio and video data that may have been retrieved from UE for use in creating maps. As another example, host 1802 may collect and analyze real-time data to help control traffic congestion (e.g., control traffic lights). As another example, host 1802 may store surveillance videos uploaded by UE. As another example, host 1802 may store or control access to media content (e.g., video, audio, VR, or AR), which may broadcast, multicast, or unicast the media content to UE. As other examples, host 1802 may be used for energy pricing, remote control of non-time-critical electrical loads to balance power generation demand, positioning services, demonstration services (e.g., compiling charts based on data collected from remote devices, etc.), or any other function for collecting, retrieving, storing, analyzing, and / or transmitting data.
[0188] In some examples, a measurement process may be provided for the purpose of monitoring data rates, delays, and other factors that are improved by one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 1850 between the host 1802 and the UE 1806 in response to changes in the measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 1850 may be implemented in software and hardware of the host 1802 and / or the UE 1806. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 1850 passes; the sensors may participate in the measurement process by providing the values of the monitored quantities exemplified above, or by providing the values of other physical quantities from which the software can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1850 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not require direct changes to the operation of the network node 1804. Such processes and functionality may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host 1802's measurement of throughput, propagation time, delay, etc. Measurements can be made because the software causes messages to be transmitted using the OTT connection 1850, particularly empty or "dummy" messages, while monitoring propagation times, errors, etc.
[0189] Although the computing devices (e.g., UE, network node, host) described herein may include a combination of the hardware components shown, other embodiments may include computing devices with different combinations of components. It will be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions and methods disclosed herein. The determination, calculation, acquisition or similar operations described herein may be performed by a processing circuit, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with the information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of the processing. In addition, although the components are depicted as a single box located within a larger box or nested within multiple boxes, in fact the computing device may include multiple different physical components constituting a single illustrated component, and functionality may be divided between separate components. For example, a communication interface may be configured to include any component described herein, and / or the functionality of the component may be divided between a processing circuit and a communication interface. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.
[0190] In some embodiments, some or all of the functionality described herein may be provided by a processing circuit that executes instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by a processing circuit without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those specific embodiments, the processing circuit may be configured to perform the described functionality regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functionality are not limited to separate processing circuits or other components of a computing device, but are generally enjoyed by the computing device as a whole and / or end users and wireless networks.
[0191] Some example embodiments of the present disclosure are as follows:
[0192] Embodiment 1: A method performed by a user equipment UE (408) for a wireless access network, the method comprising: determining (900) whether the UE (408) satisfies one or more adjusted RS timing-channel reception resource proximity ARCP conditions for reference signal RS timing RSO and channel reception resource CRR; and performing (902) one or more operation tasks based on whether the UE (408) satisfies the one or more ARCP conditions for RSO and CRR.
[0193] Embodiment 2: A method as described in Embodiment 1, wherein determining (900) whether the UE (408) satisfies the one or more ARCP conditions for RSO and CRR includes determining (900) whether the UE (408) satisfies the one or more ARCP conditions for RSO and CRR based on one or more rules.
[0194] Embodiment 3: A method as described in Embodiment 1, wherein the one or more ARCP conditions include: (a) a condition that the RSO overlaps or partially overlaps with the CRR in time; (b) a condition that the RSO is sufficiently close to the CRR in time; (c) a condition that the time distance between the RSO and the CRR is within a first predetermined or configured threshold; (d) a condition that the time distance between the RSO and the CRR is not greater than a second predetermined or configured threshold; (e) a condition that the difference between the timing (e.g., start or end) of the RSO and the timing (e.g., start or end) of the CRR is less than a second predetermined or configured threshold; or (f) any combination of two or more of (a)-(e).
[0195] Embodiment 4: A method as described in any one of embodiments 1 to 3, wherein executing (902) the one or more operation tasks based on whether the UE (408) satisfies the one or more ARCP conditions for RSO and CRR includes: if the UE (408) does not satisfy the one or more ARCP conditions for RSO and CRR, executing (902C) at least one operation task in the first group of operation tasks; if the UE (408) satisfies the one or more ARCP conditions for RSO and CRR, executing (902C) at least one operation task in the second group of operation tasks.
[0196] Embodiment 5: The method of embodiment 4, wherein the second set of operation tasks includes: transmitting information about adjustment of RSO to the network node; and transmitting information that the one or more ARCP conditions are satisfied for RSO and CRR to the network node.
[0197] Embodiment 6: A method as described in Embodiment 4 or 5, wherein the first group of operational tasks includes: performing or continuing to perform measurements during RSO even if RSO is adjusted; and / or receiving or monitoring one or more channels during CRR (e.g., receiving paging, receiving system information (e.g., MIB, SIB1, other SIBs, etc.)).
[0198] Embodiment 7: A method as described in any one of embodiments 4 to 6, wherein the second set of operation tasks also includes: (i) not performing or continuing to perform measurements during RSO; (ii) receiving or monitoring one or more channels (e.g., receiving paging, receiving system information (e.g., MIB, SIB1, other SIBs, etc.)) during CRR; (iii) stopping adjusting RSO or postponing the adjustment of RSO for a certain period of time; (iv) depending on the type of CRR, giving priority to channel reception during CRR over performing measurements during the adjusted RSO, or vice versa; (v) prohibiting the reception or monitoring of a certain channel in the channel reception resources of up to G1 in the continuous channel reception resources of Gt; (vi) prohibiting the reception or monitoring of a certain channel in the channel reception resources of up to G1 during a certain period of time; (vii) adapting one or more measurement requirements; (viii) extending the measurement time of measurements that the UE (408) cannot perform in one or more adjusted RSOs; or (ix) any combination of two or more of (i)-(viii).
[0199] Embodiment 8: The method as described in any one of embodiments 1 to 7, wherein the wireless access network is a non-terrestrial network NTN.
[0200] Embodiment 9: The method according to any of the previous embodiments further comprises: providing user data; and forwarding the user data to the host via transmission to the network node.
[0201] Embodiment 10: A user device comprises: a processing circuit configured to perform any of the steps of any of embodiments 1 to 9; and a power supply circuit configured to supply power to the processing circuit.
[0202] Embodiment 11: A user equipment (UE), comprising: an antenna configured to send and receive wireless signals; a radio front-end circuit connected to the antenna and a processing circuit and configured to adjust signals transmitted between the antenna and the processing circuit; the processing circuit is configured to perform any of the steps of any of embodiments 1 to 9; an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit; an output interface connected to the processing circuit and configured to output information from the UE that has been processed by the processing circuit; and a battery connected to the processing circuit and configured to supply power to the UE.
[0203] Embodiment 12: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: a processing circuit configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and a processing circuit, the communication interface and processing circuit of the UE being configured to perform any of the steps of any of embodiments 1 to 9 to receive user data from the host.
[0204] Embodiment 13: The host as described in the previous embodiment, wherein the cellular network further comprises a network node configured to communicate with the UE to transmit user data from the host to the UE.
[0205] Embodiment 14: A host as described in the previous two embodiments, wherein: the processing circuit of the host is configured to execute a host application, thereby providing user data; and the host application is configured to interact with a client application executed on the UE, and the client application is associated with the host application.
[0206] Embodiment 15: A method implemented by a host operating in a communication system, the communication system also including a network node and a user equipment (UE), the method comprising: providing user data to the UE; and initiating a transmission carrying the user data to the UE via a cellular network including the network node, wherein the UE performs any of the operations of any of embodiments 1 to 9 to receive the user data from the host.
[0207] Embodiment 16: The method as described in the previous embodiment further includes: at the host, executing a host application associated with the client application executed on the UE to receive user data from the UE.
[0208] Embodiment 17: The method as described in the previous embodiment further includes: at the host, transmitting input data to the client application executed on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
[0209] Embodiment 18: A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: a processing circuit configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and a processing circuit, the communication interface and processing circuit of the UE being configured to perform any of the steps of any of embodiments 1 to 8 to transmit the user data to the host.
[0210] Embodiment 19: The host as described in the previous embodiment, wherein the cellular network further comprises a network node, and the network node is configured to communicate with the UE to transmit user data from the UE to the host.
[0211] Embodiment 20: A host as described in the previous two embodiments, wherein: the processing circuit of the host is configured to execute a host application to provide user data; and the host application is configured to interact with a client application executed on the UE, and the client application is associated with the host application.
[0212] Embodiment 21: A method implemented by a host, the host being configured to operate in a communication system further including a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host by the UE via the network node, wherein the UE performs any of the steps of any of embodiments 1 to 8 to transmit the user data to the host.
[0213] Embodiment 22: The method as described in the previous embodiment further includes: at the host, executing a host application associated with the client application executed on the UE to receive user data from the UE.
[0214] Embodiment 23: The method as described in the previous embodiment further includes: at the host, transmitting input data to the client application executed on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
[0215] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.
Claims
1. A method performed by a user equipment UE (408) for a wireless access network, the method comprising: determining (900) whether the UE (408) satisfies one or more adjusted RS opportunity-channel reception resource proximity ARCP conditions for reference signal RS opportunity RSO and channel reception resource CRR; as well as One or more operational tasks are performed (902) based on whether the UE (408) satisfies the one or more ARCP conditions for the RSO and the CRR, wherein performing the one or more operational tasks includes adapting at least one measurement scaling factor to a measurement time to extend the measurement time.
2. The method of claim 1, wherein: Performing (902) one or more operational tasks based on whether the UE (408) satisfies the one or more ARCP conditions for the RSO and the CRR includes: when multiple RSOs are configured, performing (902) one or more operational tasks based on whether the UE (408) satisfies the one or more ARCP conditions for the RSO and the CRR.
3. The method of claim 1, wherein: Determining (900) whether the UE (408) satisfies the one or more ARCP conditions for the RSO and the CRR includes determining (900) whether the UE (408) satisfies the one or more ARCP conditions for the RSO and the CRR based on one or more rules.
4. The method of claim 1, wherein: The one or more ARCP conditions include: (a) The condition that the RSO overlaps or partially overlaps with the CRR in time; (b) a condition that the temporal distance between the RSO and the CRR is within a first predetermined or configured threshold; (c) a condition that the temporal distance between the RSO and the CRR is not greater than a second predetermined or configured threshold; (d) a condition that a difference between the RSO start time or the RSO end time of the RSO and the CRR start time or the CRR end time of the CRR is less than or equal to a third predetermined or configured threshold; or (e) Any combination of two or more of (a) to (d).
5. The method according to any one of claims 1 to 3, wherein: Performing (902) the one or more operational tasks based on whether the UE (408) satisfies the one or more ARCP conditions for the RSO and the CRR includes: If the UE (408) does not satisfy the one or more ARCP conditions for the RSO and the CRR, performing (902C) at least one operational task from a first set of operational tasks; and If the UE (408) satisfies the one or more ARCP conditions for the RSO and the CRR, at least one operating task from a second set of operating tasks is performed (902D).
6. The method of claim 5, wherein: The second set of operational tasks includes: transmitting information about the adjustment of the RSO to a network node; and Information that the one or more ARCP conditions are satisfied for the RSO and the CRR is transmitted to the network node.
7. The method according to claim 5 or 6, wherein: The first set of operational tasks includes: performing or continuing to perform measurements during the RSO even if the RSO is adjusted; or One or more channels are received or monitored during the CRR.
8. The method according to any one of claims 5 to 7, wherein: The second set of operational tasks also includes: (i) not performing or continuing to perform measurements during the RSO; (ii) receiving or monitoring one or more channels during the CRR; (iii) ceasing to adjust said RSO or deferring said adjustment of said RSO for a certain period of time; (iv) depending on the type of CRR, prioritizing channel reception during the CRR over performing measurements during the adjusted RSO, or vice versa; (v) prioritizing performing measurements during the RSO over receiving paging during the CRR; (vi) prohibiting reception or monitoring of a certain channel among up to G1 number of channel reception resources among Gt number of continuous channel reception resources; (vii) prohibiting reception or monitoring of a certain channel in up to G1 number of channel reception resources during a certain time period; (viii) adapting one or more measurement requirements; (ix) extending the measurement time of measurements that the UE (408) cannot perform in one or more adjusted RSOs; or (x) Any combination of two or more of (i) to (ix).
9. The method according to claim 7 or 8, wherein: Receiving or monitoring the one or more channels during the CRR includes receiving paging or receiving system information SI.
10. The method of claim 5, wherein: The UE (408) obtains the first set of operating tasks or the second set of operating tasks based on one or more rules.
11. The method of claim 10, wherein: The one or more rules include: (i) the UE (408) receives paging even if the adjusted or shifted RSO is within Z1 time resources before the paging occasion or within Z2 time resources after the paging occasion; (ii) the UE (408) receives paging even if the adjusted or shifted RSO partially or completely overlaps with the paging occasion; or (iii) the UE (408) receives the system information SI even if the adjusted or shifted RSO is within Z3 time resources before the SI reception opportunity or within Z4 time resources after the SI reception opportunity; or (iv) Even if the adjusted or shifted RSO partially or completely overlaps with the SI reception opportunity, the UE (408) receives the SI.
12. The method of claim 11, wherein: The adjusted or shifted RSO includes a synchronization signal block SBB measurement timing configuration SMTC opportunity.
13. The method according to claim 9 or 11, wherein: The SI includes a master information block MIB, a system information block 1 SIB1 or other system information blocks SIB.
14. The method according to any one of claims 1 to 12, wherein: The wireless access network is a non-terrestrial network NTN.
15. A user equipment UE (408), comprising: transmitter circuit (1418); as well as A processing circuit (1402) associated with the transmitter circuit (1418), the processing circuit (1402) being configured to cause the UE (408): determining (900) whether the UE (408) satisfies one or more adjusted RS opportunity-channel reception resource proximity ARCP conditions for reference signal RS opportunity RSO and channel reception resource CRR; as well as One or more operational tasks are performed (902) based on whether the UE (408) satisfies the one or more ARCP conditions for the RSO and the CRR, wherein performing the one or more operational tasks includes adapting at least one measurement scaling factor to a measurement time to extend the measurement time.
16. The UE (408) of claim 15, wherein: Determining (900) whether the UE (408) satisfies the one or more ARCP conditions for the RSO and the CRR includes determining (900) whether the UE (408) satisfies the one or more ARCP conditions for the RSO and the CRR based on one or more rules.
17. The UE (408) of claim 15, wherein: The one or more ARCP conditions include: (a) The condition that the RSO overlaps or partially overlaps with the CRR in time; (b) a condition that the temporal distance between the RSO and the CRR is within a first predetermined or configured threshold; (c) a condition that the temporal distance between the RSO and the CRR is not greater than a second predetermined or configured threshold; (d) the condition that the difference between the start time or the end time of the RSO and the start time or the end time of the CRR is less than or equal to a third predetermined or configured threshold; or (e) Any combination of two or more of (a) to (d).
18. The UE (408) according to any one of claims 15 to 17, wherein: Performing (902) the one or more operational tasks based on whether the UE (408) satisfies the one or more ARCP conditions for the RSO and the CRR includes: If the UE (408) does not satisfy the one or more ARCP conditions for the RSO and the CRR, performing (902C) at least one operational task from a first set of operational tasks; and If the UE (408) satisfies the one or more ARCP conditions for the RSO and the CRR, at least one operating task from a second set of operating tasks is performed (902D).
19. The UE (408) of claim 18, wherein: The second set of operational tasks includes: transmitting information about the adjustment of the RSO to a network node; and Information that the one or more ARCP conditions are satisfied for the RSO and the CRR is transmitted to the network node.
20. A user equipment UE, adapted to perform the method according to any one of claims 1 to 13.
21. A non-transitory computer readable medium having stored thereon codes, which when executed cause a processor to perform the method recited in any one of claims 1 to 13.
