packets on outLink, outCI and vice versa. 7. The VC switch stores this information in its control store. 8. The network process controller informs the CON-TPC which connection identi- fier to use. 9. This response is also sent with MTid value control. 10. The CON-TPC creates a local connection endpoint identifier, cei, that is used for sending and receiving packets on the SAP between CONU and the discrimi- nator in the terminal. 11. The CON-TPC orders the link discriminator to use inCI in messages that carry data that CONU sends on cei. Consequently, messages that are received from the network, referring inCI are to be sent to the CONU, referring cei. 12. The CON-TPC informs CONU that it is connected to the remote CONU at the connection endpoint cei. 13. The CONU sends data over connection endpoint cei. 14. The link discriminator translates cei->inCI and creates one or several layer 2 messages, setting MTid to data. If several messages, each message contains only parts of the bitstring (an SDUfragment) that are sent by the CONU. 15. The link discriminator in the packet network reads the MTid, and since it is data, sends the SDU to the VC switch, here abstracted as the ASP recCon- RepCnf(inCI, SDU). 16. The VC switch uses the inCI value to look up its control store, which says that the packet shall be sent on outLink, referring outCl. There are considerable similarities between this scenario and the one for setting up circuit-switched connections. In both cases, the service user cannot send or receive anything before a connection is established, the connection identifier corre- sponds to B-channel identification, etc. Teleservices can also be established by using CON connections. Figure 3.34 shows the logical node structure in an ISDN terminal system that provides voice services over CON connections (e.g. voice over an IP network). The packet net- work access is provided over the ISDN network, using one 64-kbps CN connection (a B-channel). 3.3 Network Service Interface Scenarios Terminal System TE-UDT Teleservice 