Thanks Thanks:  14
Showing results 1 to 4 of 4

Thread: GPEH 101: presentation from KL, 2008

  1. #1
    Member Reputation: 416
    Join Date
    2010-06-16
    Posts
    321


    Default GPEH 101: presentation from KL, 2008

    Operator presentation on some stuff done by using GPEH.
    Presented 3 years ago in KL on EUGAP meeting, intended to motivate
    audience to start using GPEH.

    BR
    s52d
    Attached Files Attached Files

  2. # ADS
    Circuit advertisement
    Join Date
    Always
    Posts
    Many
     

  3. #2
    Junior Member Reputation: 14
    Join Date
    2011-08-10
    Posts
    52


    Default Re: GPEH 101: presentation from KL, 2008

    thank for sharing, this is good Doc for me

  4. Thanks Stantheman thanked for this post
  5. #3
    Member Reputation: 29
    Join Date
    2010-05-16
    Posts
    310


    Default Re: GPEH 101: presentation from KL, 2008

    Quote Originally Posted by s52d View Post
    Operator presentation on some stuff done by using GPEH.
    Presented 3 years ago in KL on EUGAP meeting, intended to motivate
    audience to start using GPEH.

    BR
    s52d

    can you please share more doc and the learning doc for GPEH

  6. #4
    Member Reputation: 416
    Join Date
    2010-06-16
    Posts
    321


    Default Re: GPEH 101: presentation from KL, 2008

    Quote Originally Posted by zee86 View Post
    can you please share more doc and the learning doc for GPEH
    Hi!

    With some experience with GPEH I dare to say:
    1. Alex is extremely good description for GPEH. It is all you need to roll your own parser,
    SW complexity is low, so anyone (with some experience) can do it. It is more important to understand data as
    it is to be best programmer in the world! So, many planners just did it.
    (you can firn Alex files somewhere on WFA, but you probably have access at homw as well)

    2. decode binary messages. Parsing BER ASN.1 is not trivial, but you can use wireshark.
    (Binary from parser, text2pcap, tshark)

    3. use OSS parser instead. It is slow, and it has very limited capacity.
    But, you can get fammiliar with data and do some investigations.


    then... Start with drop call analyzis to get feeling for data, proceed with more complex investigation.
    For missing neighbors you do not need binary part, it is needed only for some complex reports,
    for example distance is extracted from NBAP messages etc.

    4. Big suprice: LTE GPEH (CTR) is even simpler to parse/process. In my view, LTE CTR is biggest
    E/// advantage over competitors.

    BR
    s52d

  7. Thanks nicodrey thanked for this post

Tags for this Thread

Bookmarks

Bookmarks

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •