Patent Description:
Cellular communication networks generally comprise one or more radio access networks (RANs) that provide items of user equipment (UEs), in at least one discrete geographic region (a cell) covered by the RAN, with access to the communication network to allow the UEs to communicate with one another and to receive (or provide) one or more communication services to one another. The RAN typically comprises a base station which is configured to communicate with the UEs in an associated cell over an air-interface and with communication entities (or 'functions') in a core network (usually over a wired interface) in order to facilitate the set up and maintenance of communication sessions for individual UEs (e.g. for voice / video calls, data services etc.).

The terms '<NUM>' and 'new radio' (NR) refer to an evolving communication technology that is expected to support a variety of applications and services such as Machine Type Communications (MTC), Internet of Things (IoT) communications, vehicular communications and autonomous cars (V2V/V2X), high resolution video streaming, smart city services, and/or the like.

3GPP technical report (TR) <NUM> V14. <NUM> describes a possible architecture and general procedures for NextGen (<NUM>) systems planned for Release <NUM> of the 3GPP standards. 3GPP also studied the potential use of frequency bands up to <NUM> for new (<NUM>) radio access networks, with a maximum channel bandwidth of <NUM> per NR carrier in Rel-<NUM>. Directional beamforming and massive antenna technologies may also be used in order to overcome the severe channel attenuation characteristics associated with certain high frequency bands (e.g. mmWave bands). The term 'massive antenna' refers to an antenna having a high number of antenna elements (e.g. <NUM> or more) arranged in an array. Effectively, such a massive antenna may be used to communicate with several users at the same time, thus facilitating multi-user multiple-input and multiple-output (MU-MIMO) transmissions.

Whilst a base station of a <NUM>/NR communication system is commonly referred to as a New Radio Base Station ('NR-BS') or as a 'gNB' it will be appreciated that they may be referred to using the term, eNB (or <NUM>/NR eNB) which is more typically associated with LTE base stations. In case of MU-MIMO, a base station may also be referred to as a transmission and reception point (TRP). The term 'base station" will be used herein to refer generally to an NR-BS, gNB, eNB, TRP, or any equivalent communication device of a RAN.

One of the tasks of the base station is the provision of key information required by UEs to communicate in the cellular communication system, access particular services, and move as seamlessly as possible between cells of the same and different radio access technologies (RATs). This information is known as 'system information" and includes, amongst other information, minimum system information to allow the UE to access a cell and perform cell selection/re-selection (including information related to intra-frequency, inter-frequency and inter-RAT cell selections) and other system information that the UE may require in a cell in some circumstances (i.e. in addition to the minimum system information required to access the cell), for example to access specific services.

Elements of system information are typically grouped into a number of dedicated system information blocks, depending on the type of information. The blocks include a Master Information Block (MIB) comprising static, generally cell specific information that carries a part of the so-called minimum system information, the so-called 'RMSI' block which contains any remaining minimum system information (RMSI), and a number of additional system information blocks (SIBs) representing information that may be different for different UEs (or groups of UEs) which can be delivered via on-demand request. The MIB contains, for example, at least a part of the System Frame Number (SFN), timing information within the radio frame (e.g. SS block time index, half radio frame timing), RMSI scheduling information, reserved bits for future use, and a Cyclic Redundancy Check (CRC) value. The MIB is broadcast on the Physical Broadcast Channel (PBCH), while the RMSI and any on-demand SIBs are sent on the Physical Downlink Shared Channel (PDSCH) through Radio Resource Control (RRC) messages.

3GPP intends to provide one or more TRPs per new radio (NR) base station (i.e. <NUM> base station, or gNB) and each base station may support up to <NUM> cells. The expected NR control structure has been presented in 3GPP TR <NUM> V14. This technical report describes, amongst others, the provision of synchronization signal and downlink broadcast signal/channels (section <NUM>. <NUM>) in order to support initial access by the UEs (e.g. to a particular cell of the RAN) and mobility.

In summary, the synchronization signal used in NR is based on the cyclic-prefix (CP) orthogonal frequency-division multiplexing (OFDM) waveform. 3GPP defined a primary synchronisation signal (NR-PSS) and a secondary synchronisation signal (NR-SSS) for NR. NR-PSS is used at least for initial symbol boundary synchronization to the NR cell, and NR-SSS is used for detection of the NR cell identifier (or at least a part of it). NR-SSS detection is based on the fixed time/frequency relationship with NR-PSS resource position at least within a given frequency range and CP overhead.

At least one broadcast channel (NR-PBCH) is defined for NR. NR-PBCH is a non-scheduled broadcast channel carrying at least a part of the so-called minimum system information with fixed payload size and periodicity depending on carrier frequency range. Decoding of the NR-PBCH is based on the fixed relationship with NR-PSS and/or NR-SSS resource position.

For initial access, the UE can assume a signal corresponding to a specific, predetermined subcarrier spacing of NR-PSS/SSS in a given frequency band (which is known to the UE, e.g. factory configured). NR-PSS uses one antenna port. For NR-PBCH transmission, a single fixed number of antenna port(s) is supported. The UE assumes the predefined numerologies for NR-PBCH and NR-SS in a particular frequency range (hence no blind detection of the NR-PBCH transmission is required by the UE). At least a part of the minimum system information (e.g. MIB) is transmitted in the NR-PBCH. NR-PBCH contents include at least a part of the SFN, and an associated CRC value. The RMSI is transmitted via the NR-PDSCH.

There are ongoing discussions in the 3GPP RAN1 work group about scenarios where the overall network channel bandwidth (a gNB's system bandwidth) can be broken down into a number of smaller component carriers (CCs), which may have an effect on the way system information, and specifically, RMSI is provided.

The following is a summary of some of the agreements reached by 3GPP RAN1:.

<NPL>" discusses delivery mechanisms for the remaining minimum system information (RMSI). Specifically, it focusses on scheduling information needed for the RMSI and how the scheduling information would be conveyed.

<NPL>" discusses design aspects of physical broadcast channel (PBCH) including aspects of PBCH payload size, potential content, and antenna port configurations for PBCH.

<CIT> discloses a wireless access system which supports a machine-type communication (MTC), and more specifically, provides a method for repeatedly transmitting a physical broadcast channel (PBCH) for an MTC, and apparatuses for supporting same. The method for transmitting a physical broadcast channel (PBCH) in a wireless access system which supports a machine-type communication (MTC) comprises the steps of: broadcasting a legacy PBCH through a legacy transmission region; and broadcasting an MTC PBCH through an MTC transmission region. The legacy transmission region may consist of six resource blocks (RBs) at a frequency axial center of a second slot of a first subframe of each frame, and the MTC transmission region may consist of any subframe other than the first subframe of each frame.

<CIT> discloses technology for a user equipment, operable to configure a control resource set (CORESET). The UE can decode a signal, received from a next generation node B (gNB), that includes a resource element group (REG) bundling size for a first CORESET. The UE can decode a signal, received from the gNB that includes a REG bundling size for a second CORESET. The UE can decode a control message contained in one or more REGs in one or more of the first CORESET or the second CORESET.

The inventors realised that the above agreements have an impact on the current design of reference signals and also the current Resource Block Group (RBG) design and CSI subbands. It is also not currently agreed how to achieve a suitable PRB indexing that takes into account the above agreements.

The present invention seeks to provide a communication system and associated apparatus and methods for meeting or at least partially addressing the above issues. Specifically, the present document provides details of some of the ways in which the remaining issues of supporting wider network channel bandwidth (i.e. gNB's system bandwidth) may be achieved in NR systems, and more specifically, how to determine the PRB and RBG indexing in scenarios where the network channel bandwidth can comprise a number of smaller component carriers.

The present invention provides a communication apparatus of a radio access network, a user equipment, and corresponding methods, as set out in the appended independent claims. Optional, but advantageous features are disclosed in the appended dependent claims.

Also disclosed is a method performed by communication apparatus of a radio access network (RAN) of a telecommunication system, as defined by claim <NUM>.

Also disclosed is a method performed by a communication device for obtaining minimum system information comprising minimum parameters required to access a cell of a radio access network (RAN) of the telecommunication system, as defined by claim <NUM>.

Each feature disclosed in this specification (which term includes the claims) and/or shown in the drawings may be incorporated in the invention independently (or in combination with) with any other disclosed and/or illustrated features. In particular but without limitation the features of any of the claims dependent from a particular independent claim may be introduced into that independent claim in any combination or individually.

Whilst specific hardware apparatus having a specific physical structure (e.g. controllers and transceiver circuitry) have been disclosed for performing the various procedures described herein, each step of the methods disclosed in the description and/or forming part of the claims, may be implemented by any suitable means for performing that step. In accordance with this each method aspect of the invention has a corresponding apparatus aspect comprising respective means for performing each step of that method aspect.

Example embodiments of the invention will now be described by way of example only with reference to the attached figures in which:.

<FIG> schematically illustrates a cellular telecommunications system <NUM> in which a number of items of user equipment (UEs) <NUM> such as mobile telephones, and other fixed or mobile communication devices (e.g. MTC devices, IoT devices) can communicate with each other via a base station <NUM> and a core network <NUM> using an appropriate radio access technology (RAT). As those skilled in the art will appreciate, whilst two mobile devices <NUM> (denoted 'UE1' and 'UE2'), one MTC device <NUM> (denoted 'UE3'), and one base station <NUM> are shown in <FIG> for illustration purposes, the system, when implemented, will typically include other base stations and UEs.

The base station <NUM> forms part of a RAN and operates one or more associated cell <NUM> via which the UEs <NUM> can connect to the cellular telecommunications system <NUM>. The UEs <NUM> may connect in the cell <NUM> by establishing a radio resource control (RRC) connection with the base station <NUM> operating that cell <NUM>.

The base station <NUM> is connected to the core network <NUM> for example via an S1 interface and to any other base stations (not shown) for example via an X2 interface (either directly, or via for example an X2 gateway). The core network <NUM> typically includes logical nodes (or 'functions') for supporting communication in the telecommunication system <NUM>. Typically, for example, the core network <NUM> of a <NUM> / NR system will include, amongst other functions, control plane functions, user plane functions and other functions for providing the functionality of a mobility management entity (MME), a serving gateway (S-GW), a packet data network gateway (P-GW) etc..

In this system the system bandwidth (or 'wideband CC') can comprise a number of smaller component carriers. Therefore, the base station <NUM> is configured to operate its cell <NUM> simultaneously with multiple component carriers, some of which may have a different bandwidth to that of the wideband CC. In this example, which is illustrated in <FIG>, the base station <NUM> simultaneously operates a wideband CC (i.e. a single carrier spanning the entire system bandwidth) at least for some UEs <NUM>, and for other UEs <NUM> it operates a set of intra-band contiguous CCs (herein 'CC1' and 'CC2') which are effectively carriers within the wideband CC having a relatively smaller associated bandwidth compared to the system bandwidth.

This arrangement beneficially allows different UEs <NUM> to transmit and receive data over an appropriate part of the system bandwidth (e.g. the entire system bandwidth or only a portion thereof) depending on their needs and capabilities (as some of the UEs may be equipped with transceivers that support only a limited bandwidth). For example, as shown in <FIG>, UE1 is configured to receive or transmit over the whole network channel bandwidth since it is capable of handling a wider RF bandwidth, while UE2 and UE3 use only a part of the channel bandwidth due to e.g. their limited RF bandwidth and/or their current communication needs/settings. Although not shown, it will be appreciated that some UEs may be able to aggregate multiple component carriers (intra-band contiguous CCs with CA), when appropriate. For example, UE2 may be able to aggregate CC1 and CC2 (and/or any other CCs, within the same or in a different cell) when the bandwidth of CC1 is not sufficient. Similarly, UE1 may be able to aggregate the wideband CC and one or more additional CC (e.g. one or more additional cell) when the bandwidth of the wideband CC is not sufficient for that UE.

In order to assist the UEs <NUM> in finding its cell <NUM> and to be able to access the various CCs, the base station <NUM> provides system information in the cell <NUM>. Whilst some system information provided may be required by all UEs <NUM> in the cell <NUM> and may need to be transmitted (e.g. broadcast) on a relatively regular basis, other system information may not be required by all UEs <NUM> in the cell <NUM> at a given time and/or may not need to be sent on such a regular basis. Accordingly, the system information is divided conceptually into two different types: minimum system information and other system information.

Referring to the minimum system information, the base station <NUM> broadcasts at least some of the minimum system information in its cell <NUM>. In this example, the minimum system information includes a subset of the information blocks (such as MIB, SIB1, SIB2 and/or the like) carrying at least a part of the minimum set of information elements (e.g. those elements required to support cell selection, acquiring the remaining system information, or accessing the cell). The remaining minimum system information (RMSI) and potentially any other system information can be obtained by the UEs <NUM> using appropriate mechanisms (e.g. 'on-demand' at the request of the UE). For example, UEs <NUM> in an RRC connected state may use dedicated RRC signalling for the request and delivery of the RMSI.

Advantageously, in this network <NUM> the same PRB grid structure is used for a given numerology within the wideband CC regardless of the type or operation of UE <NUM> (narrow band UE, CA UE, or wideband UE). Some exemplary numerologies are shown in Table <NUM> below.

In LTE systems, when a UE decodes the PBCH, the UE can work out the PRB and RBG indexing straight away because the PBCH and synchronisation signals (i.e. the 'SS block') are always located at the centre frequency (i.e. the central 6RBs) of the LTE system bandwidth. On the other hand, in NR systems (e.g. as shown in <FIG>) the SS block (which corresponds to the location of the NR-PBCH) may not necessarily be at the centre frequency of the network channel bandwidth.

However, the base station <NUM> of this system beneficially uses appropriate PRB indexing in order to facilitate acquisition of NR-PBCH and RMSI by the UEs <NUM>, regardless of how the wideband CC is divided into intra-band CCs. Thus, based in such a PRB indexing, it is possible to determine the precise location of a detected SS block within the network channel bandwidth in order for the UEs <NUM> to be able to determine the associated resource block (RB) indexing (including the location of reference signals), derive channel state information (CSI), and obtain system information for the cell <NUM>.

In more detail, during the acquisition of NR-PBCH, there is a relative time between the NR-PBCH and the position of the synchronisation signals (SS), therefore the location of the NR-PBCH can be determined based on the position of the SS. In addition, since the number of PRBs carrying the NR-PBCH is fixed, there is no need for PRB indexing as there is no resource allocation signalling involved at this stage. Accordingly, the UEs <NUM> are able to obtain at least a part of the minimum system information from the NR-PBCH.

However, during acquisition of the RMSI (transmitted by the base station <NUM> over the NR-PDSCH and/or the NR-PBCH), the number of PRBs that can be scheduled to the RMSI are variable since it depends on the amount of information to be transmitted (and possibly on other factors, such as modulation being used). Therefore, the base station <NUM> employs a special scheme to indicate RMSI scheduling assignments to the UEs <NUM>, based on the exemplary PRB indexing methods described below.

In summary, in its allocation of resources to the RMSI, the base station <NUM> may employ a bandwidth for the RMSI that is confined within the bandwidth of the NR-PBCH ('option <NUM>') or employ a bandwidth for the RMSI that is larger than the bandwidth of the NR-PBCH ('option <NUM>').

In case of both option <NUM> and option <NUM>, the PRB indexing for RMSI starts from the lowest frequency of the NR-PBCH BW, and the granularity of the resource allocation scheme for RMSI scheduling is <NUM> PRB. In case of option <NUM> (i.e. when the bandwidth of the RMSI is greater than the bandwidth of the decoded NR-PBCH), the difference between the RMSI bandwidth and the NR-PBCH bandwidth (e.g. an offset amount) is given in terms of PRBs and the difference is signalled in the NR-PBCH. This beneficially allows the UEs <NUM> to obtain the location and bandwidth of the NR-PBCH (based on the detected SS block) and hence obtain at least a part of the minimum system information, then determine the RMSI bandwidth (which may equal to the NR-PBCH bandwidth or the NR-PBCH bandwidth + an offset) from the NR-PBCH.

When the base station <NUM> signals an offset value to the UEs <NUM>, the reference point for applying the offset may be either the lowest PRB of the NR-PBCH (in which case the offset increases the bandwidth upwards from the highest frequency of the NR-PBCH) or the centre PRB of the NR-PBCH (in which case the offset increases the bandwidth symmetrically both downwards from the lowest frequency of the NR-PBCH and upwards from the highest frequency of the NR-PBCH). Further details of the operation of the offset are given below with reference to <FIG> and <FIG>.

Beneficially, the RMSI in this system includes information that allows the UE <NUM> to derive the location of the NR-PBCH relative to the network channel bandwidth (regardless of which component carrier is used by that UE <NUM>). Thus, once the UE <NUM> has decoded the RMSI, it knows the location of the decoded NR-PBCH within the network channel bandwidth as well as the size of the network channel bandwidth.

It can be seen therefore that the above system meets the various requirements currently agreed for NR base stations that are configured to operate with multiple component carriers simultaneously (e.g. a wideband CC and one or more intra-band CCs within the wideband CC). The above solutions make it easier for UEs to access the RAN and/or receive system information (e.g. RMSI) via their associated carrier (wideband CC, CC1, CC2).

It will be appreciated that whilst a number of beneficial features are described above, an improved cellular communication system can still be realised even if only a subset (or one) of the beneficial features is employed.

<FIG> is a block diagram illustrating the main components of user equipment (such as a mobile telephone) <NUM> shown in <FIG>. As shown, the UE <NUM> has a transceiver circuit <NUM> that is operable to transmit signals to and to receive signals from a base station (e.g. a gNB) <NUM> via one or more antennae <NUM>. Although not necessarily shown in <FIG>, the UE <NUM> may of course have all the usual functionality of a conventional UE <NUM> (such as a user interface <NUM>) and this may be provided by any one or any combination of hardware, software and firmware, as appropriate. The UE <NUM> has a controller <NUM> to control the operation of the user equipment <NUM>.

The controller <NUM> is associated with a memory <NUM> and is coupled to the transceiver circuit <NUM>. Software may be pre-installed in the memory <NUM> and/or may be downloaded via the telecommunications network <NUM> or from a removable data storage device (RMD), for example.

The controller <NUM> is configured to control overall operation of the UE <NUM> by, in this example, program instructions or software instructions stored within the memory <NUM>. As shown, these software instructions include, among other things, an operating system <NUM>, a communications control module <NUM> and a system information management module <NUM>.

The communications control module <NUM> is operable to control communications between the UE <NUM> and the base station <NUM>. The communications control module <NUM> also controls the separate flows of uplink data and control data that are transmitted to the base station <NUM> and the reception of downlink data and control data (including system information) transmitted by the base station <NUM>. The communications control module <NUM> is responsible, for example, for managing the UE's part in idle and connected mode procedures such as cell (re)selection, camping on cells, random access channel (RACH) procedures, etc..

The system information management module <NUM> is responsible for managing the listening for, receipt, storage and interpretation of the system information (minimum system information and/or other system information), for deriving appropriate indexing being used in the cell <NUM> of the base station <NUM> to which the UE <NUM> is connected (or attempts to connect). Specifically, the system information management module <NUM> is responsible for determining the location of the RMSI within the system bandwidth (for a given CC and/or numerology).

<FIG> is a block diagram illustrating the main components of a base station <NUM> of the type shown in <FIG>. As shown, the base station <NUM> includes a transceiver circuit <NUM> which is operable to transmit signals to and to receive signals from UEs <NUM> via one or more antennae <NUM> and which is operable to transmit signals to and to receive signals from the functions of the core network <NUM> via a core network interface <NUM> and/or other base stations via a base station interface <NUM>. The network interface typically comprises an S1 (or S1-like) interface for communicating with the core network <NUM> and an X2 (or X2-like) interface for communicating with other base stations. A controller <NUM> controls the operation of the transceiver circuit <NUM> in accordance with software stored in the memory <NUM>. The software includes, among other things, an operating system <NUM>, a communications control module <NUM> and a system information management module <NUM>. Software may be pre-installed in the memory <NUM> and/or may be downloaded via the telecommunications network <NUM> or from a removable data storage device (RMD), for example.

The communications control module <NUM> is operable to control communications between the base station <NUM> and the UEs <NUM> and other network entities that are connected to the base station <NUM>. The communications control module <NUM> also controls the separate flows of uplink and downlink user traffic and control data (including system information) for the UEs <NUM> served by the base station <NUM>. Such control data may also include, for example, control data for managing the operation of the UEs <NUM> and for the provision of the RMSI (e.g. PRB scheduling / PRB indexing). The communications control module <NUM> is responsible, for example, for controlling procedures such as the communication of measurement control / configuration information, system information, the base station's part in random access channel (RACH) procedures, etc..

The system information management module <NUM> is responsible for managing the generation of system information (SI) messages carrying appropriate system information (minimum system information and/or other system information), for determining whether to transmit a particular piece (block) of system information (to a given UE or UE group), and for providing an appropriate indexing for the cell <NUM> of the base station <NUM> for the provision of the system information. The system information management module <NUM> is also responsible for allocating appropriate resources for the RMSI within the system bandwidth (for a given CC and/or numerology) such that UEs <NUM> that need it can obtain it. Such resources are typically allocated in a broadcast channel (e.g. NR-PBCH) or another shared channel (e.g. NR-PDSCH).

<FIG> and <FIG> schematically illustrate exemplary ways in which RMSI bandwidth may be defined with relation to the PBCH bandwidth in the system <NUM> of <FIG>.

As described above, the SS block that contains the NR-PBCH may not necessarily be at the centre frequency of the network channel bandwidth (in NR systems). Moreover, there might be multiple component carriers provided simultaneously within the network channel bandwidth.

The following exemplary mechanism may be used to provide a precise location of the detected SS block within the network channel bandwidth in order the UEs to be able to determine the resource block (RB) indexing, generate reference signal (RS) and derive the channel state information (CSI).

Since there is a known (predefined) relative time between the NR-PBCH and the position of the synchronisation signals, the location of the NR-PBCH can be easily determined by the UE <NUM> once it has detected the synchronisation signals. In addition, the number of PRBs carrying the NR-PBCH is fixed, so, there is no need for PRB indexing as there is no resource allocation signalling involved at this stage. In other words, the UE <NUM> is configured to decode the content of the entire NR-PBCH (which will typically include at least a part of the minimum system information).

During the acquisition of the RMSI (i.e. the part of the minimum system information that was not included in the initial NR-PBCH transmission), the number of PRBs that can be scheduled to RMSI can be variable (depending on e.g. the amount of information to be transmitted). Therefore, RMSI scheduling assignments (based on for example PRB indexing) are carried out for handling the resource allocation for the RMSI transmission.

In a first example, the bandwidth of the RMSI (for both control and data signalling) is confined within the bandwidth of the NR-PBCH. This may be possible, for example, if the size of the RMSI is relatively small. In this case, therefore, the PRBs can be indexed in the order of increasing frequency-domain (i.e. from the lowest to the highest frequency of the NR-PBCH bandwidth). However, as the UE <NUM> may not know the network channel bandwidth at this phase yet, it is not required to derive the appropriate global PRB and RBG indexing. Thus, any PRB indexing for the RMSI (if provided) is to be interpreted within the set of PRBs corresponding to the NR-PBCH bandwidth (rather than the network channel bandwidth).

In this example, the preferred granularity of the resource allocation scheme for RMSI scheduling is <NUM> PRB as this does not have an impact on other active UEs in the same cell that are scheduled based on e.g. RBG granularity. However, it will be appreciated that any other suitable granularity may be chosen, where appropriate.

In a second example, the bandwidth of the RMSI (for control and data signalling) can be larger than the bandwidth of the NR-PBCH. In other words, in this case the RMSI bandwidth includes (or overlaps with) the set of PRBs corresponding to the NR-PBCH bandwidth and a set of additional PRBs (at least one PRB). If the bandwidth required for the RMSI is larger than the bandwidth of the NR-PBCH, then the PRBs can be indexed for example in the order of increasing frequency-domain starting from the lowest frequency of the NR-PBCH bandwidth and continuing upward. In this case the lowest PRB of the NR-PBCH bandwidth serves as the reference point for determining the scheduling of the RMSI. Thus, if more resources are needed than the resources corresponding to the NR-PBCH bandwidth, the resource allocation span can simply be increased further upward (as shown in <FIG>). Alternatively, as shown in <FIG>, with the lowest PRB of the NR-PBCH bandwidth being the reference point, the resource allocation span can be increased in symmetric manner, by extending (by an equal amount) both the lowest and highest PRBs for RMSI scheduling beyond the size of the NR-PBCH bandwidth. Beneficially, the expanded RMSI bandwidth (e.g. a total bandwidth / total number of PRBs), or at least the amount of increase (e.g. an offset / number of PRBs in addition to the NR-PBCH bandwidth) can be signalled to the UEs in the NR-PBCH.

In summary, the bandwidth of the RMSI is preferably confined within the bandwidth of the decoded NR-PBCH (at least when the size of the RMSI allows it). In this case, PRB indexing for RMSI may start from the lowest frequency of the NR-PBCH bandwidth, and the granularity of the resource allocation scheme for RMSI scheduling may be <NUM> PRB. If the bandwidth of the RMSI is increased compared to the bandwidth of the decoded NR-PBCH (e.g. depending on the size of the RMSI and/or UE capability), the amount of increase (e.g. an offset) in terms of PRBs may be signalled to the UEs in the NR-PBCH. This beneficially allows each UE to determine the appropriate RMSI bandwidth for that UE from the NR-PBCH (wherein the RMSI bandwidth may equal to the NR-PBCH bandwidth or the NR-PBCH bandwidth + an offset). Alternatively, an offset from the lowest PRB index of the channel bandwidth (or bandwidth part) to the lowest PRB index or the centre of the NR-PBCH can be signalled in the NR-PBCH.

<FIG> illustrates an exemplary way for deriving the location of the PBCH in NR systems (such as the cellular telecommunication system <NUM> shown in <FIG>). Moreover, <FIG> illustrates a possible (global) RBG indexing for such NR systems.

After the UE <NUM> has decoded the RMSI and any information included in the RMSI (based on for example one of the techniques described with reference to <FIG> and <FIG>), the UE <NUM> immediately knows the location of the NR-PBCH within the network channel bandwidth as well as the size of the network channel bandwidth explicitly.

For example, the UE <NUM> may be informed about the location of the decoded NR-PBCH (and/or the detected SS block) within the network channel bandwidth via the RMSI by signalling the starting PRB index of the decoded NR-PBCH using the PRB indexing of the wider channel bandwidth. Effectively, the indication of the starting PRB index of the decoded NR-PBCH serves as an indication of an offset for the NR-PBCH from the first PRB of the system bandwidth (i.e. the PRB having index '<NUM>'), from which the UE <NUM> is able to work out the location of the first PRB (and hence any other PRB) of the system bandwidth based on the applicable subcarrier spacing/ numerology.

This approach is generally illustrated in <FIG>. In this example shown, the starting PRB (or offset) of the RMSI (or the starting PRB of the PBCH, when the RMSI is confined within the PBCH or it extends upwards only) has a PRB index '<NUM>'. Thus, in this example, the value '<NUM>' may be included in the RMSI (e.g. in an appropriate information element thereof). This beneficially allows the base station <NUM> to provide the NR-PBCH (and the SS block and/or RMSI) anywhere within its associated system bandwidth (not only in the centre portion) and may in turn allow greater flexibility for providing multiple CCs within the system bandwidth.

The UE <NUM> is configured to take the received PRB information (signalled via the RMSI) as a reference point for determining the global PRB indexing within the network channel bandwidth. When the UE <NUM> knows the global PRB indexing based on the reference point, it can also work out the number of RBGs within the network channel bandwidth. For example, as illustrated in <FIG>, the RBGs may be indexed in the order of increasing frequency-domain (i.e. staring from the lowest frequency) for a given subcarrier spacing/numerology.

A number of detailed example embodiments have been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above example embodiments whilst still benefiting from the inventions embodied therein. By way of illustration only a number of these alternatives and modifications will now be described.

It is assumed in the above examples that the PBCH and RMSI are using same numerologies (i.e. the same subcarrier spacing and CP length). However, if there are different numerologies, the numerologies may preferably be aligned from the centre of the PBCH bandwidth so that the amount of PRBs used for the RMSI on both sides is equal before expanding the RMSI bandwidth. Effectively, this means that the PRB boundary for different numerologies is always aligned from the centre of the PBCH bandwidth. As agreed in RAN1, alignment means that if the subcarriers in a PRB are numbered from '<NUM>' to '<NUM>', for a given SCS F0, then subcarrier '<NUM>' always coincides with a subcarrier '<NUM>' of all SCS of order less than F0.

In the above example embodiments, a number of software modules were described for implementing the user equipment <NUM> and base station <NUM>. As those skilled will appreciate, such software modules may be provided in compiled or un-compiled form and may be supplied to the corresponding hardware as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the corresponding hardware in order to update its functionality. Similarly, although the above example embodiments employed transceiver circuitry, at least some of the functionality of the transceiver circuitry can be performed by software.

The functionality of the user equipment <NUM> and base station <NUM> will typically be implemented using one or computer processing apparatus having one or more hardware computer processors programmed using appropriate software instructions to provide the required functionality. It will be appreciated that all or part of this functionality may be implemented in hardware as dedicated circuitry for example using one or more dedicated integrated circuits such as an application specific integrated circuit (ASIC) or the like.

It will be appreciated that the controllers referred to in the description of the UE <NUM>, and base station <NUM> may comprise any suitable controller such as, for example an analogue or digital controller. Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input/output (IO) circuits; internal memories / caches (program and/or data); processing registers; communication buses (e.g. control, data and/or address buses); direct memory access (DMA) functions; hardware or software implemented counters, pointers and/or timers; and/or the like.

Whilst the base station <NUM> has been described in terms of a gNB it may be any suitable base station including a base station in which the functionality of a gNB may be split between one or more distributed units (DUs) and a central unit (CU) with a CU typically performing higher level functions and communication with the next generation core and with the DU performing lower level functions and communication over an air interface with user equipment (UE) in the vicinity (i.e. in a cell operated by the gNB).

In the above example embodiments, the base station uses a 3GPP radio communications (radio access) technology to communicate with the mobile device. However, any other radio communications technology (i.e. WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) can be used between the base station and the mobile device in accordance with the above example embodiments.

Items of user equipment might include, for example, communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop/ tablet computers, web browsers, e-book readers and/or the like. Such mobile (or even generally stationary) devices are typically operated by a user, although it is also possible to connect so-called 'Internet of Things' (IoT) devices and similar machine-type communication (MTC) devices to the network. For simplicity, the present application refers to mobile devices (or UEs) in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and/or generally stationary) that can connect to a communications network for sending/receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.

It will be appreciated that the following modifications and alternatives are also possible (using the wording of the above described aspects of the invention):.

The at least one further communication resource may be dependent on (e.g. confined within or overlaps with) the first set of at least one communication resource.

The information identifying an allocation may comprise at least one of: information identifying an index associated with a physical resource block (PRB); and a number of PRBs (e.g. an offset) representing a difference compared to the first set of at least one communication resource. In this case, the PRBs within the first set of at least one communication resource may be indexed in order of increasing frequency-domain. Preferably, the resource allocation may have a granularity of one PRB.

The minimum system information may comprise minimum parameters required to access one of a plurality of component carriers (CCs) associated with the cell. In this case, the plurality of component carriers may comprise at least one wideband CC and/ or at least one intra-band CC.

The first set of communication resources may comprise a predetermined set of communication resources (which may be dependent on e.g. a location of at least one synchronisation signal transmitted in the cell and/or a numerology associated with the cell).

The minimum system information may comprise information identifying the location of the PBCH and/or the remaining minimum system information (RMSI) within the network channel bandwidth of the cell (e.g. an index of a starting PRB of the PBCH/ RMSI within the network channel bandwidth). In this case, the communication device may be configured to determine a global PRB indexing within a network channel bandwidth based on the received information identifying the location of the PBCH/ RMSI within the network channel.

The communication apparatus may comprise a base station (e.g. a 'gNB') for a New Radio (NR) system, and the communication device may comprise user equipment (UE) for a NR system.

Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

Claim 1:
A method performed by a communication apparatus (<NUM>) of a radio access network, RAN, the method comprising:
transmitting, to a user equipment, UE (<NUM>), via a physical broadcast channel, PBCH, a first part of minimum system information including information indicating a first bandwidth; and
transmitting a second part of the minimum system information using the first bandwidth,
wherein the information indicates a frequency offset to a reference point relative to a smallest resource block included in the PBCH.