hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
70172d647bd0430cf55959218f45740d | 25.902 | 1 The development of an Iub/Iur Congestion control solution should bear in mind both the E-DCH and HSDPA features.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 2 Iub/Iur Congestion control for both HSDPA and Enhanced Uplink should – if possible – employ similar solutions.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 3 The RNC remains the entity in charge of the Congestion Control function.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 4 NodeB behaviour when receiving the congestion indication shall be specified.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 5 The detection algorithm will not be specified in the TR. (However example algorithms may be given in an annex.)
| |
70172d647bd0430cf55959218f45740d | 25.902 | 6 Congestion indication should be signalled via the user plane.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 7 Signalling of Congestion via the user plane will also include varying levels of congestion severity.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 8 Congestion Detection will be performed on a per flow basis.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 9 Within the E-DCH data frame (user plane), congestion detection will be based upon a time reference or a sequence number.
| 10 For the handling of Iub/Iur Congestion due to HSDPA, the CRNC decides whether all or none of the HS-DSCH MAC-d Flows of a context are subject to Congestion Control.
|
70172d647bd0430cf55959218f45740d | 25.902 | 11 A "counter" field be attached to EVERY E-DCH data frame.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 12 The "counter" field within the E-DCH frame will take the form of a "frame sequence number" (FSN).
| |
70172d647bd0430cf55959218f45740d | 25.902 | 13 Different levels of congestion shall be indicated by "No congestion", "TNL Congestion – detected by delay build-up", "TNL Congestion – detected by frame loss".
| |
70172d647bd0430cf55959218f45740d | 25.902 | 14 The resulting behaviour following the signalling of Congestion Indication will not be defined – this is an implementation matter.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 15 For impacts upon RNL xxxAP Signalling protocols, please refer to CR 1080 against TS 25.423. This CR allows a CRNC to decide whether a particular E-DCH flow is subject to congestion control at flow setup.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 16 Regarding the possibility of an Iub/Iur Congestion Control solution incorporating Rate Adaptation, this functionality was discussed, but a solution was not found, nor foreseen as possible at this time.
| |
70172d647bd0430cf55959218f45740d | 25.902 | 17 With respect to Softhandover, no issues have been found concerning the relationship/interaction with E-DCH Congestion Control.
| 8 Specification impact and associated Change Requests
This clause is intended to list the affected specifications and the related agreed Change Requests. It also lists the possible new specifications that may be needed for the completion of the Work Task.
CR Title
Impacted Specification
CR implemented against vers... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 1 Scope
| This present document is for the 3GPP Release 6 Work Item "Network Assisted Cell Change – Network Side Aspects.".
The purpose of the present document is to aid TSG RAN WG3 to standardise the signalling of relevant GERAN information during cell re-selection across the relevant UTRAN interfaces.
This document is inten... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 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 a... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 3 Definitions, symbols and abbreviations
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 3.1 Definitions
| For the purposes of the present document, the following terms and definitions apply.
Local RNC: the local RNC(s) to a given cell or BSS is/are the RNC(s) with cells which are neighbouring to the GERAN cell or BSC.
Remote RNC: an RNC is remote to a given GERAN cell or BSS if none of its cells are neighbours of the GER... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 3.2 Symbols
| For the purposes of the present document, the following symbols apply:
Gb Interface between the BSS and the 2G SGSN
Gn Interface between two GSNs in the same PLMN
|
873bb0765fb9905ca579985e57bc695e | 25.901 | 3.3 Abbreviations
| Applicable abbreviations can be found in [3]. For the purposes of the present document, the following abbreviations apply:
BSSGP Base Station Subsystem GPRS Protocol
DRNC Drift RNC
GERAN Gsm/Edge Radio Access Network
NACC Network Assisted Cell Change
PSI Packet System Information
RAN Radio Access Network
RIM ... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 4 Introduction
| At the 3GPP TSG RAN #19 meeting, the Work Item Description on "Network Assisted Cell Change from UTRAN to GERAN – Network Aspects" was approved.
In today's GPRS networks (without NACC), cell re-selection can causes a service interruption in the region of 4 – 8 seconds, which obviously has an impact on the user experie... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 5 Requirements
| The standardisation of NACC from UTRAN to GERAN shall meet the following requirements:
1) The impact to the Gb and Gn interfaces shall be minimised.
|
873bb0765fb9905ca579985e57bc695e | 25.901 | 6 Study Areas
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1 UTRAN NACC signalling architecture
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.1 General
| Three possible mechanisms have been identified to gain access to the GERAN SI/PSI at the SRNC, whilst minimising the impacts on the existing Gb/Gn procedures:
1) The (P)SI is stored by the SRNC.
2) The (P)SI is stored by the local RNC
3) O&M-based distribution of (P)SI.
These solutions are explained in the followi... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.2 Solution 1: (P)SI stored by the SRNC
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.2.1 General description
| This solution is based on the serving RNC directly requesting and receiving the SI/PSI from the target BSS and it is depicted in figure 1.
1) The SRNC receives a measurement report from the UE and decides to move the UE to GERAN.
NOTE: The SRNC could request the info earlier on receiving GERAN n_cell info from DRNC.... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.2.2 Analysis of the solution
| Pros:
1) No additional Iur load generated.
2) No additional Iur implementation required.
3) Synchronised update of SI/PSI is possible using "on-modification" measurement reporting.
Cons:
1) Generally more SI/PSI stored in each RNC than in other solutions.
2) Additional load on the SGSN due to... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.3 Solution 2: (P)SI stored by the local RNC
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.3.1 General description
| This solution is based on the local RNC requesting SI/PSI from the BSS, and receiving it on an "on-modification" basis. This procedure is depicted in figure 2.
1) After installation and configuration of the GERAN neighbouring cell lists in the local RNC, a REQUEST message is sent to the SGSN requesting GERAN SI/PSI fo... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.3.2 Analysis of the solution
| Pros:
1) Generally less SI/PSI stored in each RNC than in other solutions.
2) Synchronised update of SI/PSI is possible using "on-modification" measurement reporting.
3) Impact on SGSN load is minimised.
Cons:
1) More Iur signalling than SRNC terminated solution.
2) Additional load on the DRNC... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.4 Solution 3: O&M-based distribution of (P)SI
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.4.1 General description
| This solution is based on the operator using O&M to update the stored SI/PSI in the neighbouring GERAN cell list of the RNC every time it is modified by O&M in the GERAN cell. This is depicted in figure 3.
1) On installation and initial configuration by O&M of the GERAN neighbouring cell lists in the (C)RNC, the GERAN... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.4.2 Analysis of the solution
| Pros:
1) No direct signalling required between UTRAN and GERAN.
2) No impact on the SGSN.
Cons:
1) Maybe difficult to ensure that SI/PSI stored in UTRAN is always aligned with that in the GERAN cell.2) Extra impact on 3G NMS and R interface.
|
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.1.5 Comparative analysis of the solutions
| The sub-clauses 6.1.2.2, 6.1.3.2 and 6.1.4.2 are summarised in Table 1.
Table 1: Comparative analysis of the proposed solutions.
Solution
Pros
Cons
1. (P)SI provided to the SRNC
• No additional Iur load generated.
• No additional Iur implementation required.
• Synchronised update of SI/PSI is possib... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.2 UTRAN signalling procedures for NACC
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.2.1 Iur signalling for GERAN SI/PSI transfer from the DRNC to the SRNC
| The transfer of SI/PSI over the Iur is relevant to solution 2, described in sub-clause 6.1.3. Two different solutions have been identified on the Iur interface for the transfer of (P)SI from the local DRNC to the SRNC.
Use the [RNSAP] RADIO LINK SETUP RESPONSE message.
- GERAN SI/PSI could be sent in the "GSM neighbo... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.2.2 Use of RANAP or O&M for provision of GERAN SI/PSI to RNC
| The issue of whether to use O&M or whether to use RANAP signalling to inform the RNC of the GERAN SI/PSI is dependant on how often the GERAN SI/PSI would be changed, i.e. how often the operator optimises GERAN SI/PSI. If the O&M solution were chosen and if it is required to update the SI/PSI very frequently, there may ... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 6.2.3.3.1 General
| What form should the BSS <=> 3G SGSN response RIM messages take?
Three options are analysed in this sub-clause:
1. As per existing agreements for inter-RAT signalling, the host source system - when inter-RAT signalling - adapts to the target system and thus constructs an appropriate RANAP message.
2. The GERAN syst... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 7 Agreements and associated Contributions
| The main text of the document should start here, after the above clauses have been added.
|
873bb0765fb9905ca579985e57bc695e | 25.901 | 7.1 UTRAN NACC signalling architecture
| The mechanism used to gain access to the GERAN SI/PSI at the SRNC is such that the (P)SI will be stored by the local RNC.
|
873bb0765fb9905ca579985e57bc695e | 25.901 | 7.2 Format of RIM messages
| GERAN does not adapt RIM messages to the target system and are routed via the CN without interpretation. The RNC alone needs to send and receive BSSGP messages within a container within the RANAP message.
|
873bb0765fb9905ca579985e57bc695e | 25.901 | 7.3 Exchange of Information over Iu
| The transfer of RIM information over the Iu from UTRAN, will be performed using a new RANAP procedure – Direct Information Transfer. This generic Class 2 RANAP procedure has been designed such that it will transfer information from the RNC to the CN or vice versa, in unacknowledged mode – maintaining the previously agr... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 7.4 Exchange of Information over Iur
| The transfer of RIM information over the Iur between the SRNC and the DRNC will be performed using an existing RANAP R5 procedure – [RNSAP] Information Exchange – following an appropriate modification/addition to the procedure.
|
873bb0765fb9905ca579985e57bc695e | 25.901 | 8 Specification Impact & associated Change Requests
| This section is intended to list the affected specifications and the related agreed Change Requests. It also lists the possible new specifications that may be needed for the completion of the Work Task.
8.1 TS 25.401 UTRAN Overall Description
8.1.1 Impacts
GERAN System Information Retrieval is introduced as an ad... |
873bb0765fb9905ca579985e57bc695e | 25.901 | 9 Project Plan
| |
873bb0765fb9905ca579985e57bc695e | 25.901 | 9.1 Schedule
| Date
Meeting
Scope
[expected] Input
[expected]Output
Sept 2003
RAN#21
RAN Approval
TR Approved
Mar 2004
RAN#23
RAN Approval
TR Approved
June 2004
RAN#24
RAN Approval
TR Approved
|
873bb0765fb9905ca579985e57bc695e | 25.901 | 9.2 Work Task Status
|
Planned Date
Milestone
Status
Annex A:
Change history
Change history
Date
TSG #
TSG Doc.
CR
Rev
Subject/Comment
Old
New
June 2004
TSG-RAN#24
RP-040186
Presentation of TR for information
-
1.0.0
June 2004
TSG-RAN#24
Approved at TSG RAN #24 and placed under Change Contr... |
e77d3faff9be1de0a0fd3e5e46ddb1f5 | 25.807 | 1 Scope
| Some companies have shown their interest in the feasibility of a low output power FDD base station, because it would offer the following advantages:
1. It would not be necessary to use an expensive high power amplifier when a distribution system is connected after the node B. Distribution systems require low input... |
e77d3faff9be1de0a0fd3e5e46ddb1f5 | 25.807 | 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 a... |
e77d3faff9be1de0a0fd3e5e46ddb1f5 | 25.807 | 3 Abbreviations
| For the purposes of the present document, the following abbreviations apply:
3G Third Generation
3GPP Third Generation Partnership Project
BS Base Station
CPICH Common Pilot Channel
DL Downlink
DPCH Dedicated Physical Channel
FDD Frequency Division Duplex
IE Information Element
NBAP Node B Application Part
P-... |
e77d3faff9be1de0a0fd3e5e46ddb1f5 | 25.807 | 4 Definition of low output power
| Maximum output power, Pmax, of the base station is the mean power level per carrier measured at the antenna connector in specified reference conditions, as defined in [2], section 6.2.1. The lowest maximum output power that can be set for a base station with the current specifications is 0 dBm. The individual channel c... |
e77d3faff9be1de0a0fd3e5e46ddb1f5 | 25.807 | 5 Solutions for getting low output power
| |
e77d3faff9be1de0a0fd3e5e46ddb1f5 | 25.807 | 5.1 Solution #1
| The first solution for getting low output power is described in Annex B. As it can be seen in this annex, this solution implies only one change to the current specifications, which is the following:
• TS 25.433 (NBAP protocol specification). A new IE must be created, containing the following information:
• Ex... |
e77d3faff9be1de0a0fd3e5e46ddb1f5 | 25.807 | 5.2 Solution #2
| Another way of getting low output power would be to introduce these two parameters, as described in Solution #1, DL and UL gain of the distribution system, into the O&M system.
By doing this, the base station would be aware of the presence of this equipment and could therefore adjust its output power, so as to provide... |
e77d3faff9be1de0a0fd3e5e46ddb1f5 | 25.807 | 6 Conclusions
| TSG RAN WG3 has reviewed solution #1 and concluded that, although this could be a feasible solution, it does not seem to be the optimal one.
Therefore, a second solution, solution #2, was proposed trying to minimize the changes to the current specifications.
As option a) of solution #2 seems to be the simplest solut... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 1 Scope
| The present document specifies the Remote Electrical Tilting Application Part (RETAP) between the implementation specific O&M transport function and the RET Antenna Control unit function of the Node B. It defines the Iuant interface and its associated signaling procedures.
|
1de16545e4a78484b5596a06529f4503 | 25.463 | 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 a... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 3 Definitions and abbreviations
| |
1de16545e4a78484b5596a06529f4503 | 25.463 | 3.1 Definitions
| For the purposes of the present document, the following terms and definitions apply.
Active alarm: An alarm which has an alarm state that has been raised, but not cleared
Alarm: Persistent indication of a fault
Alarm code: A code that identifies a specific alarm. The alarm code set is a subset of the return code set... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 3.2 Abbreviations
| For the purposes of the present document, the following abbreviations apply:
EP Elementary Procedure
HDLC High-Level Data Link Control
RET Remote Electrical Tilting
RETAP Remote Electrical Tilting Application Part
TCP Time-Consuming Procedure
|
1de16545e4a78484b5596a06529f4503 | 25.463 | 4 General
| |
1de16545e4a78484b5596a06529f4503 | 25.463 | 4.1 Procedure specification principles
| The principle for specifying the procedure logic is to specify the functional behaviour of the RET antenna control unit exactly and completely. The Node B functional behaviour is left unspecified.
The following specification principles have been applied for the procedure text in clause 6:
- The procedure text discri... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 4.2 Forwards and backwards compatibility
| The forwards and backwards compatibility of all versions of the protocol shall be assured by a mechanism in which all current and further messages will not be changed in the future. These parts can always be decoded regardless of the standard version.
New functionalities are added into the specification by introducing... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 4.3 Multi-antenna units
| The RETAP elementary procedures are split into a single-antenna oriented part, a multi-antenna oriented part and a common part for both device types in order to support RET units controlling single- or multi-antenna devices. The RET unit responds, upon request, the number of antennas it controls. All multi-antenna orie... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 4.4 Integer representation
| Multi-octet integer values are transmitted in little endian order. Signed integers are represented as 2-complement values.
|
1de16545e4a78484b5596a06529f4503 | 25.463 | 5 Services expected from signalling transport
| RETAP requires an assured in-sequence delivery service from the signalling transport and notification if the assured in-sequence delivery service is no longer available.
|
1de16545e4a78484b5596a06529f4503 | 25.463 | 5.1 Elementary procedure format
| Layer 2 provides a full-duplex link for the transmission of RETAP messages.
There are two types of RETAP elementary procedures:
Class 1: Initiating messages are sent either from the primary to a secondary device, or from a secondary to the primary device, in order to initiate some action within the receiving device. ... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 5.1.1 Initiating message
| The data part of an initiating message may contain parameters as specified in clause 6 of this TS.
|
1de16545e4a78484b5596a06529f4503 | 25.463 | 5.1.2 Response message
| Elementary procedures shall, unless otherwise specified, provide a response message within 1 second. The response time is measured from the time the message frame was received by the transport layer to the time the response message is ready for transfer by the transport layer.
If the class1 elementary procedure reques... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6 Control elementary procedures
| |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.1 State model
| The state model describing the RET device is shown in figure 6.1 with procedures written in italic.
The relation to the connection state model for layer 2 can be found in [3].
Figure 6.1: State model for the RET device
If an application software is not missing the RET device enters the state OperatingMode.
If ... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.2 General procedure handling
| |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.2.1 Alarms
| When a fault is detected, the corresponding alarm state shall be changed to state raised by the secondary device. When the fault no longer exists, the corresponding alarm state shall be changed to state cleared by the secondary device. Alarm changes are reported through the AlarmIndication or AntennaAlarmIndication ele... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.2.2 Procedure message interpretation
| The following message interpretation rules shall apply to a secondary device in the order mentioned:
- Any message shorter than 3 octets shall be disregarded. In case of Multi-Antenna-Procedures any messages shorter than 4 octets shall be disregarded.;
- If a message has a length inconsistent with its “Number of data... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.2.3 Parallel procedure handling
| The secondary device shall support parallel execution of in maximum one additional EP only in parallel to one of the Time-Consuming Procedures defined in table 6.2.3.1:
Table 6.2.3.1: Definition of TCPs and the execution of procedures in parallel to a TCP
Elementary Procedure
TCP
Execution in parallel to a TCP
Com... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.3 Overview of elementary procedures
| The set of elementary procedures for RET antenna control provides procedure-oriented instructions. An overview of the procedures is given in annex D. Table 6.3.1 lists all common elementary procedures described in subclause 6.5. Table 6.3.2 lists all elementary procedures specific for single-antenna device types descri... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.4 Description of elementary procedures
| Table 6.4.1: Description of elementary procedures
Name:
The name used to refer to the elementary procedure
Code:
The code is defined here. All other code references are informative
Issued by:
Primary device or secondary device
Procedure class:
Class 1 or Class 2
DownloadMode state:
Defines whether the procedu... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5 Common elementary procedures
| |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.1 Reset Software
| Table 6.5.1.1: Elementary procedure Reset Software
Name:
ResetSoftware
Code:
0x03
Issued by:
Primary device
Procedure class:
1
DownloadMode state.
Yes
Power mode:
Low
Table 6.5.1.2: Initiating message parameters and format for Reset Software
Number
Length
Type
Description
None
0 octets
None
No da... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.2 Get Alarm Status
| Table 6.5.2.1: Elementary procedure Get Alarm Status
Name:
GetAlarmStatus
Code:
0x04
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.5.2.2: Initiating message parameters and format for Get Alarm Status
Number
Length
Type
Description
None
0 octets
None
N... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.3 Get Information
| Table 6.5.3.1: Elementary procedure Get Information
Name:
GetInformation
Code:
0x05
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
Yes
Power mode:
Low
Table 6.5.3.2: Initiating message parameters and format for Get Information
Number
Length
Type
Description
None
0 octets
None
No... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.4 Clear Active Alarms
| Table 6.5.4.1: Elementary procedure Clear Active Alarms
Name:
ClearActiveAlarms
Code:
0x06
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.5.4.2: Initiating message parameters and format for Clear Active Alarms
Number
Length
Type
Description
None
0 octets... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.5 Alarm Subscribe
| Table 6.5.5.1: Elementary procedure Alarm Subscribe
Name:
AlarmSubscribe
Code:
0x12
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.5.5.2: Initiating message parameters and format for Alarm Subscribe
Number
Length
Type
Description
None
0 octets
None
No ... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.6 Self Test
| Table 6.5.6.1: Elementary procedure Self Test
Name:
SelfTest
Code:
0x0A
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
High
Table 6.5.6.2: Initiating message parameters and format for Self Test
Number
Length
Type
Description
None
0 octets
None
No data carried
T... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.7 Void
| |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.8 Void
| |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.9 Read User Data
| Table 6.5.9.1: Elementary procedure Read User Data
Name:
ReadUserData
Code:
0x10
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.5.9.2: Initiating message parameters and format for Read User Data
Number
Length
Type
Description
1
2 octets
Unsigned integer... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.10 Write User Data
| Table 6.5.10.1: Elementary procedure Write User Data
Name:
WriteUserData
Code:
0x11
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.5.10.2: Initiating message parameters and format for Write User Data
Number
Length
Type
Description
1
2 octets
Unsigned in... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.11 Download Start
| Table 6.5.11.1: Elementary procedure Download Start
Name:
DownloadStart
Code:
0x40
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
Yes
Power mode:
Low
Table 6.5.11.2: Initiating message parameters and format for Download Start
Number
Length
Type
Description
None
0 octets
None
No ... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.12 Download Application
| Table 6.5.12.1: Elementary procedure Download Application
Name:
DownloadApplication
Code:
0x41
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
Yes
Power mode:
Low
Table 6.5.12.2: Initiating message parameters and format for Download Application
Number
Length
Type
Description
1
Less... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.13 Download End
| Table 6.5.13.1: Elementary procedure Download End
Name:
DownloadEnd
Code:
0x42
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
Yes
Power mode:
Low
Table 6.5.13.2: Initiating message parameters and format for Download End
Number
Length
Type
Description
None
0 octets
None
No data c... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.5.14 Vendor specific procedure
| Table 6.5.14.1: Elementary procedure Vendor Specific Procedure
Name:
VendorSpecificProcedure
Code:
0x90
Issued by:
Vendor specific
Procedure class:
Vendor specific
DownloadMode state:
Vendor specific
Power mode:
Vendor specific
Table 6.5.14.2: Initiating message parameters and format for Vendor Specific ... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.6 Single-antenna elementary procedures
| |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.6.1 Calibrate
| Table 6.6.1.1: Elementary procedure Calibrate
Name:
Calibrate
Code:
0x31
Issued by:
Primary Device
Procedure class:
1
DownloadMode state:
No
Power mode:
High
Table 6.6.1.2: Initiating message parameters and format for Calibrate
Number
Length
Type
Description
None
0 octets
None
No data carried
... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.6.2 Send Configuration Data
| Table 6.6.2.1: Elementary procedure Send Configuration Data
Name:
SendConfigurationData
Code:
0x32
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.6.2.2: Initiating message parameters and format for Send Configuration Data
Number
Length
Type
Description
1
... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.6.3 Set Tilt
| Table 6.6.3.1: Elementary procedure Set Tilt
Name:
SetTilt
Code:
0x33
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
High
Table 6.6.3.2: Initiating message parameters and format for Set Tilt
Number
Length
Type
Description
1
2 octets
Signed integer
Tilt value
Ta... |
1de16545e4a78484b5596a06529f4503 | 25.463 | 6.6.4 Get Tilt
| Table 6.6.4.1: Elementary procedure Get Tilt
Name:
GetTilt
Code:
0x34
Issued by:
Primary device
Procedure class:
1
DownloadMode state:
No
Power mode:
Low
Table 6.6.4.2: Initiating message parameters and format for Get Tilt
Number
Length
Type
Description
None
0 octets
None
No data carried
Table... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.