Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.172  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   4.2.2…   4.2.3   4.2.4   4.2.5…   4.2.5.2   4.3…   4.3.2…   4.3.3…   4.3.3.1.3   4.3.3.1.4   4.3.3.1a…   4.3.4   4.3.5…   4.3.5.2   4.3.6…

 

4  Service change and fallback for UDI/RDI multimediap. 7

4.1  General Requirementsp. 7

The Service Change and UDI Fallback (SCUDIF) is a function which applies to UDI/RDI multimedia calls (see clause 7.2.1 of TS 22.101), and shall support the following:
  1. Fallback to speech during call setup: allow a user to attempt to set up a multimedia call, and try a speech connection if the former doesn't succeed;
  2. Fallback to the less preferred service (speech or multimedia) during call setup: allow the terminating side via specific settings for this service in the terminal to accept or reject a multimedia call, without interrupting the call setup;
  3. Fallback to the preferred service (speech or multimedia) or speech during call setup: allow the call setup to proceed with a single service if the transit network does not support the signalling of this functionality;
  4. BC negotiation at the terminating side: allow the terminating side via specific settings for this service in the terminal to turn a speech call (with service change) into a multimedia call and vice-versa;
  5. Service change: allow a speech call to be turned to multimedia by either of parties, and back to speech, through a successful in call modification procedure;
  6. Allow any of the users to reject a multimedia request from the other party while in speech mode.
  7. Network-initiated service change: The network shall initiate a sevice-change from multimedia to speech during the active call if a multimedia call can no longer be supported. If a multimedia call can again be supported at a later point in time, the network may initiate a service change from speech to multimedia.
To fulfil:
  • service request signalling between the UE and the MSC;
  • service request signalling across the Core Network.
This functionality is not supported for multimedia with Fixed Network User Rate set to 32 kbit/s. In this case, the MSC shall revert to a multimedia only call.
Up

4.2  Access Call Control Signallingp. 8

Using the repeat indicator value "support of service change and fallback", as described in clause 5.3.6 of TS 24.008, together with two BC-IEs, a multimedia and a speech, it is possible to request a service change and fallback functionality, while still maintaining the backwards compatibility with non-supporting terminals.

4.2.1  Mobile originating side - initiation of call setupp. 8

By sending a SETUP message with a Repeat Indicator set to "support of service change and fallback", a multimedia BC-IE, and a speech BC-IE (see Figure 4.1), a terminal may request a call to be set with the capability to fallback to either a speech only, a multimedia only call or to use service change later during the active state of the call (the first BC IE indicates the preferred service). If the terminal supports Network-initiated service upgrade to multimedia, then it shall also indicate this in the SETUP message with the "Enhanced Network-initiated ICM" (ENICM) Capability (see TS 24.008).
After checking the provisioning (see subclause 4.2.1.1), and verifying that the functionality is supported, the MSC replies in the CALL PROCEEDING message with either the two BCs in the same order (to indicate that it accepts the proposed settings - see Figure 4.2), or with a single BC (multimedia or speech - see Figure 4.3) unless the CALL PROCEEDING is delayed until the response from the terminating user and then it may also be sent with the BCs in reverse order (see clause 4.2.3).
In the case the MSC ignores the SETUP message if the presence of a reserved value for the Repeat Indicator is set, it sends a STATUS message back to the UE (see Figure 4.4), with the Cause Value set to #100, "Conditional IE error" (see clause 8.7.2 of TS 24.008). The UE then reacts as described in clause 5.5.3.2.2 of TS 24.008, and may resend a new SETUP message with a single BC, or perform any appropriate action according to its implementation. This also applies in case the MSC returns instead a RELEASE COMPLETE message.
Copy of original 3GPP image for 3GPP TS 23.172, Fig. 4.1: SETUP message towards the originating MSC
Up
Copy of original 3GPP image for 3GPP TS 23.172, Fig. 4.2: Normal case
Figure 4.2: Normal case
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.172, Fig. 4.3: Fallback case
Figure 4.3: Fallback case
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.172, Fig. 4.4: MSC not supporting the RI value
Figure 4.4: MSC not supporting the RI value
(⇒ copy of original 3GPP image)
Up

4.2.1.1  Subscription checkingp. 9

The functional behaviour of the originating MSC and VLR is specified in TS 23.018. The procedure specific to SCUDIF is specified in this subclause:
For mobile originated SCUDIF calls, the MSC shall convert both PLMN bearer capability 1 and PLMN bearer capability 2 to two individual Basic Service codes and send them in Send Info For Outgoing Call. The VLR shall check the subscription for those basic services, then indicates the availability of each basic service to the MSC by Complete Call. If both services are not provisioned, the VLR shall send Send Info For Outgoing Call negative response to the MSC. The MSC shall fall back to the allowed service if the availability of only one service is indicated. The MSC shall continue as a SCUDIF call if the availability of both services is indicated.
Up
4.2.1.1.1  Send Info For Outgoing Callp. 9
Send Info For Outgoing Call contains the following SCUDIF specific information elements:
Information element name Status Description
Bearer service2CBearer service 2 required for the MO call, derived from the PLMN bearer capability 2 information received in the set-up request from the MS. For a SCUDIF call, one of bearer service 2 or teleservice 2 shall be present.
Teleservice2CTeleservice 2 required for the MO call, derived from the PLMN bearer capability 2 information received in the set-up request from the MS. For a SCUDIF call, one of bearer service 2 or teleservice 2 shall be present.
Up
4.2.1.1.2  Complete Callp. 10
Complete Call contains the following SCUDIF specific information elements:
Information element name Status Description
First service availabilityCShall be present for a MO SCUDIF call if the Bearer service or Teleservice is allowed; otherwise shall be absent.
Second service availabilityCShall be present for a MO SCUDIF call if the Bearer service 2 or Teleservice 2 is allowed; otherwise shall be absent.
Up

Up   Top   ToC