Doc.
STG (19)047R1
ECC
CEPT
Electronic Communications Committee
SEAMCAT Technical Group (STG)
Working Group Spectrum Engineering
19–21 June 2019, Telefónica, Berlin, Germany 27 June 2019
Minutes of the 64th STG meeting
1. Opening of the meeting
The 64th meeting of STG took place on 19–21 June 2019 at Telefonica in Berlin, Germany. The STG Acting
Chair, Mr Ivica Stevanovic (OFCOM Switzerland), opened the meeting and welcomed the participants. He
informed the meeting that Mr José Carrascosa was not in a position to continue chairing this project team.
As no candidate was nominated for this position by the CEPT administrations, WGSE agreed to appoint
Mr Ivica Stevanovic as Acting Chairman until the next WG SE in October 2019, in order to ensure the
transition until a new Chairman is designated for STG.
The current official version of SEAMCAT is 5.3.0, released on 6 June 2019.
The list of participants is available in section 23 of these minutes.
2. Approval of the agenda
The agenda as available in document STG(19)043R2 was approved.
The meeting discussed the input documents related to SEAMCAT implementation. The following sections
summarize the discussions and decisions made by STG per topic. Specific action points for STG members
derived from the decisions of the 64th meeting of STG are underlined.
3. System Plugins (SP)
3.1. Generic System
3.1.1. Transmitter bandwidth enhancement (Document STG(19)038)
The currently implemented algorithm for the calculation of the transmitter bandwidth applies the
definition of the ITU Radio Regulations for unwanted emissions (-23 dBc at each side of the centre
frequency of the transmitter). The method ensures that there is no mismatch between transmitter
bandwidth and reception bandwidth (designated as ‘system bandwidth’ in cellular systems). Recent off-
line tests showed that in case the user introduces an emission mask that does not follow this ITU-R RR
definition, the consistency check issues a warning message that may be inaccurate and confusing for
the user. STG#64 agreed that no consistency check warning should be issued (even if the used mask
does not comply with the definition from ITU-R RR), since the mask can still be correct (such as some
masks from ETSI standards). Note that this algorithm is also used in all cellular networks and it would
be good to have this calculation done at one place for all the systems.
Action point: a new patch will be provided by Karl Koch.
1
3.2. OFDMA
3.2.1. Single Tx for 3-sector case (Document STG(19)036)
If the following setup is chosen in SEAMCAT for the interfering transmitter “three-sector (3GPP) – single
cell – single sector”, the interference seems to be computed taking into account all the three interfering
sectors (the entire cell) and not only the selected interfering sector (which would be a preferable
solution). STG#64 performed a quick test with a scenario showing that there is no difference in the
computed interference when one selects “single cell–single sector” or “single cell” only. STG#64 agreed
that there is a need to define clearly what the selection of “single sector” would mean in each case
(single cell, one tier, two tier) at the (interfering) transmitter side.
STG#64 decided to invite stakeholders to discuss about the issues related to the definition and
implementation of a single sector in cellular systems: how SEAMCAT currently deals with single sectors
and what the users would like to have implemented for different options involving the selection of a
single sector. To that aim, a forum topic was opened at the following link:
https://cept.org/ecc/groups/ecc/wg-se/stg/client/forum/topic/552
This forum topic is meant to allow an exchange of ideas and opinions, and to facilitate the decision-
making.
Action point: STG stakeholders are invited to submit contributions to the forum by the deadline set for
the December meeting of STG (STG#65). By that time STG will hopefully have a clear picture and
reach an agreement about the solution to be implemented and documented in SEAMCAT.
This issue is related to the issues reported in sections 3.2.3, 3.2.4, and 3.2.5.
3.2.2. Indoor and outdoor users setting (Document STG(19)037)
STG Acting Chair informed that the feature described in this contribution (to have different antenna
heights for outdoor and indoor terminals) is already implemented in the latest SEAMCAT release
(5.3.0).
3.2.3. Comparison of the SEAMCAT tool official versions 5.2.0 and 5.3.0 (Document
STG(19)044)
Further investigation of this issue is needed. It has to be made sure which version (5.2.0 or 5.3.0) is the
correct one. Some information based on an input document to PT1 shows that the results obtained
using SEAMCAT version 5.3.0 are in line with the 3GPP 36.942 reference results for IMT2020 cellular
network (see Document ECC PT1(19)126, in particular Section 3.2). STG#64 invites the stakeholders
to investigate this issue further and report their findings. This may be connected to the main issue with a
single sector (OFDMA downlink) – which is a bug – that results in simulating only one sector/cell (see
section 3.2.4). That may be the reason why in this contribution there are differences in results for the
same scenario simulated in SEAMCAT versions 5.2.0 and 5.3.0.
3.2.4. OFDMA Downlink calculation (Document STG(19)045)
STG#64 noted the problem. There is a difference in the simulated cellular layout between SEAMCAT
5.3.0 beta 3 and the new release of 5.3.0 for the same setup of OFDMA Downlink calculation. The
examples from Yannick Li (in section 3.2.5) use IMT2020 downlink and in that case the BSs from the
entire interfering network are shown in the layout and taken into account in the calculations. This seems
2
not to be the case for the OFDMA downlink. This is a bug that needs to be resolved. Until then, STG#64
recommends using the IMT2020 Downlink instead, which seems to be implemented correctly.
3.2.5. OFDMA/IMT2020 reference cell and separation distance between reference cells
(Document STG(19)046)
Currently, the correlated distance between two cellular networks is calculated and shown always
between the center of the interfering network A and the reference cell in the victim network B. This
contribution proposes that the distance is always defined between the reference cell in the interfering
network A and the reference cell in the victim network B. STG#64 agreed to introduce this change.
3.3. CDMA
3.3.1. CDMA UL – cell capacity – possible bug (Issue ST-535)
The developer needed clarification on the capacity computation algorithm in CDMA UL. The developer
has checked the code and there have been no changes in this implementation for years. Consequently,
this issue may have existed from the start. However, the algorithm itself seems to be correct. STG#64 is
of the opinion that there is no need to consider any change on this and no reason to consider this as a
bug, unless CDMA experts have different view on this issue. STG needs CDMA experts to further
investigate this issue and provide guidance (see section 3.3.2).
3.3.2. CDMA UL as Interferer simulation outline (Issue ST-446)
At its 59th meeting, STG agreed that a code review was necessary and that liaising with the
stakeholders involved in the implementation of the CDMA module to verify that the current
implementation is correct.
At the 63rd meeting of STG, the group decided to solve this issue when the cleaning of the code for the
CDMA module is scheduled later this year.
As no feedback has been received, STG#64 reiterated the invitation to the stakeholders to have a close
look at this issue and provide feedback to the next STG meeting.
3.4. 5G implementation
No contributions on this topic were received at the 64th meeting of STG.
4. Spectrum Emission Masks (SEM)
4.1. SEM generator (Issue ST-14, Document STG(19)040)
The implementation of this feature is still ongoing. STG#64 noted the bug reported in document
STG(19)040 that would need to be resolved.
5. Receiver Blocking Masks (RBM)
No contributions on this topic were received at the 64th meeting of STG.
6. Antenna Gain Plugins (AGP)
6.1. PreHCM Antenna Management System (Document STG(18)160)
3
At the 62nd STG meeting, Berthold Ruth and Brenda Bogner introduced the PreHCM Antenna
Management System (AMS) proposing a possible future use for SEAMCAT, so that the antenna
patterns in the AMS database in the format BSAS (Base Station Antenna Standardisation) could be
translated into the SEAMCAT format.
The developer of this database, Mr. Michael Hauck, was invited to make an introduction of the AMS
during one of the upcoming STG meeting (either participating in physical meeting or online), indicating
the data format so as to facilitate the specifications for translating data from the AMS into SEAMCAT.
For the time being, Berthold Ruth informed the group about a wide range of the output formats of the
AMS (e.g. MSI, ATOLL, ATOLL Binary, TXT, CSV, JSON, XML).
Due to the indisposition of Mr Hauck for the STG#64 meeting, this point is carried forward to the next
meeting.
Action point: Mr Michael Hauck to provide the specifications of the PreHCM AMS for the next meeting
of STG
6.2. Proposed improvements to antenna gain plot and plotting exporting of results (Issue ST-
531, Documents STG(18)147, STG(18)164 and STG(19)032)
Document STG(18)147 proposes a list of enhancements to SEAMCAT (see also corresponding
sections of the Minutes of the 62nd STG meeting and the Minutes of the 63rd STG meeting).
The first set of enhancements has been implemented in the official release 5.3.0.
6.3. New antenna plugin proposals (Issue ST-532, Documents STG(18)148 and STG(19)031)
STG#64 noted the implementation of the following AGPs:
1. ITU-R F.1336-4 recommends 3.2 (frequencies above 6 GHz). This implementation is completed
in 5.3.0 Beta 2.
2. ITU-R S.465-6 – satellite earth stations from 2-31 GHz. This implementation is completed
in 5.3.0.
7. Propagation model plugins (PMP)
7.1. Discussions on Terrain Data in SEAMCAT (Issue ST-11)
STG has already discussed the possibility of including digital terrain data in SEAMCAT on several
occasions. The latest discussions took place in 2017 and the status of these discussions is reflected in
the minutes of the 57th meeting of STG in document STG(17)125, section 5.5.
Several propagation models within SEAMCAT require terrain data to fully comply with the specifications
for the computation of the transmission loss (e.g., Rec. ITU-R P.452, P.1546, P.2001). Terrain and
clutter data would allow computing the transmission loss for real-life scenarios that are needed in some
sharing and compatibility studies (e.g., RLAN-FS sharing for real-life fixed links as done in SE45) and
some of the propagation models require terrain data to produce realistic values of transmission loss.
Noting that there is a request from IARU for having this feature in SEAMCAT and that most work has
already been done, STG#63 decided to raise this topic again and seek approval from WG SE to move
forward with the proposal.
STG#63 also discussed the possible risk of manipulating results through the terrain data. Therefore,
specific guidelines on how to use terrain data and how to prevent misuse of SEAMCAT should be done,
4
for example by allowing a visual check of the terrain data or allowing only a predefined set of
representative terrain profiles.
A new work item STG_07 was created at the 82nd WG SE meeting in May 2019 on the inclusion of
terrain data in SEAMCAT with a support from 12 CEPT administrations. STG#64 noted this decision.
This item has been included in the SEAMCAT Roadmap for 2020. The necessary work will be further
discussed and planned.
7.2. PMP applying ITU-R P.1238-9 (indoor–indoor) (Documents STG(19)034, STG(19)034A1,
STG(19)034A2)
STG#64 agreed that the implementation of Recommendation ITU-R P.1238-9, as provided in document
STG(19)034 and the related annexes, needs to be tested. After considering any feedback from STG
stakeholders, the model can be introduced in the SEAMCAT source code. The plugin provided by Mr
Karl Koch can already be imported in SEAMCAT for testing and use. See also section 12.2.
7.3. Extension of validity of the propagation model ITU-R P.1546 (Issue ST-540, Documents
STG(19)039 and STG(19)039A1)
STG#63 agreed to include a line in the event results pane, in the section “selected point”, below
“antenna height”. This new parameter will be called “Effective antenna height (ITU-R P.1546-5)”. The
units are in meters [m], and it will appear only for transmitters (VLT or ILT) and only if the P.1546-5 is
used. STG#63 also agreed to add a mouseover box on the parameter “terrain height above sea level
around the Tx” saying the following:
“This parameter is used in combination with the antenna height (from the transmitter local
environments) and the average profile height around the Tx to compute the effective antenna height.”
Finally, STG#63 agreed to add a consistency check if the user tries to apply ITU-R P.2108 together with
P.1546, which would mean that clutter loss is accounted for twice, as P.1546 inherently computes
clutter loss due to the differences in Tx/Rx antenna heights and the height of representative clutter
around Tx/Rx.
A contribution in documents STG(19)039 and STG(19)039A1 from OFCOM CH provided these updates
in a patch for the mouseover text and the consistency check for the combined use of P.2108 and
P.1546. These are implemented in the new release of SEAMCAT 5.3.0.
The STG Acting Chair provided an update on the revisions of the relevant ITU-R P-Series
Recommendations ongoing in SG 3. Once the revisions are published during the course of this year,
there will be a need to update the following propagation models in SEAMCAT: ITU-R P.452, ITU-R
P.1546, ITU-R P.2001, ITU-R P.1411, and ITU-R P.1238.
8. Event Processing Plugins (EPP)
The renaming of all EPPs from „Demo #“ to „EPP #“ and the redrafting of EPP names to make more explicit
was completed in 5.3.0 Beta 2 and is now available in the newest release 5.3.0.
8.1. EPP#8 enhancements (Issue ST-516, Document STG(19)041)
The STG Acting Chair confirmed that the implementation of this Issue is completed in v5.3.0.
5
STG#64 discussed the additional proposals in document STG(19)041 on the collected vectors
according to the distance. STG#64 agreed that the third option (keep EPP-8, but re-define it according
to the proposal in this contribution) is the one to be implemented in SEAMCAT.
Action point: a new patch will be provided by Karl Koch.
8.2. EPP#11 enhancements (Issue ST-498, Document STG(19)018)
At the 63rd STG meeting, STG chairman confirmed that the implementation of this Issue is completed
in v5.3.0 Beta 2.
STG 63 discussed the additional proposals in document STG(19)018, concluding that the advantage of
having the same vector names in the event results pane and in the collected vectors is greater than the
disadvantage of having some collected vector values of -1000, as in EPP#8 above.
Action Point: A new version of EPP#11 will be provided by Karl Koch to provide the antenna angles.
9. Libraries
No contributions received on this topic at the STG#64 meeting.
10. Intermodulation (IM) calculations plugin (Issue ST-391, Document STG(18)093)
STG#61 took note of the creation of the Forum Group on Receiver Intermodulation and agreed to actively
participate in the discussions within the FG, in particular making sure that the algorithm discussed can be
implemented in SEMCAT (i.e. system level simulation).
The final implementation of the intermodulation algorithm will be done after agreement in WG SE.
Therefore, no action was taken on this issue on the 63rd meeting of STG.
STG Acting Chair informed about discussions that took place at the 82 nd WG SE meeting in Prague,
proposing to align activities on receiver intermodulation (currently ongoing in SE21 and in the FG) by
merging FG within SE21. Mr Ladislas Loughin informed STG#64 about the current activities on the
intermodulation simulations in RMR studies within SE7.
11. Graphical User Interface (GUI) (Issue ST-4)
At the 64th STG meeting, it was confirmed that the implementation of this Issue is completed in 5.3.0.
11.1. Missing correct Power Parameter in Outline Tool Tip (Issue ST-541, Document
STG(19)029)
During the 63rd STG meeting, Berthold Ruth reported that there was a bug when IMT2020 is simulated:
the transmitted power is not reflected in the mouseover box in the simulation outline.
The bug has been corrected in the official release 5.3.0.
6
12. Positioning of elements
12.1. Finite dataset distribution (Issue ST-2, Documents STG(18)128+Annexes, STG(18)129,
STG(18)130, STG(18)131+Annex, STG(18)133, STG(18)135+Annex, STG(18)138+Annexes)
STG 61#1 agreed to test the implementation made by Béatrice Martin (Thales) in doc. STG(18)124A1
and come back to the 62nd meeting with comments /questions.
For the 62nd meeting of STG, Béatrice provided some examples of finite datasets to be used with
cellular modules in doc. STG(18)128 and an update of the finite dataset implementation in document
STG(18)138A1, taking into account the comments provided by Karl Koch in documents STG(18)129,
STG(18)130, STG(18)131 and STG(18)133.
Due to the changes made in 5.3.0 Beta 2 regarding the use of distributions in the frequency parameter
for cellular systems, Thales’ implementation of the finite dataset needs to be modified.
Action Points carried forward to STG#65:
- Béatrice Martin to look at 5.3.0 at its release and verify if there is any need to adapt the finite
dataset implementation.
- STG members to run simulations with the finite dataset implementation in document STG(18)138A1
and provide feedback to the 64th meeting of STG.
No contributions were received at the 64th meeting of STG, therefore the discussions on this topic are
on hold. This issue still pending and awaiting action point results.
12.2. Manhattan Grid (Issues ST-10, ST-32, Forum discussions, Document STG(19)030)
Based on the request in document STG(19)030, STG 63 provided the following guidance to ENSEA
students:
The input parameters (% of users indoor /outdoor and their associated antenna heights) need to
be taken from the Local environments in the workspace to be used as input to the Manhattan grid. A
check needs to be done on the height of the indoor users in order to ensure that all of them can be
positioned indoors in the Manhattan grid.
Regarding the questions on propagation models:
- Indoor-indoor (within the same building): Recommendation ITU-R P.1238-9 “office
environment” is the most complete, but still only valid for a discrete range of frequencies. If the
user chooses to simulate in a frequency outside of the range specified in the recommendation,
the equations are still valid, but there is no guarantee on the accuracy of the computation,
because the recommendation only provides parameter values for the range of frequencies
defined there. Therefore a warning should be generated so that the user is informed that there
might be some inaccuracies in the simulation due to the choice of frequency for the simulation.
Karl Koch provided a draft of this PMP during the meeting and it is uploaded as document
STG(19)034, STG(19)034A1, STG(19)034A2 for the 64th meeting of STG in Berlin.
Action Point carried forward to STG#65: Feedback on this external PMP is expected as soon as
possible and before the 65th STG meeting from Heykel Houas and ENSEA students.
- Indoor-indoor (in different buildings): Outdoor-Outdoor PMP combined with two times P.2109
for the building entry loss computation (one for each building).
7
- Indoor-outdoor: site specific PMP (e.g., a version of P.1411) combined with P.2109 for the
building entry loss computation.
Action Point carried forward to STG#65: ENSEA students to provide an implementation of this
PMP.
All the PMPs will be chosen in a menu within the Manhattan grid window, but they will be
implemented as a separate library item, accessible in the PMP library.
12.3. Clarification of the coverage radius (ST-526)
The correction of the consistency check was implemented in 5.3.0 Beta 2 and now available in the
official release 5.3.0.
Action Point: To modify the implementation so that the values of the workspace are used during the
simulation.
12.4. Deployment of Networked SRDs in SEAMCAT (Document STG(18)150)
STG 62 indicated that the options „To position with“ and „Generate multiple interferers“ might be the
solution for the positioning difficulty highlighted by the French contribution. An alternative option would
be to use finite dataset distributions for the positioning of the transceivers. Document STG(18)138A1
(Thales) contains a modified version of SEAMCAT containing the possibility to use finite dataset
distributions.
Action point for STG 62: Ladislas Loughin to explore these options and to assess if the solutions
proposed above solve the difficulties outlined in document STG(18)150.
Action point for STG 64: Ladislas Loughin will provide feedback to STG after the next SE24 meeting.
The two action points above are carried forward to STG#65.
13. Interference Calculation Engine (ICE)
13.1. Improvements to the translation mode (Documents STG(18)058+Annex)
At its 61st meeting, STG still did not receive any proposal to assess the confidence interval for the post-
processing of the calculation of the probability of interference by establishing an exclusion zone around
the VLR. STG decided to give more time and come back to this issue at a future STG.
No contributions were received at the 62nd, 63rd or 64th meeting of STG.
14. Link Budget Calculator (LBC) (Issue ST-507)
A first version of the LBC is available for testing starting from 5.3.0 Beta 3.
STG#63 proposed the following additions:
1. Display the values of local environments (including antenna heights) for ILT and VLR that are taken
from the workspace
2. Display the name of the antenna pattern for the ILT and VLR taken from the workspace
3. Display the RBM of the VLR and the SEM of the ILT taken from the workspace
8
Action point carried forward to STG#65: Ivica Stevanovic will send a list of further improvements to the
tool.
15. Tools
15.1. Vector Scatter plot (Document STG(19)042)
STG#64 agreed to implement the proposed improvement to the way vectors and functions are shown in
the Compare vectors and functions tool. It was agreed to suppress the legend – similar to the vector
diagrams – if more than 10 scatter diagrams are selected, as proposed in this contribution.
16. Documentation
16.1. Updates to the SEAMCAT Handbook (online manual, Issue ST-18, Document STG(19)016)
No contributions received at the STG#64.
Action Point carried forward to STG#65: Ivica Stevanovic will provide updates to Annex 17 (i.e.
extension of the range of validity of ITU-R P.1546 up to 6 GHz and modification of ITU-R P.452 to
account for 3-D Tx-Rx distance in free space transmission loss for shorter Tx-Rx distances).
16.2. Update to the manual for Cognitive Radio
At the 59th STG meeting, the group was made aware of the current documentation on the Cognitive
Radio manual (2010). This documentation might require updates to match the current SEAMCAT
versions. Updates to the documentation will be made if there is a need for that (e.g. the module is used
in WG SE PTs for compatibility studies).
No contributions were received on this topic up to the 64th meeting of STG.
STG members are invited to have a close look to the Cognitive Radio handbook.
16.3. Review of list of action points from the 63rd meeting of STG (Document STG(18)164)
STG reviewed some of action points from the 63rd meeting of STG and established new action points.
17. Simulation performance
17.1. Multi-threading in Ubuntu OS (Issue ST-448)
At the 59th STG meeting, the group agreed to move this issue to a low priority due to the fact that no
other bug report has been submitted from SEAMCAT users with OS Ubuntu.
This issue is still pending to be developed.
17.2. Determination of the amount of memory necessary for a simulation (Issue ST-15) and
estimation of the time necessary to run a simulation (Issue ST-16)
At the 59th STG meeting, the group agreed that, in order to have an estimation of the memory and time
necessary to run a simulation, the user could run a simulation with few events and look at the allocated
memory in the simulation bar, and the time elapsed during the simulation in the results tab. A FAQ
could be added to indicate how to do that with screen prints.
9
In the meantime between the 59th and 61st STG meetings, discussions with the developer indicated that
a button could be added in SEAMCAT to perform this estimation, but its implementation is shifted to
2019.
As the implementation of these two issues is to complex and costly for the benefit it would bring,
STG#64 agreed to drop these two issues.
17.3. Detection of the wrong JAVA version in user’s computers (Issue ST-366)
At the 59th STG meeting, the group agreed that, if it is possible for SEAMCAT to check the version of
JAVA installed in the user’s PC, then a warning could be displayed if the JAVA version is not
compatible with the current SEAMCAT version. If it is not possible, the Issue will be dropped and a FAQ
question / reply to address this issue will be added.
This issue is still pending to be developed.
18. Issue tracking and status on testing in JIRA.
Action point: STG Acting Chair will review and update the Kanban board in JIRA to reflect the decisions
taken during the 64th meeting of STG.
19. Roadmap of SEAMCAT development
STG#64 reviewed the Roadmap for SEAMCAT development for 2019 and drafted the Roadmap for the
year 2020 available in STG(19)047A1. STG#64 agreed to present the new Roadmap to the 83rd WG SE
meeting (30 September – 2 October 2019) in order to obtain WG SE support during that meeting.
20. Next meetings
The following are the dates and venue for the upcoming STG meetings. Invitations to these meetings will
be uploaded in the STG document area as soon as they are received:
STG #65: 12–13 December 2019 at ANFR, Maisons-Alfort, France.
STG#66: March 2020, ENSEA, Cergy Pontoise, France
STG#67: June 2020, Telefonica, Berlin
21. Any other business
Mr Yannick Li (Orange) pointed out that feeder loss is missing in the list of parameters in SEAMCAT. The
proposal is to include this parameter in the transmitter parameter list. There may be some workarounds that
can be used at the moment (such as reducing the transmitter power level by the value of feeder loss at the
Tx side). STG#64 agreed that this is a necessary enhancement. There will be a contribution and an offline
exchange in which more details will be given on how to include the feeder loss in link budget equations.
Mr Ralf Schuh (Ericsson) introduced a document STG(19)035 proposing some improvements for better test
functionalities in SEAMCAT, including a possibility to control also the position of the UEs within the cellular
network. This could be useful in testing and in simulating fixed wireless access systems as well. STG#64
discussed the issue. No actions to be taken at this point in time.
During the meeting it was pointed out that sufficient technical specifications do not seem to be always
provided to the developer and consequently more time is necessary to have the proposed feature correctly
10
implemented in SEAMCAT. It was pointed out that a flowchart that defines the whole process of submitting
the contribution, writing technical specification, testing after the feature is implemented, giving feedback,
testing after readjustments made, and finally writing a sufficiently detailed help file would be very useful.
Such a flowchart would need to be followed with every new bug or enhancement implementation in
SEAMCAT.
22. Closure of the meeting
The STG Acting Chair expressed his sincere thanks to all participants in the Project Team STG for their
hard work, enthusiasm, expertise, and spirit of cooperation. Particular thanks were given to Ms Brenda
Bogner and Telefonica for providing the venue and organizing the meeting. The meeting was closed on 21
June with a round of applause.
23. Participation
In addition to the Acting Chair, five delegates attended the physical meeting and one delegate attended the
meeting using the web meeting facilities.
Name Represented Entity Participation
Ivica Stevanovic OFCOM CH Physical meeting
Brenda Bogner Telefonica Physical meeting
Ladislas Loughin ANFR Physical meeting
Berthold Ruth PreHCM Services GmbH Physical meeting
Karl Koch - Web meeting
Ralf Schuh Ericsson Physical meeting
Yannick Li Orange Physical meeting
Ivica Stevanovic
Federal Office of Communications
OFCOM Switzerland
STG Acting Chair
_________
11
