Method, network entity and computer software for configuring user equipment to measure one or more synchronization signals and to receive synchronization signal measurements

Abstract

A method of configuring a user equipment (UE) to measure one or more synchronization signals from one or more potential target base stations is provided. A serving base station of the UE is configured to periodically transmit a first synchronization signal and a second synchronization signal. Each of the one or more potential target base stations is configured to periodically transmit a first synchronization signal. The method includes transmitting, from each of the one or more potential target base stations, an indication of whether the respective base station periodically transmits a second synchronization signal to the serving base station. The method also includes transmitting configuration data from the serving base station to the UE, the configuration data causing the UE to measure the one or more synchronization signals from the one or more potential target base stations. If at least a threshold number of one or more potential target base stations periodically transmit a second synchronization signal, the configuration data causes the UE to measure the second synchronization signal for each of the one or more potential target base stations. If one or more potential target base stations whose number is lower than the threshold number periodically transmit the second synchronization signal, the configuration data causes the UE to measure the first synchronization signal for each of the one or more potential target base stations.

Description

Technical Field

[0001] This invention relates to configuring apparatus in a telecommunications network for measuring synchronization signals. In particular, this invention relates to configuring apparatus in scenarios where base stations are configured to transmit multiple individual synchronization signals. The invention also relates to receiving synchronization signal measurements from the apparatus.

[0002] Vocabulary eMBB – Enhanced Mobile Broadband URLLC – Ultra-Reliable Low-Latency Communication IoT – Internet of Things IIoT – Industrial Internet of Things mMTC – Massive Machine Type Communication LPWA – Low Power Wide Area Network LTE-M – Long Term Evolution of Machines NB-IoT – Narrowband IoT MIMO – Multiple Input Multiple Output SISO – Single Input Single Output FR1 – Frequency Range 1 FR2 – Frequency Range 2 HD-FDD – Half-duplex Frequency Division Duplex FD-FDD – Full-duplex Frequency Division Duplex BD – Blind Decoding CCE – Control Channel Element PDCCH – Physical Downlink Control Channel SFN – System Frame Number eDRX – Extended Discontinuous Reception RRM – Radio Resource Management IE – Information Elements RACH – Random Access Channel SSB – Synchronization Signal Block PSS – Primary Synchronization Signal SSS – Auxiliary Synchronization Signal PBCH – Physical Broadcast Channel DMRS – Demodulation Reference Signal MIB – Master Message Block SIB – System Information Block CD-SSB – Cell Definition SSB NCD-SSB – Non-Cell Definition SSB BWP – Bandwidth Section SMTC – SS / PBCH Block Measurement Timing Configuration RMSI – Remaining Minimal System Information OAM – Operations, Management and Management MO – Managed Objects RAN – Radio Access Network UE – User Equipment BS – Base Station ABS – Advanced Base Station BTS – Base Station Transceiver BSS – Basic Services Set ESS – Extended Services AP – Access Point NB – Node B (Radio Base Station Receiver) eNB – Evolved Node B gNB – Next Generation Node B TRP – Transmit and Receive Point PS – Server Management TE – Terminal Equipment MS – Mobile Station MT – Mobile Terminal UT – User Terminal SS – Subscriber Site PDA – Personal Digital Assistant CDMA – Code Division Multiple Access FDMA – Frequency Division Multiple Access TDMA – Time Division Multiple Access OFDMA – Orthogonal Frequency Division Multiple Access SC-FDMA – Single-Carrier Frequency Division Multiple Access MC-FDMA – Multi-Carrier Frequency Division Multiple Access UTRA – Universal Terrestrial Radio Access GSM – Global System for Mobile Communications GPRS – General Packet Radio Service EDGE – Enhanced data rate evolution of GSM IEEE – Institute of Electrical and Electronics Engineers E-UTRA – Evolved UTRA UMTS – Universal Mobile Telecommunications System E-UMTS – Evolved UMTS 3GPP – Third Generation Partnership Project DL – Downlink UL – Uplink LTE – Long Term Evolution (4G) LTE-A – Advanced LTE NR – New Radio (5G) FDD – Frequency Division Duplex TDD – Time Division Duplex CRS – Cell-Specific Reference Signal CSI-RS – Channel State Information Reference Signal FPGA – Field Programmable Gate Array ASIC – Application-Specific Integrated Circuit DSP – Digital Signal Processor CD-ROM – Read-Only Optical Disc Memory DVD-ROM – Digital Multifunction Optical Disc Read-Only Memory ROM – Read-Only Memory RAM – Random Access Memory EEPROM – Electrically Erasable Programmable Read-Only Memory EPROM – Erasable Programmable Read-Only Memory. Background Technology

[0003] Releases 15 and 16 of the 3GPP (5G) standard provide enhanced mobile broadband (eMBB) services with reliable coverage and mobility tolerance for high-speed and high-capacity data connections. An alternative service requirement, Ultra-Reliable Low-Latency Communication (URLLC), is defined for devices / applications requiring high reliability and the lowest possible latency. However, not every UE requires such an elevated level of service. For example, IoT devices (sometimes referred to as IIoT in 5G) may only need to transmit small amounts of data and may tolerate high latency. These devices may have a large number of connections in a specific area. A third service requirement for such devices is defined as Massive Machine-Type Communication (mMTC) in 5G. There may also be devices (such as sensor devices, surveillance devices, and wearable devices) that require service levels between these extremes.

[0004] Release 17 of the 3GPP (5G) standard added a new UE type definition, which has reduced requirements compared to eMBB and URLLC, but enhanced performance characteristics (e.g., data throughput and speed) compared to LPWA (i.e., LTE-M / NB-IoT) or mMTC. This UE type is called a "reduced capability" UE or RedCap UE.

[0005] 3GPP Technical Report (TR) 38.875 (which is incorporated here by reference) specifies three potential use cases for RedCap devices, including industrial sensors, monitoring devices, and health wearables.

[0006] Some RedCap devices implement strategies to reduce complexity, cost, and power consumption. One strategy is to use fewer antennas in the device, which also reduces the maximum number of MIMO layers. Some RedCap devices only support 2×2 MIMO in the downlink and SISO in the uplink.

[0007] Compared to other devices, RedCap devices can also support lower bandwidths. For example, some RedCap devices may only support 20 MHz bandwidth for FR1 and 100 MHz bandwidth for FR2. Lower bandwidth reduces the complexity of the power amplifier and enables efficient operation of the device.

[0008] Additionally, some RedCap devices use half-duplex FDD (HD-FDD) transmission instead of full-duplex FDD (FD-FDD). This prevents the device from simultaneously transmitting and receiving data on different frequencies, thus reducing complexity. In such devices, isolation between the transmission and reception paths may not be required. Therefore, RedCap devices can use switches instead of duplexers.

[0009] Additional strategies can be employed to reduce the power consumption of RedCap devices. In some examples, RedCap UEs have reduced the blind decoding (BD) and control channel element (CCE) limits monitored by the device in the physical downlink control channel (PDCCH), which can reduce power consumption.

[0010] RedCap devices can use System Frame Number (SFN) technology to increase the Extended Discontinuous Receive (eDRX) cycle when the device is disconnected from the network or becomes idle, which can reduce power consumption. Longer eDRX cycles can also be beneficial in certain use cases, such as industrial sensors. Release 17 also allows RedCap devices to transmit data without being connected to a network.

[0011] Additionally, radio resource management (RRM) requirements can be reduced to accommodate RedCap devices, which enables the devices to reduce their power consumption.

[0012] Modifications to device capabilities also impact the network. For example, lower bandwidth support may require corresponding changes to the Bandwidth Part (BWP) configuration. New Information Elements (IEs) can also enable dynamic bandwidth adaptation.

[0013] Lower bandwidth can also affect the RACH procedure used by the device to access the network. The network can specify a specific BWP for RedCap devices, or it can reduce the size of the BWP for these devices.

[0014] In 5G (NR), the gNB periodically transmits SSBs, which are used by the UE for synchronization, cell search, and initial beamforming. The SSB includes synchronization signals (PSS and SSS) and the PBCH. The PBCH includes the PBCH DMRS and payload data; the PBCH DMRS serves as a reference signal for decoding the PBCH, and the payload data is used to transmit the MIB.

[0015] For devices with reduced capabilities, an alternative to SSB, namely NCD-SSB, can be used.

[0016] Release 18 of the 3GPP (5G) standard introduces a new UE type definition that allows for even further reduced performance characteristics (e.g., data throughput and speed) compared to RedCap UEs. This UE type is called "Enhanced RedCap" or eRedCap UE. For example, a RedCap UE might be limited to 20MHz bandwidth, while an eRedCap UE might be limited to 5MHz bandwidth. Release 18 also extends support for NCD-SSB to all UEs, not just RedCap UEs. Summary of the Invention

[0017] Some existing technologies use a single NCD-SSB for devices with reduced capabilities. However, they do not consider whether there are sufficient devices in the network that will use the NCD-SSB to justify the resources used by transmitting a single NCD-SSB. Against this background, a method for selectively enabling the NCD-SSB is provided.

[0018] A method is provided for a base station to facilitate synchronization of multiple user equipment (UEs). The multiple UEs include at least one UE of a first capability type. The method includes: The first synchronization signal is transmitted periodically; Determine the network traffic level transmitted via the base station and associated with at least one UE of a first capability type; and Based on the network traffic level transmitted via the base station and associated with at least one UE of the first capability type, a second synchronization signal is selectively and periodically transmitted.

[0019] Network traffic can be a measure of the data transmitted between the UE and the base station.

[0020] When we refer to a UE of "first capability type," this can also be written as a UE "having first capability type." A first capability type can be used to define a group of UEs with similar capabilities (e.g., UEs with reduced capabilities). Alternatively, a first capability type can be used to define a group of UEs, all of which have at least the minimum required set of capabilities. UEs with additional / enhanced capabilities may be permitted to be defined as belonging to the first capability type, provided they meet the minimum requirements. An example of the minimum capability requirement for a first capability type is that the UE can synchronize using a second synchronization signal.

[0021] Selectively and periodically transmitting a second synchronization signal based on a traffic level transmitted via a base station and associated with at least one UE of a first capability type may include: If the network traffic level transmitted via the base station and associated with at least one user equipment of a first capability type exceeds a first threshold, a second synchronization signal is periodically transmitted; and If the level of network traffic transmitted via the base station and associated with at least one user equipment of the first capability type drops below the second threshold level, the periodic transmission of the second synchronization signal is disabled.

[0022] The first and second thresholds can be the same or different. Having two separate thresholds for enabling and disabling NCD-SSB can provide the network with a degree of flexibility.

[0023] In the first example, if the NCD-SSB can be found, the UE measures the NCD-SSB. Otherwise, the UE falls back to the CD-SSB. In the second example, based on the network decision, the network notifies the UE whether to measure the NCD-SSB. The second example requires another signal from the network to the UE to inform the UE of the network decision.

[0024] Leveraging the flexibility introduced by having two separate thresholds, and based on the behavior described above, the network can notify the UE of NCD-SSB changes in a manner that allows for a delay. In other words, the network does not need to immediately notify the UE when making network decisions.

[0025] Thresholds can be absolute or relative. The “level” of network traffic can be measured as an absolute value or as a proportion of total network traffic transmitted via a base station (associated with any type of UE).

[0026] The method may also include: Receives network traffic levels associated with one or more UEs of a first capability type, transmitted via the respective base stations and corresponding to one or more neighboring cells. The selective periodic transmission of the second synchronization signal is also based on network traffic levels associated with the UE of the first capability type, transmitted via one or more base stations corresponding to one or more neighboring cells.

[0027] Selectively and periodically transmitting a second synchronization signal, based on network traffic levels transmitted via base stations and associated with at least one UE of a first capability type, and also based on network traffic levels transmitted via one or more base stations corresponding to one or more neighboring cells and associated with UEs of the first capability type, may include: For a base station and one or more base stations corresponding to one or more neighboring cells, the total network traffic level associated with a UE of the first capability type is determined by combining the network traffic level transmitted via the base station and associated with at least one UE of the first capability type with the network traffic level transmitted via one or more base stations corresponding to one or more neighboring cells and associated with a UE of the first capability type. If the total network traffic level associated with a UE of the first capability type exceeds a first threshold, a second synchronization signal is periodically transmitted. If the total network traffic level associated with a UE of the first capability type drops below the second threshold level, the periodic transmission of the second synchronization signal is disabled.

[0028] The combination of network traffic levels transmitted via base stations and associated with at least one UE of a first capability type and network traffic levels transmitted via one or more base stations corresponding to one or more neighboring cells and associated with a UE of a first capability type may include one or more of the following: Summing each of the network traffic levels transmitted via a base station and associated with at least one UE of a first capability type, and the network traffic levels transmitted via one or more base stations corresponding to one or more neighboring cells and associated with UEs of the first capability type; and Calculate a weighted average of each of the network traffic levels transmitted via a base station and associated with at least one UE of a first capability type, and the network traffic levels transmitted via one or more base stations corresponding to one or more neighboring cells and associated with a UE of a first capability type.

[0029] The method may also include sending network traffic levels transmitted via the base stations and associated with at least one UE of a first capability type to one or more base stations corresponding to one or more neighboring cells.

[0030] Multiple UEs may also include at least one UE of a second capability type, wherein: Compared to the second ability type, the first ability type corresponds to a reduced ability; Compared to the second capability type, the first capability type is not a downgrade and corresponds to a UE compatible with the second synchronization signal; or The first capability type corresponds to a UE compatible with the second synchronization signal, and at least one UE of the first capability type includes at least one UE with reduced capability compared to the second capability type and at least one UE with no reduced capability compared to the second capability type.

[0031] The first ability type can correspond to the reduced ability "RedCap" ability type and / or the enhanced RedCap "eRedCap" ability type.

[0032] Alternatively, the first capability type may correspond to one or more non-RedCap UEs that support synchronization based on the second synchronization signal (release version 18 of the 3GPP standard plans to support NCD-SSB measurements performed by non-RedCap UEs).

[0033] Alternatively, the first capability type of UE may include a combination of zero or more RedCap UEs (optionally including zero or more eRedCap UEs) and zero or more nonRedCap UEs that support second synchronization signal (NCB-SSB) measurement.

[0034] The second synchronization signal can be used to facilitate the synchronization of at least one UE of the first capability type.

[0035] UEs of the first capability type (e.g., RedCap UEs) may be able to synchronize using a second synchronization signal (e.g., NCD-SSB). RedCap UEs are compatible with the new synchronization information. According to Release 18, other (non-RedCap) UEs are also able to synchronize using a second synchronization signal (e.g., NCD-SSB).

[0036] In some examples, a first synchronization signal (e.g., CD-SSB) may be used to facilitate synchronization of at least one UE of a second capability type. Non-RedCap UEs may require CD-SSB (e.g., if the UE is not compatible with NCD-SSB).

[0037] When the periodic transmission of the second synchronization signal is disabled, the first synchronization signal can be used to facilitate the synchronization of at least one UE of a first capability type.

[0038] CD-SSB can be used to synchronize non-RedCap UEs. When an NCD-SSB is transmitted, it can be used to facilitate synchronization of RedCap UEs (and optionally eRedCap UEs and / or release version 18+ UEs). When an NCD-SSB is disconnected, CD-SSB can be used to synchronize RedCap UEs (and optionally eRedCap UEs and / or release version 18+ UEs). In other words, if an NCD-SSB is unavailable (i.e., disconnected), UEs that would otherwise use an NCD-SSB (i.e., those compatible with an NCD-SSB, such as RedCap UEs, eRedCap UEs, and compatible release version 18+ UEs) can fall back to using CD-SSB.

[0039] If NCD-SSB is configured (i.e., enabled), UEs operating in the corresponding BWP (e.g., RedCap UE, eRedCap UE, and / or release version 18+ UE) can use NCD-SSB for purposes that RedCap UEs would otherwise use the serving cell's CD-SSB (e.g., to obtain synchronization, measurement, RLM, and the like).

[0040] Each of the first synchronization signal and the second synchronization signal can be a synchronization signal block, including: Primary synchronization signal (PSS); Auxiliary synchronization signal (SSS); Physical Broadcast Channel (PBCH); and Physical Broadcast Channel Demodulation Reference Signal (PBCH DMRS).

[0041] For each of the first synchronization signal and the second synchronization signal, the PBCH may include a Master Information Block (MIB).

[0042] The MIB of the first synchronization signal may include information about the reference subcarrier spacing, the control channel of the SIB PDSCH, the DMRS location, and the like. SIB1 may carry all the basic information for the UE to perform the initial attachment procedure (at least up to RrcSetup). SIB1 may also carry scheduling information for other SIBs.

[0043] The MIB of the second synchronization signal may lack information related to the SIB because the second synchronization signal may not be associated with any SIB.

[0044] The first synchronization signal may include data that enables the UE to obtain the first system information block (SIB1). In contrast, the second synchronization signal may not be used to obtain SIB1.

[0045] In other words, as defined in the 3GPP physical layer specification, the NCD-SSB can be an SSB that is not used to obtain SIB1.

[0046] Alternatively, the first synchronization signal may be associated with a System Information Block (SIB), while the second synchronization signal may not be associated with an SIB.

[0047] The first synchronization signal can be associated with the Residual Minimal System Information (RMSI) block. The second synchronization signal can be unassociated with the RMSI block.

[0048] The first synchronization signal can be a cell-defined synchronization signal block (CD-SSB). The second synchronization signal can be a non-cell-defined synchronization signal block (NCD-SSB).

[0049] Each of the first synchronization signal and the second synchronization signal may include multiple parameters.

[0050] The second synchronization signal may include parameters that are different from those of the first synchronization signal.

[0051] Compared to the first synchronization signal, the second synchronization signal may include a larger number of parameters.

[0052] Compared to the first synchronization signal, the parameter subset of the second synchronization signal can have different values ​​(and the remaining parts can be the same).

[0053] Each of the first synchronization signal and the second synchronization signal may include multiple information elements, wherein each of the multiple information elements includes corresponding multiple parameters.

[0054] The information elements of the second synchronization signal may include one or more of the following parameters: The absolute frequency of the synchronization signal; The periodicity of the synchronization signal; and The time offset of the second synchronization signal relative to the first synchronization signal.

[0055] The information elements of the first synchronization signal may include one or more of the following parameters: The absolute frequency of the synchronization signal; The periodicity of the synchronization signal; and Time offset.

[0056] The periodicity of the second synchronization signal may differ from that of the first synchronization signal.

[0057] Since the second synchronization signal can be used in devices with reduced capability, signals can be transmitted with greater periodicity (i.e., less frequently). As a result, radio resources can be conserved.

[0058] Determining the network traffic level transmitted via the base station and associated with at least one user equipment of a first capability type may include determining whether a UE communicating via the base station is a UE of a first capability type based on UE device type information and / or UE capability information reported by the UE to the base station.

[0059] The UE can report its radio access capabilities to the base station.

[0060] Determining whether a UE is a first-capability type UE can include: Determine whether the UE is a RedCap UE or an eRedCap UE; Determine that the UE is a UE capable of using a second synchronization signal (e.g., NCD-SSB) (e.g., a non-RedCap UE); or Determine whether the UE is a RedCap UE, an eRedCap UE, or a UE capable of using the second synchronization signal.

[0061] RedCap UEs from 3GPP Release 17 onwards are compatible with the second synchronization signal. From 3GPP Release 18 onwards, non-RedCap UEs are compatible with the second synchronization signal (as well as RedCap UEs and eRedCap UEs).

[0062] The method may further include requesting UE device type information and / or UE capability information from each of the plurality of UEs, and receiving UE device type information and / or UE capability information in response.

[0063] UE device type information and / or UE capability information may be provided in information elements that specifically relate to the first capability type. Determining whether a UE communicating via a base station is a UE of the first capability type can be based on the presence of information elements specifically relating to the first capability type in the signaling from the UE.

[0064] For example, the information element could be RedCapParameters or UE-NR-Capability.

[0065] As discussed above, determining whether a UE is a first-capability type UE can include: Determine whether the UE is a RedCap UE or an eRedCap UE; It is determined that the UE is a Rel18 UE capable of using NCD-SSB; or Determine whether the UE is a RedCap UE, an eRedCap UE, or a 3GPP release version 18+ UE that can use NCD-SSB.

[0066] It also provides a network entity that can be configured to perform the methods described above.

[0067] Computer software including instructions is also provided, which, when executed on a processor, cause the processor to perform the methods described above.

[0068] As described above, a base station can transmit two separate synchronization signals (e.g., synchronization signal blocks (SSBs)). The first synchronization signal is suitable for all devices, and the second synchronization signal is provided for devices that support measurements of the second synchronization signal (e.g., RedCap devices, eRedCap devices, and / or devices conforming to 3GPP release 18). Compared to the first synchronization, the second synchronization can be simplified (and can be a non-cell-defined synchronization signal block (NCD-SSB), while the primary synchronization signal can be a cell-defined synchronization signal block (CD-SSB)).

[0069] As described above, the base station can selectively enable the auxiliary synchronization signal based on the network traffic level associated with the device capable of using the auxiliary synchronization signal. Furthermore, during periods of high traffic, the base station can selectively enable additional synchronization signals (e.g., third and fourth synchronization signals).

[0070] Synchronization signals can be selectively enabled and disabled based on network traffic levels. Therefore, a region can include a mix of base stations, some of which enable auxiliary synchronization signals and others which disable them.

[0071] To enable the UE to switch to a different cell under appropriate circumstances (e.g., due to changes in network conditions or because the UE has been moved), the UE periodically measures the signal strength of the synchronization signal from the potential target base station. For this purpose, the UE is configured to measure the synchronization signal on one or more frequencies.

[0072] Where available, existing techniques configure the UE to measure the primary synchronization signal (e.g., CD-SSB) and also the secondary synchronization signal (e.g., NCD-SSB).

[0073] In contrast to existing technologies, for each neighboring base station, the proposed method transmits an indication to the adjacent base station (which, if a UE is attached, can be the serving base station, although the indication can be received shortly after the base station is powered on, before any UE is connected) as to whether the neighboring base station is transmitting a second synchronization signal. Based on this indication, the serving base station can send configuration data to the UE, which enables the UE to measure the second synchronization signal of the neighboring base stations (if available). If enough neighboring base stations are transmitting the second synchronization signal, the UE may not need to measure the first synchronization signal of any of these base stations.

[0074] A method is provided to configure a user equipment (UE) to measure one or more synchronization signals from one or more potential target base stations. The serving base station of the UE is configured to periodically transmit a first synchronization signal and a second synchronization signal. Each of the one or more potential target base stations is configured to periodically transmit the first synchronization signal. The method includes transmitting from each of the one or more potential target base stations to the serving base station an indication of whether the corresponding base station is periodically transmitting the second synchronization signal. The method also includes transmitting configuration data from the serving base station to the UE, the configuration data causing the UE to measure the one or more synchronization signals from the one or more potential target base stations. If at least a threshold number of the one or more potential target base stations periodically transmits the second synchronization signal, the configuration data causes the UE to measure the second synchronization signal of each of the one or more potential target base stations. If the number of the one or more potential target base stations is less than a threshold number, the configuration data causes the UE to measure the first synchronization signal of each of the one or more potential target base stations.

[0075] In order for the serving base station to correctly configure the UE to measure synchronization signals from neighboring base stations, the serving base station needs to know whether the neighboring base stations are transmitting a second synchronization signal. Therefore, the proposed method transmits this information between neighboring base stations (e.g., from a potential target base station to the UE's serving base station).

[0076] In the case where the method includes transmitting an indication from each of one or more potential target base stations to the serving base station as to whether the respective base station is periodically transmitting a second synchronization signal, it should be noted that the serving base station may not be the UE's serving base station at the time the indication is received. The indication may be received in advance before the UE is attached to a base station. Therefore, this communication can alternatively be written as communication of indications between adjacent base stations. In some examples, the indication may be transmitted between base stations shortly after one of the base stations is activated.

[0077] If each neighboring base station is transmitting a second synchronization signal, the UE may only need to measure the second synchronization signal of each of the neighboring base stations (i.e., the UE may not need to measure the first synchronization signal of any of these base stations). Furthermore, if each of the neighboring base stations transmits a second synchronization signal on the same frequency, then the UE may only need to measure the synchronization signal on one frequency.

[0078] If most (but not all) of the neighboring base stations are transmitting a second synchronization signal, the UE can measure the second synchronization signal of each of the neighboring base stations that are transmitting a second synchronization signal, but may not need to measure the first synchronization of any of the base stations (including those that are not transmitting a second synchronization signal). In this case, the UE will not consider the few neighboring base stations that are not transmitting a second synchronization signal as candidates for handover.

[0079] The first and / or second synchronization signals of each of one or more potential target base stations can be used to determine whether to perform a handover from the UE's serving base station to the corresponding potential target base station.

[0080] Each of one or more potential target base stations can be associated with one or more neighboring cells. This indication can be an indication of whether each of the one or more neighboring cells is periodically transmitting a second synchronization signal. A base station (e.g., a gNB) can have multiple cells. For example, each sector and frequency band can be a different cell. Each cell can enable a different number of NCD-SSBs. For example, a base station with 100 MHz bandwidth on a 3.5 GHz cell and 10 MHz bandwidth on a 900 MHz cell may not have NCD-SSB enabled on the 900 MHz cell because their total bandwidth may be less than 20 MHz.

[0081] A base station that periodically transmits a second synchronization signal can be understood as one that actively and periodically transmits a synchronization signal when indicating the time to be transmitted to the serving base station.

[0082] The configuration data enables the UE to measure the second synchronization signal of the service base station.

[0083] If at least a threshold number of potential target base stations periodically transmit a second synchronization signal, the configuration data can enable the UE to measure only the second synchronization signal of each of the one or more potential target base stations that periodically transmit the second synchronization signal. The configuration data can also enable the UE not to measure the first synchronization signal (e.g., CD-SSB) of any of the potential target base stations (and serving base stations), regardless of whether they periodically transmit the second synchronization signal.

[0084] One or more potential target base stations may all transmit a second synchronization signal on the same predetermined frequency. Therefore, the configuration data allows the UE to measure the second synchronization signal of each of the one or more potential target base stations, which periodically transmit the second synchronization signal on the predetermined frequency.

[0085] If at least a threshold number of potential target base stations periodically transmit a second synchronization signal, the configuration data can enable the UE to perform measurements only on a predetermined frequency.

[0086] If the number of potential target base stations is below a threshold number and they are periodically transmitting a second synchronization signal, the configuration data can enable the UE to measure the first synchronization signal of each of one or more potential target base stations that are not periodically transmitting a second synchronization signal.

[0087] The configuration data enables the UE to measure the first synchronization signal of each of one or more potential target base stations, and to measure the second synchronization signal of each of one or more potential target base stations that periodically transmits a second synchronization signal.

[0088] The second synchronization signal can be transmitted at a different frequency than the first synchronization signal. Therefore, the configuration data enables the UE to measure the second synchronization signal of each of one or more potential target base stations that periodically transmit the second synchronization signal at a predetermined frequency, and to measure the first synchronization signal of each of one or more potential target base stations at different frequencies.

[0089] The configuration data allows the UE to perform measurements at multiple different frequencies.

[0090] One or more potential target base stations may transmit the first synchronization signal on the same predetermined frequency as each other (but different from the predetermined frequency of the second synchronization signal).

[0091] If the number of potential target base stations is less than a threshold number and they periodically transmit a second synchronization signal (causing the UE to need to measure the first synchronization signal of some of the potential target base stations), the configuration data can enable the UE to measure the first and second synchronization signals of both potential target base stations that periodically transmit the first and second synchronization signals.

[0092] In some examples, the configuration data enables the UE to measure at least one synchronization signal from each of one or more potential target base stations; in other examples, the UE may not measure signals from some of the potential target base stations.

[0093] For example, if there is only one potential target base station that does not transmit NCD-SSB, the UE can ignore that base station and only measure the signal from the base station that transmits NCD-SSB. In other words, since performing measurements on two different frequencies may increase the scheduling complexity of the base stations and reduce the data rate of the UE, it may be preferable to measure only NCD-SSB, rather than measuring NCD-SSB on one frequency and CD-SSB on different frequencies, simply to measure at least one synchronization from a potential target base station that does not transmit NCD-SSB.

[0094] Neighboring base stations can be configured to communicate with each other via an X2 or Xn interface. In particular, a serving base station can be configured to communicate with each of one or more potential target base stations via an X2 or Xn interface.

[0095] For example, neighboring base stations may transmit indications via the X2 or Xn interface regarding whether they periodically transmit the second synchronization signal. Base stations may also transmit information regarding the number of RedCap UEs served by the base station and their traffic load via the X2 or Xn interface, and may receive corresponding information in return. Base stations may also transmit instructions or requests via the X2 or Xn interface to enable / disable the periodic transmission of the second synchronization signal.

[0096] Indicating whether the corresponding base station periodically transmits a second synchronization signal may include transmitting one or more of the following messages from the corresponding base station to the serving base station: Change the message. Xn establishes a response message, Xn establishes a request message, and NG-RAN node configuration update message.

[0097] If the corresponding base station is periodically transmitting the second synchronization signal, the indication of whether the corresponding base station is periodically transmitting the second synchronization signal may include an indication of transmitting one or more of the following: The absolute frequency of the second synchronization signal, The periodicity of the second synchronization signal, The time offset of the second synchronization signal relative to the first synchronization signal, and The second synchronization signal has a frequency offset relative to the first synchronization signal.

[0098] The configuration data transmitted that enables the UE to measure the second synchronization signal of a potential target base station may include an indication of the frequency at which the second synchronization signal is transmitted.

[0099] The configuration data transmitted to enable the UE to measure the first synchronization signal of a potential target base station may include an indication of the frequency at which the UE should measure the first synchronization signal. The absolute frequency of the CD-SSB may already be known to the UE and therefore may not need to be transmitted to the UE.

[0100] A base station can be configured to facilitate synchronization of multiple UEs. The multiple UEs may include at least one UE of a first capability type. The method may further include periodically transmitting a first synchronization signal. The method may further include determining a network traffic level transmitted via the base station and associated with the at least one UE of the first capability type. The method may further include selectively and periodically transmitting one or more additional synchronization signals based on the network traffic level transmitted via the base station and associated with the at least one UE of the first capability type. The one or more additional synchronization signals may include a second synchronization signal.

[0101] As described above, if there is sufficient demand, the base station can selectively enable a second synchronization signal (e.g., NCD-SSB). Additionally, if there is sufficient demand, the base station can selectively enable other additional synchronization signals. For example, the base station can activate a third synchronization signal, a fourth synchronization signal, and so on. The first synchronization signal can be CD-SSB, and the second and subsequent synchronization signals can be NCD-SSB.

[0102] Each of one or more potential target base stations can be configured to selectively and periodically transmit one or more additional synchronization signals based on the level of network traffic transmitted via the respective base station. The one or more additional synchronization signals may include a second synchronization signal.

[0103] Optionally, the network traffic level transmitted via the corresponding base station can be a network traffic level associated with one or more UEs of the first capability type (e.g., UEs capable of measuring NCD-SSB).

[0104] The threshold number can be expressed as a threshold proportion of the total number of potential target base stations.

[0105] The threshold ratio can be 100%.

[0106] In other words, if all base stations in one or more potential target base stations periodically transmit the second synchronization signal, the configuration data allows the UE to measure the second synchronization signal of each of the one or more potential target base stations, and if none of the one or more potential target base stations periodically transmit the second synchronization signal, the configuration data allows the UE to measure the first synchronization signal of each of the one or more potential target base stations that do not periodically transmit the second synchronization signal.

[0107] The method may further include transmitting an instruction from the serving base station to at least one potential target base station that does not periodically transmit the second synchronization signal, in order to enable periodic transmission of the second synchronization signal.

[0108] The instruction may also include the frequency of the second synchronization signal.

[0109] The serving base station can command (or request) neighboring base stations to enable a second synchronization signal, and can specify the required frequency. The required frequency can be the same as the frequency of the serving base station's second synchronization signal, and / or can be the same as the frequency of the second synchronization signals of one or more other potential target base stations.

[0110] The base station can be configured to facilitate synchronization of multiple UEs. The multiple UEs may include at least one UE of a first capability type. The first capability type may include one or more of the following: Reduced capabilities (RedCap) UE; Enhanced red-capped UEs; and Non-RedCap UE that supports the measurement of a second synchronization signal.

[0111] The frequency of the first synchronization signal can be predetermined and fixed (e.g., defined by a standard). The frequency of the second synchronization signal can be configurable. In one example, the second synchronization signal can be provided at one end of the available spectrum. In another example, an algorithm can be used to allocate the frequency of the second synchronization signal. Base stations can all use common logic to allocate the frequency of the second synchronization signal, making it possible for the frequencies of the second synchronization signals on adjacent base stations to be aligned.

[0112] The method may further include enabling periodic transmission of the second synchronization signal and allocating the frequency of the second synchronization signal based on the frequency of the second synchronization signal of the base station associated with the neighboring cell.

[0113] When a base station is first powered on, there is no initial load, so the second synchronization signal is unlikely to be activated. After the base station is powered on, it can acquire information regarding the second synchronization signals of neighboring base stations (including the frequencies of the second synchronization signals transmitted by neighboring base stations). When the base station's second synchronization signal is unilaterally activated (e.g., based on network traffic levels), the frequency of the second synchronization signal can be set to match the frequencies of the second synchronization signals of one or more neighboring base stations. Alternatively, when the base station's second synchronization signal is activated due to a command received from a commanding base station (e.g., a neighboring base station), the frequency of the second synchronization signal can be set by the commanding base station to match the frequencies of the second synchronization signals of the commanding base station and / or one or more of its neighboring base stations.

[0114] Alternatively, each of the base stations can be configured with a pre-selected frequency for a second synchronization signal.

[0115] Advantageously, if adjacent base stations are each configured to transmit a second synchronization signal on the same frequency, a UE measuring the second synchronization signal of each base station may only need to measure one frequency. This can improve efficiency.

[0116] Measurements taken by the UE of synchronization signals from one or more potential target base stations can be radio resource management (RRM) measurements.

[0117] Each of the first synchronization signal and the second synchronization signal can be a synchronization signal block (SSB). An SSB can include one or more of the following: Primary synchronization signal (PSS); Auxiliary synchronization signal (SSS); Physical Broadcast Channel (PBCH); and Physical Broadcast Channel Demodulation Reference Signal (PBCH DMRS).

[0118] For each of the first synchronization signal and the second synchronization signal, the PBCH may include a Master Information Block (MIB).

[0119] The first synchronization signal may include data that enables the UE to obtain the first system information block (SIB1). The second synchronization signal may not be used to obtain SIB1.

[0120] The first synchronization signal can be associated with the Residual Minimal System Information (RMSI) block. The second synchronization signal can be unassociated with the RMSI block.

[0121] The first synchronization signal can be a cell-defined synchronization signal block (CD-SSB). The second synchronization signal can be a non-cell-defined synchronization signal block (NCD-SSB).

[0122] Each of the first synchronization signal and the second synchronization signal may include multiple parameters.

[0123] The second synchronization signal may include parameters that are different from those of the first synchronization signal.

[0124] Each of the first synchronization signal and the second synchronization signal may include multiple information elements. Each of these multiple information elements may include corresponding multiple parameters.

[0125] The information elements of the second synchronization signal may include one or more of the following parameters: The absolute frequency of the second synchronization signal; The periodicity of the second synchronization signal; and The time offset of the second synchronization signal relative to the first synchronization signal.

[0126] The periodicity of the second synchronization signal may differ from that of the first synchronization signal.

[0127] Configuration data may include SS / PBCH block measurement timing configuration (SMTC).

[0128] Configuration data may include one or more of the following parameters: The absolute frequency of the first synchronization signal; The periodicity of the first synchronization signal; The absolute frequency of the second synchronization signal; The periodicity of the second synchronization signal; and The time offset of the second synchronization signal relative to the first synchronization signal.

[0129] Configuration data may include SS / PBCH block measurement timing configuration (SMTC).

[0130] It also provides a network entity that can be configured to perform the methods described above.

[0131] A computer program comprising instructions is also provided, which, when executed on a processor, cause the processor to perform the methods described above.

[0132] As described above, potential target base stations can be configured to transmit two separate synchronization signals (e.g., synchronization signal blocks (SSBs)). However, there may be some potential target base stations that only transmit the first synchronization signal. As a result, the UE can be provided with configuration data that enables the UE to measure the first synchronization signal of some of the potential target base stations (e.g., those that do not transmit the second synchronization signal) and the second synchronization signal of some other potential target base stations (e.g., those that transmit the second synchronization signal).

[0133] Measuring the first synchronization signal of some of the potential target base stations may include measuring the signal at a specific frequency. If all potential target base stations transmit the first synchronization signal at the same frequency, then the UE can then measure the first synchronization signal from each potential target base station (including those transmitting the second synchronization signal). As a result, the UE can measure both the first and second synchronization signals of potential target base stations that periodically transmit both the first and second synchronization signals.

[0134] Each base station can be associated with a cell. Each cell can have an identifier. Synchronization signals may include the identifier of the associated potential target cell. A UE can receive multiple synchronization signals from multiple potential target cells and send one or more measurement report messages to its serving cell. For each received synchronization signal, one or more measurement report messages may include a measurement report entry, which includes signal strength data and the identifier of the potential target cell associated with the synchronization signal. The cell identifier can be locally unique, enabling the UE and / or serving cell to uniquely identify the potential target cell involved in each synchronization signal.

[0135] If a measurement report message includes more than one measurement report entry with the same cell identifier, the prior art method assumes that the UE has received signals from two different cells, and that the two cells simultaneously visible to the UE have been assigned the same cell identifier. This can cause problems if the signal strength of one of these cells meets the handover conditions, as the serving cell may not be able to uniquely identify which cell has met the handover conditions and may be unable to perform the handover, or may attempt to hand the UE to the wrong cell, potentially leading to communication failure. Therefore, in such cases, the prior art method may issue an alert. Alternatively or additionally, the prior art method could increment a counter, such as an OAM counter, to document the detected unusual conditions.

[0136] Compared with existing technologies, the proposed method recognizes that two different synchronization signals can be received that relate to the same cell association (whereas previously, each cell might only be associated with one synchronization signal).

[0137] A method for receiving synchronization signal measurements in a cellular network is provided. The method includes receiving one or more measurement report messages from a user equipment (UE), the measurement report messages including a first measurement report entry relating to a first synchronization signal of a first potential target cell. The first measurement report entry includes a cell identifier of the first potential target cell. The one or more measurement report messages also include a second measurement report entry relating to a second synchronization signal of the first potential target cell. The second measurement report entry includes the cell identifier of the first potential target cell. The method further includes identifying that the one or more measurement report messages include two measurement report entries, each including the same cell identifier, and, in response, determining whether to issue an alarm and / or increment a counter. The method also includes determining that the two measurement report entries relate to the same cell, and suppressing the alarm.

[0138] In other words, if two measurement report entries involve the same cell, the proposed method can suppress alarms.

[0139] The first and second measurement report entries can be in the same measurement report message. In other words, a single measurement report message can include two measurement report entries, each containing the same cell identifier. Whether the measurement report entries are sent by the UE in a single measurement report message or in separate measurement report messages depends on the reporting configuration. The UE can combine multiple measurement report entries in the same measurement report message simultaneously, or it can send different measurement report messages at different times.

[0140] Each measurement report entry can correspond to a synchronization signal received by the UE. The UE can send measurement report entries corresponding to the first synchronization signal of each potential target base station in a single measurement report message (these entries can correspond to a first measurement object configured on the UE, which causes the UE to measure the synchronization signal at the frequency of each of the first synchronization signals). The UE can also send measurement report entries corresponding to the second synchronization signal of each potential target base station (each potential target base station transmitting a second synchronization signal) in a separate measurement report message (these entries can correspond to a second measurement object configured on the UE, which causes the UE to measure the synchronization signal at the frequency of each of the second synchronization signals).

[0141] Configuration data can define one or more measurement objects. Each measurement object can involve a specific frequency. Measurement report messages can include measurements (e.g., RSRP, RSRQ) of the synchronization signal (which may also be referred to as a "reference signal") associated with each measurement object. The UE can send a measurement report message to the serving base station containing multiple measurement report entries, each entry corresponding to a specific synchronization signal of a particular potential target base station.

[0142] Determining that two measurement report entries involve the same cell may include determining different synchronization signals (i.e., a first synchronization signal and a second synchronization signal transmitted by a base station associated with the cell) for the two measurement report entries involving the same cell.

[0143] Identifying that two measurement report entries pertain to the same cell can be based on information from that cell (such as information transmitted from a base station associated with the potential target cell to a base station associated with the UE's serving cell). For example, the base station associated with the potential target cell can provide an indication that it is periodically transmitting a first synchronization signal and a second synchronization signal.

[0144] The indication may also include an indication of the corresponding frequency of each of the synchronization signals.

[0145] Information can be transmitted via the X2 and / or Xn interfaces.

[0146] This method can be performed by a base station associated with the UE's serving cell.

[0147] Two measurement report entries involving the same cell can be the first measurement report entry and the second measurement report entry.

[0148] Identifying one or more measurement report messages includes two measurement report entries, each of which relates to the same cell. These two measurement report entries may include the same cell identifier.

[0149] The method may further include receiving one or more additional measurement report messages (e.g., from different UEs). The method may also include identifying that one or more additional measurement report messages include two measurement report entries, each including the same cell identifier, and, in response, determining whether to issue an alarm and / or increment a counter. The method may further include determining that the two measurement report entries in one or more additional measurement report messages involve different cells, and issuing an alarm and / or incrementing a counter.

[0150] In other words, if the measurement report entry involves different synchronization signals associated with the same cell, the method can suppress alarms (and / or increment counters), but if the measurement report entry involves different cells that have been mistakenly assigned the same identifier, the method can issue alarms (and / or increment counters).

[0151] If a potential target cell transmits only a synchronization signal, then the measurement report entry may involve different cells, and an alarm may be issued (and / or the counter may be incremented).

[0152] Determining that the two measurement report entries involve different cells may include receiving an indication from the cell that it has not transmitted a second synchronization signal (e.g., NCD-SSB).

[0153] The method may further include transmitting configuration data to the UE, the configuration data causing the UE to measure a first synchronization signal and a second synchronization signal of the first potential target cell.

[0154] The first synchronization signal of the first potential target cell can be transmitted on a first frequency, and the second synchronization signal of the first potential target cell can be transmitted on a second frequency. The configuration data enables the UE to measure the signals on both the first and second frequencies.

[0155] The UE can be configured to measure the frequency of transmitted synchronization signals, rather than being configured to read a specific synchronization signal. As a result, the UE can receive all synchronization signals transmitted from cells within the UE's range at the same frequency.

[0156] Configuration data may include SS / PBCH block measurement timing configuration (SMTC).

[0157] Configuration data may include one or more of the following parameters: The absolute frequency of the first synchronization signal; The periodicity of the first synchronization signal; The absolute frequency of the second synchronization signal (or the frequency offset of the second synchronization signal relative to the first synchronization signal); The periodicity of the second synchronization signal; and The time offset of the second synchronization signal relative to the first synchronization signal.

[0158] The method may further include transmitting an indication from the first potential target cell to the UE's serving cell that the first potential target cell is periodically transmitting a second synchronization signal.

[0159] This instruction can be transmitted via the X2 or Xn interface.

[0160] Each of the two measurement report entries may also include a measurement of the signal strength relating to the corresponding synchronization signal.

[0161] Measurement report entries may include Radio Resource Management (RRM) measurements.

[0162] Each of the first synchronization signal and the second synchronization signal can be a synchronization signal block, including: Primary synchronization signal (PSS); Auxiliary synchronization signal (SSS); Physical Broadcast Channel (PBCH); and Physical Broadcast Channel Demodulation Reference Signal (PBCH DMRS).

[0163] For each of the first synchronization signal and the second synchronization signal, the PBCH may include a Master Information Block (MIB).

[0164] The first synchronization signal may include data that enables the UE to obtain the first system information block (SIB1). The second synchronization signal may not be used to obtain SIB1.

[0165] The first synchronization signal can be associated with a Residual Minimal System Information (RMSI) block. The second synchronization signal can be independent of an RMSI block.

[0166] The first synchronization signal can be a cell-defined synchronization signal block (CD-SSB). The second synchronization signal can be a non-cell-defined synchronization signal block (NCD-SSB).

[0167] Each of the first synchronization signal and the second synchronization signal may include multiple parameters.

[0168] The second synchronization signal may include parameters that are different from those of the first synchronization signal.

[0169] Each of the first synchronization signal and the second synchronization signal may include multiple information elements. Each of these multiple information elements may include corresponding multiple parameters.

[0170] The information elements of the second synchronization signal may include one or more of the following parameters: The absolute frequency of the second synchronization signal; The periodicity of the second synchronization signal; and The time offset of the second synchronization signal relative to the first synchronization signal.

[0171] The periodicity of the second synchronization signal may differ from that of the first synchronization signal.

[0172] It also provides a network entity that can be configured to perform the methods described above.

[0173] A computer program comprising instructions is also provided, which, when executed on a processor, cause the processor to perform the methods described above.

[0174] A method for a base station to facilitate handover of user equipment (UE) is also provided. The base station is configured to periodically transmit a first synchronization signal and selectively periodically transmit a second synchronization signal. The method includes: Based on network traffic levels, it was determined that a procedure should be initiated to disable the periodic transmission of the second synchronization signal; Based on measurements of the second synchronization signal taken by the UE, it is determined that a handover procedure for the UE has been initiated, wherein the base station is the target base station for the handover procedure; and Modify one or more programs and complete the handover process to make the base station become the UE's serving base station.

[0175] The base station can be configured to selectively and periodically transmit a second synchronization signal based on network traffic levels associated with one or more UEs of a first capability type.

[0176] Network traffic levels associated with one or more UEs of the first capability type may include: Network traffic levels transmitted via base stations and associated with one or more UEs of the first capability type; and Network traffic levels transmitted via one or more base stations corresponding to one or more neighboring cells and associated with a UE of the first capability type.

[0177] The base station can be configured to communicate with multiple UEs, wherein the multiple UEs include at least one UE of a first capability type and at least one UE of a second capability type, wherein: Compared to the second ability type, the first ability type corresponds to a reduced ability; Compared to the second capability type, the first capability type is not a downgrade and corresponds to a UE compatible with the second synchronization signal; or The first capability type corresponds to a UE compatible with the second synchronization signal, and at least one UE of the first capability type includes at least one UE with reduced capability compared to the second capability type and at least one UE with no reduced capability compared to the second capability type.

[0178] The UE whose handover procedure has been initiated can be a UE of the first capability type.

[0179] The measurement of the second synchronization signal taken by the UE can be a radio resource management (RRM) measurement.

[0180] In some alternative examples, the measurement of the second synchronization signal taken by the UE can be a radio resource control (RRC) measurement.

[0181] Each of the first synchronization signal and the second synchronization signal can be a synchronization signal block, including: Primary synchronization signal (PSS); Auxiliary synchronization signal (SSS); Physical Broadcast Channel (PBCH); and Physical Broadcast Channel Demodulation Reference Signal (PBCH DMRS).

[0182] For each of the first synchronization signal and the second synchronization signal, the PBCH may include a Master Information Block (MIB).

[0183] The first synchronization signal may include data that enables the UE to obtain the first system information block (SIB1). The second synchronization signal may not be used to obtain SIB1.

[0184] The first synchronization signal can be associated with the Residual Minimal System Information (RMSI) block. The second synchronization signal can be unassociated with the RMSI block.

[0185] The first synchronization signal can be a cell-defined synchronization signal block (CD-SSB). The second synchronization signal can be a non-cell-defined synchronization signal block (NCD-SSB).

[0186] Each of the first synchronization signal and the second synchronization signal may include multiple parameters.

[0187] The second synchronization signal may include parameters that are different from those of the first synchronization signal.

[0188] Each of the first synchronization signal and the second synchronization signal may include multiple information elements, wherein each of the multiple information elements includes corresponding multiple parameters.

[0189] The information elements of the second synchronization signal may include one or more of the following parameters: The absolute frequency of the synchronization signal; The periodicity of the synchronization signal; and The time offset of the second synchronization signal relative to the first synchronization signal.

[0190] The periodicity of the second synchronization signal may differ from that of the first synchronization signal.

[0191] In some examples, the periodicity of the second synchronization signal can be greater than that of the first synchronization signal. In other examples, the periodicity of the second synchronization signal can be less than that of the first synchronization signal.

[0192] Determining that the handover procedure has been initiated may include receiving carrier resource information from a neighboring base station (e.g., via network interface Xn or X2) that identifies a portion of the carrier bandwidth (BWP) associated with the second synchronization signal.

[0193] In some examples, the bandwidth portion (BWP) may include a second synchronization signal. In other words, the NCD-SSB may be within the BWP. In other examples, the second synchronization signal may be separate from the BWP.

[0194] Modifying one or more programs may include modifying the program to disable the periodic transmission of the second synchronization signal.

[0195] Modifying the procedure to disable the periodic transmission of the second synchronization signal may include delaying (or “suppressing” or “temporarily suppressing”) the procedure to disable the periodic transmission of the second synchronization signal, such that the periodic transmission of the second synchronization signal continues while the switching procedure is in progress.

[0196] In the example described above, although the base station determines that the periodic transmission of the second synchronization signal should be disabled based on the network traffic level, the periodic transmission of the second synchronization signal can continue while the handover procedure is in progress.

[0197] The method may also include disabling the periodic transmission of the second synchronization signal after the switching procedure is completed.

[0198] The handover procedure may include a handover procedure based on a second synchronization signal.

[0199] Modifying one or more programs may include modifying the switching program.

[0200] Modifying the handover procedure may include providing the UE with a configuration that enables the UE to measure a first synchronization signal (instead of a second synchronization signal).

[0201] The configuration may include SS / PBCH block measurement timing configuration (SMTC).

[0202] The configuration may include one or more of the following parameters: The absolute frequency of the first synchronization signal; The periodicity of the first synchronization signal; and Time offset of the first synchronization signal.

[0203] The time offset of the first synchronization signal can be relative to the total resource block grid. The time offset can be provided based on the number of subcarriers.

[0204] The method may also include disabling the periodic transmission of the second synchronization signal while the switching procedure is in progress (before the switching procedure is completed).

[0205] The handover procedure may include a handover procedure based on the first synchronization signal.

[0206] It also provides a network entity that can be configured to perform the methods described above.

[0207] Computer software including instructions is also provided, which, when executed on a processor, cause the processor to perform the methods described above. Attached Figure Description

[0208] The invention will be described with reference to the non-limiting examples illustrated in the following figures.

[0209] Figure 1 The illustration shows a telecommunications network based on a specific example.

[0210] Figure 2 The flowchart for the example method is shown. Detailed Implementation

[0211] To serve use cases between eMBB and IoT, new device capability types have been defined. In some scenarios, a new device capability type represents a reduced capability compared to other devices in the network designed to use eMBB. Therefore, devices with a new device capability type are sometimes referred to as "RedCap" devices. The new device capability type may be suitable for use cases including sensor devices, wearables, and surveillance cameras. By defining specific capabilities for the new device capability type (which may be reduced compared to eMBB), devices with lower complexity can be designed to use the new device capability type. By considering such capabilities when designing devices, the complexity and overall cost of such devices can be reduced.

[0212] As described above, devices operating under the new device type have reduced capabilities compared to devices operating according to the eMBB use case. The new device capability type can impose constraints and limitations to achieve these reduced capabilities. In some examples, the new device capability type has the following limitations: • UL / DL bandwidth up to 20 MHz, • The number of MIMO layers is reduced, and there are a maximum of 2 RX / branch. • Reduced modulation order, and • Carrier aggregation or dual connectivity is not supported.

[0213] UE capability information can be transmitted to the network via information elements. In some examples, the RedCapParameters information element can be used. In other examples, different information elements can be used to transmit UE capabilities.

[0214] The RedCapParameters information element definition, based on a specific example, is reproduced below: .

[0215] The IE RedCap parameter indicates the UE capabilities supported by the RedCap UE. This IE can be used to provide RedCap capability information to the network.

[0216] Given the nature of devices that may be classified as RedCap devices (sensors, surveillance devices, wearable devices, and the like), a large number of RedCap devices are expected to exist in the network after support for these devices is implemented. Efforts have been made in standardization to achieve coexistence with legacy devices and to provide mechanisms for these devices to offload and utilize network resources. A specific enhancement in Release 17 for RedCap UEs is the introduction of an additional Non-Cell Defined Synchronization Block (NCD-SSB). In some examples, the NCD-SSB differs from the legacy Cell Defined Synchronization Block (CD-SSB) because the NCD-SSB is not associated with the SIB. The NCD-SSB is configured by the network in a Bandwidth Part (BWP) to allow RedCap UEs operating in that BWP to use the SSB for purposes they would otherwise use the CD-SSB of the serving cell (e.g., for synchronization, measurement, radio link monitoring). This additional synchronization block provides advantages. For example, it provides the network with the flexibility to offload some or all of RedCap traffic in a cell.

[0217] In some examples, the difference between NCD-SSB and CD-SSB lies in the parameters defined in the nonCellDefiningSSB information element.

[0218] The definition of the NonCellDefiningSSB information element, based on a specific example, is reproduced below: .

[0219] The IE NonCellDefiningSSB is used to configure the NCD-SSB to be used when the UE is operating in a RedCap-specific initial BWP or a dedicated BWP.

[0220] The following table provides field descriptions for NonCellDefiningSSB IE: .

[0221] In release 18, this enhancement is expanded to cover both non-RedCap UEs and eRedCap UEs (enhanced RedCap).

[0222] The ERedCapParameters information element can be used to indicate UE capabilities supported by the eRedCap UE. The ERedCapParameters information element definition for a specific example is reproduced below: .

[0223] The RF-Parameters information element can be used to convey RF-related capabilities for NR operations (e.g., for non-RedCap UEs). In release 18, this IE was expanded to include NCD-SSB capabilities (e.g., via the ncd-SSB-BWP-Wor-r18 field).

[0224] Transmitting additional synchronization blocks with characteristics similar to legacy synchronization blocks increases overall network signaling overhead, network energy consumption, and reduces the amount of network resources available for scheduling data transmission. Therefore, a mechanism is proposed to selectively control NCD-SSB transmission. This mechanism allows network operators to benefit from the advantages associated with using NCD-SSB while balancing these benefits and disadvantages.

[0225] To control NCD-SSB transmission, a method is proposed that takes into account the number of RedCap UEs camped in the cell, their traffic load represented in the total cell, and similarity information from neighboring cells. In some examples, NCD-SSB is transmitted after a specific threshold is met, based on the factors mentioned above, and is not transmitted whenever there is almost no RedCap traffic.

[0226] Figure 1The illustration depicts a telecommunications network according to a specific example. Three adjacent cells are shown, each with a corresponding base station 100A, 100B, and 100C. Within each cell, there are one or more UEs. Each UE can be a first-capability type UE (e.g., a RedCap UE) 120AA, 120AB, 120CA, 120CB, and 120CC, or a second-capability type UE (e.g., a mobile phone configured for enhanced mobile broadband) 110AA, 110AB, 110BA, and 110CA. Base stations 100A, 100B, and 100C can communicate via an X2 or Xn interface 150.

[0227] The purpose of including neighboring cells as one of the criteria for transmission is that although there may be no traffic in a cell, its neighboring cells may have RedCap traffic, and these UEs may perform neighboring cell measurements for handover purposes. For example, such as Figure 1 As illustrated, base station 100B currently does not serve any RedCap UEs. However, there are RedCap UEs in neighboring cells, many of which can switch to base station 100B. In particular, RedCap UEs 120AB, 120CB, and 120CC can switch to base station 100B. Therefore, although RedCap UE traffic is low at base station 100B, it may be advantageous for base station 100B to transmit NCD-SSB.

[0228] Figure 2 The diagram below shows a flowchart illustrating the example method. The program behaves as follows: At step 201, the network measures the number of RedCap UEs by their early identification during initial access. This value is stored as a critical parameter. The traffic load attributed to RedCap UEs in the cell is also measured and updated as another (or alternative) critical parameter.

[0229] The RedCapParameters information element is used to indicate the UE capabilities supported by a RedCap UE. This can be used to identify UEs in a cell that support RedCap. UE capabilities can be transmitted to the base station in one or more other information elements. For example, the UE-NR-Capabilities information element may include this information.

[0230] Traffic load associated with RedCap UE can be monitored separately from the rest of the network traffic.

[0231] At step 202, the base station exchanges information regarding the number of RedCap UEs and traffic load with its neighboring cells via the X2 (or Xn) interface, and receives the corresponding information back. New signaling parameters (or multiple parameters) can be introduced through the X2 or Xn signaling interface to transmit this information.

[0232] At step 203, the network decides whether to transmit the NCD-SSB. This decision is based on the number of RedCap UEs connected to the base station, the traffic load attributable to the RedCap UEs, and / or information from neighboring cells. These values ​​may be compared to one or more thresholds defined at the base station.

[0233] The threshold value can be set by the network through the implementation method, or it can be set according to the value in the standard.

[0234] The decision to transmit NCD-SSB based on traffic load and / or the number of connected RedCap UEs can be left to the gNB (each individual gNB can make the decision based on thresholds configured individually), or it can be controlled by the OAM (gNBs belonging to the same OAM center can follow the same decision / policy and use the same thresholds).

[0235] The decision to enable one (or more) non-cell-defined SSBs in a cell can depend on the number of UEs capable of using NCD-SSB connections and / or the network traffic levels attributable to those UEs. Similarly, the decision can also be based on the number of UEs that cannot use NCD-SSBs (UEs requiring the bandwidth portion containing the cell-defined SSB, such as “non-RedCap” UEs) and / or the network traffic levels attributable to those UEs. The number of UEs and network traffic levels may differ across cells. Therefore, the number of NCD SSBs in a cell can vary dynamically based on one or more of these factors. In other words, as load increases, the base station can activate a second synchronization signal (the first NCD-SSB) (e.g., at one end of the spectrum). If the load increases further, the base station can activate a third synchronization signal (e.g., the second NCD-SSB). If the load increases even further, additional synchronization signals (e.g., NCD SSBs) can be enabled.

[0236] To enable the UE to measure one or more synchronization signals (which can be CD-SSB and / or NCD-SSB), the serving base station can send configuration data to the UE. The configuration data can define one or more measurement objects (MOs), each of which includes the frequency at which the UE should measure the synchronization signal. For each measurement object, the UE can report the measurement of one or more synchronization signals received at that frequency to the serving base station in a measurement report message.

[0237] If the network wants the UE to use NCD-SSB for serving cell measurements, the network can configure the measurement object on the frequency corresponding to the serving cell's NCD-SSB.

[0238] For neighboring cell measurements, it depends on the network to configure one or more MOs on the frequencies corresponding to the CD-SSB and / or one or more NCD-SSBs of the neighboring cells.

[0239] If all neighboring cells are transmitting NCD-SSB on the same frequency, the UE can use a single MO to make all measurements.

[0240] If one or more neighboring cells are not transmitting NCD-SSB, then the UE may need to measure the CD-SSB of those cells. For this purpose, the network can configure separate measurement targets on the frequencies corresponding to the CD-SSBs.

[0241] If one or more neighboring cells are transmitting NCD-SSB to the serving cell, but at different frequencies, the network can configure separate measurement objects on the frequencies corresponding to the NCD-SSBs of one or more neighboring cells.

[0242] If the UE uses a BWP that includes the NCD-SSB, then any measurement on the CD-SSB is an "intER frequency" measurement. If the UE (which has a BWP that includes the NCD-SSB) must measure the CD-SSB (e.g., to perform neighboring cell measurements), it may be necessary to use some form of "measurement gap".

[0243] Similarly, if a UE with a BWP containing the first NCD-SSB on the first frequency also needs to measure the second NCD-SSB on the second (different) frequency, it may be necessary to perform neighboring cell measurements using a "measurement gap".

[0244] Measurement gaps can increase scheduling complexity and degrade UE performance and throughput (and actual network capacity). Therefore, efficiency can be improved by avoiding measurement gaps. It would be useful if the serving base station knew whether all neighboring cells (on the UE's frequency band) were transmitting NCD-SSBs on the same frequency as the NCD-SSB the UE was using (the serving cell's NCD-SSB). In this case, the UE might not need to measure the CD-SSB or any NCD-SSBs on different frequencies. Therefore, measurement gaps might not be required (and the MO corresponding to the CD-SSB could be eliminated).

[0245] TS 38.423 (which is merged by reference) describes that Xn setup request / response (and NG-RAN node configuration update) signaling does not carry any information about the presence / absence of the NCD-SSB (nor its carrier frequency). The Redcap information in these messages is only about the (e)Redcap UE prohibition setting of the transmitting cell.

[0246] In a first aspect, the proposed method improves upon the current state of the art by transmitting to the serving base station an indication of whether each of the neighboring base stations periodically transmits a second synchronization signal (and optionally, the frequency of the second synchronization signal). This indication can be added to Xn setup request / response and NG-RAN node configuration update messages.

[0247] The proposed method facilitates the dynamic exchange of this information, enabling the serving base station to configure the UE using this information for more efficient measurement. To this end, the serving base station can configure one or more measurement objects on the UE at one or more predetermined frequencies.

[0248] The base station can also use this information to coordinate its second synchronization signal, so that each base station transmits the second synchronization signal on the same frequency. Advantageously, this can reduce the number of different frequencies of the synchronization signal that the UE needs to measure, and thus improve the efficiency of the UE.

[0249] As indicated above, there are situations where the UE is using the NCD-SSB of the serving base station cell, but one or more neighboring cells are not transmitting NCD-SSB (or at least not transmitting NCD-SSB on the same frequency). Therefore, the UE can be configured to measure the CD-SSB of such neighboring cells. For this purpose, the network can configure the UE with separate MOs for CD-SSB and NCD-SSB (on separate frequencies).

[0250] In this scenario, there may still be one or more neighboring cells transmitting both CD-SSB and NCD-SSB. In this case, the UE can report the signal strength of both CD-SSB and NCD-SSB from neighboring cells. The NCD SSB(s) in the cell use the same Physical Cell ID (PCI) as the cell-defined SSB. Therefore, each measurement report entry will carry the same PCI.

[0251] Prior to the introduction of NCD-SSB, the serving gNB would detect two measurement report entries with the same PCI and determine that this was an unusual situation indicating an error. For example, if two neighboring cells were incorrectly assigned the same PCI, the gNB might receive a measurement report message from the UE containing two measurement report entries for the same PCI. In this case, the gNB could notify the O&M and / or trigger automatic neighbor cell reporting to diagnose the problem.

[0252] In the second aspect, the proposed method improves upon the prior art by detecting that the measurement report message from the UE includes two measurement report entries with the same PCI, and suppressing alarms (and / or counter increments) if this is normal (e.g., because the reports involve CD-SSB and NCD-SSB of the same cell).

[0253] If a UE (e.g., a Redcap UE or a UE without a restricted type [C] release version 18+ bandwidth portion) is using a BWP with an NCD-SSB, and the gNB has configured an MO for both the CD-SSB and the NCD-SSB, then the gNB can accept this situation as normal and will not trigger an alarm, increase the OAM counter, or trigger an automatic neighbor relationship update (e.g., via the automatic neighbor cell reporting function).

[0254] As described in TS 38.331 (which is merged by reference), the NCD-SSB allows RedCap UEs operating in the corresponding BWP to use the NCD-SSB for purposes they would otherwise use with the serving cell's CD-SSB (e.g., for synchronization, measurement, radio link monitoring). All of these operations are in RRC_Connected mode because there is no standard to support idle / inactive.

[0255] These types of measurements can form the basis for handover decisions, and the following example scenarios may occur depending on the state of NCD-SSB transmissions at the serving and target cells: • The UE performs RRM measurements on the NCD-SSB. • The network makes handover decisions based on measurements, specifically the NCD-SSB of neighboring cells. • At the same time, the neighboring cell decided to disconnect NCD-SSB.

[0256] Due to several factors, this scenario is expected to occur very rarely in most cases. One reason is that hysteresis is preferably configured during the on / off state of the NCD-SSB, making handover only infrequent. Therefore, the time interval between the UE taking measurements and the neighboring cell deciding to disconnect the NCD-SSB should be shorter compared to the time during which the NCD-SSB is on and uninterrupted. Thus, the probability of this scenario should be low. Furthermore, the decision to disconnect the NCD-SSB is based on information from neighboring cells, so this decision should only be made if there are relatively few RedCap devices connected in neighboring cells. Therefore, the probability of a RedCap device attempting to hand over to a cell after making the decision to disconnect the NCD-SSB should be low.

[0257] Nevertheless, such a scenario is possible, and when it does occur, the network should be able to manage it. Two solutions are proposed to handle this scenario.

[0258] In the first solution, the target cell is not allowed to disable NCD-SSB transmission until the finalize handover.

[0259] After a handover decision is made (e.g. by a base station in the network), the source cell transmits the frequency information of the BWP corresponding to the NCD-SSB (i.e., an indication of the NCD-SSB that should not be turned off) to the target cell through a network interface (e.g., X2 or Xn).

[0260] In the second solution, the target cell provides a modified measurement configuration during handover. The target cell can send a configuration that allows handover to be performed using either the target cell's initial BWP or a different BWP that does not correspond to the NCD-SSB. An SS / PBCH block measurement timing configuration (SMTC) can be configured for the UE to cover the absolute frequency of the CD-SSB. Additional configurations (such as periodicity and offset) can be provided to enable the UE to perform measurements on another SSB (e.g., the CD-SSB) instead of the NCD-SSB. Once the configuration is provided, the base station can proceed to disable NCD-SSB transmission based on the criteria discussed above (traffic, thresholds, and the like).

[0261] For many attributes of the corresponding CD-SSB (e.g., ssb-PositionsInBurst, PCI, ssb-PBCH-BlockPower), NCD-SSB has the same values. However, for NCD-SSB, the values ​​of attributes configured in NonCellDefiningSSB-r17 IE may differ. These attributes include (as discussed above): • absoluteFrequencySSB, • ssb-Periodicity, and • ssb-TimeOffset.

[0262] If the UE performs measurements on the NCD-SSB, and the attributes of the NCD-SSB differ from those of the CD-SSB, then comparing measurements on the NCD-SSB with those on the CD-SSB is inaccurate. Whatever measurements are used for handover decisions (measurements prior to the handover) should be consistent during the handover. Otherwise, the handover is based on arbitrary measurements or measurements that are no longer valid, leading to ambiguity in the handover decision.

[0263] In some examples, a RedCap UE may include simplified components compared to other UEs not designated as RedCap (which can communicate via eMBB). While a "RedCap" UE may be referred to as a "reduced capability" UE, the UE itself is still capable of communicating via eMBB (at a higher data rate). A UE may be designated as a RedCap UE for several reasons, including power saving, reduced network load, and the like. In some examples, a RedCap UE may include simplified components and requires reduced power consumption.

[0264] Furthermore, devices that are not designated as "RedCap" UEs but are still capable of using the second synchronization signal can use the second synchronization signal. This can conserve network resources and / or enable the device to implement power-saving techniques.

[0265] Any of the methods described herein can be implemented as a computer program. This computer program can be configured to control RAN entities (e.g., network nodes) and / or UEs to perform any of the methods disclosed herein. RAN entities (e.g., network nodes) and / or UEs of a cellular network may also be provided, configured to operate according to certain methods disclosed herein. For example, the RAN entity may include a processor and at least one communication interface, particularly including one of a transmitter and a receiver, or both. A UE may also be provided, configured to operate according to certain methods disclosed herein. The UE may also include a processor and at least one communication interface, particularly including one of a transmitter and a receiver, or both.

[0266] Although specific embodiments have now been described, those skilled in the art will understand that various modifications and variations are possible. For example, while this disclosure has been described with respect to existing network architectures, it will be understood that changes to the architecture (and / or terminology) are possible, but this disclosure still applies in such cases. Similarly, any combination of particular features shown with reference to one or more embodiments is also provided, even if such combination is not explicitly detailed herein.

[0267] A base station (BS) generally refers to a fixed station that communicates with a UE and / or another BS, and exchanges various types of data and control information with the UE and another BS. Depending on the protocol, standard, context, or technology, a BS may be referred to as an Advanced Base Station (ABS), Base Transceiver Station (BTS), Radio Base Station, Radio Transceiver, Transceiver Function, Basic Service Set (BSS), Extended Service Set (ESS), Access Point (AP), Node B (NB), eNode B (eNB), gNode B (gNB), Transmit and Receive Point (TRP), Processing Server (PS), or some other suitable terminology. In some examples, a base station may include two or more transceivers, which may or may not be co-located. Each transceiver may communicate on the same or different carrier frequencies within the same or different frequency bands.

[0268] For example, in the case of a server or network entity in this application, this can actually be a pair of server or network entities (a primary entity and a failover entity) for redundancy.

[0269] In this invention, a node refers to a fixed point capable of transmitting / receiving radio signals through communication with a UE. Various types of base stations (such as those described above) can be used as nodes, regardless of the terminology used. In other examples, a node can be a repeater, a retransmitter, and the like.

[0270] In this invention, the UE can be a fixed or mobile device. Examples of UEs include various devices that transmit and receive user data and / or various types of control information to and from a base station. The UE can be referred to as a terminal equipment (TE), mobile station (MS), mobile terminal (MT), user terminal (UT), subscriber station (SS), wireless device, personal digital assistant (PDA), wireless modem, handheld device, etc.

[0271] While the above methods are described for 5G / NR networks, these methods, technologies, equipment, and systems can be applied to a variety of radio multiple access systems. Examples of multiple access systems include CDMA, FDMA, TDMA, OFDMA, SC-FDMA, and MC-FDMA. CDMA can be implemented using radio technologies such as UTRA or CDMA2000. TDMA can be implemented using radio technologies such as GSM, GPRS, or EDGE. OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA. UTRA is part of UMTS. 3GPP LTE is part of E-UMTS using E-UTRA. 3GPP LTE uses OFDMA in the downlink and SC-FDMA in the uplink. LTE-A is an evolution of 3GPP LTE. 3GPP NR uses OFDMA for both downlink and uplink and can operate in both FDD and TDD modes. For ease of description, it is assumed that the present invention is applied to 3GPP NR. However, the technical features of the present invention are not limited thereto. For example, although the following detailed description is given based on a mobile communication system corresponding to the 3GPP NR system, aspects of the present invention that are not specific to 3GPP NR are also applicable to other mobile communication systems.

[0272] In this invention, a cell refers to a geographical area to which one or more nodes provide communication services. Therefore, in this invention, communicating with a specific cell can mean communicating with a gNB or node that provides communication services to that specific cell. Furthermore, the channel state / quality of a specific cell refers to the channel state / quality of the channel or communication link formed between the gNB or node providing communication services to the specific cell and the UE. The UE can measure the DL channel state received from the specific node using one or more cell-specific reference signals (CRS) transmitted on CRS resources and / or one or more channel state information reference signals (CSI-RS) transmitted on CSI-RS resources, which are assigned to the specific node by one or more antenna ports of the specific node. Meanwhile, the 3GPP system uses the concept of a cell to manage radio resources and distinguish between cells associated with radio resources and cells in geographical areas.

[0273] The examples can be executed on any suitable data processing device, such as a personal computer, laptop computer, mobile phone, server, virtual machine, etc. For the purposes of discussion, the above description of the systems and methods has been simplified and is intended to provide specific examples to illustrate the invention. As will be appreciated by those skilled in the art, different types of systems and methods can be used. It will be understood that the boundaries between logic blocks are merely illustrative, and alternative embodiments may combine logic blocks or elements, or alternative functional decompositions may be imposed on various logic blocks or elements.

[0274] It will be understood that the functions mentioned above can be implemented as hardware and / or software as one or more corresponding modules. For example, the functions mentioned above can be implemented as one or more software components executed by the system's processor. Alternatively, the functions mentioned above can be implemented as hardware, such as on one or more FPGAs, and / or on one or more ASICs, and / or on one or more DSPs, and / or on other hardware arrangements. The method steps implemented in the flowcharts included herein or as described above can each be implemented with their respective corresponding modules. Furthermore, the multiple method steps implemented in the flowcharts included herein or as described above can be implemented together by a single module.

[0275] The examples can be implemented by computer software or "computer programs". Storage media and transmission media for carrying the computer software are also provided. The computer software may include one or more instructions or code that, when executed by a computer, cause the described methods to be performed. The computer software may be a sequence of instructions designed to execute on a computer system and may include subroutines, functions, programs, modules, object methods, object implementations, executable applications, applets, service programs, source code, object code, shared libraries, dynamic link libraries, and / or other sequences of instructions designed to execute on a computer system. The storage medium may be a disk (such as a hard disk drive or floppy disk), an optical disk (such as a CD-ROM, DVD-ROM, or Blu-ray disc), or a memory (such as ROM, RAM, EEPROM, EPROM, flash memory, or portable / removable memory devices), etc. The transmission medium may be a communication signal, data broadcast, a communication link between two or more computers, etc.

[0276] Unless otherwise stated, each feature disclosed in this specification may be replaced by an alternative feature serving the same, equivalent, or similar purpose. Therefore, unless otherwise stated, each disclosed feature is merely one example of a general series of equivalent or similar features.

[0277] As used herein, including in the claims, unless the context otherwise indicates, the singular form of a term herein shall be construed as including the plural form, and vice versa. For example, unless the context otherwise indicates, singular references included in the claims herein, such as “a” or “an” (such as a UE, node, network entity, RAN entity, or cell), mean “one or more” (e.g., one or more UEs, one or more nodes, one or more network entities, one or more RAN entities, or one or more cells). Throughout the description and claims of this disclosure, the words “comprising,” “containing,” “having,” and “including,” and variations thereof, such as “comprising of” and “including,” or similar terms, mean “comprising” and are not intended to (and will not) exclude other components.

[0278] The use of any and all examples or exemplary language (“e.g.,” “such as,” “for example,” and similar language) provided herein is intended merely to better illustrate the invention and does not indicate any limitation on the scope of the invention unless otherwise claimed. No language in the specification should be construed as indicating that any unclaimed element is essential to the practice of the invention.

[0279] Any steps described in this specification may be performed in any order or simultaneously, unless otherwise stated or required by the context. Furthermore, the fact that a step is described as being performed after another step does not preclude the execution of intermediate steps.

[0280] All aspects and / or features disclosed in this specification may be combined in any combination, except for combinations in which at least some of such features and / or steps are mutually exclusive. As described herein, there may be specific combinations of further advantageous aspects, such as determining a set of compensation parameters and applying the set of compensation parameters to aspects of the measurement. In particular, preferred features of the invention apply to all aspects of the invention and can be used in any combination. Similarly, features described in non-essential combinations may be used individually (not in combination).

[0281] Methods for manufacturing and / or operating any of the devices disclosed herein are also provided. These methods may include steps of providing each of the disclosed features and / or configuring or using the corresponding feature for its stated function.

Claims

1. A method for receiving synchronization signal measurements in a cellular network, the method comprising: Receive one or more measurement report messages from a user equipment (UE) including a first measurement report entry relating to a first synchronization signal of a first potential target cell, wherein the first measurement report entry includes a cell identifier of the first potential target cell, and wherein the one or more measurement report messages further include a second measurement report entry relating to a second synchronization signal of the first potential target cell, wherein the second measurement report entry includes the cell identifier of the first potential target cell; The identifier of the one or more measurement report messages includes two measurement report entries, each including the same cell identifier, and in response, determines whether to issue an alarm and / or increment a counter; and The two measurement report entries were determined to involve the same cell, and alarm and / or counter increases were suppressed.

2. The method according to claim 1, further comprising: Receive one or more additional measurement report messages; The identifier of the one or more additional measurement report messages includes two measurement report entries, each including the same cell identifier, and in response, determines whether to issue an alarm and / or increment a counter; and If it is determined that the two measurement report entries of the one or more additional measurement report messages involve different cells, an alarm is issued and / or a counter is incremented.

3. The method according to claim 1 or claim 2, further comprising: Configuration data is transmitted to the UE, the configuration data causing the UE to measure the first synchronization signal of the first potential target cell and the second synchronization signal of the first potential target cell.

4. The method according to claim 3, wherein the configuration data includes SS / PBCH block measurement timing configuration (SMTC).

5. The method according to claim 3 or 4, wherein the configuration data includes one or more of the following parameters: The absolute frequency of the first synchronization signal; and The periodicity of the first synchronization signal.

6. The method according to any of the preceding claims further comprises: Instructions are sent from the first potential target cell to the UE's serving cell to indicate that the first potential target cell periodically transmits the second synchronization signal.

7. The method according to any of the preceding claims, wherein each of the two measurement report entries further includes a signal strength measurement relating to the corresponding synchronization signal.

8. The method according to any of the preceding claims, wherein the measurement report entries include radio resource management (RRM) measurements.

9. The method according to any preceding claim, wherein each of the first synchronization signal and the second synchronization signal is a synchronization signal block (SSB), comprising one or more of the following: Primary synchronization signal (PSS); Auxiliary synchronization signal (SSS); Physical Broadcast Channel (PBCH); and Physical Broadcast Channel Demodulation Reference Signal (PBCH DMRS).

10. The method of claim 9, wherein for each of the first synchronization signal and the second synchronization signal, the PBCH includes a Master Information Block (MIB).

11. The method according to any of the preceding claims, wherein: The first synchronization signal includes data that enables the UE to obtain the first system information block (SIB1); and The second synchronization signal is not used to obtain SIB1.

12. The method according to any of the preceding claims, wherein: The first synchronization signal is associated with the Residual Minimum System Information (RMSI) block; and The second synchronization signal is not associated with a separate RMSI block.

13. The method according to any of the preceding claims, wherein: The first synchronization signal is the Cell Defined Synchronization Signal Block (CD-SSB); and The second synchronization signal is a non-cell defined synchronization signal block (NCD-SSB).

14. The method according to any of the preceding claims, wherein each of the first synchronization signal and the second synchronization signal includes a plurality of parameters.

15. The method of claim 14, wherein the second synchronization signal includes parameters different from those of the first synchronization signal.

16. The method according to claim 14 or 15, wherein each of the first synchronization signal and the second synchronization signal comprises a plurality of information elements, wherein each plurality of information elements comprises a corresponding plurality of parameters.

17. The method of claim 16, wherein the information element of the second synchronization signal includes one or more of the following parameters: The absolute frequency of the second synchronization signal; The periodicity of the second synchronization signal; and The second synchronization signal is time-off relative to the first synchronization signal.

18. The method according to any of the preceding claims, wherein the periodicity of the second synchronization signal is different from the periodicity of the first synchronization signal.

19. A network entity configured to perform the method according to any of the preceding claims.

20. A computer program comprising instructions that, when executed on a processor, cause the processor to perform the method according to any one of claims 1 to 18.

Images