리눅스 비프음 제거
소리 줄이기 setterm -blength 0 vi .bash_profile 에 추가
almost home
🩵 avery cochrane 🩵

Jar Jar Binks Fan Club
Color Me Curious
No title available
cherry valley forever
The Stonewall Inn

Kiana Khansmith

Discoholic 🪩

No title available
Phantogram Three
Cosmic Funnies
Monterey Bay Aquarium
Interview Vampire Daily
2025 on Tumblr: Trends That Defined the Year
The Bowery Presents

izzy's playlists!

blake kathryn
Fai_Ryy
tumblr dot com
seen from Philippines
seen from South Africa

seen from Romania
seen from Canada
seen from India
seen from United States
seen from Peru
seen from Canada
seen from United States

seen from Germany

seen from Italy

seen from Italy
seen from France
seen from France
seen from United States
seen from United States
seen from Mexico
seen from United States
seen from Argentina
seen from Malaysia
@k-zeno-blog
리눅스 비프음 제거
소리 줄이기 setterm -blength 0 vi .bash_profile 에 추가
PDN Connectivity Request
The PDN connectivity procedure is used by the UE to request the setup of a default EPS bearer to a PDN.
The UE requests connectivity to a PDN by sending a PDN CONNECTIVITY REQUEST message to the network. If this request is accepted by the network, then it initiates the establishment of a default EPS bearer context activation procedure.
This procedure is used either to establish the first default bearer (PDN CONNECTIVITY REQUEST is sent along with initial attach message), or to establish subsequent default bearers to additional PDNs (a stand-alone PDN CONNECTIVITY REQUEST is sent by the UE).
If the UE is in EMM-IDLE mode, the Service Request procedure is performed before the PDN Connectivity procedure can be initiated.
If there is already a PDN connection for emergency bearer services established, the UE shall not request an additional PDN connection for emergency bearer services.
A UE attached for emergency bearer services shall not request a PDN connection to any other PDN.
When the PDN CONNECTIVITY REQUEST message is sent together with an ATTACH REQUEST message, the UE shall not include the APN.
When requesting connectivity to an additional PDN, the UE shall include the requested APN (in the stand-alone PDN CONNECTIVITY REQUEST) except for emergency bearer services
The UE may set the ESM information transfer flag in the PDN CONNECTIVITY REQUEST message to indicate that it has ESM information, i.e. protocol configuration options, or APN, or both, that needs to be transferred to the MME after the NAS signalling security has been activated.
If the ESM information transfer flag is set in PDN CONNECTIVITY REQUEST message, the MME initiates (after NAS sigalling security is activated) the ESM information request procedure in which the UE can provide the MME with protocol configuration options or APN or both.
If the UE wishes to connect to a PDN using default APN, it need not include the APN in the Access Point Name IE in the ESM INFORMATION RESPONSE or PDN CONNECTIVITY REQUEST (stand-alone) message. The only exceptional case is, if the connectivity to a PDN using the default APN requires PAP/CHAP, then the UE should include the APN in the Access point name IE.
The UE shall set the Request Type IE to "initial request" when the UE is establishing a new PDN connectivity to a PDN in an attach procedure or in a stand-alone PDN connectivity procedure.
The UE shall set the Request Type IE to "emergency" when the UE is requesting a new PDN connectivity for emergency bearer services.
The Request Type IE is set to "handover" when the connectivity to a PDN is established upon handover from a non-3GPP access network and the UE was connected to that PDN before the handover to the 3GPP access network
The other IEs in the PDN CONNECTIVITY REQUEST message include EPS Bearer Identity, Procedure Transaction Identity, PDN Type, and Device Properties etc…
If the UE includes ESM information transfer flag in the PDN CONNECTIVITY REQUEST message, the MME waits for completion of the ESM information request procedure before proceeding with the PDN connectivity procedure. The MME then checks if connectivity with the requested PDN can be established.
If requested APN is not included in the PDN CONNECTIVITY REQUEST or the ESM INFORMATION RESPONSE message and the request type is different from "emergency", the MME shall use the default APN as the requested APN. If the request type is "emergency", the MME shall use the APN configured for emergency bearer services
Reference 3GPP TS 24.301
Initial Attach Cases
Case 1) Unknown UE / 이전 접속 X Attach Request (IMSI) -> Authentication -> NAS Security Setup -> Location Update -> EPS Session Establishment
Case 2) Unknown UE / MME Unchanged / 이전접속정보 X Attach Request (IMSI) -> Identity Request to UE (IMSI) -> Authentication -> NAS Security Setup -> Location Update -> EPS Session Establishment
Case 3) Unknown UE / MME Changed / 이전접속정보 X Attach Request (IMSI) -> Identification Request to Old MME (IMSI) -> Identity Request to UE (IMSI) -> Authentication -> NAS Security Setup -> Location Update -> EPS Session Establishment
Case 4) Known UE / MME Unchanged Attach Request (IMSI) -> EPS Session Establishment
Case 5) Known UE / MME Changed Attach Request (IMSI) -> Identification Request to Old MME (IMSI) -> Location Update & Cancel Location -> EPS Session Establishment
리눅스 link 생성
* 심볼릭 링크 생성 - ln -s 원본파일 링크파일
* 심볼릭 링크 타켓 변경 - ln -Tfs 타겟파일 링크파일
L3 로그에서 usec 출력
RRC_FPRINTF 참고 ?
S1AP SCTP Association
S1AP가 MME와 초기 연결 시 SCTP 연결요청 수행
- SCTP Client로서 SCTP server 생성은 하지 않음.
디렉토리 용량 확인
$du -hs directory
SCTP - Cookie-ECHO ERROR
SCTP 스택에서 “SCTO_DYNAMIC_IP_SUPPORT” 지원이 되지 않아 발생하는 현상
스레드 동작확인
$ps -eL
pmon.sh
- 프로세스의 상태관리 (ps -ef)
- 알람기능 (to OAM)
filterCoefficeintRSRP/RSRQ 값 설정 시
RRC Reconfiguration 메시지 전송 시
- MeasConfig>QuantityConfig>filterCoefficientRSRP/RSRQ
값을 default 값(fc4)으로 설정하는 경우 메시지 전송 시 해당 element 정보를 실제로 encoding 하지 않고 전송함.
tcpdump
$tcpdump -i eth0 -p sctp