Wireshark-users: Re: [Wireshark-users] Support for UTRAN Iupc interface PositioningCalculation Ap
From: "Joyce Jin" <joyce.jin@xxxxxxxxxxxx>
Date: Wed, 13 Feb 2008 11:28:38 -0600
Hi Anders,
Thanks for the quick reply. PCAP signalling is
specified in 3GPP TS 25.453. Basically what we want is the analyzer be
able to decode the following
messages:
PostionActivationRequestPosition Initiation Response (SAS -> RNC)
Position Initiation Failure (SAS -> RNC)
Position Activation Request (SAS -> RNC)
Position Activation Response (RNC -> SAS)
Position Activation Failure (RNC -> SAS)Abort (RNC -> SAS)
Error Indication (RNC< -> SAS)
I have an sample trace and maybe you can take a
look. Thanks.
BR,
/Joyce
From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of Anders Broman
Sent: Wednesday, February 13, 2008 11:15 AM
To: Community support list for Wireshark
Subject: RE: [Wireshark-users] Support for UTRAN Iupc interface PositioningCalculation Application
Hi,
It does not, but if you have a sample trace
it may not be to difficult to implement depending
on the protocol layers.
regards
Anders
From: wireshark-users-bounces@xxxxxxxxxxxxx on behalf of Joyce Jin
Sent: Wed 2/13/2008 6:10 PM
To: wireshark-users@xxxxxxxxxxxxx
Subject: [Wireshark-users] Support for UTRAN Iupc interface PositioningCalculation Application
Hi,
I want to know if
Wireshark Ethereal can decode UTRAN Iupc interface Positioning Calculation
Application (PCAP) protocol. If it does, from which Wireshark version it
starts to support the protocol? Thanks.
//Joyce
value PCAP-PDU ::= initiatingMessage : { procedureCode 9, criticality reject, transactionID longTID : 6, value PositionInitiationRequest : { protocolIEs { { id 28, criticality reject, value RequestType : { event direct, reportArea geographical-area, horizontalaccuracyCode 0 } }, { id 29, criticality reject, value UE-PositioningCapability : { standAloneLocationMethodsSupported TRUE, ueBasedOTDOASupported FALSE, networkAssistedGPSSupport both, supportGPSTimingOfCellFrame TRUE, supportForIPDL FALSE, supportForRxTxTimeDiff FALSE, supportForUEAGPSinCellPCH FALSE, supportForSFNSFNTimeDiff FALSE } }, { id 30, criticality reject, value UC-ID : { rNC-ID 301, c-ID 1001 } }, { id 25, criticality ignore, value VerticalAccuracyCode : 1 }, { id 31, criticality ignore, value ResponseTime : low-delay }, { id 32, criticality ignore, value PositioningPriority : normal-priority }, { id 33, criticality ignore, value ClientType : value-added-services } } } } ====================================================================================== value PCAP-PDU ::= initiatingMessage : { procedureCode 10, criticality reject, transactionID longTID : 7, value PositionActivationRequest : { protocolIEs { { id 34, criticality reject, value PositioningMethod : { additionalMethodType ue-based-preferred-but-ue-assisted-allowed, selectedPositionMethod cell-id } }, { id 38, criticality ignore, value Positioning-ResponseTime : ms500 } } } } ========================================================================= value PCAP-PDU ::= successfulOutcome : { procedureCode 10, criticality reject, transactionID longTID : 7, value PositionActivationResponse : { protocolIEs { { id 20, criticality reject, value CellId-MeasuredResultsSets : { { { uC-ID { rNC-ID 301, c-ID 1001 }, uTRANAccessPointPositionAltitude { geographicalCoordinates { latitudeSign north, latitude 0, longitude 0 } }, iE-Extensions { { id 64, criticality ignore, extensionValue RoundTripTimeInfoWithType1 : { ue-RxTxTimeDifferenceType1 1162, roundTripTime 15053 } } } } } } } } } } =========================================================================== value PCAP-PDU ::= successfulOutcome : { procedureCode 9, criticality reject, transactionID longTID : 6, value PositionInitiationResponse : { protocolIEs { { id 18, criticality reject, value UE-PositionEstimate : pointWithAltitudeAndUncertaintyEllipsoid : { geographicalCoordinates { latitudeSign north, latitude 5537364, longitude 836535 }, altitudeAndDirection { directionOfAltitude height, altitude 0 }, uncertaintyEllipse { uncertaintySemi-major 18, uncertaintySemi-minor 18, orientationOfMajorAxis 0 }, uncertaintyAltitude 8, confidence 67 } }, { id 40, criticality ignore, value PositionData : { positioningDataDiscriminator '0000'B, positioningDataSet { '5B'H } } }, { id 23, criticality ignore, value AccuracyFulfilmentIndicator : requested-Accuracy-Fulfilled } } } } =============================================================================== value PCAP-PDU ::= initiatingMessage : { procedureCode 11, criticality ignore, transactionID longTID : 319, value Abort : { protocolIEs { { id 1, criticality ignore, value Cause : radioNetwork : ue-positioning-error-Undefined-Error } } } } ================================================================================== value PCAP-PDU ::= unsuccessfulOutcome : { procedureCode 10, criticality reject, transactionID longTID : 122, value PositionActivationFailure : { protocolIEs { { id 1, criticality ignore, value Cause : radioNetwork : information-temporarily-not-available } } } }
- Follow-Ups:
- References:
- Prev by Date: Re: [Wireshark-users] Support for UTRAN Iupc interface PositioningCalculation Application
- Next by Date: Re: [Wireshark-users] Support for UTRAN Iupc interfacePositioningCalculation Application
- Previous by thread: Re: [Wireshark-users] Support for UTRAN Iupc interface PositioningCalculation Application
- Next by thread: Re: [Wireshark-users] Support for UTRAN Iupc interfacePositioningCalculation Application
- Index(es):