hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
8a9283a656db20cd080be5c53231664c | 23.922 | 7.1.2 All IP UTRAN to All IP ERAN Handover | The need to support this handover scenario is for FFS.
In this scenario, a CSCF will support terminals in both the ERAN and the UTRAN. The terminal will have access to the same Media Gateway from both RANs, hence the same media codec will be used in the network. |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.2 SRNC Relocation/Handover Between All IP and CS Domain/GSM | |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.2.1 Requirement | The need to support these handover scenarios is for FFS.
The expected scenarios:
• Inter system handover, where target system does not support the necessary RT requirements for its packet domain (e.g. Inter system hand-over towards R97)
To fulfill this potential requirement, 2 solutions have been currently proposed (ot... |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.2.2 Solution with CSCF supporting MAP E | The following text considers the scenario when a UE has at least one session active which involves the CSCF.
On receipt of an SRNC relocation required message, the SGSN determines that the SRNC relocation results in a change of SGSN to one, which does not support the All IP services. One option is to force the serving... |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.2.3 Inter-System handover using the ISHF | The mechanism described in this section, identifies a new functional element, the ISHF. This isolates MAP/E from the CSCF. Further work is required to identify if this approach, or the approach of supporting MAP/E on the CSCF (see section 7.2.2) should be adopted. |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.2.3.1 General | Based on the handover requirements given in Table 4-1, the following intersystem handover scenarios should be accommodated by the All IP architecture.
• UMTS R 00 IP network to/from 2G GSM network handover
These procedures listed shall not require change to the terminal.
Figure 7-1: Support of InterSystem Handover
To s... |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.2.3.2 UMTS R 00 IP network to/from 2G network handover | This example shows how handover (Hard Handover) is performed from UMTS R 00 IP network to a legacy GSM network. This demonstrates the signaling required between the networks and assumes a trunk circuit bearer between the networks. Other bearer connection schemes are possible, but not addressed in this example. (Note ... |
8a9283a656db20cd080be5c53231664c | 23.922 | 7.3 Areas for Further Study | The following areas may require further study.
• Bearer set-up/control between networks during handover
• Anchoring bearer in the UMTS R 00 IP network
• MAHO support
• Inter-RNC Soft handover
• Inter RAN to RAN of same type streamlining
• Inter RAN to RAN of different type streamlining |
8a9283a656db20cd080be5c53231664c | 23.922 | 8 Radio Aspects | Note: This section requires support from the RAN group. |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.1 General | 1) CN – RAN interface definition
(a) Functional split between CN and RAN- new radio access network called EGPRS Radio Access Network (ERAN) is considered. The interface between the radio access network such as ERAN or UTRAN and the CN needs to be defined/extended and should allow different air interface technologies t... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2 Airlink Optimisation for Real-Time IP | |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.1 Introduction | In the all-IP architecture, a fundamental objective is to support IP-based real-time and non real-time traffic for a mobile terminal while achieving spectral efficiency and error robustness. In the case of real-time voice, spectral efficiency and error robustness have a performance baseline coming from the current cell... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.2.1 Full opacity (no adaptation) | The UPA has no knowledge of the internal structure of the headers or payload, and no transformation is done on the IP/UDP/RTP headers which are sent in full over the air interface. Error protection is applied evenly to all the bits in the header, and evenly to all the bits in the payload. The header part will likely re... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.2.2 Payload opacity (header adaptation only) | In this case, the UPA only needs to know the internal structure of the IP/UDP/RTP header but not of the payload. Only the headers are adapted, either by header compression or header stripping. |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.2.2.1 Header compression/decompression | IP/UDP/RTP headers are compressed before transmission over air interface and decompressed at the receiving end. Like before, headers require stronger error protection than payload. The most wellknown header compression algorithm is the Van Jacobson algorithm (RFC 1144, Compressing TCP/IP Headers for low speed serial li... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.2.2.2 Header stripping/regeneration | IP/UDP/RTP headers are stripped before transmission over air interface and regenerated at the receiving end. Essentially only the payload is transmitted, but some additional header-related information needs to be transmitted to enable the header regeneration. The degree of header transparency achieved is variable, depe... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.2.3 No opacity (full adaptation) | The UPA knows the structure of the headers and the payload. Headers can be compressed or stripped. In addition, payload transmission is optimised by techniques such as unequal bit protection, channel and error coding optimised for the payload structure, etc. |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.3 Application to all-IP network | The all-IP network is expected to provide real-time bearer services intended to carry
• Basic conversational voice (service equivalent to voice in current cellular)
• Real-time Multimedia (includes voice which is seen as a component of multimedia) |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.3.1 Basic voice | For basic voice, the emphasis is on meeting and if possible exceeding the baseline of traditional cellular in terms of spectrum efficiency, error robustness and voice quality. Traditional cellular systems achieve that baseline by using well known techniques such as unequal bit protection, channel and error coding optim... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.3.2 Real-Time multimedia | Real-time multimedia is a new service that does not exist in traditional 2G cellular systems. A new bearer is proposed. For that bearer, transparency for all the IP/UDP/RTP fields is crucial. Under the transparency constraint, we want to optimise spectrum efficiency and error robustness, but unlike voice, there is no b... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.3.3 Pure IP | The Pure IP service can be provided to accommodate end-to-end protocols such as IPSEC. In order to achieve this accomodation, the bearer does not do any adaptation and corresponds to the "No adaptation" case above. Header adaptation may also apply for Pure IP. Specific algorithms for header adaptation shall be evalua... |
8a9283a656db20cd080be5c53231664c | 23.922 | 8.2.4 Conclusions | IP/UDP/RTP packets require adaptation to the radio link to meet the spectrum efficiency and error robustness requirements of cellular systems. It shall be investigated if a single scheme can simultaneously and fully meet the above requirements and IP transparency. An alternative to a single scheme is a gradation of sc... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9 Call Control | 9.1 Terminology for Call Control
The terminology in this section is that terminology used that is new or has been changed from that defined for R99. The terminology defined in this section has not been the object of a real debate and hence cannot be considered as agreed. This section needs to be aligned with the term... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.2 Assumptions | The following assumptions have been considered in the development of the roaming models described in the present version of the document.
1 The addressing requirements and mechanisms will be based on the requirements and mechanisms identified by 3GPP in 3G TR 22.975 and 3G TS 33.003.
2 Call admission/denying and call r... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3 Roaming Within All IP networks | In the follow, a set of roaming scenarios is described.
Editor's Note: please note that the network interfaces and the names shown in the diagrams from 6.4 to 6.7 may not always be correct. |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.1 Call Model | The call model described by the following statements has been adopted in the present document:
• Calls from/through PSTN are routed to an MGCF with connectivity to the Home Network corresponding to the dialled DN.
• Calls from a Release 2000 all IP network to a different Release 2000 all IP networks originated with a D... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.2 Scenario 1, Traditional Model | The following pictures show respectively the roaming scenario 1 applied to roaming inside a single network and applied to roaming between networks.
Figure 9-2: Scenario 1 applied to roaming inside a single network
Figure 9-3: Scenario 1 applied to roaming between networks
The following points characterise scenario 1:
•... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.3 Scenario 2 | The following pictures show respectively the roaming scenario 2 applied to roaming inside a single network and applied to roaming between networks.
Figure 9-4: Scenario 2 applied to roaming inside a single network
Figure 9-5: Scenario 2 applied to roaming between networks
The following points characterise scenario 2:
•... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.4 Scenario 1: Information Flows for Validation | In order to validate scenario 1 proposed above, information flows for registration, location management and call delivery/origination are provided in this section.
The information flows presented in the Call Control and Roaming proposal do not provide many details. Generic names have been chosen for signalling messages... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.4.1 Registration and Location Management | • In this version of the Technical Report, only a basic registration procedure is considered.
• The basic registration procedure is composed of three steps:
• GPRS attach: is a plain GPRS attach procedure;
• PDP context activation: a PDP context is set up to support application level signalling;
• application level reg... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.4.2 MT/MO Calls | Two call information flows are presented in this version of the Technical Report. The call flows are based on the following call delivery model:
• a call from PSTN towards a DN corresponding to the user is received by one of the MGCF of the Home Network, ISP or corporate LAN domain in the IP multimedia network;
• MGCF ... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.4.2.1 Incoming call from PSTN to a Release 2000 all IP network | The following flow describes the call delivery for a MT call from PSTN to a Release 2000 all IP network user addressed through a DN.
Figure 9-7: Incoming call from PSTN to a Release 2000 all IP network
Issues such as QoS negotiation, policy management, etc. are FFS. |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.4.2.2 Call from an 3GPP IP based network/Multimedia IP Network to 3GPP IP network | The following flow assumes that a Release 2000 all IP network user has roamed into a visited network. The flow describes a call from a different Release 2000 all IP network terminated into the home domain of the called user. It is assumed that the Release 2000 all IP network where the call is coming from, is aware of ... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.3.5 Scenario 2: Information Flows for Validation | No flow will be shown for this version of the document. |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.4 Roaming to Other Networks | In order to ensure compatibility and easy roaming between 2G GSM/GPRS, UMTS R99 and UMTS R00 CS and GPRS domain (excluding the VoIP/multimedia domain), the same mobility procedures are used within and between the 3 kind of networks (storage of the current location in the HSS, use of MAP to update the HSS with the curre... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.4.1 Roaming Procedures for R00 networks | One possible solution for the support of roaming in R00 networks is described in Tdoc S2k99117. The contribution covers both roaming between R00 networks and roaming to mobile legacy networks. The contribution only covers the PS-only architecture in UMTS R00. Roaming from UMTS R99 considered in this document is in term... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.4.2 Overlaid solution to roaming | One roaming solution is to introduce an overlaid personal number service, which keeps track of users registrations (attached to 2G/3G CS and/or PS MultiMedia) and call reception preferences. This enables inter-service as well as inter network roaming for Telephony as classical TeleService Speech in 2G/3G networks and T... |
8a9283a656db20cd080be5c53231664c | 23.922 | 9.5 Open Issues | The following issues need to be discussed and solved through interaction with the other working groups in Release 2000 all IP network and might require discussion in the plenary.
• Support of multiparty voice and data communications sessions (including the capability for the user or service logic to dynamically add or ... |
8a9283a656db20cd080be5c53231664c | 23.922 | 10 Service Platform Impacts | |
8a9283a656db20cd080be5c53231664c | 23.922 | 10.1 3GPP Release 2000 Service Architecture | This section describes how the 3GPP release 99 service architecture [3] can be applied to the 3GPP release 2000 network by extending the VHE/OSA concept to the Multi-Media core network. This can be done by providing an application interface (as described in VHE specification [3]) from the CSCF, see Figure 10-1.. As VH... |
8a9283a656db20cd080be5c53231664c | 23.922 | 10.2 IN based Services | The IN based service is one example of legacy services and the IN based service logic is one example of how legacy services may be introduced to the 3GPP Release 2000 networks. This IN based service logic may need to be enhanced in 3GPP Release 2000 networks, based on the proposed architecture, when full support for ... |
8a9283a656db20cd080be5c53231664c | 23.922 | 10.3 Issues requiring further contributions | The following issues require further contributions:
• Applications may reside not only in Application Servers (AS) but also in terminals.
• Options for sharing applications or parts of them between AS and terminals
• Which elements, beside the CSCF, will provide API for application design (aligned with VHE/OSA)
• Termi... |
8a9283a656db20cd080be5c53231664c | 23.922 | 11 Security | There will be a common authentication scheme for the terminals operating in the all-IP mode, which will be SIM/USIM based. It is required that all-IP terminals will be able to register and provide basic service when used with a 3GPP SIM/USIM.
12 Work Plan |
8a9283a656db20cd080be5c53231664c | 23.922 | 12.1 Milestones for Release 00 | 3GPP has the objective of producing the second release of specification for UMTS by the end of 2000. The project management for this work will need to include the elements of work package definition, the interdependency of these work packages and their scheduling. As the work is undertaken in the various TSGs and WGs i... |
8a9283a656db20cd080be5c53231664c | 23.922 | 12.1.1 Release 00 milestones | 3GPP has not yet agreed overall milestones for release 00. For the purposes development of a high-level work plan the following key milestones are proposed.
July 99 3GPP All-IP network feasibility study started
Sept 99 TSG-S2 R00 Ad Hoc will submit the results of the TSG-S2 for approval
Oct 99 After TSG-S2 approval,... |
8a9283a656db20cd080be5c53231664c | 23.922 | 12.1.2 Detailed activity plan | Date
Meeting group
Proposed activity
August 23 – 27
S2
Progress architectural study
September 13 - 17
S2
Joint S1 – S2 activity on R00 - Finalize the requirements for the architectural study and identify the key issues. Finalize the proposed R00 architecture at the TSG-S2 R00 ad hoc group.
Late September/early October... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 1 Scope | The present document specifies the overall requirements for 3G Fault Management as it applies to the NE, EM and NM.
Clauses 4 and 5 define the fault management concept and functional requirements for the detection of faults and the generation, collection and presentation of alarms, operational state data and test resul... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 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... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 3 Definitions and abbreviations | |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply:
Active alarm: an alarm that has not been cleared. An alarm is active until the fault that caused the alarm is corrected and a clear alarm is generated
Alarm: an alarm is an abnormal network entity condition which categorises an event a... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply:
CCITT The International Telegraph and Telephone Consultative Committee
CM Configuration Management
CMIP Common Management Information Protocol
CMIS Common Management Information Service
CMISE Common Management Information Service Element
EIR E... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4 Fault Management concept | Any evaluation of the network elements' and the overall network health status will require the detection of faults in the network and, consequently, the notification of alarms to the OS (EM and/or NM). Depending on the nature of the fault, it may be combined with a change of the operational state of the logical and/or ... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1 Faults and alarms | Faults that may occur in the network can be grouped into one of the following categories:
• Hardware failures, i.e. the malfunction of some physical resource within a NE.
• Software problems, e.g. software bugs, database inconsistencies.
• Functional faults, i.e. a failure of some functional resource in a NE and no har... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.1 Fault detection | When any type of fault described above occurs within a 3G network, the affected network entities must be able to detect them immediately.
The network entities accomplish this task using autonomous self-check circuits/procedures, including, in the case of Nes, the observation of measurements, counters and thresholds. Th... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.2 Generation of alarms | For each detected fault, appropriate alarms shall be generated by the faulty network entity, regardless of whether it is a steady or unsteady fault. Such alarms shall contain all the information provided by the fault detection process as described in subclause 4.1.1.
In order to ease the fault localisation and repair, ... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.3 Clearing of alarms | The alarms originated in consequence of faults need to be cleared. To clear an alarm it is necessary to repair the corresponding fault. The procedures to repair faults are implementation dependent and therefore they are out of the scope of the present document, however, in general:
• the equipment faults are repaired b... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.4 Alarm forwarding and filtering | |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.5 Storage and retrieval of alarms in/from the NE | For fault management purposes, each NE will have to store and retain the following information:
• a list of all active alarms, i.e. all alarms that have not yet been cleared; and
• alarm history information, i.e. all notifications related to the occurrence and clearing of alarms.
The storage space for alarm history in ... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.6 Fault Recovery | After a fault has been detected and the replaceable faulty units have been identified, some management functions are necessary in order to perform system recovery and/or restoration, either automatically by the NE and/or the EM, or manually by the operator.
The fault recovery functions are used in various phases of the... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.7 Support of Maintenance Action | |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.1.8 Configuration of Alarms | |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.2 State management | The State Management is a common service defined within Configuration Management (TS 32.106) and used by several management areas, including Fault Management. In this clause, some detailed requirements on State Management as they apply to the Fault Management are defined.
From the point of view of Fault Management, onl... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.2.1 Propagation of state change | Within a managed element, when for any reason a resource changes its state, the change must be propagated, in a consistent way, to all the other resources that are functionally dependent on the first one. Therefore:
• In case of a fault occurring on a resource makes that resource completely out of service, if the curre... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 4.3 Test management | x Fault management requirements
This clause defines the FM requirements from the OS's perspective. According to the concept described in clause 4, the NEs shall maintain alarm and state change information. This information shall then be forwarded to one or more OS(s), i.e. the OMC and/or NMC. The OMC's role to play in ... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5 N interface | |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.1 Fault Management concept of Itf-N | An operations system on the network management layer (i.e. the NM) provides fault management services and functions required by the 3G operator on top of the element management layer.
As pointed out in clause 5, the N interface (Itf-N) may connect the network management system either to EMs or directly to the NEs. This... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.2 Management of alarm and state change event reports | |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.2.1 Mapping of alarm and related state change event reports | The alarm and state change reports received by the NM relate to functional objects in accordance with the information model of Itf-N. This information model tailored for a multi-vendor capability is different from the information model of the EM-NE interface (if an EM is available) or from the internal resource modelli... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.2.2 Real-time forwarding of event reports | If the Itf-N is in normal operation (the NM connection to the subordinate entities is up), alarm and related state change event reports are forwarded in real-time to the NM via appropriate filtering located in the subordinate entity. These filters may be controlled either locally or remotely by the managing NM (via Itf... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.2.3 Alarm clearing | On the Itf-N, alarm reports containing the value "cleared" of the parameter perceivedSeverity are used to clear the alarms. The correlation between the clear alarm and the related active alarms is performed by means of unambiguous identifiers.
This clearing mechanism ensures the correct clearing of alarms, independentl... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.3 Retrieval of alarm and state information | The retrieval of alarm and state information comprises two aspects:
a) Retrieval of current information
This mechanism shall ensure data consistency about the current alarm/state change information between the NM and its subordinate entities and is achieved by means of a so-called synchronisation ("alignment") procedur... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.3.1 Retrieval of current alarm information on NM request | The present document defines a flexible, generic synchronisation procedure, which fulfils the following requirements:
• The alarm information provided by means of the synchronisation procedure shall be the same (at least for the mandatory parameters) as the information already available in the alarm list. The procedure... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.3.2 Retrieval of current state change information on NM request | The requirements defined above for the alarm synchronisation procedure are valid analogously for the retrieval of current state change information as well.
Nevertheless the state change synchronisation procedure takes into account only the object instances whose state information is different from a combined default st... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.3.3 Logging and retrieval of alarm and state change history information on NM request | The alarm/state change history information may be stored in the subordinate entities in dependence on the NM requirements. The NM is able to create logs for alarms/state change event reports and to define the criteria for storage of alarm/state change information according to [11].
The subsequent retrieval of stored in... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.4 Co-operative alarm acknowledgement on the Itf-N | The acknowledgement of an alarm is a maintenance function that aids the operators in his day to day management activity of his network. An alarm is acknowledged by the operator to indicate he has started the activity to resolve this specific problem. In general a human operator performs the acknowledgement, however a ... |
98d280e9ebdd62e62b9d51749d594208 | 32.111 | 5.5 Overview of IRPs related to fault management | The N interface is built up by a number of IRPs. The basic structure of the IRPs is defined in [2] and [3].
For the purpose of Fault Management the following IRPs are needed:
• Alarm IRP
• Notification IRP
• Log IRP
(NOTE: This IRP may not be part of Release 1999)
Annex A (informative):
Change history
This annex lists ... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 1 Scope | This document outlines the working methods [to be] used by SMG and its sub-groups and by PT SMG in relation to document management, i.e. handling of specifications, updating procedures, change request procedures, version control mechanisms, specifications status information etc. It complements the rules and procedures ... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 2 Definitions and Abbreviations | Change Control When a specification has been put under change control, changes to the specification require an approval of formal change requests. Rules for change control are defined in section 4.
Closed A closed major version of a specification is still published; however no changes to the major version of the specif... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 3 General responsibilities of the Project Team | The Project Team for SMG (PT, or PT SMG) is responsible for the project management of the work of the TB. This includes editorship and management of specifications once they have been put under TB change control. It also includes preparation of and support for the meetings (including meeting reports) of the TB and its ... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4 Handling of Specifications | This section describes the general procedures and events involved in, and related to, the lifetime of a specification. |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.1 Overview | This section gives an overview on the development of a specification, dealing with the unexceptional cases only, and leaving out details. A more detailed description is given in the remainder of section 4.
A new specification is created in a TB WG. At creation, a rapporteur is nominated. The rapporteur elaborates the f... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.2 Characteristics of a specification | - The specification has a prime responsible TB.
- The specification may have a prime responsible TB WG.
- The specification may have one or more secondary responsible TBs and/or TB WG.
- The specification may have a prime responsible TB Sub-Group below a Working Group as decided by the prime responsible TB WG.
- The s... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.3 Characteristics of a major version of a specification: | A major version 0 or 1 or 2 of a specification has the following characteristics:
- It is either a draft or withdrawn.
- It is TB internal.
A major version w > 2 of a specification has the following characteristics:
- It is either under TB WG Change Control or under TB Change Control or closed or withdrawn.
- It is eit... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.4 Characteristics of a version of a specification | 0.x.y
- draft (or withdrawn)
- TB internal
- no version of the specification has been presented for information to the TB yet
- no major version of the specification is under TB change control yet
1.0.0
- draft (or withdrawn)
- TB internal
- this version 1.0.0 is presented to TB
- for information
- or for information a... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.5 Actions on a specification | In the following subsections the concept of "stability" is used , which is linked to the likelihood that a given specification will change more or less significantly before reaching it's final steady. The attributes "low stability", "medium stability" and "good stability" are used. The assessment of stability cannot be... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.5.1 Actions on a new specification (version 0.x.y) | - A new specification (a specification version 0.0.0) may be created by a TB WG. A rapporteur (more exactly: at least one rapporteur) is assigned by that WG. A prime responsible subgroup of the TB WG may be allocated by the TB WG.
- The rapporteur prepares version 0.1.0 and presents it to the prime responsible TB WG/SG... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.5.2 Actions on version 1.x.y of a specification | - On decision of the prime responsible TB WG, the PT transforms version 0.x.y of a specification into version 1.0.0, performing the necessary - strictly editorial - cleaning up, and version 1.0.0 is presented by the TB WG to the to the prime responsible TB and to the secondary responsible TB SG(s) for information or fo... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.5.3 Actions on version 2.x.y of a specification | - On decision of the prime responsible TB WG, the PT transforms version 1.x.y of a specification into version 2.0.0, performing the necessary - strictly editorial - cleaning up, and version 2.0.0 is presented by the prime responsible TB WG to the prime responsible TB for approval; comments of the secondary responsible ... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.5.4 Actions on version w.x.y of a specification (w > 2) | - On decision of the TB, the PT transforms a version v.x.y of a specification into version w.0.0, performing the necessary - strictly editorial - cleaning up.
- The prime responsible TB WG may agree on Change Requests to the most recent version w.x.y of major version w of a specification. It will then propose these CRs... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.5.5 Actions on the major version of a specification | - The TB may decide to create a new major version >2 of a specification.
- The TB may decide to withdraw a major version of a specification.
- The TB may decide to close a frozen major version of a specification.
- The TB may authorise a major version >2 for publication or decide that it is TB internal.
- The TB may de... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.6 Change Request Regime | Modifications to specifications under TB Change Control are decided by the TB, on the basis of Change Requests (CR). These CRs, described in the following sections, shall in principle only be presented to the TB after having been scrutinised by the TB WG responsible for the concerned specification; comments from second... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.6.1 Change Requests | Whenever an error or an inconsistency is discovered or when a new feature is proposed to be included, a Change Request is produced, normally by the one discovering the error but in consultation with the rapporteur and/or with the PT.
In the case of an essential error corrections, separate Change Requests for each affec... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.6.2 Change Request forms | To ensure an appropriate and consistent way of presenting and documenting Change Requests, there exist standardised front covers (forms) for CRs as well as rules on how to accurately identify the modified parts of the specification.
The purpose of the CR form itself is to provide the relevant management information of ... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.6.3 Contents of Change Requests | Although the CR form shall indicate the details of change, each CR shall have attached the pages of the specification that are affected by the CR, using the latest version of the major version. These pages shall have the proposed modifications clearly marked, by means of the word processor's "revision mode", i.e. new p... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.6.4 Handling of the Change Requests | Entry to the TB WG:
A proposed CR should be brought to the relevant TB WG or, if applicable, to the prime responsible TB SG in charge of the specification concerned and discussed there, before presentation to the TB. If possible it should be distributed, by the source, as soon as possible and prior to the coming TB SG ... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 4.6.5 Updating and release of new versions of the specifications | After TB approval of one or more CRs, the PT produces a new version of the specification (with the version number incremented according to above). |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 5 Availability and distribution of specifications | The latest versions of TB approved and TB WG approved specifications are made available on a TB server (exact location see TB meeting report) by the PT. For specifications (or major versions of specifications) that are not yet under change control, the versions presented to the responsible TB-SG or WG, shall be made av... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 6 Work items | For project management purposes, the work is itemised in Work Items (WI), which are documented, developed and handled as described in this section.
The possible modifications of the specifications are basically of different natures:
- Error corrections; Modifications which correct overlooked errors or inconsistencies i... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 6.1 Creation of a Work Item | When an enhancement of the standard is considered desirable a delegate or delegation can make a proposal by submitting a Work Item Description sheet to the relevant TB or TB WG.
- For new services, features or functions, the TB responsible for Services and System Aspects is the relevant TB. This TB also assigns prime a... |
714fea1a3412b60c57d0fb418fe8bfee | 01.00 | 6.2 Type of Work Items | Modifications of the standard could in principle be of two different types:
- New services/features/functions that in general affects several specifications and several TB-SGs;
- Pure [technical] enhancements that affects a small number of specifications and TB-SGs only (generally only one).
Of these, modifications of ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.