• 3Gpp2 specifications to be incorporated include:

• X.S0013-003: All-IP Core Network Multimedia Domain: IP Multimedia (IMS) Session Handling; IP Multimedia (IM) Call Model; Stage 2

• X.S0013-004: All-IP Core Network Multimedia Domain: IP Multimedia Call Control Protocol Based on SIP and SDP Stage 3

• X.S0013-005: All-IP Core Network Multimedia Domain: IP Multimedia Subsystem Cx Interface Signalling Flows and Message Contents

• X.S0013-006: All-IP Core Network Multimedia Domain: Cx Interface Based on the Diameter Protocol; Protocol Details

• X.S0013-009: IMS/MMD Call Flow Examples

• X.S0013-010: All-IP Core Network Multimedia Domain: IP Multimedia Subsystem Sh Interface; Signalling Flows and Message Contents - Stage 2

• X.S0013-011: All-IP Core Network Multimedia Domain: Sh Interface Based on Diameter Protocols Protocol Details - Stage 3

• X.S0013-013: All-IP Core Network Multimedia Domain: Service Based Bearer Control – Tx Interface Stage-3

• X.S0013-014: All-IP Core Network Multimedia Domain: Service Based Bearer Control – Ty Interface Stage-3

• X.S0013-016: All-IP Core Network Multimedia Domain: Messaging service using the IP Multimedia (IM) Subsystem (IMS)

• X.S0027-003: Presence Service using IP Multimedia Core Network Subsystem; stage 3

• X.S0029: Conferencing Using the IP Multimedia (IM) Core Network (CN) Subsystem

• X.S0049: All-IP Network Emergency Call Support

• X.S0050: Session Initiation Protocol (SIP) - ISDN User Part (ISUP) Interworking

• X.P0055: MMD Supplementary Services

7.4 Ims Enhancements for support of Packet Cable access (PktCbl) uid_350005

Cable requirements are driven by cable deployments. As such, this work does not place additional requirements on mobile networks or non-cable network operators.

UID	Name	Resource	Hyperlink
350005	IMS Enhancements for support of Packet Cable access	-	-
350008	IMS Enhancements for Cable Client Types and Deployment Models	S2,C1	SP-070105
350011	IMS Inter-working aspects in Support of Cable Regulatory requirements	S2,C1,C3	SP-070107
340008	IMS Enhancements for Security Requirements in Support of Cable Deployments	S3,C1,C3,C4	SP-060933

Ims Enhancements for Cable Client Types and Deployment Models (PktCbl-Deploy) uid_350008

Resources: S2, C1

References

Document	Title/Contents
WID(s)
SP-070105	S2 WID on IMS Enhancements for Cable Client Types and Deployment Models
CP-070122	C1 WID on IMS Protocol Enhancements for Cable Client Types and Deployment Models
Impacted Specifications
TS 23.228	IP Multimedia Subsystem (IMS); Stage 2 [Changes to support cable client configuration requirements]
New Dedicated Specifications/Reports
-	-

Supporting Individual Members SP-070105: CableLabs, Nortel, Cisco, Samsung, Siemens, Motorola, Hewlett-Packard

UID	Name	Resource	Hyperlink	TS_TR
350008	IMS Enhancements for Cable Client Types and Deployment Models	S2,C1	SP-070105	-
350009	Architecture aspects of PktCbl-Deploy	S2	SP-070105	23.228
350010	CT1 aspects of PktCbl-Deploy	C1	CP-070122	-

Cable networks support certain deployment models and client types currently not supported by 3GPP Rel-7 IMS. This work addresses IMS architectural enhancements needed to support cable client types and deployment models.

The following client types and scenarios were identified:

• Embedded client types (e.g. embedded cable modems and IMS clients)

• Software-based Clients that are retrieved, or installed, on computing platforms that are not under operator control

• Clients that may use different physical layer technologies to access the cable network (e.g. DOCSIS, WiFi, Ethernet)

• Clients that can connect via NAT and/or Firewall devices

• Clients without existing relationship with Service Providers (i.e. no prior pre-configuration on the client or in the Service Provider's network)

Requirements:

• Ability to configure and manage these client types

• Ability to update the configuration of clients dynamically

• Ability to configure devices without requiring pre-configuration

• Ability to choose a Service Provider to obtain configuration

Currently, the IMS defines protocol-specific data element definitions. Enhancing this to allow for a wider choice of protocols provides more flexibility to cable (and other) architectures that may leverage existing or newer protocols for various reasons (e.g. one protocol may not cater to all the requirements).

SA2 TS 23.228 was impacted by this work, however no CT specification was effected vs. WID (TS 24.229, TS 24.167; no record in CR Database).