lte sidelink resource pools and pscch period -凯发k8网页登录

this example shows how sidelink direct communication resource pools and pscch periods are defined and parameterized. it shows the relationship between the semi-static rrc pool parameters and the pscch period structure. it also shows how the dynamic scheduling parameters (dci and sci) for transmission mode 1 and mode 2 affect the final transmission resource selection.

introduction to prose direct communications and the sidelink

release 12 of the 3gpp lte standard introduced a new device-to-device (d2d) interface aimed primarily at allowing lte to support public safety communication systems. in terms of the overall lte ran, this interface enables two kinds of proximity based services (known in 3gpp as prose):

prose direct communication, where direct ue to multiple ue communication (group communication) is possible without data transmission on the uplink or downlink. this is allowed for public safety applications only and supports one or more ues being out of coverage (network and/or frequency).
prose direct discovery, where business services can be enabled for ues that are close to each other. this feature can be used for commercial applications (for example, service advertising) in the case when both ues are in network coverage.

in terms of the lower stack, the lte d2d interface is called the sidelink and, in terms of the system architecture, it is known as pc5 (in contrast to the ue/enodeb interface, uu). it comprises a collection of new physical signals, physical channels, transport channels and messages. since the sidelink is transmitted by a ue, it is closely related to the uplink, but it also incorporates some aspects of downlink synchronization and control signaling. one significant result of this design is that a ue will now have to receive and generate uplink-style (sidelink).

this example focuses solely on direct communications, where the relevant sidelink physical layer channels and signals are,

physical sidelink shared channel (pssch)
physical sidelink control channel (pscch) (carrying sci)
physical sidelink broadcast channel (psbch)
sidelink shared channel (sl-sch)
sidelink broadcast channel (sl-bch) (carrying mib-sl)
sidelink synchronization signals

in addition to the above channels, new physical layer procedures have been introduced as described in ts 36.213 section 14. a key concept in these processes is that of a resource pool which defines the subset of available subframes and resource blocks for either sidelink transmission or reception. sidelink communication is a half-duplex scheme and a ue can be configured with multiple transmit resource pools and multiple receive resource pools. the resource pools are configured semi-statically by layer 3 messaging. when data is to be sent using a resource pool, the actual transmission resources are selected dynamically from within the pool using one of two different modes:

transmission mode 1 - the serving enodeb specifies the resources via a dci format 5 message sent to the transmitting ue. this mode requires the ue to be fully connected to the network (rrc_connected state).

transmission mode 2 - the transmitting ue self-selects the resources according to rules aimed at minimizing the collision risk. this mode can be used when the ue is connected, idle (rrc_idle) or out-of-network coverage.

introduction to sidelink resource pools and pscch period

a sidelink direct communication resource pool is configured on a semi-static basis using the layer 3 sl-commresourcepool rrc message (ts 36.331 section 6.3.8). the layer 1 physical resources (subframes and resource blocks) associated with the pool are partitioned into a sequence of repeating 'hyperframes' known as pscch periods. this is the standardized term used in ts 36.213 but it is also sometimes referred to as the sa (scheduling assignment) period or sc (sidelink control) period. within a pscch period there are separate subframe pools and resource block pools for control (pscch) and data (pssch). the pscch subframes always precede those for pssch transmission. this is analogous to the symbol layout of the pdcch and pdsch ofdm symbols within a single downlink subframe, where the control region precedes the data part. the pscch carries sidelink control information (sci) messages, which describe the dynamic transmission properties of the pssch that follow it. the receiving ue searches all configured pscch resource pools for sci transmissions of interest to it. a ue can be a member of more than one sidelink communications group.

these subframe and resource block pools are defined by different parameters in the sl-commresourcepool-r12 message. the asn.1 definition of the message type (see ts 36.331 section 6.1 for general terms) is given by,

sl-commresourcepool-r12 ::= sequence {

    sc-cp-len-r12                       sl-cp-len-r12,

    sc-period-r12                       sl-periodcomm-r12,

    sc-tf-resourceconfig-r12            sl-tf-resourceconfig-r12,

    data-cp-len-r12                     sl-cp-len-r12,

    datahoppingconfig-r12               sl-hoppingconfigcomm-r12,

    ue-selectedresourceconfig-r12       sequence {

        data-tf-resourceconfig-r12          sl-tf-resourceconfig-r12,

        trpt-subset-r12                     sl-trpt-subset-r12          optional    -- need op

    }                                                               optional,   -- need or

    rxparametersncell-r12               sequence {

        tdd-config-r12                      tdd-config                  optional,   -- need op

        syncconfigindex-r12                 integer (0..15)

    }                                                               optional,   -- need or

    txparameters-r12                    sequence {

        sc-txparameters-r12                 sl-txparameters-r12,

        datatxparameters-r12                sl-txparameters-r12

    }                                                               optional,   -- cond tx

...

}

this example uses a matlab structure to contain all the simulation parameters including those representing a subset of the sl-commresourcepool-r12 message.

% this example bundles all parameters into a structure based on
% sl-commresourcepool-r12. compare this parameter structure with the rrc
% message definition from ts 36.331 section 6.3.8
commpoolparameters = pscchperiod.defaultconfig(1,'5mhz')

commpoolparameters = 
  struct with fields:
                            nslrb: 25
                       duplexmode: 'fdd'
                        tddconfig: 0
                       ueselected: 'on'
                       syncenable: 'on'
                     npscchperiod: 0
                    sc_cp_len_r12: 'normal'
                    sc_period_r12: 40
         sc_tf_resourceconfig_r12: [1x1 struct]
                  data_cp_len_r12: 'normal'
            datahoppingconfig_r12: [1x1 struct]
    ue_selectedresourceconfig_r12: [1x1 struct]
                       syncconfig: [1x1 struct]

note that some of the parameters or information elements (ie) in the message are optional, for example, depending on whether the pool configuration is for transmit or receive. if ue-selectedresourceconfig-r12 is included in the message then the ue is in transmission mode 2 (ue selected) otherwise it is in transmission mode 1 (enodeb scheduled). for more information, see the following 3gpp technical standard documents: * ts 36.331 section 6.3.8 for the definition of all the sidelink related messages and information elements, * ts 36.331 section 5.10 for layer 3 sidelink procedures, * ts 36.213 section 14 for layer 1 sidelink procedures.

modeling sidelink communication pools and pscch period with lte toolbox

this example uses a matlab handle class called pscchperiod to represent the structure of a pscch period for a single sidelink direct communications resource pool. objects of type pscchperiod can be constructed using a parameter structure which combines general transmission parameters, like transmission bandwidth and duplexing mode, with semi-static layer 3 rrc parameters, primarily from the sl-commresourcepool message (ts 36.331 section 6.3.8). an object can then be used to,

get properties which provide key information about the procedural entities in the pscch period, such as the subframe pools and resource block pools
display an image representing the resources used in the pscch period, both for resource pools and actual transmission resources
generate a baseband waveform for the pscch period containing pscch, pssch and synchronization transmissions

the following code shows how a pscchperiod object can be created, the relationship between its configuration parameters and the sl-commresourcepool message, and how it can display the locations of the physical resource pools within the pscch period.

% construct a default pscch period object to illustrate pscch/pssch
% resource pool layout within the period. this default example is
% configured for 5mhz bandwidth and 40ms length, so the overall period
% contains 40 subframes. the displayed properties of the pscchperiod object
% include the 0-based indices for both pscch and pssch subframe and
% resource block pools. the subframe pool indices are relative to the
% beginning of the period
period = pscchperiod
% display an image representing the structure of this particular pscch
% period. the lighter blue part represents the pscch resource pool for sci
% control information, and the yellow region is the pssch resource pool for
% pssch shared data
displayperiod(period);
snapnow;
% re-configure for tdd then display the updated properties and pool
% locations
period.config.duplexmode = 'tdd';
displayperiod(period);
snapnow;
% the pscchperiod class includes other default parameter structures that
% can be used to configure an object. these are based on a subset of the
% reference pool configurations of ts 36.101 section a.7.2
configuration = pscchperiod.defaultconfig(1,'5mhz')

period = 
  pscchperiod with properties:
            nsubframebegin: 0
              periodlength: 40
                    txmode: 'mode2'
         pscchsubframepool: [3 4]
    pscchresourceblockpool: [25x1 double]
          numpscchresource: 24
         psschsubframepool: [8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 ... ]
    psschresourceblockpool: [25x1 double]
               alloweditrp: [70x1 double]
             syncsubframes: []
                    config: [1x1 struct]

configuration = 
  struct with fields:
                            nslrb: 25
                       duplexmode: 'fdd'
                        tddconfig: 0
                       ueselected: 'on'
                       syncenable: 'on'
                     npscchperiod: 0
                    sc_cp_len_r12: 'normal'
                    sc_period_r12: 40
         sc_tf_resourceconfig_r12: [1x1 struct]
                  data_cp_len_r12: 'normal'
            datahoppingconfig_r12: [1x1 struct]
    ue_selectedresourceconfig_r12: [1x1 struct]
                       syncconfig: [1x1 struct]

pscch subframe and resource block pools

the pscch resource pool is parameterized by the sc-tf-resourceconfig-r12 information element which is of type sl-tf-resourceconfig-r12. this type is also used to define the pssch resource pool in the case of pssch transmission mode 2. the parameters in this ie determine both the pscch subframe and resource block pools. it contains the following parameters:

sl-tf-resourceconfig-r12 ::= sequence {

    prb-num-r12                         integer (1..100),

    prb-start-r12                       integer (0..99),

    prb-end-r12                         integer (0..99),

    offsetindicator-r12                 sl-offsetindicator-r12,

    subframebitmap-r12                  subframebitmapsl-r12

}

in the case of the pscch, the offsetindicator-r12 parameter defines the offset of the pscch period sequence relative to sfn/dfn #0. the first subframe of the i-th pscch period is given by jbegin = offsetindicator-r12 i * sc-period-r12. the subframebitmap-r12 parameter is used to select subframes from the start of a period for the pscch subframe pool. the three parameters, prb-num-r12, prb-start-r12 and prb-end-r12 are used to select the prb for the pscch resource block pool. depending on the parameter values this pool can be formed from either one or two contiguous sets of resource blocks. this is described in more detail below.

% display the parameter structure used to configure the pscch resource pools
period = pscchperiod;
pscchpoolparams = period.config.sc_tf_resourceconfig_r12

pscchpoolparams = 
  struct with fields:
            prb_num_r12: 13
          prb_start_r12: 0
            prb_end_r12: 24
    offsetindicator_r12: 0
     subframebitmap_r12: '0001100000000000000000000000000000000000'

the pscch subframe pool is defined by the subframebitmap-r12 parameter which is part of the sc-tf-resourceconfig-r12 information element. for the subframe pool the first $n'$ uplink subframes in the pscch period are selected where $n'$ is the length of the bitmap. these subframes are denoted by their indices $(l_0,l_1,\ldots,l_{n'-1})$ . the pscch subframe pool then comprises the uplink subframes associated with the 1's in the bitmap $(a_0, a_1,\ldots, a_{n'-1})$ and the resulting pool is denoted by $(l^{pscch}_0, l^{pscch}_1,\ldots, l^{pscch}_{l_{pscch}-1})$ where $l_{pscch}$ is the number of subframes in the pool.

% display the pscch subframe pool bitmap parameter, subframebitmap_r12
pscchsubframebitmap = period.config.sc_tf_resourceconfig_r12.subframebitmap_r12
% display the subframe pool indices (0-based, relative to the start of the
% pscch period) selected by the 1's in the bitmap
pscchsubframepool = period.pscchsubframepool
% change the duplexing mode to tdd and observe the difference in subframe
% pool indices to account for the new uplink subframe positions for the
% current tdd configuration
period.config.duplexmode = 'tdd';
tddconfig = period.config.tddconfig
pscchsubframepool = period.pscchsubframepool

pscchsubframebitmap =
    '0001100000000000000000000000000000000000'
pscchsubframepool =
     3     4
tddconfig =
     0
pscchsubframepool =
     7     8

the pscch resource block pool is defined by the three parameters prb-start-r12, prb-end-r12 and prb-num-r12, which are also part of the sc-tf-resourceconfig-r12 information element.

the parameters define two bands prb-start-r12 $\le q <$ (prb-start-r12 prb-num-r12) and (prb-end-r12 - prb-num-12) $< q \le$ prb-end-r12. the resulting indices are denoted by $(m^{pscch}_0, m^{pscch}_1,\ldots, m^{pscch}_{m^{pscch\_rp}_{rb}-1})$ where $m^{pscch\_rp}_{rb}$ is the number of blocks in the resource pool. the bands can overlap to form a single contiguous block.

% display the pscch resource block pool parameters, prb_start-r12, prb-end-r12, prb-num-r12
prbstart = period.config.sc_tf_resourceconfig_r12.prb_start_r12
prbend = period.config.sc_tf_resourceconfig_r12.prb_end_r12
prbnum = period.config.sc_tf_resourceconfig_r12.prb_num_r12
% display the resource block pool indices (0-based) resulting from these
% parameters
pscchprbpool = period.pscchresourceblockpool
% change the prb-num-r12 parameter and observe the difference in the
% resource block pool indices to account for the reduction in the size of
% the pool bands
prbnum = 2
period.config.sc_tf_resourceconfig_r12.prb_num_r12 = prbnum;
pscchprbpool = period.pscchresourceblockpool

prbstart =
     0
prbend =
    24
prbnum =
    13
pscchprbpool =
     0
     1
     2
     3
     4
     5
     6
     7
     8
     9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
prbnum =
     2
pscchprbpool =
     0
     1
    23
    24

the following demonstrates some of the effects of these parameters visually.

% display the pscch pool resource locations for the default configuration.
% for this parameterization the pscch resource block pool spans the entire
% bandwidth and the pscch subframe pool is a pair of contiguous subframes
% (the lighter blue area towards the start of the period)
period = pscchperiod;
displayperiod(period);
snapnow;
% modify the subframe bitmap and resource block pool parameters to create
% non-contiguous pools
newconfig.prb_num_r12 = 6;
newconfig.prb_start_r12 = 2;
newconfig.prb_end_r12 = 23;
newconfig.offsetindicator_r12 = 0;
newconfig.subframebitmap_r12 = '0101010000000000000000000000000000000000';
period.config.sc_tf_resourceconfig_r12 = newconfig;
displayperiod(period);
snapnow;

pssch subframe and resource block pools

the parameterization and structure of the pssch subframe and resource block pool depends on the transmission mode.

for transmission mode 1, the pssch subframe pool comprises all the remaining uplink subframes that start immediately after the last subframe of the pscch subframe pool, $l^{pscch}_{l_{pscch}-1}$ . the pssch resource block pool comprises the full transmission bandwidth, $(0,\ldots, n_{rb}^{sl})$ .

for transmission mode 2, the rrc message uses a similar parameterization approach to that of the pscch. if the communication pool message contains a ue-selectedresourceconfig-r12 element, then the ue is in transmission mode 2 and it will self-select its final transmission resources from the pssch resource pools. these pools are defined using another instance of the same sl-tf-resourceconfig-r12 parameter set that is used to structure the pscch pools.

the ue-selectedresourceconfig-r12 information element is given by,

ue-selectedresourceconfig-r12 ::= sequence {

    data-tf-resourceconfig-r12              sl-tf-resourceconfig-r12,

    trpt-subset-r12                         sl-trpt-subset-r12  optional  -- need op

}

the additional trpt-subset-r12 parameter is a small bitmap (3 to 5 bits) which is used to restrict the set of $i_{trp}$ (time resource pattern index) values selectable by the ue. this affects the total number of transmission subframes that the ue can select from the pssch subframe pool and therefore the maximum number of transport blocks that can be sent in a scheduled period.

for the pssch subframe pool, the subframebitmap-r12 bitmap selects the pool subframes from the set of all uplink subframes that start at the subframe number given by offsetindicator-r12 (relative to the start of the period) and continue to the end of the period. the subframebitmap-r12 bitmap is repeated so that it is at least as long as the uplink subframe set and is used to select the final pssch subframe pool. the pssch resource block pool is defined in the same way as with the pscch using the three parameters, prb-num-r12, prb-start-r12 and prb-end-r12.

% configure for transmission mode 1 (not ue selected).
% note that the pssch resource pool (yellow) is always full band and
% includes all uplink subframes in the period starting immediately after
% the pscch pool (lighter blue)
period = pscchperiod;
period.config.ueselected = 'off';
displayperiod(period);
snapnow;
% change to tdd and note the subframe gaps in the period due to the
% downlink subframes
period.config.duplexmode = 'tdd';
displayperiod(period);
snapnow;
% change back to transmission mode 2 (ue selected) and fdd.
% modify the pssch resource block pool parameters to create two distinct
% prb bands
period.config.ueselected = 'on';
period.config.duplexmode = 'fdd';
period.config.ue_selectedresourceconfig_r12.data_tf_resourceconfig_r12.prb_num_r12 = 10;
period.config.ue_selectedresourceconfig_r12.data_tf_resourceconfig_r12.prb_start_r12 = 2;
% although the offset indicator is 0 relative to the start of the period,
% the leading 0's in the subframe bitmap create the gap between the period
% start and that of the pssch subframe pool
display(period.config.ue_selectedresourceconfig_r12.data_tf_resourceconfig_r12);
displayperiod(period);
snapnow;
% increase the length of the period and note the gaps created in pssch
% subframe pool due to the repetition of the pattern of 0's in the
% configured subframe bitmap (40 bits) to cover the increased number of
% uplink subframes in the period.
period.config.sc_period_r12 = 160;  % 40,60,70,80,120,140,160,240,280,320 subframes, depending on duplexing config
displayperiod(period);
snapnow;

  struct with fields:
            prb_num_r12: 10
          prb_start_r12: 2
            prb_end_r12: 24
    offsetindicator_r12: 0
     subframebitmap_r12: '0000000011111111111111111111111111111111'

sidelink transmission and dynamic resource scheduling

as described above, when data is to be sent using a resource pool, the actual transmission resources are selected dynamically from within the pool using one of two different modes,

transmission mode 1 - the serving enodeb directs the resources via a dci format 5 message sent to the transmitting ue
transmission mode 2 - the transmitting ue self-selects the resources according to rules aimed at minimizing the collision risk

in both cases, the same physical layer parameters are used to manage the actual resource selection. the difference being that, for mode 1, these parameters are provided by the network whereas, for mode 2, they are chosen randomly by the ue (ts 36.321 section 5.14.1.1 specifies - "randomly select the time and frequency resources for sl-sch and sci of a sidelink grant from the resource pool configured by upper layers. the random function shall be such that each of the allowed selections can be chosen with equal probability".)

the physical layer parameters are:

resource for pscch value ( $n_{pscch}$ ) - pscch subframes and resource blocks
time resource pattern index ( $i_{trp}$ ) - pssch subframes
resource allocation parameters (riv, hopping bits) - pssch resource blocks

resource selection for pscch transmission

the pscch control information associated with any pssch data transmission is sent twice on two separate pscch instances. each pscch uses a different single prb selected from the pscch resource block pool. the pair of subframes are selected from the pscch subframe pool. these pscch resources are signaled by a single scalar value $n_{pscch}$ ("resource for pscch"). the two subframe and prb index pairs are derived according to ts 36.213 sections 14.2.1.1 and 14.2.1.2. the range of allowed values is $0 \leq n_{pscch} < \lfloor m^{pscch\_rp}_{rb} / 2 \rfloor \cdot l_{pscch}$ . the number of allowed values is given by the numpscchresource property.

% create an example pscch period and observe the location of the pscch
% subframe and resource block pools. note that the pscch subframe pool
% contains only 2 entries in this case so all of the pool subframes will
% be used
period = pscchperiod
displayperiod(period);
snapnow;
% select a valid npscch value (use the last value in the allowed range)
% and return the associated pscch subframe and prb indices
dci.pscchresource = period.numpscchresource-1;
[subframes1,prb1,selected1] = period.getpscchresources(dci)
% let the function select an npscch value at random, as required by
% the collision avoidance mechanism used in transmission mode 2
sci.pscchresource = [];
[subframes2,prb2,selected2] = period.getpscchresources(sci)

period = 
  pscchperiod with properties:
            nsubframebegin: 0
              periodlength: 40
                    txmode: 'mode2'
         pscchsubframepool: [3 4]
    pscchresourceblockpool: [25x1 double]
          numpscchresource: 24
         psschsubframepool: [8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 ... ]
    psschresourceblockpool: [25x1 double]
               alloweditrp: [70x1 double]
             syncsubframes: []
                    config: [1x1 struct]

subframes1 =
     4     3
prb1 =
    11    23
selected1 =
    23
subframes2 =
     4     3
prb2 =
     9    21
selected2 =
    19

similar to the use of the pdcch and dci in the downlink, the pair of pscch instances carry an sci format 0 message which contains information used by the receiving ues to decode the associated pssch sequence. there is no rnti crc masking in the sci encoding. instead the receiving ues use the group destination id contained within the sci message payload to help filter out the pssch communications of interest (additional destination filtering is also done by higher layers).

sci format 0 message

release 12 of the lte standard specifies a single sci format. for more information see . the sci format 0 is defined in ts 36.212 section 5.4.3.1.1 by the following information fields:

- frequency hopping flag - 1 bit as defined in ts 36.213 section 14.1.1

- resource block assignment and hopping resource allocation - $\lceil log_2(n^{sl}_{rb}(n^{sl}_{rb} 1)/2)\rceil$ bits

-- for pssch hopping:

hopping bits - $n_{sl\_hop}$ msb bits are used to obtain the value of $\tilde{n}_{prb}(i)$ as indicated in ts 36.213 section 8.4

riv - $( \lceil log_2(n^{sl}_{rb}(n^{sl}_{rb} 1)/2)\rceil )$ bits provide the resource allocation in the subframe

-- for non-hopping pssch:

riv - $( \lceil log_2(n^{sl}_{rb}(n^{sl}_{rb} 1)/2)\rceil - n_{sl\_hop})$ bits provide the resource allocation in the subframe as defined in ts 36.213 section 8.1.1

- time resource pattern - 7 bits as defined in ts 36.213 section 14.1.1 ( $i_{trp}$ )

- modulation and coding scheme - 5 bits as defined in ts 36.213 section 14.1.1 ( $i_{mcs}$ )

- timing advance indication - 11 bits as defined in ts 36.213 section 14.2.1

- group destination id - 8 bits as defined by higher layers ( $n^{sa}_{id}$ )

% display the sci format 0 message field sizes for this example (5 mhz bw)
sci0 = ltesci(period.config,struct('sciformat','format0','freqhopping',1),'fieldsizes')
allocfields = sci0.allocation
% change bw to 10 mhz and notice the difference in resource field sizes
period.config.nslrb = 50;
sci0 = ltesci(period.config,struct('sciformat','format0','freqhopping',1),'fieldsizes')
allocfields = sci0.allocation

sci0 = 
  struct with fields:
              sciformat: 'format0'
            freqhopping: 1
             allocation: [1x1 struct]
    timeresourcepattern: 7
              modcoding: 5
            timeadvance: 11
                  nsaid: 8
                padding: 0
allocfields = 
  struct with fields:
    hoppingbits: 1
            riv: 8
sci0 = 
  struct with fields:
              sciformat: 'format0'
            freqhopping: 1
             allocation: [1x1 struct]
    timeresourcepattern: 7
              modcoding: 5
            timeadvance: 11
                  nsaid: 8
                padding: 0
allocfields = 
  struct with fields:
    hoppingbits: 2
            riv: 9

resource selection for pssch transmission

in the case of pssch, different parameters are used to specify the time and frequency resources. this differs from pscch, which signals the subframes and prb to be used by a single value.

the subframes associated with the pssch transmission are indicated by the time resource pattern index, $i_{trp}$ . this index is used to look up a bitmap from a set of tables, with the choice of table being dependent on the duplexing configuration. the selected bitmap is denoted by $({b'}_0,b'_1,\ldots,b'_{n_{trp}-1})$ where $n_{trp}$ is 6,7 or 8 depending on the table. this bitmap is repeated to form an extended bitmap $(b_0,b_1,\ldots,b_{l_{pssch}-1})$ which covers the entire pssch subframe pool. the subframes used for pssch transmission are selected by the 1 values in this extended bitmap to give the final subframe set denoted by $(n^{pssch}_0, n^{pssch}_1,\ldots, n^{pssch}_{n_{pssch}-1})$ where $n_{pssch}$ is the number of subframes that can be used for pssch transmission in the pscch period and which will also be a multiple of 4. this aligns with the fact that each transport block transmitted within the period will be sent four times using the fixed harq rv sequence = 0,2,3,1. during a pscch period, as many of the scheduled quadruples are used as transport blocks that are available to send at that time.

if frequency hopping is enabled, the resource blocks used in each of the transmission subframes depends on the riv field and hopping bits. this is in addition to the semi-static datahoppingconfig-r12 parameters and dependent resource block pool. the prb will then depend on the position of the active subframe within the subframe pool.

% display the transmission resources used within the pscch/pssch resource
% pools. turn psss/ssss/psbch on for this example
period = pscchperiod;
period.config.syncenable = 'on';
period.config.syncconfig.syncoffsetindicator_r12 = 0;
% define all the allocation control parameters, including an explicit pscch
% resource. although in mode 2, this is effectively full dci format 5
% parameterization, indicating sci format 0 and pscch resource control
dci.pscchresource = 0;             % select a specific pscch resource value
dci.timeresourcepattern = 106;     % select an unrestricted bitmap (all 1's)
dci.freqhopping = 1;               % configure frequency hopping with hopping type 2 (predefined sequence) and a single prb allocation
dci.allocation.hoppingbits = 3;    % setting the value=3 will enable hopping type 2 for all bw (1 or 2 bits)
% get the set of riv that is associated with contiguous allocations within
% the current pssch resource pool. set the first riv which will be a single
% prb allocation
[riv,range] = getallowedriv(period,dci);
dci.allocation.riv = riv(1);
% display subframe indices and prb indices associated with the dynamic allocation
[subframes,prb,poolindices] = period.getpsschresources(dci)
% display the transmission resources in addition to the pool positions
displayperiod(period,dci);
snapnow;
% display the rrc parameters that affect the pssch resource allocation and
% modify the rb offset to move the prb allocation away from the prb pool edges
period.config.datahoppingconfig_r12
period.config.datahoppingconfig_r12.numsubbands_r12 = 2;
period.config.datahoppingconfig_r12.rb_offset_r12 = 4;
displayperiod(period,dci);
snapnow;
% display the ue selected (mode 2) pscch resource pool configuration then
% modify the prb resource block pool parameters to created two distinct
% resource groups in the pool away from the band edges
dataresconfig = period.config.ue_selectedresourceconfig_r12.data_tf_resourceconfig_r12
dataresconfig.prb_start_r12 = 0;
dataresconfig.prb_end_r12 = 22;
dataresconfig.prb_num_r12 = 8;
period.config.ue_selectedresourceconfig_r12.data_tf_resourceconfig_r12 = dataresconfig;
% display the updated resource pool and its effect on the transmission resources
displayperiod(period,dci);
snapnow;
% finally generate and plot the associated baseband waveform
figure
waveform = generatewaveform(period,dci);
plot(abs(waveform)); title('pscch period baseband waveform');
snapnow;

subframes =
  columns 1 through 13
     8     9    10    11    12    13    14    15    16    17    18    19    20
  columns 14 through 26
    21    22    23    24    25    26    27    28    29    30    31    32    33
  columns 27 through 32
    34    35    36    37    38    39
prb =
  1x32 uint64 row vector
  columns 1 through 15
   12   12   11   12   23   12    0    0    0   11   12   12   11   12   23
  columns 16 through 30
   12    0    0    0   11   12   12   11   12   23   12    0    0    0   11
  columns 31 through 32
   12   12
poolindices =
  columns 1 through 13
     0     1     2     3     4     5     6     7     8     9    10    11    12
  columns 14 through 26
    13    14    15    16    17    18    19    20    21    22    23    24    25
  columns 27 through 32
    26    27    28    29    30    31

ans = 
  struct with fields:
    hoppingparameter_r12: 504
         numsubbands_r12: 2
           rb_offset_r12: 0

dataresconfig = 
  struct with fields:
            prb_num_r12: 13
          prb_start_r12: 0
            prb_end_r12: 24
    offsetindicator_r12: 0
     subframebitmap_r12: '0000000011111111111111111111111111111111'

appendix

this example uses this helper class.

selected bibliography

3gpp ts 36.101 "user equipment (ue) radio transmission and reception"

3gpp ts 36.211 "physical channels and modulation"

3gpp ts 36.212 "multiplexing and channel coding"

3gpp ts 36.213 "physical layer procedures"

3gpp ts 36.321 "medium access control (mac) protocol specification"

3gpp ts 36.331 "radio resource control (rrc) protocol specification"