Bear in mind that the TMF models need to cover a variety of jurisdictions. The Open API model is non-opinionated regarding formats of addresses, phone numbers, etc.
You can always make extensions to the model to meet your local needs.
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
Original Message:
Sent: Mar 30, 2023 05:34
From: Dave Milham
Subject: Format for telephone numbers
I did notice a discuss n the structure of e.164 in regex at
Regular Expressions for ITU E.123 and E.164 phone number formats – SecureAuth Support
So the block allocation and quarantining would have to align with those so not just a simple string. Maybe e.164 blocks need to be represented s concatenation of several string flowing this regex proposal?
------------------------------
Dave Milham
TM Forum, Chief Architect
Original Message:
Sent: Mar 29, 2023 05:31
From: Lutz Bettge
Subject: Format for telephone numbers
Thank you!
As mentioned, we are already using the pattern derived from E.164; my question concerned the representation of number ranges, and it was not meant as search parameter, but we are assigning whole blocks of numbers to business customers, so we need to express that in the response e.g. in an ProductOrder, in the Inventory etc. So we need an attribute or characteristic representing not the individual number, but the block as a whole.
I understand that there is no standard like E.164 that defines how to represent a block?
------------------------------
Lutz Bettge
Deutsche Telekom AG
Original Message:
Sent: Mar 29, 2023 04:44
From: Dave Milham
Subject: Format for telephone numbers
As mentioned earlier ITU E.164 is the international standard.
Informative overview on Wikipedia at E.164 - Wikipedia however this does not express search parametes . that is really a local matter . Whether this should be in the TMForum documents depends on a member making a proposal.
------------------------------
Dave Milham
TM Forum, Chief Architect
Original Message:
Sent: Mar 28, 2023 09:19
From: Andy Fuller
Subject: Format for telephone numbers
I am only familiar with the US telephone industry. Internal to today's network it's just a string of digits. With older US telephone networks these had real meaning, but there is less technical division today. We continue to split them into groups to make them easier to read and remember. US phone numbers are divided into a 3-digit NPA (Number Plan Area, aka "area code), 3-digit NSS (Exchange), 4-digit Subscriber or Station Identifier. In the US and Canada (which share Country Code 1) the country code is often omitted. The only meaningful ranges of numbers in the US are in the 4-digit subscriber, as these may be within "private branch exchanges", which are internal telephone switching centers used within companies.
------------------------------
Andy Fuller
AT&T Inc.
Original Message:
Sent: Mar 27, 2023 09:03
From: Lutz Bettge
Subject: Format for telephone numbers
Is there any definition for the format used to represent telephone numbers? Or is it only a string?
We are using a RegEx that restricts the value to the pattern
+<cc>-<ndc>-<sn>[[-]<ddi>]
with
<cc> ... country code
<ndc> ... national destination code
<sn> ... subscriber number
<ddi> ... direct dial in
[...] ... denoting optional parts
as defined e.g. in ITU E.123, E.164 and also aligned with RFC3966.
Our problem:
We also need to express number ranges of two different types:
- "decades", i.e. numbers with the last digit taking any digit, e.g. with wildcards:
"+49-228-181-31?" meaning any possible one-digit extension allowed
"+49-228-181-31??" meaning any possible two-digit extension allowed
...
"+49-228-181-31*" meaning any possible extension allowed
- real ranges, e.g. "+49-228-181-31(00-99)"
Is there any defined format to express the above range types?
If not, should such patterns be defined by TMF OpenAPIs?
Thank you,
Lutz
------------------------------
Lutz Bettge
Deutsche Telekom AG
------------------------------