Beruflich Dokumente
Kultur Dokumente
Time : 01:22:32.141
Vendor Header
UARFCN DL : 10712
Primary Scrambling Code : 406
cn-CommonGSM-MAP-NAS-SysInfo
CN Common GSM-MAP NAS System Information
Location Area Code (LAC) : 40101 (Hex 0x9CA5)
cn-DomainSysInfoList
CN-DomainSysInfoList :
[0 ] :
cn-DomainIdentity : cs-domain
cn-Type : gsm-MAP
gsm-MAP
CS Domain Specific System Information
T3212 timeout value : (10) 1.0 hours
Attach-Detach Allowed (ATT) : (1) MSs shall apply IMSI attach and detach procedure
cn-DRX-CycleLengthCoeff : 6
[1 ] :
cn-DomainIdentity : ps-domain
cn-Type : gsm-MAP
gsm-MAP
PS Domain Specific System Information
Routing area code (RAC) : 2 (Hex 0x02)
NMO : (1) Network mode of operation II
cn-DRX-CycleLengthCoeff : 6
ue-ConnTimersAndConstants
t-301 : ms100
n-301 : 0
t-302 : ms1000
n-302 : 2
t-305 : m5
t-308 : ms40
t-309 : 8
t-310 : ms40
n-310 : 0
t-311 : ms250
n-313 : s50
t-314 : s4
t-315 : s30
t-316 : s0
t-317 : infinity0
ue-IdleTimersAndConstants
t-300 : ms2000
n-300 : 3
t-312 : 2
n-312 : s1
System Information Message (SIB 2) System Information Message (SIB 3)
Time : 01:22:32.443
Vendor Header
UARFCN DL : 10712
Primary Scrambling Code : 406
sib12indicator : False
measurementControlSysInfo
use-of-HCS : hcs-not-used
cellSelectQualityMeasure : cpich-Ec-N0
intraFreqMeasurementSysInfo
intraFreqCellInfoSI-List
newIntraFreqCellList
NewIntraFreqCellSI-List-ECN0 :
[0 ] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 406
readSFN-Indicator : True
tx-DiversityIndicator : False
[1 ] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 307
readSFN-Indicator : True
tx-DiversityIndicator : False
[2 ] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 140
readSFN-Indicator : True
tx-DiversityIndicator : False
[3 ] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 208
readSFN-Indicator : True
tx-DiversityIndicator : False
[4 ] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 142
readSFN-Indicator : True
tx-DiversityIndicator : False
[5 ] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 356
readSFN-Indicator : True
tx-DiversityIndicator : False
[6 ] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 354
readSFN-Indicator : True
tx-DiversityIndicator : False
[7 ] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 154
readSFN-Indicator : True
tx-DiversityIndicator : False
[8 ] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 132
readSFN-Indicator : True
tx-DiversityIndicator : False
[9 ] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 390
readSFN-Indicator : True
tx-DiversityIndicator : False
[10] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 407
readSFN-Indicator : True
tx-DiversityIndicator : False
[11] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 405
readSFN-Indicator : True
tx-DiversityIndicator : False
[12] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 365
readSFN-Indicator : True
tx-DiversityIndicator : False
[13] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 364
readSFN-Indicator : True
tx-DiversityIndicator : False
[14] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 363
readSFN-Indicator : True
tx-DiversityIndicator : False
[15] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 40
readSFN-Indicator : True
tx-DiversityIndicator : False
[16] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 13
readSFN-Indicator : True
tx-DiversityIndicator : False
[17] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 12
readSFN-Indicator : True
tx-DiversityIndicator : False
[18] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 89
readSFN-Indicator : True
tx-DiversityIndicator : False
[19] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 88
readSFN-Indicator : True
tx-DiversityIndicator : False
[20] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 116
readSFN-Indicator : True
tx-DiversityIndicator : False
[21] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 115
readSFN-Indicator : True
tx-DiversityIndicator : False
[22] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 114
readSFN-Indicator : True
tx-DiversityIndicator : False
[23] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 61
readSFN-Indicator : True
tx-DiversityIndicator : False
[24] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 392
readSFN-Indicator : True
tx-DiversityIndicator : False
[25] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 391
readSFN-Indicator : True
tx-DiversityIndicator : False
[26] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 268
readSFN-Indicator : True
tx-DiversityIndicator : False
[27] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 139
readSFN-Indicator : True
tx-DiversityIndicator : False
[28] :
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 138
readSFN-Indicator : True
tx-DiversityIndicator : False
intraFreqReportingQuantityForRACH
sfn-SFN-OTD-Type : noReport
modeSpecificInfo : fdd
intraFreqRepQuantityRACH-FDD : cpich-EcN0
maxReportedCellsOnRACH : currentCell
interFreqMeasurementSysInfo
interFreqCellInfoSI-List
newInterFreqCellList
NewInterFreqCellSI-List-ECN0 :
[0 ] :
frequencyInfo
modeSpecificInfo : fdd
fdd
uarfcn-UL : 9612
uarfcn-DL : 10562
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 406
readSFN-Indicator : False
tx-DiversityIndicator : False
[1 ] :
frequencyInfo
modeSpecificInfo : fdd
fdd
uarfcn-UL : 9637
uarfcn-DL : 10587
cellInfo
modeSpecificInfo : fdd
primaryCPICH-Info
primaryScramblingCode : 355
readSFN-Indicator : False
tx-DiversityIndicator : False
interRATMeasurementSysInfo
interRATCellInfoList
removedInterRATCellList
RemovedInterRATCellList : removeAllInterRATCells
newInterRATCellList
NewInterRATCellList-B :
[0 ] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 1
bcc : 2
frequency-band : dcs1800BandUsed
bcch-ARFCN : 668
[1 ] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 7
bcc : 0
frequency-band : dcs1800BandUsed
bcch-ARFCN : 814
[2 ] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 6
bcc : 3
frequency-band : dcs1800BandUsed
bcch-ARFCN : 667
[3 ] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 7
bcc : 3
frequency-band : dcs1800BandUsed
bcch-ARFCN : 661
[4 ] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 3
bcc : 2
frequency-band : dcs1800BandUsed
bcch-ARFCN : 811
[5 ] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 0
bcc : 3
frequency-band : dcs1800BandUsed
bcch-ARFCN : 810
[6 ] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 6
bcc : 7
frequency-band : dcs1800BandUsed
bcch-ARFCN : 664
[7 ] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 5
bcc : 6
frequency-band : dcs1800BandUsed
bcch-ARFCN : 675
[8 ] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 1
bcc : 4
frequency-band : dcs1800BandUsed
bcch-ARFCN : 665
[9 ] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 5
bcc : 4
frequency-band : dcs1800BandUsed
bcch-ARFCN : 667
[10] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 0
bcc : 3
frequency-band : dcs1800BandUsed
bcch-ARFCN : 996
[11] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 0
bcc : 5
frequency-band : dcs1800BandUsed
bcch-ARFCN : 992
[12] :
technologySpecificInfo : gsm
interRATCellIndividualOffset : 0
bsic
ncc : 5
bcc : 5
frequency-band : dcs1800BandUsed
bcch-ARFCN : 663
System Information Message (SIB 19)
Time : 01:22:52.555
Vendor Header
UARFCN DL : 10712
Primary Scrambling Code : 115
utra-PriorityInfoList
priority : 5
s-PrioritySearch1 : 5
s-PrioritySearch2 : 7
threshServingLow : 5
eutra-FrequencyAndPriorityInfoList
EUTRA-FrequencyAndPriorityInfoList :
[0 ] :
earfcn : 1634
measurementBandwidth : mbw25
priority : 7
qRxLevMinEUTRA : -58
threshXhigh : 5
threshXlow : 7
eutraDetection : False
sysInfoType19-v920ext
utra-PriorityInfoList-v920ext
threshServingLow2 : 6
eutra-FrequencyAndPriorityInfoList-v920ext
EUTRA-FrequencyAndPriorityInfoList-v920ext :
[0 ] :
qqualMinEUTRA : -18
SIB(System Information Block) and their Details
SIB1 : NAS Information. UE Timers and counters to be used in RRC Idle & Connected State
SIB5: Configuration parameters of common physical channels in a cell. PCH and PICH Info (CPCH)
SIB7: Contains fast changing UL interface params and dynamic. As this is changes often so controlled by timer
SIB8: Used in FDD . Static CPCH info of cell. Used in Connected mode only
SIB9: CPCH info. As it changed often, controlled by timers connected mode only.
SIB13: For ANSI-41 . It also has 4 associated SIBS 13.1 to 13.4. Reference to subblocks. Used when System is AN
SIB14: Parameters for common and dedicated physicall DPCH UL outer loop power control info for TDD
SIB15: Assistance info for UE positioning. Used to reduce signalling by position. 15.1 to 15.5 sub sibs.
SIB16: Predefined channel conf. used while hand over. Radio Bearer transport channel, physical channel params to
SIB18: PLMN Identities of neighbouring cells. Used in Shared Access N/w with the cell reselection process
tored by UE in idle/connected mode. Several occurances but UE doesnot bother.
Cause No. 1: Unallocated (unassigned number). This cause indicates that the destination requested by the calling user cannot b
Cause No. 2: no route to specified transit network. This cause indicates that the equipment sending this cause has received a re
This cause is supported on a network-dependent basis.
Cause No. 3: no route to destination. This cause indicates that the called user cannot be reached because the network through
This cause is supported on a network-dependent basis.
Cause No. 6: channel unacceptable. This cause indicates that the channel used in this call is not acceptable to the sending entit
Cause No.7: call awarded and being delivered in an established channel. This cause indicates that the user is receiving an incom
Cause No. 16: normal call clearing. This cause indicates that the call is being cleared because one of the users involved in the c
Cause No. 17: user busy. This cause is used when the called user has indicated the inability to accept another call.
It is noted that the user equipment is compatible with call.
Cause No. 18: no user responding. This cause is used when a user does not respond to a call establishment message with eithe
Cause No. 19: no answer from user (user alerted). This cause is used when a user has provided an alerting indication but has n
This cause is not necessarily generated by Q.931 procedures but may be generated by internal network timers.
Cause No. 21: call rejected. This cause indicates that the equipment sending this cause does not wish to accept this call, althou
Cause No. 22: number changed. This cause is returned to a calling user when the called party number indicated by the calling u
Cause No. 26: non-selected user clearing. This cause indicates that the specified user has not been awarded the incoming call.
Cause No. 27: destination out of order. This cause indicates that the destination indicated by the user cannot be reached becau
Cause No. 28: invalid number format (address incomplete). This cause indicates that the called user cannot be reached because
Cause No. 29: facility rejected. This cause is returned when a facility requested by the user cannot be provided by the network.
Cause No. 30: response to STATUS INQUIRY. This cause is included in the STATUS message when the reason for generated th
Cause No. 31: normal, unspecified. This cause is used to report a normal even only when no other cause in the normal class ap
Cause No. 34: no circuit/channel available. This cause indicates that there is no appropriate circuit/channel presently available t
Cause No. 38: network out of order. This cause indicates that the network is not functioning correctly and that/ the condition is
Cause No. 41: temporary failure. This cause indicates that the network is not functioning correctly and that the condition is not
Cause No. 42: switching equipment congestion. This cause indicates that the switching equipment generating this cause is expe
Cause No. 43: access information discarded. This cause indicates that the network could not deliver access information to the re
It is noted that the particular type of access information discarded is optionally included in the diagnostic.
Cause No. 44: requested circuit/channel not available. This cause is returned when the circuit or channel indicated by the reque
Cause No. 47: resource unavailable, unspecified. This cause is used to report a resource unavailable event only when no other
Cause No 49: Quality of Service not available. This cause is used to report that the requested Quality of Service, as defined in R
Cause No. 50: requested facility not subscribed. This cause indicates that the requested supplementary service could not be pro
Cause No 57: bearer capability not authorized. This cause indicates that the user has requested a bearer capability implemented
Cause No. 58: bearer capability not presently available. This cause indicates that the user has requested a bearer capability imp
Cause No 63: service or option not available, unspecified. This cause is used to report a service or option not available event on
Cause No. 65: bearer capability not implemented. This cause indicates that the equipment sending this cause does not support
Cause No. 66: channel type not implemented. This cause indicates that the equipment sending this cause does not support the
Cause No. 69: requested facility not implemented. This cause indicates that the equipment sending this cause does not support
Cause No. 70: only restricted digital information bearer capability is available. This cause indicates that a device has requested a
Cause No. 79: service or option not implemented, unspecified. This cause is used to report a service or option not implemented
Cause No. 81: invalid call reference value. This cause indicates that the equipment sending this cause has received a message w
Cause No. 82: identified channel does not exist. This cause indicates that the equipment sending this cause has received a requ
Cause No. 83: a suspended call exists, but this call identify does not. This cause indicates that a call resume has been attempte
Cause No. 84: call identity in use. This cause indicates that the network has received a call suspend request. The call suspend r
Cause No. 85: no call suspended. This call indicates that the network has received a call resume request. The call resume reque
Cause No. 86: call having the requested call identity has been cleared. This cause indicates that the network has received a call
Cause No. 88: incompatible destination. This cause indicates that the equipment sending this cause has received a request to e
Cause No. 91: invalid transit network selection. This cause indicates that a transit network identification of an incorrect format a
Cause No. 95: invalid message, unspecified. This cause is used to report an invalid message event only when no other cause in
Cause No. 96: mandatory information element is missing. This cause indicates that the equipment sending this cause has receiv
Cause No. 97: message type non-existent or not implemented. This cause indicates that the equipment sending this cause has
Cause No. 98: message not compatible with call state or message type non-existent or not implemented. This cause indicates th
Cause No. 99: information element non-existent or not implemented. This cause indicates that the equipment sending this caus
Cause No. 100: invalid information element contents. This cause indicates that the equipment sending this cause has received a
Cause No 101: message not compatible with call state. This cause indicates that a message has been received that is incompati
Cause No. 102: recovery on timer expiry. This cause indicates that a procedure has been initiated by the expiry of a timer in as
Cause No. 111: protocol error, unspecified. This cause is used to report a protocol error event only when no other cause in the
Cause No. 127: interworking, unspecified. This cause indicates there has been interworking with a network that does not provid
he transit network does not exist or because that particular network, while it does exist, does not serve the equipment that is sending this ca
r: e.g., a physical layer or data link layer failure at the remote user, user equipment off-line, etc.
ser equipment or the network attempts to use channels 13 through 23, this cause is generated.
quipment sending the cause. However, the information element is not required to be present in the message in order for the equipment se
The UE reads the System Information that is broadcast on BCCH. The information is not read continuously. It is only read if th
The Mobile user decides to initiate a voice call. The first message the UE will send on CCCH is RRC Connection Request. This
The SRNC sends this message to Node B. It will pass the Cell Id, TFS, TFCS, frequency, UL Scrambling code, etc to Node B.
Node B allocates the resources and starts PHY Reception. While transmitting the response it includes the Transport layer addres
The AAL2 binding identity (Iub Data Transport Bearer Id) is passed to ALCAP protocol in Node B. The Iub Data Transport bea
The Node B and SRNC establishes synchronisation for the Iub Data Transport bearer by means of exchange of the appropriate D
RRC Connection Setup message is sent on CCCH with the parameters required to establish DCH. Also the state indicator will b
Once the UE establishes Radio Link, Node B will send RL Restore indication to the SRNC.
RRC Connection Setup complete will be sent on DCCH. Integrity and Ciphering related paarmeters and UE capability informat
12: RRC: Initial Direct Transfer [CM Service Request]
First NAS message is now sent by the UE. It indicates that a UE orginated Voice call is required. The UE identity (TMSI) will a
The NAS message will be forwarded to appropriate CN Domain (CS Domain in this case). Along with the CM service request,
MSC/VLR needs to perform authentication to make sure that the UE is genuine. For this reason it will challenge the UE with a
UE computes the response (RES) and sends it back in the NAS message
SRNC relays the response to the MSC/VLR. The MSC/VLR will compare the response RES with the expected response XRES
MSC/VLR sends the Security Mode Command to start Ciphering and Integrity Protection. Ciphering is optional while Integrity
RRC Forwards the Security Mode command received from MSC/VLR to the UE.
The UE configures the Ciphering and Integity Protection and responds back to the network. The response message is Integrity P
The network may decide to re-allocate the TMSI to the UE. It sends a DT message which includes the NAS TMSI Reallocation
The UE takes the new TMSI and responds with the Complete message
The UE now sends the 'Setup' message in UL Direct Transfer message. This will include all the required parameters for setting
The MSC/VLR sends Call Proceeding to the UE indicating that it is now starting with the RAB establishment procedure.
The CN initiates establishment of the Radio Access Bearer using the RAB Assignment Request message. This message include
SRNC initiates the set-up of Iu Data Transport bearer using ALCAP protocol. The request contains the AAL2 Binding Identity t
SRNC requests Node B to prepare establishment of DCH to carry the RAB. It passes the TFS, TFCS and Power Control Inform
SRNC initiates setup of Iub Data Transport Bearer using ALCAP protocol. The request contains the AAL2 Binding Identity to b
The Node B and SRNC establish synchronism for the Iub Data Transport Bearer by means of exchange of the appropriate DCH
Finally the SRNC instructs the Node B of the CFN at which the new configuration will come into effect.
SRNC sends the RB Setup message to add the new DCH's. The message will be received using the old configuration.
After the activation time the UE will respond with complete message using the new configuration.
MSC/VLR sends the Initial Address Message to the PSTN. The message tells the PSTN to reserve an idle trunk circuit from ori
The ACM message is sent to indicate that the remote end of the trunk circuit has been reserved.
The Alert message is sent to the SRNC. This message contains the ACM received from the PSTN.
46: RRC: Direct Transfer [Alert]
The Alert message is forwarded to the UE. The Alert message will inditiate the ringing tone on the handset.
When the person that is being called picks up his phone, an Answer message is sent to the MSC/VLR.
The MSC/VLR sends the Connect message to the SRNC via Direct Transfer message. The Connect message indictaes that the E
The UE confirms the reception of the Connect message using the Connect Acknowledge and sending it via Direct Transfer
The Network forwards the Connect Acknowledge to the MSC/VLR. The call has now been successfully established.
rers it is started in RLC.