hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.3 Future aspects and algorithms | |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.3.1 ECPR algorithm | |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.3.1.1 Simulator 4: Conclusions | This work proposes ECPR, a combined rate and power DCC algorithm that efficiently achieves the target awareness and rate requirements given by the application context (e.g. target applications, vehicle speed, traffic density) in varying propagation environments. By using path loss exponent estimation, ECPR adapts the T... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.3.1.2 Simulator 4: Introduction | ECPR is an environment and context aware DCC algorithm, which combines power and rate control to improve cooperative awareness by adapting to both specific propagation environments (such as urban intersections, open highways, suburban roads) as well as application requirements (e.g. different target cooperative awarene... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.3.1.3 Simulator 4: Tools and setup | Four DCC approaches are implemented (ECPR, LIMERIC, power-only DCC algorithm, and no DCC scenario) in GEMV2 V2V propagation simulator [i.21], available at http://vehicle2x.net/. GEMV2 is a computationally efficient propagation model for V2V communications, which accounts explicitly for surrounding objects (e.g. buildin... |
1758cf5690495366dcfb2435c81d9b74 | 101 613 | 5.3.1.5 Comparing ECPR, LIMERIC, Power-only, and No-DCC algorithm | a) Neighbour awareness vs. transmission distance b) Neighbours above range causing interference vs. transmission distance ETSI ETSI TR 101 613 V1.1.1 (2015-09) 46 c) Average message rate d) Average transmit power e) Channel busy ratio (CBR) Figure 33: Target Awareness 85 %, Target Awareness Distance = 150 m, default Tx... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 1 Scope | No mandatory protocol between the Service Centre (SC) and the Mobile Switching Centre (MSC) below the transfer layer is specified by GSM; this is a matter of agreement between SC and PLMN operators. The present document specifies three approaches to the specification of protocol stacks of communication protocols for th... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 1.2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 1.3 Abbreviations | Abbreviations used in the present document are listed in GSM 01.04. 2 An OSI Protocol Stack For Interconnecting SCs and MSCs This clause specifies a stack of communication protocols in terms of the OSI Reference Model (see X.200) and therefore makes use of all seven layers for the purpose of relaying short messages and... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 2.1 Service elements on the application layer | An association (class 3) between SMRSEs is formed via ACSE and ROSE operations (class 2 and 5) are used to implement the Short Message Relay Layer described in clause 9 of GSM 03.40. This results into a asynchronous symmetric situation where both (the application entity in) the SC and (the application entity in) the MS... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 2.2 Detailed specification of the SMRSE services | On the following pages, the new SMRSE service element is specified with the ASN.1 notation, together with the entire SM-RL protocol. The Abstract Syntax Notation of the Short Message Relay Service Element SMRSE NOTE: The first two arcs of the object identifier are arbitrarily allocated, the name "etsi" is adopted from ... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 2.3.1 Application rule set 1 Semi-permanent symmetric connection | This set of application rules is to be used in situations where the connection (on all the protocol layers) between the SC and the MSC is maintained for ever. Within the SMR-BIND service, all operations are allowed on the association; semi-permanent connection is accepted (by not forcing the connection transient). This... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 2.3.2 Application rule set 2 Transient asymmetric connection | This set of application rules is to be used e.g. in situations where one SC has connections with many MSCs or vice versa, and there is a switched data network connecting them. A data network connection (and the higher layer connections on top of it) is maintained for the duration of the relay or alert operations only. ... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 2.4 Timing terminology | The overall delay of a short message relay operation between an SC and an MS may be affected i.e. by the following delays: a) transport connection establishment time between an SC and an MSC (including the time spent establishing a new network connection, if needed); b) the time needed to establish the higher layer pro... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 2.5 Error Cause Mapping | MAP to SC - MSC IllegalSubscriber illegal-subscriber IllegalEquipment illegal-equipment TeleServiceNotProvisioned teleservice-not-provisioned SM-DeliveryFailure (#0) memory-capacity-exceeded SM-DeliveryFailure (#1) error-in-MS SM-DeliveryFailure (#2) sms-not-provisioned CallBarred call-barred DataMissing system-failure... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 3.1 SMRSE Definition | The Short Message Service Relay Element (SMRSE) is defined in terms of the following service : SMR - BIND: This operation must be involved by the party which is responsible for establishing the application association ; only after the application association has been established may be remaining SMRSE services be used.... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 3.2 ASN1 Specification | The Abstract Syntax Notation of the Short Message Relay Service Element SMRSE NOTE: The first two arcs of the object identifier are arbitrarily allocated, the name "etsi" is adopted from GSM 12.20 but the value 040 is arbitrary, and the last three arcs are allocated in this module. 1st module of 2: SMS-UsefulDefinition... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 3.3.1 Semi-permanent Connections | On a semi-permanent connection the SMR-UNBIND operation is not normally invoked following an application association. |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 3.3.2 Transient Connection | In a situation where an SC has several connections to an MSC, or an MSC has several connections to MSCs, and a public data network connection may be maintained for the duration of the relay and/or alert operations the association may be ended via SMR-UNBIND as soon as all operations on the association have been complet... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 3.5 Error Cause Mapping | As section 2.5. |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 4 SS7 Protocol Stacks | |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 4.1 Introduction | Concepts described in Q.1400 (see CCITT Study Group XI Report R219, April 1992) are followed. These concepts enable - specification of an application layer such as SMS-MAP (see section 4.2) - use of the protocol specified in Section 2 of GSM 03.47 to be supported (with minor modifications) |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 4.2 Application Layer Protocol SMS-MAP | |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 4.2.1 Introduction | The present document specifies a CCITT No.7 based interface for interconnecting Short Message Service Centres (SCs) and Gateway/Interworking MSCs (GMSCs and IWMSCs). The interface is based on the Mobile Application Part (MAP, GSM 09.02) protocol stack and principles. The proposed protocol stack and specific MAP-operati... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 4.2.2 Protocol Stack | The SMS Mobile Application Part (SMS-MAP) provides the necessary signalling procedures required for information exchange between the network entities, GMSC/IWMSC and Service Centre (SC). SMS-MAP uses the services of TCAP, SCCP and MTP of CCITT No.7. NOTE: SMS-MAP is restricted to signalling between SCs and a GMSC/IWMSC... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 4.2.3 SMS-MAP Version Handling | Interworking with MAP version 2 requires an upgraded version of SMS-MAP. For SMS-MAP (SC <--> GMSC/IWMSC) version negotiation, the principles outlined in MAP version 2 shall be used (GSM 09.02). |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 4.2.4 Operations | GENERAL RULES - Components in messages (SMS-MAP protocol violation). If a component, which according to the present document shall be received in a specific message, e.g. a Result component in an End message, is received in another message, the dialogue should be aborted. - If an operation which is not supported is rec... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 4.2.5 SMS-MAP SIGNALLING SEQUENCES | SMS-MAP VERSION 1 SIGNALLING PROCEDURES Timers Operation = Forward Mobile Terminated Short Message Timer: T-fmtsm Value: 15-180 s Operation = Forward Mobile Originated Short Message Timer: T-fmosm Value: 15-30 s Operation = Service Centre Alert Timer: T-sca Value: 5-10 s Forward Mobile Terminated Short Message Procedur... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 4.2.6 Errors | ERRORS COMMON FOR VERSION 1 AND VERSION 2 - CallBarred This error is returned, when a short message delivery failsdue to barring conditions attached to the subscriber. Barring conditions can be attached to the subscriber due to a active call barring supplementary service or by operator initiated barring. A parameter in... |
88b75c4d7b19c861f7cfed50f9701701 | 101 635 | 4.2.7 SMS-MAP Parameter Data Types | DATA TYPES COMMON FOR VERSION 1 AND VERSION 2 AddressString ASN.1 Formal Description AddressString ::= OCTET STRING (SIZE (1..maxAddressLength)) a) First octet including a one bit Extension Indicator, 3 bits Nature Of Address and 4 bits Numbering Plan Indicator. The following codes are handled by SMS-GMSC: - Bit 8: Ext... |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 1 Scope | The present document describes the support of Videotex service within the GSM PLMN network, taking into account the service definition as per CCITT Recommendation F.300 and Bearer Services specified in GSM 02.02 for a GSM PLMN. |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 2.1 Abbreviations | In addition to those below, abbreviations used in the present document are listed in GSM 01.04. AU Access Unit SBVT Syntax Based Videotex Terminal VAP Videotex Access Point VSC Videotex Service Centre VTX host The computer dedicated to Videotex service |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 3 Service definition | The Videotex service is an interactive service that by means of proper access points and standardized procedures provide the access to data base information stored in host computers external to the PLMN, via public telecommunication networks. The basic elements considered for a Videotex system are: - the user terminal;... |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 3.1 Videotex service in the GSM context | Figure1 shows the basic concept underlying all the GSM Bearer Services, as defined in GSM 02.02. The most general case is the GSM PLMN interworking with a Transit Network (PSTN and/or ISDN, none), interconnected to a Terminating Network (PSPDN, PSTN and/or ISDN). Figure 1/03.43: GSM Bearer Service scheme As the informa... |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 4 Network architecture | As identified in CCITT Recommendation F.300, various configurations are permitted for the structure of a Videotex system. A terminal can be connected to a Videotex host server: - directly by a telecommunication network; - via a Packet Assembly/Disassembly (PAD); - via a Videotex Access Point (VAP); - via a Videotex Ser... |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 4.1 Videotex host directly connected to PSTN/ISDN | When it is assumed that the Videotex centre is directly connected to the PSTN/ISDN, the network scheme is as shown in figureig.2 /03.43. Figure 2/03.43: VTX host directly connected to PSTN/ISDN With reference to the general scheme in figure1/03.43, the terminating network (in this case working as transit network as wel... |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 4.2 Videotex host accessed via PAD | Figure 3/03.43 summarizes this configuration, outlining all possible network alternatives. Figure 3/03.43: VTX host accessed via PAD The main service alternative concerns basic/dedicated PAD access. In case of basic PAD access, the transit network (PSTN and/or ISDN) is utilized to access the PAD, remotely located with ... |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 4.3 Videotex host accessed via VAP | Figure 4/03.43 summarizes this configuration, outlining all possible network alternatives. Figure 4/03.43: VTX host accessed via VAP Circuit Mode access to the VAP via ISDN transit network (and BS 3x) is according to ETS 300 079 and ETS 300 080. Concerning Packet Mode access to VAP, again the main choice concerns basic... |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 4.4 Videotex host accessed via VSC | Though the Videotex Access Function is explicitly separate with respect to the Videotex host, no impact results on the overall Network architecture. Actually the VSC can be considered a front-end function of the same Videotex host (either physically separate or integrated), so that all the above configuration in princi... |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 5 Reference configuration of the Mobile Station (MS) | The following types of reference configuration of the MS are possible: TE2 TE1 M T2 TA M T1 M T0 Um M obile Station a) b) c) d) R S M T1 TE2 S R Figure 5/03.43: Reference Configuration of the MS The definitions of the functional blocks shown in figure 5 are reported in GSM 04.02. Concerning specific Videotex functions ... |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 6 Bearer Service configuration and settings | Support of Videotex service on the the GSM PLMN is via GSM standard Bearer Services, as specified in various GSM Technical Specificationa. In the following specific reference on the main technical aspects are reviewed. |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 6.1 Connection Types | Transparent or non-transparent network support can be requested to the GSM PLMN for Videotex service. The information transfer protocol models are those in figure 6/GSM 03.10, models 1a, 2a, 3a, 4a for ISDN-related MS configurations, and models 1b, 2b, 3b, 4b for PSTN-related MS configurations. Concerning "Circuit mode... |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 6.2 Terminal Adaption functions | The TAFs used for Videotex are the asynchronous and synchronous standards defined in GSM 07-series; rate adaption functions are those specified in GSM 04.21 and GSM 08.20. |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 6.3 Signalling aspects | All GSM standard rates (up to 9 600 bit/s) can be used for Videotex on a GSM PLMN; appropriate settings in BC-IE and LLC (where applicable) fix the rate on the GSM connection, and identify the voiceband modem to be used (when applicable) by the IWF. When a 1 200/75 bit/s Bearer Capability is requested, the 75 bit/s rat... |
810caf4a35dbca96b6bba9d985444862 | 101 633 | 6.4 Network interworking | Ad-hoc Specifications are devoted in the GSM normative to explicitly cover the aspects of PLMN interworking; being Videotex service a generic application running on top of GSM standard Bearer services, all technical aspects in those GSM specifications apply. The reference are: - GSM 09.07, which details interworking re... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 1 Scope | The present document describes the specific protocols for systems providing a throughput of 1 Gbit/s/km2. Such systems include features such as self-backhauling in both licensed and un-licensed bands, cognitive-radio based self-organization, etc. |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 2 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... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. Not applicable. |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 101 534 (V1.1.1) (2012): "Broadband Radio Access Networks (BRAN); Very high capacity density BWA networks; System architecture, economic model... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 3 Definitions and abbreviations | |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: DL-MAP: structured data sequence that defined the mapping of the downlink self-backhauling: wireless links between HBS and ABS which may share a frequency channel with the access operation (in-band) and use in addition license-exempt s... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAA Authentication, Authorization, and Accounting ABS Access BS ACK Acknowledge ARA Adaptive Resource Allocation ASN Access Service Network BS Base Station BS-BS Base Station to Base Station BSID Base Station IDentifier BWA user Fixed, Nomadic... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 4 Introduction | The present document presents new possible protocols specific to wireless BWA network, as described in [i.1], including heterogeneous elements (a two tier approach), combined use of licensed and license-exempt spectrum, very low delay communications between network elements, enabling the operation of the network MIMO t... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 4.1 Architecture for the underlaying system | The architecture presented in [i.1] is summarized below, for easing the reader understanding. Its main features are: • Multiple access links aggregation. • Self-backhauling link aggregation. • Network MIMO (for downlink and uplink). • Radio Resource Management. • Direct BS-BS or MS-MS communication. The system architec... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 4.2 Radio resource management | This clause presents protocols and procedures related to RAN RRM and dynamic resource (frequency, power) assignment. The description relates to the air interface and the network interfaces and presents reference design for procedures and protocol primitives, required to support the aforementioned RRM mechanisms. BACKHA... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 4.2.1 RRM functional decomposition in system architecture | The functional decomposition is based on the state-of-the-art WiMAXTM and 3GPP standards, where Radio Resource Management (RRM) functional entity is located in the Base Station/eNodeB, while ASN GW/MME may act as a protocol relay function, but do not implement RRM-specific functions. RRM functional entity BS/ eNodeB RR... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5 Frequency channel assignment | |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.1 Dynamic centralized frequency assignment | |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.1.1 Overall objectives | The centralized dynamic RRM protocol is based on an overall supervision of the radio network status, and tries to optimize radio link resources depending on interference levels, throughput load and architecture deployment. Certain extent of information is required for this purpose, which mainly consist of different req... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.2 Description of the algorithms | The procedures related to Dynamic Frequency Planning (DFP) should be performed automatically upon initial RAN segment activation and after that periodically or event driven to take into consideration global evolutions of the radio access network deployment characteristics. The main purpose of the cluster radio resource... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.2.1 Recovery procedure | The recovery procedure is based on the centralized dynamic frequency planning, with the additional aspect of station failure detection. In this procedure, stations status is periodically checked, just more frequently than the dynamic frequency planning. This way the station failure can be detected quite quickly and the... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.2.2 Centralized interference mitigation | In the case that the station detects performance degradation below the threshold because of high interference level and no useable channels can be found locally with acceptable noise/interference levels, the request may be sent to the centralized RRM entity to readjust its dynamic frequency planning. The request is sen... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.2.3 Adaptive resource allocation | In the case of some special events, such as New Year fests, throughput required in some hot-spots may drastically increase. The centralized RRM can then be triggered to readjusts its channel assignment model and to provide wider frequency bands to some ABSs. This process is basically the same as the dynamic frequency p... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.2.4 Centralized RRM macro-application | The hierarchy of centralization nodes for radio resource management may be introduced because previously presented topology assumes centralized RRM entity for a number of Access Base Stations (e.g. collocating centralized RRM-E in HBS serving the associated ABSs). However, similar RRM-E function may be introduced at th... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.2.5 Control plane primitives | The following clause presents control plan message flows and primitives designed to support the centralized RRM-E concept. |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.2.5.1 Information request | The purpose of Information request procedure is to collect the radio-related measurements from the particular BS in order to provide the centralized RRM Entity with a clear knowledge of the current status. The message flow corresponding to this request is illustrated in figure 5.6. RRM-E 1 ) RRME_Info_Req 4 ) RRME_Info... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.2.5.2 New station insertion indication | A new station insertion requires RRM adaptations. A new ABS acceding the access network and successfully recognized by the AAA server sends an insertion request to the centralized RRM entity. The corresponding message flow is illustrated in figure 5.7. AAA RRME 1 ) RRM_Insertion_Req 4 ) RRM_Insertion_Ack New ABS 2 ) Au... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.2.5.3 Capacity overload indication | Overload alarm is sent by the station to the Centralized RRM-E to indicate increase in the node throughput requirements. If possible, the Centralized RRM-E will provide the node with a larger frequency band and/or better quality channels in order to improve its performance. ETSI ETSI TR 101 589 V1.1.1 (2013-07) 19 RRME... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.2.5.4 Station re-configuration request | The purpose of this message is to send the actual configuration parameters to the station. RRME 1 ) RRME_Reconf_Req 2 ) RRME_Reconf_Ack ABS Figure 5.9: Re-configuration request message flow ETSI ETSI TR 101 589 V1.1.1 (2013-07) 20 Step 1 The RRM-E sends for each node under its responsibility a personalized message incl... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.3.1 Spectrum sensing based dynamic frequency assignment | Spectrum sensing is a process where a cognitive radio scans the available frequency bands, estimating the interference level on each of them. Based on the interference estimation the cognitive device can then select the most appropriate frequency channel to use. This cognitive capability is one of the most distinguishi... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.4 Learning based cognitive dynamic frequency assignment | |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.4.1 Overview and general objectives | Cognitive techniques, such as spectrum sensing and learning, are able to provide a very aggressive frequency reuse while reducing the radio resource management complexity. The learning based cognitive radio algorithm, we introduced in this clause, completely removes the needs for any frequency plan. All frequency chann... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.4.2 Functional decomposition and message flows | Cognitive Dynamic Frequency Assignment (Sensing and Learning): learning will only prioritize the available subchannels for individual entities distributedly based on the weight information gained by the entities. The weight is updated according to successful or unsuccessful transmission attempts based on the flowcharts... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.4.3 Control plane primitives | Table 5.8: Transmission_REQ Message purpose Indicates that new transmission is needed Trigger for the message generation When uplink transmission needs to be initiated Source RRM entity in HSS, or MS Destination RRM entity in targeted ABS or HBS List of Information Elements IE Name MANDATORY/OPTIONAL Description Transm... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.5 Cognitive and docitive RRM | This clause forms a general introduction to docition and learning from a control and signalling point of view. We introduce the basic features of learning and docition and stress the features that are critical for control and signalling. We based this clause in the learning and docition introduced in [i.1]. The learnin... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.5.1 Feature overview | The main features we want to study are: Learning and Docition. In the following we briefly introduce them: Learning is an iterative procedure by means of which an ABS is able to learn an RRM policy. The learning procedure is totally distributed, which means that the RRM policy decision is done independently at each ABS... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.5.2 Functional decomposition | The learning capabilities of the ABS allow the ABS to dynamically adapt its MCS, subchannel used and power transmitted. In here we focus only in the subchannel and transmit power case. In the case of the ABSs switching the transmit subchannel the ABS RRM entity should inform the MS RRM entity of that change. Docition: ... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.5.3 Message flows | The following clauses present the relevant message flows for the Learning and Docition procedures. Learning procedure ABS detects a drop on performance and decides to not get docition. 1) ABS may decide to request docition or directly start the learning procedure. 2) ABS starts learning procedure. i) ABS estimates the ... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 5.5.4 Protocol primitives description | Table 5.12: IQ_REQ Message purpose Indicates the ABS to compute and send the IQ value to the requesting HBS Trigger for the message generation Triggered by Docition_REQ message reception from ABS - when a Hub BS is required to start docition Source RRM entity in Hub BS Destination RRM entities in the associated ABSs Li... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6 RAN self-organization and optimization support | This clause presents the reference protocol design for RAN SON mechanisms. In order to collect sufficient information about its surrounding for RRM protocols operations, and to supply the served MSs with a list of potential HO candidates, a self deployable BS should be aware of its neighbouring BSs. This is the objecti... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.1 Automatic neighbours discovery | Implementation of this functionality is outlined in terms of WiMAXTM technology, however the proposed concept is relevant to LTE and HSPA as well. This functionality provides for the generation of Neighbour list (NBL) in the BS. There are two mechanisms for identification of potential neighbour entities - one is that t... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.1.1 Polling | Every MS normally has periods of scanning wireless media to get knowledge of neighbour BSs. This information is kept in the MS for a certain time. Neighbor BS; BSID = N2 MS Service Broadcast Reporting N2 Serving BS BSID = N1 Figure 6.4: Neighbour detection The BS periodically polls the serviced (registered) MSs to pull... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.1.2 Proximity reports | This functionality is based on proximity reports issued by a MS to the serving BS (SBS) every time when the MS enters or leaves the proximity of a neighbour BS. The SBS can collect information on proximity Enter and Leave events that occurred in the time intervals when the MS was not registered at the SBS; then informa... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.1.2.1 Proximity reports configuration | The process starts from configuration parameters that can be either broadcasted by the SBS (then they are valid for all the registered MSs) or delivered to an individual MS in a unicast message. Table 6.3: Proximity Report Configuration Message purpose Proximity reports configuration message Trigger for the message gen... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.1.2.2 Proximity reporting | The report message contains one or more records; every record contains the following parameters. Each record describes a certain Proximity event. Table 6.4: Proximity Report Message purpose Proximity report message Trigger for the message generation Proximity report timer expiry or explicit response to proximity report... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.1.3 Neighbour BS "Hello" handshake | Once neighbouring entity is detected, the BS initiates "BS Hello handshake" procedure, intended to establish communication channel between the two entities and optionally create consistency awareness between the two (e.g. by tracking the Last Reset Time of the peer entity). RAN entity RAN peer New RAN peer entity is id... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.1.3.1 Hello request | Hello Request message is initiated by the RAN entity detecting a new RAN peer in its proximity and wishing to establish communication channel with this entity. ETSI ETSI TR 101 589 V1.1.1 (2013-07) 39 Table 6.5: Hello Request Message purpose Establish the communication channel with the peer Trigger for the message gene... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.1.3.2 Hello response | Hello Response message is sent in response to Hello Request. Table 6.6: Hello Response Message purpose Establish the communication channel with the peer Trigger for the message generation Reception of the Hello Request message Source Peer RAN entity Destination Source RAN entity List of Information Elements IE Name MAN... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.2 Neighbours data synchronization | Implementation of this functionality is outlined in terms of WiMAXTM technology however the proposed concept is relevant to LTE and HSPA as well. ETSI ETSI TR 101 589 V1.1.1 (2013-07) 40 |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.2.1 Overview | The Neighbours Data Synchronization (NDS) mechanism automatically distributes relevant configuration of the BS (e.g. UCD/DCD) to its neighbours BSs, enabling handover between the BSs. In order to provide service continuity, MS uses Handover (HO) procedure when migrating form one cell (serving BS - SBS) to a new cell (T... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.2.2 Functional decomposition | The NDS feature is implemented in RRM entity in the BS. The RRM Entity includes NDS Client and NDS Server; every NDS Client communicates with the NDS Server of every peer BS via the R8 (X2 in LTE). BS-i BS-k R8/ X2 RRM RRM NDS Client NDS Server NDS Client NDS Server Figure 6.6: NDS functional decomposition Functions of... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.2.3 Message flows | NDS feature is implemented using a symmetric protocol between BSs to update each other of their parameters. Every BS periodically polls the neighbour BSs with information requests (pull mode). The polled BSs respond to the requests. The response includes GPS reading by the BS. If yes, the info is copied from the respon... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.2.3.1 Radio configuration update (Pull) | Figure 6.7: Radio Configuration update (Pull) ETSI ETSI TR 101 589 V1.1.1 (2013-07) 42 |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.2.3.2 Radio configuration unsolicited update (Push) | Figure 6.8: Radio Configuration unsolicited update (Push) |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.2.4 Protocol primitive description | The following parameters are carried in the messages. |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.2.4.1 Neighbour information request | Table 6.7: Radio_Config_Update_Req Message purpose Request for radio configuration update parameters Trigger for the message generation Periodic Source NDS Client in RRM entity in a BS Destination NDS Server in RRM entity in a Neighbour BS List of Information Elements IE Name MANDATORY/OPTIONAL Description Sender ID M ... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.2.4.2 Neighbour information response | Table 6.8: Radio_Config_Update_Rpt Message purpose Radio configuration update message Trigger for the message generation In response to Radio_Config_Update_Req message or unsolicited, triggered by the radio parameters change Source NDS Server in RRM entity in a BS Destination NDS Client in RRM entity in a peer BS List ... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.2.4.3 UCD/DCD count update | The BS transmits two fields called DCD count and UCD count that are incremented by one each time when DCD and UCD contents respectively change. These fields are transmitted as part of the DCD and UCD messages, in the DL-MAP and UL-MAP respectively using the Configuration Change Count field. The DCD message contains the... |
6ccf47bdd683c4e0ec0322d450b82da1 | 101 589 | 6.2.4.4 UCD/DCD configuration exchange | Upon initialization or changes in its radio configuration, the BS should send an unsolicited Radio_Config_Update_Rpt message including all the relevant parameters to all the NBSs in its neighbour list (NBL). A BS should send a Radio_Config_Update_Req message to all the NBS at preconfigured intervals. These intervals sh... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.