Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • SA3 LI SA3 LI
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SA3
  • SA3 LISA3 LI
  • Merge requests
  • !17

Merged
Created Jan 18, 2022 by lovieno@lovienoDeveloper

TS 33.128 CR 0299 - Corrections on SUCI coding

  • Overview 1
  • Commits 2
  • Pipelines 2
  • Changes 1

RoutingIndicator is defined in Annex A as INTEGER(0..9999) but TS 23.003 in clause 2.2B states that “Each decimal digit present in the Routing Indicator shall be regarded as meaningful (e.g. value "012" is not the same as value "12").” So, INTEGER is not an appropriate type for the RoutingIndicator parameter. In the ASN.1 module for the internal and external interfaces, a backward compatible solution is introduced to allow indicating the number of meaningful digits for RoutingIndicator parameter, in order to avoid misinterpretations of its value.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: cr/33128/0299