IMS Release 11 (TS 23.228):
https://www.etsi.org/deliver/etsi_ts/123200_123299/123228/11.10.00_60/ts_123228v111000p.pdf
Interworking between IMS and CS (TS 29.163):
https://www.etsi.org/deliver/etsi_ts/129100_129199/129163/08.09.00_60/ts_129163v080900p.pdf
System Architecture For 5G System (TS 23.501):
https://www.etsi.org/deliver/etsi_ts/123500_123599/123501/15.02.00_60/ts_123501v150200p.pdf
Procedures for 5G System (TS 23.502):
https://www.etsi.org/deliver/etsi_ts/123500_123599/123502/15.02.00_60/ts_123502v150200p.pdf
Policy and Charging Control Framework (TS 23.503):
https://www.etsi.org/deliver/etsi_ts/123500_123599/123503/15.02.00_60/ts_123503v150200p.pdf
Service Based Architecture (TS 29.500):
https://www.etsi.org/deliver/etsi_ts/129500_129599/129500/15.00.00_60/ts_129500v150000p.pdf
Security Architecture & Procedures for 5G system (TS 33.501):
https://www.etsi.org/deliver/etsi_ts/133500_133599/133501/15.01.00_60/ts_133501v150100p.pdf
VoNR, Handovers, Registration, SMS, Location Services (TS 23.502):
https://www.etsi.org/deliver/etsi_ts/123500_123599/123502/15.02.00_60/ts_123502v150200p.pdf
As if there weren’t already enough deployment options for the upcoming 5G network standard, it turns out that for 5G Non-Standalone Option 3, there are actually 3 different variants: 3, 3A and 3X. So what exactly is the difference between them?
The GTI Whitepaper on 5G has a good description and graphics on page 14 so I’ll just summarize the affair here:
As I’ve described in previous posts, 5G Option 3 is the Non-Standalone architecture that still uses the 4G core network (the EPC). In addition, all different flavors of option 3 use the LTE base station as the signaling anchor, i.e. user connection management and radio link control for the combined 4G/5G base station is always managed by the LTE part. This is the same for all options!
At the edge of the EPC, the MME/S-GW are connected over the IP based S1 interface to the combined 4G/5G base station, i.e. the eNB (4G) and the gNB (5G). As the eNB and gNB are logically different components, there is a standardized IP interface between them, the X2 interface. If the eNB and gNB are combined into a single hardware node, the X2 interface is internal, logical, virtual, or whatever you want to call it. So in other words there is the triangle of MME/S-GW at the border of the core network connected to both the eNB and gNB of a combined 4G/5G base station site (over a single physical fiber backhaul connection) and a logical or physical IP interface between the 4G and 5G part of the base station. In other words, there are different options of how data can flow between the core network and the base station and between the two base station parts:
Option 3: In the plain option 3, all data to and from the network flows to and from the 4G part of the 4G/5G base station, i.e. to and from the eNB. The eNB can then decide to forward part of the data to the 5G gNB part of the base station over the X2 interface. This means that the 5G gNB does not communicate with the 4G core network directly!
Option 3A: In this option, both the 4G gNB and the 5G gNB directly talk to the 4G core network but they do not directly talk with each other over the X2 interface. This means that there can be no load sharing of data over a single bearer over 4G and 5G. That means, for example, that the 4G part only handles the VoLTE voice traffic for a user while his Internet traffic is only handled by the 5G part of the base station. I’d say that in most deployment scenarios, this is not really an option if mobile devices move in and out of 5G network coverage continuously.
Option 3X: In this configuration, user data traffic directly flows to the 5G gNB part of the base station. From there, it is delivered over the air interface to the mobile device. It is also possible to forward a part of the data over the X2 interface to the 4G gNB part of the base station and from there to the UE. Slow data streams, e.g. VoLTE bearers with a different IP address than that used for Internet access can be directly delivered from the core network to the 4G gNB part of the 4G/5G base station. The advantage mentioned in the paper linked to above is that the 5G upgrade of the base station is likely to have the much better performing IP interface so it is better suited to handle the higher data rates that can be reached with a 4G/5G Non-Standalone network deployment.
credit: Martin Sauter
https://blog.wirelessmoves.com/2018/07/5g-whats-the-difference-between-option-3-3a-and-3x.html
In case of SRVCC, the home network application server viz., SCC-AS anchors the call. This anchoring by home network tends to increase the handover delay in case a home subscriber roams to a distant network and latches on to a roaming partner. The roaming network now awaits signalling from home network before the call can be handed from LTE to 2G/3G and this could result in handover delay exceeding minimum acceptable limits – causing degraded quality of experience for the end subscriber.
In order to avoid this problem, eSRVCC is proposed, wherein when a subscriber roams to a roaming partner network, the call is anchored at the roaming network itself by a new entity called ATCF/ATGW – which results in substantial reduction in delay. Roaming partner’s ATCF/ATGW coordinates with the home network SCC-AS to complete necessary SIP updates without impacting handover time.
Original Source: http://lteuniversity.com/ask_the_expert/f/59/t/5672.aspx
“Request accepted” is returned when the GTPv2 entity has accepted a control plane request.
“Context Not Found” is used in the response message by a GTP entity when it receives a message for which it does not
have context, e.g. TEID-C or EBI is not known.
“Context Not Found” may also be used by the PGW during UE requested PDN connectivity procedure while non-3GPP
to 3GPP handover, if the request corresponds to the handover of the PDN connection which does not exist with the
PGW.
“Service not supported” is used by the GTP entity when it receives a message, which corresponds to a feature or a
service which is not supported by the node.
“Service denied” is used when the requested service cannot be granted.
“System failure” is used by the GTP entity to indicate a generic error condition.
“No resources available” is used by the GTP entity to indicate the temporary unavailability of the resource(s) to process
the received request.
“Semantic error in the TFT operation”, “Syntactic error in the TFT operation”, “Semantic errors in packet filter(s)”,
“Syntactic errors in packet filters(s)”, “UE context without TFT already activated”, “Semantic error in the TAD
operation” and “Syntactic error in the TAD operation” are indications of error cases involving TFT(s)/TAD(s) as
specified in subclause 7.7.11 in this specification.
“Missing or unknown APN” is used by the PGW when it does not support the Access Point Name, received in Create
Session Request message.
“Relocation failure” is used by the target MME/S4-SGSN to indicate the source MME/S4-SGSN that the relocation has
failed.
“Denied in RAT” is used by the GTP entity to indicate that the requested service is not accepted in the RAT.
“Preferred PDN type not supported” is used by the PGW to indicate that the PDN type received in the Create Session
Request message is not supported by the PGW for the PDN corresponding to the received Access Point Name.
“Protocol type not supported” is used by the SGW to indicate that the S5/S8 protocol type requested by the MME/S4-
SGSN is not supported by it.
“UE not responding” is used by the MME/S4-SGSN to indicate that the UE is not responding to the request initiated by
the network, e.g. Paging.
“UE refuses” is used by the GTP entity to indicate that the UE, without specifying further detail, rejected the request
from the network.
“Unable to page UE” is used by the MME/S4-SGSN to indicate its inability to page the UE, temporarily.
“User authentication failed” is used by the GTP entity to indicate that the request is rejected due to failure in
authentication/security procedure.
“APN access denied – no subscription” is used to indicate that the PGW has denied the user access to an APN because a
subscription is required, but the subscriber does not have the necessary subscription.
“Remote peer not responding” is used by the SGW for the messages spanning through two interfaces. This cause value
is returned by the SGW to the MME/S4-SGSN or PGW in a response message where no response message is received
from the PGW or MME/S4-SGSN.
“Collision with network initiated request” is used by the PGW to indicate that the UE-initiated bearer resource
allocation/modification request is rejected since the PGW has requested a bearer resource allocation/modification for
the same service using a network-initiated procedure.
“Unable to page UE due to Suspension” is used by the MME/S4-SGSN to indicate that the UE has not been paged
because the bearers of the UE are in a suspended state.
“APN Restriction type Incompatible with currently active PDN connection” is used by the PGW to indicate that the
newly requested PDN connection has APN restriction value that is not compatible with the currently active PDN
connection(s)’s APN restriction value(s).
“Context Not Found” is used in the response message by a GTP entity when it receives a message for which it does not
have context, e.g. TEID-C or EBI is not known.
“Context Not Found” may also be used by the PGW during UE requested PDN connectivity procedure while non-3GPP
to 3GPP handover, if the request corresponds to the handover of the PDN connection which does not exist with the
PGW.
“Service not supported” is used by the GTP entity when it receives a message, which corresponds to a feature or a
service which is not supported by the node.
“Service denied” is used when the requested service cannot be granted.
“System failure” is used by the GTP entity to indicate a generic error condition.
“No resources available” is used by the GTP entity to indicate the temporary unavailability of the resource(s) to process
the received request.
“Semantic error in the TFT operation”, “Syntactic error in the TFT operation”, “Semantic errors in packet filter(s)”,
“Syntactic errors in packet filters(s)”, “UE context without TFT already activated”, “Semantic error in the TAD
operation” and “Syntactic error in the TAD operation” are indications of error cases involving TFT(s)/TAD(s) as
specified in subclause 7.7.11 in this specification.
“Missing or unknown APN” is used by the PGW when it does not support the Access Point Name, received in Create
Session Request message.
“Relocation failure” is used by the target MME/S4-SGSN to indicate the source MME/S4-SGSN that the relocation has
failed.
“Denied in RAT” is used by the GTP entity to indicate that the requested service is not accepted in the RAT.
“Preferred PDN type not supported” is used by the PGW to indicate that the PDN type received in the Create Session
Request message is not supported by the PGW for the PDN corresponding to the received Access Point Name.
“Protocol type not supported” is used by the SGW to indicate that the S5/S8 protocol type requested by the MME/S4-
SGSN is not supported by it.
“UE not responding” is used by the MME/S4-SGSN to indicate that the UE is not responding to the request initiated by
the network, e.g. Paging.
“UE refuses” is used by the GTP entity to indicate that the UE, without specifying further detail, rejected the request
from the network.
“Unable to page UE” is used by the MME/S4-SGSN to indicate its inability to page the UE, temporarily.
“User authentication failed” is used by the GTP entity to indicate that the request is rejected due to failure in
authentication/security procedure.
“APN access denied – no subscription” is used to indicate that the PGW has denied the user access to an APN because a
subscription is required, but the subscriber does not have the necessary subscription.
“Remote peer not responding” is used by the SGW for the messages spanning through two interfaces. This cause value
is returned by the SGW to the MME/S4-SGSN or PGW in a response message where no response message is received
from the PGW or MME/S4-SGSN.
“Collision with network initiated request” is used by the PGW to indicate that the UE-initiated bearer resource
allocation/modification request is rejected since the PGW has requested a bearer resource allocation/modification for
the same service using a network-initiated procedure.
“Unable to page UE due to Suspension” is used by the MME/S4-SGSN to indicate that the UE has not been paged
because the bearers of the UE are in a suspended state.
“APN Restriction type Incompatible with currently active PDN connection” is used by the PGW to indicate that the
newly requested PDN connection has APN restriction value that is not compatible with the currently active PDN
connection(s)’s APN restriction value(s).
As specified in sub-clause 5.3.1.1 in 3GPP TS 23.401 [3] and sub-clause 9.2.1 in 3GPP TS 23.060 [35], the cause value
“New PDN type due to single address bearer only” indicates that the MS has requested PDN type IPv4v6 and both IPv4
and IPv6 addressing is possible in the PDN but the Dual Address Bearer Flag of the Indication IE is set to 0 or the
Indication IE is absent, or only single IP version addressing is possible in the PDN.
“PGW not responding” is used by the SGW in PGW Restart Notification to indicate that the peer PGW has failed and
not restarted as specified in subclause 7.9.5.
“UE context without TFT already activated” is used by the PGW in the Bearer Resource Failure Indication message to
indicate that the PGW has received the Bearer Resource Command message without TAD IE in the secondary PDP
Context Activation procedure.
“Target access restricted for the subscriber” is used by the MME/SGSN in the Context Response message to indicate
that the target access is prohibited for the subscriber, based on the subscription profile.
“P-TMSI Signature mismatch” is used by the SGSN or MME in the Identification Response and Context Response
message if the P-TMSI Signature stored in the old SGSN or MME does not match the value sent by the UE via the new
SGSN or MME.
http://blog.modsecurity.org/2010/11/advanced-topic-of-the-week-traditional-vs-anomaly-scoring-detection-modes.html
https://www.netnea.com/cms/apache-tutorial-7_including-modsecurity-core-rules/
The purpose of the service request procedure is to transfer the EMM mode from EMM-IDLE to EMM-CONNECTED
mode and establish the radio and S1 bearers when uplink user data or signalling is to be sent. Another purpose of this
procedure is to invoke MO/MT CS fallback or 1xCS fallback procedures.
This procedure is used when:
– the network has downlink signalling pending;
– the UE has uplink signalling pending;
– the UE or the network has user data pending and the UE is in EMM-IDLE mode;
– the UE in EMM-IDLE or EMM-CONNECTED mode has requested to perform mobile originating/terminating
CS fallback or 1xCS fallback;
The service request procedure is initiated by the UE, however, for the downlink transfer of signalling, cdma2000®
signalling or user data in EMM-IDLE mode, the trigger is given by the network by means of the paging procedure
The UE shall invoke the service request procedure when:
a) the UE in EMM-IDLE mode receives a paging request with CN domain indicator set to “PS” from the network;
b) the UE, in EMM-IDLE mode, has pending user data to be sent;
c) the UE, in EMM-IDLE mode, has uplink signalling pending;
d) the UE in EMM-IDLE or EMM-CONNECTED mode is configured to use CS fallback and has a mobile
originating CS fallback request from the upper layer;
e) the UE in EMM-IDLE mode is configured to use CS fallback and receives a paging request with CN domain
indicator set to “CS”, or the UE in EMM-CONNECTED mode is configured to use CS fallback and receives a
CS SERVICE NOTIFICATION message;
f) the UE performs an inter-system change from S101 mode to S1 mode and has user data pending.
Depending on how they can be initiated, three types of EMM procedures can be distinguished:
1) EMM common procedures:
An EMM common procedure can always be initiated whilst a NAS signalling connection exists. The procedures
belonging to this type are:
Initiated by the network:
– GUTI reallocation;
– authentication;
– security mode control;
– identification;
– EMM information.
2) EMM specific procedures:
At any time only one UE initiated EMM specific procedure can be running. The procedures belonging to this
type are:
Initiated by the UE and used to attach the IMSI in the network for EPS services and/or non-EPS services, and
to establish an EMM context and a default bearer:
– attach and combined attach.
Initiated by the UE and used to attach the IMSI or IMEI for emergency bearer services, and to establish an
EMM context and a default bearer to a PDN that provides emergency bearer services:
– attach.
Initiated by the UE or the network and used to detach the IMSI in the network for EPS services and/or non-
EPS services and to release an EMM context and all bearers:
– detach and combined detach.
Initiated by the UE when an EMM context has been established:
– normal tracking area updating and combined tracking area updating (S1 mode only);
– periodic tracking area updating (S1 mode only).
The tracking area updating procedure can be used to request also the resource reservation for sending data.
3) EMM connection management procedures (S1 mode only):
Initiated by the UE and used to establish a secure connection to the network or to request the resource
reservation for sending data, or both:
– service request.
The service request procedure can only be initiated if no UE initiated EMM specific procedure is ongoing.
Initiated by the network and used to request the establishment of a NAS signalling connection or to prompt
the UE to re-attach if necessary as a result of a network failure:
– paging procedure.
Initiated by the UE or the network and used to transport NAS messages:
– transport of NAS messages;
– generic transport of NAS messages.
The transport of NAS messages procedure and the generic transport of NAS messages procedure cannot be
initiated while an EMM specific procedure or a service request procedure is ongoing.
String split:testvar <- "Hello Word" chars <- strsplit(testvar, split = "")[[1]]Paste:print(paste("Hello", world))