SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Nokia Corp. (NOK)
NOK 6.435+0.5%Jan 21 3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: 49thMIMOMander who wrote (1280)9/9/2001 12:22:36 PM
From: Eric L  Read Replies (1) of 9255
 
re: GPRS PBCCH/PCCCH functionality (initial feature set) IOT discussion

Progress on what some would call a "Nokia Issue", but in reality a 3GPP Geran TSG issue that Nokia fortuitously flagged in May 2001:

Tdoc GP-011914

3gpp.org

From Naantali, Finland (Agenda Item 6.6) 27 to 31 August, 2001

>> Recommended Feature Set for IOT Testing of the R97 GPRS PBCCH/PCCCH Functionality

Source: Alcatel, Ericsson, Motorola, Nokia, Nortel, Sagem, Siemens

Provided for: information and discussion

1. Introduction

The supporting companies have recognised that the overall success of General Packet Radio Service (GPRS) is heavily dependent on multiple mobile station and network vendors being able to consistently test features and deploy interoperable products in the market.

Last week some manufacturers met in Copenhagen to discuss the testing issues regarding PBCCH/PCCCH functionality and evaluate proposals to help accelerating the adoption and evolution of GPRS services, and the speed with which products are brought to the market.

The outcome of the meeting consists in the following proposal:

- there will be no change to the existing release 97 GPRS standard, i.e. release 97 compliant mobile stations shall implement the whole release 97 set of mandatory features

- as an initial step, manufacturers will submit a recommended set of R97 PBCCH/PCCCH features that shall be IOT tested. Based upon that list, a common set of interoperability tests will be defined fully utilising the capability within each infrastructure manufacturer

- as a second step, the industry will develop an effective process to quickly address any interoperability issues that may arise as new functionalities are activated in the networks

2. Agreed recommended set of features

2.1 Decision process

It was agreed that, for a feature to be part of the recommended set, the following conditions should be met:

- it improves the packet signalling performance and provides a good business case for the operator

- it can be tested now against at least two network manufacturers in their IOT laboratories

Note: the inclusion of a feature in this list assumes that it will be testable through test cases validated by the GSM Certification Forum (GCF) before the end of September 2001.

2.2 Recommended set

According to the above decision process, the following list has been agreed:

- NMO I
- NMO III
- Multiple PCCCH (*)
- Hopping PBCCH
- Hopping PCCCH
- Hopping PDTCH
- C31 / C32
- NC0
- Multiplexing of PBCCH/PCCCH and PDTCH/PACCH
- PSI scheduling
- Variable PBCCH/PCCCH mapping
- HCS parameters
- SPLIT_PG_CYCLE
- Non-DRX mode

(*) Still under discussion: there was wide acceptance among the supporting companies that this feature should be part of the recommended set; however, only one network manufacturer could offer testing capability at present.

In order to ensure fast IOT testing of the features in the recommended set, the following actions are on-going:

- a list of parameters that should be used to configure the network during those tests is being elaborated

- a list of test cases corresponding to those features will be submitted to the GSM Certification Forum as early as possible.

3. Conclusion

The supporting companies elaborated this recommended set bearing in mind the customers’ demands and expectations. Any input to facilitate and improve this IOT testing process is welcome. <<

- Eric -
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext