10 Primitives of the physical layer
25.3023GPPRelease 17Services provided by the physical layerTS
The Physical layer interacts with other entities as illustrated in figure 1. The interactions with the MAC layer and the RRC layer are shown in terms of primitives where the primitives represent the logical exchange of information and control between the physical layer and higher layers. They do not specify or constrain implementations. The (adjacent) layers connect to each other through Service Access Points (SAPs). Primitives, therefore, are the conveyers of the information exchange and control through SAPs.
Four types of primitives are used for the present document, as follows.
– REQUEST (REQ):
– This type is used when a higher layer is requesting a service from a lower layer.
– INDICATION (IND):
– This type is used by a lower layer providing a service to notify its higher layer of activities concerning that higher layer.
– RESPONSE (RESP):
– This type is used by a higher layer providing the indicated service to respond to its lower layer that the activity has been completed.
– CONFIRM (CNF):
– This type is used by a lower layer providing the requested service to confirm to the higher layer that the activity has been completed.
The primitives defined below are for local communications between MAC and L1, as well as RRC and L1 in the same protocol stack.
For the physical layer two sets of primitives are defined:
– Primitives between layer 1 and 2:
– PHY ‑ Generic name ‑ Type: Parameters.
– Primitives between layer 1 and the RRC entity:
– CPHY ‑ Generic name ‑ Type: Parameters.
NOTE: This is a logical description of the primitives and does not cover addressing aspects (e.g. Transport Channel ID, Physical Channel ID, start frame number or disconnect frame number).
10.1 Generic names of primitives between layers 1 and 2
The primitives between layer 1 and layer 2 are shown in table 7.
Table 7: Primitives between layer 1 and 2
|
Generic Name |
Parameter |
|||
|
REQ |
IND |
RESP |
CNF |
|
|
PHY-Access |
Transport Format subset (1), ASC selected for Transport Block Set to be transmitted (5) Random Access Type (9), Random access for common E-DCH transmission (1) |
Not Defined |
Not Defined |
access information (1) |
|
PHY-Data |
TFI, E-TFI (8), Transport Block Set, CFNCELL, TTI within CFN (7), Paging Indicators (2), ASC selected for that Transport Block Set (3), HS-DSCH information (6), E-DCH information (8) |
TFI, E-TFI (8)Transport Block Set, CRC check result, TD (4), HARQ process (7) |
Not Defined |
Not Defined |
|
PHY-Status |
HARQ status (7) |
Event value, HS-DSCH Feedback information (7) |
Not Defined |
Not Defined |
|
NOTE (1): FDD only. NOTE (2): PCH only NOTE (3): 3.84/7.68 Mcps TDD RACH only NOTE (4): optional, TDD only NOTE (5): FDD RACH, and 1.28 Mcps TDD RACH and E-DCH access only NOTE (6): HS-DSCH only NOTE (7): HS-DSCH and E-DCH only NOTE (8): E-DCH only NOTE (9): 1.28 Mcps TDD only |
||||
10.1.1 PHY-Access-REQ
The PHY-Access-REQ primitive is used to request access to either a RACH transport channel from the physical layer. A PHY-Access primitive is submitted once before the actual data for peer-to-peer communication is passed to the physical layer using the PHY-Data primitive. This primitive is used in FDD and 1.28 Mcps TDD only.
In FDD, the PHY-Access-REQ primitive is also used to request the physical layer to access a common E-DCH transport channel. A PHY-Access-REQ primitive is submitted before the actual data for peer-to-peer communication is passed to the physical layer.
Parameters:
– Transport Format subset.
– ASC selected for Transport Block Set to be transmitted (FDD RACH, FDD common E-DCH and 1.28 Mcps TDD RACH and E-DCH access only)
– Random Access Type (1.28 Mcps TDD only)
– Random access for common E-DCH transmission (FDD only for common E-DCH)
10.1.2 PHY-Access-CNF
The PHY-Access-CNF primitive is used to confirm that physical layer synchronisation has been established and that the physical layer is ready for data transmission using the PHY-Data primitive. This primitive is used in FDD and 1.28 Mcps TDD only.
Parameters:
– access information.
10.1.3 PHY-Data-REQ
The PHY-Data primitives are used to request SDUs used for communications passed to and from the physical layer. One PHY-Data primitive is submitted every Transmission Time Interval for each Transport Channel.
Parameters:
– TFI;
– E-TFI (E-DCH only);
– HARQ Process (TDD E-DCH only);
– Transport Block Set;
– CFNCELL;
– TTI within CFN (HS-DSCH and FDD E-DCH (2ms TTI) only);
– Page Indicators (PIs) (PCH only);
– HS-DSCH information (HS-DSCH information);
– E-DCH information (E-DCH information);
– ASC selected for that Transport Block Set (3.84/7.68 Mcps TDD RACH only);
– Random access type (1.28 Mcps TDD RACH only).
10.1.4 PHY-Data-IND
The PHY-Data primitives are used to indicate SDUs used for Layer 2 passed to and from the physical layer. One PHY-Data primitive is submitted every Transmission Time Interval for each Transport Channel.
Parameters:
– TFI;
– E-TFI (E-DCH only);
– Transport Block Set;
– CRC check result;
– TD (RX Timing Deviation measurement) (optional, TDD only);
– Process Id (HS-DSCH and E-DCH only);
– Retransmission number (E-DCH only).
10.1.5 Void
10.1.6 Void
10.1.7 PHY-Status-IND
The PHY-Status-IND primitive can be used by the layer 1 to notify higher layers of an event that has occurred.
Parameters:
– Feedback information (HS-DSCH and E-DCH only);
– Event value:
– L1 hardware failure has occurred.
10.2 Generic names of primitives between layers 1 and 3
The status primitives between layer 1 and 3 are shown in table 8.
Table 8: Status primitives between layer 1 and 3
|
Generic Name |
Parameter |
|||
|
REQ |
IND |
RESP |
CNF |
|
|
CPHY-Sync |
Not Defined |
CCTrCH ID (1) |
Not Defined |
Not Defined |
|
CPHY-Out-of-Sync |
Not Defined |
CCTrCH ID (1) |
Not Defined |
Not Defined |
|
CPHY-Measurement |
transmission power threshold, measurement parameters |
measurement parameters |
Not Defined |
Not Defined |
|
CPHY-Error |
Not Defined |
error code |
Not Defined |
Not Defined |
|
NOTE (1): TDD only. |
||||
10.2.1 STATUS PRIMITIVES
10.2.1.1 CPHY-Sync-IND
This primitive is used for L1 to indicate to RRC that synchronisation of a certain physical channel has been done in the receiver. In FDD synchronisation is based on reception of the DPCCH or F-DPCH, and in TDD synchronisation is based on Special Burst, TB reception, and DPCH burst quality estimation. For 3.84/7.68 Mcps TDD, when the UE is in cell_DCH state but no DL DPCH is configured the primitive is based on the methods specified in [5].
Parameters:
– CCTrCH ID (TDD only).
10.2.1.2 CPHY-Out-of-Sync-IND
Primitive sent from L1 to RRC indicating that synchronisation of a previously configured connection has been lost in the receiver. In FDD synchronisation is based on reception of the DPCCH or F-DPCH, and in TDD synchronisation is based on Special Burst, TB reception, and DPCH burst quality estimation. For 3.84 /7.68Mcps TDD, when the UE is in cell_DCH state but no DL DPCH is configured the primitive is based on the methods specified in [5].
Parameters:
– CCTrCH ID (TDD only).
10.2.1.3 CPHY-Measurement-REQ
The Request primitive is used for RRC to configure L1 measurements.
Parameters:
– transmission power threshold;
– refer to clause 9 for measurement parameters.
10.2.1.4 CPHY-Measurement-IND
The Indication primitive is used to report the measurement results.
Parameters:
– refer to clause 9 for measurement parameters.
10.2.1.5 CPHY-Error-IND
The CPHY-Error primitive is used to indicate to the management entity that an error has occurred as a result of a physical layer fault.
Parameters:
– error code.
10.2.1.6 Void
10.2.2 CONTROL PRIMITIVES
The control primitives between layer 1 and 3 are shown in table 9.
Table 9: Control primitives between layer 1 and 3
|
Generic Name |
Parameter |
|||
|
REQ |
IND |
RESP |
CNF |
|
|
CPHY-TrCH-Config |
transport channel description |
Not Defined |
Not Defined |
No Parameter |
|
CPHY-TrCH-Release |
No Parameter |
Not Defined |
Not Defined |
No Parameter |
|
CPHY-RL-Setup |
physical channel description |
Not Defined |
Not Defined |
No Parameter |
|
CPHY-RL-Release |
No Parameter |
Not Defined |
Not Defined |
No Parameter |
|
CPHY-RL-Modify |
physical channel description |
Not Defined |
Not Defined |
No Parameter |
|
CPHY-Commit |
activation time |
Not Defined |
Not Defined |
Not Defined |
|
CPHY-Out-of-Sync-Config |
Out of Sync detection parameters |
Not Defined |
Not Defined |
No Parameter |
|
CPHY-MBMS-Config |
MBMS information |
Not Defined |
Not Defined |
No Parameter |
10.2.2.1 CPHY-TrCH-Config-REQ
This primitive is used for setting up and configuring a transport channel, and also to modify an existing transport channel.
Parameters:
– transport channel description.
10.2.2.2 CPHY-TrCH-Config-CNF
This primitive is used for confirming the setting up and configuring a transport channel, and also modifying an existing transport channel.
Parameters:
– No Parameter.
10.2.2.3 CPHY-TrCH-Release-REQ
This primitive is used for releasing a transport channel.
Parameters:
– No Parameter.
10.2.2.4 CPHY-TrCH-Release-CNF
This primitive is used for confirming the releasing a transport channel.
Parameters:
– No Parameter.
10.2.2.5 CPHY-RL-Setup-REQ
The Request primitive is sent from RRC to L1 for establishment of a Radio link to a certain UE.
Parameters:
– physical channel description.
10.2.2.6 CPHY-RL-Setup-CNF
The Confirm primitive is returned from L1 to RRC when the Radio link is established. In case L1 is unable to execute the request, this is indicated in the confirm primitive.
Parameters:
– No Parameter.
10.2.2.7 CPHY-RL-Release-REQ
The Request primitive is sent from RRC to L1 for release of a Radio link to a certain UE.
Parameters:
– No Parameter.
10.2.2.8 CPHY-RL-Release-CNF
The Confirm primitive is returned from L1 to RRC when the radio link is released.
Parameters:
– No Parameter.
10.2.2.9 CPHY- RL-Modify-REQ
The Request primitive is sent from RRC to L1 for modification of a Radio link to a certain UE.
Parameters:
– physical channel description.
10.2.2.10 CPHY-RL-Modify-CNF
The Confirm primitive is returned from L1 to RRC when the radio link is modified. In case L1 is unable to execute the request, this is indicated in the confirm primitive.
Parameters:
– No Parameter.
10.2.2.11 CPHY-Commit-REQ
This primitive is sent from RRC to L1 to synchronise UE and NW for the physical channel modification.
Parameters:
– activation time.
10.2.2.12 Void
10.2.2.13 Void
10.2.2.14 Void
10.2.2.15 Void
10.2.2.16 CPHY-Out-of-Sync-Config-REQ
This primitive is sent from RRC to Node B L1 to reconfigure the parameters to detect "in sync" and "out of sync" conditions of uplink physical channel transmission.
Parameters:
– Out of Sync detection parameters
10.2.2.17 CPHY-Out-of-Sync-Config-CNF
This primitive is sent from Node B L1 to RRC for confirming the Reconfiguration of the Out-of-Sync parameters on Node B L1.
Parameters:
– No Parameter.
10.2.2.18 CPHY-MBMS-Config-REQ
This primitive is sent from UE RRC to L1 for the configuration of the MBMS information.
Parameters:
– MBMS information.
10.2.2.19 CPHY-MBMS-Config-CNF
This primitive is used to confirm the configuration of the MBMS information.
Parameters:
– No Parameter.
10.3 Parameter definition
10.3.1 Error code
– Hardware failure.
10.3.2 Event value
– Maximum transmission power has been reached.
– Allowable transmission power has been reached.
– Average transmission power is below allowable transmission power.
– Maximum number of retransmissions has been reached.
– Loss of DL DPCCH.
10.3.3 Access Information
– Ready for RACH data transmission (in case of FDD mode: when Ack on AICH has been received and Random access for common E-DCH transmission was not included in the PHY-Access-REQ, in case of 1.28 Mcps TDD: when Ack on FPACH has been received);
– timeout, no response on AICH (FDD only) or FPACH (1.28 Mcps TDD only) has been received while maximum number of access preamble transmissions (FDD only) /synchronisation attempts (1.28 Mcps TDD only) has been performed.
The following value of this parameter apply to FDD only:
– NACK has been received carried with an AI, if the use of E-AIs is not configured, or carried with an E-AI, if the use of E-AIs is configured on AICH;
– E-DCH resource index received on AICH (when Ack carried with an AI has been received, or when Nack carried with an AI and no Nack carried with an E-AI has been received), if Random access for common E-DCH transmission was included in the PHY-Access-REQ.
10.3.4 Transport Format Subset
– A subset of the Transport Format set of a Transport Channel.
10.3.5 Physical channel description
10.3.5.1 Primary SCH
– Tx diversity mode.
10.3.5.2 Secondary SCH
– Tx diversity mode.
10.3.5.3 Primary CCPCH
– Frequency info.
– DL scrambling code.
– Tx diversity mode.
– Timeslot (TDD only).
– Burst type (3.84/7.68 Mcps TDD only).
– Offset (TDD only).
– Repetition period (TDD only).
– Repetition length (TDD only).
10.3.5.4 Secondary CCPCH
– DL scrambling code.
– Channelisation code.
– Tx diversity mode.
– Timeslot (TDD only).
– Burst type (3.84/7.68 Mcps TDD only).
– Midamble shift (TDD only).
– Offset (TDD only).
– Repetition period (TDD only).
– Repetition length (TDD only).
– TFCI presence (TDD only).
– MCCH modification period (only S-CCPCH carrying MCCH).
– MCCH repetition period (only S-CCPCH carrying MCCH).
– MCCH access info period (only S-CCPCH carrying MCCH).
– MSCH scheduling period/offset (only S-CCPCH carrying MSCH).
10.3.5.4a Secondary CCPCH frame type 2
– Channelisation code(s).
– Sub-frame.
– MSCH scheduling period/offset (only S-CCPCH carrying MSCH).
10.3.5.5 PRACH
– Access Slot (FDD only).
– Preamble scrambling code (FDD only).
– Available preamble signatures (FDD only).
– Spreading factor for data part.
– Power control info:
– UL target SIR;
– primary CCPCH DL TX Power;
– UL interference;
– power offset (Power ramping) (FDD only).
– Access Service Class Information (PRACH Partitioning):
– Available signatures for each ASC (FDD only).
– Available Channelisation codes for each ASC (TDD only).
– Available Subchannels for each ASC.
– AICH transmission timing parameter (FDD only).
– Timeslots (TDD only).
– Available Channelisation Codes (TDD only)
– Spreading Factor (TDD only).
– Midamble Type (TDD only).
10.3.5.6 Uplink DPDCH+DPCCH
– UL scrambling code.
– DPCCH slot structure (Npilot, NTPC, NTFCI, NFBI).
– Transmission Time offset value.
10.3.5.7 Uplink DPCH
– Timing Advance (TDD only).
– DPCH channelisation code (TDD only).
– Burst Type (3.84/7.68 Mcps TDD only).
– DPCH midamble shift (TDD only).
– Timeslot (TDD only).
– Offset (TDD only).
– Repetition Period (TDD only).
– Repetition length (TDD only).
– TFCI presence (TDD only).
10.3.5.8 Downlink DPCH
– Transmission Time offset value.
– DL scrambling code:
– DL Channelisation code.
– Tx diversity mode:
– FB mode (FDD only).
– Slot structure (Npilot, NTPC, NTFCI, NFBI, , Ndata1, Ndata2) (FDD only).
– Burst Type (3.84/7.68 Mcps TDD only).
– DPCH midamble shift (TDD only).
– Timeslot (TDD only).
– Offset (TDD only).
– Repetition period (TDD only).
– Repetition length (TDD only).
– TFCI presence (TDD only).
10.3.5.8a F-DPCH (FDD only)
– Transmission Time offset value.
– DL scrambling code:
– DL Channelisation code.
10.3.5.9 Void
10.3.5.10 PICH
– Scrambling code.
– Channelisation code.
– Timeslot (TDD only).
– Burst Type (3.84/7.68 Mcps TDD only).
– Midamble shift (TDD only).
– Offset (TDD only).
– Repetition period (TDD only).
– Repetition length (TDD only).
10.3.5.11 AICH
– Scrambling code.
– Channelisation code.
– Tx diversity mode.
NOTE: The value for the parameters needs to be consistent with the corresponding PRACH.
10.3.5.12 Void
10.3.5.13 Void
10.3.5.14 Void
10.3.5.15 Void
10.3.5.16 PDSCH (TDD only)
– Scrambling code.
– Channelisation code.
– Tx diversity mode:
– DL channelisation code (TDD only).
– Burst Type (3.84/7.68 Mcps TDD only).
– PDSCH Midamble shift (TDD only).
– Timeslot (TDD only).
– Offset (TDD only).
– Repetition period (TDD only).
– Repetition length (TDD only).
– TFCI presence (TDD only).
10.3.5.17 PUSCH
– PUSCH channelisation code.
– Burst Type (3.84/7.68 Mcps TDD only).
– PUSCH midamble shift (TDD only).
– Timeslot (TDD only).
– Offset (TDD only).
– Repetition period (TDD only).
– Repetition length (TDD only).
– TFCI presence (TDD only).
– Timing Advance (TDD only).
10.3.5.18 DwPCH (1.28 Mcps TDD only)
– Tx diversity mode.
– SYNC_DL code ID.
10.3.5.19 UpPCH (1.28 Mcps TDD only)
– SYNC_UL code ID.
10.3.5.20 FPACH (1.28 Mcps TDD only)
– Scrambling code
– Channelisation code
– Timeslot
– Midamble shift
– Tx diversity mode.
10.3.5.21 PNBSCH (Physical Node B Synchronisation channel)
– Node B – Node B over the air communication.
– Only for TDD cells.
– Repetition period.
– Concatenated periodically Extended Complementary sequences.
10.3.5.22 HS-SCCH
– Scrambling code.
– Channelisation code.
– Timeslot (TDD only).
– Burst type (3.84/7.68 Mcps TDD only).
10.3.5.23 HS-SICH (TDD only)
– Channelisation code.
– Burst Type 1 (3.84/7.68 Mcps TDD only).
– Midamble shift.
– Timeslot.
10.3.5.24 E-AGCH
– Scrambling code.
– Channelisation code.
– Tx diversity mode.
– Timeslot (TDD only).
– Burst type (3.84 Mcps and 7.68 Mcps TDD only).
10.3.5.25 E-DPCCH (FDD only)
– No parameter.
10.3.5.26 E-DPDCH (FDD only)
– No parameter.
10.3.5.27 E-HICH
FDD:
– Scrambling code.
– Channelisation code.
– Hadamard sequence.
TDD:
– Scrambling code.
– Channelisation code.
– First Hadamard sequence.
– Second Hadamard sequence.
– Timeslot.
10.3.5.28 E-RGCH (FDD only)
– Scrambling code.
– Channelisation code.
– Hadamard sequence.
10.3.5.28a E-RUCCH (TDD only)
– Power control info:
– UL target SIR;
– primary CCPCH DL TX Power;
– UL interference.
– Timeslot;
– Available Channelisation Code;
– Random access type (1.28 Mcps TDD only)
10.3.5.29 MICH
– Scrambling code.
– Channelisation code.
– Timeslot (TDD only).
– Burst Type (3.84/7.68 Mcps TDD only).
– Midamble shift (TDD only).
– Offset (TDD only).
– Repetition period (TDD only).
– Repetition length (TDD only).
10.3.6 Feedback information
In CELL_DCH state:
– Quality indication (HS-DSCH only).
– HARQ Status (HS-DSCH and E-DCH only).
In CELL_FACH state, if a common E-DCH is allocated to a UE (FDD only):
– Quality indication (HS-DSCH only).
– HARQ Status (HS-DSCH and E-DCH only).
In Idle mode, if a common E-DCH is allocated to a UE (FDD only):
– HARQ Status (E-DCH only).
10.3.7 HARQ process
– Process Id.
10.3.8 HS-DSCH information
– Modulation scheme.
– Channelisation code.
– Timeslot (TDD only).
– Redundancy version/Constellation.
– Process Id.
– HS-SCCH Cyclic Sequence Number (HCSN) for TDD.
10.3.9 HARQ status
– HARQ acknowledgement (acknowledgement or negative acknowledgement).
10.3.10 E-DCH information
– Number of allowed redundancy versions.
– Maximum number of transmissions
– New transmission indication
– Process Id.
– Power offset
10.3.11 MBMS information
– MBMS L1 combining schedule.
– MBMS service transmission schedule.