Commit 48f33657 authored by Lev Walkin's avatar Lev Walkin

3GPP Radio Resource Control

parent 4fe13ffa
......@@ -4,10 +4,7 @@ This directory contains a few examples.
1. The ./sample.source.PKIX1 directory contains the X.509 Certificate decoder,
as specified in rfc3280.txt. Just type `make` in there to compile.
2. The ./sample.source.TAP3 directory contains the GSM TAP3 decoder.
Before trying to compile, read the README file in that directory.
3. The ./sample.source.MHEG5 directory contains the decoder for
2. The ./sample.source.MHEG5 directory contains the decoder for
ISO 13522 MHEG-5/ITU-T T.172 (Multimedia Hypermedia Experts Group,
Multimedia Presentations). Read the README file in that directory.
......@@ -18,6 +15,14 @@ This directory contains a few examples.
Lightweight Directory Access Protocol version 3 PDU as specified in
rfc4211.txt.
5. The ./sample.source.TAP3 directory contains the GSM TAP3 decoder.
Before trying to compile, read the README file in that directory.
6. The ./sample.source.RRC directory contains the 3GPP Radio Resource Control
decoder. Before trying to compile, read the README file in that directory.
The clyx2asn1.pl script can be used to extract ASN.1 data from LyX editor files.
The crfc2asn1.pl script can be used to extract ASN.1 data from RFC texts.
For instance, it is used to extract X.509, MEGACO, and LDAPv3 ASN.1 modules
from the corresponding RFC texts (rfc3280.txt, rfc3525.txt, rfc4211.txt).
......@@ -25,5 +30,3 @@ from the corresponding RFC texts (rfc3280.txt, rfc3525.txt, rfc4211.txt).
To regenerate the .asn1 files from the original RFC texts, execute
`make clean; make` in the current directory.
The clyx2asn1.pl script can be used to extract ASN.1 data from LyX editor files.
This source diff could not be displayed because it is too large. You can view the blob instead.
GENERAL INFORMATION
===================
The 3GPP TS 25.331 RRC (Radio Resource Control) PER decoder.
Invoking `make` will compile the ASN.1 specifications from the
../rrc.asn1 file.
THERE IS NO rrc.asn1 FILE THERE YET!
OBTAINING THE RRC SPECIFICATION
================================
Due to licensing restrictions, asn1c can not include the RRC ASN.1 module
in its distribution.
To obtain the RRC ASN.1 specification, you should go to
http://www.3gpp.org/ftp/Specs/html-info/25331.htm
and download any version of RRC specification (preferably 7.1.0, 2006-06).
A .ZIP file with a Microsoft Word .DOC files will download shortly.
You should extract the ASN.1 modules from the chapter 11 of that .DOC file,
and save it as the ../rrc.asn1 file. The ../rrc.asn1 file should start with
the following line
"Class-definitions DEFINITIONS AUTOMATIC TAGS ::="
and end with the "END" token.
Be careful not to copy any preambles, chapter titles and other non-ASN.1 text.
After obtaining the rrc.asn1, type `make` in the directory containing
this README file.
rrc-dump USAGE
==============
The rrc-dump utility may be used to dump the contents of a PER-encoded
RRC protocol data unit. Since RRC specification contains multiple PDUs,
a PDU must be selected manually using -p <PDU> command line option:
./rrc-dump -p DL-DCCH-Message message.per
./rrc-dump -p PCCH-Message message.per
The list of recognized PDUs may be obtained using `-p list`.
The full list of recognized command line options may be obtained with
> ./rrc-dump -h
extern int opt_debug;
#define ASN_DEBUG(fmt, args...) do { \
if(opt_debug < 2) break; \
fprintf(stderr, fmt, ##args); \
fprintf(stderr, " (%s:%d)\n", \
__FILE__, __LINE__); \
} while(0)
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment