Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.237  Word version:  18.0.0

Top   Top   Up   Prev   Next
0…   4…   5…   5.4…   6…   6.2…   6.2.2…   6.3…   6.3.2…   6.3.2.1.3…   6.3.2.1.7…   6.3.2.1.9…   6.3.2.2…   6.3.2.3…   6.3.2.3.6…   6.3.3…   6.4…   6a…   6a.3…   6a.4…   6a.4.3…   6a.4.5…   6a.4.7…   6a.4a…   6a.5…   6a.6…   6a.7…   6a.8…   6a.9…   6a.10…   6a.11…   6c…   7…   A…   B…   C… 
6.4 Operator Policy and User Preferences  6.5 Execution of supplementary services 
...

 

6.4  Operator Policy and User Preferences  p. 102

Operator Policy is provisioned in the network by the operator, and should be communicated to the UE during initial provisioning or via OMA Device Management [7]. Operator policy should be communicated to the UE, via OMA Device Management, whenever the policy is updated by the operator.
Operator policy shall indicate, for each supported type of media or group of media:
  • a list of access networks that are restricted for originating sessions and Access Transfer;
  • a list of preferred access networks (in order of priority) to be used by the UE with SC capabilities for originating sessions and Access Transfer, when those access networks become available and Access Transfer is possible;
  • whether the UE with SC capabilities "shall"/"should"/"may" start transferring media flow(s) to target access networks with higher priorities than the current access network, when the target access networks become available and Access Transfer is possible;
    • by indicating "shall" the operator mandates the UE to start Access Transfer according to the home operator's list of preferred access networks as soon as possible;
    • by indicating "should" the operator recommends the UE to start Access Transfer according to the home operator's list of preferred access networks, if Access Transfer is possible and desirable after having taken into account the Local Operating Environment Information;
    • by indicating "may" the operator leaves the UE free to decide whether or not to start Access Transfer in accordance with user preferences (when configured), if Access Transfer is possible and desirable after having taken into account the Local Operating Environment Information. Whenever user preferences are not configured, the UE shall to take into account the home operator's list of preferred access networks;
  • whether to keep or drop non transferable media flow(s) in the case of partial Access Transfer.
User preferences may indicate for example:
  • preferred access/domain, i.e. CS preferred or IMS preferred, and which IP-CAN within IMS.
The Local Operating Environment Information is implementation specific and may comprise of such items as, radio environment information, quality of IP connection (jitter, delay and packet loss), application specific requirements, memory considerations, power considerations, etc.
The UE shall take in account operator policy, user preferences and the Local Operating Environment Information when deciding which access to use for outgoing sessions, performing UE assisted T-ADS, or before considering initiating Access Transfer.
Up

6.5  Execution of supplementary services  p. 103

6.5.1  General |R9|  p. 103

This clause describes the SCC AS and UE procedures for execution of supplementary service as described in TS 22.173.
The related interactions apply to scenarios when the media components for the UE are split into multiple Access Legs due to IMS Service Continuity procedures. The Remote Leg is presented with one session including all the media components.
For Access Leg where CS media is used, the interaction described in the following clauses still applies and the service request should be sent via PS Access Leg. The operations on the CS media flows shall be handled based on the service request and shall follow the procedures as described in TS 23.292.
When service invocation fails on one Access Leg, the UE and the SCC AS may retry on a different Access Leg.
Up

6.5.2  Originating Identification Presentation (OIP) |R9|  p. 103

The OIP service is not impacted.

6.5.3  Originating Identification Restriction (OIR) |R9|  p. 104

The OIR service is not impacted.

6.5.4  Terminating Identification Presentation (TIP) |R9|  p. 104

The TIP service is not impacted.

6.5.5  Terminating Identification Restriction (TIR) |R9|  p. 104

The TIR service is not impacted.

6.5.6  Communication Diversion (CDIV) |R9|  p. 104

Upon receiving an incoming session split across multiple Access Legs, if an UE wants to invoke the CDIV service, the UE may use any of the Access Legs to invoke the CDIV service following the procedures defined in TS 24.604.
When the SCC AS splits an incoming session into multiple Access Legs and receives a CDIV request from the UE on any of the Access Legs, the SCC AS shall terminate the other Access Leg(s) and shall invoke the CDIV service following the procedures defined in TS 24.604.
Up

6.5.7  Communication Hold (HOLD) |R9|  p. 104

If the UE wants to invoke the HOLD service on one or more media component(s) and the UE has multiple Access Legs, the UE shall invoke the HOLD procedures, as defined in TS 24.610 on all the Access Legs which contain the affected media component(s). The SCC AS shall update the remote Access Leg using the procedures defined in TS 24.610.
If the remote end initiates the HOLD service on one or more media component(s) and the UE has multiple Access Legs, the SCC AS shall forward the HOLD request on all the Access Legs which contain the affected media component(s).
Up

6.5.8  Communication Barring (CB) |R9|  p. 104

The CB service is not impacted.

6.5.9  Message Waiting Indication (MWI) |R9|  p. 104

The MWI service is not impacted.

6.5.10  Conference (CONF) |R9|  p. 104

When the UE wants to invoke the CONF services and has multiple Access Legs, the UE may send any CONF related requests, e.g. subscribe request for conference package or refer request to the conference, as defined in TS 24.605, on any of the Access Legs.
When the UE has multiple Access Legs and the remote end sends a request for the CONF service to replace an existing session within the same dialog, the SCC AS may deliver the request for CONF service on any of the Access Legs.
When the UE has multiple Access Legs and receives a request on one of the Access Legs for a CONF service to replace an existing session, the UE shall follow the procedures specified in TS 24.605 to establish a new session to the conference focus.
When the UE has multiple Access Legs and receives a request for a CONF service to replace an existing session outside the dialog, the UE shall follow the procedures specified in TS 24.605 to establish a new session to the conference focus.
Up

6.5.11  Explicit Communication Transfer (ECT) |R9|  p. 105

When the UE acts as the transferor UE and has multiple Access Legs, the UE may send the request for ECT service, as specified in TS 24.629, on any of the Access Legs.
When the UE acts as the transferee UE and has multiple Access Legs, the SCC AS may deliver the request for ECT service on any of the Access Legs.
When the UE has multiple Access Legs and receives an ECT request on one of the Access Legs, the UE shall follow the procedures specified in TS 24.629 to establish a new session to the Transfer Target.
Up

6.5.12  Advice of Charge (AOC) |R9|  p. 105

When the AOC service specified in TS 24.647 is active and the UE has multiple Access Legs, the SCC AS may deliver charging information during the communication to the UE over any of the Access Legs.

6.5.13  Closed User Groups (CUG) |R9|  p. 105

The CUG service is not impacted.

6.5.14  Three-Party (3PTY) |R9|  p. 105

The 3PTY service in TS 24.605 is considered as a special case of CONF service and the interaction with Session Transfer is the same as that specified in clause 6.5.10 for CONF service.

6.5.15  Flexible Alerting (FA) |R9|  p. 105

The FA service is not impacted.

6.5.16  Communication Waiting (CW) |R9|  p. 105

Upon receiving an incoming session split across multiple Access Legs, if an UE wants to invoke the CW service, the UE may use any of the Access Legs to invoke the CW service following the procedures defined in TS 24.615.
When the SCC AS splits an incoming session into multiple Access Legs and receives a CW request from the UE on any of the Access Legs, the SCC AS shall invoke the CW service following the procedures defined in TS 24.615.
Up

6.5.17  Completion of Communications to Busy Subscriber (CCBS)/Completion of Communications by No Reply (CCNR) |R9|  p. 105

The CCBS/CCNR service is not impacted.

6.5.18  Customized Alerting Tones (CAT) |R9|  p. 105

The CAT service is not impacted.

6.5.19  Malicious Communication IDentification (MCID) |R9|  p. 105

When invoking the MCID service in temporary subscription mode and there are multiple active Access Legs for the session, the UE may send the re-INVITE request for invoking MCID service as defined in TS 24.616 on any of the Access Legs.

6.5.20  Reverse Charging |R9|  p. 105

The Reverse Charging service is not specified.

6.5.21  Personal Network Management (PNM) |R9|  p. 106

The PNM service is not specified.

6.5.22  Customized Ringing Signal (CRS) |R9|  p. 106

The CRS service is not specified.

Up   Top   ToC