hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.1.1 Disabling of IP Header Compression Per Connection | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.1.1.0 General | A backwards-compatible RNC feature is offered that permits IP header compression to be enabled/disabled per connection at the UE for the purposes of interoperability and troubleshooting. The feature permits support of an AT command option in ETSI TS 127 007 [7] (clause 10.1.1, AT CGDCONT) which cannot otherwise be util... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.1.1.1 RNC Behaviour (Mandatory) | For a bi-directional AM or UM connection the RNC will not compress IP headers in the forward direction until it has received an IP header compressed PDCP PDU in the uplink direction. When the RNC has not yet started its compressor, it will send IP headers uncompressed with the PDCP header byte having the value 0. The f... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.1.1.2 UE Behaviour (Optional) | The current and default behaviour will be to compress IP headers in the return direction if enabled by PDCPInfoParam AVP signalling. Optionally, the UE may implement a configuration parameter which forces the UE to send PDCP PDUs with uncompressed IP headers in a specified Packet Data Protocol (PDP) context. As a conse... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.1.2 PDCP Behaviour for operation with BM domain | The PDCP behaviour for operation with the BM domain is simplified in that IP Header compression is disabled in the PDCP layer, and takes place within the TFT layer. The functionality of the PDCP entity for operation with the BM domain is to map the TFT Filter ID to the PDCP-Info field at the interface to the Bearer Con... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2 TFT Handler | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.1 UE User Plane Protocol Stack Overview | A more detailed presentation of the BM domain-specific user-plane of the UE protocol stack, showing the references that are utilized at each layer is shown in Figure 7.2. ETSI ETSI TS 102 744-3-9 V1.1.1 (2015-10) 37 Figure 7.2: User Plane BM Domain - UE Protocol Stack The TFT Handler, while having generic forwarding fu... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2 TFT Based Compression Approach | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.0 General | For Secondary PDP Contexts and MBMS contexts, the compressor state for each Traffic Filter Template shall be as described in this clause. It should be noted that in principle this approach could be combined with other compression algorithms such as RFC 2507 [i.1]/RFC 2508 [i.3] or RFC 3095 [i.2]. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1 IPv4 operation | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.1 IP Version | The compressor shall delete the IP version. The decompressor shall reinstate the IP version. Interface 11 Bearer Control (tBCnID) Bearer Connection (BCnID) 61 Comp/ Decomp TFT Handler PId Decomp ressor Compre ssor 53 52 Primary 05 129 12 62 Comp/ Decomp Secondary 06 Decomp ressor Compre ssor MBMS PId 01 02 03 04 01 (NS... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.2 IHL | If the Internet Header Length (IHL) has a value of 4, then it shall be deleted by the compressor, and reinstated by the decompressor. If the value is not equal to 4 then the packet shall be sent uncompressed. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.3 ToS (/DSCP) | If the value is specified in the TFT then it shall be deleted by the compressor and reinstated by the decompressor using the specified value. Otherwise the ToS field shall be present. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.4 Total Length | This field is deleted by the compressor and reinstated by the decompressor - it shall be derived from the link layer packet length. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.5 Identification | This field should normally always be sent. This is defined as DELTA for Protocol = TCP, else RANDOM. TCP shall not be used for Multimedia Broadcast Multicast Services (MBMS). For multicast services, deletion and reinstatement of Identification should take place for non-fragmented compressed packets. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.6 Flags/Fragment Offset | If Flags = 0, then Flags and Fragment offset are deleted by the compressor and reinstated by the decompressor. If Flags not equal to zero, then packet is sent uncompressed. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.7 TTL | TTL (Time To Live) is indicated as being 'NOCHANGE' in RFC 2507 [i.1]. This can be done with a full negotiated compressor state. However deletion and reinstatement of a fixed value (e.g. 255) while considered an option, it is potentially problematic and requires further analysis. Typically the UE will be at one end of ... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.8 Protocol | If specified in the TFT, then this shall be deleted by the compressor and reinstated by the decompressor. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.9 Header Checksum | This shall be deleted by the compressor and recalculated by the decompressor. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.10 Source Address | In the uplink direction the compressor shall delete the Source Address, and the PDP address shall be reinstated by the Decompressor. In the downlink direction, if the Remote IP Address Netmask specified in the TFT is 255.255.255.255, then the Source Address shall be deleted by the compressor, and the Remote IP Address ... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.11 Destination Address | In the downlink direction the compressor shall delete the Source Address. For unicast PDP contexts the decompressor shall reinstate the PDP address. For MBMS contexts, the MBMS address shall be reinstated by the decompressor. In the uplink direction, if the Remote IP Address Netmask is 255.255.255.255, then the destina... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.12 Source Port | In the uplink direction, if the Local Port is specified within the TFT as a single value, then this shall be deleted by the compressor and reinstated by the decompressor. If a Local Port Range is specified, then the field width shall be determined by the range value, for instance if the Local Port Range is specified as... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.13 Destination Port | In the uplink direction, if the Remote Port is specified within the TFT as a single value, then this shall be deleted by the compressor and reinstated by the decompressor. If a Remote Port Range is specified, then the field width shall be determined by the range value, for instance if the Remote Port Range is specified... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.14 UDP Length | If the Protocol Type is specified as UDP, and the packet is not fragmented then this field shall be deleted by the compressor and derived by the decompressor from the link layer length information. If the packet is fragmented it shall not be compressed, and therefore the UDP length shall remain intact. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.15 UDP CRC | This value shall be deleted by the compressor and recalculated by the decompressor, noting that the packet will be discarded in the link layer if the Media Access Control (MAC) layer CRC or the link layer reassembly mechanism fails. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.16 SPI | If specified within the TFT, the compressor shall delete the SPI (Security Parameter Index) and the decompressor shall reinstate the SPI. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.1.17 Padding | The compressor shall pad the compressed header to an octet boundary using padding bits which shall be zeros. The decompressor shall ignore the padding bits. Note that padding occurs prior immediately before UDP payload. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2 IPv6 operation | |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.1 IP Version | The compressor shall delete the IP version. The decompressor shall reinstate the IP version. ETSI ETSI TS 102 744-3-9 V1.1.1 (2015-10) 40 |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.2 Traffic Class | If specified by the TFT, the compressor shall delete the Traffic Class field, and the decompressor shall reinstate the Traffic Class field. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.3 Flow Label | If specified by the TFT, the compressor shall delete the Flow Label field, and the decompressor shall reinstate the Flow Label field. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.4 Payload Length | This field is deleted by the compressor and reinstated by the decompressor - it shall be derived from the link layer packet length. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.5 Next Header | If equal to the value specified in the TFT, then this field shall be deleted by the compressor and reinstated by the decompressor. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.6 Hop Limit | This field shall always be sent. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.7 Source Address | If the source IP address mask is FF::FF, then the source address is deleted by the compressor, and the source address is reinserted by the decompressor. For any other value of source IP address mask, only the non-static elements of the address are sent (i.e. the value that is not masked) by the compressor. The decompre... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.8 Destination Address | If the destination IP address mask is FF::FF, then the destination address is deleted by the compressor, and the destination address is reinserted by the decompressor. For any other value of destination IP address mask, only the non-static elements of the address are sent (i.e. the value that is not masked) by the comp... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.9 Source Port | If the Source Port is specified within the TFT as a single value, then this shall be deleted by the compressor and reinstated by the decompressor. If a source port range is specified, then the field width shall be determined by the range value, for instance if the source port range is specified as 5 060 to 5 063, then ... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.10 Destination Port | If the Destination Port is specified within the TFT as a single value, then this shall be deleted by the compressor and reinstated by the decompressor. If a destination port range is specified, then the field width shall be determined by the range value, for instance if the destination port range is specified as 5 060 ... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.11 UDP Length | If the Protocol Type is specified as UDP, and the packet is not fragmented then this field shall be deleted by the compressor and derived by the decompressor from the link layer length information. If the packet is fragmented it shall not be compressed, and therefore the UDP length shall remain intact. ETSI ETSI TS 102... |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.12 UDP CRC | This value shall be deleted by the compressor and recalculated by the decompressor, noting that the packet will be discarded in the link layer if the MAC layer CRC or the link layer reassembly mechanism fails. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.13 SPI | If specified within the TFT, the compressor shall delete the SPI and the decompressor shall reinstate the SPI. |
326f5e82591253bdfba751b668f0b9aa | 102 744-3-9 | 7.2.2.2.14 Padding | The compressor shall pad the compressed header to an octet boundary using padding bits which shall be zeros. The decompressor shall ignore the padding bits. ETSI ETSI TS 102 744-3-9 V1.1.1 (2015-10) 42 Annex A (normative): Circuit Switched Call type - Supported Bearer Capability Information Element A.1 Introduction The... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 1 Scope | The present document defines the operation of Multimedia Broadcast Multicast Services (MBMS) in support of efficient delivery of IP multicast traffic across the Family SL satellite radio interface. This includes extensions to the Non-Access Stratum (NAS) Layer peer-to-peer interface (defined in ETSI TS 124 007 [1] and ... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 2 References | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 3 Abbreviations | For the purposes of the present document, the abbreviations in clause 3 of ETSI TS 102 744-1-4 [3] apply. |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 4 Introduction | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 4.1 Network Architecture | Figure 4.1 presents the network architecture of this multi-part deliverable (Release 1) illustrating the entities which are responsible for the provision of Multimedia Broadcast Multicast Services (MBMS). This includes: • the Broadcast Multicast Service Node (BMSN), which contains the agents for the Non-Access Stratum ... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 4.2 Protocol Architecture | The function of the satellite radio interface NAS Layer is to provide support to the IP User Plane Handler (UPH). The NAS Layer uses the services provided by the Adaptation Layer (AL). Figure 4.2 illustrates the position of the NAS Layer within the Family SL air interface protocol stack. An overview of the radio interf... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5 MBMS NAS Layer Operations | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.1 MBMS Mobility Management procedures | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.1.1 GPRS Attach to BM Domain | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.1.1.1 Successful GPRS Attach Procedure | The GPRS Mobility Management Procedures and Security Mode Procedures which operate towards the PS domain are utilized for the BM Domain. If a combined PS/CS Attach procedure is employed to minimize signalling across the radio interface, then the GMM signalling is directed to the PS domain and the mobility management st... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.1.1.2 Unsuccessful GPRS Attach Procedure | An unsuccessful GPRS Attach procedure may occur for a number of reasons, including: 1) The IMSI for the UE is not provisioned for operation with the BM domain; 2) Security mode procedures fail; 3) Communications within the Access Stratum are unreliable. Until the GPRS Attach Procedure towards the BM succeeds (or a Comb... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.1.2 GPRS Detach | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.1.2.0 General | The GPRS Detach procedure may be initiated by either the User Equipment or the Core Network to remove the mobility management association between the UE and the CN. |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.1.2.1 CN-initiated GPRS Detach Request | If the UE was attached to multiple domains using a combined Attach procedure, a GPRS Detach procedure initiated by any of the Core Network domains will result in loss of connectivity between the UE and all Core Network Domains, including the BM Domain. If the UE utilized a specific Attach procedure towards the BM domai... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.1.2.2 UE-initiated GPRS Detach Request | If the UE utilized a combined Attach procedure, then the Detach procedure will be directed to the PS domain. If the UE utilized a specific Attach procedure to obtain access to the BM domain, then the UE shall initiate a specific GPRS Detach procedure towards the BM domain. All connection states within the UE are delete... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.2 MBMS Service Management Procedures | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.2.1 MBMS Service Activation | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.2.1.0 General | MBMS Services are delivered to UEs using MBMS Radio Access Bearers established during the MBMS Context activation procedure. Whenever it is necessary to deliver a MBMS Service to a UE, the MBMS Context Activation procedure will be initiated at the UE, either by an external trigger or by a Request from the BMSN. In the ... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.2.1.1 MBMS Context Activation | Figure 5.4 shows the procedure initiated by the UE that triggers the MBMS Context Activation. Figure 5.4: MBMS Context Activation Procedure The procedure is illustrated in Figure 5.4 and described as follows: 1) The UE creates a handler (Enhanced Network Service Access Point Identifier (NSAPI)) for this MBMS Context an... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.2.1.2 CN-initiated MBMS Context Activation | Figure 5.5: CN initiated MBMS Context Activation The procedure is illustrated in Figure 5.5 and described as follows: 1) The BMSN initiates a Request_MBMS_Context_Activation(Linked NSAPI, Multicast Group Address, TMGI) message towards the UE and sends it to the RAN in a BRANAP (downlink) Direct Transfer message via the... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.2.1.3 Unsuccessful MBMS Context Activation (Service not authorized) | Figure 5.6: Unsuccessful MBMS Context Activation- Service not authorized The procedure is illustrated in Figure 5.6 and described as follows. Transactions 1 to 3 are described in clause 5.2.1.1. 1) The Authorization entity determines that the UE is not authorized to access the MBMS Service (TMGI) and responds to the re... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.2.2 MBMS Context Deactivation | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.2.2.0 General | The MBMS Context deactivation is a normal procedure when a UE no longer requests access to a specific MBMS Service. The MBMS Context deactivation is either initiated by the UE (for example after reception of an external AT command) or the Core Network (following reception of an IP Multicast Internet Group Management Pr... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.2.2.1 UE Initiated MBMS Context Deactivation | This procedure will be triggered in the UE by reception of an AT Command (APN) or equivalent signal on an external interface. Note that Deactivate_PDP_Context_Request NAS primitive is used to initiate the deactivation of the MBMS Context. Figure 5.8: MBMS Context Deactivation - UE initiated The procedure is illustrated... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.2.2.2 Core Network Initiated MBMS Context Deactivation | This procedure allows the Core Network to trigger the deactivation of a MBMS Context to stop the delivery of a MBMS Service to/from a UE. This is a normal procedure following reception of a trigger. Figure 5.9: MBMS Context Deactivation - Core Network initiated The procedure is illustrated in Figure 5.9 and described a... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.3 MBMS Bearer Management procedures | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.3.1 Radio Access Bearer Release | The procedure illustrated in Figure 5.10 shows the BMSN requesting the release of a unicast Radio Access Bearer. Figure 5.10: RAB Release The procedure is described as follows: 1) The BMSN sends a RAB Assignment Request containing the RAB_ID of the RAB to release and the cause for release. 2) The RAN signals the releas... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.3.2 MBMS Radio Access Bearer Release | The procedure illustrated in Figure 5.11 shows the BMSN requesting the release of a MBMS Radio Access Bearer. Figure 5.11: MRAB Release The procedure is described as follows: 1) The BMSN sends a RAB Assignment Request containing the RAB_ID/MRAB_ID of the MRAB to release and the cause for release. 2) The RAN signals the... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.3.3 MBMS Radio Access Bearer Modify | Figure 5.12 shows a RAB Assignment Request primitive initiated by the BMSN to request the change of state of a MBMS Radio Access Bearer. If the reason for this modification is a change of state of the MBMS Context, then this procedure is initiated for each UE associated to the MBMS Context which state has been changed.... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.3.4 MBMS Radio Access Bearer Modification Request | Mobility management and physical-bearer radio resource management decisions taken by an RNC result use either the handover or retuning mechanisms over the satellite interface. Both of these procedures result in a similar set of interactions on the RAN-CN interface, in that a UE may be associated with a new MBMS Context... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.3.5 MBMS Service modification | In this scenario, the BMSC will initiate a procedure to signal a modification in the MBMS service state or parameters (for example the change from inactive to active or a change in the Quality of Service definition). This will trigger a request to modify all MBMS Radio Access Bearers associated to all MBMS Contexts sup... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 5.3.6 MBMS Service Removal | This procedure is triggered by the BMSC operator to remove a specific MBMS Service, and is repeated for each BMSN which is currently supporting delivery of the MBMS Service. At each BMSN this has the effect of sending one or more PIM-SM Prune messages upstream to indicate that the multicast traffic being supported by t... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 6 Mobility Management Behaviour | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 6.1 Spot Beam Handover | Spot-beam handover procedures occur as a consequence of a UE transition across a spot-beam boundary. The UE is responsible for determining when such a transition has occurred, by comparing its current location, derived from GPS navigation information, with the spot-beam maps received from the RAN in System Information ... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 6.2 Inter-RNC operation (via different satellites) | No direct support for mobility between satellites is provided, and is this is true of both the PS and BM domains. However the multicast system does support the allocation of static IP addresses; and to simplify routing, the BMSN- router is deliberately separate from the BMSN-server functions, such that a global APN-spe... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 6.3 Inter-system mobility | This is outside the scope of this multi-part deliverable (Release 1) and is not covered in the present document. |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 7 Exception handling | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 7.1 Forced Detach (CN Initiated) | An operator may forcibly detach an UE. When this occurs, the UE shall release the Primary PDP context from the BM domain. 7.2 Primary PDP Context deactivation (while MBMS Contexts present) If the Primary PDP Context is released while a Secondary PDP context and/or a MBMS Context is still active, the BMSN shall explicit... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8 IP User Plane Handler for MBMS Services | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.0 General | Requests to join and leave MBMS Services and resources allocation and release are driven by different triggers, which are defined in this clause. |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.1 UE-TE Controller triggered MBMS Services via R-interface | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.1.1 Activation of MBMS Services | Activation of MBMS Services using an externally triggered event is handled by the reception of an AT command via the R interface exactly as for unicast secondary PDP context activation. A primary PDP context shall be in existence and activated. The procedure requires that the external controller device is provisioned w... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.1.2 Deactivation of MBMS Services | If a MBMS Context is activated using an external controller, then the persistence of that MBMS Context is indefinite, and it is the responsibility of the external controller to deactivate the MBMS Context by issuing an appropriate AT command via the R interface. It should be noted that the BMSN shall ignore an IGMP mem... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.2 Directly Connected TEs - use of IGMP as a trigger | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.2.0 General | When TE devices are directly connected to the UE, MBMS Services may be activated or deactivated by issuance of IGMP membership reports as described in this clause. Maintenance of the services is controlled through the periodic transmission of BMSN-triggered IGMP membership query messages. It should be noted that IP mul... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.2.1 Joining and leaving multicast services | When an IGMP Membership Report is received on an interface to the UE, the UE shall perform the following decision making process, as illustrated in Figure 8.1 and Figure 8.2. If the UE is configured with a local firewall, the firewall rules shall be inspected to determine whether the IGMP forwarding is allowed and whet... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.2.2 Maintenance of multicast services - IGMP query mechanism | The BMSN should generate all-group IGMP membership query messages periodically towards the UE. If the UE is operating in bridge mode, then it should forward the IGMP membership report onto the local interface without modification. If the UE is operating in router mode, then it should inspect its BMSN interface state ta... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.3.1 Joining and leaving multicast services | The behaviour for support of routers in the mobile domain is similar to IGMP handling, with the extension that the PIM-SM transactions may originate from either the TE (or more specifically a downstream router), or from an upstream PIM-SM router (or Rendezvous Point). To determine whether a PIM-router exists at the UE ... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.3.2.0 General | In this architecture (see Figure 8.3), a number of TEs may be connected to a single UE via a multicast-enabled router. In this configuration, both multicast sources and receivers are supported, and for Any Source Multicast (ASM) the Rendezvous Point is located in the terrestrial network. BMMF TE MT RAN BMSN 3. GTP-U (I... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.3.2.1 Multicast Receivers with a Mobile Domain Router | In ASM mode, the Multicast Receiver communicates with the Rendezvous Point via the PIM-SM router in the mobile domain and generates IGMP membership reports towards the mobile domain PIM-SM router (default multicast behaviour). There are two possible Mobile Domain router behaviours: a) The Mobile Domain router can behav... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.3.2.2 ASM Multicast Sources with a Mobile Domain Router | When an ASM source located in the mobile domain wishes to send multicast traffic, it will immediately start generating packets towards the PIM-SM router in the Mobile Domain. In ASM mode, the mobile domain PIM-SM router will generate a PIM Register message (standard multicast behaviour) towards the UE. The UE transpare... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.3.2.3 SSM Multicast Sources with a Mobile Domain Router | In SSM mode, the Rendezvous Point is not required. Initially, no traffic is forwarded by the PIM-SM router towards the UE. The MBMS Context Activation is triggered by a source specific PIM-Join message arriving at the BMSN as a result of a multicast receiver located in the External Network expresses interest in the {So... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.3.3 Rendezvous Point in the Mobile Domain | |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.3.3.0 General | In this architecture, the Rendezvous Point is located in the mobile domain. It is conceptually similar to the architecture defined in the previous clause, but the PIM-SM router in the Mobile Domain is now configured as a Rendezvous Point for a set of group addresses. It should be noted that this solution is only applic... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.3.3.1 Multicast Receivers with a Mobile Domain Rendezvous Point | Although this scenario is conceptually significantly more complex than the one defined in clause 8.3.2.1, traffic from the ASM source is initially encapsulated in unicast PIM-Register messages. These are forwarded via the already established RAB towards the UE. The UE transparently forwards the PIM-Register message to ... |
60e82dae8b3be524f0a53f99492f43a9 | 102 744-3-8 | 8.3.3.2 Multicast Sources with a Mobile Domain Rendezvous Point | If the source and Rendezvous Point are both located in the Mobile Domain, all communication between the PIM-SM and Rendezvous Point is constrained to the Mobile Domain. The MBMS Context Activation is triggered by a PIM-Join originated from the External Network. The high level message sequence is shown in Figure 8.9. Mu... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.