Mind hover

NSSF - Network Slice Selector Function The 5G System architecture (3GPP TS 23.501: 5G SA; Stage 2) consists of the following network functions (NF). - Authentication Server Function (AUSF) - Core Access and Mobility Management Function (AMF) - Data network (DN), e.g. operator services, Internet access or 3rd party services - Structured Data Storage network function (SDSF) - Unstructured Data Storage network function (UDSF) - Network Exposure Function (NEF) - NF Repository Function (NRF) - Network Slice Selection Function (NSSF) ======>>> our focus - Policy Control function (PCF) - Session Management Function (SMF) - Unified Data Management (UDM) - Unified Data Repository (UDR) - User plane Function (UPF) - Application Function (AF) - User Equipment (UE) - (Radio) Access Network ((R)AN)

4G steps towards moving into world of network slicing with different options to utilize the opportunities which cloud/ virtualization market unleashing. Final destination to 5G architecture, where the network slicing is build-in with NSSF introduction in 3GPP. CUPS – Control User Place Separation of 4G network. This attempts to separate the Control and User Place at SGW/ PGW to achieve better control and resource requirements for network deployments. (e)DÉCOR – (enhanced) Dedicated Core Network allocation DÉCOR – R13 (No UE Changes, UE Usage Type parameter in Subscription Data … /// describes UE usage characteristics that enables the selection of a specific Dedicated Core Network (DCN).… MME uses it to map to DCN value. DCN selection at ENodeB Messages where it can be contained ULR (MME-> HSS) / IDR (HSS -> MME) / Reset (HSS -> MME) Authentication Information Answer (AIA – S6A) 29272 – S6A spec - If the MME or SGSN supports the Dedicated Core Netwo

# Linux Networking - http://jodies.de/ipcalc?host=10.230.208.121&mask1=28&mask2= - To explore IP addressing/ masks IPv6 MTU related http://www.tcpipguide.com/free/t_IPv6DatagramSizeMaximumTransmissionUnitMTUFragment.htm https://tgsidau.wordpress.com/2013/12/16/ipv6-pmtud/ # RFCs UDP - 768 IP      - 791 ICMP - 792 TCP   - 793 SCTP - 3286 DIAMETER - 3588 (old), 6733 (latest) # Diameter RFC's Credit control application - 4006 (old), 8506 (latest) DOIC - 7683 DOIC rate control - 8582 # Telecom/ 3GPP / 4G PCC architecture - TS 23.203 Gx Interface - TS 29.212 Procedures -  GTPv1-U - TS 29.281 GTPv2-C - TS 29.274 NAS   TS 24.301  (for 5G its 501) EUTRAN Architecture - TS 23.401 4G procedures - TS 23.401 S1AP Application Part - TS 36.413 S1 general aspects - TS 36.410 4G Security Arechitecture - 33.401 # 5G Arena ------------ 5g spec list from 3gpp site - https://www.3gpp.org/dynareport/SpecList.htm?release=Rel-16&tech=4&ts=1&tr=1 Service Architecture TS 23.501

Radio has always remained as one of crucial resources to wireless technology. They are always first to go into factory to look upon and improve the existing design/ architecture/ philosophies to give better user experience of the core/ back-haul capabilities. https://www.netmanias.com/en/?m=view&id=techdocs&no=13463 more to come ..

The transport has gone for several churn to cater to different requirements at each occassions. Currently after having experiences with SCTP/ MPTCP, the transport is getting one more re-calibrating as QUIC (google experiment) ...... to be updated in coming days. Main aim remains to be as light as UDP and still provide some reliability as TCP but not all. QUIC is an experimental projects towards same. Though the TCP was consistently used over the years and enhanced to mitigate the security/ reliability/ performance aspects. Its defeating the market progression to cloud. Cloud has made new technical advancements for the framework/ protocol/ environments where things can be deployed faster and analysis & results are much faster and quicker. Then our traditional OS based layering and very hard coupling and similarly tedious releasing it for usages and subsequently rollbacks and rollouts processes. Hence the experiment by google QUIC to decouple some of TCP sort of features from

HTTP/2.0 path chosen in 5G wireless technology !! Aka HTTP/2, published as  RFC 7540  in May 2015. HTTP/1.0 releases since 1995 and update by HTTP/1.1 in 1999. For last 20 years the web has transformed and evolved multifold but not HTTP protocol. During these years there were improvement done to HTTP/1.1 from web developers and browsers to improve the user experience. But these changes never made as standards and remains in their own world of web users/ developers for being experienced. That brought difficulty in following terms, Still not optimized enough to meet the full bandwidth utilization. Web design/ maintenance were becoming complex as there exists multiplicity of improvements segregated around the internet. HTTP/2.0 introduced improvements, Multiplexing/ Concurrency Stream Dependencies Header compression Server Push In some cases, the various improvements developed on HTTP/1.1 by individual browser providers became redundant with HTTP/2.0 Best of all, t

SMS with LTE  (SG-SMS) SMS (Short Messaging Service) was quite popular among people during 2G/3G, but now with the advent of 4G losing the shine/ attraction. With 4G people are moving to always-on kind of data connectivity and thus market rising with many application options to provide the messaging capabilities. The examples are such as whatsapp, snapchat etc Now here we are going to discuss, “can an SMS possible in LTE technology ?” and if so “how?” One possibility of using IMS framework and delivering SMS to/from UE. IMS provides the data (e.g. data, media-voice/video) usage overlaid on LTE technology. The bigger question and climax is on market pace in adapting and deployment of the IMS. To address the feature availability, an interim solution (SG interfaces) are suggested in specs. (its similar on the lines on how CS fallback option before LTE supporting Voice calls) Lets revisit the past (2G) on how SMS are delivered. SMS is delivered over signaling channel. This me

5G Specs MTC MTC device addtressing - Since so far wireless devices are addressed using MSISDN/ IMSI which has potentially reached to close to its capacity, given the huge population currently served by networks. A new identifier called "External Identifier" has been introduced, and will be associated with IMSI, format will be NAI based user@host. MEC MicroServices IoT