hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d4763978937007086749bc87bda933cc | 182 019 | 7.6.1.2 Unicast download delivery - CCF proxy redirect mode | The CCF proxy redirect delivery mode procedure is shown in figure 7.6.1.2.1. UE (1) Delivery initiation request (Download) CDF (2) Delivery initiation response (download) ETSI ETSI TS 182 019 V3.1.2 (2011-09) 47 Figure 7.6.1.2.1: Unicast download delivery procedure - proxy redirect mode The unicast download delivery pr... |
d4763978937007086749bc87bda933cc | 182 019 | 7.6.1.3 Unicast download delivery in CCF triangular proxy Mode | The CCF triangular proxy delivery mode procedure is shown in figure 7.6.1.3.1. UE CCF (1) Delivery initiation request (Download) CDF1 (2) Delivery initiation request (Download) (3) Delivery initiation Redirect (CDF2) CDF2 CDFn ………. (4) Delivery initiation request (Download) (2n-1) Delivery initiation Redirect (CDFn) . ... |
d4763978937007086749bc87bda933cc | 182 019 | 7.6.1.4 Unicast download delivery in redirect mode | The redirect mode procedure for unicast content download delivery is shown in figure 7.6.1.4.1. Figure 7.6.1.4.1: Unicast download delivery procedure - redirect mode UE CDNCF (2) Delivery request CCF (5) Delivery redirection response (3) Delivery redirection response (4) Delivery request (1) UE performs content selecti... |
d4763978937007086749bc87bda933cc | 182 019 | 7.6.2 Unicast download/downstream session initiation for IMS based IPTV | This clause describes the processing for a UE -initiated unicast download service described in clauses 8.18.1 and 8.18.2 of TS 182 027 [2]. The procedures for UE-initiated content download and SCF initiated content download service are included in this clause. Figure 7.6.2.1 outlines the different steps and messages ex... |
d4763978937007086749bc87bda933cc | 182 019 | 7.6.3 Unicast download/downstream initiation for NGN integrated IPTV | In general, the procedures for download/downstream initiation are same as clause 7.6.2 for either IPTV subsystem. Comparing the procedures in two IPTV subsystems, it is the SCF in the IMS based IPTV subsystem, and the "IPTV Control" entity in the NGN integrated IPTV subsystem, which provide initiation signalling with t... |
d4763978937007086749bc87bda933cc | 182 019 | 7.7 Termination procedures | This clause depicts the termination procedures involving the IPTV subsystem and CDN. Clause 7.7.1 gives the generic termination procedures that are applicable on either the query approach or service approach on CDN routing mechanism. Clause 7.7.2 gives the additional termination procedures of query approach on either I... |
d4763978937007086749bc87bda933cc | 182 019 | 7.7.1 Generic termination procedures | |
d4763978937007086749bc87bda933cc | 182 019 | 7.7.1.1 UE-initiated termination | The following sequence depicts the procedure for UE initiated termination for unicast streaming. Figure 7.7.1.1.1: UE-initiated termination 1) The UE initiates termination towards the IPTV subsystem. 2) The IPTV subsystem, in turn, initiates a content delivery termination towards the CCF, which in turn initiates a cont... |
d4763978937007086749bc87bda933cc | 182 019 | 7.7.1.2 IPTV subsystem-initiated termination | The following sequence depicts the procedure for IPTV subsystem initiated termination of unicast streaming. ETSI ETSI TS 182 019 V3.1.2 (2011-09) 52 UE IPTV Subsystem CDNCF CCF CDF 1. Termination Request/Response 2. Terminate the Content Delivery Figure 7.7.1.2.1: IPTV subsystem-initiated termination 1) The IPTV subsys... |
d4763978937007086749bc87bda933cc | 182 019 | 7.7.2 Additional termination procedures - query approach | |
d4763978937007086749bc87bda933cc | 182 019 | 7.7.2.1 CCF initiated termination - query approach | The following sequence depicts the procedure for CCF triggered termination of unicast streaming. Figure 7.7.2.1.1: CCF initiated termination 1) The CCF imitates content delivery termination towards the CDF. 2) The CCF announces to the IPTV subsystem that delivery is terminated. 3) The IPTV subsystem initiates the conte... |
d4763978937007086749bc87bda933cc | 182 019 | 7.7.2.2 CDF initiated termination - query approach | Figure 7.7.2.2.1: CDF initiated termination (query approach) 1) The CDF announces to the CCF that the content delivery is terminated. 2) The CCF announces to the IPTV subsystem that the content delivery is terminated. 3) The IPTV subsystem initiates the content delivery termination towards the CCF. 4) The CCF initiates... |
d4763978937007086749bc87bda933cc | 182 019 | 7.7.3.1 CCF initiated session termination - IMS-based service approach | The following sequence depicts the procedure for CCF triggered termination of unicast streaming using the service approach. ETSI ETSI TS 182 019 V3.1.2 (2011-09) 54 SCF CDNCF CCF CDF 3. Session Termination Request 2. Session Termination Request 1. Terminate the Content Delivery Session IMS Core UE 6. Session Terminatio... |
d4763978937007086749bc87bda933cc | 182 019 | 7.7.3.2 CDF initiated session termination - IMS-based service approach | SCF CDNCF CCF CDF 3. Session Termination Request 2. Session Termination Request 1. Announce Session Termination IMS Core UE 6. Session Termination and response 4. Session Termination Repsonse 5. Session Termination Repsonse 7. Terminate the Content Delivery Session Figure 7.7.3.2.1: CDF initiated session termination (s... |
d4763978937007086749bc87bda933cc | 182 019 | 7.7.3.4 SCF initiated session termination - IMS-based service approach | This is the SCF initiated session termination, the session termination request sent to CDN and UE by SCF. ETSI ETSI TS 182 019 V3.1.2 (2011-09) 56 Figure 7.7.3.4.1: SCF initiated session termination (service approach) 1) SCF sends session termination request to CDNCF to request to terminate the unicast streaming sessio... |
d4763978937007086749bc87bda933cc | 182 019 | 7.8 Content management procedures within CDN | This part describes the procedures for content ingestion and deployment in the CDN. |
d4763978937007086749bc87bda933cc | 182 019 | 7.8.1 Content ingestion Procedures | |
d4763978937007086749bc87bda933cc | 182 019 | 7.8.1.1 Procedures for pre-positioning | Figure 7.8.1.1.1: Content pre-positioning ETSI ETSI TS 182 019 V3.1.2 (2011-09) 57 1) The COF may be externally trigger to retrieve content. 2) The content is acquired by the COF. NOTE: How the COF acquires the content is out of scope. 3) COF issues a content ingestion notification to the ALF when a new media content h... |
d4763978937007086749bc87bda933cc | 182 019 | 7.8.1.2 Procedures for dynamic acquisition | Content ingestion through dynamic ingestion is covered in clause 7.1.2. |
d4763978937007086749bc87bda933cc | 182 019 | 7.8.2 Content deployment procedures | |
d4763978937007086749bc87bda933cc | 182 019 | 7.8.2.1 Receiver driven pre-positioned content deployment | This clause describes the procedures for content ingestion for within CDN when pre-positioning is triggered by the receiver. CDF CDNCF CCF 4. Content Deployment Request 6. Content Deployment Request ALF COF 3. CCF Selection 5. CDF Selection 1. CDNCF selection 7. Content Deployment Response 8. Content Deployment Respons... |
d4763978937007086749bc87bda933cc | 182 019 | 7.8.2.2 Sender driven pre-positioned content deployment | This clause describes the procedures for content deployment within the CDN when content pre-positioning is triggered by the sender. ETSI ETSI TS 182 019 V3.1.2 (2011-09) 59 Figure 7.8.2.2.1: Sender driven pre-positioned content deployment 1) ALF selects one or several CDNCF(s) to get the content. 2) ALF sends a content... |
d4763978937007086749bc87bda933cc | 182 019 | 7.9 Content replication within the CDN | The CDNCF periodically monitors the content usage within clusters and makes storage adjustments to enable high availability of CDN service. Content copies that are rarely requested during a given time range are removed from the CDF, while content that is frequently requested within a time range will be duplicated onto ... |
d4763978937007086749bc87bda933cc | 182 019 | 7.9.1 Duplication of content copy within cluster | CDNCF ALF CCF CDF-1 3. Duplicate Request 5. Duplicate Response 7. Content duplication notification 6. Update the Datebase CDF-2 4. Content Delivery 1. Trigger 2. CCF selects a CDF. Figure 7.9.1.1: Duplication of content copy within cluster 1) An (optional) external or internal trigger is sent to CCF for initiating the ... |
d4763978937007086749bc87bda933cc | 182 019 | 7.9.2 Duplication between two clusters under the same CDNCF | Figure 7.9.2.1: Duplication of content copy between two clusters under the same CDNCF 1) An (optional) external or internal trigger is sent to CDNCF for initiating the duplication of content copy. 2) The CDNCF (optionally) sends the metrics request to the CCF for acquiring the statistics of request for the content in a... |
d4763978937007086749bc87bda933cc | 182 019 | 7.9.3 Duplication between two clusters under different CDNCFs | Figure 7.9.3.1: Duplication of content copy between two clusters under different CDNCFs 1) An (optional) external or internal trigger is sent to CDNCF for initiating the duplication of content copy. 2) CDNCF-1 sends the CDNCF Query request to ALF seeking the CDNCFs that may respond a content request. 3) Based on the kn... |
d4763978937007086749bc87bda933cc | 182 019 | 7.9.4 Media Relay based unicast streaming delivery for IMS based IPTV | |
d4763978937007086749bc87bda933cc | 182 019 | 7.9.4.1 Content deployment & delivery flow by media relay between two clusters | Figure 7.9.4.1.1 provides an overview of the information flows for media relay based unicast streaming delivery flow among clusters. Figure 7.9.4.1.1: Content delivery flow by media relay among clusters ETSI ETSI TS 182 019 V3.1.2 (2011-09) 64 1) The sequence is triggered by an action from the user. The user requests u... |
d4763978937007086749bc87bda933cc | 182 019 | 7.9.4.2 Content delivery flow by media relay via centre cache | This clause gives two service flows for media relay based unicast streaming deliver flow via centre cache for PUSH or PULL respectively as depicted in figures 7.9.4.2.1 and 7.9.4.2.2. The centre cache can be a cloud network, a super server or a cluster. If the centre cache is constituted by a cluster, it will contain t... |
d4763978937007086749bc87bda933cc | 182 019 | 7.10 Procedures of content removal | The following clauses describe the procedures of content removal for CDN. |
d4763978937007086749bc87bda933cc | 182 019 | 7.10.1 Procedures for content removal CCF initiated | A CCF may be triggered and may choose to remove a content item, or some copies of this content from its cluster. ETSI ETSI TS 182 019 V3.1.2 (2011-09) 67 Figure 7.10.1.1: Content removal CCF initiated 1) CCF can be internally or externally triggered to remove copy(ies) of content. 2) When it is the last copy of the clu... |
d4763978937007086749bc87bda933cc | 182 019 | 7.10.2 Procedures for content removal CDNCF initiated | Figure 7.10.2.1: Content removal CDNCF initiated 1) An (optional) external or internal trigger is sent to CDNCF for initiating the deletion of content copy. 2) The CDNCF (optionally) sends the metrics request to the CCF acquiring the statistics of the content usage in a time range. 3) If step 2 occurs, the CCF returns ... |
d4763978937007086749bc87bda933cc | 182 019 | 7.10.3 Procedures for mandatory content removal COF initiated | This clause describes the procedures of content removal for CDN. A content item may need to be removed from the CDN in case of right violation for example (e.g. content reproducing a part of a movie without the allowance of the content owner). ETSI ETSI TS 182 019 V3.1.2 (2011-09) 69 CDNCF CCF CDF (3) Content Removal N... |
d4763978937007086749bc87bda933cc | 182 019 | 7.10.4 Procedures for COF content removal | This clause describes the procedures of content removal for COF. Content may need to be removed from the COF in case of space management. ETSI ETSI TS 182 019 V3.1.2 (2011-09) 70 (3) Content Removal Notification COF ALF (4) Content Removal response (2) Content Deletion (1) ExternalTrigger Figure 7.10.4.1: COF Content r... |
d4763978937007086749bc87bda933cc | 182 019 | 7.10.5 Procedures for content removal on CDF (optional procedure) | The call flow depicts the case when a CDF deletes content from its cache. CDNCF CCF CDF ALF (2) Content Removal Request (4) CCF initiated content removal (7.10.1) (1) CDF based internal triggers decides to delete a content (3) Content Removal Response Figure 7.10.5.1: CDF content removal The following is a description ... |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 1 Scope | ........................................................................................................................................................5 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 2 References | ................................................................................................................................................5 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 3 Definitions and abbreviations | ..................................................................................................................7 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 4 Introduction | ..............................................................................................................................................8 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 5 Network characteristics | ............................................................................................................................8 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 5.1 Characteristics of GSM PLMNs | ........................................................................................................................ 8 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 5.2 Characteristics of PSPDNs | ................................................................................................................................ 9 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 5.3 Characteristics of ISDN | ..................................................................................................................................... 9 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 5.4 Characteristics of the packet service provided by the PH | .................................................................................. 9 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 5.5 Characteristics of the packet service provided by a PH assuming the role of an AU or by X.32 | ...................... 9 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 6 Interworking classifications | .....................................................................................................................9 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 6.1 Service interworking | .......................................................................................................................................... 9 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 6.2 Network interworking | ........................................................................................................................................ 9 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 7 Network interworking scenarios | ............................................................................................................10 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 7.1 General | ............................................................................................................................................................. 10 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 7.2 Interworking through transit networks | ............................................................................................................. 10 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 7.3 Direct Interworking | .......................................................................................................................................... 11 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8 Basic packet mode service | .....................................................................................................................11 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.1 General | ............................................................................................................................................................. 11 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.2 Service provided by the GSM PLMN network | ................................................................................................ 12 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.3 Mobile originated calls | .................................................................................................................................... 12 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.3.1 Subscriber on home PLMN | ........................................................................................................................ 12 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.3.2 Subscriber on visited PLMN | ...................................................................................................................... 12 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.4 Mobile terminated calls | ................................................................................................................................... 14 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.4.1 Subscriber on home PLMN | ........................................................................................................................ 14 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.4.2 Subscriber on visited PLMN | ...................................................................................................................... 14 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.5 Mobile originated mobile terminated calls | ...................................................................................................... 14 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.6 Subscriber profiles | ........................................................................................................................................... 14 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 8.7 GSM bearer services quality of service | ........................................................................................................... 14 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9 Dedicated packet mode service | ..............................................................................................................15 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.1 General | ............................................................................................................................................................. 15 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.2 General application rules | ................................................................................................................................. 16 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.3 Specific application of rules for dedicated packet mode service | ..................................................................... 16 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.4 Mobile originated calls | .................................................................................................................................... 17 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.4.1 General | ....................................................................................................................................................... 17 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.4.2 Short code | .................................................................................................................................................. 18 |
df2d34ca0632e94d705eff08e29e31be | 129 006 | 9.5 Particular packet access functionality | .............................................................................................................. 18 Annex A: Change history......................................................................................................................19 History.......................................................... |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 1 Scope | ........................................................................................................................................................5 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 1.1 References | .......................................................................................................................................................... 5 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 1.2 Abbreviations | ..................................................................................................................................................... 5 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 2 General description | ..................................................................................................................................5 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 2.1 Scheduling Information | ..................................................................................................................................... 6 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3 Message format on BTS-MS Interface | ....................................................................................................6 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.1 General | ............................................................................................................................................................... 6 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.2 Format convention | ............................................................................................................................................. 7 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.2.1 Numbering convention | ................................................................................................................................. 7 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.2.2 Order of bit transmission | .............................................................................................................................. 7 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.3 Block content | ..................................................................................................................................................... 7 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.3.1 Block Type | ................................................................................................................................................... 7 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.4 SMSCB Message | ............................................................................................................................................... 8 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5 Schedule Message | .............................................................................................................................................. 8 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.1 Header | .......................................................................................................................................................... 9 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.2 New CBSMS Message Bitmap | .................................................................................................................... 9 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.3 New CBSMS Message Description | ............................................................................................................. 9 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.4 Other Message Descriptions | ....................................................................................................................... 10 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.5 Message description encoding | .................................................................................................................... 10 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.5.1 First transmission of an SMSCB within the Schedule Period | .............................................................. 10 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.5.2 Retransmission indication | ..................................................................................................................... 11 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.5.3 Free Message Slot, optional reading | ..................................................................................................... 11 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.5.4 Free Message Slot, reading advised | ...................................................................................................... 11 |
0541c1884e20c43182af33dfb675ffbe | 124 012 | 3.5.5.5 Reserved Codepoints | ............................................................................................................................ 11 Annex A (informative): Sample Implementation of SMSCB DRX Mode ................................................12 Annex B: Change history ......................................................... |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 1 Scope | ........................................................................................................................................................5 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 2 References | ................................................................................................................................................5 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 3 Definitions and abbreviations | ..................................................................................................................6 |
ca81f9f4b6a2eafbb9c7ec4387e66ce1 | 123 070 | 4 Introduction | ..............................................................................................................................................6 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.