для Cisco Cisco Packet Data Gateway (PDG)
S-GW Changes in Release 17
S-GW Enhancements for 17.1 ▀
Release Change Reference, StarOS Release 17 ▄
571
S-GW Enhancements for 17.1
This section identifies all of the S-GW enhancements included in this release:
Feature Changes - new or modified features or behavior changes. For details, refer to the S-GW Administration Guide
for this release.
for this release.
Command Changes - changes to any of the CLI command syntax. For details, refer to the Command Line Interface
Reference for this release.
Reference for this release.
Performance Indicator Changes - new, modified, and deprecated bulk statistics, disconnect reasons, counters and/or
fields in new or modified schema and/or show command output. For details, refer to the Statistics and Counters
Reference for this release.
fields in new or modified schema and/or show command output. For details, refer to the Statistics and Counters
Reference for this release.
Important:
This release includes enhancements that are applicable to multiple products. The following lists the
various multi-product enhancements sections, some of which might include content applicable to your S-GW.
AAA Enhancements
CF Enhancements
ECS Enhancements
Firewall Enhancements
GTPP Enhancements
Lawful Intercept Enhancements
MVG Enhancements
NAT Enhancements
SNMP MIB Enhancements
System and Platform Enhancements
CSCum88408, CSCum93286 - Separate Paging for IMS Service Inspection
Feature Changes
Support for Separate Paging for IMS Service Inspection
When some operators add an additional IMS service besides VoLTE such as RCS, they can use the same IMS bearer
between the two services. In this case, separate paging is supported at the MME using an ID which can be assigned from
the S-GW according to the services, where the S-GW distinguishes IMS services using a small DPI function to inspect
where the traffic comes from using an ID which is assigned from SGW according to the services. The S-GW
distinguishes IMS services using a small DPI function to inspect where the traffic comes from (for example IP, Port and
so on). After the MME receives this ID from the S-GW after IMS service inspection, the MME will do classified
separate paging for each of the services as usual.
between the two services. In this case, separate paging is supported at the MME using an ID which can be assigned from
the S-GW according to the services, where the S-GW distinguishes IMS services using a small DPI function to inspect
where the traffic comes from using an ID which is assigned from SGW according to the services. The S-GW
distinguishes IMS services using a small DPI function to inspect where the traffic comes from (for example IP, Port and
so on). After the MME receives this ID from the S-GW after IMS service inspection, the MME will do classified
separate paging for each of the services as usual.
Previous Behavior: No private extension was present in Information Element in Downlink Data Notification message.