아이피 부분은 검색하고 싶은 아이피로 편집 

휴대폰 단말에서 와이파이 혹은 모바일 통신에 의해 나가고 들어오는 패킷 확인에 사용

adb radio 로그 상에서 wifi 혹은 Mobile network 가 전환된 로그 확인 후, 

더블체크 용으로 TCP Dump 취득해서 와이어 샤크로 확인


Wifi IP는 와이파이 접속 후, 상세 화면에서 확인 가능, 

Mobile Network IP는 단말설정에서 확인 가능. 

(찾기 귀찮으면 사용중 아이피 알려주는 어플도 많음)  


특정 아이피로 출발 도착 패킷 필터링

 ip.addr == 10.179.154.206


특정 아이피 출발 패킷 필터링

 ip.src == 10.179.154.206 


adb -d 옵션으로 shell에 안 들어간 상태로 확인 가능 

귀찮게 들어갔다 나왔다 안 해도 되었다는 ㅠ_ㅠ



https://developer.android.com/studio/command-line/adb.html#commandsummary


셸 명령 실행


shell 명령을 사용하면 에뮬레이터/기기에서 adb 원격 셸에 들어가거나 들어가지 않고도 adb를 통해 기기 명령을 실행할 수 있습니다. 원격 셸에 들어가지 않고 단일 명령을 실행하려면, 다음과 같은 shell 명령을 사용합니다.


adb [-d|-e|-s serial_number] shell shell_command


-d 연결된 USB 기기로만 adb 명령을 전달합니다.

        둘 이상의 USB 기기가 연결된 경우 오류가 발생합니다.


-e 실행 중인 에뮬레이터 인스턴스로만 adb 명령을 전달합니다.

        둘 이상의 에뮬레이터 인스턴스가 실행 중인 경우 오류가 발생합니다.


-s serial_number adb 할당 일련 번호(예: "emulator-5556")로 참조되는 

                        특정 에뮬레이터/기기 인스턴스로 adb 명령을 전달합니다.





①Google 검색 (eSRVCC); 개요 

   IMS_Information_Gateway_VoLTE_Signaling_Analysis_Manual(eSRVCC).pdf


②SRVCC&eSRVCC의 차이. QA (참조용)

   http://lteuniversity.com/ask_the_expert/f/59/t/5672.aspx


③관련 문서(로그 확인 용)

 http://www.qtc.jp/3GPP/Specs/24237-a30.pdf

   3GPP TS 24.237 V10.3.0 (2011-06) 

   Technical Specification 3rd Generation Partnership Project; 

   Technical Specification Group Core Network and Terminals; 

   IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) Service Continuity;

   Stage 3 (Release 10)


④관련 문서(참고용)

   http://www.qtc.jp/3GPP/Specs/23216-b70.pdf

 3GPP TS 23.216 V11.7.0 (2012-12)

 3rd Generation Partnership Project;

 Technical Specification Group Services and System Aspects; 

 Single Radio Voice Call Continuity (SRVCC); Stage 2 (Release 11)


참고해서 낼은 로그를 확인해봐야.. . 과연과연 두구두구 

http://zewtion.tistory.com/m/post/274


adb devices
:디바이스 검색


adb install -? APP설치파일.APK
: 어플을 설치한다
(명령어 사용안한다면 일반 설치한다)
-r 설치된 어플을 재 설치한다 단 데이터는 삭제되지 않는다.
-s 메모리카드에 설치한다.
* adb install c:\어플폴더\abcd.apk


adb uninstall -? 어플이설치된경로
: 어플을 삭제한다
(명령어 사용안한다면 모두 삭제한다)
-k 어플의 데이터는 삭제 하지 않는다.
* adb uninstall com.android.abcd


adb reboot
: 스마트폰을 재부팅 시킨다.


adb kill-server
: 문제 발생시 adb 종료


adb start-server
: 종료 시킨 adb 실행


adb pull 스마트폰경로 PC경로
: 스마트폰기기내에 파일이나 어플등을 본인의 PC로 복사한다
* adb pull /sdcard/abcd.apk c:\abcd

adb push PC경로 스마트폰경로
: PC의 파일이나 어플등을 스마트폰으로 복사한다
* adb push c:\abcd\abcd.apk /sdcard/

adb root
: 스마트폰에 root권한으로 접근한다.

adb shell
:연결된 스마트폰의 쉘을 연결한다
* adb -s emulator-디바이스번호 shell
퍼미션 부여 =adb chmod 777 경로
파일삭제 = adb shell rm 경로
폴더삭제 = adb shell -r 경로

아래는 shell 명령어 가져온글 입니다
시스템 기본정보: 하드웨어, 커널 등
cat /proc/version : 커널 버전
cat /proc/cpuinfo : 프로세서 정보, CPU타입, 모델 제조사 등
cat /porc/meminfo : 메모리 정보, 실제 메모리 및 가상 메모리
cat /proc/devices : 현재 커널에 설정되어 있는 장치 목록
mount : 마운트된 모든 장치 정보
df : 하드디스크 사용량
cat /porc/filesystems : 커널에 설정되어 있는 파일시스템 목록
cat /proc/swaps : 스왑 파티션의 크기와 사용량
cat /proc/interrupts : 장치가 사용중인 인터럽트(IRQ)목록 표시
cat /proc/ioports : 현재 사용중인 input/output 포트
cat /proc/partitions : 파티션 정보
cat /proc/uptime : 시스템이 얼마나 살아있었는지
cat /proc/stat : 시스템 상태에 관한 다양한 정보, CPU 사용 통계, 부팅이후 page fault 발생 횟수 등
cat /proc/zoneinfo : ZONEINFO
dmesg : 시스템 부팅시 나왔던 메시지
ps : 실행중인 프로세스 정보
ps -p - t : 프로세스와 쓰레드 목록
set or printenv : 환경설정값 출력


시스템 리소스 사용 현황
vmstat : 시스템 리소스 상황 모니터, CPU, I/O, Memory 등
cat /proc/diskstats : 디스크 utilization과 throughput. 즉 디스크 I/O현황
top : 시스템 프로세스 상황 모니터링/ 프로세스별 CPU사용량, 메모리와 스왑 사용량 등
procrank : 프로세스별 메모리
dumpsys meminfo [PID] : 해당 프로세스 메모리 상세 정보
cat /proc/[PID]/stat : 해당 프로세스에 대한 정보, 시작시간, 상태, CPU 사용량 등
cat /proc/[PID]/maps : 해당 프로세스의 메모리 맵 정보
cat /proc/vmstat : 버추얼 메모리 통계?
librank : 라이브러리별 메모리 사용량?


네트워크 관련
cat /proc/net/netlink : 네트워크 정보
netcfg : 네트워크 인터페이스와 IP주소 목록
netstat : 네트워크 연결상태 확인
nc : 네트워크용 cat 명령어(netcat)
ifconfig : 네트워크 인터페이스 설정 정보. 장치명을 파라미터로 받음. ip 주소. 서브넷마스크 등
tcpdump : 실시간 패킷 모니터링
iftop : 네트워크를 위한 top
route : 해당 호스트까지 연결하는 중간 경로 정보인 라우팅 테이블 표시
ping : 원격 호스트와의 연결 테스트
cat /proc/net/route : Route


안드로이드 제공
logcat : 로그캣 보기
pm : package manager의 약자. 패키지/permission/instrumentation/feature 목록, 패키지 설치/제거 등
am : activity manager의 약자, 액티비티 시작, Intent 브로드캐스팅, Instrumentation 시작, profiling 시작 / 중지 등
service : 안드로이드 서비스 목록 표시, 서비스에 명령 전달
monkey : 애플리케이션에 랜덤 이벤트 발생시킴. 사용자 이벤트, 시스템 이벤트의 무작위 발행
cat /data/anr/traces.txt : VM TRACES (쓰레드 덤프)
cat /proc/binder/proc/[PID] : 바인더 프로세스 상태
cat /proc/binder/xxx : 바인더 관련 정보(xxx은 transaction, transaction_log, failed_transaction_log, stats 등)
cat /data/system/packages.xml : 설치된 패키지 세팅 정보
setprop : system property 셋팅
getprop : 셋팅된 system property 목록 출력


종합 리포트
dumpsys [service] : app/service 상태정보 덤프, 서비스별로 추가 파라미터 받을 수 있음
dumpstate : device 상태정보 덤프. 상태정보를 추출하는 여러 명령어들의 조합으로 구성
dumpcrash : 애플리케이션이 crach될 때의 상태정보 덤프
bugreport : logcat + dumpsys + dumpstat



조금더 정보가 필요하신분들을 위한 정보 입니다.

ADB Shell Command - 15가지 팁

Basic Android Terminal and ADB Shell Command List
1. How to open a cmd in Android Phone
Method 1: “Start” ? “”Program”-” “Accessories” ? “” Command Prompt ”
Method 2: “Start” ? “” Run “, type cmd ENTER
2. How to restart Android Phone
When the phone and Computer is connected to the data cable, you can enter the following command
adb shell reboot === ENTER
3. Restart Android into Recovery Mode
With the data cable connected to your phone and computer, enter the following command

adb shell reboot recovery === ENTER
4. Convert back to ext2 partition
Restart the phone into Recovery mode, press “Alt + X” into the console. Open cmd and enter the following command

adb shell === ENTER
tune2fs-O ^ has_journal / dev/block/mmcblk0p2 === carriage return
e2fsck / dev/block/mmcblk0p2 === carriage return (optional, can be a problem area in section 2, when used)
5. Pulling applications from Android phone to computer
adb pull /system/sd/app app
adb pull /system/sd/app-private app-private
6. Pushing applications back to android phone from the computer
adb push app /system/sd/app
adb push app-private /system/sd/app-private
7. Delete existing apps on Android SD
adb shell rm -r /system/sd/app
adb shell rm -r /system/sd/app-private

8. Repair gravity System or switch to screen
Sometimes frequent brushing of phone can cause gravity system or switch to screen failure. Just follow the steps below-
Restart the phone into Recovery mode, press “Alt + X” into the console
Open cmd and enter the following command
mount / data === carriage return
rm / data / misc / akmd * / data / misc / rild * === ENTER
9. Ext2/ext3/ext4 formatted partition
Enter the following command in the cmd
adb remount === ENTER
adb shell === ENTER
rm-r / system / sd / * === carriage return

10. Remove/ system / app under the application
Under normal circumstances / system / app is not under an application. Use the following methods to remove these applications.
Open cmd and enter the following command

adb remount === ENTER
adb rm / system / app / Stocks.apk === Enter
11. If the start Time is too Long
Just enter the following command in order to view the boot process.
adb logcat === ENTER
12. Through Terminal Partition SD card
It will erase everything on your SD card
$ su
# cd /data
# wget http://64.105.21.209/bin/lib/droid/sdsplit
# chmod 555 sdsplit
# /data/sdsplit -fs *size* (add -nc to the end for JFv1.5ADP)
13. From the Recovery Screen, send an update file to your SD card.
adb shell mount /sdcard
adb shell rm /sdcard/update.zip
adb push *filename* /sdcard/update.zip
14. Restoring a nandroid backup via Fastboot
Start command-prompt/terminal cd to the nandroid folder and enter following commands
fastboot erase boot
fastboot erase recovery
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot reboot
15. Clear Search History in Android
Search History is accounted for Mobile Memory. It can also leak your privacy information as well. Just follow the steps below to clear android history.
Steps are as follows:
1. Make sure your mobile phone has Root authority.
2. Open the super-terminal.
3. Enter the following command
su
rm / data / data / com.android.vending / databases / suggestions.db
4. Exit Hyper Terminal and restart the phone.

'Japan > Work As Tester' 카테고리의 다른 글

adb -d 옵션  (0) 2017.02.14
eSRVCC 참조용 링크  (0) 2017.02.14
adb shell  (0) 2016.05.25
회선, 메시지, 패킷 교환방식 (Circuit, Message, Packet switching)  (0) 2016.05.20
[Mobile] LTE IP Address Allocation Schemes I: Basic  (0) 2016.05.20
모바일 네트워크  (0) 2016.05.19

Circuit Switched Core Network (CS-CN


http://proneer.tistory.com/trackback/327

http://proneer.tistory.com/entry/%ED%9A%8C%EC%84%A0-%EB%A9%94%EC%8B%9C%EC%A7%80-%ED%8C%A8%ED%82%B7-%EA%B5%90%ED%99%98%EB%B0%A9%EC%8B%9DCircuit-Message-Packet-switching

회선, 메시지, 패킷 교환방식


'Japan > Work As Tester' 카테고리의 다른 글

eSRVCC 참조용 링크  (0) 2017.02.14
adb shell  (0) 2016.05.25
회선, 메시지, 패킷 교환방식 (Circuit, Message, Packet switching)  (0) 2016.05.20
[Mobile] LTE IP Address Allocation Schemes I: Basic  (0) 2016.05.20
모바일 네트워크  (0) 2016.05.19
Call Flow  (0) 2016.05.19

SUMMARY

This document will describe how an LTE network allocates IP addresses to users accessing the network. IP addresses can be either dynamic or static depending on their allocators. Below we will discuss how the two types are different, and how they are allocated.

 Table of Contents  
  I. Introduction
  II. Types of IP Address Allocation
  III. Dynamic IP Address Allocaion
  IV. Static IP Address Allocation
  V. Closing

I. Introduction

LTE networks are all-IP networks. This means that they deliver all user traffic in IP packets, and provide users with “always-on IP connectivity”. When UE joins an LTE network, a Packet Data Network (PDN) address (i.e. the one that can be used in the PDN) is assigned to the UE for its connection to the PDN, and a default bearer is established in the LTE network (i.e. between UE and P-GW). This default bearer remains connected (i.e. the IP address assigned to the UE during the initial attach remains valid) until the UE is detached from the LTE network.
A default bearer is established for each APN (Access Point Name)1 a user has, and thus a unique IP address is assigned for each APN. An IP address can be an IPv4, IPv6 or IPv4/IPv6 type.

This document will explain how an LTE network allocates an IP address to a user (i.e. UE) when the user initially attaches to the network, by giving an example of a case where UE uses only one PDN, the Internet, and an IPv4 type address is assigned to the UE.

Two different types of IP address allocation will be discussed in this and next documents. This document will cover the basic IP address allocation schemes and procedures, describing how IP addresses are allocated to a user who, while staying in one place, is performing initial attach to the network multiple times (e.g. by turning off UE and then back on). The next document will look into different ways of IP address allocation in case a user performs initial attach from two geographically-separated locations (e.g. City A and City B).

This document is organized as follows: In Chapter II, different types of IP address allocation – dynamic and static - and their characteristics will be discussed. Chapters III and IV will provide the detailed explanation of the dynamic and static IP address allocation procedures, respectively.

II. Types of IP Address Allocation

When UE initially attaches to an LTE network, it requests for a PDN connection. Then a P-GW allocates an IP address (i.e. PDN address) to be used by the UE for the PDN, and forwards it to the UE while a default bearer connecting the two is being established. With this IP address, the UE can use services provided through the PDN.

A P-GW allocates IP addresses in two ways: dynamic or static IP address allocation. In case of dynamic allocation, it automatically assigns an IP address every time UE accesses the network. On the other hand, in case of static allocation, it assigns a designated IP address to UE upon its subscription, and then allocates the designated IP address every time it accesses the network. Figure 1 below compares the two types.

 

Figure 1. IP Address Allocation Schemes

[출

In case of dynamic IP allocation, the network (e.g. P-GW) automatically selects an IP address for UE. The network operator has IP pool(s) provisioned at the P-GW in advance. Then later when UE initially attaches to the LTE network, the P-GW dynamically allocates an IP address to the UE. So, a new dynamic IP address is allocated to the same UE every time it initially attaches to the network.

However, in case of static IP allocation, the network operator allocates a permanent IP address to each UE upon their subscription to the network. The operator has an allocated static IP address provisioned for UE in the network (HSS) along with other subscription information. Then later when the UE initially attaches to the LTE network, the P-GW obtains the static IP address from HSS, and forwards it to the UE. So, this particular IP address is allocated to the UE every time it initially attaches from then on.

When requesting for a PDN connection during initial attach, UE can request for protocol data related with external protocol/application (e.g. configuration parameters) by using Protocol Configuration Options (PCO)2 parameters (e.g. request for DNS server address, P-CSCF address). This document will explain a case where DNS server addresses as well as an IP address are requested.

III. Dynamic IP Address Allocation

For dynamic allocation, the network (P-GW) keeps IP pool(s) for UEs, and dynamically allocates an IP address to UE upon its initial attach to the LTE network as seen in Figure 2 below.

 

Figure 2. Procedure for Dynamic IP Address Allocation

 


IP Provisioning at P-GW
At P-GW, an IP Pool containing IP addresses to be assigned, and DNS server IP addresses are already provisioned.


 



Procedure for Dynamic IP Address Allocation
A user turns on his UE, attempting initial attach to the LTE network. An explanation about general procedure for initial attach can be found in our previous technical document [2]. Here we will focus on IP address allocation only.

  1)   [UE → MME] Requesting for PDN (Internet) Connectivity
The UE requests for a PDN connection by sending PDN Connectivity Request (PDN type=IPv4, PCO=DNS Server IPv4 Address Request) message to MME. At this time, in addition to an IPv4 address for the UE, IP addresses for DNS servers (by PCO field) are requested as well. The PDN Connectivity Request message is an ESM message, and thus is embedded in the ESM Message Container field of Attach Request (IMSI3, ESM Message Container), an EMM message, when delivered.

  2) ~ 3) [MME → S-GW → P-GW] Requesting for Session Creation
The MME, based on the subscription profile received from HSS, sends Create Session Request (IMSI, PDN Type=IPv4, PDN Address=0.0.0.0, PCO=DNS Server IPv4 Address Request) message to the P-GW for EPS session creation. As it is dynamic IP allocation, the subscription profile does not include IP address information. In the Create Session Request message, 0.0.0.0 is set for PDN Address field, and the PCO information received from the UE is included in PCO field.

  4)   [P-GW] Allocating PDN Address and DNS Server Addresses
The P-GW, after checking the PDN type and PDN address (0.0.0.0), knows that an IPv4 address has to be assigned. It selects an IP address (e.g. UE IP=1.1.1.5) from the IPv4 pool, and assigns it to the UE. As requested by PCO field, DNS server IP addresses are also assigned accordingly.

  5) ~ 6) [MME ← S-GW ← P-GW] Responding to Create Session Request
As a response to the request made in Steps 2) and 3), the P-GW sends Create Session Response message to the MME. This message includes the UE IP address (dynamically assigned by the local P-GW) in PDN Address field, and the DNS server IP addresses (requested by user through PCO field) in PCO field.

  7)   [UE ← MME] Requesting for Activation of Default Bearer Context
The MME requests for activation of the default bearer context by sending UE Activate Default EPS Bearer Context Request (PDN Type=IPv4, PDN Address=UE IP(1.1.1.5), PCO={Primary DNS IP, Secondary DNS IP}) message. This ESM message contains the DNS server IP addresses as well as the UE IP address, and is embedded in Attach Accept message, an EMM message, when delivered.

  8)   [UE] Obtaining Dynamic IP Address for Using PDN Service
The UE obtains the dynamic IP address (1.1.1.5) and DNS server IP addresses (Primary DNS IP=10.1.1.1, Secondary DNS IP=10.1.1.2). A default bearer is established between the UE and the P-GW. The UE, now connected to a PDN (Internet), can use the Internet service with its dynamic IP address.

IV. Static IP Address Allocation

In case of static IP address allocation, the network operator assigns a UE IP address to a user when the user subscribes to the network for the first time, provisions his subscription profile at HSS, and assigns the static IP address stored in the profile every time he attempts initial attach to the network. The detailed procedure is illustrated in Figure 3.
 

 

Figure 3. Procedure for Static IP Address Allocation

[


IP Provisioning at HSS
At HSS, subscription profiles of each subscriber are provisioned. The profile includes a PDN type and a PDN address to be used for PDN connection.

 

IP Provisioning at P-GW
At P-GW, DNS server IP addresses have already been set.

 

Procedure for Static IP Address Allocation
A user turns on his UE, attempting initial attach to the LTE network.

  1)   [UE → MME] Requesting for PDN (Internet) Connectivity
The UE requests for a PDN connection by sending PDN Connectivity Request (PDN type=IPv4, PCO=DNS Server IPv4 Address Request) message to the MME. At this time, in addition to an IPv4 address for the UE, IP addresses for DNS servers (by PCO field) are requested as well.

  2)   [MME → HSS] Requesting the LTE Network for Registration
The MME informs HSS that the UE is under its (e.g. MME1) control by sending Update Location Request message, and registers the UE at the network.

  3)   [MME ← HSS] Forwarding Subscription Profile
The HSS, recognizing the UE is registered at MME1, forwards the UE’s subscription profile to MME1 by sending Update Location Answer (IMSI, PDN Type=IPv4, PDN Address=Static UE IP(1.1.1.1)) message. This subscription profile includes the static IP address assigned to the UE.

  4) ~ 5) [MME → S-GW → P-GW] Requesting for Session Creation
After receiving the UE’s subscription profile from the HSS, the MME knows the UE has a static IP address (1.1.1.1). The MME prepares Create Session Request (IMSI, PDN Type=IPv4, PDN Address=Static UE IP(1.1.1.1), PCO=DNS Server IPv4 Address Request) message and sends it to the P-GW. At this time the message includes the static IP address received from the HSS in PDN Address field, and PCO information received from the UE in PCO field.

  6) ~ 7) [MME ← S-GW ← P-GW] Responding to Create Session Request
As a response to the request made in Steps 4) and 5), the P-GW and the S-GW send Create Session Response (IMSI, PDN Type=IPv4, PDN Address=Static UE IP(1.1.1.1), PCO={Primary DNS IP, Secondary DNS IP}) message to the MME. This message includes the static IP address assigned to the UE in PDN Address field, and the DNS server IP addresses (requested by user through PCO field) in PCO field.

  8)   [UE ← MME] Requesting for Activation of Default Bearer Context
The MME requests for activation of the default bearer context by sending the UE Activate Default EPS Bearer Context Request (PDN Type=IPv4, PDN Address=Static UE IP(1.1.1.1), PCO={Primary DNS IP, Secondary DNS IP}) message. This ESM message contains the UE’s static IP address (1.1.1.1) as well as DNS server IP addresses, and is embedded in Attach Accept message, an EMM message, when delivered.

  9)   [UE] Obtaining Static IP Address for Using PDN Service
The UE obtains the static IP address (1.1.1.1) and DNS server IP addresses (Primary DNS IP=10.1.1.1, Secondary DNS IP=10.1.1.2). A default bearer has been established between the UE and the P-GW. The UE, now connected to a PDN (Internet), can use the Internet service with its static IP address.

V. Closing

So far we have discussed the two types of IP address allocation: dynamic and static. When a user attempts initial attach to the LTE network to use a PDN service (e.g. Internet, VoLTE, etc), the LTE network provides the user with PDN connectivity by allocating an IP address to be used for the PDN and a default bearer. As long as the user’s network registration is valid, the PDN address (IP address) and the default bearer are kept for the user even when he is no longer using the service. This way, the user is provided “always-on IP connectivity”.

This document has explained the scheme and procedure of IP address allocation by an LTE network when UE attempts to use a PDN service from one location, but in different times. In the next document [1], we will cover the same topics, but discuss a case where UE attempts to use a PDN service from different locations.

References

[1] Netmanias Technical Document, “LTE IP Address Allocation Schemes II: A Case for Two Cities”, February 2014 (TBD)
[2] Netmanias Technical Document, “EMM Procedure 1. Initial Attach - Part 1. Cases of Initial Attach”, December 2013
[3] NMC Consulting Group Confidential Internal Report, “E2E LTE Network Design”, August 2010


Footnotes

1. Default bearers are established for each PDN. APN is a PDN ID, and PDN information is delivered to users as APN. So, APN, more appropriate term from a user perspective, was used here.
2. See 3GPP TS 24.008 for more information about PCO.
3. If UE has a valid old GUTI, the GUTI can be used as an EPS Mobile ID.



http://blog.naver.com/PostView.nhn?blogId=netmaniascom&logNo=220282969002


 [출처] [Mobile] LTE IP Address Allocation Schemes I: Basic|작성자 넷매니아즈

'Japan > Work As Tester' 카테고리의 다른 글

adb shell  (0) 2016.05.25
회선, 메시지, 패킷 교환방식 (Circuit, Message, Packet switching)  (0) 2016.05.20
[Mobile] LTE IP Address Allocation Schemes I: Basic  (0) 2016.05.20
모바일 네트워크  (0) 2016.05.19
Call Flow  (0) 2016.05.19
qxdm references  (0) 2016.05.19

http://victor8481.tistory.com/202

http://passorfail.tistory.com/6


Call Flow 

'Japan > Work As Tester' 카테고리의 다른 글

[Mobile] LTE IP Address Allocation Schemes I: Basic  (0) 2016.05.20
모바일 네트워크  (0) 2016.05.19
Call Flow  (0) 2016.05.19
qxdm references  (0) 2016.05.19
Circuit-Switched (CS) Call Control (CC)  (0) 2016.05.19
GSM  (0) 2016.05.19

http://passorfail.tistory.com/30 불바다폴


http://withwani.tistory.com/73  박투

'Japan > Work As Tester' 카테고리의 다른 글

모바일 네트워크  (0) 2016.05.19
Call Flow  (0) 2016.05.19
qxdm references  (0) 2016.05.19
Circuit-Switched (CS) Call Control (CC)  (0) 2016.05.19
GSM  (0) 2016.05.19
CBS  (0) 2016.05.18

http://www.slideshare.net/LouisKHKuo/elementary-procedures-for-circuit-switched-cs-call-control-cc-in-3-gpp



Elementary procedures for Circuit-Switched (CS) Call Control (CC) in 3GPP


'Japan > Work As Tester' 카테고리의 다른 글

Call Flow  (0) 2016.05.19
qxdm references  (0) 2016.05.19
Circuit-Switched (CS) Call Control (CC)  (0) 2016.05.19
GSM  (0) 2016.05.19
CBS  (0) 2016.05.18
네트워크 테스트 용 Secret code(Samsung)  (0) 2016.05.16

+ Recent posts