B.3 Example information flows for a voicemail service
23.2183GPPIM call modelIP Multimedia (IM) session handlingRelease 17Stage 2TS
B.3.1 User out of coverage message recording
Figure B.3.1.1 shows a possible scenario of an Application Server, which acting as a terminating UA performs the function of a Voicemail Server in order to terminate a call and record a message on behalf of a UE that is out of coverage or powered off. The Application Server’s use of the MRF to record a message is not shown in this example.
An initial INVITE destined for a UE that is not currently IMS registered is forwarded to a S-CSCF. The Default Filter Criteria in the S-CSCF indicates that for the case of an unregistered user the INVITE request should be forwarded to the Voicemail and Announcement Server.
Upon receiving the INVITE request the Voicemail and Announcement Server determines that the destination UE has subscribed to the Voicemail Service (possibly by downloading some subscriber profile information via the Sh interface). The Voicemail and Announcement Server therefore in addition to playing an announcement to inform the caller that the called party is either powered off or out of coverage also informs the caller that he may leave a message for the called party.
The calling party leaves a message for the called party and then hangs up the call by sending a BYE request.
Figure B.3.1.1: Voicemail server records messages
Notes for figure B.3.1.1:
NOTE: For simplicity the 100 (Trying) response returned or received by the S-CSCF in reponse to requests is omitted from figure B.3.1.1.
1) INVITE request destined for an unregistered user is received at the S-CSCF.
2) Based on trigger point of the initial Filter Criteria S-CSCF proxies the INVITE request to the AS (Voicemail Server).
3 – 4) The AS starts the voicemail application and responds with a 183 (Session Progress) response containing SDP which is proxied back to the caller by the S-CSCF.
5 – 8) The caller responds with a PRACK request containing SDP, which the S-CSCF proxies to the AS and the AS responds with a 200 (OK) response containing SDP which the S-CSCF proxies back to the caller.
9) QOS establishment and resource reservation takes place.
10 – 13) After completing resource reservation the caller sends a UPDATE request containing SDP which is proxied by the S-CSCF to the AS which responds with a 200 (OK) response containing SDP which is proxied back to the caller by the S-CSCF.
14 – 15) The AS then sends a 200 (OK) response to the initial INVITE request which the S-CSCF proxies to the caller.
16 – 17) The caller returns an ACK request to the 200 (OK) response.
18) The AS plays an announcement using the session established indicating that the caller is powered off but that the caller may leave a message.
19) The caller leaves a message using the session established.
20 – 21) The caller hangs up by sending a BYE request which the S-CSCF proxies to the AS.
22 – 23) The AS responds with a 200 (OK) response, which the S-CSCF proxies back to the caller.
B.3.2 User IMS registers voice mail service plays back messages
Figure B.3.2.1 shows the scenario when the UE that has subscribed to a voicemail service with a feature enabled that contacts the user upon registration informing him of any recorded messages. The Application Server’s use of the MRF to play announcements and to select and play the recorded messages is not shown in this example.
The Filter Criteria downloaded by the S-CSCF indicates that a third party REGISTER request should be sent to the Voicemail Server. Upon receiving the third party registration of the UE, the Voicemail Server acting as an originating UA contacts the UE by sending an INVITE request to inform him that he has voicemail messages recorded while he was not registered.
The user listens to the messages played back by the voicemail server, (only streaming class QOS is required for this session) and then terminates the session with a BYE request.
Figure B.3.2.1: Upon registration voicemail server replays messages
Notes for figure B.3.2.1:
NOTE: For simplicity the 100 (Trying) response returned or received by the S-CSCF in reponse to requests is omitted from figure B.3.2.1.
1 – 4) The UE sends a REGISTER request to the S-CSCF which authenticates with a 401 (Unauthorized) response challenge with the authentication response being supplied in a second REGISTER request. The registration completes with a 200 (OK) response from the S-CSCF to the UE.
5 – 6) The S-CSCF downloads Filter Criteria for the UE from the HSS which indicates the S-CSCF should send a third party REGISTER request on behalf of the UE to an AS that performs a voicemail service. The AS responds to the REGISTER request with a 200 (OK) response.
7 – 8) The AS downloads subscriber data for the subscriber (possibly from the HSS via the Sh interface) that indicates that the subscriber has enabled a feature that has the voicemail application contact the subscriber upon registration to deliver recorded messages. The AS sends an INVITE request containing SDP for the UE to the S-CSCF which proxies it to the UE.
9 – 10) The UE responds with 183 (Session Progress) response containing SDP which the S-CSCF proxies to the AS.
11 – 14) The AS sends a PRACK request, which the S-CSCF proxies to the UE and the UE respond with a 200 (OK) response which the S-CSCF proxies to the AS.
15) QOS establishment and resource reservation takes place.
16 – 19) The AS sends an UPDATE request, which the S-CSCF proxies to the UE and the UE responds with a 200 (OK) response which the S-CSCF proxies to the AS.
20 – 21) The UE sends a 180 (Ringing) response indicating that it is alerting the user which the S-CSCF proxies to the AS.
22 – 25) The AS to indicate receipt of the 180 (Ringing) response sends a PRACK request which the S-CSCF proxies to the UE and the UE responds with a 200 (OK) response which the S-CSCF proxies to the AS.
26 – 27) When the subscriber answers the UE sends a 200 (OK) response to the initial INVITE request which the S-CSCF proxies to the AS.
28 – 29) The AS acknowledges the 200 (OK) response with an ACK request which the S-CSCF proxies to the UE.
30) The AS plays an announcement indicating the number of messages stored and then plays back the messages to the UE using the session established.
31 – 32) The UE hangs up by sending a BYE request, which the S-CSCF proxies to the AS.
33 – 34) The AS responds with a 200 (OK) response, which the S-CSCF proxies back to the UE.
Annex C (informative):
Example for Initial filter criteria triggering
This example applies both for UE-originating and UE-terminating procedures. But we assume this is a call UE-originating procedure. User has registered with the network. Its filter criteria and addresses of the assigned application servers have been downloaded to its S-CSCF during registration via Cx interface. Also, the application server specific data may have been downloaded via the Sh interface to the application server during registration.
Figure C.1: Initial Filter Criteria Triggering Example
There is a flow example in figure C.1:
In this example, two application servers are assigned to provide additional services to a subscriber and they are showed as AS1 and AS2 in this example.
1. User initiates a SIP session by sending a SIP initial request to its S-CSCF.
2. On receiving this request, the S-CSCF evaluates the SPTs and checks if they match the initial filter criteria X for AS1. If they match, the S-CSCF forwards this request to AS1.
3. The AS1 performs any needed service logic based on the Service Key and sends the SIP request possibly with service related modification back to the S-CSCF.
4.a On receiving the request from the AS, the S-CSCF evaluates the SPTs and checks if they match the initial filter criteria Y for AS2. If they match the S-CSCF forwards the request to the associated Application Server AS2.
4.b If the request doesn’t match any further filter criteria, the S-CSCF forwards this request to the next hop based on the route decision.
5.a The AS2 performs any needed service logic based on the Service Key and sends the SIP request possibly with service related modification back to the S-CSCF.
6.a The S-CSCF checks the request sent by AS2 and finds that no initial criteria is matched, then the S-CSCF forwards this request to next hop based on the route decision.
Annex D (informative):
Change history
|
Change history |
||||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
WG doc |
|
Nov 2000 |
N1-001300 |
First draft created. Presented to CN1meeting #14. |
||||||
|
21/11/00 |
N1-001352 |
V 0.1.0 created based on discussion in CN1#14. Additional clause on OSA API added. |
||||||
|
22/11/00 |
N1-001386 |
V 0.2.0 created based on discussion in CN1#14. The clause on scope modified. |
||||||
|
28/11/00 |
N1-001448 |
V 0.3.0 created based on discussion in CN1/SA2 joint meeting. The title modified. |
||||||
|
Jan 2001 |
N1-010069 NJ-010102 |
V0.3.1 created. Specification number TS 23.218 allocated to TS 23.cde. |
||||||
|
16/1/01 |
NJ-010106 |
V0.4.0 created. Clause 8 on OSA API updated to include the proposal in NJ-010104 agreed at joint CN1/2/4 meeting on 23.218. |
||||||
|
Mar 2001 |
N1-010762 |
V0.5.0 created. Clause 6.5 updated to include the proposal in NJ-010117 agreed at the joint CN1/2/3/4 Feb meeting in Sophia. Reference to Visited Network updated. |
||||||
|
Jun 2001 |
N1-010981 |
V0.5.1 created. Informative Annex B created containing N1-010749 agreed at Joint CN1/2/3/4 meeting in Puerto Rico. |
||||||
|
Aug 2001 |
N1-011090 |
V0.5.2 created. Section 5 updated to include the proposals in N1-010982, N1-011013 and N1-011043; Section 6 updated to include the proposals in N1-011044 and N1-011045, agreed at CN1#18 and joint CN1/2/3/4 meetings in Dresden. |
||||||
|
Sep 2001 |
N1-011365 |
V0.6.0 created. Document layout reorganized and content updated to conform to proposal in N1-011277; Section 6 and Section 9 updated to include the proposals in N1-011342, agreed at CN1#19 meeting in Helsinki. |
||||||
|
Oct 2001 |
N1-011522 |
V.0.7.0 created. Appendix B.1 added based on N1-011423 agreed at CN1#19bis meeting in Sophia Antipolis |
||||||
|
Oct 2001 |
N1-011707 |
V.0.8.0 created using Tdocs: |
0.7.0 |
0.8.0 |
||||
|
Nov 2001 |
N1-011867 |
V.0.9.0 created using Tdocs: |
0.8.0 |
0.9.0 |
||||
|
Dec 2001 |
NP-010640 N1-020033 |
V.1.0.0 created using Tdocs: |
0.9.0 |
1.0.0 |
||||
|
Jan 2002 |
N1-020343 |
V.1.1.0 created using Tdocs: N1-020035, N1-020036, N1-020069, N1-020071 N1-020072, N1-020107, N1-020109, N1-020110, N1-020114, N1-020115 N1-020116, N1-020119 N1-020137, N1-020153, N1-020156, N1-020164 agreed at CN1 SIP Adhoc 0102 in Phoenix. |
1.0.0 |
1.1.0 |
||||
|
Feb 2002 |
N1-020552 |
V.1.2.0 created using Tdocs: N1-020231, N1-020385, N1-020387, N1-020392, N1-020393, N1-020448, N1-020450, N1-020451, N1-020452, N1-020453 agreed at CN1#22 in Sophia Antipolis, and corrected implementation error of N1-020156. |
1.1.0 |
1.2.0 |
||||
|
Feb 2002 |
V.2.0.0 created using Tdocs: N1-020607, N1-020620, N1-020633, N1-020634, N1-020637, N1-020653, N1-020661, N1-020662, N1-020667 agreed at CN1#22 bis in Oulu. |
1.2.0 |
2.0.0 |
|||||
|
Mar 2002 |
Editorial clean-up by ETSI/MCC. |
2.0.0 |
2.0.1 |
|||||
|
Mar 2002 |
TSG CN#15 |
NP-020047 |
The draft was approved and decided to be ‘frozen’, and 3GPP TS 23.218 was then to be issued in Rel-5 with the needed new RFC numbers allocated in NP-020134 incorporated. |
2.0.1 |
5.0.0 |
|||
|
Jun 2002 |
NP-16 |
NP-020226 |
002 |
3 |
HSS providing to the S-CSCF the subset of the relevant end user profile |
5.0.0 |
5.1.0 |
N1-020972 |
|
Jun 2002 |
NP-16 |
NP-020226 |
003 |
10 |
Clarification on SPI related text |
5.0.0 |
5.1.0 |
N1-021405 |
|
Jun 2002 |
NP-16 |
NP-020226 |
004 |
4 |
Passing charging correlation information |
5.0.0 |
5.1.0 |
N1-021423 |
|
Jun 2002 |
NP-16 |
NP-020226 |
006 |
1 |
Correction of terminology in 23.218 regarding Offer-counter offer answer |
5.0.0 |
5.1.0 |
N1-020951 |
|
Jun 2002 |
NP-16 |
NP-020226 |
012 |
5 |
Update of the S-CSCF AS relationship, for REGISTER |
5.0.0 |
5.1.0 |
N1-021425 |
|
Jun 2002 |
NP-16 |
NP-020226 |
014 |
1 |
User profile filter criteria updates |
5.0.0 |
5.1.0 |
N1-021384 |
|
Jun 2002 |
NP-16 |
NP-020226 |
015 |
1 |
Add references for Sh and Si interfaces |
5.0.0 |
5.1.0 |
N1-021385 |
|
Jun 2002 |
NP-16 |
NP-020226 |
016 |
1 |
SIP Application Server acting as a Gatewas to an external Application Server; and OSA API usage. |
5.0.0 |
5.1.0 |
N1-021404 |
|
Jun 2002 |
NP-16 |
NP-020226 |
017 |
1 |
Clarification to Handling of IP multimedia registration for barred public user identities |
5.0.0 |
5.1.0 |
N1-021424 |
|
Jun 2002 |
NP-16 |
NP-020226 |
019 |
Correction of COMET to UPDATE in 23.218 |
5.0.0 |
5.1.0 |
N1-021252 |
|
|
Sep 2002 |
NP-17 |
NP-020373 |
021 |
1 |
Service profiles and implicitly registered public user identities |
5.1.0 |
5.2.0 |
N1-021828 |
|
Sep 2002 |
NP-17 |
NP-020373 |
022 |
2 |
Clarification on specialized charging server |
5.1.0 |
5.2.0 |
N1-021859 |
|
Sep 2002 |
NP-17 |
NP-020373 |
025 |
1 |
Clarification on location information for IMS |
5.1.0 |
5.2.0 |
N1-021829 |
|
Sep 2002 |
NP-17 |
NP-020373 |
026 |
1 |
Proposed change of term SPI to SPT |
5.1.0 |
5.2.0 |
N1-021830 |
|
Sep 2002 |
NP-17 |
NP-020373 |
027 |
1 |
Support of originating requests from Application Servers |
5.1.0 |
5.2.0 |
N1-021831 |
|
Dec. 2002 |
NP-18 |
NP-020552 |
029 |
1 |
Clarification on CCF/ECF addresses |
5.2.0 |
5.3.0 |
N1-022142 |
|
Dec. 2002 |
NP-18 |
NP-020553 |
030 |
3 |
Clarification on MRFP reference point |
5.2.0 |
5.3.0 |
N1-022468 |
|
Dec. 2002 |
NP-18 |
NP-020552 |
031 |
1 |
Support of originating requests from Application Servers |
5.2.0 |
5.3.0 |
N1-022144 |
|
Dec. 2002 |
NP-18 |
NP-020552 |
033 |
Addition of Request-URI as SPT |
5.2.0 |
5.3.0 |
N1-022297 |
|
|
Dec. 2002 |
NP-18 |
NP-020552 |
034 |
1 |
Clarifications on Annex C (Informative) |
5.2.0 |
5.3.0 |
N1-022469 |
|
Dec. 2002 |
NP-18 |
NP-020552 |
038 |
1 |
Clarification to use of Service Information |
5.2.0 |
5.3.0 |
N1-022475 |
|
Mar 2003 |
NP-19 |
NP-030045 |
040 |
2 |
Clarification on Sh interface for charging purposes |
5.3.0 |
5.4.0 |
N1-030309 |
|
Mar 2003 |
NP-19 |
NP-030046 |
042 |
Correction related to implicit public user identities in third party REGISTER |
5.3.0 |
5.4.0 |
N1-030197 |
|
|
Jun 2003 |
NP-20 |
NP-030272 |
043 |
5 |
Correction on Handling of MO request |
5.4.0 |
5.5.0 |
N1-030943 |
|
Jun 2003 |
NP-20 |
NP-030272 |
044 |
1 |
Corrections regarding SPTs and Filter Criteria handling on REGISTER request |
5.4.0 |
5.5.0 |
N1-030516 |
|
Jun 2003 |
NP-20 |
NP-030272 |
046 |
1 |
Clarifications on SPT. |
5.4.0 |
5.5.0 |
N1-030517 |
|
Jun 2003 |
NP-20 |
NP-030272 |
048 |
Service Key Clarification |
5.4.0 |
5.5.0 |
N1-030663 |
|
|
Jun 2003 |
NP-20 |
NP-030272 |
051 |
1 |
S-CSCF behavior correction to enable call forwarding |
5.4.0 |
5.5.0 |
N1-030855 |
|
Jun 2003 |
NP-20 |
NP-030272 |
055 |
1 |
Filtering of unknown header fields and header parameters |
5.4.0 |
5.5.0 |
N1-030924 |
|
Sept 2003 |
NP-21 |
NP-030411 |
057 |
Removal of Incorrect Information |
5.5.0 |
5.6.0 |
N1-031070 |
|
|
Dec 2003 |
NP-22 |
NP-030475 |
053 |
3 |
Flow number corrections in Annex B |
5.6.0 |
5.7.0 |
N1-031630 |
|
Dec 2003 |
NP-22 |
NP-030482 |
059 |
Corrections on charging specification number |
5.7.0 |
6.0.0 |
N1-031468 |
|
|
Mar 2004 |
NP-23 |
NP-040032 |
064 |
1 |
Dh interface |
6.0.0 |
6.1.0 |
N1-040158 |
|
Mar 2004 |
NP-23 |
NP-040032 |
066 |
2 |
Initiating Back to Back User Agent |
6.0.0 |
6.1.0 |
N1-040472 |
|
Sep 2004 |
NP-25 |
NP-040384 |
69 |
IFC process termination at R-URI change |
6.1.0 |
6.2.0 |
N1-041440 |
|
|
Sep 2004 |
NP-25 |
NP-040384 |
70 |
1 |
Third party registration optimization |
6.1.0 |
6.2.0 |
N1-041562 |
|
Mar 2005 |
NP-27 |
NP-050069 |
76 |
Filter criteria matching and generation of third-party REGISTER request for network-initiated deregistration |
6.2.0 |
6.3.0 |
N1-050223 |
|
|
Mar 2005 |
NP-27 |
NP-050073 |
072 |
|
Resolution of references to 24.228 |
6.2.0 |
6.3.0 |
N1-050061 |
|
Mar 2005 |
NP-27 |
NP-050073 |
074 |
1 |
Default handling |
6.2.0 |
6.3.0 |
N1-050288 |
|
Dec 2005 |
CT-30 |
CP-050550 |
079 |
Mobile originated request unregistered |
6.3.0 |
7.0.0 |
C1-051428 |
|
|
Mar 2006 |
CT-31 |
CP-060160 |
0080 |
2 |
Change of originating and terminating terminal terminology |
7.0.0 |
7.1.0 |
|
|
Mar 2006 |
CT-31 |
CP-060124 |
0081 |
1 |
Editorial corrections |
7.0.0 |
7.1.0 |
C1-060122 |
|
Mar 2006 |
CT-31 |
CP-060124 |
0082 |
– |
Correction for the description of the contents of the clauses |
7.0.0 |
7.1.0 |
C1-060409 |
|
Jun 2006 |
CT-32 |
CP-060274 |
0086 |
1 |
Amend the playing announcement call flow |
7.1.0 |
7.2.0 |
C1-061081 |
|
Jun 2006 |
CT-32 |
CP-060262 |
0085 |
1 |
3Rd party registratin clarification |
7.1.0 |
7.2.0 |
C1-061005 |
|
Sept 2006 |
CT-33 |
CP-060466 |
0089 |
2 |
Impact of GRUU on Service Control in 23.218 |
7.2.0 |
7.3.0 |
C1-061364 |
|
Sept 2006 |
CT-33 |
CP-060468 |
0090 |
1 |
Clarification of Cases of Downloading iFC to S-CSCF |
7.2.0 |
7.3.0 |
C1-061704 |
|
Sept 2006 |
CT-33 |
CP-060468 |
0091 |
1 |
S-CSCF handling of terminations when AS modifies the Req-URI |
7.2.0 |
7.3.0 |
C1-061760 |
|
Oct 2006 |
Version 7.3.1 created by MCC to corrrect styles |
7.3.0 |
7.3.1 |
|||||
|
Nov 2006 |
CP-060660 |
0092 |
3 |
Introduction of communication service concept in TS 23218 |
7.3.1 |
7.4.0 |
C1-062521 |
|
|
Mar 2007 |
CT-35 |
CP-070153 |
0094 |
1 |
The IMS Communication sevice identifier can be included in the SIP response message |
7.4.0 |
7.5.0 |
C1-070559 |
|
Jun 2007 |
CT-36 |
CP-070383 |
0095 |
6 |
IMS Communication Service ID |
7.5.0 |
7.6.0 |
C1-071477 |
|
Jun 2007 |
CT-36 |
CP-070387 |
0097 |
1 |
Dynamic Service Activation Info |
7.5.0 |
7.6.0 |
C1-070977 |
|
Sep 2007 |
CT-37 |
CP-070586 |
0100 |
2 |
Additions in TS 23.218 due to ICSI/IARI |
7.6.0 |
7.7.0 |
C1-072182 |
|
Sep 2007 |
CT-37 |
CP-070586 |
0101 |
2 |
Completing 23.218 ICSI procedures |
7.6.0 |
7.7.0 |
C1-072160 |
|
Sep 2007 |
Correction in History table (new version column) done by MCC |
7.7.0 |
7.7.1 |
|||||
|
Dec 2007 |
CT-38 |
CP-070806 |
0104 |
3 |
Completing 23.218 ICSI text |
7.7.1 |
7.8.0 |
C1-073100 |
|
Dec 2007 |
CT-38 |
CP-070810 |
0103 |
1 |
Correction of request handling in terminating unregistered case |
7.8.0 |
8.0.0 |
C1-072664 |
|
Dec 2007 |
CT-38 |
CP-070810 |
0102 |
1 |
Enabling service triggering after call forwarding |
7.8.0 |
8.0.0 |
C1-072662 |
|
Mar 2008 |
CT-39 |
CP-080140 |
0105 |
2 |
Addition of other access network types. |
8.0.0 |
8.1.0 |
C1-080415 |
|
Jun 2008 |
CT-40 |
CP-080418 |
0108 |
3 |
B2BUA AS influence of filter criteria evaluation |
8.1.0 |
8.2.0 |
C1-082032 |
|
Jun 2008 |
CT-40 |
CP-080365 |
0111 |
1 |
Cr interface description |
8.1.0 |
8.2.0 |
C1-081341 |
|
Jun 2008 |
CT-40 |
CP-080354 |
0113 |
1 |
Editorial changes to subclauses 6.4 and 6.5 |
8.1.0 |
8.2.0 |
C1-082026 |
|
Jun 2008 |
CT-40 |
CP-080344 |
0116 |
– |
Correction of GRUU references |
8.1.0 |
8.2.0 |
C1-081797 |
|
Sep 2008 |
CT-41 |
CP-080536 |
0117 |
2 |
Enhancement of Filter Criteria to Include Incoming Register in Third Party Register |
8.2.0 |
8.3.0 |
C1-083098 |
|
Sep 2008 |
CT-41 |
CP-080537 |
0118 |
1 |
MRB |
8.2.0 |
8.3.0 |
C1-083361 |
|
Dec 2008 |
CT-42 |
CP-080854 |
0120 |
Cr interface addition to architecture diagram |
8.3.0 |
8.4.0 |
C1-084751 |
|
|
Dec 2008 |
CT-42 |
CP-080854 |
0121 |
Media example fixes |
8.3.0 |
8.4.0 |
C1-084753 |
|
|
Dec 2008 |
CT-42 |
CP-080873 |
0122 |
Enhancement of Filter Criteria to include final response to Incoming Register in Third Party Register |
8.3.0 |
8.4.0 |
C1-085056 |
|
|
Dec 2008 |
CT-42 |
Editorial cleanup by MCC |
8.3.0 |
8.4.0 |
||||
|
Dec 2009 |
CT-46 |
CP-090894 |
0127 |
Updating of GRUU references |
8.4.0 |
8.5.0 |
C1-094829 |
|
|
Dec 2009 |
CT-46 |
CP-090923 |
0124 |
2 |
Allowing direct routing between AS and MRFC |
8.5.0 |
9.0.0 |
C1-094735 |
|
Dec 2009 |
CT-46 |
CP-090936 |
0125 |
Registration of IMS media plane security capabilities |
8.5.0 |
9.0.0 |
C1-094418 |
|
|
Mar 2010 |
CT-47 |
CP-100110 |
0129 |
Resolve EN on terminating request handling |
9.0.0 |
9.1.0 |
C1-100467 |
|
|
Jun 2010 |
CT-48 |
CP-100366 |
0130 |
Updating references to OMA specifications |
9.1.0 |
9.2.0 |
C1-101714 |
|
|
Mar 2011 |
CT-51 |
Upgrade to Rel-10 |
9.2.0 |
10.0.0 |
||||
|
Sep 2011 |
CT-53 |
CP-110693 |
0132 |
2 |
Identifying Application Server capabilities on the signaling route |
10.0.0 |
11.0.0 |
C1-113592 |
|
Sep 2011 |
CT-53 |
CP-110688 |
0133 |
2 |
Adding MRB between AS and MRFC |
10.0.0 |
11.0.0 |
C1-113725 |
|
Dec 2011 |
CT-54 |
CP-110889 |
0137 |
1 |
Border control elements and the MRB |
11.0.0 |
11.1.0 |
C1-115156 |
|
Dec 2011 |
CT-54 |
CP-110889 |
0138 |
MRB interfaces |
11.0.0 |
11.1.0 |
C1-114812 |
|
|
Mar 2012 |
CT-55 |
CP-120119 |
0136 |
3 |
AS selection of MRF resources |
11.1.0 |
11.2.0 |
C1-120753 |
|
Mar 2012 |
CT-55 |
CP-120119 |
0139 |
1 |
Revisions to Rc interface |
11.1.0 |
11.2.0 |
C1-120754 |
|
Jun 2012 |
CT-56 |
CP-120320 |
0141 |
Editorial correction in border control concepts |
11.2.0 |
11.3.0 |
C1-120991 |
|
|
Jun 2012 |
CT-56 |
CP-120307 |
0143 |
Correction of reference to TS 33.328 |
11.2.0 |
11.3.0 |
C1-121958 |
|
|
Jun 2012 |
CT-56 |
CP-120320 |
0144 |
1 |
Access to MRB and to MRF resources by entities other than an application server |
11.2.0 |
11.3.0 |
C1-122241 |
|
Jun 2012 |
CT-56 |
CP-120316 |
0145 |
3 |
Creation of a new functional entity to support application servers in the enterprise |
11.2.0 |
11.3.0 |
C1-122479 |
|
Jun 2012 |
CT-56 |
CP-120320 |
0146 |
1 |
Correction of MRF and MRB related interfaces |
11.2.0 |
11.3.0 |
C1-122242 |
|
Jun 2012 |
CT-56 |
CP-120320 |
0147 |
MRB to MRB operation |
11.2.0 |
11.3.0 |
C1-122140 |
|
|
Sep 2012 |
CT-57 |
CP-120597 |
0148 |
1 |
Usage of visited network MRB address when allocating MRF resources |
11.3.0 |
11.4.0 |
C1-123276 |
|
Sep 2012 |
CT-57 |
CP-120591 |
0149 |
Addressing an editor’s note relating to interface naming |
11.3.0 |
11.4.0 |
C1-122926 |
|
|
Sep 2012 |
CT-57 |
CP-120591 |
0150 |
1 |
Addressing an editor’s note supported functionality for the ISC gateway function |
11.3.0 |
11.4.0 |
C1-123268 |
|
Sep 2012 |
CT-57 |
CP-120597 |
0152 |
Addressing an editor’s note relating to resources in multiple VPLMNs |
11.3.0 |
11.4.0 |
C1-122934 |
|
|
Sep 2012 |
CT-57 |
CP-120597 |
0153 |
1 |
Addressing an editor’s note relating to border control functions on Mr, Mr’ and Cr interfaces |
11.3.0 |
11.4.0 |
C1-123278 |
|
Sep 2012 |
CT-57 |
CP-120597 |
0154 |
Addressing an editor’s note relating to border control concepts for the Rc interface |
11.3.0 |
11.4.0 |
C1-122936 |
|
|
Sep 2012 |
CT-57 |
CP-120597 |
0155 |
Addressing an editor’s note relating to IBCF usage on media resource allocation architecture |
11.3.0 |
11.4.0 |
C1-122970 |
|
|
Sep 2012 |
CT-57 |
CP-120591 |
0157 |
1 |
Functionalities of the IBCF on the ISC interface |
11.3.0 |
11.4.0 |
C1-123269 |
|
Dec 2012 |
CT-58 |
CP-120804 |
0158 |
1 |
Recover screened information |
11.4.0 |
11.5.0 |
C1-124096 |
|
Dec 2012 |
CT-58 |
CP-120809 |
0160 |
2 |
Transit Function – ISC alternative |
11.4.0 |
11.5.0 |
C1-124938 |
|
Dec 2012 |
CT-58 |
CP-120818 |
0162 |
1 |
Transferring IMS CAMEL Data with Sh Protocol |
11.5.0 |
12.0.0 |
C1-124878 |
|
Mar 2013 |
CT-59 |
CP-130127 |
0168 |
1 |
Interface IM-SSF / HSS with Diameter |
12.0.0 |
12.1.0 |
C1-130505 |
|
Jun 2013 |
CT-60 |
CP-130249 |
0170 |
1 |
Renaming the Mz reference point to be Mf |
12.1.0 |
12.2.0 |
C1-131618 |
|
Sep 2013 |
CT-61 |
CP-130513 |
0171 |
1 |
Updating TS 23.218 to RFC 6665 |
12.2.0 |
12.3.0 |
C1-133235 |
|
Mar 2015 |
CT-67 |
CP-150082 |
0175 |
1 |
Correction of Mf reference point name in figure |
12.3.0 |
13.0.0 |
C1-150598 |
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
CT-75 |
Upgrade to Rel-14 |
14.0.0 |
||||
|
2018-06 |
SA-80 |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
|
2020-07 |
SA-88e |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
|
2022-03 |
SA-95e |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |