|
|
## TS 33.128 XIRIEvent and IRIEvent tag allocation
|
|
|
|
|
|
#### Temporary tag numbers for CRs
|
|
|
|
|
|
Allocate tags for `XIRIEvent` and `IRIEvent` using the formula:
|
|
|
|
|
|
`(CRnumber * 10) + (0..9 tag offset)`
|
|
|
|
|
|
where `CRnumber` is the CR's number.
|
|
|
|
|
|
**Note**: if more than 10 tags are required by a given CR, seek assistance from the [Maintainers](https://forge.etsi.org/rep/li/trial/-/wikis/Process/Maintainers).
|
|
|
|
|
|
For example:
|
|
|
|
|
|
* CR0219 uses tags: 2190..2199
|
|
|
* CR0223 uses tags: 2230..2239
|
|
|
* CR0311 uses tags: 3110..3119
|
|
|
|
|
|
|
|
|
Rationale: This is to reduce the chance of merge conflict between multiple CRs within a given meeting cycle.
|
|
|
|
|
|
The tags will be normalized by the maintainers before publication, ensuring there are no unnecessary "holes" in the tag numbering.
|
|
|
|
|
|
#### Same message added to both XIRIEvent and IRIEvent
|
|
|
|
|
|
Use the same field name and ASN.1 tag for the same.
|
|
|
|
|
|
#### Message only added to IRIEvent
|
|
|
|
|
|
Add a comment to `XIRIEvent` reserving the tag used by `IRIEvent` field. For example, in `XIRIEvent`:
|
|
|
|
|
|
`-- tag 16 is reserved because there is no equivalent mDFCellSiteReport in XIRIEvent`
|
|
|
|
|
|
#### Message only added to XIRIEvent
|
|
|
|
|
|
Add a comment to `IRIEvent` reserving the tag used by an `XIRIEvent` field. For example, in `IRIEvent`:
|
|
|
|
|
|
`-- tag 100 is reserved because there is no equivalent n9HRPDUSessionInfo in IRIEvent.` |
|
|
\ No newline at end of file |