A method, network entity and computer software for facilitating synchronisation of a plurality of ues

Abstract

A method of a base station facilitating synchronisation of a plurality of user equipments, UEs, is provided. The plurality of UEs comprises at least one UE of a first capability type. The method comprises: periodically transmitting a first synchronisation signal; determining a level of network traffic communicated via the base station and associated with the at least one UE of the first capability type; and selectively periodically transmitting a second synchronisation signal, based on the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type.

Description

A method, network entity and computer software for facilitating synchronisation of a plurality of UEsField

[0001] The present invention relates to synchronisation of devices in a telecommunications network. In particular, the invention relates to synchronisation of devices having different capabilities.Glossary eMBB - Enhanced Mobile BroadbandURLLC - Ultra-Reliable Low Latency Communications loT - Internet of ThingsI loT - Industrial Internet of Things mMTC - Massive Machine-Type CommunicationsLPWA - Low-Power Wide AreaLTE-M - Long Term Evolution for MachinesNB-loT - Narrowband loTMIMO - Multiple-Input Multiple-OutputSISO - Single-Input Single-OutputFR1 - Frequency Range 1FR2 - Frequency Range 2HD-FDD - Half-Duplex Frequency Division DuplexFD-FDD - Full-Duplex Frequency Division DuplexBD - Blind DecodingCCE - Control Channel ElementPDCCH - Physical Downlink Control ChannelSFN - System Frame Number eDRX - Extended Discontinuous ReceptionRRM - Radio Resource ManagementIE - Information ElementRACH - Random-Access ChannelSSB - Synchronisation Signal BlockPSS - Primary Synchronization SignalSSS - Secondary Synchronization SignalPBCH - Physical Broadcast ChannelDMRS - DeModulation Reference SignalMIB - Master Information BlockSIB - System Information BlockCD-SSB - Cell Defining SSBNCD-SSB - Non-Cell Defining SSBBWP - Bandwidth PartSMTC - SS / PBCH Block Measurement Timing ConfigurationRMSI - Remaining Minimum System InformationCAM - Operations, Administration, and ManagementRAN - Radio Access NetworkUE - User EquipmentBS - Base StationABS - Advanced Base StationBTS - Base Transceiver StationBSS - Basic Service SetESS - Extended Service SetAP - Access PointNB - Node B (Radio Base Station Receiver) eNB - Evolved Node B gNB - Next-Generation Node BTRP - Transmission and Reception PointPS - Processing ServerTE - Terminal EquipmentMS - Mobile StationMT - Mobile TerminalUT - User TerminalSS - Subscriber StationPDA - Personal Digital AssistantCDMA - Code Division Multiple AccessFDMA - Frequency Division Multiple AccessTDMA - Time Division Multiple AccessOFDMA - Orthogonal Frequency Division Multiple AccessSC-FDMA - Single Carrier Frequency Division Multiple AccessMC-FDMA - Multicarrier Frequency Division Multiple AccessUTRA - Universal Terrestrial Radio AccessGSM - Global System for Mobile CommunicationsGPRS - General Packet Radio ServiceEDGE - Enhanced Data Rates for GSM EvolutionIEEE - Institute of Electrical and Electronics EngineersE-UTRA - Evolved UTRAUMTS - Universal Mobile Telecommunications SystemE-UMTS - Evolved UMTS3GPP - 3rd Generation Partnership ProjectDL - DownlinkUL - UplinkLTE - Long Term Evolution (4G)LTE-A - LTE-AdvancedNR - New Radio (5G)FDD - Frequency Division DuplexTDD - Time Division DuplexCRS - Cell-specific Reference SignalCSI-RS - Channel State Information Reference SignalFPGA - Field-Programmable-Gate-ArrayASIC - Application-Specific-lntegrated-CircuitDSP - Digital-Signal-ProcessorCD-ROM - Compact Disc Read-Only MemoryDVD-ROM - Digital Versatile Disc Read-Only MemoryROM - Read-Only MemoryRAM - Random-Access MemoryEEPROM - Electrically Erasable Programmable Read-Only MemoryEPROM - Erasable Programmable Read-Only MemoryBackground

[0002] Releases 15 and 16 of the 3GPP (5G) standard provide enhanced mobile broadband (eMBB) services for high speed and capacity data connections with reliable coverage and mobility tolerance. An alternative service requirement is defined for devices / applications that require high reliability and the lowest possible latency: Ultra-Reliable Low Latency Communications (URLLC). However, not every UE requires such an elevated level of service. For example, loT devices (sometimes referred to as I loT in 5G) may only need to send small volumes of data and may be tolerant to high latency. These devices may be connected in large numbers in a particular area. A third service requirement for such devices is defined as Massive Machine-Type Communications (mMTC) in 5G. There may also be some devices that require a level of service between these extremes, such as sensor devices, surveillance devices, and wearable devices.

[0003] Release 17 of the 3GPP (5G) standard adds a definition of a new UE type requiring performance characteristics (e.g., data throughput and speed) that are reduced compared to eMBB and URLLC but enhanced compared to LPWA (i.e., LTE-M / NB-loT) or mMTC. This UE type is referred to as a “reduced capability” or RedCap UE.

[0004] 3GPP technical report (TR) 38.875 (which is incorporated by reference) specifies three potential use cases for RedCap devices, including industrial sensors, surveillance devices, and health wearables.

[0005] 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 2x2 MIMO for the downlink and SISO for the uplink.

[0006] RedCap devices may also support lower bandwidths than other devices. For example, some RedCap devices may only support bandwidths of 20 MHz for FR1 and 100 MHz for FR2. Lower bandwidths reduce power amplifier complexity and may enable efficient operation of the device.

[0007] In addition, some RedCap devices use half-duplex FDD (HD-FDD) transmission instead of full-duplex FDD (FD-FDD). This prevents the device from transmitting and receiving data on different frequencies at the same time and therefore reduces complexity. Isolation of the transmit path from the receive path may not be required in such devices. RedCap devices may therefore use switches instead of duplexers.

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

[0009] RedCap devices may use the system frame number (SFN) technique to increase extended discontinuous reception (eDRX) cycles when the device disconnects from the network or becomes idle, which can reduce power consumption. Longer eDRX cycles may also be beneficial in specific use cases such as industrial sensors. Release 17 also allows RedCap devices to transmit data without connecting to the network.

[0010] In addition, radio resource management (RRM) requirements may be reduced to accommodate RedCap devices, which can enable devices to reduce their power consumption.

[0011] Modifications to a device’s capabilities also have implications for the network. For example, lower bandwidth support may require corresponding changes in bandwidth part (BWP) configurations. New information elements (IE) may also enable dynamic adaptation of the bandwidth.

[0012] Lower bandwidths may also impact the RACH procedure used by the devices to access the network. The network may specify a specific BWP for RedCap devices or may reduce the size of the BWP for these devices.

[0013] In 5G(NR), a gNB periodically transmits a SSB, which is used by UEs for synchronisation, cell search and initial beamforming. The SSB is comprised of synchronisation signals (PSS and SSS) and PBCH. The PBCH is comprised of PBCH DMRS, which functions as a reference signal for decoding the PBCH, and payload data, which is used for transmitting the MIB.

[0014] For reduced capability devices, an alternative version of the SSB may be used, which is the NCD-SSB.Summary

[0015] Some prior art devices use a separate NCD-SSB for reduced capability devices. However, they do not consider whether there are sufficient devices in the network thatwould use the NCD-SSB to justify the resources used by transmitting a separate NCD- SSB. Against this background, a method of selectively enabling NCD-SSB is provided.

[0016] A method of a base station facilitating synchronisation of a plurality of user equipments, UEs, is provided. The plurality of UEs comprises at least one UE of a first capability type. The method comprises: periodically transmitting a first synchronisation signal; determining a level of network traffic communicated via the base station and associated with the at least one UE of the first capability type; and selectively periodically transmitting a second synchronisation signal, based on the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type.

[0017] Network traffic may be a measure of data communicated between the UE and the base station.

[0018] Where we refer to a UE “of a first capability type,” this could equally be written as a UE “having a first capability type.” The first capability type may be used to define a group of UEs having similar capabilities (e.g., reduced capability UEs). Alternatively, the first capability type may be used to define a group of UEs all having at least a minimum set of required capabilities. UEs having additional / enhanced capabilities may be permitted to be defined as belonging to the first capability type, provided they meet the minimum requirements. One example of a minimum capability requirement for the first capability type is that the UE is capable of synchronisation using the second synchronisation signal.

[0019] Selectively periodically transmitting the second synchronisation signal based on the level of traffic communicated via the base station and associated with the at least one UE of the first capability type may comprise: if the level of network traffic communicated via the base station and associated with the at least one user equipment of the first capability type exceeds a first threshold, periodically transmitting the second synchronisation signal; and if the level of network traffic communicated via the base station and associated with the at least one user equipment of the first capability type falls below a second threshold, disabling periodic transmission of the second synchronisation signal.

[0020] The first and second threshold may be the same or may be different. Having two separate thresholds for enabling and disabling of NCD-SSB may provide some flexibility to the network.

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

[0022] With flexibility introduced of having two separate thresholds, and based on the behaviour described above, the network can inform the UEs of a change to the NCD-SSB in a manner that is tolerant to delay. In other words, the network does not need to inform the UE immediately when the network decision is made.

[0023] The threshold may be an absolute threshold or may be a relative threshold. The “level” of network traffic may be measured as an absolute value or may be measured as a proportion of the overall network traffic communicated via the base station (associated with a UE of any capability type).

[0024] The method may further comprise: receiving, from one or more base stations corresponding to one or more neighbouring cells, a level of network traffic communicated via the respective base station and associated with one or more UEs of the first capability type, wherein selectively periodically transmitting the second synchronisation signal is further based on the level of network traffic communicated via the one or more base stations corresponding to the one or more neighbouring cells and associated with UEs of the first capability type.

[0025] Selectively periodically transmitting the second synchronisation signal based on the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type and further based on the level of network traffic communicated via the one or more base stations corresponding to the one or more neighbouring cells and associated with UEs of the first capability type may comprise:determining, for the base station and the one or more base stations corresponding to the one or more neighbouring cells, an overall level of network traffic associated with UEs of the first capability type by combining the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type with the level of network traffic communicated via the one or more base stations corresponding to the one or more neighbouring cells and associated with UEs of the first capability type; if the overall level of network traffic associated with UEs of the first capability type exceeds a first threshold, periodically transmitting the second synchronisation signal; if the overall level of network traffic associated with UEs of the first capability type falls below a second threshold, disabling periodic transmission of the second synchronisation signal.

[0026] Combining the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type with the level of network traffic communicated via the one or more base stations corresponding to the one or more neighbouring cells and associated with UEs of the first capability type may comprise one or more of: summing the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type and each of the levels of network traffic communicated via the one or more base stations corresponding to the one or more neighbouring cells and associated with UEs of the first capability type; and calculating a weighted average of the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type and each of the levels of network traffic communicated via the one or more base stations corresponding to the one or more neighbouring cells and associated with UEs of the first capability type.

[0027] The method may further comprise sending, to one or more base stations corresponding to one or more neighbouring cells, the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type.

[0028] The plurality of UEs may further comprise at least one UE of a second capability type, wherein: the first capability type corresponds with a reduced capability compared to the second capability type;the first capability type is not reduced compared to the second capability type and corresponds with UEs that are compatible with the second synchronisation signal; or the first capability type corresponds with UEs that are compatible with the second synchronisation signal and wherein the at least one UE of the first capability type includes at least one UE having a reduced capability compared to the second capability type and at least one UE not having reduced capability compared to the second capability type.

[0029] The first capability type may correspond with a reduced capability “RedCap” capability type.

[0030] Alternatively, the first capability type may correspond with one or more normal UEs supporting synchronisation based on the second synchronisation signal (support for NCD- SSB measurements by non-RedCap UEs is planned for Release 18 of the 3GPP standards).

[0031] Alternatively, UEs of the first capability type may include a combination of one or more RedCap UEs and one or more normal UEs supporting measurements of the second synchronisation signal (NCB-SSB).

[0032] The second synchronisation signal may be for facilitating synchronisation of the at least one UE of the first capability type.

[0033] A UE of the first capability type (e.g., a RedCap UE) may be capable of synchronising using the second synchronisation signal (e.g., NCD-SSB). Redcap UEs are compatible with the new synchronisation information. From Release 18, other (non- RedCap) UEs may also be capable of synchronising using the second synchronisation signal (e.g., NCD-SSB).

[0034] The first synchronisation signal (e.g., CD-SSB) may be used for facilitating synchronisation of the at least one UE of the second capability type in some examples. A non-RedCap UE may require a CD-SSB (e.g., if the UE is not compatible with the NCD- SSB).

[0035] The first synchronisation signal may be used for facilitating synchronisation of the at least one UE of the first capability type when periodic transmission of the second synchronisation signal is disabled.

[0036] The CD-SSB may be used to synchronise the non-RedCap UEs. The NCD-SSB may be used to facilitate synchronisation of the RedCap UEs, when it is being transmitted. The CD-SSB may be used to synchronise the RedCap UEs when the NCD-SSB is switched off. In other words, if the NCD-SSB is not available (i.e., switched off), the UEs that would otherwise use the NCD-SSB (i.e., are compatible with the NCD-SSB, such as RedCap UEs and compatible Release 18+ UEs) may fall back to using the CD-SSB.

[0037] If NCD-SSB is configured (i.e., switched on), RedCap UEs operating in the corresponding BWP may use NCD-SSB for the purposes for which it would otherwise have used the CD-SSB of the serving cell (e.g., obtaining sync, measurements, RLM, and the like).

[0038] Each of the first synchronisation signal and the second synchronisation signal may be a synchronisation signal block comprising: a primary synchronisation signal, PSS; a secondary synchronisation signal, SSS; a physical broadcast channel, PBCH; and a physical broadcast channel demodulation reference signal, PBCH DMRS.

[0039] For each of the first synchronisation signal and the second synchronisation signal, the PBCH may comprise a master information block, MIB.

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

[0041] The MIB of the second synchronisation signal may lack information relating to SIBs, because the second synchronisation signal may not be associated with any SIBs.

[0042] The first synchronisation signal may comprise data to enable a UE to obtain a first system information block, SIB1. In contrast, the second synchronisation signal may not be used to obtain SIB1.

[0043] In other words, as defined in the 3GPP physical layer specification, a NCD-SSB may be a SSB which not used to obtain SIB1 .

[0044] Alternatively, the first synchronisation signal may be associated with a system information block, SIB, whereas the second synchronisation signal may not be associated with a SIB.

[0045] The first synchronisation signal may be associated with a Remaining Minimum System Information, RMSI, block. The second synchronisation signal may not be associated with a RMSI block.

[0046] The first synchronisation signal may be a cell-defining synchronisation signal block, CD-SSB. The second synchronisation signal may be a non-cell-defining synchronisation signal block, NCD-SSB.

[0047] Each of the first synchronisation signal and the second synchronisation signal may comprise a plurality of parameters.

[0048] The second synchronisation signal may comprise parameters that are different to the parameters of the first synchronisation signal.

[0049] The second synchronisation signal may comprise a greater number of parameters than the first synchronisation signal.

[0050] A subset of the parameters of the second synchronisation signal may have different values compared to the first synchronisation signal (and the rest may be the same).

[0051] Each of the first synchronisation signal and the second synchronisation signal may comprise a plurality of information elements, wherein each plurality of information elements comprises the respective plurality of parameters.

[0052] An information element of the second synchronisation signal may comprise one or more of the following parameters: an absolute frequency of the synchronisation signal; a periodicity of the synchronisation signal; and a time offset of the second synchronisation signal relative to the first synchronisation signal.

[0053] An information element of the first synchronisation signal may comprise one or more of the following parameters: an absolute frequency of the synchronisation signal; a periodicity of the synchronisation signal; and a time offset.

[0054] A periodicity of the second synchronisation signal may be different to a periodicity of the first synchronisation signal.

[0055] Since the second synchronisation signal may be used for devices having reduced capabilities, the signal may be transmitted with a greater periodicity (i.e., less frequently). As a result, radio resources may be conserved.

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

[0057] The UE may report its radio access capabilities to the base station.

[0058] Determining whether a UE is a UE of the first capability type may comprise: determining that the UE is a RedCap UE; determining that the UE is a UE (e.g., a non-RedCap UE) capable of using the second synchronisation signal (e.g., NCD-SSB); or determining that the UE is either a RedCap UE or a UE capable of using the second synchronisation signal.

[0059] RedCap UEs from 3GPP Release 17 onwards may be compatible with the second synchronisation signal. Non-RedCap UEs from 3GPP Release 18 onwards may be compatible with the second synchronisation signal.

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

[0061] UE device type information and / or UE capability information may be provided in an information element relating specifically to the first capability type. Determining whether a UE communicating via the base station is a UE of the first capability type may be based on the presence of the information element relating specifically to the first capability type in signalling from the UE.

[0062] The information element may be RedCapParameters or UE-NR-Capability, for example.

[0063] As discussed above, determining whether a UE is a UE of the first capability type may comprise: determining that the UE is a RedCap UE; determining that the UE is a Rel 18 UE capable of using NCD-SSB; or determining that the UE is either a RedCap UE or a 3GPP Release 18+ UE capable of using NCD-SSB.

[0064] A network entity configured to perform a method as described above is also provided.

[0065] Computer software comprising instructions that, when executed on a processor, cause the processor to perform a method described above is also provided.

[0066] A method of a base station facilitating handover of a user equipment, UE, is also provided. The base station is configured to periodically transmit a first synchronisation signal and selectively periodically transmit a second synchronisation signal. The method comprises:determining that a procedure to disable periodic transmission of the second synchronisation signal should be initiated, based on network traffic levels; determining that a handover procedure has been initiated in respect of a UE, based on measurements of the second synchronisation signal taken by the UE, wherein the base station is a target base station of the handover procedure; and modifying one or more procedures and completing the handover procedure, so that the base station becomes a serving base station of the UE.

[0067] The base station may be configured to selectively periodically transmit the second synchronisation signal based on a level of network traffic associated with one or more UEs of a first capability type.

[0068] The level of network traffic associated with one or more UEs of the first capability type may comprise: a level of network traffic communicated via the base station and associated with one or more UEs of the first capability type; and a level of network traffic communicated via one or more base stations corresponding to one or more neighbouring cells and associated with UEs of the first capability type.

[0069] The base station may be configured to communicate with a plurality of UEs, wherein the plurality of UEs comprises at least one UE of a first capability type and at least one UE of a second capability type, wherein: the first capability type corresponds with a reduced capability compared to the second capability type; the first capability type is not reduced compared to the second capability type and corresponds with UEs that are compatible with the second synchronisation signal; or the first capability type corresponds with UEs that are compatible with the second synchronisation signal and wherein the at least one UE of the first capability type includes at least one UE having a reduced capability compared to the second capability type and at least one UE not having reduced capability compared to the second capability type.

[0070] The UE in respect of which the handover procedure has been initiated may be a UE of the first capability type.

[0071] The measurements of the second synchronisation signal taken by the UE may be radio resource management, RRM, measurements.

[0072] In some alternative examples, the measurements of the second synchronisation signal taken by the UE may be radio resource control, RRC, measurements.

[0073] Each of the first synchronisation signal and the second synchronisation signal may be a synchronisation signal block comprising: a primary synchronisation signal, PSS; a secondary synchronisation signal, SSS; a physical broadcast channel, PBCH; and a physical broadcast channel demodulation reference signal, PBCH DMRS.

[0074] For each of the first synchronisation signal and the second synchronisation signal, the PBCH may comprise a master information block, MIB.

[0075] The first synchronisation signal may comprise data to enable a UE to obtain a first system information block, SIB1. The second synchronisation signal may not be used to obtain SIB1.

[0076] The first synchronisation signal may be associated with a Remaining Minimum System Information, RMSI, block. The second synchronisation signal may not be associated with a RMSI block.

[0077] The first synchronisation signal may be a cell-defining synchronisation signal block, CD-SSB. The second synchronisation signal may be a non-cell-defining synchronisation signal block, NCD-SSB.

[0078] Each of the first synchronisation signal and the second synchronisation signal may comprise a plurality of parameters.

[0079] The second synchronisation signal may comprise parameters that are different to the parameters of the first synchronisation signal.

[0080] Each of the first synchronisation signal and the second synchronisation signal may comprise a plurality of information elements, wherein each plurality of information elements comprises the respective plurality of parameters.

[0081] An information element of the second synchronisation signal may comprise one or more of the following parameters: an absolute frequency of the synchronisation signal; a periodicity of the synchronisation signal; and a time offset of the second synchronisation signal relative to the first synchronisation signal.

[0082] A periodicity of the second synchronisation signal may be different to a periodicity of the first synchronisation signal.

[0083] In some examples, a periodicity of the second synchronisation signal may be greater than a periodicity of the first synchronisation signal. In other examples, A periodicity of the second synchronisation signal may be less than a periodicity of the first synchronisation signal.

[0084] Determining that a handover procedure has been initiated may comprise receiving, from a neighbouring base station (e.g., via a network interface Xn or X2), carrier resource information identifying a portion of carrier bandwidth (BWP) associated with the second synchronisation signal.

[0085] The bandwidth part (BWP) may comprise the second synchronisation signal in some examples. In other words, the NCD-SSB may be within the BWP. In other examples, the second synchronisation signal may be separate from the BWP.

[0086] Modifying one or more procedures may comprise modifying the procedure to disable periodic transmission of the second synchronisation signal.

[0087] Modifying the procedure to disable periodic transmission of the second synchronisation signal may comprise delaying (or “suppressing,” or “temporarily suppressing”) the procedure to disable periodic transmission of the second synchronisationsignal, so that periodic transmission of the second synchronisation signal continues while the handover procedure is ongoing.

[0088] In the example described above, periodic transmission of the second synchronisation signal may continue while the handover procedure is ongoing, despite the determination by the base station that periodic transmission of the second synchronisation signal should be disabled, based on network traffic levels.

[0089] The method may further comprise disabling periodic transmission of the second synchronisation signal after the handover procedure has been completed.

[0090] Completing the handover procedure may comprise completing the handover procedure based on the second synchronisation signal.

[0091] Modifying one or more procedures may comprise modifying the handover procedure.

[0092] Modifying the handover procedure may comprise providing configuration to the UE to cause the UE to measure the first synchronisation signal (instead of the second synchronisation signal).

[0093] The configuration may comprise SS / PBCH Block Measurement Timing Configuration, SMTC.

[0094] The configuration may comprise one or more of the following parameters: an absolute frequency of the first synchronisation signal; a periodicity of the first synchronisation signal; and a time offset of the first synchronisation signal.

[0095] The time offset of the first synchronisation signal may be relative to an overall resource block grid. The time offset may be provided in terms of a number of subcarriers.

[0096] The method may further comprise disabling periodic transmission of the second synchronisation signal while the handover procedure is ongoing (before the handover procedure has been completed).

[0097] Completing the handover procedure may comprise completing the handover procedure based on the first synchronisation signal.

[0098] A network entity configured to perform a method described above is also provided.

[0099] Computer software comprising instructions that, when executed on a processor, cause the processor to perform a method as described above is also provided.Detailed description

[0100] To serve use cases in between eMBB and loT, a new device capability type is defined. In some scenarios, the new device capability type represents reduced capabilities compared to other devices in the network that are designed to use eMBB. Therefore, devices having the 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, wearable devices, and surveillance cameras. By defining specific capabilities for the new device capability type (which may be reduced compared to eMBB) lower complexity devices may be designed to use the new device capability type. By designing devices with such capabilities in mind, the complexity and overall cost of such devices may be reduced.

[0101] As described above, a device operating in accordance with the new device type has reduced capabilities, when compared to a device operating in accordance with a eMBB use case. The new device capability type may impose some restrictions and limitations, in order to implement these reduced capabilities. In some examples, the new device capability type has the following limitations:• up to 20 MHz of UL / DL bandwidth,• a reduced number of MIMO layers and RX / branches of up to 2,• reduced modulation order, and• no support for carrier aggregation or dual connectivity.

[0102] UE capability information may be communicated to the network via an information element. In some examples, a RedCapParameters information element may be used. Inother examples, a different information element may be used to communicate UE capabilities.

[0103] The RedCapParameters information element definition according to a specific example is reproduced below.— ASN1START— TAG-REDCAPPARAMETERS-STARTRedCapParameters-rl7 : : = SEQUENCE {— R1 28-1 : RedCap UE supportOf RedCap-rl7 ENUMERATED { supported } OPTIONAL, supportOf 16DRB-RedCap-rl7 ENUMERATED { supported } OPTIONAL}RedCapParameters-vl740 : : = SEQUENCE { ncd-SSB-ForRedCapInitialBWP-SDT-rl7 ENUMERATED { supported }OPTIONAL}— TAG-REDCAPPARAMETERS-STOP— ASN1STOP

[0104] The IE RedCapParameters is used to indicate the UE capabilities supported by RedCap UEs. This IE may be used to provide RedCap capability information to the network.

[0105] Given the nature of the devices that are likely to be designated as RedCap devices (sensors, surveillance, wearables, and the like), it is expected that large numbers of RedCap devices may be present in the network after support for these devices is implemented. Efforts in standardization have been undertaken to achieve coexistence with legacy devices, and to provide mechanisms to offload and to leverage the resources of a network for these devices. A specific enhancement in Release 17 for RedCap UEs is the introduction of an additional non-cell defining synchronization block (NCD-SSB). In some examples, the NCD-SSB differs from the legacy cell-defining synchronization block (CD-SSB) by not being associated with SIB. The NCD-SSB is configured by the network in a bandwidth part (BWP), allowing RedCap UEs operating in this BWP to use this SSB for the purposes for which it would otherwise have used the CD-SSB of the serving cell (e.g., obtaining sync, measurements, radio link monitoring). This extra synchronization block provides advantages. For example, it provides flexibility for the network to offload part or all the RedCap traffic in a cell.

[0106] The NonCellDefiningSSB information element definition according to a specific example is reproduced below.— ASN1START— TAG-NONCELLDEFININGSSB-STARTNonCellDef iningSSB-rl7 : : = SEQUENCE { absoluteFrequencySSB-rl 7 ARFCN-ValueNR, ssb-Periodicity-rl7 ENUMERATED { ms5 , msl O , ms20 , ms40 , ms80 , ms l 60 , spare2 , sparel } OPTIONAL, — Need S ssb-TimeOf f set-rl 7 ENUMERATED { ms5 , ms lO , ms l5 , ms20 , ms 40 , ms 80 , spare2 , sparel } OPTIONAL, -- Need S}— TAG-NONCELLDEFININGSSB-STOP— ASN1STOP

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

[0108] Field descriptions for the NonCellDefiningSSB IE are provided in the table below.

[0109] Transmitting an extra synchronization block, with similar characteristics as the legacy one, will increase the overall network signalling overhead, increase the network energy consumption, and reduce the number of resources that the network has available to schedule for data transmission. Therefore, a mechanism is proposed to selectively control the NCD-SSB transmission. The mechanism may enable the network operator to benefit from the advantages associated with using NCD-SSB and to balance these benefits against the drawbacks.

[0110] To control the NCD-SSB transmission, a method is proposed that takes into account the number of RedCap UEs camped in a cell, the traffic load they represent in the overall cell, and similar information from the neighbour cells. In some examples, NCD-SSB is transmitted after a particular threshold is met in terms of the factors mentioned above, and not transmitted whenever there is little or no RedCap traffic.

[0111] Figure 1 illustrates a telecommunications network according to a specific example. Three neighbouring cells are illustrated, each having a respective base station 100A, 100B and 100C. In each cell, there are one or more UEs. Each UE may be a UE of a first capability type (e.g., a RedCap UE) 120AA, 120AB, 120CA, 120CB and 120CC or a UE of a second capability type (e.g., a mobile phone configured for enhanced mobile broadband)110AA, 1 10AB, 1 10BA and 110CA. The base stations 10OA, 10OB and 10OC may communicate via an X2 or Xn interface 150.

[0112] The purpose of including neighbour cells as one of the criteria for the transmission, is whilst there may not be traffic in a cell, its neighbour cells may have RedCap traffic and these UEs can be performing neighbour cell measurements for handover purposes. For example, as illustrated in Figure 1 , base station 100B is not currently serving any RedCap UEs. However, there are RedCap UEs in the neighbouring cells, many of which could handover to base station 100B. In particular, RedCap UEs 120AB, 120CB and 120CC may handover to base station 100B. Therefore, despite RedCap UE traffic being low for base station 100B, it may nevertheless be advantageous for the base station 100B to transmit a NCD-SSB.

[0113] A flow diagram illustrating an example method is shown in Figure 2. The procedural behaviour is as follows:

[0114] At step 201 , the network measures the number of RedCap UEs through their early identification during initial access. This value is stored as one important parameter. A traffic load attributed to RedCap UEs in the cell is also measured and updated as another (or alternative) important parameter.

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

[0116] The traffic load related to RedCap UEs may be monitored separately form the rest of the network traffic.

[0117] At step 202, the base station exchanges information relating to the number of RedCap UEs and the traffic load with its neighbour cells through the X2 (or Xn) interface, and receives corresponding information back. A new signalling parameter (or parameters) may be introduced over the X2 or Xn signalling interface for communication of this information.

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

[0119] The values of the thresholds can be set by the network, by implementation, or set from a value in the standards.

[0120] The decision to transmit NCD-SSB or not, based on the traffic load and / or number of connected RedCap UEs can either be left to gNB implementation (each individual gNB may make a decision based on thresholds configured individually) or controlled by CAM (gNBs that belong to the same OAM centre may follow the same decision / policy and use the same thresholds).

[0121] As described in TS 38.331 (which is incorporated by reference), the NCD-SSB allows a RedCap UE operating in the corresponding BWP to use the NCD-SSB for the purposes for which it would otherwise have used the CD-SSB of the serving cell (e.g. obtaining sync, measurements, radio link monitoring). All these operations are in RRC_Connected mode as there is no standards support for idle / inactive.

[0122] These types of measurements can be the basis of a handover decision and, depending on the state of the NCD-SSB transmission at the serving and target cells, the following example scenario can occur:• A UE performs RRM measurements on the NCD-SSB,• the network makes the decision for handover based on the measurements based on the NCD-SSB of the neighbouring cell,• in the meantime, the neighbouring cell decides to switch off NCD-SSB.

[0123] Due to a number of factors, this scenario will hopefully be rare in most cases. One reason is that hysteresis is preferably configured in the switching-on and switching-off of the NCD-SSB, so that switching happens only infrequently. The time period between the UE making the measurements and the neighbouring cell deciding to switch off the NCD- SSB should therefore be small, compared to the time during which the NCD-SSB is on and uninterrupted. Therefore, the probability of this scenario should be low. Moreover, thedecision to switch off the NCD-SSB is based on information from neighbouring cells so should only be taken if there are relatively few connected RedCap devices in neighbouring cells. Therefore, the probability of a RedCap device attempting handover to the cell after the decision has been taken to switch off the NCD-SSB should be low.

[0124] Nevertheless, this scenario can happen, and the network should be able to manage the scenario when it does occur. The following two solutions are proposed to address the scenario.

[0125] In a first solution, the target cell is not allowed to shut down the NCD-SSB transmission before the handover is finalized.

[0126] After the handover decision has been taken (e.g. by a base station in the network), the frequency information of the BWP corresponding to the NCD-SSB (i.e., an indication of the NCD-SSB that should not be shut down) is communicated by the source cell to the target cell over the network interface (e.g., X2 or Xn).

[0127] In a second solution, the target cell provides changes measurement configuration upon handover. The target cell may send configuration so that handover is performed using the initial BWP of the target cell or a different BWP not corresponding to the NCD-SSB. SS / PBCH Block Measurement Timing Configuration (SMTC) may be configured for the UE to cover the CD-SSB absolute frequency. Remaining configuration (such as periodicity and offset) may be provided to enable the UE to perform measurements on another SSB (e.g., the CD-SSB), rather than on the NCD-SSB. Once the configuration has been provided, the base station may proceed to shutdown NCD-SSB transmission, based on the criteria discussed above (traffic, thresholds, and the like).

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

[0129] Given that the UE is measuring on NCD-SSB and the attributes for NCD-SSB are different from CD-SSB, it is not accurate to compare the measurements on NCD-SSB to CD-SSB. Whatever measurements are used for the handover decision (measurements prior to the handover) should be consistent during the handover. Otherwise, the handover was made based on arbitrary measurements or measurements which are no longer valid, resulting in ambiguity of the handover decision.

[0130] In some examples, a RedCap UE may comprise simplified components compared to other UEs that are not designated as RedCap (which may communicate via eMBB). While a “RedCap” UE may be referred to as a “reduced capability” UE, the UE itself may nevertheless be capable of communication via eMBB (at higher data rates). A UE may be designated as a RedCap UE for a number of reasons, including power saving, reducing network load, and the like. In some examples, a RedCap UE may comprise simplified components and require reduced power consumption.

[0131] Moreover, devices that are not designated as “RedCap” UE but are nevertheless capable of synchronising using the second synchronisation signal may use the second synchronisation signal. This may conserve network resources and / or enable the device to implement power-saving techniques.

[0132] Any of the methods described herein may be implemented as a computer program. The computer program may be configured to control a RAN entity (e.g., a network node) and / or UE to perform any method according to the disclosure. A RAN entity (e.g., a network node) of a cellular network and / or a UE may also be provided, configured to operate in accordance with certain methods disclosed herein. For example, the RAN entity may include a processor and at least one communication interface, particularly comprising one or both of a transmitter and receiver. A UE may also be provided, configured to operate in accordance with certain methods disclosed herein. The UE may likewise include a processor and at least one communication interface, particularly comprising one or both of a transmitter and receiver.

[0133] Although specific embodiments have now been described, the skilled person will understand that various modifications and variations are possible. For example, whilst the disclosure is described in relation to existing network architecture, it will be understood that changes to the architecture (and / or nomenclature) are possible, but the present disclosuremay still be applicable in this case. Also, combinations of any specific features shown with reference to one embodiment or with reference to multiple embodiments are also provided, even if that combination has not been explicitly detailed herein.

[0134] A base station (BS) generally refers to a fixed station that performs communication with a UE and / or another BS, and exchanges various kinds of data and control information with the UE and another BS. The BS may be referred to as an advanced base station (ABS), a base transceiver station (BTS), a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), an access point (AP), a Node B (NB), an eNode B (eNB), a gNode B (gNB), a transmission and reception point (TRP), a processing server (PS), or some other suitable terminology, depending on the protocol, standard, context or technology. In some examples, a base station may include two or more transceivers that may or may not be collocated. Each transceiver may communicate on the same or different carrier frequency within the same or different frequency band.

[0135] Where this application refers to a server or network entity, for instance, this may actually be a pair of servers, or network entities (primary and failover), for redundancy.

[0136] In the present invention, a node refers to a fixed point capable of transmitting / receiving a radio signal through communication with a UE. Various types of base stations (such as those described above) may be used as nodes, irrespective of the terms used. In other examples, a node may be a relay, a repeater, and the like.

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

[0138] Whilst the above methods are described in relation to a 5G / NR network, these methods, techniques, apparatuses, and systems may be applied to a variety of wireless multiple access systems. Examples of the multiple access systems include CDMA, FDMA, TDMA, OFDMA, SC-FDMA, and MC-FDMA. CDMA may be embodied through radiotechnology such as UTRA or CDMA2000. TDMA may be embodied through radio technology such as GSM, GPRS, or EDGE. OFDMA may be embodied through radio technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or E-UTRA. UTRA is a part of a UMTS. 3GPP LTE is a part of E-UMTS using E-UTRA. 3GPP LTE employs OFDMA in DL and SC-FDMA in UL. LTE-A is an evolved version of 3GPP LTE. 3GPP NR employs OFDMA for both downlink and uplink and can operate in both FDD and TDD. For convenience 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 a 3GPP NR system, aspects of the present invention that are not specific to 3GPP NR are applicable to other mobile communication systems.

[0139] In the present invention, a cell refers to a geographical area to which one or more nodes provide a communication service. Accordingly, in the present invention, communicating with a specific cell may mean communicating with an gNB or a node which provides a communication service to the specific cell. Furthermore, channel status / quality of a specific cell refers to channel status / quality of a channel or communication link formed between an gNB or node which provides a communication service to the specific cell and a UE. The UE may measure DL channel state received from a specific node using cellspecific reference signal(s) (CRS(s)) transmitted on a CRS resource and / or channel state information reference signal(s) (CSI-RS(s)) transmitted on a CSI-RS resource, allocated by antenna port(s) of the specific node to the specific node. Meanwhile, a 3GPP system uses the concept of a cell in order to manage radio resources and a cell associated with the radio resources is distinguished from a cell of a geographic region.

[0140] The examples may be carried out on any suitable data processing device, such as a personal computer, laptop, mobile telephone, server, virtual machine, and the like. The above description of the systems and methods has been simplified for purposes of discussion, and is intended to provide a specific example to illustrate the invention. Different types of systems and methods may be used, as will be appreciated by the skilled person. It will be appreciated that the boundaries between logic blocks are merely illustrative and that alternative embodiments may merge logic blocks or elements, or may impose an alternate decomposition of functionality upon various logic blocks or elements.

[0141] It will be appreciated that the above-mentioned functionality may be implemented as one or more corresponding modules as hardware and / or software. For example, the above-mentioned functionality may be implemented as one or more software components for execution by a processor of the system. Alternatively, the above-mentioned functionality may be implemented as hardware, such as on one or more FPGAs, and / or one or more ASICs, and / or one or more DSPs, and / or other hardware arrangements. Method steps implemented in flowcharts contained herein, or as described above, may each be implemented by corresponding respective modules. Moreover, multiple method steps implemented in flowcharts contained herein, or as described above, may be implemented together by a single module.

[0142] Examples may be implemented by computer software or a “computer program.” A storage medium and a transmission medium carrying the computer software are also provided. The computer software may comprise one or more instructions, or code, that, when executed by a computer, causes the methods described to be performed. Computer software may be a sequence of instructions designed for execution on a computer system, and may include a subroutine, a function, a procedure, a module, an object method, an object implementation, an executable application, an applet, a servlet, source code, object code, a shared library, a dynamic linked library, and / or other sequences of instructions designed for execution on a computer system. The storage medium may be a magnetic disc (such as a hard drive or a floppy disc), an optical disc (such as a CD-ROM, a DVD- ROM, or a Blu-ray disc), or a memory (such as a ROM, a RAM, EEPROM, EPROM, Flash memory or a portable / removable memory device), etc. The transmission medium may be a communications signal, a data broadcast, a communications link between two or more computers, etc.

[0143] Each feature disclosed in this specification, unless stated otherwise, may be replaced by alternative features serving the same, equivalent, or similar purpose. Thus, unless stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.

[0144] As used herein, including in the claims, unless the context indicates otherwise, singular forms of the terms herein are to be construed as including the plural form and vice versa. For instance, unless the context indicates otherwise, a singular reference herein including in the claims, such as "a" or "an" (such as a UE, a node, a network entity, a RANentity, or a cell) means "one or more” (for instance one or more UE, 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 "comprise", "including", "having" and "contain" and variations of the words, for example "comprising" and "comprises" or similar, mean "including", and are not intended to (and do not) exclude other components.

[0145] The use of any and all examples, or exemplary language ("for instance", "such as", "for example" and like language) provided herein, is intended merely to better illustrate the invention, and does not indicate a limitation on the scope of the invention unless otherwise claimed. No language in the specification should be construed as indicating any nonclaimed element as essential to the practice of the invention.

[0146] Any steps described in this specification may be performed in any order or simultaneously unless stated or the context requires otherwise. Moreover, where a step is described as being performed after a step, this does not preclude intervening steps being performed.

[0147] All of the aspects and / or features disclosed in this specification may be combined in any combination, except combinations where at least some of such features and / or steps are mutually exclusive. As described herein, there may be particular combinations of aspects that are of further benefit, such the aspects of determining a set of compensation parameters and applying a set of compensation parameters to measurements. In particular, the preferred features of the invention are applicable to all aspects of the invention and may be used in any combination. Likewise, features described in non- essential combinations may be used separately (not in combination).

[0148] A method of manufacturing and / or operating any of the devices disclosed herein is also provided. The method may comprise steps of providing each of the features disclosed and / or configuring or using the respective feature for its stated function.

Claims

CLAIMS:1 . A method of a base station facilitating synchronisation of a plurality of user equipments, UEs, wherein the plurality of UEs comprises at least one UE of a first capability type, the method comprising: periodically transmitting a first synchronisation signal; determining a level of network traffic communicated via the base station and associated with the at least one UE of the first capability type; and selectively periodically transmitting a second synchronisation signal, based on the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type.

2. The method of claim 1 , wherein selectively periodically transmitting the second synchronisation signal based on the level of traffic communicated via the base station and associated with the at least one UE of the first capability type comprises: if the level of network traffic communicated via the base station and associated with the at least one user equipment of the first capability type exceeds a first threshold, periodically transmitting the second synchronisation signal; and if the level of network traffic communicated via the base station and associated with the at least one user equipment of the first capability type falls below a second threshold, disabling periodic transmission of the second synchronisation signal.

3. The method of claim 1 , further comprising: receiving, from one or more base stations corresponding to one or more neighbouring cells, a level of network traffic communicated via the respective base station and associated with one or more UEs of the first capability type, wherein selectively periodically transmitting the second synchronisation signal is further based on the level of network traffic communicated via the one or more base stations corresponding to the one or more neighbouring cells and associated with UEs of the first capability type.

4. The method of claim 3, wherein selectively periodically transmitting the second synchronisation signal based on the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type and further based on the level of network traffic communicated via the one or more base stationscorresponding to the one or more neighbouring cells and associated with UEs of the first capability type comprises: determining, for the base station and the one or more base stations corresponding to the one or more neighbouring cells, an overall level of network traffic associated with UEs of the first capability type by combining the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type with the level of network traffic communicated via the one or more base stations corresponding to the one or more neighbouring cells and associated with UEs of the first capability type; if the overall level of network traffic associated with UEs of the first capability type exceeds a first threshold, periodically transmitting the second synchronisation signal; if the overall level of network traffic associated with UEs of the first capability type falls below a second threshold, disabling periodic transmission of the second synchronisation signal.

5. The method of claim 4, wherein combining the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type with the level of network traffic communicated via the one or more base stations corresponding to the one or more neighbouring cells and associated with UEs of the first capability type comprises one or more of: summing the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type and each of the levels of network traffic communicated via the one or more base stations corresponding to the one or more neighbouring cells and associated with UEs of the first capability type; and calculating a weighted average of the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type and each of the levels of network traffic communicated via the one or more base stations corresponding to the one or more neighbouring cells and associated with UEs of the first capability type.

6. The method of any preceding claim, further comprising sending, to one or more base stations corresponding to one or more neighbouring cells, the level of network traffic communicated via the base station and associated with the at least one UE of the first capability type.

7. The method of any preceding claim, wherein the plurality of UEs further comprises at least one UE of a second capability type, wherein:the first capability type corresponds with a reduced capability compared to the second capability type; the first capability type is not reduced compared to the second capability type and corresponds with UEs that are compatible with the second synchronisation signal; or the first capability type corresponds with UEs that are compatible with the second synchronisation signal and wherein the at least one UE of the first capability type includes at least one UE having a reduced capability compared to the second capability type and at least one UE not having reduced capability compared to the second capability type.

8. The method of claim 7, wherein: the second synchronisation signal is for facilitating synchronisation of the at least one UE of the first capability type.

9. The method of claim 8, wherein the first synchronisation signal is used for facilitating synchronisation of the at least one UE of the first capability type when periodic transmission of the second synchronisation signal is disabled.

10. The method of any preceding claim, wherein each of the first synchronisation signal and the second synchronisation signal is a synchronisation signal block comprising: a primary synchronisation signal, PSS; a secondary synchronisation signal, SSS; a physical broadcast channel, PBCH; and a physical broadcast channel demodulation reference signal, PBCH DMRS.11 . The method of claim 10, wherein for each of the first synchronisation signal and the second synchronisation signal, the PBCH comprises a master information block, MIB.

12. The method of any preceding claim, wherein: the first synchronisation signal comprises data to enable a UE to obtain a first system information block, SIB1 ; and the second synchronisation signal is not used to obtain SIB1.

13. The method of any preceding claim, wherein: the first synchronisation signal is associated with a Remaining Minimum System Information, RMSI, block; andthe second synchronisation signal is not associated with a RMSI block.

14. The method of any preceding claim, wherein: the first synchronisation signal is a cell-defining synchronisation signal block, CD- SSB; and the second synchronisation signal is a non-cell-defining synchronisation signal block, NCD-SSB.

15. The method of any preceding claim, wherein each of the first synchronisation signal and the second synchronisation signal comprise a plurality of parameters.

16. The method of claim 15, wherein the second synchronisation signal comprises parameters that are different to the parameters of the first synchronisation signal.

17. The method of claim 15 or claim 16, wherein each of the first synchronisation signal and the second synchronisation signal comprise a plurality of information elements, wherein each plurality of information elements comprises the respective plurality of parameters.

18. The method of claim 17, wherein an information element of the second synchronisation signal comprises one or more of the following parameters: an absolute frequency of the synchronisation signal; a periodicity of the synchronisation signal; and a time offset of the second synchronisation signal relative to the first synchronisation signal.

19. The method of any preceding claim, wherein a periodicity of the second synchronisation signal is different to a periodicity of the first synchronisation signal.

20. The method of any preceding claim, wherein determining a level of network traffic communicated via the base station and associated with the at least one user equipment of the first capability type comprises determining whether a UE communicating via the base station is a UE of the first capability type, based on UE device type information and / or UE capability information reported to the base station by the UE.21 . The method of any preceding claim, further comprising requesting UE device type information and / or UE capability information from each of the plurality of UEs and receiving the UE device type information and / or UE capability information in response.

22. The method of any preceding claim, wherein UE device type information and / or UE capability information is provided in an information element relating specifically to the first capability type, and wherein determining whether a UE communicating via the base station is a UE of the first capability type is based on the presence of the information element relating specifically to the first capability type in signalling from the UE.

23. A network entity configured to perform the method of any preceding claim.

24. Computer software comprising instructions that, when executed on a processor, cause the processor to perform the method of any of claims 1 to 22.

Images