Unisoc Latam: Logel User Guide

UNISOC LATAM
Logel User Guide by Edgar Cortes
1 July 2021
Introduction- Guide Logel
This document is aimed to apply for user guide of UNISOC Logging Tool
(ArmLogel), including log catching and log analysis.
.2
Agenda
1. Internal Log
How to take an internal Log Using SD card
Ylog / A10
Ylog / A11
- Settings options
- Extra steps
- How to save Logs
How to open a log taken by SD card

- Using ArmLogel UNISOC tool
2. PC Log
***Precondition: Driver Install
- How to take a log with PC
- How to save the log taken by PC
- How to open a log taken by PC
.3
Agenda
3. ArmLogel Measurements windows

L3 flow messages Analysis
- Log Analyzes of some typical scenarios (Registration & Ciphering)
- NITZ
- Data Service
- VoLTE / VoWiFi
- Call Services
- AMR ( Adaptative Multi-Rate )
- Short Message Service ( SMS )
- Multimedia Messaging Service ( MMS)
- Some Messages in Mobility
- Fast Dormancy
- Enhanced Cell FACH
- CPC
- VAMOS
.4
Logs according to OSI Model
.5
How to take an internal Log Using SD card
.6
Ylog / A10
.7
Ylog
⚫ Ylog tool is used from Android 8.0 version. That means Ylog
interface in Android 8.0, 9.0 and 10.0 Ylog interface is the same.
⚫ The engineering code to access Ylog tool is the same for all
models, except those which ODM programs a custom code.
Note: UNISOC general YLOG/Engineer mode code *#*#83781#*#*.

Log Capture –by Ylog (UE)
➢ Ylog is used for catching AP, Connectivity,

modem, poweron and sensorhub logs
➢ Step by step:
SD Card must be inserted into the phone
1.- Dial “*#*#83781#*#*”
2.- Slide to 2nd sheet “DEBUG&LOG”
3.- Choose “Ylog”
.9
Log Capture –by Ylog UI (UE)
➢ Step by step:
▪ When the Round button is blue, that's means Ylogs
logs are running.
– Go to Settings for more options.
. 10
Ylog Setting Options
➢To have a complete log must select Custom scene ->

- Custom Scene > Add Log Scene (click on Accept) ->
- Enable ARM Pcm Log and DSP Pcm Log options ->
- Press Commit
1. Once you press commit -> set airplane mode as ON

2. Return to the main page Ylog and choose the trashcan please push accept
3. Once you clear the Ylog restart the phone
“After the reboot is completed, the UE is already set to take R&D suggested logs”
1. 2. 3.
These steps need to

be realized to
guaranteed the correct
mode to saved Ylog.
Clear the Ylog

pushing in the
trashcan symbol
Catching Ylog info
1. The logs will be saved in the SD log path showed

(External storage/SD card).
Note: You can also go to SD Card and look for

Ylog file and rename folder to catch log info without stopping log.
Ylog / A11
. 14
Ylog
⚫Ylog on A11 has change a little bit on the way to catch the internal logs
➢ There are just two more test steps, before to start taking the logs
Note: UNISOC general YLOG/Engineer mode code *#*#83781#*#*

*#*#TEST1#*#*

➢ Step by step:
1.- Dial “*#*#83781#*#*” (*#*#TEST1#*#*)
. 16
➢ Step by step:
▪ When the Round button is blue, that's means Ylogs
logs are running.
. 17

- Custom Scene > Add Log Scene (click on Accept) ->
- Enable ARM Pcm Log and DSP Pcm Log options ->
- Press Commit
Ylog Setting Options – Extra steps
➢Extra steps ONLY for A11
1.-Go to settings > Debug Settings & Tools > Log auto copy to SD card settings > Press START AUTO COPY
2.-After to press “Start Auto Copy” the phone is ready to catch the log
1. Once you press commit -> set airplane mode as ON

2. Return to the main page Ylog and choose the trashcan please push accept
1. 2. 3.
These steps need to be realized

to guaranteed the correct mode to
saved Ylog.
Clear the Ylog

pushing in the
trashcan symbol
Ylog Setting Options To save logs

3.-After to perform the test which wants to save the logs
Go to Ylog Menu > Settings > Debug Settings & Tools > Log auto copy to SD card settings > Press STOP AUTO COPY

4.-After to press “STOP AUTO COPY”
Go to Ylog Menu > Settings > Debug Settings & Tools > Press Log copied to SD card(disposable)
5.-Logs is already saved on SD Card Files
Catching Ylog info
1.- The logs will be saved in the SD log path showed

Just rename Ylog folder to catch log info without stopping log.
Ylog / A12
. 24
Ylog
⚫ The engineering code to access Ylog tool is the same for all
models, except those which ODM programs a custom code.
Note: UNISOC general YLOG/Engineer mode code *#*#83781#*#*.

➢ Step by step:
1.- Dial “*#*#83781#*#*”
. 26
Log Storage Location –by Ylog UI (UE)
➢ Step by step:
▪ Go to Setting Option>> Select Log Storage Location
▪ >>Select External (To Save the Logs In SD Card).
. 27
➢ Step by step:
▪ When the Round button set in stop, that's means Ylogs
logs are running.
. 28

- Custom > Select All -> Press Modem Log
- Enable DSP Pcm Log options ->
- Return to Main Page Ylog
1. Choose Setting Option
1. 2.
Set as Big as
Posible
1. Enable Sysdump
1. 2.
1. Once you return to main page Ylog -> set airplane mode as ON
2. Choose the option “clear” please push accept
1. 2. 3.
These steps need to

be realized to
guaranteed the correct
mode to saved Ylog.
Catching Ylog info
1. The logs will be saved in the SD log path showed

Note: You can also go to SD Card and look for

Ylog file and rename folder to catch log info without stopping log.
How to open a log taken by SD card
. 34
Log Capture – ArmLogel tool
1. Open ArmLogel UNISOC tool
. 35
Log Capture – Log catched by SD Card
2. Press “File”option
3. Then press “Replay” on File options
4. Log location go to “modem_log”>”cp_5mode” or “modem” folder and
select the file with “LOG”extension pressing double click on it
. 36
Log Capture – Log catched by SD Card
4. After to press “OK” the log will run automatically.
. 37
How to take a log with PC
. 38
Environment Setup – Debugging Mode
➢ Ensure that the device has already enable the Developer option.
• Go to settings
• Go to the last option “About phone”
• Go to the last option “Build number”
• Click 5-6 times in Build number to enable “Developer option”

mode
• Go back to settings and now you can see the option “Developer
option”
. 39
Environment Setup
➢ Ensure that the device has already enable the Developer option.
• Go to Developer options.
• Ensure that Developer option is enabled and also USB debugging.
• Now that developer option is enabled,

connect the device in PC to continue
with the drivers installing.
. 40
Environment Setup - Driver Install
➢ For 3G or 2G Product (6531/7715/7731):
Plug in the USB cable, 4 unknown ports named as “UNISOC”
. 41
➢ For LTE Product (9820/9832/9850):
Plug in the USB cable, 8 unknown ports named as “UNISOC”
. 42
➢ Update driver: DriverCoding
. 43
➢ Successfully installed the 4 ports for 2G & 3G products
. 44
➢ For LTE Products:
Successfully installed All ports
. 45
Log Capture – ArmLogel tool
1. Open ArmLogel UNISOC tool
. 46
Log Capture - ArmLogel
➢ ArmLogel.exe - Step by step
. 47
Log Capture - ArmLogel
➢ L3 flow messages
. 48
How to save the log taken by PC
. 49
Saving Logs - ArmLogel
➢ ArmLogel.exe - Save logs
➢ Make sure .logel file is contained in the log path
. 50
How to open a log taken by PC
. 51
Log Capture – Log catched by PC
1. Press “File”option
2. Then press “Replay” on File options
3. Select the file with “.Logel” extension and press double click on it
. 52
Log Capture – Log catched by PC
4. The next window will appear, press OK without any settings modification.
5. After to press “OK” the log will run automatically.
. 53
ArmLogel Measurements windows
. 54
Log Analyses – Cell Measurements Windows
. 55
Log Analyses – Measurement Windows
➢ LTE
EARFCN, PCID, RSRP, RSRQ
➢ WCDMA
UARFCN, PSC, RSCP, EcNo, Srxlev, Squal, HCS, RRC State
➢ GSM
ARFCN, BSIC, RSSI
. 56
Log Analyses - Measurements
➢ LTE Cell Measurements
. 57
➢ 3G Cell Measurements
. 58
➢ 2G Cell Measurements
. 59
L3 flow messages Analysis
. 60
Log Analyzes of some typical scenarios
Registration & Ciphering
. 61
Log Analyses – Registration & Ciphering 2G
➢Attach_request
. 62
➢ For more information from L3 information, press right click on
“[LOCAL] ll_unitdata_req_struct”and select “Parse By WireShark”
. 63
➢ Will find more L3 Info on WireShark
. 64
➢Attach_complete
. 65
➢ rr_peer_sysinfo_type2quarter
▪ On this message can be found all the information network on 2G
. 66
➢Attach_request
. 67
➢ For more information from L3 information, press right click on
“[LOCAL] gmmas_sig_est_req_struct”and select “Parse By WireShark”
. 68
➢ Will find more L3 Info on WireShark
. 69
Log Analyses – Registration 3G
➢ Will find more L3 Info on WireShark Registro &

➢Attach_accept
. 71
➢Attach_complete
. 72
➢Attach_request
. 73
➢Attach_request on WireShark
. 74
➢Attach_accept
. 75
➢Attach_accept on WireShark
. 76
➢Attach_complete
. 77
➢Attach_complete on WireShark
. 78
NITZ
. 79
Log Analyses - NITZ
➢ NITZ
▪ Purpose: Purpose: After the end of
Registration Procedure, the Network may
send GMM INFORMATION to UE to
synchronize the time with the Network.
▪ Important: From GMM INFORMATION
Message, the Network will tell the UE its
full/short network name, time and time
zone, DST information. The UE shall use this
information and set the time automatically.
. 80
Log Analyses - NITZ
. 81
Data Services
. 82
Log Analyses – Data Services LTE
➢On LTE the APN Address will found on activate_default_eps_bearer_conext_request
. 83
Log Analyses – Data Services 3G
➢IPv4v6
. 84
➢APN connection on Active PDP Context Request
. 85
➢APN connection on Active PDP Context accept
. 86
➢ Active PDP reject
▪ Purpose: ACTIVATE PDP CONTEXT REJECT message is sent by the Network to UE to
reject activation of a PDP context.
▪ Important: According to 3GPP TS24.008 9.5.3 & 10.5.6.6, we can find the cause value
in strut of ACTIVATE PDP CONTEXT REJECT message.
. 87
. 88
Log Analyses - Data Services in 2G
➢ How to check the time slot assigned to UL/DL on 2G
After to some connection that requires an active_pdp_context_req (Browsing,

Wap,MMS, FTP download) go to Armlogel tool and find
PH_MAC_TBF_CONNECT_REQ message within MESSAGE window.
. 89
➢ UL/DL timeslot assigned: PH_MAC_TBF_CONNECT_REQ
. 90
➢ How to check Modulation Coding Scheme using in UL

Wap,MMS, FTP download) go to Armlogel tool and find RLC_MAC_DATA_REQ
message within MESSAGE window.
. 91
➢ Uplink Modulation Coding Scheme
. 92
➢ How to check Modulation Coding Scheme using in DL

Wap,MMS, FTP download) go to Armlogel tool and find MAC_RLC_DATA_IND
message within MESSAGE window.
. 93
➢ Downlink Modulation Coding Scheme
. 94
VoLTE / VoWIFI
. 95
IMS - IP Multimedia Subsystem
• 3GPP defined IMS in 1999
• IMS as the framework for delivery of multimedia services was standardized in 3GPP rel.5 for
delivery of “Internet” services on GPRS. This was updated and extended to CDMA and WLAN.
• In 2009 a group of over 40 organizations, operators, vendors etc. came together to form One
Voice, whose aim was essentially to decide or drive the method of voice delivery on LTE through
IMS.
• GSMA finally adopted VoLTE in 2010, and so did many of the industry big Companies
• The first use of IMS through the Verizon LTE network in the USA accelerated the use of IMS
development for mobile devices.
Support for Voice with LTE
2G/3G – Circuit Switched calls have an allocated resource even during times of
inactivity - even when nothing is being said.
• Inefficient use of available bandwidth
• Access times between requesting resource and being able to talk were too slow to enable a
reaction based allocation plus reduced flexibility for resource allocation
• An LTE UE will generally only be provided resources when it is necessary –

• even for voice
❑ Allows efficient use of network resources. If we are saying nothing we will require no network resources.
❑ Places stress on the network to ensure suitable access timing and quality of service (QoS).
• LTE transportation is fully IP – no circuit switched services

Voice with LTE: What is the goal and how to get there
The long term solution for voice is to use VoIP and an IMS based core network,
there are already many networks fully operational.
• For networks which do not support IMS or have incomplete coverage, several fall back
technologies are required:
o CSFB (Circuit Switched Fall Back) - single radio approach
o SVLTE or Dual Standby approach (Simultaneous Voice and Data LTE) - dual radio
approach
o SRVCC (Single Radio Voice Call Continuity) – Voice on LTE with CS backup
• CSFB, SVLTE and SRVCC all involve some level of I-RAT behavior
IMS Architecture
IMS ：IP Multimedia Subsystem is an architectural framework for delivering IP multimedia

services
IP = Transmission based on IP
Session control based on IP
Service implement based on IP
Multimedia = Voice, Video, Pictures, Text etc, and A combination of multimedia
Subsystem = The system relies on the development of existing network

technology and network equipment. This is done by having a
horizontal control layer that isolates the access network from the
service layer.
VoLTE Architecture(IMS)
DiameterDh
Diameter
Ro,Rf
SLF HSS AS
Sh
Diameter Diameter ISC
Dx Cx Cx
Gm Mw Mw Mr
Ro,Rf
P- I- S- MRFC
UE
CSCF Rf CSCFRf Mi CSCF
Ro,Rf Mp H.248
Compression
MRFP
Mg
GGSNVisited
Home Mj
DomainDomain BGCF MGCF SGW
Rf SIP Rf SIP-ISUP
H.248 Mn
MGW
HSS – Home Subscriber Server
▪ Central repository of Subscriber Data in the IMS Network
HSS
Core Mobility and ▪ Stores the IMS User Profiles
Home Subscription – User Identification
Server – Addressing information
– Service Provisioning Information
HSS – User Mobility Information (S-CSCF address)
– Charging Information
▪ Provides support for User Authentication
▪ Provides Subscriber Self Administration (SSA) support

CSCF – Call State Control Function
▪ Can be viewed as a SIP based Multimedia Session

Controller
CSCF
Call State
Control Function ▪ Includes 3 standard functions: P-CSCF, I-CSCF, S-CSCF
– P-CSCF (Proxy CSCF)
» Provides Signaling Compression
» QoS Support
» Integrity / Confidentiality Support (IMS AKA)
– I-CSCF (Interrogating CSCF)
» First contact point into the operator network
» Performs the S-CSCF Selection
– S-CSCF (Serving CSCF)
» User Authentication
» Charging
» Session/Service Control
LTE Layer2 Feature
IMS Protocols
From the UE’s point of view of the IMS subsystem, the critical protocols are the Session Initiation Protocol (SIP),
SigComp, Real-time Transport Protocol (RTP), RTP Control Protocol (RTCP) and IP Security (IPSec).
SIP (Session Initiation Protocol)

• SIP is a protocol used to create, modify and terminate multimedia sessions, essentially negotiating a media
session between two users. As a text-based client/server protocol, SIP is completely independent of underlying
protocols, (e.g. TCP/IP vs. UDP or IPv4 vs. IPv6). SIP is not a transport protocol and does not actually deliver
media, leaving that task to RTP/RTCP.
• One popular misconception is that SIP is specific to IMS. In fact, it is used in media services deployed via
Internet PDN as well. Skype™ and FaceTime® are two well-known examples of non-IMS-based SIP-based
applications.
SigComp (Signaling Compression)

• SIP is, like HTTP, a text-based protocol. While this can make for easy debugging it is inefficient when used in its
native text form. The compression mechanism used is SigComp, defined in RFC 332015. SigComp is not specific
to IMS and, contrary to popular belief, does not define a specific algorithm.
The Real-time Transport Protocol (RTP) and RTP Control Protocol (RTCP)
• IMS uses RTP as the media data transfer protocol. Both RTP and RTCP are defined in RFC 355017.
• In an IMS scenario, RTCP is used to provide statistical Quality-of-Service (QoS) information and aid in
synchronizing streams. While the protocol can be used to provide other rudimentary connection information, an
IMS subsystem uses SDP for this purpose.
SIP Request
SIP is a sequential (request/response) protocol similar to HTTP both in functionality and
format. Every SIP request begins with a starting line that includes the name of the method
(request type).
SIP Responses
SIP Responses are maintained in an IANA list called Session Initiation Protocol (SIP) Parameters. They always begin with a
Response Code, which falls into one of the following categories:
• Informational/Provisional (1xx):
Request received and being processed – Examples: 100 Trying, 180 Ringing
• Successful (2xx):
The action was successfully received, understood, and accepted – Examples: 200 OK, 202 Accepted
• Redirection (3xx):
Further action needs to be taken (typically by the sender) to complete the request – Examples: 301 Moved Permanently,
302 Moved Temporarily
• Client Failure (4xx):

The request contains bad syntax or cannot be fulfilled at the server – Examples: 401 Unauthorized, 403 Forbidden
• Server Failure (5xx):

The server failed to fulfill an apparently valid request – Examples: 500 Server Internal Error, 504 Server Time-out
• Global Failure (6xx):

The request cannot be fulfilled at any server – Examples: 600 Busy Everywhere, 604 Does Not Exist Anywhere
SIP Registration
SIP Registration
After Authentication, Security and UE Capability requests, the network accepts the Attach request and
activates the EPS bearer context. Once that has happened and the UE has also established a PDP context, a
typical IMS SIP client registration begins:
1. The IMS client attempts to register by sending a REGISTER request to the P-CSCF.
2. The P-CSCF forwards the REGISTER request to the I-CSCF.
3. The I-CSCF polls the HSS for data used to decide which S-CSCF should manage the REGISTER request. The I-CSCF then
makes that decision.
4. The I-CSCF forwards the REGISTER request to the appropriate S-CSCF.
5. The S-CSCF typically sends the P-CSCF a 401 (UNAUTHORIZED) response as well as a challenge string in the form of a
“number used once” or “nonce”.
6. The P-CSCF forwards the 401 – UNAUTHORIZED response to the UE.
7. Both the UE and the network have stored some Shared Secret Data (SSD), the UE in its ISIM or USIM and the network on
the HSS. The UE uses an algorithm per RFC 33101 (e.g. AKAv2-MD5) to hash the SSD and the nonce.”
8. The UE sends a REGISTER request to the P-CSCF. This time the request includes the result of the hashed nonce and SSD.
9. The P-CSCF forwards the new REGISTER request to the I-CSCF.
10. The I-CSCF forwards the new REGISTER request to the S-CSCF.
11. The S-CSCF polls the HSS (via the I-CSCF) for the SSD, hashes it against the nonce and determines whether the UE should
be allowed to register. Assuming the hashed values match, the S-CSCF sends 200 – OK response to the P-CSCF. At this
point an IPSec security association is established by the P-CSCF.
12. The P-CSCF forwards the 200 – OK response to the UE.
SIP Registration
SIP Registration
The UE initiates the registration sequence, attaches to the LTE network and activates the PDP context.
It discovers which P-CSCF to use, then makes a deliberately unauthenticated registration attempt. It
waits for the expected 401 response, extracts the nonce from the response and hashes it with the SSD
before including the result in a second REGISTER request.
• The P-CSCF, typically resident in the visited network, acts as the UE’s gateway into the UE’s home network. It
identifies the home IMS network, routes traffic to and from the home IMS network and establishes the IPSec security
association.
• The I-CSCF, typically resident in the home network, acts as the front-end of the home IMS. It interfaces with the P-
CSCF in the visited network and selects the S-CSCF (by querying the HSS).
• The S-CSCF, typically resident in the home network, handles the registration request from the I-CSCF, pulls
authentication vectors from the HSS and passes them to the P-CSCF (via the I-CSCF), and authenticates the user in the
second registration attempt.
Event Subscription
The UE will begin the transaction using the

SUBSCRIBE method. This method, defined in RFC
3265, is one of the many SIP extensions used in IMS.
This is basically a request to be notified (for a
specified period of time) of a change in resource
state. As is shown in the call flow section later in this
document, the eventual response is a NOTIFY
method indicating that there has been a change in
status.
Registration
1 2
VoLTE call
The initial stages of setting up a VoLTE call are the processes of the initial attach, P-
CSCF discovery and creating the default bearer for SIP signaling (by registering with
the IMS network and subscribing to a registration event package).
The first step in a VoLTE call setup is a SIP INVITE request initiated by the calling UE.
Following this step, agreement is made on the media-specific parameters such as
codecs (e.g. AMR or WB-AMR). After some RINGING, TRYING and OK messaging, the
calling UE may respond with a Provisional ACK (PRACK) method as shown in the flow
diagram above and as defined in RFC 3551. The PRACK method is used because ACK
cannot safely traverse proxy servers that comply with RFC 3261. The PRACK is also
forwarded to the called UE. When the called subscriber answers the call, the called UE
will respond with a 200 OK before the RTP (media) messaging begins.
VoLTE Call
ViLTE Call
MO MT
VoLTE call upgrade to ViLTE
MO MT
1 2 1 2
ViLTE call downgrade to VoLTE call
MO MT
1 2 1 2
VoLTE Conference Call
1 2 3 4 5 6
SMS by IMS
MO
Communication Forwarding Unconditional (cfu)
Access to Call Forwarding Enable Call Forwarding Unconditional (cfu)

menu
Communication Forwarding
SRVCC – 3G
Starting VoLTE call
Starting SRVCC
<- MOBILITYFROMEUTRACOMMAND
SRVCC – 3G
HO completed
Normal call clearing

-> HANDOVERTOUTRANCOMPLETE
SIP Codes
Acronyms
Call Services
. 126
Log Analyses - Call Services LTE
➢ CSFB: CS Fall Back – “extended_service_request”
. 127
Log Analyses - Call Services
CSFB with RRC release Redirection(R8)
. 128
CSFB with RRC release Redirection(R8)
. 129
After success of redirected to WCDMA, Set up call as normal flow
. 130
When the call is disconnected, UE redirect to LTE as network

requirement
. 131
Log Analyses – MO Call
➢ MO Call
▪ Purpose: When UE tries to do a MO call, on L3 window will appear the next messages.
. 132
Log Analyses – MO Call
➢ MO Call
On Setup message can be found the dial number.
. 133
Log Analyses – MT Call
➢ MT Call
▪ Purpose: When UE receive a MT call, on L3 window will appear the next messages.
. 134
Log Analyses – MT Call
➢ MT Call
On Setup message can be found the dial number.
. 135
Log Analyses – Disconnect Message
➢ Disconnection Message in a call (Released by Network or Released by UE)
▪ We concerns on DISCONNECT message during the call is cleared. Refers to 3GPP
TS24.008 9.3.7 & 10.5.4.11, this message contains two directions: released by
Network (DISCONNECT_NW_MS) and by UE (DISCONNECT_MS_NW).
. 136
➢ Disconnection Message in a call (Released by Network)
. 137
➢ Disconnection Message in a call (Released by UE)
. 138
➢ Another way to check Disconnection message in logel tool is find it on Trace
Window, following the next steps
1. Start a call
2. Hang up on the call
3. Press Ctrl-F, select to look in Trace and add the search key “signal ptr->”:
4. ClicK FIND
. 139
➢ Notice the cause value in the following trace window
. 140
AMR (Adaptive Multi-Rate)
. 141
Log Analyses – AMR
➢ AMR (Adaptive Multi-Rate)
Adaptive Multi-Rate (AMR or AMR-NB or GSM-AMR) audio codec is an audio compression

format optimized for speech coding. AMR speech codec consists of a multi-rate
narrowband speech codec that encodes narrowband (200–3400 Hz) signals at variable bit
rates ranging from 4.75 to 12.2 kbit/s with toll quality speech starting at 7.4 kbit/s.
➢ How to check AMR?

Do a MO/MT call, once that the call is established check on trace window from
ArmLogel tool.
. 142
Log Analyses - AMR
➢ AMR Codec - search AMR message on Logel tool
. 143
Log Analyses - AMR
➢AMR-Codec Voice
. 144
Short Message Service (SMS)
. 145
Log Analyses – MO SMS LTE
➢ MO SMS
▪ Purpose: When UE make a MO SMS, on L3 window will appear the next messages.
. 146
Log Analyses – MT SMS LTE
➢ MT SMS
▪ Purpose: When UE make a MT SMS, on L3 window will appear the next messages.
. 147
Log Analyses – MO SMS 3G&2G
➢ MO SMS
▪ Purpose: When UE make a MO SMS , on L3 window will appear the next messages.
. 148
Log Analyses – MT SMS 3G&2G
➢ MT SMS
▪ Purpose: When UE make a MT call, on L3 window will appear the next messages.
. 149
Multimedia Messaging
Service (MMS)
. 150
Log Analyses – MO MMS LTE
➢ MO MMS
▪ Purpose: When UE make a MO MMS, on L3 window will appear the next messages.
. 151
Log Analyses – MT MMS LTE
➢ MT MMS
▪ Purpose: When UE make a MT MMS, on L3 window will appear the next messages.
. 152
Log Analyses – MO MMS 3G&2G
➢ MO MMS
▪ Purpose: When UE make a MO MMS, on L3 window will appear the next messages.
. 153
Log Analyses – MT MMS 2G&3G
➢ MT MMS
▪ Purpose: When UE make a MT MMS, on L3 window will appear the next messages.
. 154
Log Analyses – MMS 2G&3G
➢APN connection on MT MMS
. 155
Log Analyses – APN Deactivate Message
➢ Deactivate_pdp_context_req on MO/MT MMS
. 156
Log Analyses – APN Deactivate Message
➢ Deactivate_pdp_context_acc on MO/MT MMS
. 157
Some Messages in Mobility
. 158
Log Analyses – Mobility Messages
➢ Cell Updated
▪ Purpose: CELL UPDATE message is used by the UE to initiate a cell update procedure on
UL CCCH channel
▪ Note: Refers to 3GPP TS25.331 10.2.7 & 10.3.3.3, there’s a set of cell update cause
values enumerated. The UE usually does a cell update when reselection from one cell to
another, or there’s some uplink data transmission after some time of inactivity or UE
responses to a paging in CELL_PCH/URA_PCH.
. 159
➢ Example of Cell Updated
In the example below, UE does a cell update with the cause “periodical cell update”.
. 160
➢ Types of Cell Updated
. 161
➢ Handover 3G to 2G
▪ Purpose: UE initiates a CS call on 3G, then the Network orders UE to go to 2G by

HANDOVER FROM UTRAN COMMAND_GSM message.
This message is sent on 3G. If the handover is success
. 162
➢ Handover 3G to 2G messages
. 163
➢ Handover 2G to 3G
▪ Purpose: the Network sends PHYSICAL INFORMATION on 2G, UE replies with
HANDOVER COMPLETE if synchronize success.
. 164
Log Analyses - Mobility
➢ Inter-RAT Handover 2G to 3G
. 165
➢ Inter-RAT Handover 2G to 3G - Inter Layer Messages
. 166
➢ Inter-RAT Handover 2G to 3G - Inter Layer Messages

WDM_GSM_RAT_CHG_TO_WCDMA_CNF
ho_type, ho_status
. 167
➢ 2G Serving Cell attach
▪ How can you check the serving cell that UE is attached and the neighbors cells (Cell
information)
▪ Go to Measurement Report message and press double click, then find the message
MPH_CELL_MEAS_IND
. 168
In order to get more info related to Cell Measurement, press double click on the message
MPH_CELL_MEAS_IND, there will be Serving Cell and Neighbor Cells
. 169
In order to get the values on dBm and dB we should apply the next formula
➢GSM
RSSI: (x – 110) dBm
➢ Example
RSSI: (40- 110) = -70 dBm
. 170
➢ 3G Scrambling Code attach
▪ How can you check the serving cell that UE is attached and the neighbors cells (Cell
information)
▪ Go to MEASUREMENTREPORT message on L3 and press double click, then find the

message “[LOCAL] rlc_data_req_struct”
171
In order to get more info related to Cell Measurement, press double click on the message
“[LOCAL] rlc_data_req_struct” and select “Parse By Wireshark”
. 172
In order to get the values on dBm and dB we should apply the next formula
➢WCDMA
RSCP: (x - 116) dBm
EcNo: (x - 49) / 2 dB
➢ Example
RSCP: (34- 116) = -82dBm
EcNo: (31 - 49) / 2 = -9 dB
. 173
Fast Dormancy
. 174
Log Analyses – RRC State Transitions
➢ RRC State Transitions
▪ Purpose: After PDP activation procedure, UE goes into CELL_DCH state at most times. If
the data volume is very small, the Network may reconfigure the UE to some other RRC
states rather than CELL_DCH to save radio resource at Network side and power at UE
side. Refers to 3GPP TS25.331 7.1, it shows the transitions between Idle Mode and UTRAN
RRC Connected Mode.
. 175
Fast Dormancy Test Area
➢ Fast Dormancy is available in all All Mexico DF
. 176
➢ Fast Dormancy Area
In order to check if the area has available or not Fast Dormancy feature, check it
into the logs on SIB1 L3 message the value “t-323: s5”, if it does not appear,
it means that Area does not support Fast Dormancy
▪ Note: We may find the “RRC_StateIndicator” in “Radio Bearer Reconfiguration” or
Physical Channel Reconfiguration message, which is sent by Network to order the
UE go into the specific state. The UE will reply with Radio Bearer Reconfiguration
Complete or Physical Channel Reconfiguration Complete, and then transit to the
specific state.
. 178
. 179
When DUT changes from “DCH state” to “FACH state” it has to send a SCRI “Signalling
Connection Release Indcation with a cause value UE REQUEST DATA SESSION END
. 180
Also the RRC state can be found in the next window
➢ Fast Dormancy Test Cases

. 181
Enhanced cell FACH
Testing Enhanced cell FAH Rel8 implemented
. 182
What is E-FACH?
➢3GPP introduced the next one
▪ ‘Enhanced CELL_FACH’ for DL in Release 7.
▪‘Enhanced CELL_FACH’ in UL and ‘ Enhanced DRX’ in Release 8.
▪These features belong to Enhanced CELL_FACH (E-FACH), It allows that HSPA uses the
CELL_FACH state in order to transfer small and medium data packages.
. 183
Benefits
For Customers For Operators

1. High data rates in Cell_FACH 1. Reduced signaling in the network
2. Real “always on” feeling 2. Increased throughput
3. Fast state transitions from 3. More users supported
Cell_PCH to Cell_FACH (tens of 4. Improvement of UL capacity
milliseconds)
. 184
E-FACH Test Area
➢ E-FACH is available in all All Mexico DF
. 185
Log Analyses – E-FACH
➢ E-FACH Area
In order to check if the area has available or not E-FACH feature, find into the logs
the value “HS-DSCH-CommonSystemInformation IE”into SIB5 L3 messages.
If not E-FACH is not available in area test.
➢ Check HS-DSCH in Cell FACH/PCH and mac-ehs messages in a
“RCCCONNECTION REQUEST”
▪ "HS-PDSCH in CELL_FACH"-TRUE
▪ "MAC-ehs"-TRUE
. 187
. 187
➢RCCCONNECTION REQUEST on WireShark
. 188
➢Then in a RCCCONNECTIONSETUPCOMPLETE message check

the HS-DSCH in CellFACH/PCH and mac-ehs.
. 189
➢Check if UE support HS-DSCH in CellFACH/PCH and mac-ehs
on WireShark
•hsdschReception-CellFach" -TRUE
•hsdschReception-cellPCH" -TRUE
•enhancedFdpch -TRUE
. 190
Also the RRC state can be found in the next window
➢ E-FACH Test Cases
. 191
CPC
. 192
E-FACH Test Area
➢ CPC is available in all All Mexico DF
. 193
CPC Test Plan
Log Analyses – CPC Radio Bearer Setup
➢ CPC relevant parameter
. 195
Log Analyses – CPC Feature
➢ RRC Connection Setup Complete
. 196
Log Analyses – CPC
How Can we check on ARMLOGEL?
▪ DTX_DRX_ENABLE
▪ DRX_ACTIVE
▪ DTX_ACTIVE
. 197
Log Analyses – VAMOS
How to check VAMOS on ARMLOGEL?
▪ VAMOS
▪ Half Rate Channel
Log Analyses – CPC
o CPC: DTX_DRX_ENABLE.
▪ If the value is1, it means that CPC is activated.
o DRX_ACTIVE.
▪ If the value is1, it means that DRX is activated.
o DTX_ACTIVE.
▪ If the value is1, it means that DTX is activated.
. 199
VAMOS
. 200
Introduction
➢ VAMOS doubles voice capacity for GSM; you can have up to four calls per
timeslot, without the need for any additional transceivers.
➢ VAMOS is an excellent solution for increasing voice capacity in a very cost-

efficient way.
. 201
Test Route – VAMOS (Mexico City)
. 202
VAMOS Test Plan
➢ We focus on call in GSM
▪ MO Call with Vamos enabled Cell Static Good RF

▪ MT Call with Vamos enabled Cell Static Good RF
▪ MO Call with Vamos enabled Cell Mobility(RF condtion varies
preferable on routes whereby we move from Good RF to Cell
Edge with Handovers)
▪ MT Call with Vamos enabled Cell Mobility(RF condtion varies
preferable on routes whereby we move from Good RF to Cell
Edge with Handovers)
▪ VAMOS -VAMOS Pairing under different Traffic Load
▪ VAMOS-NON VAMOS Pairing
▪ Long MO Call Mobility on VAMOS test route
▪ MO Call with Vamos enabled Cell Static poor RF
▪ MT Call with Vamos enabled Cell Static poor RF
How to check VAMOS on ARMLOGEL?
▪ VAMOS
▪ Half Rate Channel
o VAMOS level 1.
▪ If the value is1, it means that VAMOS is activated.
o Half Rate Channel

▪ Network assign Half Rate Channel
UNISOC Confidential and Proprietary
All data and information contained in or disclosed by this document is confidential and
proprietary information of UNISOC and all rights therein are expressly reserved. By
accepting this material, the recipient agrees that this material and the information
contained therein is to be held in confidence and in trust and will not be used, copied,
reproduced in whole or in part, nor its contents revealed in any manner to others without
the express written permission of UNISOC. The contents are subject to change without
prior notice. Although every reasonable effort is made to present current and accurate
information, UNISOC makes no guarantees of any kind with respect to the matters
addressed in this document. In no event shall UNISOC be responsible or liable, directly or
indirectly, for any damage or loss caused or alleged to be caused by or in connection with
the use of or reliance on any such content.
THANKS
本文件所含数据和信息都属于紫光展锐所有的机密信
息，紫光展锐保留所有相关权利。本文件仅为信息参
考之目的提供，不包含任何明示或默示的知识产权许
可，也不表示有任何明示或默示的保证，包括但不限
于满足任何特殊目的、不侵权或性能。当您接受这份
文件时，即表示您同意本文件中内容和信息属于紫光
展锐机密信息，且同意在未获得紫光展锐书面同意前，
不使用或复制本文件的整体或部分，也不向任何其他
方披露本文件内容。紫光展锐有权在未经事先通知的
情况下，在任何时候对本文件做任何修改。紫光展锐
对本文件所含数据和信息不做任何保证，在任何情况
下，紫光展锐均不负责任何与本文件相关的直接或间
接的、任何伤害或损失。
请参照交付物中说明文档对紫光展锐交付物进行使用，
任何人对紫光展锐交付物的修改、定制化或违反说明
文档的指引对紫光展锐交付物进行使用造成的任何损
失由其自行承担。紫光展锐交付物中的性能指标、测
试结果和参数等，均为在紫光展锐内部研发和测试系
统中获得的，仅供参考，若任何人需要对交付物进行
商用或量产，需要结合自身的软硬件测试环境进行全
面的测试和调试。
207

Unisoc Latam: Logel User Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Unisoc Latam: Logel User Guide

Uploaded by

Copyright:

Available Formats

UNISOC LATAM

Logel User Guide by Edgar Cortes

How to open a log taken by SD card

- How to take a log with PC

- How to save the log taken by PC

- How to open a log taken by PC

3. ArmLogel Measurements windows

- AMR ( Adaptative Multi-Rate )

- Short Message Service ( SMS )

- Multimedia Messaging Service ( MMS)

- Some Messages in Mobility

- Enhanced Cell FACH

Note: UNISOC general YLOG/Engineer mode code *#*#83781#*#*.

➢ Ylog is used for catching AP, Connectivity,

1.- Dial “*#*#83781#*#*”

2.- Slide to 2nd sheet “DEBUG&LOG”

3.- Choose “Ylog”

▪ When the Round button is blue, that's means Ylogs

logs are running.

– Go to Settings for more options.

➢To have a complete log must select Custom scene ->

1. Once you press commit -> set airplane mode as ON

These steps need to

Clear the Ylog

1. The logs will be saved in the SD log path showed

Note: You can also go to SD Card and look for

Note: UNISOC general YLOG/Engineer mode code *#*#83781#*#*

➢ Ylog is used for catching AP, Connectivity,

1.- Dial “*#*#83781#*#*” (*#*#TEST1#*#*)

2.- Slide to 2nd sheet “DEBUG&LOG”

3.- Choose “Ylog”

▪ When the Round button is blue, that's means Ylogs

logs are running.

– Go to Settings for more options.

➢To have a complete log must select Custom scene ->

1. Once you press commit -> set airplane mode as ON

These steps need to be realized

Clear the Ylog

➢Extra steps ONLY for A11

➢Extra steps ONLY for A11

1.- The logs will be saved in the SD log path showed

Note: UNISOC general YLOG/Engineer mode code *#*#83781#*#*.

➢ Ylog is used for catching AP, Connectivity,

modem, poweron and sensorhub logs

SD Card must be inserted into the phone

1.- Dial “*#*#83781#*#*”

2.- Slide to 2nd sheet “DEBUG&LOG”

3.- Choose “Ylog”

▪ Go to Setting Option>> Select Log Storage Location

▪ >>Select External (To Save the Logs In SD Card).

– Go to Settings for more options.

▪ When the Round button set in stop, that's means Ylogs

logs are running.

– Go to Settings for more options.

➢To have a complete log must select Custom scene ->

1. Choose Setting Option

These steps need to

1. The logs will be saved in the SD log path showed

Note: You can also go to SD Card and look for

1. Open ArmLogel UNISOC tool

3. Then press “Replay” on File options

4. Log location go to “modem_log”>”cp_5mode” or “modem” folder and

select the file with “LOG”extension pressing double click on it

Note: UNISOC general YLOG/Engineer mode code ##83781##.

1.- Dial “##83781##”

Note: UNISOC general YLOG/Engineer mode code ##83781##

1.- Dial “##83781##” (##TEST1##)

Note: UNISOC general YLOG/Engineer mode code ##83781##.

1.- Dial “##83781##”