Actions
Feature #1821
closedBSC-side PCU socket interface for paging and RACH
Status:
Closed
Priority:
High
Assignee:
Category:
libbsc
Start date:
10/15/2016
Due date:
% Done:
100%
Resolution:
Spec Reference:
Description
When the PCU is co-located with the BTS, there's a pcu_socket interface between the two of them. This interface is usd for a lot of things, but also for
- passing of paging requests from PCU to BTS for transmission on the PCH
- passing of RACH requests for packet from BTS to PCU
In case the PCU is co-located with the BSC, this interface will have to be introduced to libbsc.
Important things to keep in mind- there will be no PH-DATA.req/.ind messages on this BSC-side PCU socket. The actual data frames are passed directly into the PCU (from E1 timeslot devices/sockets), similar to the pcu_socket bypass on the sysmoBTS devices
- on a BTS-located PCU there is a 1:1 mapping for PCU and BTS. So both ends of the socket don't need any further addressing information. In the case of a BSC-located PCU, this is different. There might be many BTSs connected to a single BSC, so when we pass around paging and RACH requests, we need to make sure from/for which BTS they actually were. The architecture is not quite clear yet. It might actually make sense to run one osmo-pcu process for each BTS, resulting in many PCUs connecting to one BSC...
Files
Actions